commit 052a87afdf331d99090c7f6fd72ab3800b412429 Author: ilgiz Date: Fri Oct 9 15:28:00 2026 +0300 srv1c-web:8.3.27.2342 diff --git a/Dockerfile b/Dockerfile new file mode 100644 index 0000000..649fcbe --- /dev/null +++ b/Dockerfile @@ -0,0 +1,84 @@ +FROM debian:12-slim + +# Arguments for build image +ARG S6_OVERLAY_VERSION=3.2.1.0 +ARG SERVER_VERSION=8.3.27.2342 + +# Variables For Container +# Common +ENV LANG=ru_RU.UTF-8 +ENV LC_ALL=ru_RU.UTF-8 +ENV TZ=Europe/Moscow +ENV USER=www-data +# Server +ENV SERVER_VERSION=${SERVER_VERSION} +ENV BASES_DIR=/bases +ENV WORKDIR=/opt/1cv8/x86_64/${SERVER_VERSION}/ +ENV LIC_DIR=/var/1C/licenses +ENV JAVA_HOME=/opt/1cv8/x86_64/${SERVER_VERSION}/jre/ + +# add contrib repo for debian 13 and install requiments +RUN sed -i '/Components:/s/$/ contrib/' /etc/apt/sources.list.d/debian.sources +RUN apt-get -qq update \ + && apt-get -qq install --yes --no-install-recommends \ + ca-certificates \ + wget \ + locales \ + tzdata \ + procps \ + fontconfig \ + imagemagick \ + cabextract \ + ttf-mscorefonts-installer \ + xz-utils \ + libssh-4 \ + iproute2 \ + apache2 \ + libwebkit2gtk-4.0-37 \ + gawk \ + && apt-get clean && apt-get autoremove + +# Set locale and timezone +RUN echo "${LANG} UTF-8" > /etc/locale.gen \ + && locale-gen ${LANG} \ + && update-locale LANG=${LANG} \ + && ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone + +# S6 overlay install +ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp +RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz +ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp +RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz + +# Install 1C Server and license util +ADD ./distr/setup-full-${SERVER_VERSION}-x86_64.run /tmp/distr/1c/ +ADD ./distr/license/ /tmp/distr/license/ +RUN /tmp/distr/1c/setup-full-${SERVER_VERSION}-x86_64.run \ + --mode unattended \ + --enable-components \ + ws,liberica_jre,v8_install_deps,client_thin_fib \ + --disable-components \ + client_full + +RUN /tmp/distr/license/1ce-installer-cli install --ignore-signature-warnings +RUN rm -rf /tmp/distr/* + +# 1c exchange folder +RUN mkdir -p /1cshare && chown -R ${USER}:${USER} /1cshare + +# Apache owns folders +RUN mkdir --mode=770 --parents /var/1C/licenses +RUN chown -R ${USER}:${USER} /var/cache/apache2/ /var/cache/fontconfig/ /var/log/apache2 /var/1C /var/www + +#COPY ./services.d /etc/services.d +COPY ./entrypoint.sh /entrypoint.sh +RUN chmod +x /entrypoint.sh +ENTRYPOINT [ "/entrypoint.sh" ] +# S6 Entrypoint +#ENTRYPOINT ["/init"] +# CMD [ "apache2ctl", "-D", "FOREGROUND" ] +EXPOSE 1540-1541 1545 1560-1591 +EXPOSE 80 443 + +VOLUME ${BASES_DIR} +VOLUME ${LIC_DIR} diff --git a/Dockerfile.save b/Dockerfile.save new file mode 100644 index 0000000..c96537b --- /dev/null +++ b/Dockerfile.save @@ -0,0 +1,84 @@ +FROM debian:12-slim + +# Arguments for build image +ARG S6_OVERLAY_VERSION=3.2.1.0 +ARG SERVER_VERSION=8.3.27.2342 + +# Variables For Container +# Common +ENV LANG=ru_RU.UTF-8 +ENV LC_ALL=ru_RU.UTF-8 +ENV TZ=Europe/Moscow +ENV USER=www-data +# Server +ENV SERVER_VERSION=${SERVER_VERSION} +ENV BASES_DIR=/bases +ENV WORKDIR=/opt/1cv8/x86_64/${SERVER_VERSION}/ +ENV LIC_DIR=/var/1C/licenses +ENV JAVA_HOME=/opt/1cv8/x86_64/${SERVER_VERSION}/jre/ + +# add contrib repo for debian 13 and install requiments +RUN sed -i '/Components:/s/$/ contrib/' /etc/apt/sources.list.d/debian.sources +RUN apt-get -qq update \ + && apt-get -qq install --yes --no-install-recommends \ + ca-certificates \ + wget \ + locales \ + tzdata \ + procps \ + fontconfig \ + imagemagick \ + cabextract \ + ttf-mscorefonts-installer \ + xz-utils \ + libssh-4 \ + iproute2 \ + apache2 \ + libwebkit2gtk-4.0-37 \ + gawk \ + && apt-get clean && apt-get autoremove + +# Set locale and timezone +RUN echo "${LANG} UTF-8" > /etc/locale.gen \ + && locale-gen ${LANG} \ + && update-locale LANG=${LANG} \ + && ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone + +# S6 overlay install +ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp +RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz +ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp +RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz + +# Install 1C Server and license util +ADD ./distr/setup-full-${SERVER_VERSION}-x86_64.run /tmp/distr/1c/ +ADD ./distr/1c_enterprise_license_tools_0.15.28_linux_x86_64.tar.gz /tmp/distr/license/ +RUN /tmp/distr/1c/setup-full-${SERVER_VERSION}-x86_64.run \ + --mode unattended \ + --enable-components \ + ws,liberica_jre,v8_install_deps,client_thin_fib \ + --disable-components \ + client_full + +RUN /tmp/distr/license/1ce-installer-cli install --ignore-signature-warnings +RUN rm -rf /tmp/distr/* + +# 1c exchange folder +RUN mkdir -p /1cshare && chown -R ${USER}:${USER} /1cshare + +# Apache owns folders +RUN mkdir --mode=770 --parents /var/1C/licenses +RUN chown -R ${USER}:${USER} /var/cache/apache2/ /var/cache/fontconfig/ /var/log/apache2 /var/1C /var/www + +#COPY ./services.d /etc/services.d +COPY ./entrypoint.sh /entrypoint.sh +RUN chmod +x /entrypoint.sh +ENTRYPOINT [ "/entrypoint.sh" ] +# S6 Entrypoint +#ENTRYPOINT ["/init"] +# CMD [ "apache2ctl", "-D", "FOREGROUND" ] +EXPOSE 1540-1541 1545 1560-1591 +EXPOSE 80 443 + +VOLUME ${BASES_DIR} +VOLUME ${LIC_DIR} diff --git a/distr/1c_enterprise_license_tools_0.15.28_linux_x86_64.tar.gz b/distr/1c_enterprise_license_tools_0.15.28_linux_x86_64.tar.gz new file mode 100644 index 0000000..d47e393 Binary files /dev/null and b/distr/1c_enterprise_license_tools_0.15.28_linux_x86_64.tar.gz differ diff --git a/distr/Liberica-Notice.txt b/distr/Liberica-Notice.txt new file mode 100755 index 0000000..acb422c --- /dev/null +++ b/distr/Liberica-Notice.txt @@ -0,0 +1,12 @@ +Liberica JRE is used for the operation of some components of 1C:Enterprise 8. +Liberica JRE is distributed under the GNU General Public License, version 2, +with the Classpath Exception. The source text is available upon request +to the technical support service by e-mail v8@1c.ru. The full text +of the Liberica JRE licenses and included third-party components is available +in the LibericaJDK-8-9-10-licenses.pdf file. + +Liberica JRE распространяется под лицензией GNU General Public License, +version 2, with the Classpath Exception. Исходный текст доступен по запросу +в службу технической поддержки по электронной почте v8@1c.ru. Полный текст +лицензий Liberica JRE и включенных сторонних компонентов доступен +в файле LibericaJDK-8-9-10-licenses.pdf diff --git a/distr/LibericaJDK-8-9-10-licenses.pdf b/distr/LibericaJDK-8-9-10-licenses.pdf new file mode 100755 index 0000000..b2050a6 Binary files /dev/null and b/distr/LibericaJDK-8-9-10-licenses.pdf differ diff --git a/distr/all-clients-distr-8.3.27.2342-x86_64.run b/distr/all-clients-distr-8.3.27.2342-x86_64.run new file mode 100755 index 0000000..0b12f47 Binary files /dev/null and b/distr/all-clients-distr-8.3.27.2342-x86_64.run differ diff --git a/distr/docs/en/V8Update.htm b/distr/docs/en/V8Update.htm new file mode 100644 index 0000000..601293b --- /dev/null +++ b/distr/docs/en/V8Update.htm @@ -0,0 +1,1597 @@ +V8Update

1C:Enterprise 8

Version 8.3.27

Version 8.3.26

Version 8.3.25

Version 8.3.24

Version 8.3.23

Version 8.3.22

Version 8.3.21

Version 8.3.20

Version 8.3.19

Version 8.3.18

Version 8.3.17

Version 8.3.16

Version 8.3.15

Version 8.3.14

Version 8.3.13

Version 8.3.12

Version 8.3.11

Version 8.3.10

Version 8.3.9

Version 8.3.8

Version 8.3.7

Version 8.3.6

Version 8.3.5

Version 8.3.4

Version 8.3.3

Version 8.3.2

Version 8.3.1

List of functionalities.

All functionalities, Compatibility mode, 1C:Enterprise language, 1C:Enterprise script, 1C:Enterprise software system, A client application form, Access rights, Access to mobile device features, Accounting registers, Accumulation registers, Add-ins, Administration, Administration tools, Advanced error handling, Analytics - charts, Analytics - dashboards, Analytics - desktop, Analytics - expression language, Analytics - other, Analytics - sources, Analytics system, Application appearance, Applied objects, Attribute fill checks, Automated testing, Autorun, Background and scheduled jobs, Backups, Binary data, Binary data storage, Calculation registers, Calendars, Catalogs, Charts, Charts of accounts, Charts of calculation types, Charts of characteristic types, Client application, Client application form, Client application installation, Client applications, Client/server interaction, Collaboration system, Collaboration System, Command interface, Common attributes / Data separation, Common objects, Configuration comparison and merging, Configuration comparison reports, Configuration extensions, Configuration extensions,, Configuration installation, Configuration properties, Configuration repositories, Cross-platform architecture, Cryptography, Cryptography support, Data Accelerator, Data accelerator, Data access restrictions, Data analysis, Data composition system, Data Composition System, Data display, Data exchange, Data history, Database configuration update, Database configuration updates, Database copies, Database operations, DBMS operations, Defined types, Designer, Developer tools, Development methodology, Development tools, Distributed infobases, Document journals, Documentation, Dumping configurations to files/Restoring configurations from files, Dumping/loading configurations to files, Dynamic list, Dynamic lists, Dynamic update, Error handling, Event log, Export to Microsoft Excel, External data sources, External reports and data processors, File infobase Queries, File mode, File operations, Formatted document, Formatted documents, Full-text search, Functional options, Geographical schemas, Global search, HTML support, Infobase operations, Infobase users, Infobase verification and repair, Information registers, Input by string, Integration service, Interface, InterfaceConfiguration extensions, Internet-enabled functionality, JSON support, Licensing system, Linux, Localization, Location tools, Lock manager, macOS, Managed forms, Managed locks, Metadata objects, Mobile application, Mobile application builder, Mobile Application Builder, Mobile application development, Mobile applications, Mobile client, Mobile device-specific features, Mobile platform, Multimedia support, Multimedia tools, National settings, Navigation links, OData interface, OData operations, OpenID authentication, Operating system, Ordinary forms, PDF document operations, Pictures, Platform algorithms, Predefined data, Print tools, Printing, Printing documents, Printing tools, Processing PDF documents, Queries, Regional settings, Server cluster, Server clusters, Settings storage, Software licensing, Special tools, Speech recognition, Speech synthesis, Spreadsheet document, Spreadsheet documents, Standalone server, Standalone serverDumping configurations to files/Restoring configurations from files, Standard functions, Storing settings, System enumerations, System operation safety, System requirements, Technological log, Telephony, Temporary storages, Text operations, Thick client, Thin client access over the Internet, Third-party software, URLs, Using the clipboard, Web client, Web client and web service publishing tools, Web client, web service, and HTTP service publishing tools, Web links, Web services, Web services and HTTP services, WebSocket operations, Window management, Window-based interface, xBase support, XML and XDTO support, ZIP archive operations, Встроенный язык, Сlient application form.

Version 8.3.27

Version 8.3.27 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
New value for the Compatibility mode configuration property: Version 8.3.26.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.25 was available.Configurations developed using 1C:Enterprise platform version 8.3.26 or earlier can now run on version 8.3.27 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.27 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.26 after the migration to version 8.3.27. Even if you have disabled the compatibility mode (simply enable it again).
WebSocket operations.
Now 1C:Enterprise can function as a WebSocket client. This feature is available for the thin, thick, and web clients and the 1C:Enterprise server. +You can create WebSocket clients in the "Common - WebSocket clients" branch of the configuration object tree. +New global context properties: WebSocketClientConnectionHandlers and WebSocketClients.This feature was not provided.1C:Enterprise applications can function as a WebSocket client.
Collaboration system.
New feature: global search can search by context conversation messages. The maximum number of found messages (for both noncontext and context conversations) is 20.Previously, global search only searched in noncontext conversation messages. The maximum number of found messages was 15.Expanded global search features.
Data Accelerator.
Server clusters.
The Data Accelerator now allows you to choose how the database is stored: either entirely in RAM, or using both RAM and disk space. +You can set the storage directory using the standard mechanism for changing data storage directories for cluster services (specifically, the DataAcceleratorService). This functionality is supported by all cluster server administration tools. +The DatabaseCopiesManager.Add() method has a new DataAcceleratorDataStorageVariant parameter that allows you to specify the location of the Data Accelerator database. Introduced a new property: DatabaseCopyManager.DataAcceleratorDataStorageVariant. +The standard database copy management tool now supports this feature in both the new copy creation dialog and the list of database copies.Until now, the Data Accelerator only stored the database in RAM. This meant that in the event of an unexpected shutdown of the Data Accelerator or the server cluster, the database had to be repopulated from the main database, causing delays or even the inability to generate required reports.Now, the Data Accelerator can be set up so that it doesn't require repopulating the database upon restart. This change ensures quicker access to the data you need.
Database copies.
Now you can get detailed information about the database copy state. With this information, you can evaluate the current database copy state, the copy update state, and so on. You can now run database copy updates in the background using a system background job. +New method: DatabaseCopiesManager.UpdateInBackgroundMode().

New method: DatabaseCopyManager.GetCopyInfo(). +You can view the state of selected copy instances in the standard database copy management tool. The copy update is now started in the background.

This feature was not provided.

You could get only the date of the last data replication.

Advanced troubleshooting when operating with database copies.
Cryptography support.
You can now check the status of certificates at any point in the past. Use the UniversalVerificationDate parameter of the crypto manager's CheckCertificate() and CheckCertificateAsync() methods. +New features for cryptography certificates include:
  • Checking the validity period of the private key. Use the UniversalStartDateOfPrivateKey and UniversalEndDateOfPrivateKey properties of the CryptoCertificate object.
  • Retrieving a list of certificate extensions. Use the CertificateExtensions property of the CryptoCertificate object.
  • Obtaining certificate extensions in raw form. Use the CertificateExtensionsAsRawData property of the CryptoCertificate object.
  • Identifying the algorithms used to generate the public key and signature, along with obtaining the digital signature itself. Use the PublicKeyAlgorithm, SignatureAlgorithm, and SignatureValue properties of the CryptoCertificate object.

The CryptoCertificate.Extensions property is deprecated. Instead, use CryptoCertificate.CertificateExtensions.

These features were not provided.Enhanced the cryptography certificate functionality. You can now verify that the private key is usable (i.e., it hasn’t expired).

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Collaboration system.
The thin client running on Linux now supports video calls.On Linux, you could only use video calls in the web client.Advanced collaboration system features.
Speech recognition.
Administration tools.
Upgrade: the tool for managing local speech recognition is updated.
  • New checkbox for the dialog box for creating a client/server infobase: Deny local speech recognition.
  • New parameter for the conf.cfg file located in the infobase directory (for the file infobase): DisableLocalSpeechToText.
  • In the dialog box for adding a file infobase, the Deny local speech recognition checkbox is deleted.
  • The /DisableLocalSpeechToText command-line option of the client application startup is deleted.
Previously, other tools were used to manage local speech recognition:
  • In the dialog box for adding an infobase, the Deny local speech recognition checkbox was available.
  • The /DisableLocalSpeechToText command-line option of the client application startup was available.
Local speech recognition management is unified with other similar 1C:Enterprise tools.
Server clusters.
When an abnormal termination dump is generated by the cluster monitoring tool, the SIGABRT signal is used to complete the process and generate the dump.When an abnormal termination dump was generated by the cluster monitoring tool, the SIGSEGV signal was used to complete the process and generate the dump.When 1C support analyzes abnormal termination dumps, it will be easier to distinguish between dumps generated by the cluster monitoring tool (SIGABRT) and dumps generated as a result of critical application errors (SIGSEGV).
Add-ins.
Server clusters.
Now you can forcibly terminate the session with isolated attachment of add-ins, even if the session to terminate is waiting for an add-in method execution.Previously, you could not forcibly terminate the session with isolated attachment of add-ins if the session to terminate was waiting for an add-in method execution.Improved server cluster administration. Reduced the number of situations when the administrator cannot terminate the session which locks the normal operation of the system.
Collaboration system.
During video calls, you can inform call participants about the desire to speak out or ask a question (raise your hand). Several people can raise their hand simultaneously.

Information about the raised hand is displayed in the frame of the user who raised their hand. The number of participants who raised their hand is also displayed in the video call window. Users who raised their hand are displayed in the order they raised it (the earlier they raised their hand, the higher they will be in the list).

If the user who raised their hand leaves the video call, the system will lose their raise status. After returning, this user will need to raise their hand again if it is still necessary.

This feature was not provided.In conversations of group video calls, it will become easier to "request the floor", while the number of attempts by participants to interrupt each other will not decrease.
Standard functions.
Binary data storage.
The interface of the standard Binary data storage management function is improved to make the function more user-friendly and convenient.The interface of the standard Binary data storage management function was less user-friendly and convenient.Improved interface of the standard Binary data storage management function.
Client application.
When starting a client application with a base configuration, a form with a progress indicator will be displayed for analyzing the configuration and hardware of the current computer.Previously, when starting a client application with a base configuration, while analyzing the configuration and hardware of the current computer, the user was not informed in any way about what the client application was doing. As a result, it looked like the system was "hanging".We expect this feature to reduce the number of user complaints about system freezes when starting base configurations (especially with a large amount of metadata).
Administration tools.
New optional parameter for the command to complete the background update of the Designer agent (config update‑db-cfg --background-finish): --session-terminate. It allows you to manage the forced termination of active sessions if you need to set an exclusive database lock.

New optional parameter for the background update completion command (config update‑db-cfg --background-finish) and the interactive configuration update command (config update-db-cfg) of the Designer agent: --session-terminate-message. It allows you to specify the reason for terminating the session on the client.

This feature was not provided.Unified interactive behavior of Designer and the behavior in agent mode.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Binary data storage.
New feature: data writing to the built-in binary data storage is improved.Writing to the built-in binary data storage took more time.Faster data writing to the built-in binary data storage.
Cryptography support.
Linux.
Now the cryptography manager creates a certificate chain faster on Linux. Previously, the cryptography manager needed more time to create a certificate chain on Linux. Faster creation of a certificate chain by the cryptography manager on Linux.
Information registers.
If the information register record was previously read from the infobase, then when calling the Write() method of the information register record manager in replacement mode, the current values of key fields are checked to match the values of the read record. If the key fields match, the current record is updated.If the information register record was previously read from the infobase, then when calling the Write() method of the information register record manager in replacement mode, writing was always performed in two steps: deleting an existing record and writing a new one.Faster writing of single information register records if all key fields of the record remain unchanged during writing.
Technological log.
The deletion of outdated technological log files does not lock user operations and is performed in the background.The deletion of outdated technological log files could lock user operations (if the number of deleted files was large) and was performed by the server cluster in synchronous mode.Reduced impact of technological operations of the server cluster on user operations.
macOS.
New features: the client application operation is optimized when running on macOS. Rendering of client application windows and scrolling of large spreadsheet documents is accelerated.Previously, when the client application was running on macOS, the speed was low, and displaying and scrolling the contents of the client application windows took a long time.Optimized operation of the client application when running on macOS.
DBMS operations.
Server clusters.
Deletion of temporary tables (and their indexes) is accelerated when running on the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.Deletion of temporary tables (and their indexes) took more time when running on the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.Accelerated deletion of temporary tables (and their indexes) when running on the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.
Development tools.
Now you can build a metadata index in Designer in the background.

To disable it, use the /DisableBackgroundIndexBuild command-line option.

Previously, metadata index building started in Designer when this index was first used by the user. This locked the execution of the requested operation until the index was generated.The first use of the following operations can be accelerated after changing the metadata: searching for references to the configuration object, deleting the configuration object, and renaming the configuration object. This will happen if the metadata index managed to rebuild in the background.
Client application.
The time of the first thin client startup in a file infobase is reduced after performing the following operations:
  • Creating a new infobase.
  • Restoring an infobase from a DT file.
  • Restoring a configuration from a CF file.
  • Updating an infobase configuration.
Previously, the first thin client startup in a file infobase took more time.Reduced time of the first thin client startup in a file infobase in some cases.
Development tools.
The search for references to configuration objects, as well as the operations that use this search (renaming the configuration object and deleting the configuration object) are optimized in Designer.Previously, search for references to configuration objects in Designer took more time.Accelerated search for references to configuration objects and the related operations (renaming and deleting the configuration object) in Designer.
DBMS operations.
Server clusters.
The server cluster operation under load is optimized when using the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.The server cluster operation under load when using the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems was non-optimal.Optimized the server cluster operation under load when using the PostgreSQL, Postgres Pro, Tantor SE 1C, and Pangolin database management systems.
Full-text search.
The algorithm of generating a full-text search index is improved to reduce the index volume. You can see the improvement on full-text search indexes of a great size (over 10 GB).The previous algorithm generated indexes of a greater size.Reduced full-text search index volume for great indexes (over 10 GB).
DBMS operations.
Upgrade: temporary table cleanup takes less time when using the Microsoft SQL Server and PostgreSQL DBMS (and inherited DBMS) in case of heavy load on infobases with many tables.Previously, temporary table cleanup took more time when using the Microsoft SQL Server and PostgreSQL DBMS (and inherited DBMS) in case of heavy load on infobases with many tables.Faster temporary table cleanup when using the Microsoft SQL Server and PostgreSQL DBMS (and inherited DBMS) in case of heavy load on infobases with many tables.
Data accelerator.
Some types of queries, including queries to columns with variable length, are optimized. +Improved Data accelerator stability in case of low RAM during query execution.Some types of queries, including queries to columns with variable length, required more computer resources. +Data accelerator was unstable when executing queries in case of a lack of RAM.Improved Data Accelerator performance.
Full-text search.
A computer now uses less RAM when generating and merging full-text search indexes.Generating and merging full-text search indexes required more RAM.Reduced RAM consumption when generating and merging full-text search indexes.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Applied objects.
New property for a metadata object that describes a table: LineNumberLength. You can use this property to manage the number of rows that can be saved in the applied object table. The allowed property values are 5, 6, 7, 8, and 9. The property cannot be changed in the extension.

This change is not implemented in 8.3.26 compatibility mode.

An applied object table could not contain more than 99,999 rows (the length of the row number is 5 decimal places).You can manage the number of rows that can be saved in the applied object table. If necessary, you can save 999,999,999 rows in the object table.
Infobase users.
Administration tools.
Client application.
You can authentiate over an email. Email authetication is unavailable when using the parameterized launch mode.

New property: InfoBaseUser.EmailAuthentication.

New methods for the AdditionalAuthenticationSettingsManager object: SetEmailAuthenticationSettings() and GetEmailAuthenticationSettings().

New object: EmailAuthenticationSettings.

New property: PasswordRecoverySettings.VerificationCodeEffectivePeriod.

New system enumeration value: AuthenticationMode.EmailAuthentication.

New command of the command-line for the client application startup: /EmailAuth.

For the type attribute of the method element of the default.vrd file (point.authentication.logonView) new email value.

There is now more information for event log events:

  • _$User$_.New,
  • _$User$_.NewError,
  • _$User$_.Update,
  • _$User$_.UpdateError,
  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdate,
  • _$InfoBase$_.

We will inform you about the launch of the standard service for sending emails with a confirmation code for signing in via email in an information letter.

This feature was not provided.Extended the list of infobase authentication options.
Administration tools.
Application installation utilities (autorun and SetupV8, Read more.) now can define the format of the application distribution package: unpacked or a ZIP archive. When an archive is found, the utilities will automatically unpack this archive, then install and delete temporary files.The application installation utilities were able to work only with unpacked application distribution packages. The user needed to unpack the distribution package manually and then run the installer.Simplified installation of applications.
Binary data storage.
You can create an external binary data storage within the S3 container. For example, if the number of containers a user can create is limited. You can specify a path to the binary data storage inside the S3 container.

New property: BinaryDataExternalStorageConnectionParameters.Directory.

You can split import a file to the storage if there is a size limit for data to transfer. The part size is selected automatically.

A file is split received from the storage. A file part equals 100 MB and you cannot set up the size.

New processing of the request quantity limitation for the S3 container. If there is a limit to the number of requests, the read/write request execution is attempted multiple times with delay. You have 4 attempts maximum. Timeout between attempts does not exceed 20 seconds.

These features were not provided.External binary data storage helps to consider some S3 container limitations.
Server clusters.
Binary data storage.
Administration tools.
The 1C:Enterprise server cluster administration tools now include features for managing binary data storage:
  • New 1C:Enterprise language object: AdministrationBinaryDataStorage. +New method: AdministrationInfoBase.GetBinaryDataStorages.
  • New interface for the COM connector: IBinaryDataStorageInfo. New methods for the IWorkingProcessConnection interface: GetInfoBaseBinaryDataStorages(), ClearBinaryDataStorageUnusedSpace(), CreateBinaryDataStorageFullBackup(), CreateBinaryDataStorageDifferentialBackup(), LoadBinaryDataStorageFullBackup(), LoadBinaryDataStorageDifferentialBackup().
  • New object in the Java administration server interface: IBinaryDataStorageInfo. New methods for the IAgentAdminConnection object: getBinaryDataStorages(), сlearBinaryDataStorageUnusedSpace(), createBinaryDataStorageFullBackup(), createBinaryDataStorageDifferentialBackup(), loadBinaryDataStorageFullBackup(), loadBinaryDataStorageDifferentialBackup().
  • New mode for the rac utility: binary-data-storage. Specified parameter assignment for the Infobase mode (available in the built-in utility help).
  • New mode for the ibcmd utility: binary-data-storage.
  • Now you can view binary data storages connected to the infobase when using the cluster administration console and the Server management function. New subordinate item of the Binary data storage for the infobase detail item.
These features were not provided. Binary data storage administration was only possible by using the storage API.Administrating binary data storages is now similar to administrating other server clusters.
Collaboration system.
To integrate the collaboration system with WhatsApp, you can send a template message to a user who has not yet written to the integration user (a new user).

New property for the CollaborationSystemConversation and CollaborationSystemConversationsFilter objects: ExternalID.

For WhatsApp integration, the ExternalID property is filled with the phone number of the integration user.

For a WebHook conversation, users specified as default integration users are automatically added to the conversation if, upon receiving the first message, the conversation has no users other than an external integration user.

This feature was not provided.The application can start a conversation with a user if integration with WhatsApp is used.
Data composition system.
Now you can use formatted strings (templates, conditional appearance, using 1C:Enterprise language functions that return a formatted string, and other) during output to a spreadsheet document in the data composition system. Formatted strings are ignored during output to the chart.

Interactive tools for data composition system now support formatted strings.

New appearance items for the DataCompositionAreaTemplateFieldAppearance.AvailableParameters object: BackColor, TextColor, Font, MarkNegatives, Picture, and TextPositionRelativeToPicture. +The Text appearance item of the DataCompositionAppearance.AvailableParameters object now supports the FormattedString type.

The Presentation() function of the expression language of the data composition system returns a value of the FormattedString type if the type of the parameter value is also FormattedString.

This change is not implemented in 8.3.26 compatibility mode.

The data composition system did not support formatted strings.

For cells that display multiple fields, the appearance was applied to the whole cell.

The Presentation() function of the expression language of the data composition system returned an empty string for a value of the FormattedString type.

Expanded appearance features when outputting a report based on the data composition system to a spreadsheet document.
Spreadsheet documents.
When you set a value of the FormattedString type to the cell parameter of a spreadsheet document, the parameter formatting is saved in the resulting document. For this, the resulting cell becomes a cell with a formatted text.

The basic format for the inserted parameter value is:

  • For a cell with a parameter: the cell format.
  • For a simple cell with a template: the cell format.
  • For a formatted cell with a template: the format of the first "[" character in the parameter name.

This change is not implemented in 8.3.26 compatibility mode.

This feature was not provided.

The set value was reduced to plain text, the text type of the resulting cell remained the same as the text type of the cell with the parameter in the template.

Expanded spreadsheet document appearance features.
Database copies.
Upgrade: changed the system behavior when updating data in a database copy that runs on Microsoft SQL Server using replication Version 2. If, during data replication, a new infobase table cannot be connected to the change data capture (CDC), all tables that were previously connected to the change data capture continue to be updated. After updating, an exception of the DatabaseCopyError category is thrown with a text describing the issue and containing a list of tables that are not connected to the tool. For a batch update, an exception is thrown after updating only if all tables added to the change data capture (CDC) are ready to run queries.

To retry connecting new tables to the change data capture, update the copy data again while reducing the load on the original infobase.

The system behavior when updating data in a database copy running on Microsoft SQL Server using replication Version 2 was different. If, during data replication, a new database table could not be connected to the change data capture (CDC), the update was stopped and the source text of the SQL Server error, which was difficult to understand, was displayed to the user.Improved diagnostics and system behavior in case of issues when updating data in a database copy running on Microsoft SQL Server.
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.20.The format version of configuration dump to XML files was 2.19.Configuration dump to XML files supports new platform features.
Database copies.
Data Accelerator.
  • If a low memory error occurs while executing an SQL query on a database copy hosted in the Data Accelerator, the copy is not turned off.
  • If the query settings for the database copy allow the query to be executed on another copy (or on the primary database), the query is executed without any error notification to the user.
  • Conversely, if the query settings do not permit execution on another copy (or on the primary database), the query terminates with an error. The user receives an error message based on the platform mechanism used. In this case, the Data Accelerator error is the cause of the error displayed.
If a low memory error occurs while executing an SQL query on a database copy hosted in the Data Accelerator, the query is terminated with an error and the copy is marked as turned off. When you turn on the copy later, it will be fully updated.Reduced number of unexpected query terminations when accessing database copies in the Data Accelerator. Reduced frequency of unexpected full data updates in Data Accelerator-hosted database copies.
Data Accelerator.
Data Accelerator authentication and connection errors are categorized under ErrorCategory.DatabaseCopyError.Data Accelerator authentication and connection errors are categorized under ErrorCategory.StoredDataError.Authentication and connection errors in Data Accelerator have been more accurately categorized and described to better reflect actual usage scenarios.
Data composition system.
If the Value property of the DataCompositionAreaTemplateValueCollectionCell object is set to Undefined, XDTO serialization of such object does not result in an error.If the Value property of the DataCompositionAreaTemplateValueCollectionCell object was set to Undefined, XDTO serialization of such object resulted in an error.Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Web client.
System requirements.
Microsoft Windows XP, Windows Vista, Server 2003, and Server 2008 are no longer supported.

For the web client in Mozilla Firefox, the web browser version must be 68 or later.

Previously, 1C:Enterprise supported Microsoft Windows XP, Windows Vista, Server 2003, and Server 2008.

For the web client in Mozilla Firefox, the web browser version had to be 52 or later.

Ended support of outdated operating systems and web browsers.
Server clusters.
Infobase users.
Administration tools.
Now you can allocate user sessions by production servers. The allocation is performed using functionality assignment rules. Users are grouped either by name or by assignment rule key.

New property: InfoBaseUser.AssignmentRuleKey. You can edit this property using the standard user list tools in Designer in 1C:Enterprise mode.

New additional parameters for functionality assignment rules: UserName and UserAssignmentRuleKey.

This feature was not provided.

Sessions of new users were allocated by production servers sequentially in accordance with the load balancing tools.

You can transfer sessions of individual users or user groups to production servers.
Server clusters.
Administration tools.
Now you can set up the schedule for restarting working processes of server cluster. You can set the schedule for the entire cluster as well as for each working process individually (it has the priority over the entire server cluster schedule). Cluster working processes (if multiple) are restarted sequentially. Schedule format is same as the cron utility schedule format (in the Linux OS). The Restart interval parameter of the server cluster properties is deprecated and not used for operations.

Now you can disable a specific working process. +The 1C:Enterprise language objects now have:

  • New object property: AdministrationCluster.RestartSchedule.
  • New object property: AdministrationWorkServer.RestartSchedule.
  • New method object: AdministrationWorkProcess.TurnOff().

Objects of the COM interface of the server cluster administration now have:

  • New object property: IClusterInfo.RestartShcedule.
  • New object property: IWorkingServerInfo.RestartSchedule.
  • New object property: IWorkingProcessInfo.TurnedOn.
  • New object method: IServerAgentConnection.TurnOffWorkingProcess().
  • The IClusterInfo.LifeTimeLimit property is deprecated and not recommended to use.
  • The IWorkingProcessInfo.IsEnable() method is deprecated.

Interface administration objects from Java now have:

  • New object methods: IClusterInfo getRestartShcedule() and setRestartShcedule().
  • New object methods for IWorkingServerInfo: getRestartShcedule() and setRestartShcedule().
  • New object property: IWorkingProcessInfo.TurnedOn().
  • New object method: IAgentAdminConnection.turnOffWorkingProcess().
  • The IWorkingProcessInfo.isEnable() method is deprecated.

The rac utility now have the following start line commands:

  • --restart-schedule for the cluster and server modes.
  • --turn-off for the process mode.
This feature was not provided.

Previously, you could specify a working process restart interval counted off only from the working process restart point.

Now setting up restart time for working processes of the server cluster is more flexible.
Development tools.
After a Designer agent runs the infobase-tools restore-ib command:
  • Warning that it is required to reconnect to the Designer agent is displayed (interactive in text mode, informative when displaying results in a json file).
  • The infobase session is terminated. SSH connection is terminated.
  • The Designer agent is not restarted.
  • To continue operations, reconnect to the infobase (the Designer agent process remains the same).
After a Designer agent ran the infobase-tools restore-ib command:
  • Warning that the Designer agent is restarted was displayed.
  • The Designer agent was restarted.
  • To continue operations, it was necessary to reconnect to the infobase, but the Designer agent process was different.
Synchronized Designer agent behavior with the standalone server behavior when performing the same operation.

Table of contents

Renamed objects

ObjectThe old nameThe new name
English name of the AdministrationWorkProcess.Enable object property. The former name is supported for compatibility purposes. +
  • Enable.
  • TurnedOn.
Name of the standard function for binary data storage management.
  • Binary data storage management.
  • Binary data storages management.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
The mobile version of 1C:Enterprise now supports Android 15. The mobile version of 1C:Enterprise supports Android versions 5 - 15.Previously the mobile 1C:Enterprise version supported Android versions 5 - 14.Now the mobile 1C:Enterprise version supports the latest Android versions.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
WebSocket operations.
New method to get the WebSocket connection state: WebSocketClient.GetConnectionState().

New ID: WebSocket. It is used to describe the system object related to WebSocket in the event log, debugger, and so on.

You could find out the WebSocket connection state only after receiving the corresponding object. It was impossible to get the connection state from the WebSocket client.

It was impossible to identify actions with WebSockets that occurred in the event log, debugger, and so on.

Simplified check of WebSocket client connection state.

Simplified identification of objects related to WebSockets in the event log, debugger, and so on.

Development tools.
When using EDT, unlimited growth of metadata cache used by Designer and the thick client is excluded.Previously, when using EDT, there was sometimes an unlimited growth of metadata cache used by Designer and the thick client. This led to an unexpected depletion of free space on the hard drive where metadata cache (user profile) was located.Excluded unlimited growth of metadata cache. Significantly reduced probability of running out of free space on the hard drive where metadata cache was located due to the increase in the cache file size.
Mobile application builder.
Mobile 1C:Enterprise version 8.3.27 is now supported in the mobile application builder.Mobile 1C:Enterprise version 8.3.27 was not supported in the mobile application builder.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
System requirements.
The following Linux distribution packages are no longer supported:
  • Alt Linux 8 SP.
Previously, 1C:Enterprise supported the following Linux distribution packages:
  • Alt Linux 8 SP.
Outdated Linux distribution packages are no longer supported.
Documentation.
The documentation and Syntax Assistant now specify that picture sets (in ZIP archives) can be used in form item properties of the client application.Previously, the documentation and Syntax Assistant did not indicate that picture sets (in ZIP archives) could be used in form item properties of the client application.Updated platform documentation.
PDF document operations.
1C:Enterprise now supports the JBig2 format for displaying and printing PDF documents.The JBig2 format was not supported when displaying and printing PDF documents.Improved PDF format support.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1С: 13.20, 13.21, 14.17, 14.18, 15.12, 15.13.
  • Postgres Pro Standard: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.
  • Postgres Pro Enterprise: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.
  • Postgres Pro CERT Standard: 14.17.1, 14.18.1, 15.12.1, 15.13.1.
  • Postgres Pro CERT Enterprise: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.

DBMS version bitness: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These Postgres Pro DBMS versione were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1С: 16.8, 16.9, 17.4, 17.5.
  • Postgres Pro Standard: 16.8.1, 16.9.1, 17.4.1, 17.5.1.
  • Postgres Pro Enterprise: 16.8.1, 16.9.1, 17.5.1.
  • Postgres Pro CERT Standard: 16.8.1, 16.9.1, 17.4.1, 17.5.1.
  • Postgres Pro CERT Enterprise: 16.8.1, 16.9.1, 17.5.1.

DBMS version bitness: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.22 or later.

Supported operating systems are defined by a DBMS vendor.

These Postgres Pro DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Pangolin DBMS version 6.4.2. and 6.5.1. +Supported processors: x86-64. +Supported operating systems are defined by a DBMS vendor.Previously, 1C:Enterprise did not support these Pangolin DBMS versions.Extended list of supported DBMS.
Mobile platform.
Mobile client.
The mobile version for Android now supports Google's new requirements for operations with images and video files. The appearance of the file selection dialog box has changed in terms of photo and video selection.

To enable support for the new requirements, rebuild the mobile application with a new mobile version and publish it.

The mobile version for Android did not support Google's new requirements for operations with images and video files.Implemented support for Google's new requirements for operations with images and video files in the mobile version for Android.
System operation safety.
Documentation.
The documentation now contains information that during the execution of some configuration object and subscription handlers, unsafe operation protection is disabled. After the handler is executed, unsafe operation protection is enabled again (if it was enabled before the handler was called).

To enable unsafe operation protection in event handlers manually, use the implemented SetUnsafeActionProtectionDisabled() and GetUnsafeActionProtectionDisabled() global context methods. The methods are not available in the extension.

The documentation did not contain information that unsafe operation protection is disabled in event handlers of object modules.

It was impossible to return unsafe operation protection if it was necessary in the event handler.

You can use unsafe operation protection when the platform disables this protection.
System operation safety.
When you open a URL using an HTML document field, unsafe operation protection is active if enabled. To enable this mode, use the user property or the conf.cfg configuration file.

The positive answer to the system's question is recorded by user and infobase. The negative answer is not recorded, and the confirmation request is displayed the next time you try to open the URL.

When you opened a URL using an HTML document field, unsafe operation protection was not active.Improved system security when using the HTML document field.
Common objects.
If, when solving (by any algorithm) a system of equations or its part using the SystemOfLinearEquationsCalculation object, the exact solution cannot be obtained with the specified accuracy (in the AdequateAccuracy property) in the specified number of iterations (in the IterationCount property), the solution that was found in the specified number of iterations is returned, but it may not correspond to the specified accuracy criterion.If, when solving a system of equations or its part using the SystemOfLinearEquationsCalculation object, the exact solution was not obtained with the specified accuracy (in the AdequateAccuracy property) in the specified number of iterations (in the IterationCount property), the solution of the system or its part was reset to zero.If the exact solution of a system of linear equations cannot be obtained with the specified accuracy in the specified number of iterations, a solution that may not meet the specified accuracy criterion is returned.
DBMS operations.
System requirements.
The system now supports Tantor:
  • SE 1C DBMS versions 14.17.0, 15.12.0, 15.14.2, 15.15.0, 16.8.0, 16.10.2, 16.11.0, 17.5.0, 17.6.0, 17.7.0.
  • Certified 1C versions 15.12, 15.14.1, 16.8, 16.10.0, 16.11.0.

Processor architectures supported by DBMS: x86-64.

Supported operating systems are defined by a DBMS vendor.

Previously, 1C:Enterprise did not support these Tantor DBMS versions.Extended list of supported DBMS.
Spreadsheet documents.
Converting a spreadsheet document into a compact format will always be completed in an adequate time.Converting a spreadsheet document into a compact format could lead to an emergency system shutdown.Eliminated unexpected system behavior.
Linux.
System requirements.
1C:Enterprise now supports Mos.OS Server for the Intel architecture.This feature was not provided.Extended list of supported operating systems.
DBMS operations.
System requirements.
The system now supports PostgreSQL DBMS version 18 (x86-64).This PostgreSQL DBMS version was not supported.Reduced number of certificate check errors when accessing Russian websites.
Collaboration system.
New feature: improved audio transmission (including improved noise reduction and echo cancellation) when making video calls in the collaboration system. Improved stability of video calls.The collaboration system had issues with sound in video calls.Improved sound handling in the collaboration system.
Collaboration system.
You can now integrate the collaboration system with MAX instant messaging systems.This feature was not provided.Advanced features for collaboration system integration with instant messaging systems.
Infobase users.
Administration tools.
Client application.
If the standard 1C email service is used for authentication operations (such as email authentication or password recovery), the ITS portal user credentials must be specified in the client application. In other words, anonymous sending of emails is no longer supported. The protocol of interaction between the platform and the standard email service is changed. When configuring a custom SMTP service for user authentication or password recovery via email, you can now set up authentication on the mail server.

New properties for the GetPasswordRecoverySettings and GetEmailAuthenticationSettings objects: SMTPSecureAuthenticationOnly, TokenAuthentication, AccessToken, and Sender.

If the standard 1C email service was used for authentication operations (such as email authentication or password recovery), anonymous access to the mail server was used to send emails.Improved security of sending emails when using the standard 1C email sending service.
Internet-enabled functionality.
New feature: an intermediate certificate of the Federal Treasury of the Russian Federation is added to the cacert.pem and cacertnx.pem files.The intermediate certificate of the Federal Treasury of the Russian Federation was missing in the cacert.pem and cacertnx.pem files.Reduced number of connection errors with the Unified Information System in procurement.

Table of contents

Transition from the previous version to the version 8.3.27

Table of contents

Version 8.3.26

Version 8.3.26 includes known bug fixes and functionality modifications. +

Data accelerator graduated out of beta.

Data accelerator requires CORP license.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
New value for the Compatibility mode configuration property: Version 8.3.25.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.24 was available.Configurations developed using 1C:Enterprise platform version 8.3.25 or earlier can now run on version 8.3.26 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.26 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.25 after the migration to version 8.3.26. Even if you have disabled the compatibility mode (simply enable it again).
Development tools.
Now you can notify the client application from the server without using the collaboration system.

New global context property: ClientNotifications.

New property: BackgroundJob.ParentSessionNumber.

New client notification service for the cluster manager.

New parameter for the standalone server: --clnt-notif-data.

This feature is available only for a PROF license.

Previously, you could notify the client application from the server either using the collaboration system or by constantly polling the server by the client application to get the necessary information.You can notify the client application from the server without using the collaboration system or constantly polling the server by the client application, which reduces system performance.
Configuration extensions.
Now you can create native document journals in extensions. Such journals can include any system documents.This feature was not provided.Advanced configuration extension features.
Applied objects.
Development tools.
Now you can get datasets from the infobase filtered by reference list.

New method for the CatalogManager, DocumentManager, ChartOfCharacteristicTypesManager, ChartOfAccountsManager, ChartOfCalculationTypesManager, ExchangePlanManager, BusinessProcessManager, and TaskManager objects: SelectByRefs().

This feature was not provided.Simplified batch processing of an object list when the list is known in advance. However, not all objects may be changed.
Information registers.
For a record set of an independent information register, you can now update information register records that have the same key fields as the records present in the record set.

New system enumeration value: ReplacementMode.Update.

This feature was not provided.Simplified and improved mass update of records in the information register. For example, it is required to fill a new register resource or attribute with a fixed value after adding this resource.
Event log.
Implemented the following event log events:
  • Users. Changing access rights (_$User$_.PermissionChange). Generated when user access rights are changed.
  • Infobase. Changing role (_$InfoBase$_.RoleUpdate). Generated when the application role changes. A separate event log event is generated for each role.
  • Infobase. Changing session start lock (_$InfoBase$_.SessionLockChange). Generated if the infobase session start lock is set.
  • Infobase. Error changing session start lock (_$InfoBase$_.SessionLockChangeError). Generated if an error occurs when setting the infobase session start lock.
  • Infobase. Modifying regional settings (_$InfoBase$_.RegionalSettingsChange). Generated if the regional infobase settings are changed.
  • Infobase. Error changing regional settings (_$InfoBase$_.RegionalSettingsChangeError). Generated if an error occurs while changing the regional infobase settings.
  • Infobase. Error deleting infobase data (_$InfoBase$_.EraseDataError). Generated when an error occurs while deleting infobase or data area data.
  • Infobase. Error changing configuration (_$InfoBase$_.ConfigUpdateError). Generated if an error occurs while saving the configuration.
  • Infobase. Error during background database configuration update (_$InfoBase$_.DBConfigBackgroundUpdateError). Generated if an error occurs during a background database configuration update.
  • Infobase. Adding database configuration extension (_$InfoBase$_.DBConfigExtensionInsert). Generated when adding an infobase configuration extension.
  • Infobase. Error adding database configuration extension (_$InfoBase$_.DBConfigExtensionInsertError). Generated when an error occurs while adding an infobase configuration extension.
  • Infobase. Deleting database configuration extension (_$InfoBase$_.DBConfigExtensionDelete). Generated when an infobase configuration extension is deleted.
  • Infobase. Error deleting database configuration extension (_$InfoBase$_.DBConfigExtensionDeleteError). Generated when an error occurs while deleting the infobase configuration extension.
  • Infobase. Changing exclusive access mode to current area (_$InfoBase$_.ExclusiveModeChange). Generated when the exclusive access mode to the infobase or data area is changed.
  • Infobase. Error changing exclusive access mode to current area (_$InfoBase$_.ExclusiveModeChangeError). Generated when an error occurs while changing the exclusive access mode to the infobase or data area.
  • Infobase. Changing administrative parameters (_$InfoBase$_.AdministrationParametersChange). Generated when the infobase parameters are changed in the server cluster.
  • Infobase. Changing security profile (_$InfoBase$_.SecurityProfileChange). Generated for each infobase whose settings contain a security profile to change.
  • Session. Changing current area (_$Session$_.DataZoneChange). Occurs when the current data area is changed.
  • Session. Error changing current area (_$Session$_.DataZoneChangeError). Occurs when an error occurs while changing the current data area.
  • Session. Connecting external data processor (_$Session$_.ExternalDataProcessorConnect). Occurs when connecting to an external data processor session.
  • Session. Error connecting external data processor (_$Session$_.ExternalDataProcessorConnectError). Occurs when an error occurs when connecting to an external data processor session.
  • Session. Connecting external report (_$Session$_.ExternalReportConnect). Occurs when connecting to an external report session.
  • Session. Error connecting external report (_$Session$_.ExternalReportConnectError). Occurs when an error occurs when connecting to an external report session.
  • Session. Attaching add-in (_$Session$_.AddInAttach). Occurs when connecting to an add-in session.
  • Session. Error attaching add-in (_$Session$_.AddInAttachError). Occurs when an error occurs when connecting to an add-in session. +There is now more information for event log events:
  • _$InfoBase$_.ConfigUpdate.
  • _$InfoBase$_.DBConfigUpdate.
  • _$InfoBase$_.DBConfigUpdateError.
  • _$InfoBase$_.DBConfigExtensionUpdate.
  • _$InfoBase$_.DBConfigExtensionUpdateError.
These features were not provided.Extended list of logged actions to facilitate system administration.
Event log.
Now you can manage writing of audit events of access rights to the event log. By default, writing of audit events is disabled. Audit events of access rights include:
  • _$InfoBase$_.RoleUpdate
  • _$User$_.PermissionChange
  • _$InfoBase$_.AdministrationParametersChange
  • _$InfoBase$_.SecurityProfileChange.

New parameter for the conf.cfg file: EnableAccessRightAuditEventsWrite.

New checkbox for dialog boxes for editing cluster parameters in the cluster management console and the standard Server management data processor: Allow writing audit events of access rights.

For the rac cluster list and rac cluster info commands, the allow-access-right-audit-events-recording parameter is now displayed. New parameter for the rac cluster insert and rac cluster update commands: --allow-access-right-audit-events-recording.

New property: AdministrationCluster.EnableAccessRightAuditEventsWrite. New property: IClusterInfo.AllowAccessRightAuditEventsRecording. New method: IServerAgentConnection.SetAllowAccessRightAuditEventsRecording().

New methods in the Java administration server interface for the IClusterInfo object: isAllowAccessRightAuditEventsRecording() and setAllowAccessRightAuditEventsRecording().

New parameter for the command line of the standalone server startup (ibsrv): --access-right-audit-events-recording. New parameter for the configuration file of the standalone server for the server section: access-right-audit-events-recording.

The "Allow writing audit events of access rights" feature requires a CORP license.

These features were not provided.Now you can enable audit events of access rights when necessary.
Settings storage.
New default settings. The default setting is valid for all users who do not have the custom setting. The custom setting is prioritized. To save and delete the default settings, the Data administration right is required. Any infobase user can select and use the default setting.

New methods for the StandardSettingsStorageManager object: LoadDefaultSetting(), SaveDefaultSetting(), DeleteDefaultSetting(), and SelectDefaultSettings().

The standard 1C:Enterprise interface does not allow performing any actions with the default settings. To perform such actions, develop an appropriate dialog box.

It is recommended that application developers use the default settings, instead of copying settings to new users in bulk.

This feature was not provided.

Previously, to set previously made settings to a new user, you needed to copy these settings from the settings of another user.

Simplified the administrator work on the initial customization of the application to the needs of users (including those who are not yet created in the infobase). You no longer need to copy settings to all (or only new) infobase users if it is necessary to change any default settings for all users.
Administration tools.
Now you can check user passwords for compromise. You can check passwords using the standard 1C:Enterprise platform list, your own list of invalid passwords, as well as specify the address of an Internet password check service. Now you can specify that it is necessary to check passwords in additional authentication settings, infobase settings, and user password policy.

New features for the AdditionalAuthenticationSettings objects:

The PasswordCompromiseCheck property. +The SetPasswordCompromiseCheckSettings() and GetPasswordCompromiseCheckSettings() methods. +New global context methods: SetUserPasswordCompromiseCheck(), GetUserPasswordCompromiseCheck(),

SetActionOnUserPasswordRequirementsViolationOnAuthentication(), GetActionOnUserPasswordRequirementsViolationOnAuthentication(), and CheckPasswordCompromise().

New properties for the UserPasswordPolicy object: PasswordCompromiseCheck and ActionOnPasswordRequirementsViolationOnAuthentication.

New system enumeration property: PasswordPolicyComplianceCheckResult.DoesNotSatisfyCompromiseCheckRequirements.

New object property: InfobaseUser.PasswordDoesNotSatisfyRequirements.

Implemented the following event log events:

  • Session. Password violates authentication requirements (_$Session$_.PasswordRequirementsViolationOnAuthentication). Generated during authentication if the user password violates the requirements.
  • Session. Error of service for password compromise check upon authentication (_$Session$_.PasswordCompromiseCheckServiceErrorOnAuthentication). Generated during authentication if an error using the service for password compromise check occurs.
  • Infobase. Error of service for password compromise check (_$InfoBase$_.PasswordCompromiseCheckServiceError). Generated when an error occurs when accessing the service for password compromise check.
  • Infobase. Changing list of password compromise check (_$InfoBase$_.PasswordCompromiseCheckListUpdate). Generated when the password compromise check list is changed.
  • Infobase. Error changing list of password compromise check (_$InfoBase$_.PasswordCompromiseCheckListUpdateError). Generated when an error occurs when changing the password compromise check list. +There is now more information for event log events:
  • _$User$_.New
  • _$User$_.NewError
  • _$User$_.Update
  • _$User$_.UpdateError
  • _$InfoBase$_.ParametersUpdate
  • _$InfoBase$_.ParametersUpdateError
  • _$InfoBase$_.UserPasswordPolicyNew
  • _$InfoBase$_.UserPasswordPolicyUpdate
  • _$Session$_.PasswordChangeError
  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdate
  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdateError.
This feature was not provided.Now you can lock specifying "well-known" passwords and passwords that cannot be assigned due to corporate restrictions.
Configuration extensions.
Now you can edit the Package and Namespace properties of an adopted XDTO package, as well as the XDTOPackages property of an adopted web service in the configuration extension.

For the XDTO package, the specified properties are replaced with the same properties from the extension. For web services, the list of packages in the resulting configuration is supplemented with the value from the extension.

This feature was not provided.Advanced configuration extension features.
Database copies.
When restoring an infobase from a DT file, data synchronization with database copies that are configured in the original infobase is locked (except for the Data accelerator copy). The administrator can allow using copies using the standard Database copy management data processor in the restored infobase. The standard data processor also displays the owner of each copy configured in the infobase (except for the Data accelerator copy).

New methods for the database copy manager: SetCopyDatabaseUseByThisCopy().

New method for the database copy manager: GetInformationOnCopyDatabaseUse().

The Update() method of the database copy manager generates an exception if the database to update is used by another infobase.

It is recommended to analyze the tools for updating database copies in applications and implement (if necessary) informing the administrator about issues that arise when updating database copies.

This feature was not provided.

Previously, after restoring the infobase from the DT file and starting the application, all configured copies began to update (if the DBMS on which the copies were located were available to the restored infobase). This could lead to violation of information integrity in the copies (compared with the original infobase).

When you create an infobase copy (for example, for testing), data from the infobase copy will not go to the database copies that the original infobase uses. So, data in the copies will be protected from updating with incorrect information.
DBMS operations.
Now you can create arbitrary indexes for the following configuration objects: catalogs, documents, document journals, information registers, accumulation registers, accounting registers, calculation registers, business processes, tasks, charts of characteristic types, charts of accounts, exchange plans, and sequences. When creating an index, configuration fields and attributes are specified, not the physical database fields. The platform performs the required conversion automatically while saving the configuration. You cannot create an index that will contain more than 16 physical database fields.

The built-in system indexes are not editable and are not shown in Designer tools. Indexes are added and deleted upon infobase restructuring.

New property for configuration objects that support creation of additional indexes: AdditionalIndexes.

The GetDBStorageStructureInfo() method returns information about additional indexes if they are specified in the configuration in the Indexes column. New column in the value table that describes table index fields (Indexes.Fields): FieldType.This column describes the index field type.

You cannot create or change additional indexes in the configuration extension.

Be careful when creating additional indexes. Remember that additional indexes can lead not only to positive consequences (faster data acquisition), but also to negative ones: slowing down writing to the infobase, increasing the disk space occupied by database files, and slowing down scheduled database operations.

This features requires a CORP license.

This feature was not provided.

Previously, you could create additional indexes only for the DBMS.

If necessary, you can create additional database indexes that can speed up the execution of specialized application queries.
Client application.
Now users can authenticate using a QR code.

New checkbox in the user parameters: QR code authentication. New property: InfobaseUser.QRCodeAuthentication.

New item for the default.vrd file: <mobileApps>.

There is now more information for event log events:

  • _$User$_.New.
  • _$User$_.Update.
  • _$Session$_.Authentication.
  • _$Session$_.AuthenticationError.
  • _$Session$_.AuthenticationFirstFactor.
This feature was not provided.If you are authenticated in any infobase using a mobile application, you may not enter a password to get access to the same database from another device. Just scan the QR code displayed by the authentication form from a mobile device.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Collaboration system.
Now you can select the window (application) to display to subscribers during screen sharing in a thin client or during a collaboration system video call.

You can set up display mode of collaboration system notifications during screen sharing: Show entire message, Show only sender, and Hide messages.

Previously, you could only select a monitor (if there were several monitors) to display to subscribers during screen sharing in a thin client or during a collaboration system video call. You could not select a window (application) to display.

During screen sharing, video call subscribers could see all collaboration system notifications.

The load on the communication channel during screen sharing can be reduced as you can select to display not the entire monitor, but only the selected application window, which often does not occupy the entire selected monitor/desktop.

During a video call, you can manage display of collaboration system notifications. This will positively affect the video call privacy.

Collaboration system.
The video and image quality of the displayed screen in case of network issues is enhanced. If the channel bandwidth deteriorates, the image quality must be proportionally reduced. Screen sharing must not be interrupted.Previously, if the communication channel quality deteriorated, the video stream could be interrupted (both regular video and screen sharing) or freeze.Enhanced video quality (including screen sharing) in case of communication channel issues.
Collaboration system.
The following features are implemented when using collaboration system video calls in the thin client:
  • You can enable automatic adjustment of the microphone gain level. New checkbox in the collaboration system settings: Automatic microphone volume control. The setting is disabled by default. The setting is stored on the client computer by microphones.
  • You can select noise suppression mode: Quiet background noise (default), Loud speech, noises, and Noise suppression is off. The setting is stored on the client computer by microphones.
Previously, you could not control the microphone gain level and noise suppression mode when using video calls in the collaboration system.You can enable the mode when the collaboration system will automatically amplify the quiet and dampen the too loud voice of the subscriber. You can also manage noise suppression and echo cancellation systems.
Standard functions.
The setup form is redesigned for the standard Data change history data processor:
  • New feature: search fields by configuration objects, tables, and fields.
  • The system now displays that a specific setting is performed in 1C:Enterprise mode or in Designer.
  • You can set standard settings for the configuration object(s) from metadata.
  • You can clear the data history.
  • You can display the difference between the current history settings and the settings made in the metadata.
These features were not provided.Advanced settings of data change history.
Administration tools.
Client application.
New feature: improved client application update. If the required version is not available on the client computer, the required client application starts downloading immediately. In the form that displays the download process, you can cancel downloading or sign in to the infobase using a web client if the database is accessed over HTTP(s).If the required version of the client application was missing on the client computer when trying to sign in to the infobase, the system first prompted to choose what to do next: update the client application or sign in to the infobase using the web client. If you selected to update the client application, the client application downloading and installing started.Faster client application update.
Collaboration system.
When you make video calls in thin and web clients, the load on the CPU and network channel of the client computer is reduced. The load on the CPU and network no longer depends on the number of participants in the call.

For that, the administrator must do the following:

  • Update the collaboration system servers to version 26 or later.
  • Update 1C:Enterprise to version 8.3.26 or later.
  • Update the Janus video server to version 1.0.4 or later.
Previously, when you made video calls in thin and web clients, there was an increased load on the CPU and network channel of the client computer. The larger the number of participants in the video call, the higher was the load on the CPU and network.Reduced system load when making group calls. Now you can increase the number of users who can simultaneously participate in a video call.
Collaboration system.
The video call interface on the external user website and the website chat is now similar to the same interface in client 1C:Enterprise applications.The video call interface on the external user website and the website chat was different from the same interface in client 1C:Enterprise applications.Extended website capabilities for external users.
Collaboration system.
The following changes are made to the interface for enabling screen sharing of the collaboration system video call in the thin client:
  • The order of monitors is changed to the system one (corresponds to the horizontal placement of monitors).
  • When selecting a screen or application to share, the OK and Cancel buttons are removed. The demonstration starts immediately after you select the required object.
  • The screen or window choice form is reduced in vertical dimensions to fit on low-resolution screens.
Previously, the interface for enabling screen sharing of the collaboration system video call in the thin client had the following behavior:
  • The monitors were in alphabetical order.
  • To select a screen or window to share, it was necessary to select the object to share and click OK.
  • The screen or window choice form did not fit vertically on low-resolution screens.
Improved interface for selecting a monitor or window to share in the thin client.
Technological log.
Now you can track RAM consumption by full-text search. New item for the logcfg.xml file: <systemmemoryprofile>. Information on RAM consumption is displayed in the <system> events.

Tracking settings and descriptions of generated events are not documented. This feature is designed for 1C Company specialists.

Previously, you could not track RAM consumption by full-text search.If there are issues with RAM consumption by full-text search, 1C specialists can provide the ready-made logcfg.xml file, and receive technological log files to analyze the situation and solve the arisen issues.
Web client.
Client application.
Users with operating systems earlier than Windows 7 get notified that operating systems are not supported in version 8.3.27 and the operating system update is recommended.

The warning is shown once a month for a unique user combination, an infobase, and a client/web browser kind (if the web client is used).

The warning about supporting obsolete versions of the Windows operating system was not shown.A user gets notified that the operating system in use cannot open the following version of the 1C:Enterprise.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Server clusters.
New feature: optimized use of processor, RAM, and session data by a 1C:Enterprise server cluster.Previously, the resources of the computer running the 1C:Enterprise server cluster were not used effectively enough.Improved performance and scalability of the 1C:Enterprise server cluster.
Development tools.
New feature: optimized check for circular references when the corresponding mode is enabled.Previously, the check for circular references with the corresponding mode enabled took more time.Reduced overheads introduced by the circular reference check. This will reduce the time required to analyze a problematic operation.
Development tools.
New feature: optimized the first Designer startup after loading the configuration.After loading the configuration, the first Designer startup took a long time.Faster first Designer startup after loading the configuration.
Development tools.
New feature: reduced time for restarting the client application from Designer.Restarting the client application from Designer took a long time.Reduced time for restarting the client application from Designer.
Collaboration system.
New features for the collaboration system:
  • Search through the list of conversations is optimized.
  • When changing the list of conversation participants (the CollaborationSystemConversation.Participants property), only changes are written.
  • The request from the 1C:Enterprise server to the collaboration system server is executed every 45 seconds. If the action was not performed during this time, an exception is thrown.
Previously, for the collaboration system:
  • Search through the list of conversations took more time.
  • When the list of conversation participants was changed (the CollaborationSystemConversation.Participants property), the entire list was written.
  • The request from the 1C:Enterprise server to the collaboration system server was executed without timeout. This could cause the 1C:Enterprise server freezes.
Improved performance of the collaboration system server.
Full-text search.
When using full-text search on large infobases, RAM consumption is now reduced.

For that, re-index the full-text search index.

1C:Enterprise platform version 8.3.25 and earlier will clear the index if it was built by version 8.3.26.

Previously, full-text search on large infobases required a large amount of RAM.Full-text search requires fewer resources for operation.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Settings storage.
Now you can get access to standard settings storages even if custom settings storages are set.

New global context methods:

GetStandardReportsVariantsStorage(), GetStandardURLExternalDataStorage(), GetStandardFormDataSettingsStorage(), GetStandardCommonSettingsStorage(), GetStandardDynamicListsUserSettingsStorage(), and GetStandardReportsUserSettingsStorage(). The methods return values of the StandardSettingsStorageManager type.

Previously, if custom settings storages were set in the application, it was impossible to access the corresponding standard storage.You can transfer settings from the standard storage to the custom one when updating the configuration if the new application version contains a custom settings storage that replaces the standard storage.
Server clusters.
Administration tools.
Now you can specify alternative data directories for some server cluster services. When you specify an alternative directory, data transfer is not performed automatically. You need to transfer data manually. The structure of data directories does not change during transfer.

You can set up directory transfer in the cluster console and in the standard Server management data processor.

New methods for the AdministrationWorkServer object: CreateServiceSetting(), GetServiceSetting(), GetServiceSettings(), and GetServiceDataDirectoriesForTransfer().

The AdministrationWorkServer.SpeechToTextModelDirectory property is deprecated.

New methods for the IServerAgentConnection COM connector object: CreateServiceSetting(), GetServiceSettings(), RegServiceSetting(), DeleteServiceSetting(), GetServiceDataDirsForTransfer(), GetServiceSettingByID(), GetServiceSettingByParams(), GetSettingActive(), and ApplyServiceSettings().

The IWorkingServerInfo.SpeechToTextModelDirectory property is deleted.

New methods for the IAgentAdminConnection Java interface object: createServiceSetting(), getServiceSettings(), regServiceSetting(), deleteServiceSetting(), getServiceDataDirsForTransfer(), getServiceSettingByID(), getServiceSettingByParams(), getSettingActive(), and applyServiceSettings().

The IAgentAdminConnection.SpeechToTextModelDirectory property is deleted.

New mode for the rac utility: service-setting. The --speech-to-text-model-directory parameter is deleted for the insert and update commands of the server mode.

Specifying alternative data directories for some server cluster services requires a CORP license.

This feature was not provided.

Previously, you could transfer directories only using the operating system used. This was not obvious to the user.

You can place cluster data on different disk drives to improve overall system performance.
Binary data storage.
You can specify configuration objects whose data can be placed in the binary data storage. You can specify objects both in Designer and during execution (from 1C:Enterprise language or using a standard function).

New methods for the binary data storage manager: SetStoredDataContent(), GetStoredDataContent(), SetUsingAsStorageByDefault(), and GetUsingAsStorageByDefault().

New properties for the manager of the external binary data storage: StoredDataContent and StorageByDefault.

New properties for attributes and resources of the ValueStorage type configuration objects: BinaryDataStorageLocationUse and BinaryDataStorageLocationUseField.

The standard Binary data storage management data processor is improved.

This feature was not provided.

There was only a limit on the minimum amount of binary data that got into the external storage. It was impossible to limit the configuration objects whose data could enter the binary data storage.

You can manage writing data to the binary data storage not only by configuration object attributes, but also by specific data that is written to the infobase.
ZIP archive operations.
You can unpack archives of the following formats: GZIP, RAR, 7-ZIP, XZ, and TAR. You cannot pack into these formats.

New objects: ArchiveFileReader and ArchiveFileWriter.

New property: ErrorCategory.UnsupportedFormat.

The ZipFileReader, ZipFileWriter, and related objects are deprecated.

+

This feature was not provided.You can get data in archives that are packed not only in ZIP file format.
Server clusters.
You can change the parameters of the disconnection tracking system without restarting the cluster processes. This feature is implemented for all administrative tools: cluster console, COM connection, Java administration interface, and administration server.

New properties for the AdministrationCluster object: PingPeriod and PingTimeout. New properties for the IClusterInfo object:

PingPeriod and PingTimeout.

You can edit the Ping timeout and the Ping period parameters in the form for editing cluster parameters in the cluster console and the standard Server management function.

New parameters for the rac cluster update command: --ping-period and --ping-timeout. Information on the current values of the --ping-period and --ping-timeout parameters is added to the result of the rac cluster info command.

New methods in the Java administration server interface for the IClusterInfo object: getPingPeriod(), setPingPeriod(), getPingTimeout(), and setPingTimeout().

You could change the parameters of the disconnection tracking system only by restarting the cluster processes, as these parameters were specified in the command line to start the server agent (ragent).Server cluster administrators can set up a connection check system without restarting cluster processes. With this feature, they can set up the cluster in the current network conditions or perform long-running internal operations (for example, data migration).
Information registers.
Accumulation registers.
Now you can update and delete records (in addition to adding and replacing them) of subordinate information and accumulation registers. ReplacementMode.Join write mode is not supported. The behavior is similar to the behavior of independent information registers. +The function is managed by the ExtendedReplaceMode property of the register record set. The property has an effect only when operating with subordinate information and accumulation registers. If the property has the True value, you can delete and replace records, change the LineNumber property of a set record, and specify supported values of the ReplacementMode system enumeration as the Replace parameter value of the Write() method for the subordinate information and accumulation registers.Previously, you could only add and fully replace the records existing in the infobase for a record set of subordinate information and accumulation registers.In some scenarios, you can significantly speed up operations with subordinate information registers and accumulation registers.
Database copies.
Errors that occur when executing a query to a database copy DBMS are divided into recoverable and non-recoverable errors. Recoverable errors do not disable a database copy and allow further execution of queries from the application to such copy. Unrecoverable errors result in disabling a database copy and do not allow further query execution from the application.

The list of recoverable and non-recoverable errors differs in version 8.3.24 compatibility mode and with compatibility mode disabled.

Previously, any error that occurred when executing a query to a database copy DBMS led to disconnecting such copy from the infobase and did not allow further query execution in such copy. If you try to run a query on a database copy that does not take into account possible data features, an exception will be thrown. The database copy will not be disabled, and other queries will be able to run queries in this copy.
PDF document operations.
Now you can define page parameters in a PDF document.

New property: PDFDocument.Pages.

New optional parameter for the AddRepresentationObject(), AddRepresentationObjectAsync(), AddSignature(), and AddSignatureAsync() methods of the PDFDocument object: ConsiderPageOrientation.

This feature was not provided.Advanced PDF document features.
Client application.
Event log.
Administration tools.
Web client.
New feature: updated client application authentication form. Now you can display all available authentication types on the authentication form and quickly select the required authentication type. The system can store the last user authentication parameters for thin, thick, and web clients. The last 4 names of successfully authenticated users are now displayed in the user selection list. The authentication splash is displayed before the authentication dialog box appears and after successfully signing in to the infobase.

The payload used by the client application upon JWT authentication is changed.

To disable any authentication method, either prohibit this authentication method or change the password of the compromised user(s). If the password is changed, all stored access tokens become invalid.

New command of the client application startup: /ResetSavedAuth. It resets the parameters of the last successful authentication.

New additional user authentication parameters: Allow saving authentication, Save authentication by default, and Saved authentication lifetime.

New methods for the manager of additional authentication settings: GetAuthenticationAutoSaveSettings() and SetAuthenticationAutoSaveSettings().

New element for the <point> element of the default.vrd file: <authentication>. You can use it to set up the default authentication type and the available authentication types for this infobase.

There is now more information for event log events:

  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdate.
  • _$Session$_.Authentication.
  • _$Session$_.AuthenticationError.
  • _$Session$_.AuthenticationFirstFactor.
These features were not provided.

The system could remember the last authenticated user only when using the OpenID Connect authentication.

Improved the interface of the user authentication dialog box. You can set the required authentication type as the default one. The system stores data for re-entry for all authentication types.
Collaboration system.
In group conversations, you can now search in the participant list.

For group conversations with a large number of participants (more than 100 participants), you can load the participant list asynchronously. No more than 3,000 participants can participate in a group conversation.

You can create conversations with Read only mode. Such conversations do not allow you to add or change these conversations. You can change them using 1C:Enterprise language. New property: CollaborationSystemConversation.ReadOnly.

Previously, you could not search for participants in group conversations.

The list of group conversation participants was always loaded immediately.

You could have an unlimited number of participants in conversations.

You could not create conversations unavailable for editing.

Improved collaboration system operations with group conversations with a large number of participants.
Dynamic lists.
Now you can manage what to display on the search string form of the dynamic list. Now you can enable and disable the search string, as well as disable the search string if it is impossible to effectively use full-text search. This feature is only available from 1C:Enterprise language via the system settings storage. +New object: DynamicListViewSettings.

New settings for the system settings storage: DynamicListViewSettings and DynamicListsViewSettings.

This feature was not provided.

In some cases, full-text search used by the search string could be ineffective or incorrect.

You can specify that it is required to use the search string for both a specific dynamic list and all dynamic lists of the application.
Binary data storage.
Now you can use block binary data storage in the 1C:Enterprise infobase (only in client/server mode). In version 8.3.25 and earlier compatibility mode, you can enable and disable the feature using the Block binary data storage mode configuration property. In other cases, the feature is always enabled and cannot be disabled.

For the built-in binary data storage, you can now manage where binary data which must be written to the binary data storage will be stored: only in the binary data storage or both in the infobase and storage. If data is stored both in the infobase and storage, the infobase will stay operational if the built-in binary data storage is destroyed or lost.

New methods for the binary data storage manager: GetBinaryDataStorageBinaryDataCopiesPlacementMode() and SetBinaryDataStorageBinaryDataCopiesPlacementMode().

This feature was not provided.

When the binary data storage was connected, you could store data only in this storage.

You can convert an infobase that stores binary data larger than 1 GB between Microsoft SQL Server and PostgreSQL.

Improved reliability of storing binary data when using external binary data storages. If binary data is stored both in the infobase and binary data storage, to back up data, it is enough to back up the infobase.

Infobase verification and repair.
Binary data storage.
If, when checking the binary data storage integrity (during infobase verification and repair), infobase objects with a binary data error were found (the binary data storage is unavailable, binary data is deleted from the storage or does not exist in the storage), the system outputs information that will identify the problematic object.Previously, when checking the binary data storage integrity (during infobase verification and repair), if binary data errors occurred, the system did not identify the problematic objects.Simplified identification of objects that have issues with binary data transferred to the binary data storage.
Collaboration system.
Now 1C:Enterprise supports attachments for integration of the webhook type.

New optional parameters for the createMessage collaboration interface request: data and datаType. New property for the CollaborationSystemMessage object: StringDataFormat.

This feature was not provided.The integration of the webhook type can transfer data to 1C:Enterprise.
Collaboration system.
Now you can invite external users to conversations and video calls. The invitation is sent via a special URL. Both external and internal users can follow the URL. The invitation may allow users to fully participate in the conversation or participate only in video calls. It is specified when generating the invitation.

You can get a URL when creating a new conversation, in the dialog box for adding conversation/video call participants, or in the menu of the out-of-context conversation form.

The user interface of the collaboration system is improved to provide new features.

Now you can revoke all issued invitations to participate in the conversation.

New method for the collaboration system manager: GetInviteUrlToConversation().

Previously, you could not connect an external or internal user to a video call via a URL. You needed to invite an external user to the website for external users and only then start a video call.Users will be able to connect to video calls manually. The existing participants do not need to call a new participant.
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.19.The format version of configuration dump to XML files was 2.18.Configuration dump to XML files supports new platform features.
Queries.
If the type collection acts as an operand of the SUM() and AVG() query language functions, the result of the functions will be a number without dimension limitation.

An accounting register resource with a type collection will have a length of 38 digits and a precision described by the type collection.

If the type collection acted as an operand of the SUM() and AVG() query language functions, the result of the functions was a number with parameters (length and precision) specified in the type collection.

Previously, an accounting register resource with a type collection had parameters (length and precision) described by the type collection.

Eliminated unexpected system behavior.
Integration service.
Standalone server.
Now the documentation shows that the standalone server does not support integration services. The change is made to the documentation starting from version 8.3.21.Previously, the documentation did not show that the standalone server does not support integration services.Fixed error in the documentation.
Database copies.
Now when you set the query text (the Query.Text property) or call the Query object methods, it does not change the values of the DatabaseCopiesUse and UsedDatabaseCopies properties of the Query object.

This change is not implemented in 8.3.25 compatibility mode.

Previously, when you set the query text (the Query.Text property) or called the Query object methods, it set the Query.DatabaseCopiesUse property to DatabaseCopiesUse.Auto and cleared the Query.UsedDatabaseCopies property.Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Administration tools.
Now you can select the following hash algorithm of 1C:Enterprise infobase user passwords: SHA-1, SHA-256, SHA-512, and PBKDF2-HMAC-SHA256. The hash algorithm is configured in the infobase parameters. If the hash algorithm differs from SHA-1, you can run the infobase only using 1C:Enterprise version 8.3.26 and later.

The PBKDF2-HMAC-SHA256 hash algorithm support is added for the DataHashing object.

New global context methods: GetUserPasswordHashAlgorithmType(), SetUserPasswordHashAlgorithmType(), EvaluateStoredUserPasswordValue(), and CheckUserPasswordComplianceWithStoredValue().

New system enumeration property: HashFunction.PBKDF2SHA256.

New property: InfobaseUser.PasswordHashAlgorithmType.

Data of the _$InfoBase$_.ParametersUpdate, _$InfoBase$_.ParametersUpdateError, _$User$_.New, _$User$_.NewError, _$User$_.Update, and _$User$_.UpdateError event log events now contains information about the used hash algorithm.

Previously, the SHA-1 algorithm was always used to hash passwords of 1C:Enterprise infobase users.You can use more robust hash algorithms for infobase user passwords.
Client application.
Administration tools.
Now 1C:Enterprise supports USIA protocol version 3.34.

New parameter for the clientconfig section of the OpenID Connect provider details in the default.vrd file: client_certificate_hash. It is required for the new protocol version.

You can still use the previous version of the USIA protocol.

This feature was not provided.Now 1C:Enterprise supports the latest USIA protocol version.
Administration tools.
Now you can specify the inactivity period time after which the user session will be forcibly terminated. This feature is implemented in thin, thick, mobile, and web clients. This feature is not provided in Designer. Before the session termination, the user will receive a warning. If they respond to this warning, they can cancel the forced session termination.

New parameters in the dialog box to set up infobase parameters: Time for inactive session termination notification and Inactive session termination timeout.

New global context methods: SetInactivityTimeForTerminateSessionNotification(), GetInactivityTimeForTerminateSessionNotification(), SetInactivityTimeForTerminateSession(), and GetInactivityTimeForTerminateSession().

There is now more information for event log events:

  • _$InfoBase$_.ParametersUpdate.
  • _$InfoBase$_.ParametersUpdateError.

To forcibly terminate sessions due to inactivity, a CORP license is required.

This feature was not provided.Reduced risk of unauthorized access to infobase data.

Reduced license consumption by disabling users who do nothing in the infobase for a long period of time.

Integration service.
Upgrade: the MaximumCount parameter of the SelectMessages() method of the integration service channel manager is used in accordance with the name: messages of the integration service channel are returned in the quantity that does not exceed the value specified in the parameter.

This change is not implemented in 8.3.25 compatibility mode.

When calling the SelectMessages() method of the integration service channel manager, the value of the MaximumCount parameter was ignored. The method always returned all messages of the integration service channel.Eliminated unexpected system behavior.
Integration service.
If in the filter structure of the SelectMessages() method of the integration service channel manager, the CorrelationId filter parameter is set to the value of a zero UUID (NIL UUID, a value of zeros only), messages whose request message ID is equal to the zero UUID are returned.

This change is not implemented in 8.3.25 compatibility mode.

If in the filter structure of the SelectMessages() method of the integration service channel manager, the CorrelationId filter parameter was set to the value of a zero UUID (NIL UUID, a value of zeros only), such filter value was ignored and all channel messages were returned.Eliminated unexpected system behavior.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
Mobile application builder.
Mobile device-specific features.
1C:Enterprise mobile version now supports RuStore mobile services:
  • In-app purchases.
  • Push notifications.
  • Cartography and operations with coordinates.
  • Evaluation of applications in the store.

If a built mobile application supports all mobile services, RuStore services have a higher priority than other mobile services. Now you can enable/disable RuStore service management modules (similar to Google and Huawei mobile services), as well as specify the parameters required to successfully build applications for RuStore in the mobile application builder.

New system enumeration values: DeliverableNotificationSubscriberType.RMS and InAppPurchaseService.RuStoreInAppPurchase.RuStoreInAppPurchase.

The GetAccessToken() method of the manager for sending deliverable notifications considers using RuStore services.

1C:Enterprise mobile version did not support RuStore mobile services. You were unable to develop mobile applications that could not be distributed through the Google Play and Huawei AppGallery stores.More mobile services are now supported.

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Database copies.
Configuration extensions.
If an extension that adds data (or contains its own data objects) is attached to the infobase, the tables of those objects cannot be transferred to a copy of the infobase. If the copy already has those tables, they will be removed during the update.If such extensions were attached, 1C:Enterprise would not work properly. Eliminated unexpected system behavior.
Full-text search.
Faster merging of full-text search indexes. Increased computer CPU usage during the merge. Complete merging is now only possible when you call the UpdateIndex() method of the full-text search manager with the EnableJoining parameter set to True. Previously, merging full-text search indexes took longer. Complete merging could occur when a new batch of data was added to the search index.Faster merging of full-text search indexes. Unpredictable complete merging of indexes when adding new data has been eliminated.
DBMS operations.
Infobase verification and repair.
New infobase parameter: Use additional indexes. New methods: SetAdditionalIndexesUsage() and GetAdditionalIndexesUsage(). When the parameter is enabled, the CORP license availability is checked.

New infobase verification and repair mode: Check and enable CORP functionality.

New parameter of the /IBCheckAndRepair command: -CheckAndEnableCORPFunctionality.

This feature was not provided.Now you can manage creation of additional indexes in the infobase.
DBMS operations.
System requirements.
IBM Db2 of all versions up to 10.1 (inclusive) is no longer supported.

Only IBM Db2 version 11.1 is supported.

Previously, IBM Db2 versions 9.1, 9.5, 9.7, and 10.1 were supported.Obsolete IBM Db2 versions are no longer supported.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro Enterprise: 12.20.2, 13.16.2, 14.13.2, 15.8.2;
  • Postgres Pro CERT Enterprise: 13.16.2, 14.13.2, 15.8.2;

DBMS version bitness: x86-64, E2k, ARM64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

These Postgres Pro DBMS versions were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1C: 17.0;
  • Postgres Pro Standard: 17.0.1;
  • Postgres Pro Enterprise: 16.4.2;
  • Postgres Pro CERT Enterprise: 16.4.2.

DBMS version bitness: x86-64, E2k, ARM64. +The products are supported in 1C:Enterprise version 8.3.22 or later. +Supported operating systems are defined by a DBMS vendor.

These Postgres Pro DBMS versions were not supported.Extended list of supported DBMS.
System requirements.
Linux.
The following Linux distribution packages are no longer supported:
  • CentOS 7
  • Oracle Linux 7
  • Red Hat Enterprise Linux 7
  • Astra Linux Common Edition 2.12
Previously, 1C:Enterprise supported the following Linux distribution packages:
  • CentOS 7
  • Oracle Linux 7
  • Red Hat Enterprise Linux 7
  • Astra Linux Common Edition 2.12
Outdated Linux distribution packages are no longer supported.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1С: 12.22, 13.18, 14.15, 15.10
  • Postgres Pro Standard: 12.22.1, 13.18.1, 14.15.1, 15.10.1
  • Postgres Pro Enterprise: 12.22.1, 13.18.1, 14.15.1, 15.10.1
  • Postgres Pro CERT Standard: 14.15.1, 15.10.1
  • Postgres Pro CERT Enterprise: 13.18.1, 14.15.1, 15.10.1.

DBMS version bitness: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These Postgres Pro DBMS versions were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1С: 16.6, 17.2
  • Postgres Pro Enterprise: 16.6.1
  • Postgres Pro CERT Standard: 16.6.1, 17.2.1
  • Postgres Pro CERT Enterprise: 16.6.1.

DBMS version bitness: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.22 or later.

Supported operating systems are defined by a DBMS vendor.

These Postgres Pro DBMS versions were not supported.Extended list of supported DBMS.
Internet-enabled functionality.
Administration tools.
OpenID authentication is considered a priority authentication method if this method is configured for the infobase. The general authentication form is displayed only if the user has explicitly performed the logout operation in the OpenID authentication provider, or the provided username and password cause a provider authentication error. In all other cases, the system tries to use the customized authentication before displaying any input forms to the user.

If OpenID Connect authentication is configured for the infobase, when the web client is launched, an attempt is made to authenticate with the provider using the parameters of the last successful authentication. The general authentication form will be displayed if the web client has failed to authenticate with OpenID Connect.

If OpenID authentication was configured for the infobase, a login confirmation dialog (containing a list of available authentication types) was displayed each time a user tried to sign in.Application authentication has become more straightforward and expected.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro Enterprise: 17.2.1.

DBMS version bitness: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.22 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported.Extended list of supported DBMS.
Mobile application builder.
Mobile 1C:Enterprise version 8.3.26 is now supported in the mobile application builder.Mobile 1C:Enterprise version 8.3.26 was not supported in the mobile application builder.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
DBMS operations.
System requirements.
The system now supports Tantor SE 1C DBMS versions 14.15.0, 15.10.0 and 16.6.0.

Supported processors: ARM64 and x86-64.

Supported operating systems are defined by a DBMS vendor.

This Tantor SE DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
Client application.
Administration tools.
The protocol of OpenID provider implemented in the 1C:Enterprise platform is changed to ensure backward compatibility. We recommend that you update the client applications.

For the thin client version 8.3.26, the default authentication flag is saved when using an OpenID provider that runs on the 1C:Enterprise platform version 8.3.25 and earlier.

An OpenID provider that runs on the 1C:Enterprise platform version 8.3.26 can service client applications version 8.3.25 and earlier.

For the thin client version 8.3.26, the default authentication flag was not displayed or remembered when using an OpenID provider that runs on 1C:Enterprise platform version 8.3.25 and earlier.

Client applications of version 8.3.25 and earlier received unexpected responses from an OpenID provider running on the 1C:Enterprise platform version 8.3.26. As a result, their correct operation was impossible.

Restored backward compatibility of the OpenID provider version 8.3.26 and client applications of earlier versions. Client applications of version 8.3.26 can operate with the OpenID provider version 8.3.25 and earlier.
Binary data.
If you try to simultaneously delete and read a database record containing binary data, no binary data reading errors occur.Previously, if you tried to simultaneously delete and read a database record containing binary data, binary data reading errors could occur.Eliminated the issue that might occur when simultaneously trying to delete and read a record containing binary data.

Table of contents

Transition from the previous version to the version 8.3.26

Table of contents

Version 8.3.25

Version 8.3.25 includes known bug fixes and functionality modifications. +

The binary data storage graduated out of beta.

The binary data storage requires CORP license.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
New value for the Compatibility mode configuration property: Version 8.3.24.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.23 was available. +Configurations developed using 1C:Enterprise platform version 8.3.24 or earlier can now run on version 8.3.25 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.25 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.24 after the migration to version 8.3.25 even if you have disabled the compatibility mode (simply enable it again).
Speech synthesis.
Now you can use speech synthesis.

Implemented the following methods for the speech manager: StartTextToSpeech(), StopTextToSpeech(), Synthesize(), and GetTextToSpeechAvailableVoices().

New objects: TextToSpeechVoiceDescription, TextToSpeechVoiceParameterDescription, TextToSpeechVoiceParameterValueDescription.

Speech synthesis is not supported on Windows XP and Windows Server 2003.

Previously, 1C:Enterprise platform did not contain built-in speech synthesis tools.Now you can use speech synthesis. Now you can use the platform tools to implement voice interfaces with users.
Common objects.
New global context method: CallSleep(). The method is available only on the server. The method is unavailable in server calls initiated from the client application.This feature was not provided.Now you can terminate the execution of code in 1C:Enterprise language in server code (background and scheduled jobs, Internet services, and other).
Binary data storage.
Administration tools.
New tool for Designer: Main menu - Administration - Binary data storage management. It is similar to the standard Binary data storage management function.Managing the binary data storage was not available in Designer.In Designer, you can now perform the same set of operations as when using the standard function. You could only call the function if the client application with this infobase was successfully started.
Binary data storage.
New feature for the binary data storage: deduplication of binary data chunks in the Microsoft Compound Binary File format (CBF, files of Microsoft Office 2003 and earlier). This process is not controlled by the user. Files that have not been accessed for more than 2 months are deduplicated.This feature was not provided. Previously, only whole files were deduplicated.When you store a large number of files of Microsoft Office 2003 and earlier, you can reduce the disk space for storing this data by eliminating duplicate chunks of such files.
Queries.
New capabilities for the query language:
  • Add data to a previously created temporary table (the ADD clause is implemented).
  • Index a temporary table by field sets (the INDEX BY SETS clause is implemented).
  • Create unique indexes in temporary tables (implemented the UNIQUE option for the INDEX BY and INDEX BY SETS clauses).

New features for the QuerySchemaSelectQuery object:

  • New property: Indexes.
  • New property: TableToAdd.
  • The Index property is deprecated.

We recommend that you use new features in the following cases:

  • You select data from one temporary table, combine it with other data, and place in a new temporary table.
  • You execute multiple queries to the same temporary table with filter or merging by different fields (field sets).
These features were not provided.Advanced temporary table features in the query language.
Configuration extensions.
Now you can adopt business processes and tasks. For adopted objects, you can change a business process route map. This map fully replaces a route map of the extended configuration when you import an extension.These features were not provided.Advanced configuration extension features.
Server clusters.
Administration tools.
When you add a new production server, you can disable the assignment of any functionality to this server. To do this, create a forbidding functionality assignment rule. It will be applied automatically.

New features:

  • New checkbox in the dialog box for creating a new production server: Set forbidding functionality assignment rule.
  • New parameter for the IServerAgentConnection.RegWorkingServer() COM connection method: SetProhibitingFunctionalityAssignmentRule.
  • New parameter for the IAgentAdminConnection.regWorkingServer() Java interface method: AddProhibitingAssignmentRule.
  • New parameter for the server mode of the RAC utility: add-prohibiting-assignment-rule.
  • New parameter for the AdministrationWorkServer.Write() method: SetProhibitingFunctionalityAssignmentRule.
This feature was not provided.

Previously, new functionality was immediately assigned to a new production server. This could lead to various errors as the new production server was not fully configured.

Simplified setup of a new production server by the administrator after adding the server to the server cluster.
Server clusters.
Administration tools.
Now you can select a security profile from the list of existing security profiles for the Security profile and Safe mode security profile fields of the infobase properties. For the Resource consumption counter field of the properties of the resource consumption limit, you can select a counter name from the list of existing resource consumption counters.

You can still enter names of security profiles and resource consumption counters manually if needed.

These features are implemented in the cluster console and the standard data processor of server cluster management.

These features were not provided. Previously, you could enter names of security profiles and resource consumption counters only manually.Reduced the risk of incorrect input for:
  • Security profile name while editing the infobase properties.
  • Name of the resource consumption counter while editing resource consumption limits.
Administration tools.
In the file infobase, the list of places where 1C:Enterprise searches for the ExternalSessionManagementRequired and ExternalSessionManagementConnectionString parameters in the conf.cfg files is extended.In the file infobase, 1C:Enterprise searched for the ExternalSessionManagementRequired and ExternalSessionManagementConnectionString parameters in the conf.cfg file. This file was located in the infobase directory or by a path specified in the ConfLocation parameter of the configuration file located in the infobase directory.Now you can manage the placement of settings of the external session management service more flexibly in the file infobase.
Server clusters.
Administration tools.
Now you can manage the load on server clusters for infobases with low user activity:
  • Minimum period to start scheduled jobs without active users.
  • Maximum shift to start scheduled jobs without active users.
  • Delay in configuration export by a working process without active users.

New features:

  • New infobase parameters in the cluster console and the standard data processor: Delay in configuration export by a working process, Minimum period to start scheduled jobs, and Maximum shift to start scheduled jobs.
  • New COM connection properties of the IInfoBaseInfo object: ConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers, MinimumScheduledJobsRunningPeriodWithoutActiveUsers, and MaximumScheduledJobsStartShiftWithoutActiveUsers.
  • New Java interface methods of the IInfoBaseInfo object: getConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers(), setConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers(), getMinimumScheduledJobsStartPeriodWithoutActiveUsers(), setMinimumScheduledJobsStartPeriodWithoutActiveUsers(), getMaximumScheduledJobsStartShiftWithoutActiveUsers(), and setMaximumScheduledJobsStartShiftWithoutActiveUsers().
  • New parameters of the infobase mode of the RAC utility: configuration-unload-delay-by-working-process-without-active-users, minimum-scheduled-jobs-start-period-without-active-users, and maximum-scheduled-jobs-start-shift-without-active-users.
  • New properties for the AdministrationInfoBase object: ConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers, MinScheduledJobsStartPeriodWithoutActiveUsers, and MaxScheduledJobsStartShiftWithoutActiveUsers.
This feature was not provided.Now you can manage the scheduled job behavior for infobases with low user activity easier and faster.
Administration tools.
Technological log.
New features:
  • You can manage the placement of technological log files: in a directory structure or in a flat file list. New attribute of the log item of the logcfg.xml file for technological log setup: placement.
  • You can set up log file rotation: by the time or by a log file size. You can specify rotation criteria: a file size and a rotation period. New attributes of the log item of the logcfg.xml file for technological log setup: rotation, rotationsize, and rotationperiod.
  • You can set up compression for outdated technological log files. Compression is performed in the background during the log file rotation. New attribute of the log item of the logcfg.xml file for technological log setup: compress.
  • You can save technological log files in the JSON format. New attribute of the log item of the logcfg.xml file for technological log setup: format.

You can disable automatic deletion of technological log files by specifying 0 in the history attribute of the log item of the logcfg.xml file for technological log setup. In this case, use external tools to clear the technological log directory. Changed the algorithm for deleting technological log files. Canceled the check for unknown technological log files in the directory.

Implemented a new property that describes a severity level of technological log events: level.

These features were not provided.Advanced features for generating the 1C:Enterprise technological log. For example, you can use it in external log analysis tools.
Server clusters.
Administration tools.
Now you can provide performance indicators (metrics) of the server cluster in the OpenMetrics format for the cluster administration server (ras) and the standalone server (ibsrv). Implemented a set of HTTP request parameters that will allow you to limit the set of received metrics.

New commands for the command line of the cluster administration server: monitor-address, monitor-port, and monitor-base. To access metrics, use 1C:Enterprise authentication.

New parameters for the command line of the standalone server: monitor-address, monitor-port, and monitor-base. New section of the gates section for the standalone server configuration file: monitor. The section includes the following parameters: address, port, and base. Authentication is not required to access metrics.

To use metrics in OpenMetrics format, a CORP license is required.

This feature was not provided.Advanced features for generating the 1C:Enterprise technological log. For example, you can use it in external log analysis tools.
Server clusters.
Administration tools.
Implemented a new event log mode (without the infobase) for the standalone server management utility (ibcmd): You can export the event log in the XML and JSON formats and export the log event model as an XSD schema. New command: eventlog.This feature was not provided.Simplified the event log receipt for analysis with external tools.
Database copies.
Now 1C:Enterprise supports a new tool for database backup update (version 2) for PostgreSQL. To enable this tool, make sure all the following conditions are met:
  • PostrgeSQL version 10 or later.
  • The DBMS is installed or updated from a distribution package provided by 1C Company.
  • The DBMS configuration file has the wal_level=logical parameter set.
  • In the standard data processor for database backup management, the standard replication version 2 is enabled for the selected infobase.
Previously, 1C:Enterprise supported the new tool for database backup update (version 2) only for Microsoft SQL Server.When you use the new tool for database backup update, the update speed increases.
Cryptography support.
Now 1C:Enterprise supports the ACH.1 format in the base64 encoding in cryptography methods.This feature was not provided.Now you can process ACH.1 data (certificates, revocation lists, and PKCS#7 data) directly in the base64 encoding without prior conversion into binary data.
Information registers.
Implemented additional record modes for a record set of an independent information register:
  • Merge. In this case, records whose key fields match with the record set to be saved are updated in the infobase. The remaining set records are simply added to the register.
  • Delete. In this case, records whose key fields match with the records included in the record set are deleted from the infobase.

New system enumeration that describes possible options for saving a record set of the information register: ReplacementMode. For the InformationRegisterRecordSet.Write() method, you can specify a value of the ReplacementMode system enumeration type as a value of the Replace parameter in addition to the Boolean type value.

The BeforeWrite() and OnWrite() event handlers and the respective subscription handlers receive a value of the Replacing parameter as it was passed to the Write() method of the record set of the information register.

Previously, you could only add or fully replace the existing infobase records of a record set of an independent information register.In some scenarios, you can significantly speed up operations with independent information registers.
Automated testing.
Extended automated configuration testing capabilities:
  • New method: TestedFormTable.CopyRow().
  • New GetParent() method for the following objects: TestedClientApplicationWindow, TestedCommandInterfaceGroup, TestedCommandInterfaceButton, TestedForm, TestedFormField, TestedFormGroup, TestedFormButton, TestedFormTable, and TestedFormDecoration.
  • New methods for the TestedFormField object: TitleIsShown().
  • New method for the form field extension for the tested formatted document: ClickFormattedDocumentHyperlink().
  • New feature for the TestedFormField.WriteContentToFile() method: you can save content to a file with a different name if the document in the field has already been saved. New SaveAs method parameter.
  • New HTML document extension for the tested form field. It allows you to perform actions similar to the formatted document field.
  • New methods to expand a form field for a tested spreadsheet document: TextIsWithinAreaBounds() and IncludedInMergedArea().
  • New method for the TestedFormDecoration and TestedFormField objects that display a formatted document: GetFormattedStringHyperlinksPresentations().
  • New method for cases when a form field displays a spreadsheet document: TestedFormField.ExecuteChoiceFromDetailsMenu().
  • New method: TestedApplication.ClearFileDialogResult().
  • New methods for the TestedForm object: GetChoiceListPresentation(), CurrentEnable(), and CurrentReadOnly().
  • New property: TestedClientApplicationWindow.URL.
  • New global context method: CurrentSessionIsTested().
These features were not provided.Extended automated application testing capabilities.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Standard functions.
Administration tools.
Server clusters.
New feature: you can save and restore administered server parameters for the Server management standard data processor (the Cluster parameters button). The parameters are saved to an XML file. The file structure is not documented.

Creating a new connection to a server cluster and commands for saving and restoring the cluster list are grouped in the Connections button.

The Server management standard data processor did not support saving or restoring parameters of administered server clusters to a file or from a file.It is now easier to transfer server cluster parameter settings between computers, for example, when you deploy identical clusters.
Managed locks.
When you use an accounting register, managed lock absorption is triggered before managed lock escalation. As a result, concurrent operation with the accounting register increases.Previously, when you used an accounting register, managed lock escalation was triggered earlier than lock absorption. As a result, concurrent operation with the accounting register could become impossible.Increased concurrent operation with an accounting register.
Collaboration system.
macOS.
Web client.
New feature: you can use video calls in Safari version 13 or later running macOS.Video calls were not supported in Safari.Video calls are now supported in Safari running macOS.
Administration tools.
If an error occurs when importing the distribution package of a client application over HTTP, the error message text includes not only the error code, but also a text description (if available).If an error occurred when importing the distribution package of a client application over HTTP, the error message text included only the error code.Simplified troubleshooting of issues that occur when importing the distribution package of a client application over HTTP.
Error handling.
Server clusters.
Administration tools.
When a session is closed and a server call is terminated from Designer, 1C:Enterprise language, the resource consumption tool, or through the administration tools, if the session data file was not deleted, the user will see a session termination reason message. The message will be displayed upon the next server call even if the session was deleted not during the server call.

New system enumeration property: ErrorCategory.ForcedShutdown. This category includes all exceptions related to terminating a server call using administration tools and all exceptions related to closing a session using platform tools (from Designer, from 1C:Enterprise language, or through administration tools).

The user could not see the text that might have been specified by the administrator in case of forced user session termination.Eliminated unexpected system behavior.
Error handling.
Server clusters.
Administration tools.
Now you can specify a session termination reason message to be displayed to the user in the dialog box of user session termination from Designer when updating the database configuration.

New parameter for the (ibcmd) infobase restore and config apply commands of the standalone server management utility: session-terminate-message. This parameter allows you to specify a text with a session termination reason to be displayed to the user.

If the session-terminate command-line option of the ibcmd utility instructs to terminate user sessions, and the session-terminate-message parameter is not specified, the utility will wait for you to enter a message in the console and will keep running only after the message is entered.

Previously, when you terminated user sessions from Designer, you could not specify a text with a user session termination reason.

The standalone server management utility (ibcmd) did not allow you to specify a text to be displayed to the user as a session termination reason.

Now you can specify a text with a session termination reason when sessions are terminated while updating the infobase configuration from Designer or using the standalone server management utility.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Global search.
Accelerated global search operations.Global search operations took more time.Accelerated global search operations.
Server clusters.
Optimized metadata loading when loading the configuration in client/server mode.

Reduced time required to connect the first client to the infobase. Faster startup of the first infobase session on a working process that has not yet serviced sessions of this infobase.

In client/server mode, configuration metadata loading was time-consuming. It took a long time to the first infobase session on a working process that has not yet serviced sessions of this infobase.Faster startup of the first infobase session on a working process that has not yet serviced sessions of this infobase.
Standalone server.
Faster startup of a standalone server in file and client/server modes.Standalone server startup was time-consuming.Faster startup of a standalone server in file and client/server modes.
Development tools.
Optimized the global replacement in the configuration in Designer.Previously, the global replacement in the configuration took a lot of time.Optimized the global replacement in the configuration in Designer.
Development tools.
Optimized search for references to configuration objects in Designer.Previously, search for references to configuration objects was time-consuming.Optimized search for references to configuration objects in Designer.
Server clusters.
Optimized CPU and RAM in a server cluster (with fault tolerance level 2 or higher), improved reliability and speed of server state replication under high loads and the overall cluster stability under high loads.When running a highly loaded server cluster with fault tolerance level 2 or higher, the cluster used more computer resources and was less stable.Optimized server cluster computer resources and improved server cluster reliability and stability.
Full-text search.
Optimized use of RAM by the full-text search engine.

For that, re-index the full-text search index.

The full-text search engine did not optimally utilize the computer RAM.Reduced RAM consumption by the full-text search engine and improved application stability.
Database copies.
Selecting a copy on which to run the query is now faster.Selecting a copy on which to run the query took more time.Improved application performance when it is necessary to select a database copy on which to run the query before running the query.
Collaboration system.
When you make video calls in the thin client, the load on the CPU and network channel of the client computer is reduced.When you made video calls in the thin client, the load on the CPU and network channel of the client computer was higher.The load on the CPU and network channel of the client computer during video calls in the thin client is reduced.
Collaboration system.
The load on the CPU and network channel of the collaboration system server is reduced when you make group video calls using the thin client.

For that:

  • update the platform to version 8.3.25.
  • update the collaboration system server to version 25.
  • update the Janus video server on the collaboration system server to version 1.0.4.
When you made group video calls using the thin client, there was an increased load on the CPU and network channel of the collaboration system server.Using thin clients for group video calls improves the quality of video calls and increases the number of users in a single group video call.
DBMS operations.
Creating object tables and writing record sets of information and accumulation registers is improved.Creating object tables and writing record sets of information and accumulation registers took more time.Improved creation of object tables and writing record sets of information and accumulation registers.
Database copies.
Improved performance of initial database copy filling.Initial database copy filling took more time.Improved performance of initial database copy filling.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Collaboration system.
Now you can change the administrator of the collaboration system subscriber. You can keep the list of administrators of the collaboration system subscriber. You can change the email address for the collaboration system user.

New methods for the collaboration system manager: GetNewAdministrationKey(), SendTemporaryCode(), AddToSubscriberAdministrators(), ExcludeFromSubscriberAdministrators(), and SetSubscriberEmail().

New property: CollaborationSystemUser.SubscriberAdministrator.

New property: CollaborationSystemUsersFilter.SubscriberAdministrator.

Updated the Collaboration system management standard function.

This feature was not provided. Previously, you could not change the subscriber administrator.Now you can restore access to a collaboration system subscriber when access to the subscriber registration email has been lost.
Administration tools.
An error is generated when saving (by any means) an infobase user with a specified operating system username exceeding 128 characters.When saving an infobase user with a specified operating system username exceeding 128 characters:
  • If an infobase user was saved in Designer, the session was abnormally terminated.
  • If an infobase user was saved using 1C:Enterprise language, the value was ignored and no error was generated.
Eliminated unexpected system behavior.
Server clusters.
Administration tools.
For the Data property of a CLSTR event (when the Event property is set to performance update), the displayed data that describes the current performance indicators of the cluster processes is documented.The data that is displayed in the Data property of a CLSTR event (when the Event property is set to performance update) was not documented.Updated the system documentation.
Configuration extensions.
New feature: you can include attributes added by a configuration extension to extended objects in native and adopted filter criteria.

New feature: you can change the Command parameter type property in extensions for common commands and configuration object commands.

New feature: you can change the Selection form property in extensions for constants, attributes, resources, dimensions, and fields of external data sources.

New feature: you can add native subordinate subsystems to adopted subsystems in extensions. New feature: you can disable modification when attaching an extension for the Content property of adopted subsystems. Adopted subsystems are edited in the properties panel, similar to other adopted configuration objects.

These features were not provided.Advanced configuration extension features.
Information registers.
Catalogs.
New feature: for dimensions of an independent information register and the Owner standard catalog attribute, you can specify what actions will be taken during infobase restructuring when the set of types that describe the type of the corresponding object is reduced. Now you can:
  • Disable type editing.
  • Convert values to a new set of types.
  • Delete records that match the deleted types.

New property for an independent information register dimension and the Owner standard catalog attribute: Type shrinking mode. New properties for the StandardAttributeDescription and Dimension metadata objects: TypeReductionMode.

This feature was not provided.

An attempt was always made to convert the value for an information register dimension. Type shrinking was always blocked for the Owner standard catalog attribute.

Now it is easier to develop configuration objects (information registers and subordinate catalogs) that are processed only using 1C:Enterprise language, but the types include a large number of other configuration objects.
Data accelerator.
New feature: parallel update of all used Data accelerator instances if a scalable Data accelerator is used (Data accelerator is running on more than one production server of the server cluster) and a database copy is located on more than one Data accelerator instance.

An update error on a single Data accelerator instance will not stop the entire Data accelerator update. All instances except for the one where the error occurred will be updated.

Previously, Data accelerator instances were updated sequentially, one by one. If an error occurred while updating one instance, the process was terminated. As a result, all Data accelerator instances that followed the one with an error had incorrect data.Reduced data update time if Data accelerator consists of several instances.
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.18.The format version of configuration dump to XML files was 2.17.Configuration dump to XML files supports new platform features.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
XML and XDTO support.
In XDTO serialization of charts of accounts, properties corresponding to common attributes are placed after properties corresponding to accounting flags.

This change is not implemented in 8.3.24 compatibility mode.

In XDTO serialization of charts of accounts, properties corresponding to common attributes were placed before properties corresponding to accounting flags.Eliminated unexpected system behavior.
Server clusters.
Administration tools.
When a server cluster is started, all the required data is immediately read from the cluster list and cluster registry files. In case of errors reading this data, the server cluster is not started and the detected errors are recorded in the technological log.When a server cluster was started, data from the cluster list and cluster registry files was read as needed. Errors that could occur when reading these files resulted in hard-to-diagnose errors during cluster operation.Simplified administration for errors that may occur when reading the cluster list and cluster registry at server cluster startup.
Collaboration system.
Upgrade: you can place the button panel in collaboration system messages (including integrations with various external systems).

Collaboration system message actions are deprecated. It is recommended that you replace the collaboration system actions on the button panel.

New property for the CollaborationSystemMessage object: SourceMessage.ButtonPanel. +New method for the CollaborationSystemIntegration object: MessageButtonPanelButtonActionSupported().

New event handler for the collaboration system bot module:

CollaborationSystemMessageButtonPanelButtonClickProcessing().

New event handler for the application module:

OnCollaborationSystemMessageButtonPanelButtonClick().

The following properties and methods are deprecated:

  • Property CollaborationSystemMessage.Actions.
  • Methods AttachMessageActionHandler() and DetachMessageActionHandler() for the collaboration system manager.
  • Application module event handler OnCollaborationSystemMessageActionChoice().
  • Objects CollaborationSystemMessageActionCollection and CollaborationSystemMessageAction.
There was an option to set actions for collaboration system messages that was not available in integration messages.Now you can implement a single visual interface of interaction between a collaboration system user and an information system (bot interface), which looks uniformly in all collaboration system messages.
Administration tools.
You can no longer specify the same email address (in different registers) for different infobase users. If you try to save a second user with an existing email address, an exception will be thrown.You could specify the same email address (in different registers) for different infobase users.Removed possible ambiguity in identifying a user by email address.
Administration tools.
Accelerated email address uniqueness verification when saving users.

For that, we recommend that you run the infobase verification and repair in repair mode. This will create the necessary index for the user table and speed up the email address uniqueness verification.

The email address length cannot exceed 128 characters.

When you saved an infobase user, the email uniqueness verification was time-consuming.

The email address length could exceed 128 characters.

Accelerated email address uniqueness verification when saving users.
Administration tools.
Server clusters.
New properties for the AdministrationSeance object:
  • CurrentDBMSCallDuration.
  • LastDBMSCallTime.
This feature was not provided. +These properties were available in other system administration interfaces, but were missing from the AdministrationSeance object.Eliminated unexpected system behavior.
Server clusters.
Administration tools.
A resource consumption counter with the "server call" registration period counts each session of a single user as a separate object. Combining different sessions of a single user is preserved for counters whose data registration period is other than "server call".A resource consumption counter with the "server call" registration period summarized the indicators of all sessions of a single user.Eliminated unexpected system behavior.
Server clusters.
Administration tools.
Implemented correct processing of termination of a server call executing a DBMS call using a resource consumption counter:
  • When a session is terminated, an error specified by the administrator is displayed and the session is terminated.
  • When a call is terminated, an error specified by the administrator is displayed and the terminated server call is not repeated.
The termination of a server call executing a DBMS call using a resource consumption counter was processed incorrectly:
  • First, a DBMS call was terminated. Then a counter restriction was triggered.
  • When a server call was terminated, the DBMS call was repeated. When a session was deleted, a bad connection error was displayed and then the session was deleted.
Eliminated unexpected system behavior.
Server clusters.
Administration tools.
Implemented correct display of used CPU time values for resource consumption counters.Used CPU time values for resource consumption counters may have been displayed incorrectly.Eliminated unexpected system behavior.
XML and XDTO support.
JSON support.
New feature: you can explicitly specify a value type during XDTO serialization (in XML or JSON) of values that dot not exist in the data model (for an open content model). New parameter for the XDTODataObject.Add() method: TypeAssignment.

When reading data using the XDTOFactory object, you can now specify how to determine the type of the value to be read if the value does not exist in the content model. New parameter for the ReadXML() and ReadJSON() methods of the XDTOFactory object: TypeAssignment.

During XDTO serialization of a value missing from the data model, the type of such value was not written to the resulting file.Eliminated unexpected system behavior.
Administration tools.
Information about closed infobase sessions is saved to:
  • Client/server mode and standalone server mode: snccntx.dat file.
  • File mode: 1Cv8snc.1CD file in the infobase directory. The file is not deleted when the last infobase session ends.

Information about closed sessions is stored for a week. Old information is cleared once an hour.

This feature was not provided.Upgrade: storage of information about closed infobase sessions.
Collaboration system.
New feature: a set of methods, availability, and behavior in different client applications are unified for the following collections: CollaborationSystemAttachmentCollection, CollaborationSystemMessageButtonPanelButtonRow, and CollaborationSystemMessageButtonPanelButtonRows.The following collections had different sets of methods, availability, and behavior in different client applications: CollaborationSystemAttachmentCollection, CollaborationSystemMessageButtonPanelButtonRow, and CollaborationSystemMessageButtonPanelButtonRows.Unified description and behavior of similar object collections in the collaboration system. Eliminated unexpected system behavior.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Standard speech processing.
  • Speech recognition management.
  • Speech service management.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
Mobile device-specific features.
Now you can use the speech recognition tool in the mobile version of 1C:Enterprise:
  • Mobile platform. Allows you to use only a cloud-based speech recognition service.
  • Mobile client. Allows you to use both a cloud-based and a local speech recognition tool.

Implemented the corresponding objects, properties, and methods of 1C:Enterprise language in the mobile version of 1C:Enterprise.

This feature was not provided.You can use speech recognition on mobile devices.
Mobile device-specific features.
Mobile platform.
Mobile client.
Collaboration system.
Now the mobile version supports sharing files from a mobile application through standard interfaces of the mobile operating system.

Now the collaboration system supports sharing the entire message, the selected text of a message or a message input field, or a message attachment.

New global context property: DeviceDataSharingTools. New feature for the MultimediaData object: a constructor of an object from a file.

New values for the CollaborationSystemStandardCommand system enumeration: ShareMessage and ShareAttachment. You can only use these commands in the mobile client.

This feature was not provided.Now it is easier to use third-party data processing applications that are generated in a mobile application built on the mobile version of 1C:Enterprise.
Mobile platform.
Mobile client.
System requirements.
iOS versions 9 and 10 are no longer supported +iOS versions 13, 14, 15, and 16 are now supported.The mobile version of 1C:Enterprise supported iOS versions 9 and 10.The list of supported iOS versions is updated. The mobile version of 1C:Enterprise supports iOS versions 11, 12, 13, 14, 15, and 16.
Mobile application builder.
To build mobile applications, use Java version 17 or later.

To build mobile applications using mobile version 8.3.25, use:

  • Mobile application builder version 8.3.25.
  • Java version 17 or later (Java version 19 or later is recommended)

To build mobile applications using earlier platform versions, use:

  • Mobile application builder version 8.3.25.
  • Java version 17 or later.

When using Java versions 8–16, you can still build mobile applications using mobile version 8.3.24 or earlier versions.

To build mobile applications, Java versions from 8 to 13 were used. The build tools did not allow you to use Java version 14 or later.Now there are new tools for building Android mobile applications.
Mobile platform.
Mobile client.
Mobile device-specific features.
New values for the BarcodeType system enumeration: QRCode, DataMatrix, PDF417, Aztec, MaxiCode, UPCA, UPCE, EAN13, EAN8, Codabar, Code93, Code128, RSS14, RSSExpanded, Code39, and ITF.

For the ShowBarcodeScanning() method, the BarcodeType parameter can have an array of values that describe what barcode types are expected in this scanning. A mobile application keeps a single list of scannable barcode types across all supported mobile platforms.

Improved barcode recognition quality.

The scan window on Android is now larger.

The ShowBarcodeScanning() method did not support accurately specifying the list of expected barcodes. The barcode recognition quality was worse. The list of supported scannable barcode types depended on the platform for which the mobile application was being built.Improved barcode scanning quality. When you specify expected barcodes accurately, this can reduce the CPU load during scanning, resulting in lower power consumption during barcode scanning.
Mobile device-specific features.
Now the mobile version allows you to offer the user to rate the application and provide feedback in the application store of the corresponding mobile operating system from 1C:Enterprise language.

New global context method: ShowInputAppRate().

This feature was not provided.Allows you to offer users to send ratings and reviews to the application store without leaving the application. Ratings and reviews affect the overall application ranking in search results. Applications that have more ratings and reviews are more commonly offered to the users.
Mobile application builder.
When you build Android-based mobile applications, the builder will check whether the added manifest element of the application you build is already available in the manifest. If the element you add is already in the manifest, it is not added again.Previously, when you built Android-based mobile applications, the builder did not check whether the added manifest element of the application you built was already available in the manifest.Reduced the number of difficult-to-diagnose errors when building Android-based mobile applications which occur when, for example, add-ins require a permission that is already requested upon building by another add-in or the application. As a result of the change, duplicate records will not be included in the resulting manifest of the application being built. This will allow you to build an application that was previously built with errors.
Mobile platform.
Mobile client.
Mobile device-specific features.
1C:Enterprise 8 now supports the Firebase Cloud Messaging service on HTTP v1 for sending push notifications. The service is supported in version 8.3.25.43 and later mobile versions. To use push notifications, modify the application in terms of getting and using an access token for the Firebase Cloud Messaging service on HTTP v1.

The GetAccessToken() method of the manager for sending deliverable notifications is used to get an access token (changes are made to the type and content of the method parameters).

The Send() method of the manager for sending deliverable notifications uses the previously received access token.

Previously, the 1C:Enterprise mobile platform did not support the Firebase Cloud Messaging service on HTTP v1. It supported the previous service version, which is disabled by Google.Updated support for the Android push notification service.

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Data accelerator.
System requirements.
Now you can run Data accelerator on Astra Linux, ALT Linux, and RED OS.

For the exact version numbers, see the documentation.

Data accelerator was not supported on Astra Linux, ALT Linux, and RED OS.Extended list of operating systems that support Data accelerator.
Common objects.
The error of generating UUIDs of versions 3 and 5 when using the UUID object is fixed. This change is not implemented in 8.3.24 compatibility mode.

New method: GetUUIDWithCompatibilitySupport(). It will allow getting a UUID with an error (as in previous platform versions) with compatibility mode disabled. It is not recommended to use this method for any other purpose.

Previously, when generating UUIDs of versions 3 and 5 using the UUID object, UUIDs were generated with an error. The result did not fully meet the RFC 4122 standard.Eliminated unexpected system behavior.
XML and XDTO support.
The size of the XML item value cannot exceed 100,000,000 characters.Previously, the size of the XML item value could not exceed 10,000,000 characters. This value was not documented.Reduced the number of errors that occurred as the actual size of the XML document item exceeded the maximum size.
Mobile platform.
Mobile client.
Mobile device-specific features.
Now you can use speech synthesis in the mobile version of 1C:Enterprise. New feature: Speech synthesis.Previously, the mobile version of 1C:Enterprise did not support speech synthesis.Advanced 1C:Enterprise mobile platform features. You can implement voice prompts for certain application processes in mobile applications based on the 1C:Enterprise mobile platform.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 16.2
  • Postgres Pro Standard 16.2.1
  • Postgres Pro Enterprise 16.2.1
  • DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.22 and later.

Supported operating systems are defined by a DBMS vendor.

+

These versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 12.18, 13.14, 14.11, 15.6
  • Postgres Pro Standard 12.18.2, 13.14.2, 14.11.2, 15.6.2
  • Postgres Pro Enterprise 12.18.2, 13.14.2, 14.11.2, 15.6.2
  • DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
Mobile application builder.
Mobile 1C:Enterprise version 8.3.25 is now supported in the mobile application builder.Mobile 1C:Enterprise version 8.3.25 was not supported in the mobile application builder.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
System requirements.
DBMS operations.
  • Support of the following Postgres Pro DBMS versions is implemented: +Postgres Pro 1C: 12.19, 13.15, 14.12, 15.7, 16.3;
  • Postgres Pro Standard: 12.19.2, 13.15.2, 14.12.2, 15.7.2, 16.3.1;
  • Postgres Pro Enterprise: 12.19.2, 13.15.2, 14.12.2, 15.7.2, 16.3.1.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1C: 16.3;
  • Postgres Pro Standard: 16.3.1;
  • Postgres Pro Enterprise: 16.3.1.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.22 or later. +Supported operating systems are defined by a DBMS vendor.

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro Standard: 13.15.2, 14.12.2, 15.7.2;
  • Postgres Pro Enterprise: 13.15.2, 14.12.2, 15.7.2.

DBMS version bitness: E2k.

The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro Standard: 16.3.1;
  • Postgres Pro Enterprise: 16.3.1.

DBMS version bitness: E2k. The products are supported in 1C:Enterprise version 8.3.22 or later. +Supported operating systems are defined by a DBMS vendor.

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
Infobase verification and repair.
Optimized one of the steps in the infobase verification and repair process (Check logical infobase integrity > Other). This step is required when upgrading to version 8.3.25 for faster interaction with infobase users.Previously, this step took a significant amount of time.Reduced the time needed to restructure the user list.
Mobile platform.
Mobile client.
System requirements.
The mobile version of 1C:Enterprise now supports Android 14. The mobile version of 1C:Enterprise supports Android versions 5.0 - 14.

When a mobile application runs on Android 14 and later, if the mobile application uses the functionality of the Picture and video library, users can not only completely allow or deny access to the library, but also specify individual images or videos to provide access to.

Previously the mobile 1C:Enterprise version supported Android versions 5.0 - 13.Now the mobile 1C:Enterprise version supports the latest Android versions.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • 13.16, 14.13, 15.8;
  • Postgres Pro Standard: 12.20.1, 13.16.1, 14.13.1, 15.8.1;
  • Postgres Pro Enterprise: 12.20.1, 13.16.1, 14.13.1, 15.8.1;
  • Postgres Pro CERT Standart: 14.13.1, 15.8.1.
  • Postgres Pro CERT Enterprise: 13.16.1, 14.13.1, 15.8.1.

DBMS version bitness: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1C: 16.4;
  • Postgres Pro Standard: 16.4.1;
  • Postgres Pro Enterprise: 16.4.1;
  • Postgres Pro CERT Standart: 16.4.1;
  • Postgres Pro CERT Enterprise: 16.4.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

The products are supported in 1C:Enterprise version 8.3.22 or later.

Supported operating systems are defined by a DBMS vendor.

Previously these versions of Postgres Pro DBMS were not supported.Extended list of supported DBMS.
Client application.
Common attributes / Data separation.
Now 1C:Enterprise supports OpenID Connect authentication (including USIA authentication) in separated infobases.

Client applications that use OpenID Connect authentication support the /Z option of the client startup string.

In the default.vrd file, you can pass the separator values to the URL specified in the redirect_uri parameter of the OpenID provider description section.

Previously, 1C:Enterprise did not support OpenID Connect authentication in separated infobases.Simplified OpenID Connect authentication in separated infobases.
Client application form.
Values of form attributes with the Arbitrary type are correctly restored from the form settings.

We recommend that application developers analyze the usage of stored attributes of this type.

Previously, values of form attributes with the Arbitrary type were not restored from the form settings.Eliminated unexpected system behavior.
Linux.
System requirements.
1C:Enterprise now supports MOC 12 Linux distribution package. The distribution package runs on x86-64 processors.The distribution package was not supported.Extended list of supported Linux distribution packages.
DBMS operations.
System requirements.
The system now supports Tantor SE 1C DBMS versions 14.13.0, 15.8.0 and 16.4.1.

Supported processors: x86-64.

Supported operating systems are defined by a DBMS vendor.

This Tantor SE DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
Common objects.
The sequence in which property values are filled when using the FillPropertyValues() method on Linux is changed. The sequence of properties may vary depending on the 1C:Enterprise version and the operating system used.

We do not recommend that you use the FillPropertyValues() method to set property values that change the value of other properties. For example, do not apply this method to the PrintParametersKey property as setting this property may replace values of other properties.

The sequence in which property values were filled when using the FillPropertyValues() method on Linux was different.Changed sequence in which property values are filled when using the FillPropertyValues() method on Linux.
DBMS operations.
Configuration extensions.
Common attributes / Data separation.
The reliability of the platform is improved when there are several working processes or production servers in the cluster, to which connections can be assigned from a single separated infobase that uses extensions.Previously, when there were several working processes or production servers in the cluster, to which connections could be assigned from a single separated infobase using extensions, the platform was unstable and could lead to unexpected errors.Improved reliability of the platform with a distributed infobase, which uses extensions.
Administration tools.
When creating an infobase, all installed configuration templates will be displayed in the creation dialog box. The AppVersion property of the configuration template manifest is ignored when filling the template list.Previously, when creating the infobase, the creation dialog box displayed only those templates that contain values 8.2 and 8.3 in the AppVersion property of the configuration template manifest file.You can create configurations from templates created by 1C:Enterprise version 8.5.1 and later.
System operation safety.
Spreadsheet document.
When you open a spreadsheet document from a file, unsafe operation protection is active if enabled. If the spreadsheet document contains OLE objects and the document is opened in a client application running Windows, a warning is displayed. To enable unsafe operation protection, use the user property or the conf.cfg configuration file.

The positive answer to the system's question is recorded by user and infobase. The negative answer is not recorded, and the confirmation request will be displayed the next time you try to open a spreadsheet document with OLE objects.

When you opened a spreadsheet document from a file, unsafe operation protection was not used.Improved system security when opening spreadsheet documents containing OLE objects from a file.

Table of contents

Transition from the previous version to the version 8.3.25

Table of contents

Version 8.3.24

Version 8.3.24 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
New value for the Compatibility mode configuration property: Version 8.3.23.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.22 was available. +You can run configurations developed in versions 8.3.23 and earlier in version 8.3.24 without changing the configuration and data structures. This way, you can migrate to version 8.3.24 without changing the configuration, then make required changes, and disable compatibility mode. You can also use version 8.3.23 after migration to version 8.3.24. You can do it both before you disable compatibility mode and after you enable it again. +
Internet-enabled functionality.
Now you can use CryptoPro to establish a secure HTTP connection. You can manage the check mode of server certificate revocation using 1C:Enterprise language.

New object: CryptoProSecureConnection. New system enumeration: ServerTLSCertificateRevocationCheckMode. New property: OpenSSLSecureConnection.ServerTLSCertificateRevocationCheckMode. New parameter for the OpenSSLSecureConnection object constructor: ServerTLSCertificateRevocationCheckMode.

New feature: the HTTPConnection object constructor can get the CryptoProSecureConnection object as a SecureConnection parameter value.

Previously you were unable to use CryptoPro to establish a secure HTTP connection. Managing the check mode of server certificate revocation using 1C:Enterprise language was unavailable. Advanced secure HTTP connection features.
Speech recognition.
Now you can restrict local speech recognition for 1C:Enterprise system using the following tools:
  • The /DisableLocalSpeechToText command-line option.
  • The "disstt" parameter of the infobase connection string.
  • The AdministrationInfoBase.DisableLocalSpeechToText property of the object for server cluster administration.
  • The IInfoBaseInfo.DisableLocalSpeechToText property of the COM object for server cluster administration.
  • The setDisableLocalSpeechToText() and getDisableLocalSpeechToText() methods of the InfoBaseInfo Java interface object for server cluster administration.
  • New infobase property for the server cluster administration utility (rac): disable-local-speech-to-text.
  • The disable-local-speech-to-text parameter of the standalone server startup (including in the configuration file).
  • You can manage this feature in the standard data processor for server management.
This feature was not provided. +Previously you were unable to restrict local speech recognition. Now you can forcibly restrict local speech recognition. However, you can still use remote speech recognition.
Binary data storage.
Now you can use any external data storage accessible over Amazon S3 as a binary data storage. New global context property: BinaryDataExternalStorages. To access the settings of a binary data storage and an external binary data storage, the Administration right is required. The standard function of binary data storage management is now improved.

To use the S3 storage as an external binary data storage, a CORP license is required.

This feature is provided solely for beta testing purpose. To use the S3 storage as an external binary data storage during beta testing, a testing license is required. Without it, the feature is unavailable.

+

+

This feature was not provided.

Previously you were able to store binary data only on the computer running 1C:Enterprise server cluster.

+

Advanced binary data storage features. +
Binary data storage.
Now you can eliminate duplicates of repeating data (deduplication). Deduplication occurs both when writing data and in the background. +New properties for the BinaryDataStorageInformation object: StoredDataSizeOnDisk and DeduplicatedItemsCount.This feature was not provided.A binary data storage can take up less disk drive space if the same data is placed in the storage.
Binary data storage.
When using a binary data storage, you can now do the following:
  • Get statistical information about the binary data storage.
  • Clear the storage of unused data.
  • Clear and back up the binary data storage at the same time.

New manager methods of the binary data storage: GetInformation(), ClearUnusedSpaceByUniversalDate(), and GetBackupCreationUniversalDate(). New global context method: GetDatabaseAndBinaryDataStorageDataSize().

New parameter for the CreateFullBackup() and CreateDifferentialBackup() manager methods of the binary data storage: UniversalDateUntilWhichPerformClearing.

New feature: the standard Binary data storage management function now displays the information about the binary data storage and has tools to clear the storage of deleted data.

These features were not provided.Advanced administration features of the binary data storage.
Standalone server.
Binary data storage.
Now the standalone server supports binary data storages.

New --binary-storage-data command is implemented for the command line of the standalone server startup.

This feature was not provided.Now the standalone server allows using binary data storages.
Using the clipboard.
Now you can use the operating system clipboard. New global context property: ClipboardTools.

New event handlers for the application module and the client application form module: OnPasteFromClipboard.

New methods for the FileRef object: GetAsStringAsync() and GetAsBinaryDataAsync().

The clipboard is unavailable on mobile devices.

This feature was not provided.Now you can use the clipboard of the current operating system.
Administration tools.
Configuration extensions.
Now you can restructure tables of infobase configuration extensions while verifying and repairing the infobase:

New item in the Verify and repair infobase dialog box: Restructuring of configuration extension tables. +New parameter for the /IBCheckAndRepair command of Designer batch mode: RebuildConfigurationExtensions. +If the verification process detects that there is no extension table, such table will be created if the verification and repair mode is enabled.

This feature was not provided.Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features.
Administration tools.
Configuration extensions.
Now you can verify and repair an infobase in specific separated infobase areas:

New capabilities in the Verify and repair infobase dialog box: you can specify data areas for running verification and repair. +New parameter for the /IBCheckAndRepair command of Designer batch mode: -Z. It allows you to specify data areas for running verification and repair. +If no separators are specified, the verification and repair operation is performed for the entire infobase. +

This feature was not provided.Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features.
Administration tools.
Configuration extensions.
If only the Check logical integrity of configuration extensions or Restructuring of configuration extension tables parameters are selected when you configure infobase verification and repair, exclusive mode for the entire infobase is not required and not set.

The following locks are set for each processed area:

  • Separated lock if only verification is selected.
  • Exceptional lock if the verification and repair operation is selected, and it is required to repair the infobase.

An area lock error does not interrupt the entire verification and repair process but moves it to the next data area.

This feature was not provided.Now the infobase verification and repair tool is more compliant with the current 1C:Enterprise platform features.
Collaboration system.
Now you can exchange files with WhatsApp if the collaboration system is integrated with it.This feature was not provided.Advanced features for integration with instant messaging systems.
Configuration extensions.
External data sources.
Now you can create your own external data sources:
  • Tables and fields for external data source tables.
  • External data source functions.
  • Dimension tables, dimension table fields, dimensions, and resources of external data source cubes.

Now you can adopt external data sources. When several configuration extensions change adopted object properties, object property values are obtained from the last extension in the list.

This feature was not provided.Advanced configuration extension features.
Development tools.
New features for a conditional breakpoint when debugging applications:
  • Enable or disable a breakpoint using the checkbox in the dialog box of breakpoint condition settings.
  • Open the dialog box by pressing Ctrl+F9.
  • Perform more actions in the field for editing the breakpoint triggering condition.
  • Specify that the breakpoint must be triggered when called from a particular configuration method. You can specify the method name using regular expressions. The regular expression dialect is similar to the dialect of regular expressions in 1C:Enterprise language.
  • Set a breakpoint triggering condition based on the number of hits in a text line in 1C:Enterprise language.
  • Specify actions to perform when hitting a breakpoint:
    • Display a message in the message window.
    • Display an expression evaluation result.
    • Display the call stack of 1C:Enterprise language.
    • Display the number of hits in the breakpoint.
    • For all the listed actions, you can choose not to stop after performing an action but to continue running 1C:Enterprise language.

Enable a disabled breakpoint by pressing F9 on it.

Move a breakpoint within the module using the mouse and the keyboard.

Copy and insert a breakpoint using the clipboard.

Previously the dialog box for editing conditional breakpoints contained only a simple string for editing the breakpoint condition.

When you pressed F9 on a disabled breakpoint, the breakpoint was deleted and all the settings were lost.

You were unable to transfer breakpoints using the keyboard, the mouse, and the clipboard.

Simplified application debugging. Extended breakpoint capabilities. Enhanced setting of conditions for conditional breakpoints.
Charts.
Data composition system.
Changed the display of pie and doughnut charts, including 3D charts. Now you can manage the display of pie and doughnut charts. When rendering pie and doughnut charts, the value of the LabelLocation property is applied.

New properties for the Chart object: BeginAngle, EndAngle, and Chart3DDepth.

For the Chart.LabelLocation property, the default value will be Auto.

New properties for the DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance data composition system objects: ChartType.BeginAngle, ChartType.EndAngle, and ChartType.Chart3DDepth.

This change is not implemented in version 8.3.23 compatibility mode.

These features were not provided.

For the Chart.LabelLocation property, the default value was Edge.

Advanced display features for pie charts.
Data display.
New pictures in the picture library:
  • FormattedString
The 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

FunctionalityAfterBeforeResult of changes
Standard functions.
Now you can manage the history usage settings of the standard Data change history function.This feature was not provided.You can manage the data change history directly from the standard function without any third-party tools.
Collaboration system.
Now you can mark messages as read in collaboration system conversations. You can see the mark in a thin client, a thick client, and a web client. In a mobile client, the mark is not displayed. However, other client applications show that a message is read in the mobile client.

You can see the read status in context conversations where the number of message senders and recipients is less than 100. You can also see the read status in noncontext conversations where:

  • There is no "All users" participant.
  • There are other participants besides you.
  • Total number of conversation participants is less than 100.
This feature was not provided.Collaboration system conversations are now more user-friendly.
Collaboration system.
When you send a message in a noncontext conversation, the conversation moves to the top in all your sessions in the infobase. This change is implemented in the thin, thick, and web clients.Previously, the order of your noncontext conversations in several sessions could differ.Collaboration system conversations are now more user-friendly.
Web services and HTTP services.
Now you can specify how many background jobs must run to perform the initial population of copy tables for the standard function of database copy management. New parameter in the Database copy parameters form: Number of filling jobs.This feature was not provided.

Previously the initial population of copy tables required four background jobs. You could not change this number manually. You could only use 1C:Enterprise language for this purpose.

Now the administrator can manage the volume of the initial population of database copy tables.
Technological log.
When you run thin and thick client applications, you can now generate a technological log using the video module of the collaboration system. You can also generate abnormal termination dumps for the video module. You can configure it using the standard file for the technological log setup: logcfg.xml.

If you use 32-bit 1C:Enterprise running on a 64-bit operating system, you cannot use an external application to create abnormal termination dumps. Abnormal termination of the video module is dumped during the process.

New technological log events: <VIDEOCALL>, <VIDEOCONN>, <VIDEOSTATS>.

This feature was not provided.Now you can send the information to the technical support easier and faster when you face any issues with the video module of the collaboration system.
Administration tools.
Now installed platform versions can be deleted automatically. They will be deleted with a separate process with a lower priority. The deletion process will not affect your operations. You can set up the parameters to automatically delete versions in the dialog box of the interactive launcher setup.

Now you can specify one or several system versions that must not be automatically deleted.

New parameters for the 1cestart.cfg and 1cescmn.cfg configuration files: AutoUninstall, AutoUninstallVersionsAfter, DontUninstallVersion.

This feature was not provided.

Previously you had to delete unused versions manually or write batch files to delete them.

Simplified system administration in terms of deleting 1C:Enterprise versions that you no longer use.
Web client.
When you perform some long-running operations in the web client, the mouse cursor switches from the main mode to "busy".In the web client, the cursor was always in the main mode.The web client is now more user-friendly.
Configuration extensions.
Spreadsheet documents.
Now it is faster to receive a template that was extended with multiple configuration extensions for the first time. The extended template is cached for further use.

The cache is stored until you change the template to be extended or the extension that contains an improvement for this template.

Previously, the first receipt of a template extended with multiple configuration extensions took more time.Templates that are extended with multiple configuration extensions are now faster and easier to use.
Collaboration system.
Upgrade: identification and display of the speaker in the videoconference window is updated. Speaker display and videoconference window behavior in various client applications are unified.Previously, speaker identification and videoconference window display were different and varied in different client applications.Improved videoconference window interface. It became easier to understand what user is talking or transmitting noise through the microphone at the moment.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Database copies.
Initial population of a database copy for metadata objects with tables is now faster.Initial population of a database copy for metadata objects with tables took more time.Initial population of a database copy for metadata objects with tables is now faster.
Server clusters.
Server cluster computers (network, RAM, and CPUs) have become less loaded when there are many users. The server cluster is now more stable.When there were many users, the server cluster consumed more RAM, CPUs, and network connections.Improved server cluster stability in configurations with a large number of users.
Server clusters.
Administration tools.
Optimized logical and referential integrity check in client/server mode when verifying and repairing infobases.

New parameter for the /IBCheckAndRepair command of Designer batch mode: -JobsCount. It identifies the number of system background jobs used for infobase verification and repair.

Infobase was verified and repaired sequentially by infobase tables.Infobase verification and repair now take less time.
Collaboration system.
Improved sound quality during video calls.Sound quality during video calls was worse.Improved sound quality during video calls.
Full-text search.
Improved relevance of full-text search results.

For this upgrade to take effect, clear the full-text search index and recreate it on platform version 8.3.24.

1C:Enterprise platform versions 8.3.23 and earlier will clear the index if it was built by platform version 8.3.24.

Previously, full-text search returned results ordered by a set of criteria that ensured low result relevance.Improved relevance of full-text search results.
Full-text search.
Data indexing by full-text search now takes less time. The size of intermediate files used for indexing is reduced.Data indexing for full-text search took more time and required more space for temporary files used for indexing.Data indexing for full-text search takes less time.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
DBMS operations.
Now you can terminate unnecessary sessions of a user and continue the current session after user authentication. You can do it if there are other sessions of this user in this infobase after authentication and you cannot start a new session without closing them.

This feature is implemented after authentication is fully completed in the following situations:

  • An error occurred when establishing exclusive access to an infobase or a data area.
  • There are not enough client licenses.
  • Starting a session is denied by the external session management service.
This feature was not provided.Simplified solution of issues that arise during user authentication when limiting the number of sessions after an unnecessary application freezes, crashes, or is unavailable.
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.17.The format version of configuration dump to XML files was 2.16.Configuration dump to XML files supports new platform features.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Linux.
1C:Enterprise installer for Linux is supplied in a zip archive. The archive includes the installAsRoot application, which allows you to easily perform installation on behalf of the superuser (root).

During the installation, an attempt is made to install all the Linux components necessary for the platform to run. If the attempt fails, the batch manager message is displayed as an error message.

During the installation, only one shortcut to the interactive launcher is created. To create other shortcuts, use the Create shortcuts launcher option or the desktops_icons parameter of the batch system installation.

During the installation, a platform uninstaller shortcut is created.

Shortcut names created by the installer became shorter and better reflect the actions the shortcuts perform. Shortcut names are now displayed in several lines.

Previously it was more complicated to install 1C:Enterprise on Linux.

The installer did not attempt to install the Linux components necessary for the system to run.

Error messages displayed during the installation were not clear enough.

Simplified installation, startup, and uninstallation of 1C:Enterprise on a computer running Linux.
Standalone server.
During database configuration update, the standalone server outputs the ID of the new infobase generation to the standard output stream.

New feature: mode of partial import of external properties for selective metadata object import from xml files. In this mode, you do not need to import metadata objects these properties belong to. You can also import form modules without importing the forms. New partial parameter for the following commands:

  • config load-config-from-files command of the Designer agent and the SSH gateway of the standalone server.
  • /LoadConfigFromFiles command of Designer batch mode.
  • infobase config import command of the standalone server management utility (ibcmd).
This feature was not provided.Database configuration update by a standalone server is now faster in some scenarios.
Navigation links.
URLs generated with the GetInfoBaseURL() method in the URL receipt dialog box with the selected External link checkbox contain separators that you can use in the current session of the separated infobase. If you receive a link in the web client or thin client connected via the web server, the URL will contain separators that do not generate the infobase address. You can specify the separators similarly to the Z command-line option of the client application startup.

When you start the client application with the URL parameter, the application searches for the client application based on the separator values specified in the URL. Similar actions are performed when you follow an external URL from the Go to link dialog box, from the global search string, and using the GoToURL() method.

This change is not implemented in version 8.3.23 compatibility mode.

URLs generated with the GetInfoBaseURL() method in the URL receipt dialog box with the selected External link checkbox did not contain values of the current session separators for the separated infobase.When you follow an external URL generated in a separated infobase, the values of the separators that were used in the session where the URL was received are considered. You will open objects in the same data area where you received the URL.
Dynamic lists.
Now you can exclude fields that are of the flexible type and contain more than 100 types from the list of dynamic list fields that can be used to order the list.

This upgrade is ignored in 8.3.23 version compatibility mode.

The list of fields that you can use to order a dynamic list was not limited by the size of the flexible type of a dynamic list field.Now when you configure a dynamic list, you are less likely to create a sorting that will slow down the dynamic list operation or lead to the list malfunction. It can happen due to a DBMS error that occurs when you try to display the list.
Data display.
Client application form.
Spreadsheet document.
Spreadsheet documents now support a formatted string in cells and pictures. You can export such spreadsheet documents to the following formats:
  • Microsoft Office OpenXML (Microsoft Word 2007 and later) and HTML in full.
  • Microsoft Office OpenXML Spreadsheet (Microsoft Excel 2007 and later), OpenDocument Spreadsheet (*.ods), and PDF with some limitations:
    • Exporting pictures and hyperlinks embedded in formatted strings is not supported.
    • Background color export is not supported.
    • Font color export to XLS (Microsoft Excel 95-2003) is not supported.

In the spreadsheet document editor, you can switch between a regular and formatted string. You can edit a formatted string.

New event for a spreadsheet document field: URLProcessing.

The Text property of the SpreadsheetDocumentRange and SpreadsheetDocumentDrawing objects can be of the String or FormattedString type.

The mobile platform does not support the formatted string.

This feature was not provided.Now you can improve spreadsheet document appearance.
Configuration repositories.
Now you can set up the configuration repository so that it is required to specify a password when creating a user.

The repository creation assistant now has a page with password requirements: minimum password length and password complexity check. You can edit these parameters in the repository administration dialog box. If you specify the minimum password length as 0, it will be possible to create users without entering a password.

In the repository user list, you can see a column with all user passwords.

New parameters for the /ConfigurationRepositoryCreate command of Designer batch mode: -MinPasswordLength and -CheckPasswordComplexity.

New parameters for the global cfgrepo.conf settings file of the configuration repository: cfgrepo.users.minPasswordLength and cfgrepo.users.checkPasswordComplexity.

It is recommended that administrators of configuration repositories analyze user lists in repositories they administer and set passwords for all users.

You were unable to set up the configuration repository so that it required a password when creating a user.Now it is less likely that any repository user without a password changes the configuration located in the repository.
Data history.
Changes made in the OnWrite() event handlers are not included in a data version to save.A data version that was saved to the history included changes made in the OnWrite() event handlers.Eliminated unexpected system behavior.
Cryptography support.
Now it is easier to initialize the cryptography manager. You can use the cryptography manager wizard where you need to select only the interactive mode. Parameters for each operation are identified by the operation context.

Now you can specify encryption, hash, and signature algorithms that you will use to perform an operation using the OID algorithm. You can still specify algorithms by naming them but OID is better for clear identification.

Now you can set the priority for hash and encryption algorithms. New properties for the cryptography manager: HashAlgorithmDefinition and EncryptAlgorithmDefinition.

Now you can receive certificates not only from encrypted or signed data but also from an arbitrary certificate storage. New methods for the cryptography manager: GetCertificates() and GetCertificatesAsync(). Do not use the following methods as they are outdated: GetCertificatesFromSignature(), GetCertificatesFromSignatureAsync(), and BeginGettingCertificatesFromSignature().

Now you can search for a key container for the used certificate on the local computer. New methods for the cryptography manager: FindKeyContainer() and FindKeyContainerAsync().

Now you can specify a certificate and an access password to the private key that can be used to decrypt data. New parameters for the Decrypt(), DecryptAsync(), and BeginDecrypting() methods: Certificate and PrivateKeyAccessPassword.

New property: CryptoModuleInformation.CryptoModuleType.

Previously, you had to specify a cryptography module name, type, and path when initializing the cryptography manager.

You were able to specify algorithms used for an operation only by the name.

You were unable to specify the priority for hash and encryption algorithms. Algorithms specified in the cryptography manager methods could be ignored when performing an operation.

You were unable to receive a list of certificates from encrypted data. You were able to receive the list only from the data signature (the GetCertificatesFromSignature(), GetCertificatesFromSignatureAsync(), and BeginGettingCertificatesFromSignature() cryptography manager methods).

You were unable to check whether there was a key container for the used certificate on the computer.

When you decrypted data, you could specify only one recipient of decrypted data.

Simplified operations with the cryptography manager in main scenarios.
Standalone server.
Removed the following standalone server parameters:
  • The --debug-server-password parameter of the ibsrvr utility.
  • The password parameter of the debug - server section of the standalone server configuration file.

If you specify the deleted parameters, it will not cause an error. The parameters are ignored.

Previously the standalone server parameters mistakenly specified that users could set a password to access the debug server on the standalone server. The specified password was never used.Eliminated the error in the standalone server parameters.

Table of contents

Renamed objects

ObjectThe old nameThe new name
English name of the NotifyDescription parameter in 1C:Enterprise language methods.
  • NotifyDescription.
  • CallbackDescription.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile application builder.
Now compatibility mode processing in the mobile platform corresponds to the similar platform behavior on a personal computer.

Designer exports information about the configuration compatibility mode to the 1cema.xml and 1cemca.xml files.

The mobile application builder considers the compatibility mode when building mobile applications. If the configuration compatibility mode does not correspond to the mobile version used to build the mobile application, the build will be completed with errors.

Previously, the compatibility mode depended on the version of the mobile platform where you initially created the infobase or updated the configuration.

The mobile application builder did not check the compatibility mode between the configuration and the mobile platform used to build the mobile application.

Eliminated unexpected system behavior.
Mobile platform.
Mobile client.
Mobile platform and mobile client with standalone mode now support type collections.This feature was not provided.Advanced 1C:Enterprise mobile platform features.
Mobile platform.
Mobile client.
Mobile device-specific features.
The mobile platform and the platform for a personal computer are now available on the server for the following objects: MultimediaData, DocumentScanningQualityParameters, and DocumentScanningPage.This feature was not provided.Simplified operations with documents that are scanned not to be sent to the recognition service but to be saved to the infobase.
Mobile platform.
Mobile client.
Mobile application builder.
Mobile device-specific features.
Now the mobile version of 1C:Enterprise supports Huawei Mobile Services (HMS). You can use the map and get an address by coordinates and vice versa, use geolocation zones, notifications, ads, and in-app purchases.

New system enumeration value: DeliverableNotificationSubscriberType.HPK. New parameter for the GetAccessToken() method of the manager for sending deliverable notifications: SubscriberType. The method contains three parameters now. The GetAccessToken() method with two parameters is now outdated.

New system enumeration value: InAppPurchaseService.HuaweiInAppPurchase.

In the mobile application builder, you can now specify which services the built mobile application will support (including the ability to disable both services). If both service sets are used on a mobile device, the Google service set has the priority (you cannot set the priority). Now you can disable both service sets if the built application does not use the mobile service features (the built application size will decrease). You cannot publish the built application to the Huawei AppGallery store from the mobile application builder.

Previously, Huawei Mobile Services (HMS) were not supported in the mobile version of 1C:Enterprise. You were unable to use the full mobile version capabilities on Huawei devices.More mobile services are now supported.
Mobile client.
Speech recognition.
Now you can use speech recognition in the mobile client (including in standalone mode). Speech recognition is not supported on mobile devices. Server methods of speech recognition are not supported in the mobile application server and the mobile standalone server.

New functionality: SpeechToText. If this functionality is not required in the application you build, an attempt to access the speech recognition tools in the built application will cause a runtime exception.

Speech recognition was not supported in the mobile client.Advanced 1C:Enterprise mobile client features.
Mobile platform.
Mobile client.
System requirements.
The mobile version of 1C:Enterprise now supports Android 13. The mobile version of 1C:Enterprise no longer supports Android 4.4. The mobile version of 1C:Enterprise supports Android versions 5.0 - 13.

To upload a mobile application to the Google Play store, build a mobile application using the mobile version 8.3.24.40 or later.

When you run a mobile application on Android 13 and later versions:

  • The Notification position permission will be used. The permission describes why the user needs notifications in the mobile device shade. This permission is used when geofences, notifications, video calls, and audio recording are applied.
  • To access the audio library and the picture and video library, install the appropriate functionality similar to iOS. If you use the previous Android versions, the Audio playback and vibration functionality will be used.
Previously the mobile 1C:Enterprise version supported Android versions 4.4-12.

After November 1, 2023, you will not be able to upload mobile applications built using mobile versions earlier than version 8.3.24.40 to the Google Play store.

Now the mobile 1C:Enterprise version supports the latest Android versions.
Mobile device-specific features.
The mobile application no longer requires a user permission to access the application document directory.

If the Access to all files functionality is disabled, you will see a message that the required functionality is disabled when you try to access files outside the data directory.

New functionality: Geofences. It manages operations with geofences.

When you started an application for the first time, the system requested access to the application's document directory.

When you tried to access a file outside the application's document directory, a file access error was generated.

Operations with geofences depended on the Geolocation in background functionality.

Eliminated unexpected system behavior.

The collaboration system behavior is more logical.

Mobile platform.
Mobile client.
Mobile device-specific features.
On the mobile version, you can get files that the user shared from other applications on a mobile device. When you set up the feature, you can specify that the mobile application will process some specific file extensions or all extensions.

New global context property: LaunchShareRequestData. New event handler of the application module: IncomingShareRequestCommandGenerateProcessing(). New properties for the MobileApplicationFunctionalities system enumeration: IncomingShareRequests and AllIncomingShareRequestsTypesProcessing.

This feature was not provided.In a 1C:Enterprise-based mobile application, you can now receive files that were shared from other applications using a standard feature of the respective mobile operating system.

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
1C:Enterprise script.
If the Find() table method cannot find the search string and the list of search columns has only a LineNumber column, the search in other columns is not executed.

Analyze the method and eliminate possible unexpected behavior.

This upgrade is ignored in 8.3.23 version compatibility mode.

If the Find() table method could not find the search string and the list of search columns had only a LineNumber column, the search was executed in all table columns.Eliminated unexpected system behavior.
Spreadsheet document.
New feature: when you fill a spreadsheet document, formatted strings in cells with the Template fill type are supported.

When you replace a parameter name with an actual value, the formatting of the resulting text is determined by the first character of the parameter name, and pictures and links inside the parameter name are deleted. Other operations with templates do not change.

When you filled a spreadsheet document, formatted strings in cells with the Template fill type were not supported.Expanded support for formatted strings in a spreadsheet document.
Client application installation.
Now you can specify the automatic bitness option of the client application to be started in the settings of the dialog box of client application startup and infobase parameters on Windows.

If a 32-bit application is running for the infobase, the distribution package of the 32-bit application will be downloaded upon automatic client application update.

Previously, when a client application was automatically updated, an application whose bitness matched the used operating system bitness was downloaded. The bitness of the running client application was ignored during the update.Simplified automatic client application update when a 32-bit client application is used on 64-bit Windows (for example, because the client application uses add-ins that exist only in the 32-bit version).
Development tools.
To copy breakpoint settings to the clipboard, press Ctrl+Alt+K.

In previous platform versions, pressing Ctrl+Alt+C opened the call stack window.

Pressing Ctrl+Alt+C copied breakpoint settings to the clipboard.Eliminated unexpected system behavior.
Mobile application builder.
Now you can export keys associated with the Google Play and Huawei AppGallery application stores in the mobile application builder. The feature is implemented as a dialog box that you can call from the dialog box for editing provider parameters and from the dialog box for editing a mobile application group.

The following information is exported:

  • Application's private signature key (for Google Play, specify the encryption key from the developer console of the application store).
  • Private key and the application signature certificate (for both stores).
  • Certificate of the application upload key (for both stores).
Previously, you could only export keys for the Google Play store in a format that was no longer supported by the store.You can continue using the Google Play store as the store changed the encryption procedure of the signature key.

You can upload AAB files to the Huawei AppGallery application store.

Standard functions.
Mobile 1C:Enterprise version 8.3.24 is now supported in the mobile application builder. Now you can use the builder to build Android-based mobile applications that use Huawei mobile services.These features were not provided.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
Collaboration system.
New features for the external user website and the chat on the website:
  • Continue your video call on another device.
  • Automatic reconnection in a video call when the connection is lost or deteriorated.

Improved the video call interface.

These features were not provided.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
DBMS operations.
System requirements.
The system now supports Postgres Pro DBMS version 11.22.1 of the following products:
  • Postgres Pro 1C
  • Postgres Pro Standard
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.17 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Postgres Pro DBMS version 12.17.1 of the following products:
  • Postgres Pro 1C
  • Postgres Pro Standard
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Postgres Pro DBMS version 13.13.1 of the following products:
  • Postgres Pro 1C
  • Postgres Pro Standard
  • Postgres Pro Enterprise
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Postgres Pro DBMS version 14.10.1 of the following products:
  • Postgres Pro 1C
  • Postgres Pro Standard
  • Postgres Pro Enterprise
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Postgres Pro DBMS version 15.5.1 of the following products:
  • Postgres Pro 1C
  • Postgres Pro Standard
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
Data composition system.
The time required to open the data composition schema is reduced if there are many predefined items in the chart of calculation types.Previously, opening the data composition schema took a long time if there were many predefined items in the chart of calculation types.Eliminated unexpected system behavior.
Linux.
New feature: the WebKit2 library is used to manage HTML objects in Linux client applications. The WebKit2 library is not included in the platform. Instead, a library included in the used operating system is used. The evince library is used to preview HTML document fields. If the libraries are not installed, they will be installed from the repositories of the used operating system during the 1C:Enterprise installation.

The WebKit1 library is no longer used and is not included in 1C:Enterprise.

Previously, the WebKit1 library included in the 1C:Enterprise distribution package was used to manage HTML objects in Linux client applications.A more modern library is used to manage HTML objects.
Analytics system.
Analytics - sources.
Now you can manage the report execution location when building the report, similar to the 1C:Enterprise Request object. You can set up the following parameters: Database copy usage, Data relevance, and Relevance time.This feature was not provided.Advanced management of report execution location in 1C:Analytics client application.
Configuration extensions.
Now you can access the configuration extension management form in Designer of the base version of 1C:Enterprise (Main menu - Configuration - Configuration extensions). This form contains interactive extension administration functions. Extensions that can be applied to the base configuration must be signed with the same key as the base configuration. The extension editing functions remain unavailable. You can view the applied extension.This feature was not provided.

Previously, you could apply and disable extensions only using Designer batch mode.

Advanced administration features of base 1C:Enterprise version.
Add-ins.
New global context method: CreateAddInObjectAsync(). It allows asynchronous creation of add-in objects.This feature was not provided.

Previously, you could create add-in objects on the client only using a synchronous constructor. This could lead to errors when using the add-in.

Reduced probability of error if an add-in method is called immediately after creating this add-in object. Eliminated unexpected system behavior.
Database configuration update.
While restructuring the infobase, eliminated deletion of trailing space characters (the Mark, spacing combining character category of the Unicode standard) if the attribute type was not changed upon restructuring. When converting a fixed-length string to a variable-length string, spaces to the right up to the first character other than a space are removed upon restructuring.Previously, when restructuring the infobase,trailing space characters (the Mark, spacing combining character category of the Unicode standard) were cut off. When converting a fixed-length string to a variable-length string, not only trailing spaces, but also trailing space characters were removed upon restructuring.Eliminated unexpected system behavior.
Mobile platform.
Mobile client.
System requirements.
The following mobile operating systems are supported:
  • for Android: version 14,
  • for iOS: versions 15 - 17.
Previously, the following mobile operating systems were supported:
  • for Android: versions 5 - 13,
  • for iOS: versions 9 - 14.
Extended list of supported mobile operating systems.
System requirements.
Linux.
The following Linux distribution packages are supported:
  • ALT SP 10,
  • Debian 12.
The distribution packages were not supported.Extended list of supported mobile operating systems.
System requirements.
Linux.
The following Linux distribution packages are no longer supported:
  • Mint 19,
  • Ubuntu 18.04 LTS,
  • ALT Education 9,
  • ALT Workstation 9,
  • ALT Workstation K9,
  • ALT Server 9.
Previously, 1C:Enterprise supported the following Linux distribution packages:
  • Mint 19,
  • Ubuntu 18.04 LTS,
  • ALT Education 9,
  • ALT Workstation 9,
  • ALT Workstation K9,
  • ALT Server 9.
Outdated Linux distribution packages are no longer supported.
Licensing system.
New service addresses to activate the software license using the file. The platform uses new service addresses. Previous service versions are planned to be disabled.

The service address has the following format: https://portal.1c.ru/support/license/license-from-file?lang=LL or https://portal.1c.eu/support/license/license-from-file?lang=LL (depending on the current settings and the system version), where LL is a two-letter localization language code of the running 1C:Enterprise instance.

Previously, to activate the software license using a file, a service located at https://users.v8.1c.ru/lc was used.A more modern service is used to activate the license using a file.
Internet-enabled functionality.
Now you can specify a timeout with 0.01 second accuracy for the HTTPConnection, FTPConnection, and WSProxy objects.Previously, a timeout specified as a fractional number was rounded up to the nearest integer number of seconds for the HTTPConnection, FTPConnection, and WSProxy objects.You can specify operation timeouts more accurately for Internet services.
Cryptography support.
Now you can generate an attached digital signature of the file.

1C:Enterprise supports multiple document signatures. The check is performed not only for the first signature, but for all digital signatures of the file.

You can add and delete certificates to the store of root certificates and intermediate certificate authority certificates.

When adding an archived timestamp, the ats-hash-index-v3 attribute is added.

New property for the cryptography manager: IncludeDataInSignature. New methods for the cryptography manager: CheckForDataInSignature(), CheckForDataInSignatureAsync(), GetDataFromSignature(), and GetDataFromSignatureAsync(). Now you can use an attached digital signature in the VerifySignature() and VerifySignatureAsync() methods. New property: CryptoSignature.Data.

Previously, 1C:Enterprise supported only detached digital file signature.

When checking a digital signature, only the first digital signature was checked.

You could not add and delete certificates to the store of root certificates and intermediate certificate authority certificates.

When adding an archived timestamp, the ats-hash-index attribute was not added.

Advanced cryptography features.
DBMS operations.
System requirements.
The system now supports Tantor SE 1C DBMS version 15.6.1.

Supported processors: ARM64 and x86-64.

Supported operating systems are defined by a DBMS vendor.

This Tantor SE DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
Infobase verification and repair.
This feature is canceled.

Now, when verifying and repairing an infobase, you can detect and delete empty tables of initialized predefined data in the Check logical infobase integrity mode.

This feature was not provided.Minimized the number of non-informative errors when using a separated infobase.
DBMS operations.
Upgrade: improved IN() query operator performance when using the PostgreSQL DBMS (and inherited DBMS) if 1C:Enterprise generates the query.When using the PostgreSQL DBMS (and inherited DBMS), queries with the IN() operator generated by 1C:Enterprise took more time.Improved performance of queries generated by 1C:Enterprise when using PostgreSQL DBMS (and inherited DBMS) if the queries use the list of values for a table filter (the IN() query language operator).
Mobile client.
If it is necessary to change the user password in mobile client versions that do not support password change, a correct message describing the current situation is displayed. The message also contains the actions that the user needs to perform.In mobile client versions that did not support changing the user password, the message about the need to change the user password was unclear and did not describe the situation.The mobile client behavior is more user-friendly.
Infobase users.
The email sent to the user by the standard password recovery service clearly indicates that the password for signing in to the 1C:Enterprise application is being restored.Previously, the email sent to the user by the standard password recovery service did not clearly indicate that the password for signing in to the 1C:Enterprise application is being restored.When reading the email, the user understands what password they restore.
macOS.
System requirements.
macOS version 15 is supported.Previously, 1C:Enterprise did not support macOS versions 15.Extended list of supported operating systems.
Linux.
System requirements.
The following Linux distribution packages are now supported:
  • For the x86 and x86-64 architectures:
    • Astra Linux Special Edition 1.8 (with generic kernel only)
    • Mint 22
    • Simply Linux 10
    • Ubuntu 24.04 LTS
    • RED OS
  • For the ARM64 architecture:
    • Astra Linux Special Edition 1.8 (with generic kernel only)
    • Simply Linux 10
    • Ubuntu 24.04 LTS
The distribution packages were not supported.Extended list of supported Linux distribution packages.
Data accelerator.
System requirements.
The list of Linux distribution packages that support Data Accelerator has been changed. The following distribution package versions are supported:
  • Astra Linux Common Edition 2.12
  • Astra Linux Special Edition 1.6 - 1.8 (only generic kernel)
  • CentOS 7
  • Debian 10 - 12
  • Mint 20 - 22
  • Oracle Linux 7 - 9
  • Red Hat Enterprise Linux 7 - 9
  • Simply Linux 10
  • Ubuntu 20.04 LTS
  • Ubuntu 22.04 LTS
  • Ubuntu 24.04 LTS
  • ALT 8 SP
  • ALT Education 10
  • ALT Workstation 10
  • ALT Workstation K 10
  • ALT Server 10
  • ALT 10 SP
  • RED OS 7.3 MUROM
  • RED OS 8
Previously, the following set of Linux distribution packages was supported for Data Accelerator:
  • CentOS 6 and later
  • Red Hat Enterprise Linux 7 or later
  • Fedora 20 or later
  • Debian GNU/Linux 8 or later
  • Ubuntu 14.04 or later
Updated the list of supported Linux distribution packages.
Distributed infobases.
New feature: information about configuration objects that change the infobase structure without compatibility mode or changing the configuration format version is now recorded in the data exchange message of the distributed infobase. This information will allow the receiving party to determine whether the exchange message can be imported to the infobase without issues or not. If it is impossible, the message will be rejected, and you will need to update the platform to import the message. +The 1C:Enterprise platform that does not support this change will not be able to import such data exchange message. The message will also not be imported if the platform does not support configuration objects whose information is recorded in the exchange message.This feature was not provided. As a result, any exchange message could be imported using any platform, and, when updating the database, changes could occur leading to the destruction of the infobase in the receiving node of the distributed infobase.Improved reliability of a distributed infobase as the platform does not allow importing exchange messages that can destroy the infobase.

Table of contents

Transition from the previous version to the version 8.3.24

Table of contents

Version 8.3.23

Version 8.3.23 includes known bug fixes and functionality modifications. +

The standalone server graduated out of beta.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
New value for the Compatibility mode configuration property: Version 8.3.22.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1 - 8.3.21 was available. +You can run configurations developed in versions 8.3.22 and earlier in version 8.3.23 without changing the configuration and data structures. This way, you can migrate to version 8.3.23 without changing the configuration, then make required changes, and disable compatibility mode. You can also use version 8.3.22 after migration to version 8.3.23. You can do it both before you disable compatibility mode and after you enable it again. +
Development tools.
New 1C:Enterprise license type: for developers. This license type has the following features:
  • It allows using the client application and the server cluster.
  • It is exclusively a software license.
  • It can be attached only to computer parameters.
  • If several licenses of this type are activated for one profile at the same time, they still have the same restriction parameters as one license.
  • It is time-restricted.
  • It does not limit quantitative characteristics of the configuration and the database.
  • To get this license, you need to register on the Read more. developer portal.

Detailed developer license features and restrictions are described in the respective documentation.

New properties for the LicenseAcquisitionRequest object: AccountName and AccountPassword. New methods for the license acquisition manager: GetDeveloperLicenseUsageAvailability() and GetDeveloperLicenseAgreement().

This feature was not provided.

The training version was used for practice.

The developer package or any other main distribution package were required for development.

1C:Enterprise version with full functionality can be used free of charge for training and development.
DBMS operations.
Administration tools.
Standard functions.
You can now manage database tablespaces in client/server infobase mode. You can manage tablespaces for indexes and data. Separation of tables by namespaces is unique for each infobase and is not preserved when you export an infobase. Tablespace management is not supported in file infobases and Data Accelerator.

New standard function available in server infobases starting from Version 8.3.7 compatibility mode: Database tablespace management.

New global context property: DatabaseTablespaces.

New parameter for the IBCheckAndRepair command-line option of Designer batch mode: RefreshTableLocation.

New columns for the value table returned by the GetDBStorageStructureInfo() method: DataStorageTablespace and IndexStorageTablespace.

New configuration property: Tablespace usage mode.

Database tablespace management is supported for CORP licenses.

This feature was not provided.Advanced infobase administration features in client/server mode. Now you can assign infobase tables to various disk drives based on table load profiles.
1C:Enterprise script.
JSON support.
New global context methods: WriteJSONValue() and ReadJSONValue(). The methods are available in any context. They serialize and deserialize a certain data type set to a JSON string and back to 1C:Enterprise language objects.This feature was not provided.

The new methods could be implemented using existing JSON tools. However, this generally required a server call.

Simplified operations with JSON format, especially in web client and on mobile devices.
Collaboration system.
You can exchange files with Telegram and VK if the collaboration system is integrated with them. Video file exchange with VK is not supported.

To store exchanged files, you can configure your own storage on the collaboration server.

This feature was not provided.

+

Advanced features for integration with instant messaging systems.
Standalone server.
Administration tools.
You can convert a server infobase into an infobase maintained by another DBMS without exporting it to a dt file and importing to a new DBMS. Conversion from file infobases is not supported.

New command for the "infobase" command of the ibcmd utility: replicate.

This feature was not provided.

The only way to change an active DBMS was infobase export to a dt file with its further import from this file to a new DBMS.

+

Simplified server infobase migration between various database management systems.
1C:Enterprise script.
ICU regular expressions can be used in 1C:Enterprise language. Operations with regular expressions are available only on 1C:Enterprise server.

New global context methods: StrFindByRegularExpression(), StrReplaceByRegularExpression(), StrLikeByRegularExpression(), and

StrFindAllByRegularExpression().

This feature was not provided.Advanced search in strings using 1C:Enterprise language.
Collaboration system.
You can integrate the collaboration system with the WhatsApp instant messaging system.

New property: CollaborationSystemIntegration.EnabledMessageEdit

New methods for the collaboration system manager: GetAnswerAvailabilityEndTime(), GetAnswerAvailabilityEndTimeAsync(), GetMessageTemplates(), GetMessageTemplatesAsync(), GetMessageTemplate(), GetMessageTemplateAsync(), SetMessageTemplatePresentations(), and SetMessageTemplatePresentationsAsync().

New properties for the CollaborationSystemMessage object: MessageTemplate and MessageTemplatePlaceholderValues.

New application module event: CollaborationSystemMessageTemplateChoiceProcessing.

This feature was not provided.Advanced features for collaboration system integration with instant messaging systems.
Collaboration system.
The standard data processor of collaboration system management displays information on parameters of the collaboration system where the infobase is registered and the subscriber email address.

New methods for the collaboration system manager: ServerAddress(), ServerVersion(), SubscriberEmail(), and CurrentUserIsSubscriberAdministrator().

+

+

This feature was not provided.Access to information about the collaboration system to which the current infobase is connected.
Configuration extensions.
You can create your own scheduled jobs in a configuration extension.This feature was not provided.Advanced configuration extension features.
DBMS operations.
Microsoft OLE DB Driver for SQL Server can be used in client/server infobase mode to ensure Microsoft SQL Server DBMS operation.Microsoft OLE DB Driver for SQL Server was not supported in client/server infobase mode to ensure Microsoft SQL Server DBMS operation. Only Microsoft SQL Server Native Client was supported.Extended list of supported access tools for Microsoft SQL Server DBMS.
Standalone server.
New standalone server features:
  • Establish direct TCP connection to the infobase in managed applications.
  • Use Designer.
  • Use a standalone server as a test manager.
  • Debug applications using a built-in debug server.
These features were not provided.

Application debugging was supported only when the debug server was deployed separately from the standalone server.

Advanced standalone server features.
Standalone server.
You can enable and disable standalone server features in the new "features" section of the configuration file. You can also use the following ibsrv utility command-line options:
  • --enable-extended-designer-features, --disable-extended-designer-features. Enables or disables advanced configuration features in the standalone server.
  • --enable-http-gate, --disable-http-gate. Enables or disables infobase access over HTTP.
  • --enable-ssh-gate, --disable-ssh-gate. Enables or disables the SSH gateway of the standalone server in agent mode.
  • --enable-direct-gate, --disable-direct-gate. Enables or disables infobase access over TCP.
These features were not provided.

All standalone server features were always available.

Advanced standalone server management features. You can now disable unused standalone server features.
Standalone server.
New standalone server features:
  • mobile-app export mode. Save the mobile application configuration. Available only after advanced configuration features are enabled.
  • mobile-client mode:
    • export. Save the mobile client configuration. Available only after advanced configuration features are enabled.
    • sign. Digitally sign the configuration.
  • config mode. Shortened version of the infobase config command.
  • extension mode. Shortened version of the infobase config extension command.
  • infobase config export. Export an external data processor, report or extension to an XML file.
  • infobase config import. Import an external data processor, report, or extension from an XML file.
These features were not provided.Advanced standalone server features.

+

Standalone server.
New commands for the SSH gateway of the standalone server:
  • config mobile-app-write-file. Save the mobile application configuration.
  • config mobile-client-write-file. Save the mobile client configuration.
  • config sign-cfg. Digitally sign the configuration.
  • config mobile-client-digi-sign. Digitally sign the mobile client configuration.

+

These features were not provided.Advanced standalone server features.
Collaboration system.
You can embed the collaboration system chat into third-party websites. New feature: API that allows the website to manage the chat.

New integration type: collaboration system web chat.

New events for the bot module: OnCreateCollaborationSystemConversation, OnAddToCollaborationSystemConversation, and OnDeleteFromCollaborationSystemConversation.

New properties: CollaborationSystemGenerateCommandParameters.User, CollaborationSystemUser.Alias, CollaborationSystemIntegration.VideoconferencesAvailable, CollaborationSystemStandardCommand.ShowUserInfo, and CollaborationSystemCommandSource.User.

New method for the Color and Font types: GetAbsolute().

New feature that allows the website to interact with the web chat: Collaboration System WebChat API.

+

This feature was not provided.Advanced collaboration system features.
Technological log.
The technological log can output the list of session data modification operations with their contexts to the Context property of the CALL events for the seanceParametersCommit and finishSeance cluster manager methods (rmngr).

This feature is managed by the <sessiondatacontext> item of the logcfg.xml configuration file of the technological log.

Since this feature slows down the system, enable it only when you investigate issues related to the size of session data storage of a server cluster.

This feature was not provided.Simplified investigation of issues related to the size of session data storage of a server cluster.
Speech recognition.
Implemented speech recognition in 1C:Enterprise platform. You can use it both in stream mode and from Ogg files. Speech recognition can be applied locally (on a user computer without Internet connection) or via 1C cloud service.

New global context property: SpeechProcessing.

New standard data processor: Manage speech recognition.

New technological log events: <STTAdm> and <STT>.

New system enumeration property: ErrorCategory.SpeechProcessingError.

New command of the client application startup command-line: /DisableLocalSpeechToText.

New 1C:Enterprise server cluster services: Speech recognition service and Speech recognition model management service.

New production server feature: change location of the directory with speech recognition models using the Speech recognition model directory property of the cluster console production server.

New parameter for the conf.cfg file: SpeechToTextModelLocation.

Speech recognition state is now displayed in the client application interface.

Speech recognition is not supported:

  • In the web client in Mozilla Firefox, Safari, Google Chrome, and Chromium-based web browsers version 66 and earlier.
  • In the web client that is accessible over HTTP and whose publishing host is not localhost.
  • On the standalone server.
  • In the training 1C:Enterprise version.
  • On Microsoft Windows XP or Microsoft Windows Server 200
  • In local mode if the used file infobase is running on:
    • macOS.
    • ARM processor.
  • If the infobase is created in version 8.1 compatibility mode.
This feature was not provided.Available speech recognition in applications based on 1C:Enterprise. Specifically, voice control of the application or text input by voice dialing.
Binary data storage.
New feature: binary data storage. Use it to store binary data in the computer file system of 1C:Enterprise server cluster instead of an infobase. The storage does not affect the way data reading and writing operations are defined by developers: the application considers that such operations are performed from applied object attributes.

The storage is supported only in client/server mode. The binary data storage is not supported on a standalone server and in a file infobase. You can manage the storage with the API developed in 1C:Enterprise language.

New global context property: BinaryDataStorage. New 1C:Enterprise server cluster service: Binary data storage service. New standard data processor: Binary data storage management. New technological log event: <STORE>.

Now you can check the binary data storage integrity:

  • New item in the Verify and repair dialog box: Binary data storage integrity check.
  • New parameter for the /IBCheckAndRepair command-line option of Designer batch mode: -BinaryDataStorageIntegrity.

The feature requires a CORP license.

The feature is currently in beta status. To use the binary data storage, you need a testing license. Without it, the feature is unavailable.

This feature was not provided.New feature: if an infobase contains a large quantity of binary data, you can manage the database size and performance of binary data operations using the binary data storage.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Client application.
The following user settings are automatically saved in the client application every 20 minutes:
  • Application window position and size
  • Table column width settings
  • Position of separators
User settings were saved only during regular client application shutdown.Reduced risk of losing configured settings in the client application.
Collaboration system.
You can switch the current video call to another device or another running application. If screen sharing is enabled at the moment of switching, it is disabled.This feature was not provided.Advanced features of collaboration system video calls.
Collaboration system.
Mobile client.
In case of network issues, the collaboration system attempts to restore connection during the call. The system attempts to restore connection until the client application is closed and the problematic video call is finished.In case of network issues, the collaboration system did not attempt to restore connection.Enhanced video call quality in case of poor communication channel quality.
Collaboration system.
Video call image quality now adapts to the current communication channel quality. Image quality can increase or decrease in direct correlation with the communication channel quality.In the collaboration system, video call image quality could only decrease if communication channel quality decreased. If communication channel quality increased, image quality was not restored.More flexible adaptation of video call image quality in relation to communication channel quality.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Configuration extensions.
When you start thin and web clients after updating one or several configuration extensions, the number of server requests and amount of transferred data is reduced.When you started thin and web clients after updating one or several configuration extensions, numerous requests were executed and a large amount of data was transferred.Faster start of thin and web clients after updating one or several extensions.
Database copies.
Initial database copy filling takes less time.Initial database copy filling took more time.Improved performance of initial database copy filling.
Server clusters.
Client application blackout is reduced or eliminated upon restart of the working process serving this client application.Upon restart of the working process serving the client application, this client application could be unavailable for a long time.Reduced or eliminated client application blackout upon restart of the working process serving this client application.
Collaboration system.
Connection established over PPP between video call participants is faster now.

Improved noise reduction when both video call participants are talking at the same time.

Improved screen sharing quality.

Connection established over PPP (time from receiving a call to conversation start) could take a very long time.

When both video call participants were talking at the same time, noise reduction quality was not good enough.

Screen sharing quality was not good enough.

Improved video stream performance in the collaboration system in the thick and thin client applications.
Data accelerator.
A sharp increase in RAM consumption by Data accelerator during some user queries is eliminated.A sharp increase in RAM consumption by Data accelerator was observed during some user queries.Reduced RAM consumption by Data accelerator in some cases.
Data accelerator.
Execution of queries with ordering to some tables takes less time.Execution of queries with ordering to some tables took more time.Improved performance of queries to some tables in Data accelerator.
Data accelerator.
In Data accelerator, stored text fields use less memory and their processing takes less time.In Data accelerator, stored text fields used more memory and their processing took more time.Faster operations with text fields in Data accelerator.
Data accelerator.
Operations with indexes set up in the configuration have been optimized in Data accelerator.Operations with indexes set up in the configuration were not optimized in Data accelerator.Improved performance of queries that use tables for which indexes are set up in the configuration.
Data accelerator.
At Data accelerator startup on Linux, the system checks that the "transparent hugepage" operating system core parameter is appropriately set for Data accelerator operation. This parameter must be set to "madwise" or "never".

If this parameter is set up incorrectly, Data accelerator is not started and respective diagnostic information is saved to the technological log.

The value of the "transparent hugepage" operating system core parameter was not checked at Data accelerator startup on Linux.Operating system settings check for optimal Data accelerator operation on Linux.
Data accelerator.
Some Data accelerator queries have been optimized.Execution of some Data accelerator queries took more time.Improved Data accelerator performance.
Data Accelerator.
Improved Data Accelerator stability in case of restrictions or insufficient memory during query execution. The improvement was achieved by changing query optimization algorithms, which might slightly slow down query execution in some cases.Previously, Data Accelerator could be unstable in case of restrictions or insufficient memory during query execution and aggressive query optimization.Improved Data Accelerator stability in case of restrictions or insufficient memory during query execution. The improvement was achieved by changing query optimization algorithms, which might slightly slow down query execution in some cases.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Administration tools.
User action logging is deprecated.

The /LogUI option of the client application startup command line is deprecated.

User action logging was supported in the client application.Outdated tools are no longer supported.
Administration tools.
Infobase verification and repair in client/server mode is always performed on the server.

Infobase verification and repair takes less time.

Infobase verification and repair in client/server mode was performed on the client in Designer.

Infobase verification and repair took more time.

Faster infobase verification and repair in client/server mode.
Configuration extensions.
The query wizard opened in the configuration extension supports operations configuration objects not included in the extension. If objects not included in the extension are used in a query, you are prompted to add all the missing configuration objects to the extension when the wizard is closed.

In the query wizard dialog box, you can manage the view of tables and fields in the extended configuration.

This feature was not provided.

The query wizard opened from the configuration extension allowed using only tables and fields of native and adopted extension objects.

Advanced configuration extension features.
Client application form.
You can save settings of the client application window. New client application form property available in the form editor: Save window settings.

New command: Restore size. To call this command, press Alt+Shift+R. This command restores not only window position and size, but also sets the position of separators and column size of all form tables to default values.

The "Restore window position" command is no longer available. Behavior of the "Restore sizes" command depends on how the form is opened.

+

This feature was not provided. Form settings were always saved regardless of whether the form developer needed it.You can save form settings.

The command to restore window position and size also restores the position of separators and the size of form table columns.

Cryptography support.
On Windows, the size of a file to be decrypted is no longer limited to 100 MB.On Windows, the size of a file to be decrypted was limited to 100 MB.Removed size restrictions for a file to be decrypted on Windows.
Client application.
In client applications and in Designer on macOS, Option and Cmd keys are displayed in keyboard shortcuts instead of Alt and Ctrl.In client applications and in Designer on macOS, keyboard specifics of Apple computers were not considered in displayed keyboard shortcuts.Keyboard shortcut representation is adjusted to macOS standards.
Development tools.
Client application.
New keyboard shortcuts for Designer on macOS:
  • Cmd+M. Open a tooltip.
  • Cmd+Shift+M. Open a tooltip on method parameters.
  • Option+F11. Go to the method in the debugger.
  • Shift+F12. Go to the method definition.
  • Cmd+Option+Shift+F5. Start the application without debug mode.

New keyboard shortcuts for any client application on macOS:

  • Cmd+J. Select from the text template list.
  • Cmd+Q. Close the application.
  • All the added shortcuts are implemented in addition to the already existing keyboard shortcuts for the specified functions.
These keyboard shortcuts were unavailable in client applications and Designer on macOS.Adjusted keyboard shortcuts for operations on macOS.
Server clusters.
When the server cluster monitoring system successfully receives data during a server call, it considers such working process functional.The server cluster monitoring system used only special cluster monitoring system calls to make sure the working process is functional. In some cases, this could lead to erroneous restarts of working processes due to heavy load on the server cluster.Reduced risk of unreasonable restarts of working processes by the server cluster monitoring system.
Client application.
If a cluster service call error occurs on the server when connecting the client application to a server cluster or during a server call, the user will see a dialog box with information about the error and option to reconnect or attempt another server call (automatically as well).If a cluster service call error occurred on the server when connecting the client application to a server cluster or during a server call, the user was prompted to close or restart the client application.Reduced number of situations when the client application is restarted or closed.
Storing settings.
For the standard settings storage, restrictions on the length of username and settings key are removed. The object key length is still restricted and cannot exceed 256 characters.

The dataset obtained by the Select() method of the standard settings storage manager will be ordered by:

  • Hash function value of the username (ascending).
  • Object key (in alphanumeric order, ascending).
  • Hash function value of the settings key (ascending).
  • The Version field (ascending).

This change is not implemented in version 8.3.22 compatibility mode.

The following restrictions on property length were set for the standard settings storage:
  • Username could no exceed 64 characters.
  • Settings key could no exceed 128 characters.

The dataset obtained by the Select() method of the standard settings storage manager was sorted in ascending order by the following fields:

  • Username
  • Object key
  • Settings key
Advanced standard settings storage features.
Full-text search.
If you enter a search query of 3 or less characters into the global search string, this query is sent to the full-text search as is.

Restrictions on the number of returned full-text search results are removed.

If you entered a search query of 3 or less characters into the global search string, this query was sent to the full-text search with an asterisk after the entered characters.

If a full-text search returned more than 1 million results, an error occurred without displaying the search results.

You can get the result of a full-text search in situations that previously caused errors.
Configuration extensions.
Development tools.
When you check the extension module syntax In Designer, in methods annotated as ChangeAndValidate, the "Variable is not defined" errors are ignored in all method areas except for #Insert ... #EndInsert.

+

When you checked the extension module syntax in Designer, in methods annotated as ChangeAndValidate, the "Variable is not defined" errors occurred when the method used an attribute not added to the extension. However, it was not required to actually add the attribute.In case of targeted changes of configuration methods using the ChangeAndValidate annotation, fewer extended configuration objects must be adopted into the extension.
Spreadsheet documents.
If vertical text alignment for a spreadsheet document cell is set to "Center" or "Bottom", but the text in it does not fit in the cell vertically, the text will be displayed as if vertical text alignment were set to "Top". In this case, the text is displayed starting from the top cell border. If the text still does not fit in the cell completely, the excess text will be truncated.

If a spreadsheet document is exported to any format other than MXL (HTML, Microsoft OpenXML, OpenOffice, and so on), alignment will remain the same and the exported document might differ from the original.

This change is not implemented in version 8.3.22 compatibility mode.

If vertical text alignment for a spreadsheet document cell was set to "Center" or "Bottom", but the text in it did not fit in the cell vertically, the text was placed and truncated in the following way:
  • If alignment was set to "Center", the text was vertically aligned to the cell center and the text parts that did not fit in the cell were truncated from its beginning and from its ending.
  • If alignment was set to "Bottom", the text was vertically aligned to the cell bottom and the text part that did not fit in the cell was truncated from its beginning.

+

Eliminated unexpected system behavior. If the text does not fit in the cell, the text beginning will be always visible regardless of selected vertical text alignment.

+

Mobile client.
Web client.
For client application form fields, you can specify the field content to be taken into account by the operating system autofill tool. The feature is implemented in mobile and web clients. In web client, only input fields of the currently open form can be automatically filled. The field content of other open forms remains unchanged.

New form field extension property for the input field: AutofillHint.

This feature was not provided.Simplified auto filling of fields that have standard meanings.

+

Data composition system.
Dynamic lists.
When restoring settings, the DataCompositionSettingsComposer.Restore() method now clears (or disables) filters in custom settings that use unavailable fields (on the left of the filter).

This change is not implemented in version 8.3.22 compatibility mode.

When restoring settings, the DataCompositionSettingsComposer.Restore() method did not check the availability of fields used in on the left of the filter.In reports or dynamic lists, custom filters by fields unavailable in the report or dynamic list are disabled or deleted. This change is also applied to filters by fields disabled by functional options.
Data composition system.
The way the list of available DCS fields is displayed in a form table field has been optimized.The way the list of available DCS fields was displayed in a form table field was not optimal.Delay-free navigation in the list of available DCS fields (especially when the list contains thousands of items).
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.16.The format version of configuration dump to XML files was 2.15.Configuration dump to XML files supports new platform features.
Data composition system.
When fields with multiple characteristics are filtered, the data composition system filters the field that contains a multiple characteristic, but does not filter the values of such characteristic.

This change is not implemented in version 8.3.22 compatibility mode.

When fields with multiple characteristics were filtered, the data composition system filtered the field that contained a multiple characteristic and the values of such characteristic.Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Administration tools.
You can set up preliminary downloading and installation of the client application distribution package on user computers. Such downloading will be performed before the actual application update on the server.

New configuration file: ClientUpdate.cfg.

This feature was not provided.

Client application update could not be scheduled.

After 1C:Enterprise update on the server, the user does not have to wait until the new client application version is downloded and installed to start working, since it is done preliminary.
Client application form.
Collection view for the input field displaying the form attribute of the ValueList or FormDataCollection type has been changed. Each collection element displayed in the input field has its own presentation, image, and the deletion button. If the input field displays a collection with a single type, you can add values to the collection directly from the input field including multiple choice. The selection button does not perform any actions. The view button activates the collection editing form.

Value list view in a table cell of the client application form is changed in the same way.

New properties for the input field of the client application form: MultipleValuesBackColor, MultipleValuesTextColor, MultipleValuesFont, MultipleValueDataPath, MultipleValuePresentationDataPath, MultipleValuePictureDataPath, MultipleValuesPicture, AllowInputEmptyMultipleValues, AllowMultipleValuesDuplicates, ShowCheckBoxesInDropListWhenInputMultipleValues, MultipleValuesHyperlink, MultipleValuePictureShape, and MultipleValuePictureSize.

New methods for input field extension for the client application form: GetSelectedMultipleValues() and SetSelectedMultipleValues().

New events for the input field of the client application form: CommandGenerateProcessing, MultipleValuesAdd, MultipleValuesDelete, MultipleValueOpening, and MultipleValueURLProcessing.

New system enumerations: InputFieldMultipleValuePictureShape and InputFieldMultipleValuePictureSize.

The changed view is implemented in the Taxi and Version 8.2 interfaces.

+

The input field displayed the form attribute of the ValueList or FormDataCollection type as a list of semicolon-separated value presentations. To change the list, you had to open a separate form.Improved view of values of the ValueList and FormDataCollection types. This will allow creating more compact and user-friendly interfaces.
Charts.
Changed Gantt chart appearance in thin and web clients. Text for points, values, and intervals of the chart can be displayed in several rows. You can display text on chart intervals.

You can select chart values using the keyboard and mouse. You can select chart intervals using the mouse. Interval time limits are displayed in a tooltip. When you drag an interval, interval time limits are displayed in the tooltip.

New property for the GanttChart object: IntervalTextRepresentation. New method for the GanttChart object: FindIntervalByID().

New property for the GanttChartPlotArea object: TextPlacement.

New properties for the GanttChartInterval object: TextColor, ID.

New properties for form field extension of the Gantt chart: CurrentValue, SelectedValues, ValueSelectionMode, CurrentInterval, SelectedIntervals, IntervalSelectionMode, VerticalLines, and HorizontalLines.

New events for form field extension of the Gantt chart: OnActivateValue, OnActivateInterval, BeforeExpand, BeforeCollapse.

The Gantt chart had a different appearance. Users could not select values and intervals.The Gantt chart is now more user-friendly. Advanced user and chart interaction features.
XML and XDTO support.
New types for the XDTO namespace (http://v8.1c.ru/8.1/data/enterprise):
  • AnyDBRef. Main type of references to database objects (any reference types, except for enumerations).
  • AnyMDEnum. Main type of references to configuration enumerations (any values of enumerations created in the configuration).
  • AnyIBRef. Type corresponding to the AnyRef type.

When you generate a native XDTO package, we recommend that you use one of the implemented types depending on the type of saved value. If you use a global XDTO factory, the new types will be used automatically.

This change is not implemented in 8.3.22 version compatibility mode.

The XDTO namespace (http://v8.1c.ru/8.1/data/enterprise) contained only the AnyRef type. It did not allow you to correctly display the AnyRef type value. When you used a global XDTO factory, the AnyRef type was used for the AnyRef type attribute.Eliminated unexpected system behavior.

With the AnylBRef type, you can correctly save and restore the value of the AnyRef type attribute.

Client application form.
The following item properties of the client application form are now supported on the server:
  • Form field extension for the input field: AutoShowClearButton, AutoShowOpenButton, AutoCorrectionOnTextInput, SpellCheckingOnTextInput, AutoCapitalizationOnTextInput, SpecialTextInputMode, OnScreenKeyboardReturnKeyText, and HeightControlVariant.
  • Form table extension for the input field: RefreshRequest.

An attempt to access the AssociatedTable property throws an exception for the following client application form items: form group extension for a normal group, form group extension for pages, and form command.

This change is not implemented in 8.3.22 version compatibility mode. +

No actions or errors occurred when the server accessed the following item properties of the client application form:
  • Form field extension for the input field: AutoShowClearButton, AutoShowOpenButton, AutoCorrectionOnTextInput, SpellCheckingOnTextInput, AutoCapitalizationOnTextInput, SpecialTextInputMode, OnScreenKeyboardReturnKeyText, and HeightControlVariant.
  • Form table extension for the input field: RefreshRequest.
  • Form group extension for a normal group: AssociatedTable.
  • Form group extension for pages: AssociatedTable.
  • Form command: AssociatedTable.
Eliminated unexpected system behavior.
Data composition system.
New restriction for programmatic or interactive editing of the DCS settings structure: not more than 30 nesting levels.

In case of interactive or programmatic import of a report, report option, or data composition schema from a file, only the settings located above the 60 nesting level are imported. The remaining settings are ignored.

This change is not implemented in version 8.3.22 compatibility mode.

+

There were not any restrictions in terms of nesting levels of items for the DCS settings structure in case of programmatic or interactive operations or import from files. That could result in an abnormal termination of the client application.Reduced probability of situations where the number of DCS settings is dramatically increased due to their editing (for example, as a result of dragging some part of settings).

Developers and users cannot interactively or programmatically set up a report option where the limit of 30 nesting levels is exceeded for settings structure items, filter items, or grouping fields.

If the user opens reports or imports report options/data composition settings, all the setting items located below the 60 nesting level are lost and the user gets a respective notification.

Client application form.
If the Accessibility property in the client application form (in thin, thick, or web client) is set to False, the buttons related to form commands become unavailable in the form.

This change is not implemented in version 8.3.22 compatibility mode.

If the Accessibility property in the client application form (in thin, thick, or web client) was set to False, the buttons related to form commands remained available in the form.

This change is not implemented in version 8.3.22 compatibility mode.

Eliminated unexpected system behavior.

Table of contents

Renamed objects

ObjectThe old nameThe new name
New names of properties and objects related to the planner field. Former names are supported for compatibility purposes.

+

  • PlannerCommandGenerateParameters.
  • PlannerCommandDescription.
  • PlannerCommandSource.
  • PlannerStandardCommand.

+

  • PlannerFieldCommandGenerateParameters.
  • PlannerFieldCommandDescription.
  • PlannerFieldCommandSource.
  • PlannerFieldStandardCommand.
English method names of the error handling manager. The old method names are supported for compatibility purposes.
  • GetCategoryForUser().
  • GetMessageForUser().
  • GetDescriptonForUser().
  • GetBriefDescription().
  • GetDetailDescription().

+

+
  • ErrorCategoryForUser().
  • ErrorMessageForUser().
  • ErrorDescriptionForUser().
  • BriefErrorDescription().
  • DetailErrorDescription().

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
On mobile devices, the SystemInfo.PlatformType property contains the relevant value. New values for the PlatformType system enumeration. They describe supported mobile operating systems.

This change is not implemented in 8.3.22 version compatibility mode.

On mobile devices, the SystemInfo.PlatformType property was set to Undefined.Simplified type and bitness identification of the used mobile version of 1C:Enterprise.
Mobile platform.
Mobile client.
Mobile device-specific features.
Mobile 1C:Enterprise version now supports NFC tags. This feature is provided on Android version 4.4 or later and iOS version 13.0 or later. You can read and write data in NDEF format, change the tag state to "read-only", and start the application upon mobile device contact with an NFC tag. The application is started using the deep linking tool.

New global context property: NFCTools. New objects: TextNDEFRecord, URINDEFRecord, MediaRecordNDEF, ExternalTypeNDEFRecord, EmptyNDEFRecord, UnknownNDEFRecord, NDEFMessage, and NDEFTag.

+

This feature was not provided.Support of NFC tags on mobile devices except for payment features.
Mobile platform.
Mobile client.
Mobile device-specific features.
Users can scale pictures in the preview window, which opens when executing the MultimediaTools.MakePhoto() method.

Scaling is available on Android and performed in a standard way.

This feature was not provided.The user can view a taken photo in more detail and retake it if necessary.
Mobile platform.
Mobile client.
The mobile version on Android can transfer data to a third-party application and get its operation result. You can configure the search for an application to be started using the MobileDeviceApplicationRun object.

New properties for the MobileDeviceApplicationRun object: ClipData and Categories.

New methods for the MobileDeviceApplicationRun object: RunAsync(), RunWithoutWaiting(), and SetApplicationChoiceParameters().

The MobileDeviceApplicationRun.Category property is deprecated.

The MobileDeviceApplicationRun.Run() method is deprecated.

For the mobile version on Android, features of data transfer to a third-party application were more limited. Users could not get the operation result of a third-party application.In versions on Android, advanced features for operations with external mobile applications.
Mobile client.
New feature for the mobile client with standalone mode: automatic exchange with the main infobase. The exchange starts every 15 minutes and the interval cannot be changed.

New parameter for the AfterExchangeDataWithMainServer event handler: ExchangeDate.

This feature was not provided.Improved data synchronization between the mobile device and the main infobase.
Mobile client.
Collaboration system.
Video calls can be switched to or from mobile devices.

+

This feature was not provided.Users can switch devices and join interrupted video calls again if they cannot continue a conversation on their initial device.
Mobile platform.
Mobile client.
The date and time choice form for mobile devices has been revised.The date and time choice form was different.More user-friendly date and time choice form for mobile devices.
Mobile platform.
Mobile client.
Mobile 1C:Enterprise version no longer supports iOS 8.0.

The minimum supported iOS version is 9.0.

+

Mobile 1C:Enterprise version supported iOS 8.0.

+

An outdated iOS version is no longer supported.

+

Mobile platform.
Mobile client.
New feature in mobile 1C:Enterprise version: document scanning (with result normalization) using the built-in mobile device camera. Scanning can be performed automatically or manually. Users can scan one or several pages and change page order in the scanned document.

New methods for the MultimediaTools object:

  • DocumentScanningSupported()
  • ShowDocumentScanning()
  • ScanDocumentsAsync()
  • CloseDocumentScanning()

New mobile application functionality: DocumentScanning.

Document scanning is not supported on Windows.

This feature was not provided.

Documents could be scanned only as photos, without image quality and placement normalization.

Document scanning using the mobile device camera with scanning results close to the ones of stationary scanners.

+

Mobile platform.
Mobile client.
Mobile device-specific features.
Extended filter features for operations with contacts and calendars.

The following filter fields can be specified for the filters used in the ContactManager.FindContacts() and CalendarsManager.FindCalendars() methods: Account, AccountID, and AccountSource.

When using the ContactManager.FindContacts(), CalendarsManager.FindCalendars(), and CalendarsManager.FindEvents() methods, the root values of the passed filter are combined in case of searching with the AND operator.

For better performance of operations with contacts and calendars, filter is always applied by the account currently used in the application.

+

Filtering by account (or its parameters) was not supported for operations with contacts and calendars.Extended filter features for operations with contacts and calendars.
Mobile platform.
Mobile client.
HEIC images can be imported in the mobile 1C:Enterprise version running on Android 9 or later and on iOS 11 or later. After such import, HEIC images are converted into JPEG and stored in this format.

+

This feature was not provided.Extended list of image formats that can be imported by mobile applications based on 1C:Enterprise platform.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Client application form.
New property for a form field that displays a form attribute of the ValueList or FormDataCollection type: MultipleValuesExtendedEdit. If the property is set to False, the input field has the same features as in previous versions, except for displaying the collection content.

New properties for the input field that displays multiple values: TypeRestriction, ChoiceParameters, ChoiceParameterLinks, TypeLink.

New parameter for the choice form: ChoiceByAdding. New parameter for the NotifyChoice() method: ChoiceByAdding. New parameter for the StartChoice and ChoiceProcessing event handlers of the form field extension for the input field: ChoiceByAdding. These parameters will allow you to identify the mode of the form field that initiated adding of values.

If the selection using checkboxes is allowed for the input field that displays multiple values and the field data contains several values, the opened choice list will contain all the selected values with selected checkboxes.

This feature was not provided.

You were unable to change multiple value presentation in the input field without using the multiple value edit mode.

In events and methods for selecting values in the input field, you were unable to specify the multiple value mode for the field.

When using multiple values in the input field, you can now specify the field mode. You can also implement the previous behavior where the new behavior is not required.
Mobile platform.
Mobile client.
Mobile device-specific features.
Now you need less time and effort to ensure that a document in the mobile device viewfinder is suitable enough for scanning (the document frame lights up green).

The algorithm for calculating the scanned document quality has been changed so that you can get a more evenly distributed value.

You will get a warning if the page you are trying to scan is already scanned.

Previously, you spent more time to ensure that the system accepts the quality of the document for scanning.

The algorithm for calculating the scanned document quality used to return values that were unevenly distributed within the valid value range.

You did not get any warning if you tried to scan an already scanned page.

Improved document scanning in 1C:Enterprise mobile version.
Administration tools.
The GetDBStorageStructureInfo() method returns a description of internal tables linked to the speech recognition tool.The GetDBStorageStructureInfo() method did not return tables linked to the speech recognition tool.Eliminated unexpected system behavior.
Administration tools.
The GetDBStorageStructureInfo() method returns a description of internal tables linked to the collaboration system.The GetDBStorageStructureInfo() method did not return tables linked to the collaboration system.Eliminated unexpected system behavior.
Administration tools.
Now the GetDBStorageStructureInfo() method returns a description of service tables related to the tool of database tablespace management.Previously the GetDBStorageStructureInfo() method did not return tables related to the tool of database tablespace management.Eliminated unexpected system behavior.
Administration tools.
Now the GetDBStorageStructureInfo() method returns a description of service tables related to collaboration system bots.Previously the GetDBStorageStructureInfo() method did not return tables related to collaboration system bots.Eliminated unexpected system behavior.
Administration tools.
Now the GetDBStorageStructureInfo() method returns a description of service tables related to settings storage.Previously the GetDBStorageStructureInfo() method did not return tables related to settings storage.Eliminated unexpected system behavior.
Mobile client.
New features during automatic data synchronization by a mobile client with standalone mode:
  • The device cannot switch to sleep mode during generation and initial import of standalone mode data, as well as during the first data exchange after configuration startup.
  • You can now click the status window at the bottom of the screen to see the exchange process status.
The mobile device could go into sleep mode during the initial infobase filling with data. This caused situations when the application was running and the data in it was incomplete, inconsistent, or missing.

Displayed exchange process information was less user-friendly.

Improved automatic data synchronization for a mobile client in standalone mode.
Mobile application builder.
Mobile 1C:Enterprise version 8.3.23 is now supported in the mobile application builder.Mobile 1C:Enterprise version 8.3.23 was not supported in the mobile application builder.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 11.19.1
  • Postgres Pro Standard 11.19.1
  • Postgres Pro Enterprise 11.19.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.17 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 11.19.1
  • Postgres Pro Standard 11.19.1
  • Postgres Pro Enterprise 11.19.1.
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 12.14.1,
  • Postgres Pro Standard 12.14.1,
  • Postgres Pro Enterprise 12.14.1.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 12.14.1,
  • Postgres Pro Standard 12.14.1,
  • Postgres Pro Enterprise 12.14.1.
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 13.10.1
  • Postgres Pro Standard 13.10.1
  • Postgres Pro Enterprise 13.10.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 13.10.1
  • Postgres Pro Standard 13.10.1
  • Postgres Pro Enterprise 13.10.1.
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 14.7.1
  • Postgres Pro Standard 14.7.1
  • Postgres Pro Enterprise 14.7.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 14.7.1
  • Postgres Pro Standard 14.7.1
  • Postgres Pro Enterprise 14.7.1.
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 15.2.1
  • Postgres Pro Standard 15.2.1
  • Postgres Pro Enterprise 15.2.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 15.2.1
  • Postgres Pro Standard 15.2.1
  • Postgres Pro Enterprise 15.2.1.
Extended list of supported DBMS.
Licensing system.
Administration tools.
Implemented the legal access verification in a server infobase: now the system verifies whether you have legal rights to use the application at 1C:Enterprise level. To pass the verification, you need to configure the licensing client.

For more information on the licensing client settings, see the documentation.

For a separated infobase, the licensing client is configured only once. You do not need to set it up for each data area.

Previously the system verified whether you had legal rights to use the application at 1C:Enterprise level only when running in file mode or using the MINI server.Now the system verifies whether you have legal rights to use the application in all infobase modes.
Administration tools.
Now you can close active sessions in the infobase when updating the infobase configuration via the command-line. The process is similar to the interactive behavior of Designer. The list of situations when you can close sessions has not changed and is provided in the documentation.

New commands and parameters:

  • New parameter for the /UpdateDBCfg command to run Designer in batch mode: SessionTerminate.
  • New parameter for Designer running in the Agent mode and for the SSH gateway of the standalone server: --session-teminate for the config update-db-cfg command.
  • New possible values for the session-terminate parameter of the infobase config apply command of the standalone server administration utility (ibcmd). New default value for the --session-terminate parameter: disable.
  • If you update the database configuration after the extension is updated, you can use the --session-terminate parameter in the infobase config apply command.
Previously you were unable to close active sessions in the infobase similarly to the interactive operation in Designer when you updated the infobase configuration via the command-line (Designer, agent, or the SSH gateway of the standalone server).Unified behavior of different infobase configuration update options.
Documentation.
In the help section of Designer and client application, you can find information on keyboard shortcuts for Mac computers.Information on keyboard shortcuts for Mac computers was not provided in the help section of Designer and client application.More informative help section.
Administration tools.
New mode for the administration console utility. In this mode, you can verify and repair only the tables of infobase data history. New startup command-line option for the 1cv8a utility: --data-history-integrity.This feature was not provided.Advanced features of the administration console utility.
Development tools.
Now it takes less time to start the thin client from Designer in the client/server infobase.Thin client startup from Designer in the client/server infobase was time-consuming.Faster thin client startup from Designer in the client/server infobase.
DBMS operations.
The system now supports Postgres Pro DBMS version 11.20.1 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.17 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 12.15.1 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 13.11.1 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise (version 13.11.2).
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 14.8.1 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 15.3.1 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
Mobile application builder.
Changed the process of building iOS mobile applications. Now you can publish built applications in the AppStore.

To publish an application, rebuild it using the mobile application version 8.3.23.80 or later on the builder that comes with the mobile version used.

Mobile applications built by an earlier version of the mobile application builder failed validation in the AppStore and could not be published.Eliminated unexpected system behavior.
DBMS operations.
The system now supports Postgres Pro DBMS version 11.21.2 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64.

The products are supported in 1C:Enterprise version 8.3.17 or later.

Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 12.16.2 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 13.12.2 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 14.9.2 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
DBMS operations.
The system now supports Postgres Pro DBMS version 15.4.2 of the following products:
  • Postgres Pro 1C.
  • Postgres Pro Standard.
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

DBMS version bitness: x86-64. +The products are supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.

This Postgres Pro DBMS version was not supported by 1C:Enterprise.Extended list of supported DBMS.
Data accelerator.
If a memory shortage error is generated in Data accelerator during query execution, the copy of the Data accelerator database is disabled for 60 seconds. After the 60-second pause, Data accelerator queries are resumed. If memory shortage errors occur for 3 times sequentially (with an interval of 60 seconds), the copy of the Data accelerator database is completely disabled until the forced update.Previously, the copy of the Data accelerator database was disabled before the forced update after the first memory shortage error.1C:Enterprise attempts to maintain the performance of the copy of the Data accelerator database to perform simpler queries than the one that caused the error. When the load is reduced, operations with complex queries, which previously caused memory shortage errors, might be resumed.
DBMS operations.
System requirements.
The system now supports Tantor SE 1C DBMS.

Supported versions: 14.8 and 15.4.

Supported processors: ARM64 and x86-64.

Supported operating systems are defined by a DBMS vendor.

Previously, 1C:Enterprise did not support Tantor SE DBMS.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Pangolin DBMS version 5.3.2.

Supported processors: x86-64.

Supported operating systems are defined by a DBMS vendor.

Previously, 1C:Enterprise did not support Pangolin DBMS.Extended list of supported DBMS.
DBMS operations.
System requirements.
The system now supports Jatoba DBMS version 4.8.2-1117.

Supported processors: x86-64.

Supported operating systems are defined by a DBMS vendor.

Previously, 1C:Enterprise did not support Jatoba DBMS.Extended list of supported DBMS.
macOS.
System requirements.
The system now supports macOS versions 11, 12, 13, and 14.Previously, 1C:Enterprise did not support macOS versions 11.4 and later.Extended list of supported operating systems.
Documentation.
The description of the OpenID authentication request when the OpenID server uses the second authentication factor check is now refined in the documentation.Previously, the OpenID authentication request when the OpenID server uses the second authentication factor check was incorrectly described in the documentation.Fixed error in the documentation.
Administration tools.
New feature: intermediate certificates of the Federal Tax Service of the Russian Federation generated using the GOST R 34.11-2012 algorithms are added to the cacert.pem and cacertnx.pem files.This feature was not provided.The number of certificate check errors when accessing the websites of the Federal Tax Service of the Russian Federation is reduced.
Development tools.
Now you can activate a developer license if you are registered on the 1C:Developer Network portal Read more..

If your localization language is Armenian, Azerbaijani, Georgian, Latvian, Kazakh, Russian, or Turkmen, the 1C for Developers portal (read more) will be used. For all other localization languages, you will be able to choose between these portals. The choice of the portal does not depend on the ExternalResourcesMode parameter of the conf.cfg configuration file.

New parameter for the GetDeveloperLicenseAgreement() method of the license acquisition manager: DeveloperPortal. New property: LicenseAcquisitionRequest.DeveloperPortal.

Previously, you were able to activate the developer license if you were registered only on the 1C for Developers portal (read more).Users who cannot register on the 1C for Developers portal (read more) can get a developer license.

Table of contents

Transition from the previous version to the version 8.3.23

Table of contents

Version 8.3.22

Version 8.3.22 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.21 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.20 + was available.Configurations developed using 1C:Enterprise platform version 8.3.21 or earlier can now run on version 8.3.22 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.21 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.21 after the migration to version 8.3.22, even if you disable the compatibility mode (simply enable it again).
Full-text search.
New version (2) of the full-text data search engine. This engine can use special algorithms for selecting root base and the list of stop words. Some search query features of the current full-text search version are not supported in the new version. New design for displaying full-text search results. Changes in the operation of the full-text search manager methods in the new full-text search version:
  • The following methods are not used: GetCompositeWordsSeparationMode() /SetCompositeWordsSeparationMode().
  • The UpdateIndex() method starts indexing and immediately returns control. To manage indexing completion, use the IndexTrue() method.
  • The IndexUpdateComplete() method does not consider that full-text search indexes must be merged.

New methods for the full-text search manager: GetFullTextSearchVersion() /InstallFullTextSearchVersion().

New server cluster services:

  • Full-text search service v2.
  • Full-text search coordination service v2.

New technological log event: <FTS>

New command line parameter for the ibsrv utility: --ftext2-data

The new full-text search version requires server cluster computers to have Java version 8 or later.

The standard data processor of full-text search management is revised.

The new full-text search version is supported for infobases in client/server mode. For a standalone server, it is also supported for infobases in file mode. In other modes, the new full-text search version is not supported.

1C:Enterprise contained only one full-text search engine option.The new full-text search engine will:
  • Improve the quality of search results.
  • Improve full-text search performance in large infobases.
  • Add new information from the infobase to an index more efficiently.
  • Prevent the following error: Maximum number of words to search exceeded.
  • Reduce the disk space occupied by the full-text search index.
  • Notify the user of multiple search results by displaying a warning instead of an error. Search results will be displayed anyway.
Common objects.
New feature: create random passwords that are easier to remember but still secure. New object: RandomPasswordGenerator.

New feature: generate random passwords in the infobase user editing form and password recovery form.

New buttons to view the password value are implemented in the infobase user editing form, password input field, and password confirmation field. If you click Generate password, a new password will be displayed in clear text in the Password field.

This feature was not provided.

+

Simplified creation of unique passwords to use in various application subsystems and set authorization passwords for infobase users.
Cryptography support.
New feature: cryptography is fully supported in client applications on macOS. The system supports CryptoPro cryptography tools (for macOS).Cryptography support on macOS was limited.

+

New feature: cryptography is fully supported in client applications on macOS.
Configuration extensions.
New feature: change numeration properties for documents, business processes, tasks, and number generators.

New feature: create native number generators in extensions. New feature: set native and adopted number generators for native and adopted extension documents.

New feature: change code length for catalogs, tasks, exchange plans, charts of characteristic types, charts of accounts, and calculation charts.

New feature: change description length for catalogs, exchange plans, charts of characteristic types, charts of accounts, and calculation charts.

These features were not provided.

+

Advanced configuration extension features.

+

Common objects.
New property: SystemInfo.ApplicationOption. The property is used to identify special distribution options of 1C:Enterprise platform.This feature was not provided.New feature: define a special distribution option of 1C:Enterprise platform.
PDF document operations.
New method: PDFDocument.Show(). Use this method to open a form to view a PDF document from 1C:Enterprise language.To view a PDF document, you could either open the view form interactively or create your own form.

+

The PDFDocument object allows you to open a form to view a document like other similar 1C:Enterprise language objects.
Distributed infobases.
Configuration extensions.
New feature: receive information about changes located in the data exchange package to be processed:
  • Configuration
  • Configuration extensions
  • Configuration extensions that change data

New methods for the exchange plan manager: ReadChangesDescription() and ReadConfigurationAndConfigurationExtensionsChanges().

This feature was not provided.

You could only receive information about the main configuration being different from the database configuration at the moment.

Improved troubleshooting for implementing automatic data exchange in systems that use a distributed infobase.
Client application.
Administration tools.
Event log.
New feature for OpenID Connect or USIA authentication: specify various values to identify infobase users (matching keys). These values are specified for each infobase user and linked to the authentication provider used in a certain case. Matching keys can have an arbitrary ID and value.

New property for the InfobaseUser object: UsersMatchingKeys. You can access this property only from 1C:Enterprise language.

New value for the authenticationUserPropertyName field of the provider parameter details in the default.vrd file: matchingKey. This value allows you to specify that a user is determined via a matching key upon authentication.

More detailed messages about errors that occur upon OpenID Connect or USIA authentication.

Upon OpenID Connect or USIA authentication, you could use a limited list of fields to determine an infobase user.

Messages about authentication errors were unclear and did not provide information on reasons of authentication issues.

Improved user matching upon OpenID Connect or USIA authentication. Improved troubleshooting of authentication issues.

+

Data composition system.
New feature: specify an appearance template to be used in all application reports by default. New feature: specify this template for the whole infobase or for a certain user. You can specify a system data appearance template or a data appearance template created as a common configuration template.

New configuration property: Main report appearance template. New global context property: ReportsAppearance.

This feature was not provided.

You could specify an appearance template only for single reports in the application.

Improved report appearance features. You can apply the same appearance to all configuration reports, including those that will be added later and by other technicians.

+

Collaboration system.
Administration tools.
New feature: create a collaboration system data export and restore data from a backup.

New feature: transfer data between different collaboration system server instances.

New methods for the collaboration system manager: GetDataExportsAsync(), GetDataExports(), GetDataExportAsync(), GetDataExport(), BeginCreateDataExportAsync(), BeginCreateDataExport(), GetDataExportAddressAsync(), GetDataExportAddress(), LoadDataExportAsync(), LoadDataExport(), RegisterDataExportAsync(), RegisterDataExport(), BeginRestoreFromDataExportAsync(), BeginRestoreFromDataExport(), DeleteDataExportAsync(), DeleteDataExport(), SetDataExportDescriptionAsync(), SetDataExportDescription().

New feature for the standard Collaboration system management data processor: operate with data export and import.

The file format of the collaboration system data export is not documented.

The collaboration system can store a limited number of export files at the same time: not more than 5 copies. You can change this parameter using the collaboration server configuration tools.

These features were not provided.

You could not export collaboration system data and transfer data between different collaboration system server instances.

New features: Data transfer from one collaboration server (including a cloud server) to another one.

Export of all collaboration system data as one file.

PDF document operations.
New feature: convert a PDF document so that the color scheme is converted into grayscale.

New commands in forms for operating with PDF documents allow you to execute this conversion. New methods for the PDFDocument object: ConvertToGrayScaleAsync(), ConvertToGrayScale().

This feature was not provided.

+

Advanced PDF document features.
PDF document operations.
New property for the PDF document form field extension: UsedFileName. You can use this property to specify a file name that will be used if a user decides to save a document displayed by the form field.

+

This feature was not provided.Advanced PDF document features.

+

1C:Enterprise script.
New property for attribute columns of the client application form of the ValueTable and ValueTree types: Fill check (FillChecking). The check is executed by the client application form. The check is executed similarly to tabular sections of catalogs, documents, and so on.You could execute the fill check for the client application form attributes of the ValueTable or ValueTree type only for the availability of at least one row. The fill check for attribute columns was not supported.Improved automatic fill check for the client application form attributes of the ValueTable or ValueTree type.
Configuration extensions.
New feature: change localizable properties of configuration objects in the extension. You can change the following configuration objects: note, presentation and editing formats, tooltips, presentations of objects, records, and lists.

New feature: modify adopted common templates and configuration object templates.

You could not change localizable properties of objects and templates, except for spreadsheet documents.

+

Advanced configuration extension features.

+

Configuration extensions.
New optional parameter for the ConfigurationExtensions.Create() method: Data. This method allows you to create an object of the ConfigurationExtension type from the BinaryData type value. For such ConfigurationExtension object, the Data parameter is not required in the Write() method.

New method: ConfigurationExtensions.ConfigurationExtensionsChanged(). It indicates that either the extension composition is changed or one of the existing extensions is updated after the current session is started.

You could not receive extension parameters without saving the extension to the database.

You could analyze whether the extension composition was changed or an extension was updated after the current session is started. You could do it by analyzing the hashes of session and infobase extensions. +

Advanced extension administration features.
Queries.
Data composition system.
New feature in queries and data composition system: receive an infobase object reference UUID.

New function in query language and expression language of the Data composition system: UUID().

This feature was not provided.New feature in queries and data composition system: receive an infobase object reference UUID.
Administration tools.
Server clusters.
New feature: use the external session management service for file infobases. You can use the external session management service for a file infobase only with a PROF-level license.

New parameters for the conf.cfg configuration file: ExternalSessionManagementRequired and ExternalSessionManagementConnectionString.

New parameters for the synchronize() method of the external session management web service: SessionNumber and ClientIPAddress. New properties for the Sessions object: SessionNumber and ClientIPAddress. The new features are available only if the value of the wsver parameter is 4.

This feature was not provided.

External session management was available only for infobases in client/server mode.

You can centrally manage the number of concurrently used licenses for different applications without modifying the applications themselves.
Spreadsheet documents.
Automatic column width calculation when displaying the report result in a spreadsheet document is executed as follows:
  • Column width for the first 100 displayed rows is calculated accurately.
  • Column width for rows starting from 101 is not calculated automatically.

This change is not implemented in 8.3.21 compatibility mode.

If you double-click the column separator, the column width is calculated according to the Location property.

Automatic column width calculation when displaying the report result in a spreadsheet document was executed as follows:
  • For columns of the first displayed row, the width was calculated "accurately".
  • For the next 99 displayed rows, the width was calculated "approximately".
  • For rows starting from 101, the width was not calculated automatically.

+

More accurate column width calculation in reports.

+

Spreadsheet documents.
New spreadsheet document feature: set indents of the content from the borders of a cell/cell area.

New properties for the SpreadsheetDocumentCellsArea, SpreadsheetDocumentDrawing, DataCompositionAppearance, DataCompositionAreaTemplateTableCellAppearance objects: LeftIndent, RightIndent, TopIndent, BottomIndent. For the data composition system settings, these properties are available only for report settings.

Export to the following formats considers indents availability: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 or later, Microsoft Word 2007 or later), or ODS (OpenDocument).

+

This feature was not provided.Improved report appearance features. +
Spreadsheet documents.
New feature: get the row format of a spreadsheet document cell area.

New property: SpreadsheetDocumentCellsArea.RowsFormat.

New RowsFormat parameter for the Area() and GetArea() methods of the SpreadsheetDocument object.

This feature was not provided.

+

Using 1C:Enterprise language, you can determine which row format is set for the selected cell area.

+

DBMS operations.
Information that describes the data exchange table for mobile client with standalone mode is included in the data (the Purpose field) returned by the GetDBStorageStructureInfo() global context method.This feature was not provided.Eliminated unexpected system behavior.
DBMS operations.
System requirements.
The following versions of PostgreSQL DBMS are supported now: 10.19, 11.14.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following versions of PostgreSQL DBMS are supported now: 10.20 and 11.15.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following versions of PostgreSQL DBMS are supported now: 10.21, 11.16.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following versions of PostgreSQL DBMS are supported now: 12.9, 13.5, 14.1.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following versions of PostgreSQL DBMS are supported now: 12.10, 13.6, and 14.2.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following versions of PostgreSQL DBMS are supported now: 12.11, 13.7, 14.3.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Print tools.
On macOS, you can now print using internal operating system interfaces.

On macOS and Linux, the Printer button is hidden from all report forms.

On macOS, printing was performed by the platform tools.

On macOS and Linux, print forms contained the Printer button but clicking it had no effect as these operating systems do not allow opening a separate window with printer property settings.

Printing using familiar print tools is now available on iOS.

+

Collaboration system.
New feature: noncontext conversation search by a conversation title and full names of participants. To search, you can enter only several space-separated words. All the entered words must be found.Only search by a conversation title was available.Simplified noncontext conversation search when only a conversation participant (or participants) is known.

+

Collaboration system.
 +

Simplified monitor selection for screen sharing. You can select a monitor if several monitors are connected to the computer. The change is implemented only for thin and thick client applications.

Monitor selection for screen sharing was less clear and required more actions.Simplified monitor selection for screen sharing.
Spreadsheet documents.
Extended area beyond which you can drag a spreadsheet document area.The area beyond which you could drag a spreadsheet document area was smaller.You can drag a spreadsheet document area more conveniently.
Error handling.
Web client.
If you need to take a screenshot when generating an error report in Mozilla Firefox, you need to use a web browser extension for 1C:Enterprise.

If you do not have the web browser extension, you will see a warning that will prompt you to install the extension and specify the reason why it is required (taking a screenshot is time-consuming).

Taking a screenshot when generating an error report in Mozilla Firefox could take a long time.

+

If you need to attach a screenshot when generating an error report in web client, taking a screenshot will take less time. The change is applied only to web client in Mozilla Firefox.
Collaboration system.
Improved user interface of the collaboration system and video call window.

New keyboard shortcut for the Mark as read command in the message list: Ctrl + M.

+

The user interface of the collaboration system and video call window was less convenient.Improved user interface of the collaboration system and video call window.
Collaboration system.
New features for the website that manages operations for external collaboration system users:
  • Quote when responding to a message using a special command.
  • Mark a conversation as read using a special command. Configure the reading mark in the user settings.
  • View an image without downloading the image file to the local drive.
  • Select hardware to use during video calls in a special dialog box.
  • Edit the profile picture of the current user.
  • Copy attachments using the context menu.
  • Start video conferences in a more convenient window.
These features were not provided.Improved website that manages operations for external collaboration system users.
Collaboration system.
Updated appearance of the video conference form and its buttons (expand to full view, and so on) in the collaboration system. Changed animation upon connecting a new user, reconnecting a user, and starting screen sharing.The appearance of form buttons and animation in the video conference form of the collaboration system was different.Improved video conference appearance.
Mobile client.
Collaboration system.
Enhanced image quality during video calls if they are executed in mobile client using a video server.

Image quality is adjusted to the current processor load and video size on the mobile device screen.

Image quality during video calls did not depend on the processor load and video size on the mobile device screen.Enhanced image quality during video calls in mobile client on mobile devices.

+

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
DBMS operations.
Receiving results of a query with multiple nested tables is improved.Receiving results of a query with multiple nested tables was time-consuming.Receiving results of a query with multiple nested tables takes less time.
DBMS operations.
Improved use of the IN(<value list>) query language operator when using PostgreSQL DBMS. Execution of data access restriction queries takes less time.

It is recommended that you analyze query conditions and, if PostgreSQL DBMS is used, substitute the Var1=Var2 OR Var1=Var3 expression for the Var1 IN (Var2, Var3) expression.

Execution of queries with the IN(<value list>) query language operator when using PostgreSQL DBMS took more time.Improved performance of the IN(<value list>) query language operator when using PostgreSQL DBMS.
File operations.
File transfer operations between the client and the server take significantly less time.

The size of a file to be placed in the temporary storage is no longer restricted.

Transferring files between the client and the server took more time.

The size of a file to be placed in the temporary storage could not exceed 4 GB (in serialized form).

Improved file management characteristics in 1C:Enterprise.
Configuration extensions.
Server clusters.
Reduced RAM consumption by server cluster working processes when using extensions in a shared infobase.When using extensions in a shared infobase, server cluster working processes consumed more RAM.Reduced RAM consumption by server cluster working processes when using extensions in a shared infobase.

+

Server clusters.
Improved efficiency of session data repository operations.

+

Operations with the session data repository were not efficient.No loss of server cluster performance if the server cluster stores large amounts of data in the session data repository.

+

Development tools.
Faster configuration export to a CF file.Configuration export to a CF file took more time.Faster configuration export to a CF file.

+

Development tools.
Configuration comparison takes less time.

Application configuration update takes less time. Reduced RAM consumption in 32-bit Designer upon configuration update.

The operations of configuration comparison and update took more time.

32-bit Designer consumed more RAM upon configuration update.

Configuration comparison and update take less time.

+

Full-text search.
Execution of full-text search query with the AND operator takes less time. Full-text search index must be rebuilt to achieve better performance.Execution of full-text search queries with the AND operator was more time-consuming.

+

Improved performance of full-text search queries with the AND operator.
Full-text search.
Improved full-text search reliability:
  • The occurrence of large index files with high fragmentation is prevented.
  • Merging indexes in large infobases takes less time.

+

Creation of large index files could lead to file system errors.Improved full-text search engine reliability.
Development tools.
Reduced RAM consumption when opening the All roles form in Designer.

+

When opening the All roles form in Designer, RAM consumption was high.

+

Reduced RAM consumption when opening the All roles form in Designer.
Administration tools.
Improved receipt of the user authentication lock list. Time required to receive the lock list no longer depends on the number of infobase users.Time required to receive the user authentication lock list depended on the number of infobase users.Improved performance of the Administration – Authentication locks commands in Designer and of the AuthenticationLock.GetLocks() 1C:Enterprise language method.

+

Full-text search.
 +

If file errors related to index files occur when indexing full-text search data, the full-text search index remains correct.

If file errors related to index files occurred when indexing full-text search data, the full-text search index could no longer be used.Improved full-text search stability upon data indexing.

+

Configuration extensions.
Server clusters.
Reduced RAM consumption by a server cluster working process if the working process serves a distributed infobase with distributed extensions that affect the user interface.RAM consumption by a server cluster working process was excessive if the working process served a distributed infobase with distributed extensions that affect the user interface.Reduced RAM consumption by a server cluster that serves distributed infobases with extensions that affect the user interface.

+

Pictures.
Accessing properties of the PictureLib object (as well as accessing the same property sequentially) takes less time.Accessing properties of the PictureLib object took more time.Improved performance of operations with 1C:Enterprise picture library. In particular, now it takes less time to open the Functions for technician form in configurations with large volumes of metadata.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
DBMS operations.
1C:Enterprise sets the row-level lock granularity for Microsoft SQL Server 2008 or later. Lock escalation is prevented. RAM consumption by Microsoft SQL Server might increase.1C:Enterprise set the page-level lock granularity for Microsoft SQL Server.Locks when different users operate with different database objects that occur on the same DBMS index page are prevented.
Event log.
The event log cannot be converted to SQLite format.

This event log format will no longer be supported in later 1C:Enterprise versions.

It is recommended that you convert the event log to sequential format.

1C:Enterprise supported the ability to convert the registration log into the SQLite format1C:Enterprise is prepared to stop supporting the SQLite format of the event log.
Web services and HTTP services.
Client application.
If the connection is lost when calling a web service, a catchable exception is thrown.

If the client application runs over HTTP, loss of connection opens a standard error dialog box that allows you to retry the uncompleted action.

If the connection was lost when calling a web service, the application froze.

When the client application ran over HTTP, loss of connection caused the application to hang. +

Improved client application responsiveness when running over HTTP and using web services in case of unstable network connection.
Server clusters.
Revised procedure of server cluster monitoring. Improved stability of the cluster and connected users. Performance indicators are also estimated for working processes running on the same working server. Monitoring does not stop even when one of the working processes freezes. When the number of main servers increases, the load on working processes does not increase.

New properties of the <ATTN> and <CLSTR> events.

Performance indicators were not estimated for working processes running on the same working server. Cluster monitoring stopped when one of the working processes froze. When the number of main servers increased, the load on working processes also increased.

+

Improved stability of the server cluster and users served by it.

+

Common objects.
For the RandomNumberGenerator object, the random number generator is used in accordance with standard NIST SP 800-90A (Hash_DRBG algorithm). A number sequence after creating two different random number generator objects using the same beginning number will be different.For the RandomNumberGenerator object, the Mersenne twister algorithm was applied.Improved random number generator.

+

Configuration extensions.
New additional checks for the "Extension applicability test" command in Designer:
  • Check whether a method specified in the annotation exists.
  • Check whether the number of method parameters and the number of value transfer modifiers match in the method of the main configuration and extension.

These checks are executed for methods that are not event handlers.

This feature was not provided.Simplified correction of issues that occur when an extended method no longer exists in the main configuration or the number of parameters or parameter transfer modifiers changed.

+

Client application.
In thin client, if a server call is not completed within 400 msec, the mouse cursor changes to "busy". The upgrade is ignored in thick client.In thin and thick client applications, the mouse cursor changed to "busy" when starting a server call.The mouse cursor change displays a long server call but the cursor does not blink upon numerous short server calls.

+

Client application form.
If a font is generated from another font and the size of the new font is specified, the base font size and scale are not used to determine the new font characteristics.

This change is not implemented in 8.3.21 compatibility mode.

A text for which 0 font size is set is always displayed by 13 pt font size in all client applications and on the server.

If a font was generated from another font and the size of the new font was specified, the base font size and scale were used to determine the new font characteristics.

A text for which 0 font size was set was displayed differently in different client applications.

Eliminated unexpected system behavior.
Data composition system.
If one available data composition filter field is generated from several fields, its LinkByType and ChoiceForm properties are filled in. They are filled in only if these properties of all the fields used for the generation contain the same values. The new data composition filter field is generated by merging fields in a query or by receiving several fields using dot syntax for different reference types. Besides, the ChoiceParameters and ChoiceParametersLinks properties of the available field are filled in so that the resulting links and parameters receive only links and parameters that exist in all the fields included in the available field and have matching property values.

This change is not implemented in 8.3.21 compatibility mode.

If one available data composition filter field is generated from several fields, its LinkByType, ChoiceForm, ChoiceParameters, and ChoiceParametersLinks properties were filled in from the first field with the filled value of the respective property. The new data composition filter field is generated by merging fields in a query or by receiving several fields using dot syntax for different reference types.Eliminated unexpected system behavior.
Add-ins.
Web client.
New feature: add-ins running in a web browser under Linux support operations in Russian even if the OS does not have the Russian localization.

To ensure that add-ins support this feature, they must be rebuilt with new adapter libraries.

Add-ins running in a web browser under Linux caused errors when the OS did not have the Russian localization.You can use add-ins, file system and cryptography extensions in web client running under Linux that does not have the Russian localization.
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.15.The format version of configuration dump to XML files was 2.14.Configuration dump to XML files supports new platform features.
Dumping configurations to files/Restoring configurations from files.
In XDTO package describing data types of the current configuration, the minimum value is set to 0 for all attributes that belong either to a group or an item of the hierarchical chart of characteristic types.In XDTO package describing data types of the current configuration, the minimum value was set to 1 for all attributes that belonged either to a group or an item of the hierarchical chart of characteristic types.Eliminated unexpected system behavior.

Upon XDTO serialization of objects of the hierarchical chart of characteristic types, attributes that belong either to a group or an item are displayed correctly.

Spreadsheet documents.
Data composition system.
New feature: when exporting a spreadsheet document to various formats, you can manage the quality of pictures that are placed in the spreadsheet document.

New spreadsheet document property: SavedPicturesDensity. New parameter for the list of data composition output parameters (the DataCompositionOutputParameterValues type): SavedPicturesDensity. New object: DataCompositionAreaDocumentTemplate. The first template placed in the data composition template for a spreadsheet document is the DataCompositionTemplateAreaTemplateDefinition object. This template is placed in the body of the data composition template.

When exporting a spreadsheet document in Office OpenXML (*.docx) format, pictures are saved in DrawingML format.

If the SavedPicturesDensity parameter is not set for the data composition system, the composer of the data composition template sets this parameter to High. In 8.3.21 compatibility mode, the composer sets the parameter to Original.

If you know that a report or a spreadsheet document contains pictures that should be used in the original quality (for example, they will be saved to files and edited), set the SavedPicturesDensity property to Original.

This change is not implemented in 8.3.21 compatibility mode.

This feature was not provided. Pictures were saved in the initial format.

When exporting a spreadsheet document in Office OpenXML (*.docx) format, pictures were saved in VML format.

You can control the size of the file that resulted from a spreadsheet document export to another format.
Configuration extensions.
Reduced RAM consumption if an extension contains numerous roles and adopted objects.

Faster session startup if an extension contains numerous roles and adopted objects.

Reduced number of similar messages about access restrictions upon extension of roles. +

RAM consumption by the application was greater if a configuration extension contained numerous roles and adopted objects.

Session startup took more time if an extension contained numerous roles and adopted objects.

When an extension was applied, numerous similar messages about access restrictions upon extension of roles were generated.

RAM consumption by the application was greater if a configuration extension contained numerous roles and adopted objects.

Session startup took more time if an extension contained numerous roles and adopted objects.

When an extension was applied, numerous similar messages about access restrictions upon extension of roles were generated.

Spreadsheet document.
When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects now behave as follows:
  • If the PictureSize property value is not Tile, an original picture is saved to the resulting document. If a pattern is specified for a cell, pattern picture is also saved.
  • If the PictureSize property is set to Tile, a picture is redrawn into the resulting document and the background color of a Microsoft Excel document picture becomes the same as the one of the source document picture.

As a result of these changes, pictures in a spreadsheet document become less distorted when scaling a Microsoft Excel document.

This change is not implemented in version 8.3.21 compatibility mode.

When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects behaved as follows:
  • When the PictureSize property value was not Stretch, a picture was redrawn into the resulting document.
  • When the PictureSize property value was set to Stretch, a picture was redrawn to the resulting document if a background color or pattern was not set. Otherwise, an original picture was saved.

The result of saving a spreadsheet document in Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats meets expectations of users to a greater extent.
PDF document operations.
If a PDF document contains pictures in JPEG 2000 format, they are displayed when you view this document using 1C:Enterprise platform tools.If a PDF document contained pictures in JPEG 2000 format, they were not displayed when viewing this document using 1C:Enterprise platform tools.Eliminated unexpected system behavior.
Mobile platform.
Mobile client.
Updated user notification behavior in the mobile version of 1C:Enterprise:
  • To close a notification, you need to click it.
  • If a notification allows performing an action, the right part of the notification displays a picture.
  • When displaying a notification, the application attempts to place it so that it does not overlap (or overlaps as little as possible) form controls that a user might use. In any case, the application attempts to display a notification in the lower third of the screen on a mobile device.
User notification behavior in the mobile version of 1C:Enterprise had the following distinctive features:
  • To close a notification, you had to swipe it.
  • If a notification allowed performing an action, you could perform it by clicking the notification. If a notification contained no action, clicking the notification navigated you back to the opened form.
  • A notification had a fixed location on the screen.
Now the user notification behavior in the platform is highly similar to the notification behavior in the mobile operating system. Notifications are now more convenient to use.
Data composition system.
If a report parameter contains a value of the ValueList type, then value presentation settings specified by the user are used when generating the parameter presentation:
  • Presentation of each list value is generated considering conditional appearance and available values.
  • Empty values are displayed by the <Empty value> string.
  • Value presentations are separated by a semicolon ";".

+

+

Value presentation settings specified by the user were not used to generate the presentation of a report parameter with a value of the ValueList type.Presentation of a report parameter that contains a value list is generated similarly to other report parameters.
Collaboration system.
Enhanced image quality during video calls from external users of the collaboration system.Image quality during video calls from external users of the collaboration system was insufficient.Enhanced image quality during video calls. Reduced load on slow client computers.
Collaboration system.
The CollaborationSystemUser.InfoBaseUserID property can be written now.

To change the InfoBaseUserID and MatchingKey properties of the CollaborationSystemUser object, the user must have the DataAdministration access rights.

The CollaborationSystemUser.InfoBaseUserID property could not be written.

To change the CollaborationSystemUser.MatchingKey property, the user did not require any special access rights.

Loss-free data transfer between different collaboration system servers.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
External reports and data processors.
New parameter for the Connect() method of the external data processor manager: LanguageCode. You can use this parameter to specify the current language for an external data processor to be connected.This feature was not provided.

When connecting an external data processor, the current language of the authenticated user was used. The language code is returned by the CurrentLanguage() global context method.

Open external data processors in the required localization language.
Data accelerator.
Licensing system.
Server clusters.
New feature: start several Data Accelerator instances within one server cluster. New feature: control the possibility of creation of several Data Accelerator instances using permissive and prohibitive functionality assignment rules.

PROF-level license allows you to use only one Data Accelerator instance in one server cluster. CORP-level license allows you to use an unlimited number of Data Accelerator instances in one server cluster.

Within one 1C:Enterprise server cluster.Load balance among several Data Accelerator instances. Improved performance of queries that use Data Accelerator.
Client application form.
Administration tools.
When saving form settings for another user (not the current one), new settings are applied in less than 20 seconds after saving. Form settings are settings that are located in the system settings storage and have a suffix of the /FormSettings settings key.

+

+

Form settings copied to another user were applied only after disconnecting from the infobase if this form had already been opened in a session by the user to which the settings were copied.Simplified copying of form settings to other infobase users.
1C:Enterprise script.
If you specify an error processing method when creating the NotifyDescription() object, this method receives management only when an error occurs within an asynchronous call where the created NotifyDescription object is passed.

This change is not implemented in 8.3.21 compatibility mode.

If you specified an error processing method when creating the NotifyDescription() object, this method received management in two cases. First case: an error occurred during an asynchronous call. Second case: an error occurred when executing a method that was called after an asynchronous call had been completed.

+

Eliminated unexpected system behavior.

+

Collaboration system.
The CollaborationSystemInfobaseRegistrationData object is now available in thin and web clients.The CollaborationSystemInfobaseRegistrationData object was available only in thick client and on the server. When passing a value of this type from the server to the thin client, the value was available as a value of the BinaryData type on the client side.

+

Eliminated unexpected system behavior.
Data composition system.
If the "Text" appearance parameter (specified in appearance of the data set field of the data composition schema) is used in report templates of the data composition system, the parameter value is displayed in a report.

This change is not implemented in 8.3.21 compatibility mode.

It is recommended that you analyze the "Text" appearance parameter use. If the data set field settings contain filled parameters that are not supposed to be displayed, clear their check boxes.

The "Text" appearance parameter (specified in appearance of the data set field of the data composition schema) was not used when displaying a report if a field with the same parameter was used in report templates of the data composition system.

+

Eliminated unexpected system behavior.

+

Data composition system.
The "Mark negatives" appearance parameter (specified in appearance of the data set field of the data composition schema) is used in report templates of data composition system and dynamic list templates. The NegativeTextColor style color is used in a report template cell of data composition system and the dynamic list if the field to be displayed contains a negative value. In data composition template in cell appearance, an expression of the data composition system template is created for the TextColor appearance parameter.

This change is not implemented in 8.3.21 compatibility mode.

The "Mark negatives" appearance parameter (specified in appearance of the data set field of the data composition schema) was used in report templates of data composition system and dynamic list templates. The NegativeTextColor style color was used in a report template cell and in the dynamic list of data composition system only if the cell contained a text where the first significant character was "-". The MarkNegatives parameter was created in the data composition template in the data composition appearance.Eliminated unexpected system behavior.
Charts.
The "Update" chart property is considered obsolete for Managed application mode. In web client, the property does not affect the chart behavior.In thin client, the "Update" chart property did not affect chart generation. In web client, the property operated correctly.The difference in chart behavior in web and thin clients is eliminated.

+

Web services and HTTP services.
Web client, web service, and HTTP service publishing tools.
Administration tools.
Improved performance of calling a web service method by optimizing the selection of a session suitable for call execution. There is no limit on session pool size. All web service calls are executed at once.

In the default.vrd file, the poolSize and poolTimeout attributes are deleted for items describing web services, HTTP services, and standard OData Interface.

When calling a web service, there was a limit on pool size of sessions that executed calls.

+

Improved performance of web service calls.
Administration tools.
According to the SetUserPasswordMinLength() method, a user password cannot contain less than 0 and more than 99 characters. If the restriction is violated, an exception is thrown. This change is not implemented in version 8.3.21 compatibility mode.

If the infobase checks user password complexity, the lower limit for password length is the maximum value of 7 and the specified minimum password length.

If the specified "Minimum user password length" infobase parameter exceeds 99, value 99 is used. This change is not implemented in version 8.3.21 compatibility mode.

If you clear the "Password complexity check" check box in the dialog box to set up infobase parameters, the "Minimum user password length" parameter value is not changed.

The SetUserPasswordMinLength() method did not impose restrictions on the minimum user password length.

When receiving a value of the "Minimum user password length" infobase parameter, the platform did not control the received value.

When you cleared the "Password complexity check" check box in the dialog box to set up infobase parameters, the "Minimum user password length" parameter was set to 0.

Eliminated unexpected system behavior.
Administration tools.
The default value for the IgnoreServerCertificatesChainRevocationSoftFail parameter of the conf.cfg file is True.The default value for the IgnoreServerCertificatesChainRevocationSoftFail parameter of the conf.cfg file was False.Now you can establish HTTPS connection (without additional system settings) if one or several servers with certificate revocation lists are unavailable.
Web client.
System requirements.
The following web browsers are no longer supported:
  • Microsoft Edge version 18 or earlier.
  • Microsoft Internet Explorer 10.
The following web browsers were supported in web client:
  • Microsoft Edge version 18 or earlier.
  • Microsoft Internet Explorer 10.
Obsolete web browsers are no longer supported.
Web client.
System requirements.
Development tools.
Microsoft Edge version 19 or later running Linux, macOS, and Windows is supported.

Video calls in Microsoft Edge version 64 or later are supported.

Progressive web applications in Yandex Browser and Microsoft Edge version 73 or later are supported.

New feature: debugging for web client in Yandex Browser and Microsoft Edge.

These features were not provided.Extended list of supported web browsers.

New system features that you can use in web client.

Full-text search.
New parameter for the conf.cfg configuration file: FtsJavaOpts. You can use it to configure settings of Java Virtual Machine used by full-text search version 2.This feature was not provided.You can set up Java Virtual Machine used by full-text search version 2.
External reports and data processors.
New parameter for the Attach() method of the external report manager: LanguageCode. Use this parameter to specify a language to be used as the current one in the attached external report.This feature was not provided.

The current language of authenticated user was used when attaching an external report. The code of this language was returned by the CurrentLanguage() global context method.

You can now open external reports in a required localization language.
XML and XDTO support.
When you import the XSD schema to the XDTO package, for properties whose items are included in the choice content model in the XSD schema description, values defined for these items in the XSD schema are specified as minimum values.When you imported the XSD schema to the XDTO package, the minimum value was always set to 0 for properties whose items were included in the choice content model in the XSD schema description.Eliminated unexpected system behavior.

Table of contents

Renamed objects

ObjectThe old nameThe new name
English name for the SystemOfLinearEquationsCalculation.SolveSystemOfLinearEquations() method.

+

  • SolveSystemOfLinearEquations.
  • SolveSystemsOfLinearEquations.

+

English name of the following appearance parameters of the data composition system:
  • MaximumHeight
  • MaximumWidth
  • MinimumHeight
  • MinimumWidth

To ensure compatibility, both new and former names will be used for parameter search from 1C:Enterprise language and import from XML.

In 8.3.21 (or later) compatibility mode, the former parameter names will be used for the English version of 1C:Enterprise language when exporting to XML.

+

 +
  • MaximumHeight
  • MaximumWidth
  • MinimumHeight
  • MinimumWidth

+

+

  • MaxHeight
  • MaxWidth
  • MinHeight
  • MinWidth
English name of the NotifyDescription property of the client application form.
  • NotifyDescription.

+

  • CallbackDescription.

+

English name of the ExecuteNotifyProcessing global context method.
  • ExecuteNotifyProcessing.

+

  • RunCallback.

+

English name of the OnCloseNotifyDescription property of the client application form.
  • OnCloseNotifyDescription.

+

  • CallbackDescriptionOnClose.
New parameter of the conf.cfg file that allows you to set up Java Virtual Machine to use the optimized restructuring feature.
  • JavaOpts

+

  • RestructJavaOpts

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile client.
New feature for mobile client in the standalone mode: automatically synchronize data with the main server. When editing standalone configuration data, you can specify that an object takes part in automatic exchange. Also, you can specify whether object changes need to be registered for automatic exchange purposes. New dialog box to configure automatic exchange with a standalone configuration.

New event handlers for the exchange plan object module: OnAutoCreateNewNode(), BeforeCreateInitialImage(), BeforeSendDataToSubordinate(), BeforeSendDataToMaster().

New standard attribute for the exchange plan: ExchangeDate.

New global context property: DataExchangeWithMainServer.

New application module event handler: AfterDataExchangeWithMainServer().

This feature was not provided. Synchronization could be executed only in 1C:Enterprise language.Simplified exchange between mobile client in the standalone mode and the main server.
Spreadsheet documents.
New feature in the mobile platform: view a spreadsheet document using the SpreadsheetDocument.Show() method or interactive opening.This feature was not provided.

+

View external spreadsheet documents in mobile platform applications.

+

Mobile client.
New feature for mobile client in the standalone mode: switch a collaboration system call to background mode. If you switch a call to background mode, the video stream will no longer be transmitted from your mobile device. On iOS, this feature is available starting from version 10. On Android, this feature is available on all supported versions.

New feature for mobile client: share your own screen and view the screen of another device using the collaboration system video stream. The screen is demonstrated even when the application is not active. On iOS, this feature is available starting from version 12. On Android, this feature is available on all supported versions.

New functionality for the list of used mobile device functionalities: Video conference.

Participation in a video call stopped after collapsing the mobile client application, switching to another application, or locking the device.

The screen demonstration used another protocol.

+

You can continue a call after switching the mobile application to background mode. New feature: you can share not only the mobile application screen but also the device screen. Improved performance when sharing the device screen.

+

Mobile client.
If a report form is used in mobile client in standalone mode when connection with the main server is lost, then:
  • A spreadsheet document field is not locked in the report form. Report form settings and commands become unavailable.
  • Commands for saving and printing a report become available.
  • Report decryption is not supported in this mode.
  • When opening a standalone report form, the current report form is not closed. If you select the Open online command, the offline report form is closed.
  • If the report is generated in background on the server, the report form displays the result after connection is restored. If generation is not completed, the report form waits for generation to be completed.
When a report form was used in mobile client in standalone mode and connection with the main server was lost:
  • The entire report form became unavailable for editing.
  • When opening the offline report form, the online report form was closed.

+

+

+

More user-friendly report behavior in mobile client after switching to standalone mode.

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
Mobile device-specific features.
Calls and text messages can be processed in the mobile application built for Android. To apply this feature, rebuild your mobile application using the mobile version 8.3.22 and configuration exported by Designer version 8.3.22.

If necessary, specify hint texts for the required mobile application functionality.

Calls and text messages in the mobile application built for Android could not be processed even when the mobile application functionality to be used was specified correctly.Eliminated unexpected system behavior.

+

DBMS operations.
System requirements.
The following version of PostgreSQL DBMS is supported now:14.4. +DBMS version bitness: x86-64. +The version is supported in 1C:Enterprise version 8.3.18 or later. +Supported operating systems are defined by a DBMS vendor.This PostgreSQL DBMS version was not supported.Extended list of supported DBMS.
Database configuration update.
The MergeCfg command in Designer batch mode is executed faster. The new command execution time matches the execution time of respective interactive operation.Execution of the MergeCfg command in Designer batch mode took more time.Eliminated unexpected system behavior.
XML and XDTO support.
New method for the XDTODataObject and XDTODataValue objects: Factory(). The method returns an object of the XDTOFactory type that was used to create an object or value in use.

When operating with XDTO objects (and saving them to XML), use one factory instance for all used objects.

This feature was not provided.If required, you can get an XDTOFactory object that was used to create an XDTO object or value.
System requirements.
1C:Enterprise platform now supports the 64-bit architecture of ARM processors including Baikal processors.

1C:Enterprise for ARM processors does not support:

  • Windows operation for ARM processors.
  • HASP dongles (only software licensing is supported).
  • Processors Apple M1 and later.
  • Elbrus processors.
  • Automatic update of client applications for thin client distribution packages intended for ARM processors.
  • Operations in the following DBMS:

New system enumeration value: PlatformType.Linux_ARM_64.

(read more)add-in development technology has been changed.

CORP license is required for 1C:Enterprise operation on ARM processors.

1C:Enterprise could not operate in systems running on ARM processors.Extended list of devices supported by 1C:Enterprise.
Add-ins.
Web client.
Extensions for file operations and cryptography are now supported in Yandex.Browser, Chromium-gost, and Microsoft Edge.

Documentation on (read more) add-in development technology has been changed.

Extension manifests and add-in adapters are installed in the following directories (registry keys):

  • Linux:

~/.config/yandex-browser/NativeMessagingHosts +~/.config/chromium-gost/NativeMessagingHosts +~/.config/chromium/NativeMessagingHosts +~/.config/microsoft-edge/NativeMessagingHosts

  • macOS:

/Library/Application Support/Chromium/NativeMessagingHosts

  • Windows (information on file location is recorded):

HKEY_CURRENT_USER\SOFTWARE\Chromium\NativeMessagingHosts +HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\NativeMessagingHosts

Extensions for file operations and cryptography were not supported for web client in Yandex.Browser, Chromium-gost, and Microsoft Edge.

Extension manifests and add-in adapters were installed in the following directories (registry keys):

  • Linux:

~/.config/google-chrome/NativeMessagingHosts +~/.mozilla/native-messaging-hosts

  • macOS:

/Library/Application Support/Mozilla/NativeMessagingHosts +/Library/Google/Chrome/NativeMessagingHosts

  • Windows (information on file location is recorded):

HKEY_CURRENT_USER\SOFTWARE\Google/Chrome\NativeMessagingHosts +HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts

Extended web client features in Yandex.Browser, Chromium-gost, and Microsoft Edge.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 10.21
  • Postgres Pro Standard 10.21.1
  • Postgres Pro Enterprise 10.21.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 10.21
  • Postgres Pro Standard 10.21.1
  • Postgres Pro Enterprise 10.21.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 11.16
  • Postgres Pro Standard 11.16.2
  • Postgres Pro Enterprise 11.16.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 11.16
  • Postgres Pro Standard 11.16.2
  • Postgres Pro Enterprise 11.16.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 12.11
  • Postgres Pro Standard 12.11.2
  • Postgres Pro Enterprise 12.11.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 12.11
  • Postgres Pro Standard 12.11.2
  • Postgres Pro Enterprise 12.11.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 13.7
  • Postgres Pro Standard 13.7.2
  • Postgres Pro Enterprise 13.7.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 13.7
  • Postgres Pro Standard 13.7.2
  • Postgres Pro Enterprise 13.7.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 14.4
  • Postgres Pro Standard 14.4.1
  • Postgres Pro Enterprise 14.4.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 14.4
  • Postgres Pro Standard 14.4.1
  • Postgres Pro Enterprise 14.4.1
Extended list of supported DBMS.
Collaboration system.
The storage scheme of separator values has been changed for some collaboration system objects in a distributed infobase.

After migration to version 8.3.22, collaboration system bots will be activated after one of the following events:

  • Connection to a client application infobase.
  • Call to the collaboration system from a server cluster.
The storage scheme of separator values for some collaboration system objects was different.Eliminated unexpected system behavior.
Mobile platform.
Mobile client.
Mobile device-specific features.
 +

You can interactively manage the camera backlight in the mobile application interface used for barcode scanning after calling the MultimediaTools.ShowBarcodeScanning() method. The backlight control button depends on whether the device has backlight and light sensor features. Backlight state is preserved between sessions.

This feature was not provided.

Camera backlight could be enabled only automatically. That did not allow users to enable it on devices without a light sensor.

Simplified barcode scanning by built-in tools in case of insufficient lighting on devices with supported camera backlight, but without a light sensor. +
Server clusters.
Performance of administration operations via the administration server (ras) has been improved.

The frequency and duration of periods when administration server connections might conflict with exclusive infobase access have been reduced. +

Administration operations via the administration server (ras) took more time.

Connection to a server cluster established by the administration server (ras) could result in more conflicts with exclusive infobase access.

Improved performance of server cluster administration operations via the administration server (ras).
Standalone server.
New commands for the SSH gateway of the standalone server:
  • config dump-external-data-processor-or-report-to-files. Dump an external report or data processor to XML files.
  • config load-external-data-processor-or-report-to-files. Load an external report or data processor from XML files. +New parameter for infobase config export commands to specify the location of an external data processor or configuration: --file. +New parameter for infobase config import commands to specify the location of an external data processor or configuration: --out.

+

These features were not provided.Extended standalone server features related to external reports and data processors.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 10.22.1
  • Postgres Pro Standard 10.22.1
  • Postgres Pro Enterprise 10.22.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 10.22.1
  • Postgres Pro Standard 10.22.1
  • Postgres Pro Enterprise 10.22.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 11.17.1
  • Postgres Pro Standard 11.17.1
  • Postgres Pro Enterprise 11.17.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 11.17.1
  • Postgres Pro Standard 11.17.1
  • Postgres Pro Enterprise 11.17.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 12.12.1
  • Postgres Pro Standard 12.12.1
  • Postgres Pro Enterprise 12.12.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 12.12.1
  • Postgres Pro Standard 12.12.1
  • Postgres Pro Enterprise 12.12.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 13.8.1
  • Postgres Pro Standard 13.8.1
  • Postgres Pro Enterprise 13.8.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 13.8.1
  • Postgres Pro Standard 13.8.1
  • Postgres Pro Enterprise 13.8.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 14.5.1
  • Postgres Pro Standard 14.5.1
  • Postgres Pro Enterprise 14.5.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 14.5.1
  • Postgres Pro Standard 14.5.1
  • Postgres Pro Enterprise 14.5.1
Extended list of supported DBMS.
System requirements.
Linux.
New supported Linux distribution packages:
  • Debian 11
  • Mint 21
  • Oracle Linux 9
  • RHEL 9
  • Ubuntu 22.04 LTS
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:
  • Debian 9
1C:Enterprise supported the following distribution packages for Linux operating system:
  • Debian 9
Outdated Linux distribution packages are no longer supported.
System requirements.
Mobile platform.
Mobile client.
Mobile applications built using the mobile 1C:Enterprise version 8.3.22.40 will meet Google Play store requirements related to uploading of new applications with in-app purchases.

For a mobile application to be uploaded to Google Play store, it must be built using the mobile 1C:Enterprise version 8.3.22.40 or later.

Starting from November 1, 2022, you will not be able to upload mobile applications with in-app purchases to Google Play store if such applications are built using mobile 1C:Enterprise versions earlier than 8.3.22.40.The mobile 1C:Enterprise version meets Google Play store requirements.
Mobile client.
Mobile platform.
The list of root certificates has been extended.Fewer root certificates were supported.Extended list of supported root certificates.
Standalone server.
Standalone server shutdown is improved.Previously, standalone server shutdown took more time.Accelerated standalone server restart after infobase configuration update.
Mobile platform.
Mobile client.
Mobile device-specific features.
Statistics library versions for the mobile platform and mobile client have been updated.The mobile platform and mobile client contained outdated versions of statistics libraries.Updated statistics library versions that meet Google Play store requirements.
System requirements.
Now 1C:Enterprise platform supports Elbrus-8S processors.
  • 1C:Enterprise for Elbrus processors does not support:

Windows.

  • HASP dongles (only software licensing is supported).
  • Thin client distribution packages assembled for Elbrus processors in automatic update tools of client applications.
  • DBMS:
    • IBM Db2.
    • Microsoft SQL Server.
    • Oracle
    • Data accelerator.
  • Local speech recognition.

Implemented a new system enumeration value: PlatformType.Linux_E2K.

Changed the development technology for URL1 add-ins.

To use 1C:Enterprise for Elbrus processors, you need to acquire a CORP license.

Previously, 1C:Enterprise did not support systems running on Elbrus processors.Extended list of devices supported by 1C:Enterprise.
DBMS operations.
System requirements.
Microsoft SQL Server 2022 is now supported.Microsoft SQL Server 2022 was not supported.New Microsoft SQL Server version is now supported.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 10.23.1
  • Postgres Pro Standard 10.23.1
  • Postgres Pro Enterprise 10.23.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 10.23.1
  • Postgres Pro Standard 10.23.1
  • Postgres Pro Enterprise 10.23.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 11.18.1
  • Postgres Pro Standard 11.18.1
  • Postgres Pro Enterprise 11.18.2

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 11.18.1
  • Postgres Pro Standard 11.18.1
  • Postgres Pro Enterprise 11.18.2
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 12.13.1,
  • Postgres Pro Standard 12.13.1,
  • Postgres Pro Enterprise 12.13.2.

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 12.13.1,
  • Postgres Pro Standard 12.13.1,
  • Postgres Pro Enterprise 12.13.2.
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 13.9.1
  • Postgres Pro Standard 13.9.1
  • Postgres Pro Enterprise 13.9.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 13.9.1
  • Postgres Pro Standard 13.9.1
  • Postgres Pro Enterprise 13.9.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 14.6.1
  • Postgres Pro Standard 14.6.1
  • Postgres Pro Enterprise 14.6.1

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 14.6.1
  • Postgres Pro Standard 14.6.1
  • Postgres Pro Enterprise 14.6.1
Extended list of supported DBMS.
System requirements.
DBMS operations.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 15.1.1
  • Postgres Pro Standard 15.1.1
  • Postgres Pro Enterprise 15.1.1
  • DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 15.1.1
  • Postgres Pro Standard 15.1.1
  • Postgres Pro Enterprise 15.1.1.
Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 10.22.

Supported processors: x86, x86-64.

The version is supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 11.17.

Supported processors: x86-64.

The version is supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 12.12.

Supported processors: x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 13.8.

Supported processors: x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 14.5.

Supported processors: x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 10.23.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 11.18.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 12.13.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 13.9.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 14.6.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 15.1.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 11.19.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.14 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 12.14.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 13.10.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 14.7.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
The following PostgreSQL DBMS version is supported now: 15.2.

Supported processors: ARM64, E2k, x86-64.

The version is supported in 1C:Enterprise version 8.3.18 or later.

Supported operating systems are defined by a DBMS vendor.

These PostgreSQL DBMS versions were not supported.Extended list of supported DBMS.
Internet-enabled functionality.
When the HTTPConnection, WSDefinitions, WSProxy, and WSReferences object are used on Linux and macOS, you can now use Kerberos authentication. This feature is implemented in the thick client and on the server.When the HTTPConnection, WSDefinitions, WSProxy, and WSReferences object were used on Linux and macOS, you could not use Kerberos authentication. This authentication type was supported only on Windows.When the HTTPConnection, WSDefinitions, WSProxy, and WSReferences object are used on Linux and macOS, you can use Kerberos authentication.
Full-text search.
Accelerated full-text search. Decreased the load on the processor upon searching.Full-text search took more time to find a result and significantly loaded the processor.Accelerated full-text search.
File operations.
In thick client, the BeginPutFile(), BeginPuttingFiles(), BeginPutFileToServer(), BeginPutFilesToServer(), PutFileToServerAsync(), and PutFilesToServerAsync() methods are executed on the main thread, but remain asynchronous. As a result, when these methods are executed, the user interface update is locked, but method programming interface keeps running.Executing the BeginPutFile(), BeginPuttingFiles(), BeginPutFileToServer(), BeginPutFilesToServer(), PutFileToServerAsync(), and PutFilesToServerAsync() methods in thick client could cause unexpected application shutdown.Eliminated unexpected system behavior.
Administration tools.
Client application installation.
Linux.
Now you can install 1C:Enterprise on Linux using RPM and DEB packages. The packages contain all the system components. To install or remove the application, use the package manager of the used operating system.

New parameters for the conf.cfg file: PublishDistributiveLocationLinuxDeb64, PublishDistributiveLocationLinuxDeb32, PublishDistributiveLocationLinuxRpm64, and PublishDistributiveLocationLinuxRpm32.

New attributes for the point item of the default.vrd file: pubdstlindeb32, pubdstlindeb64, pubdstlinrpm32, and pubdstlinrpm64.

New parameters for the pubdst parameter of the http section of the standalone server configuration file: lindeb64, lindeb32, linrpm64, and linrpm32.

Installation using the RUN file (the installer) will be supported and available along with the package files.

+

Previously 1C:Enterprise applications were distributed as RUN packages.Advanced options to install 1C:Enterprise components on Linux.
Development tools.
Now you can enable debugging over HTTP if the 1C:Enterprise server cluster is configured to start automatically on Linux. To enable the debugging protocol, use the SRV1CV8_DEBUG parameter of the server cluster configuration file.Previously if the 1C:Enterprise server cluster on Linux was configured to start automatically upon the operating system startup, the HTTP debugging protocol was not supported. Only the TCP debugging protocol was supported.Eliminated unexpected system behavior.
System requirements.
DBMS operations.
Web services and HTTP services.
The following versions of Postgres Pro DBMS are supported now:
  • Postgres Pro 1C 11.18.1
  • Postgres Pro Standard 11.18.1
  • Postgres Pro Enterprise 11.18.2

DBMS version bitness: x86-64.

The versions are supported in 1C:Enterprise 8.3.16 or later.

Supported operating systems are defined by a DBMS vendor.

+

The following versions of Postgres Pro DBMS were not supported:
  • Postgres Pro 1C 11.18.1
  • Postgres Pro Standard 11.18.1
  • Postgres Pro Enterprise 11.18.2.
Extended list of supported DBMS.
Accounting registers.
Improved features when operating with accounting registers:
  • The query that is executed when filter by extra dimensions is applied in the Filter parameter of virtual tables of the accounting register and in case of unspecified ExtDimensionTypes parameter has been optimized.
  • The query that is executed when filters by date range including period adjustment are applied in virtual tables has been optimized.
Some queries to accounting registers were not optimal.Faster data acquisition from accounting registers.
Distributed infobases.
When operating with a distributed infobase, objects are exported to the file of changes in the following order:
  • Constants
  • Charts of characteristic types
  • Charts of accounts
  • Charts of calculation types
  • Catalogs
  • Other reference objects of the infobase (without defined sequence)
  • Register record sets (without defined sequence)
  • Calculation register records
  • Sequence data
When operating with a distributed infobase, the export order to the file of changes was undefined.Decreased number of inconsistent infobase states during exchange (before its completion) due to defined exchange order.
Infobase verification and repair.
During infobase verification and repair, logical and referential integrity check of an infobase can be performed for specific object types (constants, catalogs, documents, and so on). Regardless of selected object types, some checks are still performed for all object types.

New parameter values for the -LogIntegrity and -LogAndRefsIntegrity parameters of the /IBCheckAndRepair command:

  • Constants
  • Catalogs
  • Documents
  • DocumentJournals
  • ChartsOfCharacteristicTypes
  • ExchangePlans
  • ChartsOfAccounts
  • ChartsOfCalculationTypes
  • InformationRegisters
  • AccumulationRegisters
  • AccountingRegisters
  • CalculationRegisters
  • BusinessProcesses
  • Tasks
  • Other
This feature was not provided.Logical and referential integrity check of an infobase can be performed more precisely by required object types.
Add-ins.
When you attach and install an add-in using the AttachAddIn(), InstallAddIn(), or AttachAddInAsync() methods, the add-in file is cached as earlier. At the same time, for add-ins that are attached from infobase data, data changes are tracked. The check is performed when the add-in is attached but no more than once per second. If the data is changed since the last add-in attachment, add-in cache is cleared for this add-in. Next time the add-in is attached, it is extracted from the data again. For metadata objects without a record version, cache is cleared when you access the data but no more than once per second.Previously, when you attached and installed an add-in using the AttachAddIn(), InstallAddIn(), or AttachAddInAsync() methods, the add-in file was cached in a temporary directory on the server to improve the performance when reusing the add-in. However, if the add-in was obtained from the infobase, you could not understand that the add-in version in the cache had become different from the add-in version in the infobase until you restarted the client application.Improved add-in management.
Server clusters.
System requirements.
Linux.
Now the server cluster on Linux always requires a server license in the same way as the server cluster on Windows.Previously, the server cluster on Linux allowed running up to 12 client sessions without a server license if the server cluster consisted of one production server with one working process.Now you cannot use the server cluster on Linux without a license. Unexpected system shutdown due to the lack of a 1C:Enterprise server cluster license is eliminated.
Print tools.
HTML support.
Now you can save print settings for an HTML document field to the system settings storage in thin and thick client applications. The settings are saved when you change them in the Print options dialog box for an HTML document field and are read before you open the Print options dialog box, as well as when you print/preview an HTML document field.This feature was not provided. +An HTML document field was always printed with the default settings.Now it is more convenient to print data from an HTML document field as the previously specified settings will be used and you will not have to specify them again every time.
Client application.
New parameters that define traffic compression modes between the client and the server cluster for the /TComp command-line option of the thin client: lz4 and zstd. The default value is zstd.The default traffic compression parameter was -SDC.Now you can more flexibly manage traffic compression between the client application and the 1C:Enterprise server cluster.

In -zstd compression mode, the amount of traffic transmitted between the client and the 1C:Enterprise server cluster is reduced.

DBMS operations.
The system now supports PostgreSQL DBMS version 16 (x86-64).This PostgreSQL DBMS version was not supported.Reduced number of certificate check errors when accessing Russian websites.
Administration tools.
Now the root certificates of the Ministry of Digital Development, Communications and Mass Communications of the Russian Federation generated using the GOST R 34.11-2012 algorithms are added to the cacert.pem and cacertnx.pem files.This feature was not provided.Reduced number of certificate check errors when accessing Russian websites.
Localization.
Localized client application interface for Portuguese (Brazil), (pt_BR).This feature was not provided.Users who speak the Brazilian dialect of Portuguese can use 1C:Enterprise.
Client application installation.
New feature: when you install a client application, when updating over HTTP or from a self-extracting application installer (created by the 1CEClientSetupMake utility) running on Windows 8.1 and earlier, the system warns that it is impossible to verify the installer signature and that the installation is running on an outdated version, and allows you to cancel the installation.

When you install a client application (when updating over HTTP) running on Windows 8.1 and earlier, you can also disable signature verification of a new version of the client application installer. The checkbox is stored in the DisableInstallerVerification parameter of the 1cestart.cfg configuration file.

Previously, when you installed a client application, when updating over HTTP or from a self-extracting application installer (created by the 1CEClientSetupMake utility) running on Windows 8.1 and earlier, you could not install the client application as it was impossible to verify the digital signature of the installer.Simplified diagnostics of the situation that occurs when trying to install current versions of a client application running on outdated Windows-based operating systems (version 8.1 and earlier).
DBMS operations.
The system now supports PostgreSQL DBMS version 17 (x86-64).This PostgreSQL DBMS version was not supported.Extended list of supported PostgreSQL DBMS versions.

Table of contents

Transition from the previous version to the version 8.3.22

Table of contents

Version 8.3.21

Version 8.3.21 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.20 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.19 was available.Configurations developed using 1C:Enterprise platform version 8.3.20 or earlier can now run on version 8.3.21 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.21 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.20 after the migration to version 8.3.21, even if you disable the compatibility mode (simply enable it again).
Dynamic lists.
You can now get a URL to an object or a record of the current dynamic list row without having to open the object/record form.

New form table extension property for the dynamic list: AllowGetCurrentRowURL. New event handlers for the form table extension for a dynamic list: URLListGetProcessing and URLGetProcessing.

The dialog box for getting a form URL is upgraded considering this feature.

The dialog box for getting a URL on the home page displays all the URL options received from all forms on the home page.

Getting a URL to an object or a record of the current dynamic list row without having to open the object/record form was unavailable.

On the home page, getting a URL of any home page form from one dialog box was unavailable.

Improved and simplified interface for getting a URL in a dynamic list or on the home page.
Dumping configurations to files/Restoring configurations from files.
Standalone server.
Development tools.
You can now export the application to the zip. archive of XML files. New feature: multi-threaded application export on the server cluster side.

The Dump configuration to files command in Designer allows you to set the export method (on the server/on the client), the number of simultaneous export threads, and the need to archive the export file.

To enable this feature, a special parameter is implemented for the following import tools:

  • Command line to start 1C:Designer. New parameter for the /DumpConfigToFiles command: -Server, -Archive, -JobsCount.
  • 1C:Designer in the agent mode. New parameters for the config dump-config-to-files command: --archive, --server, --threads.
  • Standalone server management utility (ibcmd). New parameters for the infobase config export commands: --archive, --server, --threads.
This feature was not provided.Improved performance of the application export to XML files. Now you can export files to another computer in a ZIP archive.
Data display.
New pictures in the picture library:
  • RotateClockwise
  • RotateCounterclockwise
The listed pictures were not available in the picture library.The picture library is upgraded.
Processing PDF documents.
You can now view and print PDF documents using 1C:Enterprise platform tools. You can view and verify digital signatures in documents. Encrypted documents are now supported. Current restrictions are listed in the documentation.

New object: PDFDocument. New field form kind for the client application: PDFDocumentField.

New global context methods: PasswordProtectedDocument() and PasswordProtectedDocumentAsync().

New methods for the PDFAttachmentCollection object: Clear() and Delete().

New properties for the PDFDocumentFileType system enumeration: PDF, PDF_A_1, PDF_A_2, and PDF_A_3.

New properties for the ErrorCategory system enumeration: IncorrectPassword and SignatureCheckError.

This feature was not provided.

Only PDF document generation was available.

Advanced PDF document features.

+

Internet-enabled functionality.
New feature for the HTTPConnection object: use client certificates supporting GOST algorithms. CryptoPRO CSP is now supported on Linux and macOS.

New parameter for the conf.cfg configuration file: CryptoAPILibraryLocation.

New objects: LinuxClientCertificate, OSCertificateSelectMode, and OSClientCertificate.

The OpenSSLSecureConnection object constructor can take the OSClientCertificate object as the value of its ClientCertificate parameter.

+

+

Client certificates supporting GOST algorithms were not supported.Extended list of certificate kinds used for the HTTPConnection object operations.
Client application form.
New feature: display the Gantt chart with a table that contains additional data for the chart values.

New feature: expand the form table for the Gantt chart.

New property for the GanttChart object: DataColumns. New method for the GanttChart object: FindValueByID().

New property to expand the form field for the Gantt chart: TablePosition.

New properties for the GanttChartValue object: ID and Data.

New properties for the GanttChartPlotArea object: ShowPointsText and ShowData. +New property for the FormField object Table.

This feature was not provided. The Gantt chart could only display the point names created for the chart series.

+

Advanced Gantt chart features.
Database copies.
New feature to update a database copy when using standard replication. This feature applies specialized DBMS tools of the main database. The new feature is used only for Microsoft SQL Server DBMS that records changes.

New methods for the DatabaseCopiesManager object: GetStandardReplicationVersion() and InstallStandardReplicationVersion().

This feature was not provided.Improved performance of database copy update when using the new database copy update tool.
Internet-enabled functionality.
New feature: use the JWT token (URL44 standard) for authorization in online services of 1C:Enterprise platform. You can also create and verify a JSON Web Signature (JWS).

New object: AccessToken.

New method for the HTTPRequest object: AddAccessToken(). New property for the InfoBaseUser object: AccessTokenAuthentication.

New item for the defaul.vrd file: <accessTokenAuthentication>.

New startup command line commands for thin and web clients: /AccessToken.

This feature was not provided.Advanced access token features and improved security when using online services.
Error handling.
In the dialog box that appears in case of infobase connection errors, you can now view information that will help you understand why a certain error occurred and who you need to contact in case of such error.

New object: StartupErrorProcessingSettings. New methods for the ErrorProcessingManager object: SetStartupErrorProcessingSettings() and GetStartupErrorProcessingSettings().

New parameters for the infobase connection parameters described in the *.v8i file: StartupErrorHelpURL and StartupErrorHelpText.

This feature was not provided.

A link to supporting information could be placed only in the dialog box for entering the username and password.

Connection errors of the client application to the infobase are now more comprehensible to users.
Command interface.
When selecting a subsystem, you can now execute only one command of this subsystem.

New property for the Subsystem metadata object: UseOneCommand.

This feature was not provided.Simplified application usage with only one subsystem command available to a user.
Web client.
Internet-enabled functionality.
You can now take advantage of HTTP requests in web client. Provided features are limited by web browser capabilities.

The following objects are available in the web client: HTTPConnection, HTTPRequest, HTTPResponse, and OpenSSLSecureConnection. Synchronous object methods are not supported in web client.

This feature was not provided.Advanced web client features for Internet resources.
Internet-enabled functionality.
New feature in client applications (thin, mobile, thick, and web clients): asynchronous HTTP requests.

New methods for the HTTPConnection object: CallHTTPMethodAsync(), WriteAsync(), ChangeAsync(), PostAsync(), GetAsync(), GetHeadersAsync(), and DeleteAsync().

The CallHTTPMethod(), Write(), Change(), Post(), Get(), GetHeaders(), and Delete() methods of the HTTPConnection object are considered obsolete for client applications and supported for compatibility reasons. Specified methods are available only on the server application side.

1C:Enterprise did not support asynchronous HTTP request execution. Only request execution timeout could be specified.Asynchronous data exchange with various Internet resources.

+

Configuration extensions.
Common attributes / Data separation.
New feature: include your own extension objects in adopted common attributes being separators.

New feature: install extensions that extend data simultaneously for the whole infobase as well as for a specific data area.

Including your own extension objects in adopted common attributes being separators was not supported.

An extension that extends data could be installed in a specific data area or for the whole infobase. Simultaneous installation of such extensions was not supported.

The configuration extension now provides more features.
Applied objects.
Dynamic lists.
Data composition system.
When setting up application object characteristics, you can now specify that a characteristic can contain more than one value. This feature is implemented in the data composition system and dynamic list.

New properties for the CharacteristicsDescription object: MultipleValuesUseField and MultipleValuesKeyField. MultipleValuesOrderField.

If multiple characteristics are specified in the infobase, data can be duplicated as a result of data composition when migrating to previous platform versions. It is not recommended that you use previous versions of 1C:Enterprise after specifying multiple characteristic values.

More than one value could not be specified in object characteristics.Support of multiple values in required characteristics. For example, WiFi frequency bands, materials used for goods, and so on.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Collaboration system.
You can now create a new conversation during a video call in the collaboration system. The current video call participants are added to the conversation participants.

In the video call window, there is a submenu for the Go to conversation button containing the following commands: Go to conversation and New video call conversation.

Participants could go to a conversation during a video call only if a video call was started from a conversation. If a video call was started from the collaboration system menu, to exchange text messages on the discussed topic, a user had to manually create a new conversation and add all video call participants to it.Fast creation of a text chat (and access to it) during a video call.
Error handling.
New feature: view About window in the dialog box that generates an error report.This feature was not provided.Access to error environment details (application and platform version, connection mode, user, infobase name, and so on) when generating an error report.
Error handling.
Web client.
If a web client connects to an infobase using the HTTPS protocol, this infobase was accessed from this computer before, and the web browser supports the service-worker technology, a special page will be displayed in case of a connection error (similar to the exit page). This page will display connection error information and various supporting information. The page will be functionally identical to the connection error form in thin client, but its implementation will depend on web application specifics.This feature was not provided.The same view of the infobase connection error via HTTPS and errors in web applications.
Collaboration system.
When working via a video server, the image quality in a video call in the speaker view mode has been improved.

When working via a video server, the load on the client computer is reduced when all subscribers in a group video call are displayed in the gallery view mode.

When working via a video server, the image quality in a video call in the speaker view mode was insufficient.

When working via a video server, the load on the client computer was significant when all subscribers in a group video call were displayed in the gallery view mode.

Improved video call quality via a video server.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Client application form.
Optimized transfer of tables from the server to the client in the client application form. If some table rows are changed on the server, only the rows with changed columns are transferred to the client. Only the lines previously transferred to the client side are modified. The transfer is carried out in portions of 35 rows (or less). If more than 105 rows are changed on the server (3 portions of 35 rows), then after transferring three portions of 35 rows each, all table rows are transferred to the client. If a form is opened, no more than 35 rows are trensferred to the client.When a form was opened, only the displayed table part was transferred to the client. In case of any change of the table on the server, the entire table was transferred to the client. With a large table, this could take a long time and even cause run-time errors.Improved performance of the client application form when a small number of rows are changed in a large table on the server (in one call).
Server clusters.
Improved working process cache: frequently used objects are stored for longer periods and rarely used objects are deleted sooner. Reduced memory consumption by the working process, improved operation stability, and reduced probability of restarting cluster working processes when the memory threshold is exceeded.The working process cache of server clusters had a different operation procedure. This could lead to increased RAM consumption by the working process.Reduced memory consumption by the working process, improved operation stability, and reduced probability of restarting cluster working processes when the memory threshold is exceeded.
Common objects.
Improved setting of values in the ValueTable object if the column where a value is specified participates in the index created for the value table. The following operations take less time now (not limited to this list):
  • Setting a value to a column.
  • Copying a value table.
Setting a value to the ValueTable type object column that participated in the index was very time-consuming.Improved performance when changing values in the ValueTable type object columns that participate in the indexes created for the value table.
Full-text search.
 +

Improved full-text search by the beginning of a word. The improvement is manifested when performing a full-text search from 1C:Enterprise language with a search string of the "sear*" kind or when using the global search field.

Full-text search by the beginning of a word took more time.Improved performance of full-text data search.
Metadata objects.
Improved performance of the application that contains numerous metadata objects, including improved:
  • The Value(EnumerationID) query language expression.
  • Operations of a user with numerous roles.
Performance of the application that contains numerous metadata objects was insufficient.Improved performance of applications with numerous metadata objects.
Spreadsheet documents.
In thin client, the display of a spreadsheet document that contains a large number of merged cells and columns is improved.In thin client, the display of a spreadsheet document that contains a large number of merged cells and columns took longer.Improved display of spreadsheet documents with a complex structure.
Development tools.
When trying to view a large collection in the Expression dialog box, the collection is received by Designer (for display) in portions. As a result, you do not have to spend a lot of time to view the collection.When trying to view a large collection in the Expression dialog box, the entire collection was received by Designer (for display). This caused significant delays and could lead to disconnection from the debug item.Viewing large collections in the Expression dialog box is more convenient for developers.
Full-text search.
Preparing full-text search results for users takes less time now.

In full-text search results, the first exact match of the search word (if there is one) is always highlighted. If there is no exact match, the first found form of the search word is highlighted.

Preparing full-text search results for users took longer.

In full-text search results, the first found form of the search word was always highlighted.

Displaying search results to users takes less time.

Search text in search results is highlighted more correctly.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Web client.
Client application form.
In web client, the indent between a picture and a page title text as well as the indent from page edges depend on the font size of all Page items of the current form.In web client, the indent between a picture and a page title text as well as the indent from page edges depended on the font size of a Page item.The web client behavior is now identical to the thin client behavior.
Queries.
When working in the thick client, the QueryWizard object constructor can be called with an empty query text. In this case, the default constructor is called.When working in the thick client, the QueryWizard object constructor threw an exception if the constructor parameter value was an empty string.Unified behavior of the QueryWizard object constructor in different client applications.
Error handling.
Extended features when working with errors for application developers. New features: define exception codes for your own exceptions; throw an exception based on another exception. The presentation of errors generated from the application code has been changed.

New parameters for the Raise operator: Category, Code, AdditionalInformation, and Cause. When specifying more than one parameter, the operator can be written only in the functional form (with parameters enclosed in parentheses).

New system enumeration property: ErrorCategory.ConfigurationError.

New properties for the ErrorInfo object: Code and AdditionalInformation.

New parameters for the getInfo query of the error registration service: errorCategories, clientID, and reportID. New error report properties: id (contains the reportID value from the getInfo query) and dump.reasonForNoDump (contains the reason why a report does not contain a crash dump).

New properties for the ErrorProcessingSettings object: SendReportAtServer, SendCrashReportAtServer, SendCrashReportToPlatformErrorRegistrationService, IncludeUserNameInReportAtServer, IncludeInfobaseInformationInReportAtServer, IncludeDetailErrorDescriptionInReportAtServer.

These features were not provided.Extended features for error operations. You can now create codes for application errors. Extended API features of the error registration service.
1C:Enterprise language.
The Undefined value can now be used as a key for the objects of the Map and FixedMap types. This feature was already available in the web client.

This change is not implemented in 8.3.20 version compatibility mode.

The Undefined value could be used as a key for the objects of the Map and FixedMap types only in the web client.Possible use of the Undefined value as a key for the objects of the Map and FixedMap types.
XML and XDTO support.
For the WriteXML() and XDTOSerializer.WriteXML() global context methods, you can now pass a metadata object of the following types as the Value parameter: a catalog, a document, a chart of characteristic types, a chart of accounts, a chart of calculation types, an information, accumulation, or accounting register, a constant, a business process and task. All metadata object data available to the user that writes data will be written.This feature was not provided. Export of all configuration object data to XML was unavailable. Data had to be sorted and each data item had to be exported separately.Improved performance of data export from the application.
URLs.
New feature: get a URL with its presentation. New radio button in the dialog box for getting a URL: Copy name. The dialog box to follow a link, the global search, and the collaboration system consider that the clipboard may contain a URL with a presentation.This feature was not provided.Simplified simultaneous receiving of a URL and a presentation of the object to which this URL refers.
Common objects.
New feature: generate UUIDs of versions 1, 3, 4, and 5. New parameters for the UUID object constructor for creating IDs of the required version.

New system enumeration: UUIDVersion.

This feature was not provided. Only version 4 IDs could be generated by 1C:Enterprise platform.Now application developers can generate a UUID version required to complete a specific task.
Internet-enabled functionality.
If the HTMLDocumentField form item in thin and thick clients displays a URL that requires an SSL certificate, and this certificate contains any errors (for example, it is invalid), a page with error details will be displayed, and you will be offered to continue working with the URL or close it.If the HTMLDocumentField form item in thin and thick clients displays a URL that requires an SSL certificate, and this certificate contains any errors (for example, it is invalid), an error message will be displayed in the field and further operations with the required URL will be unavailable.Improved troubleshooting of problems with URLs displayed in the client application. Access to resource operations in cases where such operations are not recommended, but the user is confident in their actions.
Database copies.
Data Composition System.
If during the execution of a data query to a copy, an error occurs related to the copy used in the query, the copy is no longer used in all existing or new sessions until the copy is updated or the server cluster is restarted.

If an error is caused by a copy during the execution of the report created in the Data Composition System that contains several data sets or a hierarchical data set, the data access error will be displayed to the user. In other cases, as well as if a report/query does not require using only a database copy, an error is not displayed to the user, and the query is automatically re-executed in the main database or in one of the available database copies (except for the copy with an error).

This feature was not provided.

The copy in which an error occurred had to be manually disabled. After restarting the cluster or updating the copy, it had to be included in the used copies again.

When working with database copies, the damaged copy is disabled automatically without user intervention. If a query can be generated without the damaged copy of the database, the user will not notice the copy failure. The user will receive an error message only if a data query cannot be completed without the data of the database copy, all copies are marked as damaged, and queries to them are not executed.
Full-text search.
Full-text search correctly processes situations with numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items.

To enable this feature, the user must create an index in compatibility mode with version 8.3.14 or later (including the "Do not use" value).

+

Full-text search index could be incorrect in case of numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items in the infobase.Eliminated unexpected system behavior.
Spreadsheet documents.
When converting a spreadsheet document to compact mode used on mobile devices, the AutoIndent property is used to align text in cells.When converting a spreadsheet document to compact mode used on mobile devices, only the Indent property was used to align text in cells.Improved spreadsheet documents view on mobile devices.
Collaboration System.
 +

If screen sharing is enabled during a video call in thin or web clients, the video call window switches to the compact display mode. New feature: minimize the compact video call window to the heading size.

If screen sharing was enabled during a video call in thin or web clients, the video call window disappeared from the screen. The users that shared the screen could not tell whether they had listeners or not.

+

Improved screen sharing during a video call.

+

Spreadsheet documents.
When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the Sheet1 name is set in the resulting document for the Microsoft Excel sheet. In version 8.3.20 compatibility mode, this behavior is not changed.

When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the document sheet panel is not hidden.

When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the TDSheet name was set in the resulting document for the Microsoft Excel sheet.

When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the document sheet panel was hidden.

+

Eliminated performance issues when trying to open a document with a hidden sheet panel in Microsoft Excel. The naming of sheets in the resulting Microsoft Excel document is more understandable and predictable now.
Collaboration system.
You can now enable support for specific types of audio devices (multichannel microphones and audio systems) in the Collaboration System. This feature is enabled separately in the settings dialog box for video and sound in the Collaboration System settings. The user can use this feature in case of problems with capturing or playing audio on their computer.Some users had sound problems when making video calls.Extended list of supported audio devices in thin client.
Data composition system.
When displaying list templates of the data composition system in the lower-right cell of the template, the cell is no longer vertically merged with an empty cell in the row below.

This change is not implemented in 8.3.20 compatibility mode.

When displaying list templates of the data composition system in the lower-right cell of the template, the cell was vertically merged with an empty cell in the row below.Eliminated unexpected system behavior.
Dynamic list.
If a dynamic list contains a visible field whose type consists of a string of unlimited length and any other type (except for NULL and Undefined):
  • You can use the search string in this dynamic list.
  • Such field will not be in the list of available filter fields.

In version 8.3.20 compatibility mode, the behavior has not changed.

If a dynamic list contained a visible field whose type consisted of a string of unlimited length and any other type (except for NULL and Undefined):
  • You could not use the search string in this dynamic list (an error was generated).
  • If such field was in the list of available filter fields, any attempt to apply filter by this field resulted in an error.
Eliminated unexpected system behavior.
Add-ins.
New method for the program and add-in interface: SetUserInterfaceLanguageCode(). It is used to transfer an interface localization language of the client application to the add-in. The SetLocale() method is considered deprecated. The technology for creating add-ins has been changed (read more).

It is recommended that you use the new method of getting the interface localization code for the current add-in.

The SetLocale() method was used to transfer an interface localization language of the client application to the add-in. This method worked differently in different client applications and with different interface localization languages.Unified method of transferring information about a client application localization language to the add-in.
Data display.
Spreadsheet document.
If the print scale of a spreadsheet document is set to "Fit page width" in the print parameters, and the page width is not enough to fit the whole document, then when exporting a spreadsheet document to Microsoft Word format, the document is scaled similarly to the scaling applied by 1C:Enterprise when printing a spreadsheet document: the column width, the row height, and the font size are changed.

In version 8.3.20 compatibility mode, the behavior has not changed.

If the print scale of a spreadsheet document was set to "Fit page width" in the print parameters, and the page width was not enough to fit the document, then when the spreadsheet document was exported to Microsoft Word format, the document was not changed in the way 1C:Enterprise system would change this spreadsheet document when printing.If the print scale is set to "Fit page width" for a spreadsheet document, the printed document and the document exported to Microsoft Word format will be almost identical.
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is 2.14.The format version of configuration dump to XML files was 2.13.Configuration dump to XML files supports new platform features.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Client application form.
When trying to change the form attributes or dynamic list settings from 1C:Enterprise language, adding an attribute/column with a duplicate name will result in an exception.

This change is not implemented in 8.3.20 version compatibility mode.

When trying to change the form attributes or dynamic list settings from 1C:Enterprise language, adding an attribute/column with a duplicate name did not cause adding errors. Access to such attribute from 1C:Enterprise language was impossible.Eliminated unexpected system behavior.

+

Linux.
Administration tools.
Server clusters.
When using a 1C:Enterprise server cluster running on Linux, the SystemV subsystem for initialization and management of services will no longer be used. The systemd subsystem (similar to the previously mentioned one in terms of purpose) is used instead.

The distribution package includes a systemd-scenario for starting a server cluster and an administration server (ras) and their configuration files.

The SystemV-scenario for starting a server cluster (and its configuration file) was deleted from 1C:Enterprise distribution package.

After migration to a new version, you need to reconfigure the functionality to automatically start a server cluster.

 +

When using a 1C:Enterprise server cluster running on Linux, the SystemV subsystem for initialization and management of services was used.

Improved startup and configuring of 1C:Enterprise service instances for system administrators working on Linux including (if required) multiple startups of different instances.
Add-ins.
New feature: import add-ins in a separate process separated from 1C:Enterprise platform processes. In this case, abnormal add-in termination will not result in the abnormal platform termination, but the add-in reattachment will be required.

The add-in creation technology has been changed. An add-in can now provide the platform with information about available add-in operation modes and current URL1 mode.

New parameter for the AttachAddIn() method (and all asynchronous analogs): AddInAttachmentType. New method: CheckAddInAtachment().

New event: AddInDetachmentProcessing. It is called upon abnormal termination of the add-in operating process.

It is recommended that you develop add-ins that support the isolated operation mode. When using add-ins on the client side, it is recommended that you provide a reload code in case of abnormal add-in termination.

When developing configurations in the compatibility mode with version 8.3.20 or earlier, isolated add-in import is recommended if the add-in can run in a separate process.

This feature was not provided.

Add-ins were imported only to the address space of 1C:Enterprise platform process that used this add-in. Abnormal add-in termination resulted in the abnormal termination of 1C:Enterprise process.

Improved stability of add-ins.
Administration tools.
If OS updates were automatically installed before the platform was installed, or the updated files were used by other applications, after installing the platform you will see a warning stating that a computer restart might be required. +

If OS updates were automatically installed before the platform was installed, or the updated files were used by other applications, after installing the platform the computer was restarted without a warning. That could lead to data loss of the user who installed 1C:Enterprise.

Improved installer behavior for cases when a computer restart is required to complete the installation.
Client application.
When connecting to the infobase via HTTP using thin or web clients, the /UC command can be specified in the startup command line if the session start is locked with an unlock code.When connecting to the infobase via HTTP using thin or web clients, the /UC command in the startup command line was ignored.Possible connection to the infobase via HTTP for the user knowing the unlock code even if the session start is locked.
Error handling.
If the technician mode is enabled in the user session, the interpretation of the Auto value of the ErrorProcessingSettings.MessageDisplayVariant property is changed:
  • If the technician mode is enabled, Auto is interpreted as BriefErrorDescription.
  • If the technician mode is disabled, Auto is interpreted as ErrorMessageForUser.

This change is not implemented in 8.3.20 compatibility mode.

The Auto value of the ErrorProcessingSettings.MessageDisplayVariant property was always interpreted as ErrorMessageForUser.Simplified troubleshooting and problem solving due to errors being displayed in a more technical form for developers and technicians.
Configuration extensions.
New feature: create your own predefined items for adopted objects of the following types: catalogs, charts of characteristic types, charts of accounts, and charts of calculation types. Predefined items can be adopted or native.

This change is not implemented in 8.3.20 compatibility mode.

This feature was not provided.The configuration extension now provides more features.

+

DBMS operations.
For PostgreSQL, Oracle Database, and IBM DB2 DBMS, a query language expression containing a multiple B operator with a subquery is translated to the DBMS language using the EXISTS() operator. After the change, the multiple B operator with a subquery always returns a Boolean type value. This change is not implemented in 8.3.20 compatibility mode.

It is recommended that you check the use of queries that contain the multiple B operator with a subquery in applications.

+

For PostgreSQL, Oracle Database, and IBM DB2 DBMS, a query language expression containing a multiple B operator with a subquery was translated to the DBMS language using the multivalue IN operator. The EXISTS() operator was used in Microsoft SQL Server DBMS and the file mode of the infobase. Because of that, the query language expression could return different values in different DBMS.Unified behavior of the multiple B operator with a subquery for all supported DBMS.

+

Data composition system.
The Data Composition System does not display records from other periods in the report if the following grouping is specified: field-period - field not being a period - field-period.

In version 8.3.20 compatibility mode, this behavior is not changed.

The Data Composition System displayed records from other periods in the report if the following grouping is specified: field-period - field not being a period - field-period.Eliminated unexpected system behavior.
Data composition system.
When generating a data composition template, if some optional connection of a data set query is considered used (in the data composition settings, a field from the tables of this connection is used), connections with tables whose fields are used in this connection are also considered used.

In version 8.3.20 compatibility mode, this behavior is not changed.

When generating a data composition template, if some optional data set query connection is considered used (in the data composition settings, a field from the tables of this connection is used), connections with tables whose fields were used in this connection were not considered used.The behavior of the data composition template generator is now more predictable.
Full-text search.
If a full-text search query contains the * character surrounded by quotation marks, for example, "table*", the expression is interpreted as a search for the * character, not as a metacharacter.If a full-text search query contained the * character, such expression was always interpreted as a metacharacter, no matter how the search string was formatted.Eliminated unexpected system behavior.
Dynamic list.
The dynamic list key fields are added to the end of the list of order fields in the data composition system settings obtained by calling the form table extension method for the GetPerformingDataCompositionSettings() dynamic list if these fields are specified in the Key fields property of the dynamic list. As a result, data sorting performed according to such settings will always be stable.

It is recommended that you analyze all places where the GetPerformingDataCompositionSettings() method is used for dynamic lists with any key and make sure that the resulting settings are not imported to the dynamic list settings. The resulting settings can be used only with the data composition schema obtained by calling the GetPerformingDataCompositionScheme() method of the form table extension for the same dynamic list.

Dynamic list key fields were not added to the end of the list of order fields in the data composition system settings obtained by calling the form table extension method for the GetPerformingDataCompositionSettings() dynamic list. As a result, data sorting performed according to such settings could be unstable.Consistently stable sorting of data obtained using the executable data composition schema and the executable data composition settings of the dynamic list.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Properties of the ErrorProcessingSettings object. The former names are supported for compatibility purposes.
  • IncludeUserNameInReport,
  • IncludeSystemInfoInReport,
  • IncludeDetailErrorDescriptionInReport,
  • IncludeInfobaseInformationInReport,
  • IncludeWindowsPictureInReport,
  • SendCrashReport,
  • SendCrashReportToPlatformErrorRegistrationService,
  • SendReport.
 +
  • IncludeUserNameInReportAtClient,
  • IncludeSystemInfoInReportAtClient,
  • IncludeDetailErrorDescriptionInReportAtClient,
  • IncludeInfobaseInformationInReportAtClient,
  • IncludeWindowsPictureInReportAtClient,
  • SendCrashReportAtClient,
  • SendCrashReportToPlatformErrorRegistrationServiceAtClient,
  • SendReportAtClient.

+

+

New property used to specify the error registration service address of the ErrorProcessingSettings object.
  • ErrorRegistrationServiceURL
  • ErrorProcessingServiceURL
Russian picture names of the picture library. Former names are considered obsolete and unsupported for compatibility.

+

  • AppearanceCharExclamationMark
  • AppearanceExclamationMark

The names contain Latin letter "c".

  • AppearanceCharExclamationMark
  • AppearanceExclamationMark

The names contain Russian letter "c".

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
ZIP archive operations.
The mobile version of 1C: Enterprise now supports ZIP archive operations.This feature was not provided.Supported ZIP archive operations in the mobile version of 1C:Enterprise.
Mobile platform.
Mobile client.
Dynamic list.
Data composition system.
In the mobile version of 1C:Enterprise, custom report settings are saved when generating a report. The UserSettingsModified report form extension property is set to False when generating the report result. This change is not implemented in 8.3.20 compatibility mode.

In the mobile version of 1C:Enterprise, a report option is saved after closing the report option editing form by clicking Finish editing. This change is not implemented in 8.3.20 compatibility mode.

Custom dynamic list settings are saved after dynamic list records are successfully imported.

In the mobile version of 1C:Enterprise, custom report settings were saved when closing a report form. The UserSettingsModified report form extension property was set to False when closing the form.

In the mobile version of 1C:Enterprise, a report option was saved only when the Save option command was manually called.

More logical and understandable operations with report and dynamic list settings.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Mobile client.
Startup of the mobile client with the connected collaboration system takes less time.Startup of the mobile client with the connected collaboration system took more time.Startup of the mobile client with the connected collaboration system takes less time.

+

Development tools.
New feature: prohibit exporting references to deleted configuration objects to XML files.

New radio button in the dialog box for dumping configuration to files: Do not export references to non-existent objects.

New parameter for the /DumpConfigToFiles command: -ignoreUnresolvedReferences.

New parameter for the config dump-config-to-files Designer agent command: --ignore-unresolved-refs.

New parameter for the (ibcmd) config export management utility of the standalone server: --ignore-unresolved-refs.

This feature was not provided.

+

You can deny export of references to previously deleted objects that remained in forms, command interface, and so on to XML configuration files.
Collaboration system.
Web client.
If a collaboration system user makes a video call in web client using Mozilla Firefox, video stream quality always remains high. Video stream quality does not depend on how this user is displayed for their counterparty.If a collaboration system user made a video call in web client using Mozilla Firefox, the web client tried to manage video stream quality, but the attempts failed.Eliminated unexpected system behavior.
Dynamic lists.
You cannot receive a URL of the current row for an information register subordinate to the recorder. An item with the WriteCurrentListRow key is not passed to the list of URLs. This list is passed to the ProcessURLsReceiving event handler for this information register.You could receive a URL of the current row for an information register subordinate to the recorder.

+

Eliminated unexpected system behavior as the record form is missing for an information register subordinate to the recorder.
Data composition system.
Mobile client.
User report settings are saved:
  • When the settings form is closed (in thin, thick, mobile, and web clients).
  • Upon calling the standard report generation command.
  • After 10 seconds since the latest change in user settings.

This change is not implemented in version 8.3.20 compatibility mode. +

User report settings were saved only upon calling the standard report generation command.Eliminated unexpected system behavior.

Reduced risk of losing configured settings due to automatic saving.

+

+

+

+

Distributed infobases.
Licensing client data must be entered in each node of a distributed infobase.Licensing client data had to be entered only in the main node of a distributed infobase.

+

Eliminated unexpected system behavior.
Mobile platform.
Mobile client.
Administration tools.
The cacertnx.pem file that contains root CA certificates is included in the mobile version of 1C:Enterprise.

When establishing a secure connection, certificate revocation is checked in the following order: certificates from the cacertnx.pem file, configuration certificates, application certificates, and mobile OS certificates.

This feature was not provided.Advanced features for certificate revocation check.
DBMS operations.
Accounting registers.
Accounting register indexes have been changed when running in PostgreSQL, Oracle Database, and Data accelerator.

Indexes change in case of accounting register restructuring including verification and restoration operations.

Accounting register indexes when running in PostgreSQL, Oracle Database, and Data accelerator were different.

+

Data acquisition from accounting registers is faster now.
Mobile client.
System requirements.
Mobile application builder.
Android 12 is supported now. Android 4.1 is no longer supported. The minimum supported Android version is 4.4.

(read more) add-in development technology has been changed.

The mobile application that will be published in Google Play Store and uses the "Installing applications" functionality must meet the app store requirements effective on July 11, 2022. To meet the requirements, use mobile version 8.3.21.41 or later.

Android version 4.1 was supported.The latest Android version is supported.

The mobile version of 1C:Enterprise no longer supports devices for which Google stopped releasing security updates.

Infobase operations.
Administration tools.
If you call the EraseInfoBaseData() method and exclusive mode is disabled, the system attempts to enable it. If the attempt is not successful, the method throws an exception.

The EraseInfoBaseData() method deletes data in extension object tables, but does not delete extensions installed in the infobase.

In file infobases, the EraseInfoBaseData() method could be successfully executed with disabled exclusive mode.Eliminated unexpected system behavior.
PDF document operations.
New parameters for the Write() and WriteAsync() methods: FileType.

New feature: when saving a PDF document interactively, select a PDF subset for it.

This feature was not provided.Saving PDF files in required format (including PDF/A archival formats).
Mobile platform.
Mobile client.
If the scale is increased on a mobile device on iOS, the interface of the mobile 1C:Enterprise version is also increased in scale.This feature was not provided.Improved user interface view on mobile devices on iOS.
XML and XDTO support.
If XSL transformation using the XSLTransform object results in an HTML file, the attribute value is URL-encoded for the href, action, and src attributes of various elements, and for the name attribute of the a element. You cannot use the following characters in URL encoding: @/:=?;#%&,+\.If XSL transformation using the XSLTransform object resulted in an HTML file, no values were URL-encoded.Eliminated unexpected system behavior.
XML and XDTO support.
New feature for the ReadXML() global context method: partial reading. You can read only data specified in an XML file without changing the data in the infobase object. Such reading is enabled if an XML element that describes a 1C:Enterprise object contains the optional dataPart attribute set to True.

1C:Enterprise does not allow creating an XML file to perform partial reading.

Partial reading is implemented for the following configuration objects: catalogs, documents, tasks, business processes, exchange plans, charts of accounts, charts of calculation types, charts of characteristic types, and accumulation, information, calculation, and accounting registers.

Previously the ReadXML() method did not allow partial reading of a configuration object from an XML file.Advanced exchange with third-party systems using XML files.
Internet-enabled functionality.
Secure connection is used when calling the InternetMail.Logon() method. If the application uses mail servers that do not require server certificate verification, specify these servers in the conf.cfg configuration file. Now you can do it using the new IgnoreInternetMailServerCertificateVerificationList parameter of the configuration file.Unsecure connection was used when calling the InternetMail.Logon() method.Enhanced security for using objects related to remote access to various external services.
Add-ins.
New feature: if the user, on whose behalf the application trying to attach an add-in (the AttachAddIn() method) in isolation is running, does not have enough rights to create a separate process, the add-in will be attached in non-isolated mode.Previously, if the user, on whose behalf the application trying to attach an add-in (the AttachAddIn() method) in isolation was running, did not have enough rights to create a separate process, the add-in was not attached, and it was impossible to use it.Now you can use an add-in regardless of whether you have the rights to start a separate process, on whose behalf the application that attaches the add-in is running.

Table of contents

Transition from the previous version to the version 8.3.21

Table of contents

Version 8.3.20

Version 8.3.20 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult 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.
System requirements.
Astra Linux Special Edition 1.7 and PostgreSQL DBMS 11.10 are now supported from this OS.Astra Linux Special Edition 1.7 and PostgreSQL DBMS 11.10 were not supported from this OS.Astra Linux Special Edition 1.7 and PostgreSQL DBMS 11.10 are now supported from this OS.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult 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

FunctionalityAfterBeforeResult 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

FunctionalityAfterBeforeResult 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

FunctionalityAfterBeforeResult 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.
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 performed within the full infobase session with checking rights of a user performing the action and registering actions in the event log.

Commands related to the server as a whole (for example, commands to receive a list of sessions or terminate a call) do not require to create a session. However, they must be executed on behalf of an infobase user with administrative rights.

The execution of administration interface commands did not require to create a session, check rights of a user performing an administrative action, and register performed actions in the infobase event log.Improved standalone server management security.
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.
Standalone server.
System requirements.
Standalone server is no longer supported on 64-bit Windows Server 2003 and Windows XP.Standalone server was supported on 64-bit Windows Server 2003 and Windows XP.Standalone server is no longer supported on obsolete Windows operating systems.

Table of contents

Renamed objects

ObjectThe old nameThe 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"

FunctionalityAfterBeforeResult 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.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"

FunctionalityAfterBeforeResult 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 + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult 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.
System requirements.
Microsoft Windows 11 operating system is supported.Microsoft Windows 11 operating system was not supported.Extended list of supported operating systems.
Integration service.
New integration service feature: sending messages with a significant data amount (hundreds of megabytes).

The IntegrationServiceMessage.GetBodyAsStream() method returns the stream for which position change is always unavailable. The reading and writing availability depends on the message for which the method is called.

The IntegrationServiceMessage.ExpirationDate property is read only. The property value can be set only when creating a message. New parameter for the IntegrationServiceManager.CreateMessage method: ExpirationDate.

New property: IntegrationServiceMessage.BodySize.

An attempt to send messages with a significant data amount could lead to various side effects and impossibility to use the integration service.

The stream that was returned by the IntegrationServiceMessage.GetBodyAsStream() method was always available for writing and reading.

The IntegrationServiceMessage.ExpirationDate property was writable.

 +

Improved integration service stability when working with messages of significant size.

Mobile platform.
Mobile client.
If the user does not agree to receive data, the promise execution result obtained by using the GetDataAsynс() method of the secure storage manager will be Undefined.

+

The promise execution result obtained by using the GetDataAsync() method of the secure storage manager did not reveal what happened during the method execution: a runtime error or the user did not agree to receive data.

+

Now it's possible to distinguish a runtime error and a situation when the user did not agree to receive data when using the GetDataAsync() method of the secure storage manager.

+

System requirements.
Microsoft Windows Server 2022 operating system is supported.Microsoft Windows Server 2022 operating system was not supported.Extended list of supported operating systems.
Analytics system.
In the main menu of the administration console of the 1C: Analytics system, the ability to gain access to the description of the system programming interface has been implemented.

The ability to change the server settings of the 1C:Analytics system using the built-in language object AnalyticsSystemServerConnection

The built-in language of the 1C:Enterprise system made it possible to read and write the parameters of the 1C:Analytics system server, but did not allow changing these parameters, because they were not documented.Implemented the ability to change the server settings of the 1C: Analytics system using the built-in language object AnalyticsSystemServerConnection
Standalone server.
When using a standalone server, the server license is required in the following cases:
  • When running the ibcmd utility in client/server mode.
  • When connecting to a standalone server in client/server mode over SSH.

When a file infobase is used and the ibcmd utility performs operations with the infobase without connecting to a standalone server, the server license is not required.

+

When using a standalone server, the server license was required when running the ibcmd utility and the standalone server over SSH. The license was not required only when using a file infobase with less than 3 concurrent sessions.Eliminated unexpected system behavior.
Mobile platform.
Mobile client.
New feature in the mobile application build service: build a developer platform.This feature was not provided.Advanced features of the mobile application build service.

+

Cryptography support.
Web client.
Improved signature standard CAdES is now supported in the cryptography manager. CAdES defines the standard of a digital signature that remains valid for a long period of time.

New property for the CryptoManager object: TimestampsServersAddresses. New parameter for the Sign(), SignAsync(), and BeginSigning() methods of the CryptoManager object: CryptoSignatureType. New parameter for the VerifySignature(), VerifySignatureAsync(), and BeginVerifyingSignature() methods of the CryptoManager object: CheckAdditionalAttributes.

New methods for the CryptoManager object: ImproveSignature(), ImproveSignatureAsync(), BeginImprovingSignature(), AddArchiveTimestamp(), AddArchiveTimestampAsync(), BeginAddingArchiveTimestamp().

New methods for the CryptoCertificateStore object: RefreshCertificatesRevocationLists(), RefreshCertificatesRevocationListsAsync(), BeginRefreshingCertificatesRevocationLists(), CheckTimestamp(), CheckTimestampAsync(), BeginCheckingTimestamp(), GetCryptoSignaturesContainer(), GetCryptoSignaturesContainerAsync(), BeginGettingCryptoSignaturesContainer().

Improved digital signatures are not supported in the cryptography extension in Safari. Improved digital signatures might be unavailable in the latest versions of Internet Explorer on Windows 10. In this case, it is recommended that you use Mozilla Firefox, Google Chrome or previous versions of Internet Explorer instead.

This feature was not provided.Advanced cryptography features in 1C:Enterprise.
Web client.
Add-ins.
For web client on Linux, file system extensions, cryptography extensions, and add-in adapters now use GTK-3 library.For web client on Linux, file system extensions, cryptography extensions, and add-in adapters required GTK-3 library.To use add-ins, file system extensions, and cryptography extensions in web client on Linux, GTK-3 library must be available on the computer.
Administration tools.
New cacertnx.pem file that is used in thin client, thick client, and server cluster to check certificate revocation. Root certificates of trusted certification authorities are added to the cacert.pem and cacertnx.pem files.

Now you can update the cacertnx.pem file when installing thin client or full distribution package (using an MSI file). +Certificate revocation check in 1C:Enterprise is performed as follows:

  • In compatibility mode with version 8.3.8 or later, the check is performed using the cacertnx.pem file and then using the current operating system.
  • In compatibility mode with version 8.3.7 or earlier, the check is performed using the cacert.pem file only.

+

These features were not provided.Advanced features for certificate revocation check.
Administration tools.
Hash algorithms implemented according to GOST are now supported upon USIA authentication.Hash algorithms implemented according to GOST were not supported upon USIA authentication.

+

Eliminated unexpected system behavior.
Mobile application builder.
Mobile 1C:Enterprise version 8.3.20 is now supported in the mobile application builder.Mobile 1C:Enterprise version 8.3.20 was not supported in the mobile application builder.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
Mobile application builder.
Mobile 1C:Enterprise version 8.3.22 is now supported in the mobile application builder.Mobile 1C:Enterprise version 8.3.22 was not supported in the mobile application builder.Extended list of supported mobile 1C:Enterprise versions in the mobile application builder.
XML and XDTO support.
If an error occurs during XML operations, the error message contains the error cause, which is specified in the library used by 1C:Enterprise for XML operations.If an error occurred during XML operations, the error message did not contain the error cause specified in the library used by 1C:Enterprise for XML operations.Eliminated unexpected system behavior.

Simplified troubleshooting of some issues that might occur during XML operations.

DBMS operations.
Server clusters.
 +

New feature: secure connection between the server cluster and PostgreSQL DBMS over SSL protocol.

This feature was not provided.Eliminated unexpected system behavior.
Standalone server.
Dumping configurations to files/Restoring configurations from files.
Loading a configuration from XML files in Designer and on the standalone server requires less RAM.

Loading a configuration from XML files in Designer and on the standalone server takes less time.

Designer and the standalone server used more RAM when loading a configuration from XML files.

Loading a configuration from XML files in Designer and on the standalone server took more time.

+

Reduced RAM consumption and better performance when loading a configuration from XML files in Designer and on the standalone server.
Administration tools.
The list of supported root certificates has been extended.Fewer root certificates were supported.Extended list of supported root certificates.
Server clusters.
Now 1C:Enterprise in client/server mode contains indexes for tables related to infobase users if you use IBM Db2, Oracle Database, or PostgreSQL.

Once the platform is updated, connect a user to the infobase to restore the indexes before the system starts connecting other users.

+

Previously, 1C:Enterprise in client/server mode did not contain indexes for tables related to infobase users if you used IBM Db2, Oracle Database, or PostgreSQL. So, it took more time to find a user by name and connect a large number of new users to the infobase. +Eliminated unexpected system behavior. +
Web client, web service, and HTTP service publishing tools.
Now the web server extension consumes less RAM on Windows.Previously the web server extension consumed more RAM on Windows.Reduced RAM consumption by the web server extension on Windows.

Table of contents

Transition from the previous version to the version 8.3.20

Table of contents

Version 8.3.19

Version 8.3.19 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.18 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.17 was available.Configurations developed using 1C:Enterprise platform version 8.3.18 or earlier can now run on version 8.3.19 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.19 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.18 after the migration to version 8.3.19, even if you disable the compatibility mode (simply enable it again).
Documentation.
New feature: objects available on a standalone mobile server can be selected for the Syntax Assistant.

New availability mode for the Syntax Assistant: Standalone mobile server. This availability mode describes objects and methods available on the 1C:Enterprise server running on a mobile device in standalone mode of the mobile client. +

In the Syntax Assistant, it was not possible to select objects available on a mobile device on the server side of the mobile client running in standalone mode.New features of the 1C:Enterprise mobile version are considered in the Syntax Assistant.
Navigation links.
Now you can specify additional parameters in URLs. The composition of parameters depends on the URL kind. Now you can do the following:
  • Pass additional parameters for the form to open.
  • Get a URL to a report option.
  • Get a URL to full report settings.
  • Get a URL to a dynamic list with settings.
  • Get a URL to the current dynamic list row with settings.
  • Get a URL to a command and pass parameters to it.

In the get URL dialog box (if necessary), you can choose which URL to get at a specific place in the client application interface.

New methods for the client application form extension for a report: GetReportURL(), GetCurrentReportOptionURL(), and GetCurrentReportSettingsURL().

New method for the client application form extension for a data processor: GetDataProcessorURL().

New methods for the client application form extension for a dynamic list: GetListURL() and GetCurrentListSettingsURL(). New client application form parameter for a dynamic list: TableDisplay.

New method for the client application form extension for an object, a document, a catalog, a business process, a task, a chart of characteristic types, and an object of an external data source table: GetObjectURL().

New method for the client application form extension for an information register record and a record of an external data source table: GetRecordURL().

New feature: all the listed URL options can be received for the GetURL() global context method.

New handlers for the client application form: GetURLsListProcessing and GetURLProcessing.

New configuration property: URLsExternalDataStorage.

Changed format of the XML configuration export. +

These features were not provided.Advanced navigation links features.
Client application form.
For form field extensions for an HTML document, a formatted document, a geographical schema, and the planner, implemented the BeforePrint event that occurs before an object is printed interactively.

For form field extensions for an HTML document and a formatted document, implemented the BeforeWrite event that occurs before an object is written interactively.

For form field extensions for an HTML document and a formatted document, implemented the AfterWrite event that occurs after an object is saved interactively.

The Save command of the client application form called for a spreadsheet document does the following:

  • If a file name is not specified or a spreadsheet document is not in edit mode, the dialog box to specify a name of a file to be saved is generated.
  • If a file name is specified and a spreadsheet document is in edit mode, saving is performed without displaying the dialog box to specify a file name.

Once a spreadsheet document is saved, an operation completion notification appears.

For all form item kinds that support saving (except a spreadsheet document), the value that matches the executing action is passed to the Copy parameter of the BeforeWrite event handler:

  • True if the Save as command is selected.
  • False if the Save command is selected.

For a spreadsheet document or a report, the behavior is not changed when you select the Save command. +

For all form item kinds that supported saving, the system behavior was the same when the Save and Save as commands were specified: the dialog box to select a file to be saved was generated.

For all form item kinds that supported saving (except a spreadsheet document), the True value was always passed to the Copy parameter of the BeforeWrite event handler. For a spreadsheet document, when the Save command was selected for a spreadsheet document or a report, the False value was passed to the BeforeWrite handler in the Copy parameter. +

Implemented the BeforePrint, BeforeWrite, and AfterWrite event handlers for all client application form items that support saving and printing.
Client application.
Changed icons of all 1C:Enterprise executable files and icons associated with different file extensions related to 1C:Enterprise.Icons of executable and generated files of 1C:Enterprise were different.Icons follow the same style.
Pictures.
SMIL animation of SVG images is now supported. SMIL animation is not supported in Microsoft Internet Explorer and Microsoft Edge up to version 18 inclusive. In web browsers that do not support SMIL animation, a static picture will be displayed.

New feature: in a set of picture variants, you can specify a web browser the variant element is intended for. When a picture is output in a web browser, an attempt is made to define a variant for the used web browser first.

We recommend that you use SVG images with SMIL animation to create animated pictures in the application. Such pictures take up little space and do not require large resources for their display.

This feature was not provided.Animated SVG images can now be displayed. Animation is displayed in both ordinary client applications and the web client (except Microsoft Internet Explorer and Microsoft Edge up to version 18).
Dynamic lists.
The following features similar to the features provided in the data composition system are available for a dynamic list:
  • Setting up query fields (a title, a type, appearance, a use restriction, and other).
  • Operations with calculated fields.
  • Using parameters in user settings.
  • Setting up parameter properties (a title, a type, and other).
  • In fields of the Date type, you can now use parent fields (beginning of day, month, and other) in sorting and grouping.

Changed the dynamic list settings editor.

New properties for a dynamic list: Fields, FieldsToCalculate, and DataParameters. Changed the configuration XML dump format.

The following dynamic list methods are deprecated: SetRestrictionsForUseInGroup(), SetRestrictionsForUseInFilter(), SetRestrictionsForUseInOrder(), GetRestrictionsForUseInGroup(), GetRestrictionsForUseInFilter(), and GetRestrictionsForUseInOrder(). We recommend that you use the UseRestriction dynamic list properties and the AttributesUseRestriction dynamic list fields.

This change is not implemented in version 8.3.18 compatibility mode. +

These features were not provided.Simplified setup of dynamic list fields. In particular, you can now specify localized presentations of query fields displayed in a dynamic list.
Data composition system.
Dynamic lists.
When you set up configuration object characteristics, you can now specify which configuration object field contains a characteristic name. Changing the characteristic presentation will not result in the loss of settings field of the data composition system or a dynamic list.

New property: CharacteristicsDetails.DataPathField.

The value that returns the Presentation virtual field is used as a characteristic presentation. A new field remains blank for existing characteristics.

If you change a field that contains a characteristic name in the characteristic description, we recommend that you provide a mechanism that converts data composition settings by replacing the old characteristic name with a new one.

Changed format of the XML configuration export.

The presentation of this characteristic was used as a characteristic name. Changing the characteristic presentation resulted in the loss of characteristics of data composition system settings and dynamic list settings.Simplified creation of localized characteristic presentations in applications.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Collaboration system.
The client application on Windows uses the Video Tools module that matches the operating system bitness for video calls.The client application on Windows used the Video Tools module that matched the client application bitness for video calls.On a video call, computer resources are used more efficiently.
Client application.
Web client.
Now the Taxi interface supports right-to-left languages (in thin and thick client applications). This mode is supported in the entire client application interface automatically.

The need to change the interface is determined by the interface language or the configuration language. Now client applications support Arabic numbers and dates.

When calculating placement of form items and other interface elements, Almarai font is used by default.

If a right-to-left language is set as the current configuration language in Designer, then the form preview in the form editor will also be performed in the relevant format.

Support of right-to-left languages has been implemented starting with version 8.3.7 compatibility mode.

The web client now supports right-to-left languages for the planner and charts.

Right-to-left languages were supported in the web client only.1C:Enterprise is now available in right-to-left languages (using thin and thick client applications).
Spreadsheet documents.
Data display.
If the length of the text within a cell exceeds 3276 characters in a spreadsheet document being saved in the Microsoft Excel format (Microsoft Excel 97 or Microsoft Office OpenXML), saving is terminated and an error message appears.When saving a spreadsheet document in the Microsoft Excel format (Microsoft Excel 97 or Microsoft Office OpenXML), the length of the text within a cell was not checked. This could result in a document that Microsoft Excel could not open.Saving in the Microsoft Excel format is more correct now.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Queries.
Improved query execution including when data access restrictions are used.

Improved performance of the StrContains() function of the data access restriction expression.

Query execution (including queries that used data access restrictions) took more time.Improved query performance.
Server clusters.
In a client/server infobase, loading from the .dt file is now faster as several background jobs are used for loading. To speed up significantly, we recommend that the server cluster and the DBMS are on the same computer or that the server cluster and the DBMS are interconnected with a high-bandwidth channel (1 GB/s or higher).

For the /RestoreIB command of the Designer batch mode, implemented the JobsCount parameter that allows you to manage the number of used background jobs.

In a client/server infobase, loading from the .dt file was performed sequentially.Upgrade: information is restored from the .dt file faster in a client/server infobase.
Common objects.
When solving systems of linear equations, reduced the time spent on obtaining a solution and the use of RAM.Solving systems of linear equations took more time and required more RAM.Improved solving systems of linear equations.
Server clusters.
Improved generation of a session list.

New service: Service for retrieving a list of server cluster sessions.

Retrieving a session list took more time and could cause the system to hang on bulk retrieving the session list when load on the server cluster was heavy.A possibility of system hanging on bulk retrieving a session list under heavy load is excluded. Reduced time of a single operation for retrieving a session list on a cluster with multiple servers. The time spent on simultaneous bulk retrieval of session lists is significantly reduced.
DBMS operations.
If you press the Write button several times in the object edit form (with the object unchanged), object tabular sections are not written to the DBMS upon each object record.If you pressed the Write button several times in the object edit form, object tabular sections were written to the DBMS upon each object record.Decreased DBMS load in some cases.
DBMS operations.
Queries.
In a file infobase, executing a query that receives data with ordering and filtering by the field for which the index is built is faster now even if the IN operator that receives a large amount of data is used to impose a condition. +In a file infobase, executing a query that received data with ordering and filtering by the field for which the index was built was not optimal if the IN operator that received a large amount of data was used to impose a condition.Improved file infobase performance.
Accounting registers.
Optimized the query used by 1C:Enterprise to access virtual tables of balance and turnovers of the accounting register.The query used by 1C:Enterprise to access virtual tables of balance and turnovers of the accounting register was not optimal.Improved performance of queries to the virtual table of balance and turnovers of the accounting register.
Data display.
Improved performance of the GetStringDeclension() and GetStringDeclensionByNumber() upon consecutive calls. For example, to get several case forms of the same phrase at once.Several consecutive calls to the GetStringDeclension() and GetStringDeclensionByNumber() methods took more time.Getting several case forms of the same phrase at once using the GetStringDeclension() and GetStringDeclensionByNumber() methods is faster now.
Automated testing.
Reduced the number of network calls when the FindObject(), FindObjects(), and GetObject() methods of automated testing are running. This improves the overall automated testing performance.When the FindObject(), FindObjects(), and GetObject() methods of automated testing were running, a large number of network calls were made, which caused poor automated testing performance.Improved automated testing performance, especially when the web client is used.
Data display.
Bulk retrieval of presentations of reference objects is now faster if only data passed to the handler is used to generate the presentation. This is reached by caching the presentations.

If data that is not passed to the presentation generation handler is used to get the presentation, when the presentation changes in the object, the presentation will change in the handler only in 20 seconds.

Bulk generation of presentations of reference objects took more time as values used to get the presentation were cached and the presentation itself was calculated every time the presentation was required.Receiving presentations of reference objects and related operations are faster now. For example, ordering a value table by a reference column will speed up.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Database copies.
Queries.
Data composition system.
Now you can control where a specific query or data composition will be executed: use only copies, only the main database, or mostly copies to execute a query, or select automatically. Thus, it became possible not to load the main database with a query that was created to be executed on a copy.

New properties for the Query and DataCompositionOutputParametersValues objects: DatabasesCopiesUse and UsedDatabaseCopies.

The platform automatically selected where the query would be executed. If it was not possible to execute a query on a copy, the main database was used to execute the query.It is now possible not to execute queries or reports on the main database that can affect the database performance and that were intended to be executed on a copy only.
Data composition system.
Once the report is generated, the server part of the data composition system notifies the client application initiated the report generation of report generation completion using the Collaboration System. This mechanism works in conjunction with the existing mechanism for determining whether report generation is completed (periodic polling of the system background job).To determine whether report generation was completed, periodic polling of the system backgroud job generating the report was used. Each failed completion check increases the time interval after which the next check will be done.If there is the Collaboration System, a user will know right away when long report generation is completed.

If the Collaboration System is not connected to the infobase or is temporarily not functioning, the existing mechanism will be used.

Dynamic lists.
For the header of the table column displaying a dynamic list with an order setting item that cannot be disabled by a user:
  • In the web client: clicking the header changes the sorting order.
  • In thin and thick client applications: the column header always displays the sorting direction.

As a result, the behavior of thin, thick, and web clients is the same when a user left-clicks the header of the dynamic list column whose ordering settings include an item that cannot be controlled by the user.

For the header of the table column displaying a dynamic list with an order setting item that could not be disabled by a user:
  • In the web client: clicking the header did not change the sorting order.
  • In thin and thick client applications: the sorting direction was displayed in the column header only if there were user ordering settings for that column.

The behavior of thin, thick, and web clients was not uniform when a user left-clicked the header of the dynamic list column whose settings included an item that could not be controlled by the user.

Unified behavior of thin, thick, and web clients when a user left-clicks the header of the dynamic list column whose ordering settings include an item that cannot be controlled by the user.
Data display.
The behavior of the GetStringDeclensionsByNumber() method changes when generating a number:
  • For an ordinal:
    • For a cardinal: an error of invalid parameter specification is generated. +

      • This change is not implemented in version 8.3.18 compatibility mode.

When generating a numeral with an ending using the GetStringDeclensionByNumber() method, two-letter endings were always returned for ordinal and cardinal numbers.Eliminated unexpected system behavior.
Database copies.
Now you can add objects included in separators to a database copy. On initial filling, the entire table is transferred. On change transfer, only the area that matches the separators of the current (transferred) transaction is transferred.

To create a database copy (using the DatabaseCopyManager.Write() method) and update copy data (using the DatabaseCopyManager.Update() method), the DataAdministration access right is required.

It was possible to add only tables that were not part of separators or a table with conditionally disabled separators to a copy.Now you can add separated application objects to a database copy.
Client application.
Now each infobase user can manage OpenIDConnect authentication. New property: InfobaseUser.OpenIDConnectAuthentication.

Now you can end an authentication session according to the OpenID Connect standard. New property in OpenID Connect provider description–default.vrd file, <providers> item: endSessionEndpoint.

This feature was not provided.Improved OpenID Connect support.
Licensing system.
Expanded the set of information displayed by the licensing utility (the ring license info command):
  • Added information about the license type and the license binding type in the section with license information.
  • New section with machine-readable information: TechnicalInfo. Data in this section is always displayed in English.
The output of the ring license info command did not contain information about the license type and the license binding type, and did not contain a section with machine-readable information about the license.Expanded the set of activated license information that can be obtained. Simplified obtaining information about licenses using various automation tools.
Charts.
Data composition system.
Upgrade: a chart in a data composition system report better adjusts to the width of the screen showing the report.

This change is not implemented in version 8.3.18 compatibility mode.

A chart in a data composition system report did not adjust well to the width of the screen showing the report.Improved appearance of charts on low-resolution screens.
Queries.
If a query that generates a temporary table based on a value table retrieves a field separated by dot from another expression, a query language error is generated on executing such a query.

We recommend that you analyze texts of queries to generate temporary tables to eliminate the modifiable behavior.

This change is not implemented in 8.3.18 compatibility mode.

If a query that generated a temporary table based on a value table retrieved a field separated by dot from another expression, a runtime error was generated when executing this query in client/server mode and an incorrect value was placed in the temporary table value when executing this query in file mode. +Eliminated unexpected system behavior.
Spreadsheet documents.
This feature is canceled.

When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects now behave as follows:

  • If the PictureSize property value is not Tile, an original picture is saved to the resulting document. If a pattern is specified for a cell, the pattern picture is also saved.
  • If the PictureSize property is set to Tile, a picture is redrawn into the resulting document and the background color of a Microsoft Excel document picture becomes the same as the one of the source document picture.

As a result of these changes, pictures in a spreadsheet document become less distorted when scaling a Microsoft Excel document.

When exporting a spreadsheet document to Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats, the Picture objects behaved as follows:
  • When the PictureSize property value was not Stretch, a picture was redrawn into the resulting document.
  • When the PictureSize property value was set to Stretch, a picture was redrawn to the resulting document if a background color or pattern was not set. Otherwise, an original picture was saved.
The result of saving a spreadsheet document in Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) formats meets expectations of users to a greater extent.
Data composition system.
Functional options.
When calculating the availability of child fields used in data composition expressions, a check whether the field is not disabled using a functional option is performed for both the field itself and all parent fields of this field.

This change is not implemented in version 8.3.18 compatibility mode.

When calculating the availability of child fields used in data composition expressions, a check whether the field was not disabled using a functional option was performed only for the field itself. Parent fields were not checked.Upgrade: the availability of fields associated with functional options is checked in the same way in both the query language and the data composition system.
Data exchange.
For the RecordChanges() and DeleteChangeRecords() methods, it is now possible to register and unregister changes for an arbitrary set of data objects that are passed as an array in the Data parameter of these methods.

The action for all objects in the passed array will be performed within a single transaction with the minimum number of queries used.

For the RecordChanges() and DeleteChangeRecords() methods, it was not possible to specify an array of objects to perform an action.Executing the RecordChanges() and DeleteChangeRecords() methods is now faster when these methods must be applied to a large number of data objects.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Client application.
Client application installation.
Administration tools.
Now you can update a client application using the web server when Microsoft Internet Information Services configured by default is used as a web server. Implemented support of the MIME type application/x-zip-compressed used by the web server for .zip files by default. +To update a client application using the web server when Microsoft Internet Information Services was used as a web server, you had to manually override the MIME type that the web server used to pass .zip files.Administration of the Microsoft Internet Information Services web server is more convenient when a client application update is configured via the web server.
Administration tools.
When exclusive mode is set, you can now specify a human-understandable description of the reason why exclusive mode is set (what the session is doing) and terminate the session that set the exclusive access.

New parameter for the SetExclusiveMode() method: Parameters. New global context method: GetExclusiveModeParameters(). New access right: ExclusiveModeCompletionOnStartSession.

The message text about the reason for the inability to start a new session can be a formatted string or an HTML string generated from a formatted string.

When attempting to log into the infobase where exclusive mode was set, it was impossible to terminate such a session (even if it was possible to terminate the session according to the logic of the actions being performed) and it was not clear what was being done at that moment.When exclusive mode is set, you can now specify a user-understandable text that explains why exclusive mode is set. A user can terminate the session that set exclusive access if the user rights and the logic of the actions performed allow such termination.
Predefined data.
Calling the PredefinedValue() method when a non-existent enumeration value is specified as a parameter value generates an exception.

This change is not implemented in version 8.3.18 compatibility mode.

Calling the PredefinedValue() method when a non-existent enumeration value was specified as a parameter value returned an empty value.Eliminated unexpected system behavior.
Administration tools.
The name of the distribution package of 1C:Enterprise server cluster for x86-64 architecture looks as follows: 1C:Enterprise 8 (x86-64) Server. +The name of the distribution package of 1C:Enterprise server cluster for x86-64 architecture looked as follows: 1C:Enterprise 8 (x86-64).Now software names follow a single style for all software distribution packages for Windows.
Spreadsheet documents.
Data composition system.
Now you can scale a picture so that the picture height matches the size of the font used in the item that displays the picture.

New system enumeration property: PictureSize.ByFontSize.

If a picture in a report cell is specified using the Picture conditional appearance parameter of the data composition system, the PictureSize parameter value equals the ByFontSize value (if the PictureSize parameter is not specified in conditional appearance). This change is not implemented in version 8.3.18 compatibility mode.

We recommend that you use the ByFontSize picture display mode in a spreadsheet document when a picture in a cell is a marker. When using this picture display mode, the picture height does not affect the automatically calculated height of the spreadsheet document row and does not depend on the number of text rows displayed in the cell.

If a picture in a report cell was specified using the Picture conditional appearance parameter of the data composition system, the default value was not set for the PictureSize parameter and this parameter was not used (except if this parameter was specified explicitly).Improved display of pictures in a spreadsheet document in cases where it is necessary to use a picture in the text so that the picture size automatically adjusts to the height of the font used.
Server clusters.
Administration tools.
Now you can use partial Kerberos delegation for OS authentication if the server cluster is running Windows, the web server and the client application are each on their own computer, and this computer is different from the computer where the server cluster is running.

For server cluster administration tools, a service principal name (SPN) can now be specified:

  • In the cluster administration console, the working server properties, implemented the property 1C:Enterprise server principal name (SPN).
  • The AdministrationWorkServer.ServerServiceName object property.
  • The IWorkingServerInfo.ServicePrincipalName object property for administration tools using COM connection.
  • The getServicePrincipalName() and setServicePrincipalName() methods of the IWorkingServerInfo interface for Java-based administration tools.
  • The service-principal-name parameter for the rac server insert and rac server update commands.
This feature was not provided.

OS authentication could only be performed with full Kerberos delegation if the server cluster was running Windows, the web server and the client application were each on their own computer, and that computer was different from the computer where the server cluster was running.

Now you can use OS authentication when accessed via the web server, without lowering the overall system security.
Data display.
Now you can automatically switch a report to compact mode (if necessary), regardless of how the report is generated: using the platform or the 1C:Enterprise language.

New property of the client application form extension for a report: ViewModeUseOnSetResult. The property works together with the ResultViewMode property of the client application form extension for a report.

Changed format of the XML configuration export.

If a report was generated using the 1C:Enterprise language, it was required to switch the report to compact mode (if necessary) manually.For a developer, simplified report display on a form if the report is generated using the 1C:Enterprise language and it is necessary to consider that the report can be displayed on mobile devices.
Server clusters.
The value of the Temporarily allowed amount of process memory property of the working cluster server is used to restart working processes from memory and manage large call termination. You can use this property with a PROF license.When working with PROF licenses, a value equal to 80% of the RAM of the computer where the server was running was used to restart cluster working processes and terminate large server calls. It was not allowed to change the Temporarily allowed amount of process memory property of the working cluster server with PROF licenses.Administration of systems with PROF licenses is more convenient.
Spreadsheet documents.
Now you set the report display mode for reports using the 1C:Enterprise language.

New methods for the client application form extension for a report form: GetResultViewMode(), GetCurrentResultViewMode(), and SetResultViewMode().

Changed the approach to storing information about the result display mode in the system settings storage. Information about the report display mode is stored in the system report storage when the display mode value to be set differs from the value specified in the configuration. In this case, the Auto value interpretation is ignored for various client types.

The ResultViewMode property of the client application form extension for a report form is deprecated.

It was not possible to change the report result view mode using the 1C:Enterprise language.

The value that the current client application took into account was stored in the system storage (the Auto value interpretation was not ignored).

Now you can manage report display using the 1C:Enterprise language.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile client.
Automated testing.
Now you can use the mobile client as a test client. The mobile client in standalone mode can be a test client only during connection with the main server.

Now you can record user actions on a mobile device and playback a test written earlier in the 1C:Enterprise language.

New commands for the command-line to start the mobile client: /UILOGRECORDER and /TESTCLIENT.

The developer mobile client is always started with the option to record user actions (with the /UILOGRECORDER command).

If the mobile client is started with the /UILOGRECORDER command, the Record user actions item appears in the Mobile client tools menu. +

This feature was not provided.Now you can use the mobile client for automated testing of applications.
Error handling.
New values for the ErrorsCategories system enumeration:
  • NoPermissionToUseFunctionality that describes errors that occur because the mobile application does not have permissions to use some features correctly.
  • MultimediaToolsError that describes errors that occur while using a mobile device camera or microphone.
These error categories were missing in the ErrorsCategories system enumeration. +Improved mobile application error categorization.
Mobile device-specific features.
Now you can manage audio recording in the background. If this functionality is enabled, audio recording will continue when the application is minimized and the device screen is turned off.

New system enumeration value: MobileApplicationFunctionality.AudioRecordingInBackground.

Background audio recording was not available. Audio information could be recorded only if the application was active.Improved audio information operations in the mobile application.
Mobile client.
Upgraged the video call interface in the mobile client.

In the mobile client, you can now view the screen of another device and share your own screen. The viewing screen cannot control the mobile device whose screen is being shared.

The video call interface in the mobile client was different.

The mobile client did not support screen viewing and sharing.

Improved interaction system video calls in the mobile client.

Table of contents

+

FunctionalityAfterBeforeResult of changes
Analytics - charts.
In a graph, the x-axis will show the time dimension by default.The x-axis now showed the first added dimension.The expected result is obtained more often without additional actions.
Analytics - dashboards.
The left dashboard panel shows folders, just like the desktop.The left dashboard panel showed all charts, excluding folders.It is now easier to navigate through charts on the dashboard.
Analytics - dashboards.
Decreased spacing between dashboard items.Spacing between the dashboard items was larger.The dashboard now contains more information.
Analytics - charts.
In table mode, you can now customize how totals will be placed: at the beginning or at the end of dimension values.In table mode, totals were always displayed at the beginning of a dimension.Improved appearance settings for table totals.
Analytics - expression language.
Implemented the FORMAT() function to format values in a chart.The value was displayed in the default format.You can now customize the required option to display values.
Analytics - charts.
When the chart type is switched, the chart retains roles of fields that are close in meaning.When the chart type was switched, field roles were set to default values.Switching the chart type requires fewer steps to achieve the desired chart appearance.
Analytics - sources.
When creating additional sources based on virtual tables, it is now possible to transfer parameters from report settings to a query.It was not possible to define virtual table parameters in additional sources.Additional sources based on virtual tables are now more efficient.
Analytics - expression language.
Implemented the PREVDATE() and VALUEFOR() functions to build comparative graphs for different time slices or other dimensions.

Using these functions will allow you to compare similar indicators obtained for different periods of time or other analytical dimensions in the table.

For output to the table, it was not possible to use similar indicators obtained for different periods of time or other analytical dimensions.You can now obtain the same indicators for different periods of time to build better charts.
Analytics - expression language.
Implemented the TOP() function that allows you to limit the number of values displayed in a report and combine the remaining values into a single total value. The setting is available from the dimension context menu.This feature was not provided.You can now build more descriptive charts.
Analytics - charts.
The chart editor now supports search for available fields in nested source structures (in nested references to catalog items and documents).The search only worked for the top level of the hierarchy.It is now easier to search for fields to be analyzed.
Analytics - charts.
The hierarchy can now be expanded by date similar to the directory hierarchy using the field hierarchy menu in a chart. +Periods in charts had to be refined manually.It it now easier to manage dates in charts.
Analytics - charts.
You can now customize the legend location in the chart. +The position of the legend was fixed.The chart appearance settings are now more flexible.
Analytics - charts.
Implemented tooltips and notes in the filter by date editor for universal formulas ("Current year", "Last year", and other).This feature was not provided.Help information is now available in the filter by date editor.
Analytics - charts.
The chart background now considers the currently enabled application theme.The chart background was light regardless of the theme.The chart background now matches the theme used. +
Analytics - charts.
A tooltip can now be displayed for a field value if it does not fit within one cell in the table.This feature was not provided.

Field values were clipped to cell borders. +

You can now see the full value in a table cell for any length of the text presentation of the value.
Analytics - charts.
The full date value can now be displayed in a chart using the context menu.The full date could only be displayed by editing the formula.It is now easier to manage dates.
Analytics - charts.
You can now smoothly adjust the size of the panel with data source fields.The panel size was not customizable.You can now use screen space more efficiently.
Analytics - dashboards.
When switching from the dashboard to the chart level, common dashboard filters can now be displayed and quickly enabled/disabled.There were no common filters on the dashboard.The user can quickly assess the filter impact on the dashboard data.
Analytics - other.
Implemented the command to open the web client of 1C:Enterprise infobase with which 1C:Analytics works.It was not possible to quickly call the web client for the used 1C:Enterprise infobase.It is now easier to use the infobase.
Analytics - desktop.
You can now batch copy/move objects on the desktop. +Objects on the desktop could only be copied and moved one at a time.The desktop is now more user-friendly.
Analytics - desktop.
The path to objects can now be displayed upon desktop search.Upon search, it was not clear where the object came from.Desktop search is now more informative.
Analytics - charts.
Chart data is stored in the cache of 1C:Analytics for 24 hours.Chart data was stored in the cache of 1C:Analytics until the web browser tab was reloaded.The result is now more predictable.
Analytics - dashboards.
You can now copy dashboard widgets.Dashboard widgets could not be copied. It was only possible to create a new widget that had to be configured manually.Simplified dashboard setup. +
Analytics - charts.
You can now set the display range of values on graph axes.The display range of values on graph axes was adjusted automatically based on the displayed data.Chart appearance customization is upgraded.
Analytics - sources.
When using virtual tables of balance and turnovers, balance by periods when there were no turnovers for dimension values can now be supplemented. The balance in the supplemented periods is equal to the balance of the last actual period preceding the supplemented period.When using virtual tables of balance and turnovers, balance by periods were not displayed (there could be gaps in the data) if there were no turnovers for dimension values during these periods.Data display is correct.
Analytics - expression language.
New date functions: DATEDIFF(), BEGINOFPERIOD(), and ENDOFPERIOD().This feature was not provided.Extended the list of date functions.
Analytics - dashboards.
Implemented filter templates for Boolean and Date fields on the dashboard.Filters of the specified types could only be set by a formula.Simplified filter creation.
Analytics - sources.
Improved appearance of the dialog box that is displayed when updating sources of 1C:Analytics. The dialog box now displays more detailed information and does not block the system.The dialog box that was displayed when updating sources of 1C:Analytics showed less information and blocked the system.Improved appearance and behavior of 1C:Analytics when updating sources.
Analytics - expression language.
Implemented the ADD() function to change date and time values.This feature was not provided.Extended the list of date functions.
Analytics - charts.
Pressing ESC closes the field edit window only if the window field values are not changed.Pressing ESC closed the field edit window regardless of whether the data in the window fields was changed or not, which could lead to data loss.The system is now more predictable and user-friendly.
Analytics - expression language.
Improved context hint when editing expression code.The context hint did not work well when editing expression code.The expression editor is now more user-friendly.
Analytics - charts.
Improved chart labels.When there were a lot of labels, they covered each other and the chart looked bad.Improved appearance of charts.
Analytics - charts.
Improved grouping performance.Grouping performance was non-optimal.Improved data retrieval.

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Dumping configurations to files/Restoring configurations from files.
The format version of configuration dump to XML files is now 2.12.The format version of configuration dump to XML files was 2.11.The configuration dump to XML files now supports new platform features.
Data display.
New picture was added to the picture library: StartVideoConferenceThe listed picture was not available in the picture library.The picture library is upgraded.
Full-text search.
Full-text search is now faster when the search is started from 1C:Enterprise language (including global search mechanisms) and filter by metadata is set (the FullTextSearchList.DataArea property).

It will be faster if the full-text search index is built in version 8.3.7 and later compatibility mode.

When filter by metadata was set, full-text search was slow.When filter by metadata is set, full-text search is faster.
Data composition system.
When conditional appearance is used in the Data Composition System, a conditional appearance element with the In overall usage area set is used to style templates of the overall resources horizontally and vertically in the table.

This change is not implemented in 8.3.18 compatibility mode.

A conditional appearance element with the In overall usage area set was not used to conditionally style templates of the overall resources horizontally and vertically in the table.Eliminated unexpected system behavior.
Pictures.
Mobile platform.
Mobile client.
The PictureToProcess object is now available in 1C:Enterprise mobile version. The following object methods are not implemented: SelectKeyArea(), SetColorDepth(), and SetDensity(). The features of other object properties and methods in this case can be found in Syntax Assistant.

For the Picture object, the Width(), Height(), and FileSize() methods are now available in the mobile version. The ColorDepth(), GrayScale(), HorizontalDensity(), and VerticalDensity() methods always return Undefined in the mobile version.

In 1C:Enterprise mobile version, the PictureToProcess object and all methods of the Picture object were unavailable.You can now implement some custom scenarios on mobile devices. For example, display thumbnails on the form (for more efficient use of mobile device resources).
Collaboration system.
You can now exchange a video stream only with the server upon group video calls. To do this, a special server application must be configured on the interaction server.Group video calls were made in p2p mode. That is, the client application exchanged video streams with computers of all video call participants.The load on the client computer upon a group video call and a large number of video call participants can now be reduced. Improved Collaboration System performance if a user has an asymmetric communication channel.
Mobile application builder.
Mobile platform.
Mobile client.
The distribution package of 1C:Enterprise mobile version contains requirements for the versions of the utilities used to build a mobile application.The requirements for the utilities used to build a mobile application were not included in the mobile version distribution package. It was impossible for users to understand which utility versions to install to build a mobile application.It is now possible to understand which versions of the utilities used to build a mobile application to install on the builder computer. If the versions do not match, troubleshooting is more understandable.
Licensing system.
Analytics system.
You can now start a single 1C:Analytics client without a 1C:Analytics client license if no more than 5 client application sessions are connected to the infobase.Starting 1C:Analytics client without its own license was not available.The application developer can use 1C:Analytics for development purposes without the need to obtain a 1C:Analytics client license.
File operations.
Updated distribution package of Read more. file manager. The distribution package comes with an interface in all languages supported by 1C:Enterprise.The distribution package of the file manager was available in two versions: only in Russian and in all languages supported by 1C:Enterprise.Simplified file manager operations. Users no longer need to choose which distribution package they need.
Integration service.
You can now specify that receiving an integration service message will be processed outside a transaction.

New property of the IntegrationServiceChannel configuration object: InTransaction.

Receiving an integration service message was always processed within a transaction.You can now implement more flexible algorithms for integration service channels.
Collaboration system.
Optimized screen sharing module for thin, thick, and web clients. The new screen sharing module requires the Collaboration System server version 10 or later. To use the new screen sharing module in the web client, Google Chrome version 64 or later is required (in addition to the Collaboration System server version).

The optimized version of the screen sharing module allows you to select a monitor to share (if there are multiple monitors), is faster, and loads the CPU of the computer used for sharing less.

The previous screen sharing module is used if the subscriber cannot use the new module version in the video call.

The previous screen sharing module did not allow you to select a monitor to share, had lower performance, and loaded the CPU of the computer used for sharing more heavily.Improved computer screen sharing when using Collaboration System.
Database copies.
Optimized execution of queries in a database copy when a large number of transactions are performed in the main database and data is transferred to the copy not very often.

To enable optimization, restructure the infobase (by updating the configuration or on testing and patching).

Queries executed in a database copy were not optimized.Improved performance of queries that can be executed on a database copy.
Spreadsheet documents.
Improved spreadsheet document switch to compact mode used on mobile devices.Switching a spreadsheet document to compact mode was not optimal.Improved spreadsheet documents view on mobile devices.
Mobile application builder.
Mobile Application Builder no longer supports the following features:
  • Build mobile applications using Apache Ant.
  • Build mobile applications using Android SDK 25 and earlier.
  • Build mobile applications managed by Windows 8.1.

+If you need to use these features, use Mobile Application Builder 8.3.18 or earlier.

Mobile Application Builder supported:
  • Build mobile applications using Apache Ant.
  • Build mobile applications using Android SDK 25 and earlier.
  • Build mobile applications managed by Windows 8.1.
Mobile Application Builder no longer supports obsolete technologies and mobile operating systems.
Mobile platform.
Mobile client.
Mobile application builder.
Starting from mobile version 8.3.19.52, you can build mobile applications for Android in the application bundle format (aab-file).

Changed files in the mobile distribution package.

With Mobile Application Builder, you can build applications in any format depending on the mobile version used to build the mobile application.

With Mobile Application Builder, you can upload any built application option to the application store (but not both at the same time). Before importing version 8.3.19.52 or later to Mobile Application Builder, update the builder to the distribution package version. +

1C:Enterprise mobile version (including Mobile Application Builder) did not support building application bundles (aab files).You can now build mobile applications and upload them to Google Play store.
Localization.
Localized client application interface for Turkmenian (tk).This feature was not provided.1C:Enterprise is now available to Turkmenian-speaking users.
Mobile platform.
Mobile client.
Mobile device-specific features.
Improved recognition of DataMatrix codes using mobile device cameras:
  • New feature: recognition of a light-colored code on a dark background.
  • New feature: recognition of round pixels in the code.
  • Improved recognition of complex codes: on crumpled paper, with reflections, and so on.

The following changes are implemented when recognizing barcodes using mobile device cameras:

  • Automatic setting of 1.5x magnification for easy scanning of small barcodes.
  • Reduced frame rate for recognition.
  • Reduced timeout between consecutive scans to 1.3 seconds.
DataMatrix code recognition did not work in some common situations.

Scanning small barcodes with mobile device cameras was inconvenient. The pause between consecutive scans was 2 seconds.

Improved use of mobile device cameras to scan DataMatrix codes and other barcodes.
Database copies.
Improved performance of initial filling of a database copy.Initial filling of a database copy took more time.Improved performance of initial filling of a database copy.
Spreadsheet documents.
The Save command in spreadsheet documents works as follows:
  • If the file name is not specified or the the spreadsheet document is in the "Read only" mode, a dialog box for selecting a file to save is displayed.
  • If the file name is specified and the spreadsheet document is in the editing mode, it is saved without displaying a dialog box for selecting a file.

This change is not implemented in 8.3.18 compatibility mode.

The Save command in spreadsheet documents was performed in the same way as the Save as command.Eliminated unexpected system behavior.

Table of contents

Transition from the previous version to the version 8.3.19

Table of contents

Version 8.3.18

Version 8.3.18 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.17 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.16 was available.Configurations developed using 1C:Enterprise platform version 8.3.17 or earlier can now run on version 8.3.18 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.18 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.17 after the migration to version 8.3.18, even if you disable the compatibility mode (simply enable it again).
Web client.
Support for the progressive web application (Progressive Web Apps, PWA) is implemented for the web client. A progressive web application is supported for Google Chrome version 73 and later, and if the web client is published using HTTPS protocol.

The Display as a standalone application command is implemented in the Tools and Settings menu.

The ProgressiveWebApplication global context property is implemented.

The ProgressiveWebApplicationName web client start option is implemented.

The progressiveWebApplication element is implemented for default.vrd file.

This feature was not provided.Sending the web client application launch icon to the desktop is now available. The web client (in progressive web application mode) is started in a separate window, and not in a web browser window.
1C:Enterprise script.
Updated asynchronous calls processing. Implemented the option to describe the method as an asynchronous, nonblocking analogue of a usual method. Asynchronous methods always return a Future object. The result of the asynchronous method is returned through this object.

Implemented Asynch modifier used to describe the method. Implemented Future, AddInAsynchCallResult methods. Implemented Wait operator.

The <MethodName>Asynch, Get<PropertyName>Asynch and Set<PropertyName>Asynch methods should be used to work with add-ins. These methods are added automatically by the platform; no add-in modification is required.

For global context methods and 1C:Enterprise language objects starting with Show and Start, analogues with the Asynch name suffix are implemented.

This feature was not provided.

Using asynchronous methods required using special notification handlers.

Using asynchronous methods was improved. +
Internet-enabled functionality.
Web client.
Now you can get information about MAC addresses of network adapters of the current computer in client applications (thin, thick, and web client).

New object: NetworkAdapterInformation. New global context methods: GetNetworkAdaptersInformation(), BeginGettingNetworkAdaptersInformation(), and GetNetworkAdaptersInformationAsync().

For the web client, install the extension to get information about the computer. New methods: BeginInstallingComputerInformationExtension() and BeginAttachingComputerInformationExtension().

This feature was not provided.You can get MAC address of the client computer if it is required for interaction with external systems.
Localization.
Chinese language (zh, zh_CN) support is implemented for NumberInWords() method.This feature was not provided.Simplified the presentation of information for Chinese-speaking users.
DBMS operations.
System requirements.
PostgreSQL DBMS 12 (x86-64) is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 12.2 is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
Common objects.
The DataHashing object can calculate the SHA512 hash function.This feature was not provided.The list of supported hash functions is extended.
Client application form.
Implemented the feature to specify a formatted string as the value of the Text property for the following planner items: PlannerItem, PlannerDimension, PlannerDimensionItem, PlannerBackgroundIntervalLabel, TimeScaleItemLabel. We have implemented the NewItemsTextType property for the Planner type form attribute, which allows to specify which text can be entered in new user-created planner items.

Implemented the feature to set actions for the planner item. Implemented the PlannerItem.Actions property. You can specify various appearance properties (accessibility, picture, presentation, alignment, etc.) for each action. Implemented the feature to configure various system reactions to the selection of actions or clicking the hyperlinks in the planner items.

The following events are implemented for planner field: OnURLClick, OnPlannerActionClick.

Implemented the feature to create planner items that are not user-editable. Implemented the PlannerItem.EditingPermissionMode property.

Implemented the feature to change the border color for planner background interval. Implemented the PlannerBackgroundInterval.BorderColor property.

Implemented the feature to set the border for planner, planner background interval and planner item. Implemented the Border property for Planner, PlannerBackgroundInterval, PlannerItem objects.

The Text parameter of BeforeCreate event of the planner extension for form field may have the values of Text and FormattedString type.

The Text parameter of Add() method in PlannerDimensionCollection, PlannerDimensionItemsCollection and PlannerBackgroundIntervalLabelsCollection objects may have the values of Text and FormattedString type.

The Text parameter of Insert() method in PlannerDimensionCollection, PlannerDimensionItemsCollection and PlannerBackgroundIntervalLabelsCollection objects may have the values of Text and FormattedString type.

For system enumeration

PlannerCommandSource the following new values are implemented: URL and Action.

For system enumeration PlannerCommandGenerationParameters the URL, Action, Dimension values are implemented.

For system enumeration StandardPlannerCommand the GotoURL, CopyURL, ExecuteAction values are implemented. +

These features were not provided.New planner use features. Implementing a more friendly user interface using a planner is now possible.
Global search.
Implemented the feature to set custom actions to the global search results. The set actions are displayed next to the global search result and are available for execution directly from the list of global search results.

Implemented the GlobalSearchResultItem.Actions property. Implemented the OnGlobalSearchResultActionSelect application module event handler.

These features were not provided.Enhanced global search results formatting options.
Configuration extensions.
Administration tools.
Implemented the feature to use configuration extensions for the /MergeCfg Designer start command line command. The .cfe file may be used as command option. The -Extension option is implemented for this command to specify the extension, which the command will be executed for.The /MergeCfg command did not allow to use the extensions.Using extensions in automated scenarios in development, testing and maintenance of applications is now possible.
Configuration extensions.
Implemented the feature to expand the adopted objects attribute types, except for:
  • common attribute types;
  • attributes with external data source types;
  • attributes having a definable type;
  • Type attribute of the chart of characteristic types.

+Selecting actions for individual types when comparing and combining the extensions was implemented.

This feature was not provided.New extension features.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Collaboration system.
Implemented the feature to hide all important notifications with one click in 1C:Enterprise - Startup and Notifications application. This feature appears if three (or more) notifications appear.

The button for clearing notifications in the notification center of the client application has Clear label now.

Hiding all important notifications with one click in 1C:Enterprise - Startup and Notifications application was not available.

The button for clearing notifications In the notification center of the client application was called Clear notifications.

Improved using the notifications. A large number of notifications can be hidden in one action.
Collaboration system.
Implemented highlighting of new messages in an open conversation.

Implemented an application title representation in the incoming video call title.

Implemented a feature to insert pictures using Shift+Ins hot-key.

When scrolling the list of messages up with the mouse wheel, the new messages are loaded automatically.

When sending a message, the read flag for this conversation is set.

Implemented caching of attachment files when they are received or opened (in the thin client) or received (in the web client).

Implemented the feature to quote messages. Implemented the Quote command in the selected text context menu. The ">" character in the first position of the message line is the quotation flag.

Implemented the feature to copy a message with attachments.

For a client application running in Linux or Windows, the number of unread messages in the notification center is displayed as a number on the application icon in the taskbar and on the icon of the open notification list command.

These features were not provided.Improved user operations in the collaboration system.
Web client.
Add-ins.
64-bit add-ins are now supported by the web client in 64-bit Google Chrome and Mozilla Firefox web browsers running Windows. +In 64-bit Google Chrome and Mozilla Firefox web browsers running Windows, the web client used 32-bit add-ins.Improved support of 64-bit Google Chrome and Mozilla Firefox web browsers.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Standalone server.
Faster .DT file import to the infobase when using the standalone server management utility (ibcmd).Importing a DT file to the infobase of a standalone server (using ibcmd utility) took longer.Faster DT file import to the infobase of the standalone server.
Standard functions.
Faster opening of the standard function main form for event log browsing.Opening the standard function main form for event log browsing took longer.Improved event log browsing.
Server clusters.
The time to obtain a client license by the session is significantly reduced in the following cases:
  • Mass user operations start.
  • Restarting cluster managers after a software or hardware failure.
Obtaining licenses took a lot of time and significantly slowed down the sessions starting in case of mass starting (or restarting) of the client sessions.Eliminated unexpected system behavior.
Data display.
Server clusters.
Improved performance of the GetStringDeclensions() and GetStringDeclensionsByNumber() methods if the declension feature was used by several users at the same time when using client/server mode of the infobase.If the GetStringDeclensions() and GetStringDeclensionsByNumber() methods are used by several users at the same time in the client/server mode of the infobase, execution of the methods took longer.Eliminated unexpected system behavior.
Data access restrictions.
Improved performance of StrContains() function used in data access restriction templates. +Performance of StrContains() function used in data access restriction templates, was insufficient.Improved performance of StrContains() function used in data access restriction templates.
DBMS operations.
When using queries from the platform to Microsoft SQL Server DBMS, their plans are cached in the same viewpoint of properties as when executing these queries from SQL Server Management Studio with default settings. This does not result in generation of a different query plan when the query is executed again in SQL Server Management Studio, which simplifies the analysis of the query operation. +When using the same query in Microsoft SQL Server DBMS directly from the platform and from SQL Server Management Studio, different query plans could be generated.Simplified analysis of query plans that are used in Microsoft SQL Server DBMS.
Database copies.
Optimized the process of transferring completed transactions to the database copy.The process of transferring completed transactions to the database copy took longer.Faster transfer of data to the database copy.
Data composition system.
Dynamic lists.
Faster opening of report and dynamic list settings, as well as generation of data composition templates, if child fields of fields for which a large number of characteristics are defined are used in the data composition settings.If the data composition settings involve child fields of fields for which a large number of characteristics are defined, opening report and dynamic list settings, as well as generating data composition templates took a lot of time.Faster opening of dynamic list and report settings forms.
Data access restrictions.
In data access restriction queries, a feature to replace subqueries that do not depend on the protected table with the result of their operation is implemented. Replacing one subquery for each protected table is supported. The result of calculating such subqueries is cached in the working process RAM.Queries for data access restrictions were not subjected to additional processing and were always performed in their original form.Improved performance of data access restriction queries. As a result of the change, the DBMS can plan a more efficient query.
Spreadsheet document.
Processing PDF documents.
Improved spreadsheet document export to PDF performance.Exporting a spreadsheet document to PDF required more time.Improved performance of spreadsheet document export to PDF format. Possible reduced size of the resulting PDF document if the original spreadsheet document contains cells with changed text orientation.
Development tools.
Faster standalone configuration generation. +Standalone configuration generation took more time.Faster standalone configuration generation.
Spreadsheet documents.
Improved performance of spreadsheet documents with numerous merged cells in a great number of rows.Operations with a spreadsheet document with numerous merged cells in a great number of rows took more time.Improved performance of spreadsheet documents.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Standalone server.
A partial import and export of configurations from files has been implemented for the standalone server management utility (ibcmd).

The following items are implemented for the config export command:

  • The --sync option allows to synchronize the configuration and the export directory.
  • The objects command allows to export only those configuration objects that are specified in the file, which is the command option.
  • The info command allows to get information about the infobase used by the standalone server.
  • The status command allows to get the differences between the configuration and the export directory.
  • The base command allows to export changes to the infobase configuration relative to the directory with previously exported files.
  • The all-extensions command allows to export all the infobase extensions to files. +

The following commands are implemented for the config import command:

  • The files command imports data from files that are listed as a command option.
  • The all-extensions command allows to import all the extensions that are in the specified directory from the files.
The standalone server management utility (ibcmd) allowed only complete configuration import and export from/to files.Expanded standalone server capabilities.
Internet-enabled functionality.
Implemented the feature to receive and set a custom text type for an email message when using InternetMail feature.

Implemented CustomText value for the MailTextType enumeration. Implemented CustomTextType property for the InternetMailText object, which contains the actual text type from the email Content-Type property. If the platform cannot define the mail message type, the InternetMailText.TextType property is set to MailTextType.CustomText.

The TextType parameter of the InternetMailTexts.Add() method may have a String type value.

When generating the mail text that will be actually sent to the mail server, the charset parameter with the encoding specified in the InternetMailTexts.Encoding property will be added to (or replaced in) the Content-Type header.

This change is not implemented in 8.3.17 version compatibility mode.

When using Internet mail, receiving the actual type of mail message was not available. If the platform could not define the mail message type, the InternetMailText.TextType property was set to MailTextType.SimpleText.

When generating the text of the mail to be actually sent to the mail server, the charset parameter in the Content-Type header was not generated.

Improved working with emails such as meeting invitations that are sent from electronic calendars when using Internet mail.
Collaboration system.
Implemented a feature of creating a robot (bot) that runs on the 1C:Enterprise server (does not require a running instance of the client application) for the collaboration system.

Implemented the CollaborationSystemBot object. The ProcessBots(), NewBot(), GetBot(), GetBots() methods were implemented for collaboration system manager.

Implemented system background jobs for bot operations.

Implemented the bot using features in the collaboration system management system data processor.

Implementing a robot (bot) required constantly running client application. Distinguished entity to describe bots was absent.Simplified the robots (bots) creation in the collaboration system. A working robot does not require a running client application.
Server clusters.
New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is SystemBackgroundJob.RecalcTotals. Implemented the Number of totals recalculation job parameter for the Infobase parameters dialog box. There are 4 recalculation background jobs by default.

New global context methods: GetTotalsRecalculationJobsCount() and SetTotalsRecalculationJobsCount().

Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers.New feature: totals are recalculated faster upon infobase restructuring, testing, and repair.
HTML support.
Availability of the HTMLDocumentShell.TemplateLanguageCode property in the Syntax Assistant was removed for the thick client.The HTMLDocumentShell.TemplateLanguageCode property in the Syntax Assistant was available for the thick client.Fixed bug in the Syntax Assistant.
Spreadsheet document.
Processing PDF documents.
When saving a spreadsheet document to PDF, the JPEG pictures are saved in a compressed format. The picture format does not change.When saving a spreadsheet document to PDF, the pictures were saved without using JPEG compression algorithms.Reduced size of PDF documents if the original spreadsheet document contains JPEG images.
Configuration extensions.
Implemented a feature to continue full-fledged using of the configuration, if the extensions that perform data extension were not attached for some reason when starting the configuration.

In this case, the default values for the corresponding types will be written in the extended attributes. +

If not all extensions that perform data extension are attached on session start, the application could read the extended configuration data of successfully attached extensions without errors. At the same time, an attempt to write an object, which data is supplemented by a disabled extension, was not available. +An application that uses an extension, which performs data extension, remains fully functional (except for non-attached extensions), if not all extensions that perform data extension are attached.
Common objects.
The Russian letter "ё" is now supported by the GetStringDeclensions() and GetStringDeclensionsByNumber() methods.The GetStringDeclensions() and GetStringDeclensionsByNumber() methods replaced "ё" with "е" and performed resulting string declension after that.The Russian letter "ё" is no longer replaced with "е" when using GetStringDeclensions() and GetStringDeclensionsByNumber() methods.
1C:Enterprise script.
The Number() function allows to convert exponential number representations to numbers only if the absolute value of that number order does not exceed 1,000. In the web client, the Number() function does not support conversion from the exponential number representation.The Number() function allowed exponential number representations to be converted to numbers without limiting the order value. This could cause a very large memory consumption and a very large amount of time spent on arithmetic operations with these values.Eliminated unexpected system behavior.
Add-ins.
The name of the temporary file, which the add-in is saved to before attachment, includes the name of the original add-in file. Thus, the full name of the add-in file consists of a prefix (assigned by the platform according to the standard algorithm for generating the temporary file name) and a suffix (which includes the name and extension of the original add-in file obtained from the add-in manifest).The name of the temporary file, which the add-in is saved to before attachment, consisted only of an arbitrary temporary file name (with the .tmp extension) which was generated by 1C:Enterprise.Simplified diagnostics of faults caused by problems in attached add-ins. Various event logs will clearly show the name of the add-in, in which the error occurred.
Applied objects.
If the main form attribute is ConstantsSet and there are no constants in the set when the form is opened (due to access right restrictions or displayed type restrictions), methods of reading data and writing data to an infobase are not called for the constant set upon opening or closing the form.If the main form attribute was ConstantsSet and there were no constants in the set when the form was opened (due to access right restrictions or displayed type restrictions), unavailable infobase constants were filled in with defaults for their types.Eliminated unexpected system behavior.
Client application form.
Changed the behavior of some buttons in the objects and record sets forms:
  • The Delete, Reread buttons are not available in the new object or the information register record forms and external data source table.
  • The Mark for deletion button is not available in the new object form.
  • The Activate button is not available in the new job form.
  • When clicking Copy, Mark for deletion, you will be offered to save the object and then perform an action or refuse an action in the new object, new information register record forms, or the external data source table record.
The Delete, Reread, Mark for deletion, Activate and Copy commands were always available in the new object, information register records forms or external data source records.Eliminated unexpected system behavior.
Common objects.
If the ConvertibleSplitterOfLines property is not set for DataReader object or is set to Chars.CR+Chars.LF, and the text file being read contains consecutive Chars.CR characters between the combinations of Chars.CR+Chars.LF, the ReadChars() method will be executed as follows:
  • Each pair of Chars.CR+Chars.LF will be replaced with Chars.LF.
  • All other characters are returned as is.

+This change is not implemented in 8.3.17 version compatibility mode.

If the ConvertibleSplitterOfLines property was not set for DataReader object or was set to Chars.CR+Chars.LF, and the text file being read contained consecutive Chars.CR characters between the combinations of Chars.CR+Chars.LF, the ReadChars() method could violate the sequence of characters (including permutation of characters, deletion and addition of Chars.CR or Chars.LF). +Eliminated unexpected system behavior.
Charts.
Improved the Gantt chart representation.

This change is not implemented in 8.3.17 version compatibility mode.

The Gantt chart looked different.Merging of connection lines is excluded, the number of connection lines of complex shape is reduced, the appearance of the chart items is improved on the Gantt chart.
Database configuration update.
When using the optimized infobase restructuring feature, the actual restructuring will be performed if:
  • The following changes to the configuration objects were made:
  • The tables of restructured objects do contain data that must be changed during the update process. If there is no such data, no action is taken and the restructuring is considered completed.
The optimized infobase restructuring feature always performed database tables restructuring if the following changes were made to the configuration objects:
  • A type was removed from a composite type.
  • A recorder was removed from the information register, accumulation register or accounting register.
  • A value was removed from enumeration.
In some cases, significant improvement of the optimized infobase restructuring feature performance can be reached.
Data display.
If the parameter of the GetStringDeclensions() or GetStringDeclensionsByNumber() methods contains unequal number of opening and closing brackets or quotes, the platform will automatically fix this issue and decline the correct phrase. The resulting number of brackets or quotes will match the number of brackets or quotes in the parameter.If the parameter of the GetStringDeclensions() or GetStringDeclensionsByNumber() methods contained unequal number of opening and closing brackets or quotes, the platform threw an exception.The GetStringDeclensions() and GetStringDeclensionsByNumber() methods behavior became more logical.
Full-text search.
If a full-text search is used to search by the beginning of a line, all the results are highlighted in the search results representation, regardless of the number of results.If a full-text search was used to search by the beginning of a line, and a large number of words were found that satisfied the search query as a result of the search, the found words may not be highlighted in the search results.Eliminated unexpected system behavior.
Queries.
Query Wizard generates missing aliases of query fields using the same scheme as the query execution functionality.

This change is not implemented in 8.3.17 version compatibility mode.

Query Wizard could generate missing aliases of query fields using a scheme different from the scheme used upon query execution.Now automatic generation of aliases of query fields (in different platform tools) is consistent.
Collaboration system.
Implemented the standard collaboration system commands, which allow to copy the attachment and quote the message. Implemented the CopyAttachment and QuoteMessage values for CollaborationSystemStandardCommand system enumeration.

Implemented the default constructor for CollaborationSystemUserIDCollection object.

Implemented the VideoconferencesAreAvailable(), GetMaximumVideoconferenceParticipantsNumber() and StartVideoconference() methods for CollaborationSystemManager object.

These features were not provided.Expanded the collaboration system usage capabilities.
Add-ins.
Web client.
An attempt to use a non-existent add-in method or property in web client generates an error that can be caught in the Try–Except clause. The method or property is not called at all.

The behavior in thick, thin, and web client applications is now the the same.

An attempt to use a non-existent add-in method or property in web client initiated a call from the web client. If a method or a property was missing, an error occurred only in the error handler specified in notification details. The error could not be caught in the Try–Except clause.Web client behavior is now identical to thin and thick client behavior.
Mobile platform.
Mobile client.
Implemented the HomePageSettings and HomePageForms objects on the mobile application server and the standalone mobile server.The HomePageSettings and HomePageForms were not available on the mobile application server and the standalone mobile server.Now you can customize the application home page on your mobile device.
Client application form.
In thick client and Designer, improved display of a table box whose header or footer contains numerous columns grouped into a composite multiline column using the Position of table box column property. +In thick client and Designer, a table box whose header or footer contained numerous columns grouped into a composite multiline column using the Position of table box column property, was displayed with delay.Eliminated unexpected system behavior.
Data composition system.
The DCS template generator calculates the width (in cells) of each resource template displayed in a DCS table column as the maximum width of all templates displayed in this DCS table column (both generated and predefined templates). If predefined templates are specified for group and resource templates, the number of recourses specified for them in the data composition settings is not considered for such groups.

This change is not implemented in 8.3.17 version compatibility mode.

The DCS template generator calculated the width (in cells) of each resource template displayed in a DCS table column based on all resources displayed in this template (in the data composition settings) and predefined templates. If the estimated template width was bigger than the predefined template width for a resource template specified for a table row/column intersection, the width of a template to create was equal to the estimated width. +Eliminated unexpected system behavior.
Data composition system.
When the Data Composition System groups by a calculated field, a presentation expression of this field (if specified) is used in this group and its nested groups when this field is displayed in the data composition result.

This change is not implemented in 8.3.17 version compatibility mode.

When the Data Composition System grouped by a calculated field, a calculated field presentation was displayed in detailed records only.Eliminated unexpected system behavior.
Client application form.
For a table that displays the value tree with one column, implemented the following algorithm for calculating the column width depending on the width of the text in rows of the tree being displayed:
  • For table cells with disabled automatic calculation of the cell height, the table cell width is calculated based on the width of the text displayed in cells.
  • For table cells with enabled automatic calculation of the cell height, the table cell width is calculated based on the width specified in column properties upon configuration development. If there is less than half of the table width for text display in the visible table area, the text area width becomes equal to the table width, provided that this width is bigger than the width of the selected area.
  • The actual table column width is calculated as the maximum width of all cells displayed in the visible table area.

For a table whose cell (not a complete row) is selected upon row selection, horizontal scrolling is done when you move between table rows or activate a row so that the text is fully displayed in the visible table area. If a text does not fit in the visible area, the text area is aligned to the left edge of the table.

For a table that displayed the value tree with one column, the column width and position of the text in a column did not depend on the text displayed in the tree.Eliminated unexpected system behavior.
Configuration extensions.
When the ChangeAndValidate annotation is used in configuration extensions, the applicability check does not consider changes where empty strings and strings formed only with space and tab characters are added or deleted.When the ChangeAndValidate annotation was used in configuration extensions, the applicability check considered changes where empty strings and strings formed only with space and tab characters were added or deleted.Decreased the amount of false positives of the extension applicability check. +
Spreadsheet document.
Mobile platform.
Mobile client.
Improved spreadsheet document conversion to compact mode (on a mobile device):
  • Now you can move spreadsheet document cells that are under horizontal cell merge.
  • Implemented automatic highlighting for moved cells. A single spreadsheet document column is displayed in a single color. Highlighting does not apply when the text color is explicitly specified for a spreadsheet document cell.
  • Highlighting also does not apply when cells are not moved upon spreadsheet document conversion to compact mode.
  • Now dividing lines of a spreadsheet document are lighter. +
The algorithm for spreadsheet document conversion to compact mode was different. The resulting spreadsheet document was not well suited for a mobile device.Improved spreadsheet document display on a mobile device (compact spreadsheet document mode).

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Configuration extensions.
Calling extended form methods from an extension using the Execute() method is no longer supported. Only the methods that are available through the ThisObject property can be called.

It is recommended to analyze the extensions and refactor them, if necessary.

This change is not implemented in 8.3.17 version compatibility mode.

Calling extended form methods from an extension using the Execute() method was supported. A form extension can only use the documented interface for using an extended form. A “documented interface" refers to methods declared in a form module using the Export keyword.
Administration tools.
The service message output file, which is specified in the /Out command-line option of the client applications and Designer start, is generated in UTF-8.The service message output file, which was specified in the /Out command-line option of the client applications and Designer start, was generated in the operating system encoding.The service message output file is always generated in the same encoding, regardless of the operating system encoding.
Linux.
System requirements.
Standalone server.
When using Linux, the feature was implemented to simultaneously install several versions of 1C:Enterprise, including those that differ only in the last (fourth) digit of the number.

Implemented automatic selection of the started client application version.

Changed starting of the server cluster and the location of the srv1cv83 and srv1cv83.conf files.

Implemented the feature to automatically update the client application over the network and from the web server. Implemented the feature to specify the location of client application distribution packages in the web client publishing dialog (in the Linux version of Designer).

The PublishDistributiveLocationLinuxDEB64, PublishDistributiveLocationLinuxDEB32, PublishDistributiveLocationLinuxRPM64, PublishDistributiveLocationLinuxRPM32 parameters are implemented for conf.cfg file. Implemented the pubdstlindeb64, pubdstlindeb32, pubdstlinrpm64, pubdstlinrpm32 attributes for the <point> item of default.vrd file.

Implemented the lindeb64, lindeb32, linrpm64, linrpm32 properties for the pubdst parameter of the standalone server configuration file.

These features were not provided.Using several versions of 1C:Enterprise simultaneously is now available when using Linux.
Data display.
The Parameters parameter of StringWithNumber() method was renamed to NumberFormatString. A number format string similar to the Format() method can be passed to this parameter.

The StringWithNumber() method generates a number representation considering the current session or the passed format string locale.

The StringWithNumber() method always generated a number representation considering the locale code passed as the method parameter and did not consider the current session locale. +Eliminated unexpected system behavior.

The result of the StringWithNumber() method now matches the current session locale.

Applied objects.
The following changes have been implemented for document journals:
  • The rows of the document journal table corresponding to documents, for which there is no Read right, cannot be retrieved using the query language (dynamic list, data composition system).
  • The rows of the document journal table corresponding to documents, for which there is no View right, cannot be retrieved using the data composition system when interactive rights check is enabled, for example, in a dynamic list and by default in reports.
  • A column of the document journal is available if at least one attribute included in this column is available.
  • The interactive properties of the Password mode, Format, Hint, Highlight negative and Multiline mode document journal columns in the data composition system are received from the corresponding properties of the document attributes included in the journal column.
  • The data composition system uses the Quick Select property for fields with types of references to object tables of external data sources. +

This change is not implemented in 8.3.17 version compatibility mode.

The following behavior of document journals was observed:
  • The rows of the document journal table corresponding to documents, for which there was no Read right, could be retrieved using the query language, if there were Read rights for the log table.
  • The rows of the document journal table corresponding to documents, for which there was no View right, could not be retrieved using the data composition system when interactive rights check was enabled, for example, in a dynamic list and by default in reports.
  • A column of the document journal was available if all the attributes included in this column were available.
  • The interactive properties of the Password mode, Format, Hint, Highlight negative and Multiline mode document journal columns in the data composition system were not received from the corresponding properties of the document attributes included in the journal column.
  • The data composition system did not use the Quick Select property for fields with types of references to object tables of external data sources.
Eliminated unexpected system behavior.
Collaboration system.
Reviewed the feature for working with actions in the collaboration system messages.

The CollaborationSystemMessageActionsCollection type was implemented to generate the list of actions. The CollaborationSystemMessageActionsCollection becomes a value type for the CollaborationSystemMessage.Actions property. This change is not implemented in 8.3.17 version compatibility mode.

Implemented the OnCollaborationSystemActionSelect event handler for application module.

The AttachMessageActionHandler() and DetachMessageActionHandler() are collaboration system manager methods considered obsolete and are not recommended for use.

It is necessary to change the algorithms for working with actions in the collaboration system messages in applications.

A list of values was used to specify the list of actions of the collaboration system. Setting the collaboration system message action handlers required using the AttachMessageActionHandler() and DetachMessageActionHandler() collaboration system manager methods.Procedure of using actions is unified with the other platform features.
Data composition system.
If the data composition schema query contains union, and a filtering field is available for applying filter only (and is not available for selection) in several union parts, then the filter is applied only to the union parts where this field is available for filtering.

It is recommended to review data composition schemas that contain queries with unions.

This change is not implemented in 8.3.17 version compatibility mode.

When applying a filter to a data set query containing a union, the filter was applied to all the union sections if at least one section a filtering field available for filter.The result of applying filter in the data composition schema has become more predictable.
Full-text search.
When setting the value of the FullTextSearchList.SearchArea property, an exception is thrown if the array being set contains an item that is not a metadata object.

This change is not implemented in 8.3.17 version compatibility mode.

When setting the value of the FullTextSearchList.SearchArea property, the validation of the value being set was not performed, however, when an attempt was made to get the search result (FullTextSearchList.First Part() method), an exception was thrown with incomprehensible text.Validation of parameters is aligned with standard practices. The error message now corresponds the detected error.
Charts.
The DataSource chart property is not available in the thin client and web client. When attempting to set the value of this property using 1C:Enterprise language, an error is generated.

This change is not implemented in 8.3.17 version compatibility mode.

The attempt to set the DataSource chart property depended on the client application:
  • An error was generated in the web client.
  • The setting worked in the thin client and the data was displayed in a chart until the first server call. The link of the chart to the data was lost after the first server call.
Eliminated unexpected system behavior.
Charts.
Interactive chart editing with a set data source is not supported.

This change is not implemented in 8.3.17 version compatibility mode.

For a chart with a set data source, the following behavior was observed when attempting to edit interactively:
  • Chart values were edited.
  • The values in the data source did not change.
  • When changing values in the data source, all the changes made manually were lost and the chart displayed data from the data source.
Eliminated unexpected system behavior.
Client application form.
Window settings for thin client, web client, mobile client and mobile platform are stored with different settings keys suffixes. When changing the configuration compatibility mode, the following actions are performed:
  • When setting the Do not use compatibility mode:
  • When setting the Version 8.3.17 compatibility mode:

    • +

    New settings keys are given in the documentation. +If the configuration uses direct operation with the window settings, it is recommended to analyze the program code that interacts with the settings and make appropriate changes to it.

This change is not implemented in 8.3.17 version compatibility mode.

These features were not provided.

Settings were stored separately for the web client (one setting) and all other client applications (another setting).

The client application window settings for different types of client applications are stored separately and do not mix with each other. Implementing software operations with the window settings of a single type of client application is simplified.
Data composition system.
If condition Contains, Does not contain, Like, Not like, Begins with, or Does not begin with is specified for data composition filter set at the data set level and the condition string contains a single double quote ("""), Data Composition System escapes such characters automatically upon data composition template generation.

This change is not implemented in 8.3.17 version compatibility mode.

If condition Contains, Does not contain, Like, Not like, Begins with, or Does not begin with was specified for data composition filter set at the data set level and the condition string contained a single double quote ("""), Data Composition System did not escape such characters upon data composition template generation. Executing such data composition might have caused an error.Eliminated unexpected system behavior.
Information registers.
Only register records with the Activity property set to True are included in the result of a query to a virtual table of the SliceLast information register.

This change is not implemented in 8.3.17 version compatibility mode.

All register records were included in the result of a query to a virtual table of the SliceLast information register, regardless of the Activity property value.Eliminated unexpected system behavior.
Input by string.
Global search.
Dynamic list.
Full-text search.
Implemented the search query complexity limitation. The overall search query length must not exceed 1000 characters and 32 words. The limitations are implemented for the following mechanisms:
  • Input by string.
  • Global search.
  • Dynamic list search string.
  • Full-text search.

+In the parameter structure of the GetChoiceData() method, the LimitSearchString parameter that provides search without analyzing a search query is expected.

Implemented the FullTextSearchList.LimitSearchString property. If this property is set to False, full-text search does not analyze a search query.

This change is not implemented in 8.3.17 version compatibility mode.

There was no search query complexity limitation, except for the search string of a dynamic list where the search string was not to exceed 1000 characters and 20 words.Complexity of a search query to built-in search tools is limited to avoid high server load and unexpected shutdown due to a complex search query.
Add-ins.
Examples from add-in development technology are switched to build with CMake.

Static libraries for creating adapters for web browsers running Windows are built with Microsoft Visual Studio 2017 compiler that supports Windows XP.

Developers who develop circulation add-ins must develop an add-in for all operating systems from the list of system requirements Read more.. Web client adapters for Windows must be built with Microsoft Visual Studio 2017 compiler that supports Windows XP.

Developers whose add-ins are developed for a specific deployment case can use the compiler they used for supported operating system versions. Still, use Microsoft Visual Studio 2017 compiler that supports Windows XP to build web client adapters for Windows.

Changes were made to development technology for add-ins (read more).

Examples from add-in development technology were built with Microsoft Visual Studio 2013.A more modern set of tools is used to build demo add-ins.
Client application form.
A line that does not fit to width in decorations, label fields, or field headers is broken by a word separator closest to the form item edge.

Upon disabling the compatibility mode, we recommend that you check that forms with texts that do not fit to width in decorations, label fields, or field headers are displayed correctly.

This change is not implemented in 8.3.17 version compatibility mode.

A line that did not fit to width in decorations, label fields, or field headers could be broken by a word separator that was not closest to the form item edge.Eliminated unexpected system behavior.

Table of contents

Renamed objects

ObjectThe old nameThe new name
System event log event names.
  • _$InfoBase$_.InfoBaseAdmParamsUpdate;
  • _$InfoBase$_.InfoBaseAdmParamsUpdateError;
  • _$InfoBase$_.TARInfo;
  • _$InfoBase$_.TARMess;
  • _$InfoBase$_.TARImportant;
  • _$InfoBase$_.SecondFactorAuthTemplateNew;
  • _$InfoBase$_.SecondFactorAuthTemplateUpdate;
  • _$InfoBase$_.SecondFactorAuthTemplateDelete.
  • _$InfoBase$_.ParametersUpdate;
  • _$InfoBase$_.ParametersUpdateError;
  • _$InfoBase$_.VerifyAndRepairInfo;
  • _$InfoBase$_.VerifyAndRepairMessage;
  • _$InfoBase$_.VerifyAndRepairImportant;
  • _$InfoBase$_.SecondAuthenticationFactorTemplateNew;
  • _$InfoBase$_.SecondAuthenticationFactorTemplateUpdate;
  • _$InfoBase$_.SecondAuthenticationFactorTemplateDelete.
Designer description for a name of a property with roles that will limit mobile user capabilities.

+

  • Limiting roles of a standalone configuration.
  • Limiting roles of a standalone mobile application.
Check box of the configuration check dialog box that enables configuration check in the standalone mode. +
  • Mobile client (standalone mode).
  • Mobile client (standalone mode) and standalone mobile server.
Changed the File.Exist() and FileDialog.CheckFileExist methods names.

The former names are supported for compatibility purposes.

  • File.Exist().
  • FileDialog.CheckFileExist.
  • File.Exists().
  • FileDialog.CheckFileExistence.
CopyFile() method description option.
  • FileCopy().
CopyFile().
The name of the method for verifying that a purchase has been made. The former name is supported for compatibility purposes.

+

  • Purchased().
  • CheckPurchase().
The names of the files with the Linux installation packages that contain the client application distribution packages.
  • win-mac-clients-distr-A.B.C-D.i386.rpm
  • win-mac-clients-distr-A.B.C-D.x86_64.rpm
  • win-mac-clients-distr_A.B.C-D_amd64.deb
  • win-mac-clients-distr_A.B.C-D_i386.deb

+In this list, A.B.C-D is the full version number of 1C:Enterprise.

  • win-mac-clients-A.B.C.D-distr-A.B.C-D.i386.rpm
  • win-mac-clients-A.B.C.D-distr-A.B.C-D.x86_64.rpm
  • win-mac-clients-A.B.C.D-distr_A.B.C-D_amd64.deb
  • win-mac-clients-A.B.C.D-distr_A.B.C-D_i386.deb

+

In this list, A.B.C.D and A.B.C-D are the full version number of 1C:Enterprise
The global context property that allows accessing data of the link used to start the application. The previous property name is supported for compatibility.
  • StartupURL.
  • StartupURLNavigationData.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Mobile client.
Implemented the feature to control the automatic image rotation when using the MultimediaTools.MakePhoto() method. To do this, the AutoRotate option is implemented in this method.When using the MultimediaTools.MakePhoto() method, the mobile version always rotated the resulting image if the orientation of the phone at the time of taking the photo did not match the orientation of the resulting photo.Improving the performance of taking photos by disabling the resulting photo turning is now possible.
Client application form.
Implemented the grouping of fields in a system form, which is generated for editing a form table row (not associated with a dynamic list), if such grouping is implemented in the table settings. Only the first level of grouping is displayed. Other grouping levels are not displayed. They are placed in the parent group of the first level instead.All the table row fields were displayed in a list without grouping in a system form, which was generated for editing a form table row (not associated with a dynamic list). +Improved automatically generated form for editing a form table row.
Development tools.
Now you can set up module check in the standalone mode of a mobile client in Service – Parameters – Modules – Check. Implemented the Mobile client (standalone mode) and a standalone mobile server check box. +This feature was not provided.Simplified real-time check of modules to be run in the standalone mode of a mobile client.
Printing tools.
Mobile platform.
Mobile client.
Now the mobile application supports printers that are supported by the used mobile operating system.

You can switch between printing through the operating system and printing using the platform tools (printers that support PCL3 and ZPL languages) in infobase settings on your mobile device (in Service and settings - Settings) or in Mobile Application Builder (the Print mode application settings property).

1C:Enterprise mobile platform supported only printers supporting PCL3 and ZPL languages.Extended list of printers supported by 1C:Enterprise mobile platform.
Mobile platform.
Mobile client.
Updated permission management for a mobile application built using Mobile Application Builder. Implemented the functionality mechanism that combines a mobile application permission and a text displayed to a user upon request for a permission. Included the mobile version functionality module in the mobile application.

If the functionality is disabled, the matching module will not be included in the build and an attempt to use this functionality will generate a runtime exception (on a mobile device).

Settings of mobile application functionalities can be accessed using the configuration property Used mobile application functionality.

Before you build a configuration to be dumped using version 8.3.18, we recommend that you check that the required functionality is specified correctly for the configuration.

The mechanism of mobile application permission management was different. It did not affect the total size of an application to build. A disabled permission might not affect performance of a built application.Now it is easier to manage the used mobile application functionality. When a developer specifies a functionality, they must also specify the text to be displayed to a user upon request for a permission and make this functionality available for use.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Queries.
Common attributes / Data separation.
In infobase file mode, execution of a query where an inner join between object data and its tabular section is being created is faster now. The upgrade is valid if an object used in a query is part of a common attribute that is a separator.In infobase file mode, it took more time to execute a query where an inner join between object data and its tabular section was being created for an object included into the separator.Eliminated unexpected system behavior.
Development tools.
Now you can press Ctrl+Alt+E to abort long-running operations on Windows. You can still press Ctrl+Break for this purpose. Both shortcuts can be used at the same time.To abort long-running operations, you could press Ctrl+Break on Windows.Now you can abort long-running operations on devices without the Break key.
Charts.
A chart tooltip is no longer covered by a formatted document field or the planner field. A chart tooltip is displayed without semitransparency if a thin or thick client application runs Linux or macOS.A chart tooltip could be covered by a formatted document field or the planner field. It was impossible to view some tooltip information. +Eliminated unexpected system behavior.
Configuration extensions.
New feature: you can change data of a configuration object whose attribute types are changed by an inactive extension.

When reading objects with attribute types modified by disabled configuration extensions, values stored in a database will be converted to configuration types, ignoring inactive extensions.

On recording, only changed attributes will be updated.

Information about disabled extensions is added to an error report. Changed the format of the report.json file to which collected error information is placed automatically.

We recommend that you use this mode as emergency mode when you need to update an application infobase if there are extensions that are incompatible with a new configuration version.

It was not possible to change data of a configuration object whose attribute types were changed by an inactive extension.Simplified configuration update if an extension that modifies attribute types of an extended configuration becomes inactive once the extended configuration is updated.
Mobile platform.
Mobile client.
Mobile application builder.
Now you can open the mobile application by clicking an URL. You can set up schemas and links the mobile application reacts to in Designer or Mobile Application Builder. Now the configuration supports navigation to the application when clicking an URL.

New configuration property: MobileApplicationURLs. New handler in the application module: URLNavigationProcessing(). New global context method: GetExternalURL().

This feature was not provided. The mobile application could not be called from another application, for example, when a hyperlink was placed in email.Added new features for 1C:Enterprise mobile version. Now you can register specific URLs. When you click them in another application, the mobile application opens automatically.
System requirements.
1C:Enterprise now supports Microsoft Windows Server 2019 (x86-64).1C:Enterprise did not support Microsoft Windows Server 2019 (x86-64).The list of supported operating systems is extended.
Client application form.
In the client application form, you can now handle the following events of the form field extension for the planner field:
  • Selecting an empty planner area to create a planner item.
  • Selecting planner items.
  • Dragging or changing borders of one or more planner items.
  • Copying one or more planner items.

Implemented the event handler of the form field extension of the client application for the CheckDraggingInside planner field.

For the event handler of the form field extension of the client application for the BeforeCreate planner field, the following parameters become return parameters: Start, End, DimensionsValues, and Text.

Dragging items within the planner field and changing the size of planner field items were not available.New features for interactive editing of the planner field.
Error handling.
Implemented a new error category: a database copy error. Errors that occur while using database copies fall into this category.

Implemented value of the ErrorCategory.DatabaseCopyError system enumeration.

This change is not implemented in 8.3.17 compatibility mode.

+

Errors that occurred while using database copies fell into the category of external data source errors.Improved error categorization.
Spreadsheet documents.
Web client.
Improved update of a spreadsheet document displayed in the web client with scale greater than 100% when editing text in cells. Once you finish editing text in a cell, the server is no longer called if the entered text fits the cell.Once you finished editing text in a cell of a spreadsheet document displayed in the web client with scale greater than 100%, the server was called if the entered text fitted the cell.Eliminated unexpected system behavior.
Internet-enabled functionality.
New property: NetworkAdapterInformation.IPAddress. The property contains a network adapter IP address that describes the NetworkAdapterInformation object.This feature was not provided.Expanded the network adapter information provided by 1C:Enterprise.
Full-text search.
Error handling.
An attempt to search by a word for which a lot of matches are found generates an error. Reduced the full-text search index size for very large infobases.

New system enumeration value: ErrorsCategories.FullTextSearchError.

We recommend that you clear the full-text search index and build it again if the full-text search index size exceeds 50 Gb.

When the previous platform version with the full-text search index built by platform version 8.3.19 is started, the index will be cleared and built again.

An attempt to search by a word for which a lot of matches were found could lead to unpredictable results.Improved stability and fault tolerance of full-text search.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
  • Postgres Pro 1C 12.4.1,
  • Postgres Pro Standard 12.4.1,
  • Postgres Pro Enterprise 12.4.1.
The following Postgres Pro DBMS versions were not supported:
  • Postgres Pro 1C 12.4.1,
  • Postgres Pro Standard 12.4.1,
  • Postgres Pro Enterprise 12.4.1.
Extended list of supported DBMS.
Mobile application builder.
The version of Mobile Application Builder now matches the number of the 1C:Enterprise mobile version the builder is supplied with. Thus, Mobile Application Builder that comes with the mobile version 8.3.18 has the version number 8.3.18.*. The fourth digit of the builder version number indicates the builder build number and has nothing to do with the fourth digit of the number of the mobile version of 1C:Enterprise. +Mobile Application Builder had the numbering that did not match the number of the mobile version of 1C:Enterprise.The numbering of Mobile Application Builder is now more transparent and associated with its mobile version of 1C:Enterprise.
Mobile application builder.
Mobile Application Builder does not support mobile versions of 1C:Enterprise whose number (first three digits) is greater than the builder version number (first three digits). Mobile Application Builder 8.3.18 will not load the mobile version 8.3.19 and later.

The builder still allows you to upload the previous mobile versions of 1C:Enterprise (8.3.17 and later).

In Mobile Application Builder, you can now block loading of configurations whose format is not supported by the current builder version.

Mobile Application Builder did not have any restrictions on loading mobile configurations and mobile versions of 1C:Enterprise. This could lead to hard-to-diagnose issues when configurations or mobile versions not supported by the builder were uploaded to the builder.Mobile Application Builder no longer supports loading of objects that it does not support. +
Linux.
System requirements.
The following Linux distributions are now supported:
  • ALT Education 9.
  • ALT Workstation 9.
  • ALT Workstation K 9.
  • ALT Server 9.

The following Linux distributions are no longer supported:

  • ALT Linux 6.0 SPT.
  • ALT Workstation 7.
  • ALT Server 7. +
The following Linux distributions were supported:
  • ALT Linux 6.0 SPT.
  • ALT Workstation 7.
  • ALT Server 7.
The list of supported Linux distributions is brought up-to-date.
Full-text search.
Changed the algorithm to perform the standard type of the Data global search. As a result, the search returns a more relevant result in less time.

For the algorithm description, see the documentation.

When performing the standard type of the Data global search, the result might not match the search string well. +Improved relevance and performance of the standard type of the Data global search.
Licensing system.
For system distribution packages designed for Windows XP, HASP Device Driver version 7.63 is now included.

The outdated haspds_windows.dll and hdinst_windows.dll files are removed from the distribution package. +

For system distribution packages designed for Windows XP, HASP Device Driver version 7.92 that did not run on this operating system was included.Windows XP users can install HASP Device Driver directly from the current 1C:Enterprise distribution package.
1C:Enterprise script.
Improved performance of the Insert() and Get() methods of the Map object for cases when a reference to an infobase object is used as a map key.The Insert() and Get() methods of the Map object showed poor performance when a reference to an infobase object was used as a map key. +Eliminated unexpected system behavior.
Mobile device-specific features.
Upgraged the in-app purchases mechanism. The purchases mechanism is based on the Google Play Billing 3 library.

New parameters for the InAppPurchases.UpdatePurchaseInformation() method: PurchaseType and AutoConfirmation. New parameter for the InAppPurchases.BeginPurchasing() and InAppPurchases.PurchaseAsync() methods: AutoConfirmation.

New methods for the InAppPurchasesManager object: PurchasesConfirmationSupported(), CheckConfirmation(), and ConfirmPurchase().

To build a mobile application that supports the new in-app purchases mechanism, use Mobile Application Builder version 8.3.18 or later.

We recommend that you refactor the application to switch to the new in-app purchases interface.

The old purchases mechanism is only supported in version 8.2.17 and earlier compatibility mode.

The in-app purchases mechanism was based on Google Play through Android Interface Definition Languages.Upgrade: the mobile application monetization mechanism is now supported, which will be required when publishing in Google Play, starting in August 2021.
Integration service.
You can now get the state of connection to an external integration service. You can now receive and delete messages that are in the integration service channel.

New methods for the manager of the external integration service channel: GetState(), SelectMessages(), and DeleteMessages().

These features were not provided.

The message when sent could only be out of date. If an error occurred while sending a message, this message blocked the channel.

New operations with messages in the channel of the external integration service.
Mobile application builder.
Mobile platform.
Mobile client.
In Mobile Application Builder, you can now build mobile applications for iOS if the build uses a Mac based on the Apple M1 processor and uses macOS Big Sur.Mobile Application Builder did not support running a build of mobile applications for iOS when the build used a Mac based on the Apple M1 processor and used macOS Big Sur.Mobile Application Builder now supports modern Apple computers and operating systems.
Client application.
Client application installation.
Administration tools.
On Linux, it is now possible to update the distribution package without additional configuration of the default.vrd file (via the distr directory of a specific version directory).

For Linux and Windows, installation package files that contain all client applications are implemented.

Updating the distribution package without additional configuration of the default.vrd file (via the distr directory of a specific version directory) was supported only by client applications for macOS and Windows.It is now easier to configure distribution of client application distribution packages when updating the 1C:Enterprise version on servers running Linux.
Web client.
The web client now supports URLs:
  • Global context event handler URLNavigationProcessing.
  • Global context method GetExternalURL().
  • Global context property StartupURL. This property contains the URL that started the client application. +
These features were not available in the web client.Web client URL features are now in line with the rest of the client applications.
Mobile application builder.
It is now easier to load configurations into Mobile Application Builder. The builder automatically determines which group to place the configuration to be loaded in.

You can now view properties of the used configuration directly from the built mobile application card.

For a configuration loaded into the builder, it is now possible to get a list of applications that include this configuration.

To load a new mobile configuration version, it was necessary to manually determine which group to load the configuration into, which was not very easy with a large list of used configurations.

Mobile Application Builder did not provide an easy way to get a list of applications that used any configuration. It also did not allow you to quickly view the configuration properties in the built mobile application card.

Managing mobile configurations in Mobile Application Builder is now more convenient.
Mobile client.
The mobile client signature on the server is verified in accordance with the parameter value in the infobase settings. The parameter in the infobase settings is called Mobile client signature verification.

New global context methods to access the parameter value: GetMobileClientSignatureVerificationMethod()/SetMobileClientSignatureVerificationMethod().

The mobile client signature on the server was always verified, regardless of the parameter value in the infobase settings. The parameter in the infobase settings was called Mobile client signature verification on database configuration update.You can now disable useless troubleshooting if the application is not used with the mobile client and the mobile client does not require configuration signature verification.
System requirements.
Mobile platform.
Mobile client.
Mobile applications built using mobile version 8.3.18.71 will meet the requirements of Google Play for new applications. The target SDK version is 30.

To upload a mobile application to Google Play, build a mobile application using mobile version 8.3.18.71 or later. +

Mobile applications built using mobile versions that are older than 8.3.18.71 could not be uploaded to Google Play after August 1, 2021.1C:Enterprise mobile version meets the requirements of Google Play.
Mobile platform.
Mobile client.
New mobile version functionality: Access to all data. If a configuration has this functionality enabled, an Android mobile application that includes this configuration will have permission to access an arbitrary place (within the global restrictions of the operating system) in the file system of a mobile device.Access to an arbitrary place in the file system of an Android device did not require any permission to be specified.Improved compliance with the requirements set by Google for Android mobile applications.
Client application installation.
Administration tools.
Linux.
If 1C:Enterprise server is updated to version 8.3.20 or later and the client application update is set up via the server (any method), thin client 8.3.18 and 8.3.19 managed by Linux can be updated to version 8.3.20. To update the application, you can use not only distribution packages in .deb and .rpm formats but also in .run format (implemented in version 8.3.20).The client application managed by Linux could be updated only using distribution packages in .deb and .rpm formats. After update to version 8.3.20, the client application could not be automatically updated to the current version.Migration to version 8.3.20 is now as easy as migration to previous versions despite the changed file format of the distribution package.
macOS.
System requirements.
macOS Big Sur (version 11) is now supported.

Under macOS Big Sur the SystemInformation.Processor property always contains the x86_64 value.

1C:Enterprise application did not work under macOS Big Sur (version 11).Extended list of supported macOS versions.
Analytics system.
To execute data queries, the analytics system uses a session pool similar to a pool processing HTTP service queries.

New session type: Analytics system query.

To set up the pool, use the analytics element of the default.vrd file. 1C:Designer infobase publication interface does not support editing pool settings.

To execute data queries, the analytics system used background jobs.Accelerated the analytics system queries to infobase data due to faster session initialization.
Processing PDF documents.
You can now convert a PDF document to grayscale.

New methods for the PDFWriter object: ConvertToGrayScale() and ConvertToGrayScaleAsync().

This feature was not provided.Advanced PDF document features.
Database copies.
Improved performance of queries executed in a database copy.Execution of queries in a database copy took more time.Improved performance of queries executed in a database copy.
Data composition system.
External data sources.
Fields of external data sources of the non-reference type received using dot syntax from another field become available in the source of available data composition settings. That means that such fields can be used in the data composition settings.Fields of external data sources of the non-reference type received using dot syntax from another field were not available in the source of available data composition settings. That meant that such fields could not be used in the data composition settings.Eliminated unexpected system behavior.
DBMS operations.
PostgreSQL version 10.18 (x86-64) is supported.This version of PostgreSQL was not supported.Extended list of supported PostgreSQL versions.
DBMS operations.
PostgreSQL version 11.13 (x86-64) is supported.This version of PostgreSQL was not supported.Extended list of supported PostgreSQL versions.
DBMS operations.
PostgreSQL version 12.8 (x86-64) is supported.This version of PostgreSQL was not supported.Extended list of supported PostgreSQL versions.
DBMS operations.
PostgreSQL version 13.4 (x86-64) is supported.This version of PostgreSQL was not supported.Extended list of supported PostgreSQL versions.
DBMS operations.
PostgreSQL version 14.0 (x86-64) is supported.This version of PostgreSQL was not supported.Extended list of supported PostgreSQL versions.
Analytics system.
Standard functions.
 +

New features for the standard "Analytics system management" data processor:

  • Support of virtual table parameters in queries to additional sources.
  • Operations with additional data sources.

+

The standard "Analytics system management" data processor did not support virtual table parameters in queries to additional sources. For the list of additional sources, only additional source registration was available in the data processor.The standard processor features are compliant with 1C:Enterprise features.

+

System requirements.
Minimum system requirements are specified for platform components:
  • CD reader is excluded from the list of system requirements.
  • Installation requires from 350 MB to 1 GB of disk space (depending on the application to be installed).
  • Chromium-gost - version 64 or later.
  • Google Chrome - version 64 or later.

The user can now read in the documentation about recommended hardware to select an optimal hardware configuration.

Minimum system requirements for platform components were as follows:
  • CD reader support was required.
  • Installation required from 250 MB to 800 MB of disk space (depending on the application to be installed).
  • Chromium-gost - version 49 or later.
  • Google Chrome - version 49 or later.
Specified some system requirements.

+

System requirements.
DBMS operations.
The system now supports Postgres Pro DBMS of the following versions (only for x86-64):
  • Postgres Pro 1C 12.9.1
  • Postgres Pro 1C 13.5.1
  • Postgres Pro 1C 14.1.1
  • Postgres Pro Standard 12.9.1
  • Postgres Pro Standard 13.5.1
  • Postgres Pro Standard 14.1.1
  • Postgres Pro Enterprise 12.9.1
  • Postgres Pro Enterprise 13.5.1
  • Postgres Pro Enterprise 14.1.1
These DBMS versions were not supported.Extended list of supported DBMS.
DBMS operations.
System requirements.
PostgreSQL 15 is now supported.This PostgreSQL DBMS version was not supported.Extended list of supported PostgreSQL DBMS versions.
Internet-enabled functionality.
1C:Enterprise now supports the TLS 1.3 protocol. When using the TLS 1.3 protocol, client certificates are not supported.

New parameters for the conf.cfg configuration file: ForceTLS1_1 and ForceTLS1_2. These parameters allow you to specify the maximum version of the used TLS protocol.

New commands for the client application startup command line: /HttpsForceTLS1_1 and /HttpsForceTLS1_2. These commands allow you to specify the maximum used version of the TLS protocol when accessing the web server over HTTPS.

Previously, 1C:Enterprise did not support the TLS 1.3 protocol.Increased security of the connection established by the client application when running over the Internet.

Table of contents

Transition from the previous version to the version 8.3.18

Table of contents

Version 8.3.17

Version 8.3.17 includes known bug fixes and functionality modifications. +

Thick client and Designer for macOS are out of beta.

Data Accelerator and database copy features now require a CORP license.

The feature testing license now does not provide access to the Data Accelerator and database copy features.

Added a beta testing server license for 1C:Analytics. It provides access to the 1C:Analytics, Data Accelerator, and database copy features.

New feature: license to start 1C:Analytics client. The number of concurrent sessions of 1C:Analytics client are determined by the license value. The license to start 1C:Analytics client can be PROF or CORP.

The license to start 1C:Analytics client is installed on a computer with 1C:Enterprise server cluster and allows you to:

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.16 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.15 was available.Configurations developed using 1C:Enterprise platform version 8.3.16 or earlier can now run on version 8.3.17 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.17 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.16 after the migration to version 8.3.17, even if you disable the compatibility mode (simply enable it again).
Data display.
New pictures were added to the picture library:
  • Zoom.
  • Parameters.
  • Information.
  • FunctionMenuCommand.
  • Favorites.
  • Settings.
  • Message.
  • GroupConversation.
  • CollaborationSystemUser.
  • SearchForData..
  • GotoExternalNavigationLink.
  • Calendar. CalendarInputField picture is used in version 8.3.16 compatibility mode.
  • Calculator. CalculatorInputField picture is used in version 8.3.16 compatibility mode.
  • Help. FormHelp picture is used in version 8.3.16 compatibility mode.
  • CollaborationSystemIntegrationUser,
  • OpenFromMainServer,
  • OpenFromStandaloneServer.

Conversations image was updated.

The listed pictures were not available in the picture library.The picture library is upgraded.
Error handling.
The following features related to the application running error processing were implemented:
  • Processing of all non-trapped errors that occur during the application running before displaying errors to the user.
  • ErrorDisplayProcessing application module handler was implemented.
  • Declarative configuring of error message texts is now available.
  • You can now generate and send error reports to technical support team (inter alia in default mode). ErrorReport object was implemented.
  • An 'error category' concept is supported, which enables you to group errors. ErrorInfo.IsErrorOfCategory() method is available.
  • The standard window to display errors was modified.

ErrorProcessing global context property was implemented. +Error Processing Settings Management standard function is now available, which allows you to configure error texts. +BriefErrorDescription(), DetailErrorDescription(), and ShowErrorInfo() global context methods are deprecated. It is recommended to use the similar methods of the ErrorProcessing object. +When running Linux, the libunwind library is used to get the application stack when an error occurs.

These features were not provided. +Local processing of recoverable errors was available only.You can now make error texts easier to understand by end users. +Error processing in 1C:Enterprise language was improved.
Server clusters.
Client application.
When in the client/server mode, you can by default delete temporary files created using GetTemporaryFileName() method on the side of the PC(s) running the server cluster in the following scenarios:
  • 20 minutes after the end of a session when a temporary file is created.
  • 20 minutes after the end of a server call when a temporary file was created. This feature is not available in the 8.3.16 and earlier compatibility mode.

Temporary files are deleted as soon as you start 1C:Enterprise processes (client applications, server cluster processes) without delaying the start.

Temporary files were only deleted when the 1C:Enterprise processes were started. The system startup speed depended on the number of temporary files to be deleted.1C:Enterprise processes performance is improved, if there is a large number of temporary files generated by 1C:Enterprise itself.

The risk of running out of space on the hard drivers where the temporary file directories are located is mitigated during prolonged operation without restarting and inaccurate application handling of the temporary files being created.

The number of simultaneously existing temporary files with names that were obtained using GetTemporaryFileName() method was reduced.

Collaboration system.
Integration with external (with respect to the collaboration system) instant messaging systems was implemented for the collaboration system. Interaction with the following systems is now supported: Telegram, VKontakte.

CollaborationSystemIntegration object is supported. CreateIntegration(), GetIntegration(), GetIntegrations(), GetExternalSystemTypes() and GetExternalSystemDescription() methods were implemented for CollaborationSystemManager object.

CollaborationSystemUser.ExternalSystemType, CollaborationSystemUser.ExternalSystemUserID, CollaborationSystemConversion.Integration and CollaborationSystemConversationFilter.Integration properties were implemented.

This feature was not provided.Expanded collaboration system capabilities.
Configuration extensions.
You can now borrow event subscriptions and create your own subscriptions in the extension.This feature was not provided.Extended configuration extension options.
Client application.
Data display.
System requirements.
You can save a spreadsheet document in Microsoft Excel 97 format in a client application running macOS. In Linux, to save in Microsoft Excel 97, use libgsf-v8 library included in 1C:Enterprise platform distribution package. Thus, libgsf-1 and libglib-2.0 libraries are no longer required.

You cannot save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS.

You could save a spreadsheet document in Microsoft Excel 97 format in Linux only.

Nominally, you were able to save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS. However, in practice this feature was unavailable.

Users of client applications running macOS can now save spreadsheet documents in Microsoft Excel 97 format.
Development tools.
A technical specialist mode is implemented for a managed client application. The following features are available in this mode for managed forms:
  • You are able to retrieve the full form name displayed in this window using Information for Technical Specialist command in the form header context menu and form menu.
  • You can open the current configuration object in Designer using Open in Designer command in the form header context menu and form menu. This feature is only available, if the client application is running in debug mode.
This feature was not provided.

It was difficult to determine which form is currently used in the client application.

Technical specialists operations as part of application development or deployment process were made easier.
Common objects.
You now can identify IP-address of a PC, where an infobase user session was started. IP-address cannot be determined in every instance and in every mode of operation.

ClientIPAddress property was implemented for AdministrationSession and InfobaseSession objects.

Now, IP-address of a client application can be displayed in the cluster console and standard server management processor.

ISessionInfo.getClientIPAddress() property is now available in the administration server interface in Java language.

Client-ip field is now available in the command-line utility (rac) of a server cluster. It displays values returned by session info command..

SessionNumber and ClientIPAddress parameters are now available for the onStartSession() method of external session management Web-service. New features are only available, if wsver is assigned 3.

This feature was not provided.You now can identify IP-address of a PC, where an infobase user session was started.
Analytics system.
1C:Enterprise is now integrated with 1C:Analytics (analytics system).

In the publishing settings on the Web server, you can enable analytics system publication.

In the Service and Settings menu, Analytics System command is now supported, thus allowing you to open a tab with analytics system in the web browser for the current user.

Standard Analytics System Management function is supported to integrate it with the infobase.

So far as global context is concerned, AnalyticsSystem property is available. AnalyticsSystemClient access rights are supported.

1C:Analytics is not included in distribution package. Information on this functionality is published separately. +

This feature was not provided.1C:Enterprise is now integrated with 1C:Analytics (analytics system).
Data composition system.
You can pass temporary tables manager to data composition system. In the data composition system, you can use tables that do not exist in the infobase similarly with temporary tables in the query language.

The TempTablesManager parameter is now available for the DataCompositionProcessor.Initialize() method.

This feature was not provided. You were able to use temporary tables in the data composition system only as part of a batch query.Now, you can use pre-defined temporary tables, when a query is executed by the data composition processor.
Spreadsheet documents.
Charts.
Now, you can manage the way an image selection box is displayed in a spreadsheet document in a client application form. +To expand the form field boundaries, DrawingsSelectionView property is supported for spreadsheet fields.

This upgrade is ignored in 8.3.13 version compatibility mode. +

This feature was not provided.

When you selected a chart in a spreadsheet document available in the client application form, the said chart was always highlighted.

Now, it is much more easier to use charts in a spreadsheet document available in the form.
Data display.
Сlient application form.
Nested dimension items can be created and text in background bands displayed in the Planner.

The PlannerDimensionItem object now supports Items, Parent, and ShowItemsAreaOnlyForSubordinateItems properties.

The PlannerDimensionItemsCollection.Find() method now supports IncludeSubordinates parameter.

To expand the form field, planner filed supports the following:

  • CollapseDimensionItem(), ExpandDimensionItem(), and DimensionItemExpanded() methods.
  • BeforeExpandDimensionItem and BeforeCollapseDimensionItem events.

+Text parameter is available for Add() and Insert() methods (PlannerDimensionCollection and PlannerDimensionItemCollection objects). When you use this parameter, it is recommended to specify its value to avoid server calls getting presentations.

These features were not provided.Now, you can implement a group of planner dimension items similarly to a group of spreadsheet or hierarchical catalog lines.
DBMS operations.
System requirements.
The following Oracle Database DBMS versions are supported now:
  • 12.2
  • 18c
  • 19c
These Oracle Database DBMS versions were not supported.Extended list of supported Oracle Database DBMS versions.
Integration service.
Integration service creating feature was implemented. Integration services allow to coordinate with the "External integration service" product. +The IntegrationServices property of 1C:Enterprise language was implemented. +Managing integration services was implemented in standard functions. +"External Integration Service" is not included in distribution package. Information on this functionality is published separately. +To use integration services, a license to test dedicated functionality is required. The integration services will not be available without a license to test the dedicated functionality. +This feature was not provided. +Interaction with "External Integration Service” was implemented.
Web client.
Language support with spelling from right to left is implemented for the web client. This mode is supported automatically in the entire client application interface, with the exception of the following form elements: planner, chart, Gantt chart, dendrogram, graphical schema field and graphical schema field. The requirement to change the interface is determined by the interface language or configuration language. The web client now supports Arabic formats for numbers and dates.

When calculating the arrangement of form elements and other interface items, the default font is Almarai.

The web client supports using specialized Arabic characters for writing arithmetic expressions. In such cases, the expressions are calculated correctly.

The web client did not support using of languages with right-to-left spelling.It has become possible to use 1C: Enterprise (using a web client) in countries where the national language uses right-to-left spelling.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Web client.
File operations.
As soon as you open an external report or data processor file on a web client (without a file system extension installed), there is no need to reopen the selected file after positive feedback to security warning.

In a file opening dialog box on a web client, now you can select a filter to search files you need to open (if it is defined, when you open a dialog box).

As soon as you opened an external report or data processor file on a web client (without a file system extension installed), you needed to reopen the selected file after positive feedback to security warning.

In a file opening dialog box on a web client, there was no option to define a filter to search files.

Now, you can open an external report or data processor on a web-client (without a file system extension installed) in a easier and user-friendly way.

Moreover, it's much more easier to open other files on a web client now.

Data display.
Some platform images (including part of image library) now have different appearance (they were redrawn) and are now implemented in SVG format.

In the Taxi interface windows appearance was modified. They are now generated by ShowUserNotification() and State() global context methods.

Some platform images (including part of image library) had different appearance, and they were implemented in PNG format.

Appearance of windows generated in Taxi interface using ShowUserNotification() and State() global context methods was different.

Visual perception of 1C:Enterprise interface was improved.
Error handling.
As soon as you open a dialog box with information for technical support team, the entire text available in the input field is selected by default.When you opened a dialog box with information for technical support team, text available in the input field was not selected.Now, you can copy information for technical support team (if necessary) easier and without delay.
Global search.
Client application.
Web client.
The following global search commands are available:
  • Help: you can open Help section in the client application for the current context.
  • Help Content: you can open content of client application help section.

+Search Everywhere context menu command is available, only if a pointer is set on a word or you selected a text block. If no text block is selected, and a pointer is on a word, search is made using the said word or URL (whenever a pointer is placed on URL).

In Search Everywhere command presentation in the menu a text block is added which will be searched, whenever you use this command.

Whenever you use Safari browser on a web client, click the right mouse button in the input field, formated or text document to select the entire word with a pointer placed thereon (without further analysis of that word).

Whenever you use a thin, thick or web client (other than Mozilla Firefox and Safari browsers), click the right mouse button in the input field to place a pointer in a position where the button was clicked.

Search Everywhere context menu command was available, only if there was a selected text block in the current form element. Search was made by the text block so selected.

No text block so searched was added to Search Everywhere command presentation in the menu.

Global search usage was improved.
Web client.
Spreadsheet documents.
The display of a spreadsheet document containing patterns in cells was optimized when using a web client in case of a slow connection. When saving a spreadsheet document containing patterns in cells in HTML format, the size of resulting HTML document was reduced. +Displaying a spreadsheet document containing patterns in cells took longer when using a web client in case of a slow connection.Eliminated unexpected system behavior.
Full-text search.
Standard functions.
So far as standard full-text search management function is concerned, you can check the current full-text search index for accuracy.

Before you clear the current full-text search index, a warning is displayed notifying that you can abandon this procedure. +

So far as standard full-text search management function was concerned, the current full-text search index was unavailable for accuracy verification.

The current full-text search index was cleared with a prior warning on an unconditional basis.

Capabilities supported by the standard full-text search management function were expanded.

Now, it is more difficult to clear full-text search index.

Web client.
The browser extension installation process was simplified (for Google Chrome and Mozilla Firefox browsers). The said extension is required to use file system, cryptography and add-in extensions. As soon as you install an extension for Google Chrome web browser, there is no need to restart your web client any more.The browser extension installation process was complicated (for Google Chrome and Mozilla Firefox browsers). The said extension was required to use file system, cryptography and add-in extensions. As soon as you installed an extension for Google Chrome web browser, you needed to restart your web client.Now, the web browser extension installation process is much more easier and user-friendly.
Collaboration system.
The collaboration system interface was modified as follows:
  • Now, you can change the size of the message input field in the context conversation.
  • User pictures can be displayed in the dialog box where you can create conversations and users added to non-context conversations.
  • Any user participating in a non-context conversation can be deleted by any other user.
  • Message recipients can be defined for a non-context conversation.
  • So far as a non-context conversation is concerned, a list of recipients is generated similarly to that applicable to context conversation (including but not limited to, by way of calling all data processors). No Notification option is unavailable in the user list.
  • So far as messages sent to several users are concerned, you can press either Reply or Reply All button (displayed as icons).
  • Moreover, you can reply to your own message. As such, a list of notified users specifies those defined for the original message.
  • If so far as a non-context message is concerned the current user is unavailable in the list of users, no notice is sent thereto whenever the said message is received.
  • You can view attachments in the messages you create.
Previously, the collaboration system interface was different.Now, it is much more easier to use the collaboration system.
Standard functions.
The button for accepting changes is always available, and not only after changing the parameters in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself is called OK.The button for accepting the changes was only available after changing any parameter in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself was called Set.The interface of the parameter setting dialog box has been brought to the standard accepted in the platform.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Сlient application form.
Removal of rows from tables displayed in the client application form was optimized.Previously, removal of rows from tables displayed in the client application form took more time.Client application operation when rows are removed from the form table was improved.
Event log.
You can index event log files. Indexing is performed in the background. Indexes are stored in .lgx files in 1Cv8Log directory. Algorithms for sequential reading of event log files were optimized.

No additional settings are required to enable indexing. Due to indexing, filtering of event log entries by indexed fields was significantly accelerated.

When another infobase event log file is opened in Designer, indexing of this file is performed in the background and the index file is deleted after the work with the event log being viewed is finished.

Separate Log Storage by Periods is set to Week for a new infobase. It is recommended to set separation for existing infobases, so that the size of a single log file is max 100 MB.

Event logs created in the 1C:Enterprise of version 8.0 and 8.1 are no longer supported.

This feature was not provided.

No event log files indexing was performed. Filtering of entries in event log files took a very long time, so far as large event log files were concerned.

Operations with event logs were accelerated.
Access rights.
Server clusters.
When using the client/server mode, starting of the first session is accelerated to access the infobase, the configuration of which contains a large number of roles. +When using the client/server mode, starting of the first session to access the infobase, the configuration of which contained a large number of roles, took more time.The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased. +
Server clusters.
When using the client/server mode, starting of the first session to access the infobase is accelerated. Acceleration is especially noticeable for configurations containing a large amount of metadata.When using the client/server mode, starting of the first session to access the infobase took more time.The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased.
Common objects.
Accelerated solution of some systems of linear algebraic equations is enabled.

AllowGraphReduction parameter is implemented for SolvingLinearEquationSystems.SolveLinearEquationSystems() method, which allows to control the calculation algorithm. SolvingLinearEquationSystems.GetGraphDepth() method is implemented to allow making the decision on AllowGraphReduction parameter value.

1C:Enterprise showed insufficient search speed for solutions of some linear algebraic equations systems.A finer customization of behavior of a tool designed to solve linear algebraic equations systems was implemented.
Queries.
Comparison of composite type with non-composite type was improved, provided that the latter can be NULL and a query includes temporary tables.

The following operations were optimized:

  • A = B comparison, where A is composite type and B is simple type which can be NULL.
  • ISNULL (A,B) = C comparison, where A is simple type and can be NULL, while C is composite type.
  • Comparison of Expression1 IN (SELECT ...) and Expression1 IN (List of Values), where Expression1 is a field with references to two or more tables. However, you need to procure that a subquery selection list or list of values has references to various tables and no Undefined values are available therein.

Optimization is feasible, whenever it has no impact on the query results. Optimization can contribute to query plan improvement and reduction of time required to compile a query.

Comparison of composite type with non-composite type, whenever the latter can be NULL and query had temporary tables, resulted in generation of complex queries which eventually can trigger runtime errors and generate non-optimal query plans.In some scenarios, query performance was improved.
Queries.
DBMS operations.
Server clusters.
If comparison with an empty link returned as a parameter is made in a query, DBMS receives a query, where a parameter is replaced with a constant. Optimization is feasible, if a server cluster supports such DBMS as IBM DB2, Microsoft SQL Server or Oracle Database.If comparison with an empty link returned as a parameter was made in a query, no replacement of a parameter with a constant was effected. DBMS can select a more efficient query execution plan, whenever comparison with empty links returned as parameters is made in a query.
DBMS operations.
So far as use of infobase in file mode is concerned, execution of a query with several B conditions which use indexes was largely improved.

However, in some scenarios insignificantly decelerated execution of such queries is possible.

So far as use of infobase in file mode is concerned, execution of a query with several B conditions which used indexes was non-optimal.Execution of some queries in infobase file mode was accelerated.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Data composition system.
When reading report, dynamic lists and conditional appearance settings, missing style elements do not cause an error, but are replaced with default values of the corresponding type.When reading report, dynamic lists and conditional appearance settings, missing style elements caused an error and no application of such settings was possible.If a style element is used as the appearance parameter value in any report, dynamic list, form conditional appearance settings, the entire settings object will not be lost and the remaining settings will be applied if this element is unavailable for reading as a result of deleting/renaming or applying settings on the previous platform version. Appearance options containing invalid values will also be applied, but using default values.
Web client.
Web client reliability is improved.Web client operation was characterized by lower reliability.Web client reliability is improved.
Development tools.
If halt on error during debugging is enabled, the error text is displayed both in the dialog box and in the message window. This also allows you to go to exception from the message window. +This feature was not provided.

An error message was only displayed in a dialog box with error details.

It is now much more easier to use debugger when halt on error is enabled.
Development tools.
The following control features were implemented when a report on the configuration repository versions is generated:
  • Managing a date range used to generate a report.
  • Including and excluding tagged versions from the report.
  • Displaying comments in the report starting with (//).
  • Specifying a configuration version to display related repository changes.
  • Managing a repository report format.

DateBegin, DateEnd, DoNotIncludeVersionsWithLabel, IncludeOnlyVersionsWithLabel, IncludeCommentLineWithDoubleSlash, ConfigurationVersion and ReportFormat parameters were implemented for ConfigurationRepositoryReport Designer batch run command.

These features were not provided.A list of features designed to manage repository reports in Designer batch run mode was expanded.
Collaboration system.
Linux.
After installing 1C:Enterprise - Notifications and Startup application (in Linux), a shortcut is created on the desktop to launch this application. The shortcut refers to the Finance subcategory of the Office category.In Linux, you were able to start 1C:Enterprise - Notifications and Startup application from ~/bin/1cecla directory only.Now, it became easier for Linux users to find and run 1C:Enterprise - Notifications and Startup application.
Web client.
File operations.
Whenever you use BeginPutFileToServer() and BeginPutFilesToServer() methods on the web client (without a file system extension), PutFilesDialogParameters is used, and in the file opening dialog box you can now select one of the filters defined when you created PutFilesDialogParameters object.

When you create PutFilesDialogParameters object, you can now define filter by default to be used when a file selection dialog box is opened.

Whenever you used BeginPutFileToServer() and BeginPutFilesToServer() methods on the web client (without a file system extension), PutFilesDialogParameters was used, and in the file opening dialog box you were unable to select a filter in the file opening dialog box.If there is now file system extension on the web client, it's easier to select files for further processing by application.
Cryptography support.
Values of properties starting from OID prefix which are based on Subject and Publisher properties of CryptoCertificate have the maximum length of 2,048 bytes.Values of properties starting from OID prefix which were based on Subject and Publisher properties of CryptoCertificate object had the maximum length of 128 bytes.Eliminated unexpected system behavior .

+

Global search.
GlobalSearchResultItem object cannot be created on the basis of the following standard global search kinds: GlobalStandardCommands and FunctionsForTechnicalSpecialist.You were able to create GlobalSearchResultItem object on the basis of the following standard global search kinds: GlobalStandardCommands and FunctionsforTechnicalSpecialist, so that eventually incorrect data upon global search result processing was returned.Eliminated unexpected system behavior.
Dynamic lists.
If the dynamic list settings form contains changed settings, then when attempting to close this form, the user will be warned about the changed settings and will be prompted to save the changed settings.

The UserSettingsModified and SettingsModified properties are implemented to expand the client application form for the settings composer. The standard processing of the settings composer form analyzes the flag of settings modification and prompts to save the settings, if necessary.

If the dynamic list settings form contains changed settings, when attempting to close this form, the form was closed without any warnings.Likelihood of losing work results by changing dynamic list settings was reduced.
XML and XDTO support.
When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option is exported in the same way as it is for properties with an "Attribute" presentation option.

This upgrade is ignored in 8.3.13 version compatibility mode.

When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option was not exported.Eliminated unexpected system behavior.
Spreadsheet documents.
Whenever you convert a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contain tab characters or text starting with whitespace can now be created easier.Whenever you converted a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contained tab characters or text starting with whitespace were created in a way, when the resulting document was visually different from the original one.Now you have less visual differences between the original spreadsheet document displayed in 1C:Enterprise and that created by way of conversion thereof into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format.
Queries.
If the temporary table is generated based on the table of values, a runtime error will be generated if a column with an unspecified type is present in the table of values and this column is included in the temporary table. An error will also occur if a non-typed column is involved in any expression (for example, SELECT or ISNULL).

This upgrade is ignored in 8.3.13 version compatibility mode.

If a temporary table is formed based on a table of values where a column with an unspecified type is present and this column is included in a temporary table, no runtime errors were generated, but the query result could be incorrect.Eliminated unexpected system behavior.
Collaboration system.
Web client.
Screen translation in the collaboration system running on a web client:

+

  • Google Chrome browser:

+

  • Mozilla Firefox browser:

    • +

Screen translation in the collaboration system running on a web client:
  • Google Chrome browser:
  • Mozilla Firefox browser:
The screen translation tool is improved, so far as the collaboration system runs on the web client.
Administration tools.
In Version 8.3.10 and later compatibility mode, GetDataBaseStorageStructure() function returns a table of values where the Indexes column contains short index names. At the same time, the names of indexes are displayed identically for any DBMS.In the Indexes column of the table of values returned by the GetDataBaseStorageStructure() method, long index names were indicated and the index names differed in different DBMSs.The names of indexes in the database schema are refined.
Configuration extensions.
Tooltips for the check box, which controls the behavior of the object property in the extension, have become more clear and better describing the essence of the check box status.Tooltips for the check box, which controls the behavior of the object property in the extension were poorly describing the check box status.Improved tooltips for the check box describing the behavior of an object property in the extension.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Сlient application form.
If no table is displayed in the form or there are no rows in the table or a row which is unavailable in the table is transferred to FormTable object method:
  • Use of FormTable.RowData(), TableForm.CheckRow() and FormTable.Unfolded() results in Undefined value.
  • Whenever you call FormTable.Unfold() and FormTable.Fold() methods, an exception is generated.

If no table is displayed in the form or no rows are available in the table, as soon as you call FormTable.ChangeRow() and FormTable.CopyRow() methods an exception is generated.

If no table is displayed in the form, whenever you call FormTable.AddRow(), FormTable.FinishRowEditing() and FormTable.Update() methods an exception is generated.

In 8.3.13 version compatibility mode behavior remained unchanged.

So far as thin and thick client applications are concerned:
  • If no table is displayed in the form:
  • If now rows are available in the table or a row is transferred which is unavailable therein:

Web client: +

  • If no table is displayed in the form:
  • If no rows are available in the table or a row is transferred which is unavailable therein:
  • If no rows are available in a table, as soon as FormTable.EditRow() and FormTable.CopyRow() methods are called, the said call is ignored.

+ +

Now, the system operates in a similar way both on the thin and thick client. Unexpected system behavior was eliminated.
Client application.
To describe OpenID Connect provider in default.vrd file, you can specify the fields to compare users of 1C:Enterprise and OpenID Connect provider infobases.This feature was not provided.

Users were always compared by e-mail and infobase user name.

Now, you can use OpenID Connect with a great number of providers, for instance, Microsoft Azure.
Data composition system.
If a data composition system expression in query language contains curly brackets, whenever this query is processed, the said characters cannot be deleted.

If there is no "}" character at the end of a data composition system expression in query language before that query is transmitted, an error is displayed.

In 8.3.16 version compatibility mode behavior remained unchanged.

If a data composition system expression in query language contained curly brackets, whenever this query was processed, the said characters were deleted from the query.

If there was no "}" character at the end of a data composition system expression in query language before that query was transmitted, no error was displayed.

Eliminated unexpected system behavior.
DBMS operations.
Queries.
When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator IN, which meets all of the following criteria, always returns a Boolean value:
  • Operator IN contains a subquery.
  • Operator IN subquery contains FIRST or ORDER BY operations.
  • The left side of IN operator and the subquery contain values of different types or the AnyReference type. +

It is recommended to analyze these queries and refactor them, if necessary.

This upgrade is ignored in 8.3.13 version compatibility mode.

When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator IN, which meets all of the following criteria, returned a Boolean or NULL value:
  • Operator IN contains a subquery.
  • Operator IN subquery contains FIRST or ORDER BY operations.
  • The left side of IN operator and the subquery contain values of different types or the AnyReference type.
Eliminated unexpected system behavior.
Data composition system.
If a query with merges is available in the data composition system query, whenever you use DataCompositionProcessor.Initialize() method with RestrictGettingFieldsByRefByViewRight set to True, View rights are applicable to all merging parts.

In 8.3.16 version compatibility mode behavior remained unchanged.

If a query with merges was available in the data composition system query, whenever you used DataCompositionProcessor.Initialize() method with RestrictGettingFieldsByRefByViewRight set to True, View rights were applicable to the initial merging part only.Eliminated unexpected system behavior.
Administration tools.
Now it takes less time to connect to the infobase upon mass connections. +When you start the server cluster, the working process caches the PublishDistributiveLocation* parameter values. If you change the PublishDistributiveLocation* parameters in the conf.cfg file, 1C:Enterprise will apply the new directory values in 10 seconds after you save the cong.cfg file.Previously, the system read the PublishDistributiveLocation* parameters from the conf.cfg file when it required the parameter values. It could result in significant delays upon mass connections to the infobase.Now it takes less time to connect to the infobase upon mass connections.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Some picture library items were renamed. Old names are saved for compatibility purposes, but they can refer to other pictures.
  • Calendar.
  • Calculator.
  • Magnifier.
  • SelectType.
  • Select.
  • Clear.
  • Help.
  • InputFieldCalendar.
  • InputFieldCalculator.
  • InputFieldOpen.
  • InputFieldSelectType.
  • InputFieldSelect.
  • InputFieldClear.
  • FormHelp.
Cluster service that stores dynamic information about cluster composition and status.
  • Cluster lock service.
  • Cluster status service.
Availability of 'all functions' phrase in the headers of Designer and client application configuration settings.
  • Show All Functions Command parameter in Designer starting setup dialog box.
  • All functions main menu item and header of the form that opens at the same time.
  • All Functions global search keyword.
  • Global search result display - All Functions.
  • Technical Specialist mode parameter in Designer start setup dialog box.
  • Functions for Technical Specialist main menu item and a similar header of the form that opens at the same time.
  • Functions for Technical Specialist global search keyword.
  • Global search result display - Functions for Technical Specialist. +
Names containing 'all functions' phrase. Old names are used for compatibility.
  • AllFunctionsMode access rights.
  • StandardGlobalSearchAppearance.AllFunctions system enumeration value.
  • Command line parameter to start DisplayAllFunctions client application.
  • TechicalSpecialistMode access rights.
  • StandardGlobalSearchAppearance.FunctionsForTechnicalSpecialist system enumeration value.
  • Command line parameter to start TechnicalSpecialistMode client application.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile client.
Images in SVG format can be displayed in the mobile client. No filters and effects are supported when you use images of this format.

ImageFormat.SVG system enumeration property was implemented.

This feature was not provided.1C:Enterprise mobile client now supports display of images in SVG format.
Add-ins.
Mobile platform.
Mobile client.
So far as add-ins are concerned which are supported by mobile devices running iOS, you can connect dynamic system libraries to add-ins.

The add-in technology documentation is updated. (read more)

This feature was not provided.

So far as add-ins running iOS were concerned, you were able to specify required subsystem components only.

Functionality to develop add-ins running iOS was added.
Mobile client.
Dynamic add-in setting is no longer supported by mobile client application build (including mobile clients which can run in a standalone mode) running Android. DynamicAddInInstallationSupported() method always returns False value on a mobile device (except mobile versions for developers)Whenever you were running Android, you were able to use dynamic add-in setting for mobile application application build (including mobile clients capable of running in a standalone mode).Due to update of security policy by Google, always make sure that add-ins available on a mobile client are included in a mobile application build.
Formatted documents.
External appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was changed. Functionality offered by a tool bar remained unchanged.

The formatting tool bar was made similar for mobile phones and tablets.

Previously, external appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was different. The formatting tool bar was dissimilar for mobile phones and tablets.The formatting tool bar for formatted and HTML-documents became easier and more user-friendly.
Mobile platform.
Mobile client.
Application usage statistics services can now be connected to the mobile application being built. The following statistics services are supported:
  • FirebaseAnalytics (Android and iOS).
  • AppMetrica (Android, iOS and Windows).
  • Appsee (Android and iOS).

+ApplicationUsageStatistics global context property was implemented.

This feature was not provided.Now, you can integrate mobile applications for a mobile version of 1C:Enterprise with various mobile application statistics services.
Mobile platform.
Mobile client.
User interface was enhanced (photos, audio and video recording). Now, you can review the result of action you performed and (if deemed necessary) repeat it.User interface was different (photos, audio and video recording). You were unable to preview and hear the results of your actions. Moreover, you were unable to repeat any of the actions.Now, it is much more easier to use tools supported by a mobile version to record audios and videos and make photos in a convenient way.
Mobile platform.
Development tools.
It has become possible to connect to the web server where the configuration of the mobile application is published using the HTTPS protocol in the developer's mobile platform. Opening the dialog box for configuring an HTTPS connection has been implemented in the infobase adding dialog box.This feature was not provided.Connecting a developer's mobile platform to a web server can be more secure (using the HTTPS protocol).

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Error handling.
The HTTP error registration service https://pult.1c.com/pult/platform/errors can be called when the application abnormally terminates. +To stop reports sending, disable abnormal terminations report sending in the ErrorProcessing object. +No services were used when the application terminated abnormally.When the application terminates abnormally, the information about the error is sent to 1C Company automatically. +
Error handling.
The standard texts of error messages are changed. The standard dialog box for sending an error report is changed. +To motivate the user to send a report on a specific error to the error registration service, it is recommended to return an appropriate message from the error registration service. This message will be displayed on the error form.The standard texts of the error messages were different. The dialog box of sending the error report was different.Error representation has been improved.
Information registers.
When recording an information register record set, the insignificant chars to the right of the last significant chart are deleted in string type dimensions.When recording an information register record set, the insignificant chars to the right of the last significant chart were not deleted in string type dimensions.Eliminated unexpected system behavior.
A client application form.
If after the form table display update all displayed rows have become invisible, then the InitialListView form table property is used to define the first displayed row. +If the current table row have become invisible, the nearest (by key) row of the list becomes the current one. A new display list is formed based on the new current row. +It is recommended to review the previous list behavior in the application. +This change is not implemented in version 8.3.16 compatibility mode.If after the form table display update all displayed rows had become invisible, the list display always started from the beginning.Eliminated unexpected system behavior.
Data composition system.
If the filter with the Filled or Is not filled comparison type for the filed which is set as the aggregate function in the query is specified in the settings of the data composition system, then such condition in the resulting query is placed to the HAVING query section. +This change is not implemented in version 8.3.16 compatibility mode.If the filter with the Filled or Is not filled comparison type for the filed which was set as the aggregate function in the query was specified in the settings of the data composition system, then such condition in the resulting query was placed to the WHERE query section.Eliminated unexpected system behavior.
Administration tools.
InfobaseSession.ClientIPAddress property contains IP-address for another sessions only if the user has the Administration right. Otherwise, this property contains an empty string.InfobaseSession.ClientIPAddress property always contained IP-address for another sessions.Increased security of the infobase sessions list.
Error handling.
For the ErrorCategory system enumeration, the FullTextSearchError, ExternalDataSourceError, and NavigationLinkError values are implemented.

Help is disabled in the error form and error report form, because there may be no connection with the server when these forms are displayed.

Changed the format of the report.json file, which contains automatically collected error information. Changes are stated in the documentation as well.

When adding screenshots in the error report, screenshots of all application windows will be added (even if the application is not active).

For the ErrorProcessingSettings object, the IncludeScreenshotsInReport, IncludeDetailedErrorTextInReport, IncludeInfobaseInformationInReport, and AdditionalReportInfo properties are implemented.

The appearance of the error report form has been improved.

The request file format has been modified for the getInfo method of the error registration web service. It will allow to return localized message texts to the user and specify the dump format for transferring in service (available only when running Windows).

These features were not provided.The mechanism of runtime errors processing has been improved.
Localization.
Web client.
Localized web client application interface for Arabic (ar).This feature was not provided.1C:Enterprise web client is now available for Arabic-speaking users.
Queries.
Optimized execution of queries using the IN operator with a list of values containing the UNDEFINED value.Executing queries using the IN operator with a list of values containing the UNDEFINED value was not optimal.Optimization results in faster query execution, if after the field used in the expression Field IN (Undefined) there are still fields in the index that are used in the filter.
DBMS operations.
System requirements.
Microsoft SQL Server 2019 DBMS is now supported.Microsoft SQL Server 2019 DBMS was not supported.New Microsoft SQL Server version is now supported.
Client application.
Web client.
Error handling.
If an unrecoverable error occurs, the option to automatically terminate the client application without displaying a dialog that requires a user reaction is implemented. The /DisableUnrecoverableErrorMessage client application start line command has been implemented.This feature was not provided.

When an unrecoverable error occurred, a dialog was generated that required a mandatory user reaction.

Simplified the system use in modes when the client application does not require a presence of user (for example, in automatic testing mode).
Spreadsheet documents.
Data display.
Implemented the feature to save the text writing direction in a spreadsheet document for exporting and printing. This feature is available for thin client, thick client, and web client. The text direction is saved when exporting to all appropriate formats.

Text direction is supported for the 1C:Enterprise spreadsheet document and for imported spreadsheet documents of XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) formats.

Added the TextDirection spreadsheet document property. This property allows to specify the text direction in a spreadsheet document explicitly: left-to-right or right-to-left.

If a cell has automatic horizontal alignment, the numbers are always right-aligned, and other values are aligned according to the interface text direction.

A spreadsheet document was exported and printed with left-to-right text direction. The export and print mode did not depend on the operating system used.Eliminated unexpected system behavior.
Collaboration system.
You can now perform a video call in thick or thin client in remote desktop window.There was no option to perform a video call in thick or thin client remote desktop window.Video calls in thin and thick client are more accessible now.
Mobile platform.
Mobile client.
1C:Enterprise mobile version now supports the hardware or external keyboard in the client application form fields that display values of Number and Date types.

Tab and Shift+Tab shortcuts can now be used to navigate through the form fields. The arrow keys of hardware or external keyboard, joystick, or other cursor control mechanism can now be used to navigate through the form fields.

The keyboard shortcuts configured by the developer are now supported for the form items. The standard keyboard shortcuts used in the PC version are not supported.

Implemented the Esc and Enter keys support on a hardware or external keyboard.

This feature was not provided.Improved data input on mobile devices through a hardware or external keyboard.
Accumulation registers.
When the maximum period of calculated totals of the accumulation register is set, it is not possible to add register records of this register.When the maximum period of calculated totals of the accumulation register was set, it was possible to add register records of this register. When the maximum period of calculated totals was changed and register records were added at the same time, register totals could be incorrect.Eliminated unexpected system behavior.
Analytics system.
For the analytics system manager, implemented the GetConnections() method that returns the AnalyticsSystemServerConnection object. Implemented the AnalyticsSystemSchema object.

Implemented the options to manage additional sources for the standard data processor of analytics management.

The RefreshInterface() global context method changes visibility of the Analytics item in the Service and settings menu (depending on the current analytics system settings).

These features were not provided.Extended API of interaction with the analytics system.
Analytics system.
Collaboration system.
If an infobase supports the collaboration system, the analytics system provides the ability to open information on a reference type object in all client applications of this user at once.This feature was not provided.Improved the analytics system interface.
Full-text search.
Common attributes / Data separation.
Reduced use of RAM upon indexing information register records.

Faster indexing for separated infobases.

Changed the format of temporary full-text search files. Now the format changes automatically upon index update. Upon migration to the previous platform version, the index will be cleared.

Indexing information register records required more RAM.

Building a full-text search index for a separated infobase took more time.

Improved building of a full-text search index.
Client application form.
Mobile platform.
Mobile client.
If an input field is used to enter a value of the Number type and the SpecialTextInputMode property is set to Digits, a calculator that contains only digits, a comma, the last character delete button, OK, and Cancel is used for input.If an input field was used to enter a value of the Number type and the SpecialTextInputMode property was set to Digits, a standard calculator with excessive features was used for input.Simplified number input in mobile applications.
Automated testing.
Improved performance of the following methods of the TestedApplication object and objects of client application windows: FindObject(), FindObjects(), and GetObject().Execution of the following methods of the TestedApplication object and objects of client application windows took more time: FindObject(), FindObjects(), and GetObject().Improved performance of the automated testing feature for the client application.
Mobile application builder.
The mobile application builder can now upload new 1C:Enterprise mobile versions automatically. This feature is supported by the client/server mode of the mobile application builder only.

The mobile application builder in the file mode has the following options (and settings) disabled:

  • Clearing the obsolete data from the infobase.
  • Clearing the obsolete data from the builder cache.
The mobile application builder could upload the new 1C:Enterprise mobile version interactively only.

Clearing the obsolete data from the infobase and from the builder cache were available in the file infobase mode. This could potentially cause unexpected system behavior due to the scheduled job feature specifics in the file infobase mode.

Uploading new 1C:Enterprise mobile versions in the mobile application builder is now faster and more convenient.
Infobase verification and repair.
Infobase verification and repair feature now includes an option to check the logical integrity of the configuration extension. Some repair options are also available for the extensions.

Added the new parameter for the /IBCheckAndRepair command of the Designer batch mode - ConfigurationExtensionsLogIntegrity. This parameter launches the logical integrity check of the configuration extension.

Infobase verification and repair feature had no option to check and repair configuration extensions errors. Some errors might cause the entire infobase to be unavailable. +Improved the reliability of infobases containing extensions.
Dumping configurations to files/Restoring configurations from files.
The format version of the configuration export to XML is now 2.11.The format version of the configuration export to XML was 2.10.The configuration export to XML now supports new platform features.
Error handling.
The network errors info feature was completely reviewed. Improved the error messages text, that now contain information about the error and its possible causes.

If there was a network connection error while requesting the 1C:Enterprise server cluster and there is an option to retry the request after the connection was restored, the prompt to retry the request will be replaced by the message that the network connection was restored.

The error dialog box does not provide the option to send an error report, if there is no network connection.

Application developers should rework the application code using the following recommendations:

  • Use a single idle handler to execute user actions, such as procedure delayed execution or displaying the current row data.
  • Use a repeated idle handler to execute automatic actions without user interaction, such as status updates.
  • We recommend to change the error display mode for configurations that use the version 8.3.16 and earlier compatibility mode to User message errors. Use the standard function of error processing settings management for that.
The error messages were harder to understand and more annoying.

An option to send the error report was available even if there was no network connection (thus the report could not be sent).

The network errors dialog boxes are now less annoying.
Client application.
For all client applications the login button in the authentication dialog box is now called Log in.

There is now an option to show the password. Implemented the button to show/hide the password.

Improved the authentication form display of OpenID Connect on mobile devices.

For all client applications the login button in the authentication dialog box was called Ok.

There was no option to show the password.

The authentication dialog box is now more convenient.
Improved performance of initial population of database copy table if this table is included in multiple transactions.The performance of initial population of database copy table if this table was included in multiple transactions was not optimal.Improved performance of initial population of database copy table if this table is included in multiple transactions.
System requirements.
Mobile platform.
Mobile client.
Mobile applications built using mobile version 8.3.17.67 will meet the requirements of Google Play for new applications. The target SDK version is 29.

To upload a mobile application to Google Play, build a mobile application using mobile version 8.3.17.67 or later. +

Mobile applications built using mobile versions that are older than 8.3.17.67 could not be uploaded to Google Play after August 3, 2020.1C:Enterprise mobile version meets the requirements of Google Play.
Mobile device-specific features.
Mobile platform.
Mobile client.
For mobile version tools responsible for audio recording on a mobile device, the following features are now available:
  • Managing audio recording parameters: result format, mono or stereo recording, audio stream characteristics, and other. New object: AudioRecordingParameters.
  • New parameters for the MultimediaTools.MakeAudioRecording(): AudioRecordingParameters, StartRecordingAtOnce, and DisplayListeningWindow. The parameters allow you to manage audio recording when you use the mobile application.
  • New feature: background audio recording can be managed using device microphones. New methods for the MultimediaTools global context property: EnableAudioRecording() and DisableAudioRecording().
Audio recording parameters could not be configured on a mobile device. Background audio recording was not supported on a mobile device.New features for audio recording on a mobile device.
Integration service.
Improved sending and receiving of integration service messages.When using integration services, sending and receiving of messages were not sufficient enough.Improved sending and receiving of integration service messages.
Mobile device-specific features.
Mobile platform.
Mobile client.
Mobile application builder.
AppSee is removed from the list of supported statistics services.1C:Enterprise mobile version supported AppSee.1C:Enterprise mobile version does not support AppSee.
Mobile device-specific features.
The EnableAudioRecording() and MakeAudioRecording() methods prevent the mobile device from idling to sleep to prevent audio recording from stopping.

The audio recording stop handler passed to the EnableAudioRecording() method is called to not lock the user interface.

The default value for the ButtonLocation parameter of the EnableAudioRecording() method is Undefined.

Improved the audio recording interface.

The EnableAudioRecording() and MakeAudioRecording() methods did not prevent the mobile device from idling to sleep. As a result, audio recording could stop.

The audio recording stop handler passed to the EnableAudioRecording() method was called in such a way that a long server call from this handler could lock the user interface.

The default value for the ButtonLocation parameter of the EnableAudioRecording() method was the value where the platform automatically selected the location of the button to stop recording.

Improved the audio recording interface (both user interface and API) in the mobile application.
Mobile client.
The mobile client tries to close the session in the server cluster correctly in case of unexpected shutdown. Abnormal termination can occur, in particular, when the mobile operating system removes the mobile client application from RAM when the device enters sleep.The mobile client did not try to close the session in the server cluster correctly in case of unexpected shutdown. +Reduced the number of hung mobile client sessions. This reduces the amount of occupied licenses and locks from inactive devices.
System requirements.
Updated system requirements for the client application:
  • Minimum system requirements:
  • Recommended system requirements:
The system requirements for the client application were as follows:
  • Minimum system requirements:
  • Recommended system requirements:
Updated system requirements for client applications (including Designer).
Mobile device-specific features.
Mobile platform.
Mobile client.
For a mobile application running Android 10 or later to use geolocation in the background, set the Background location permission in Designer, export the configuration, and rebuild the mobile application using Mobile Application Builder.A mobile application running Android version 10 or later was unable to use geolocation in the background.The limitations of Android 10 and later are taken into account.
Mobile client.
Upgrade: checking the connectivity to the selected infobase in the mobile client is revised. A mobile client signature is verified not only on the mobile client but also on the server. The mobile client can connect to the infobase if the mobile client configuration and the server configuration match at least 80%.

Changed setup for generating an infobase configuration signature.

Errors that occur while checking the mobile client connectivity to the selected infobase are now more user-understandable.

Mobile client connectivity to the infobase was tested only on the mobile client.

The requirement to match mobile client configurations and main infobase configurations was more stringent.

The mobile client can connect to the infobase in more cases. The need to update the mobile client is now less acute. The previously published mobile client can work with the infobase in case of minor modifications to the infobase configuration.
Mobile platform.
Mobile client.
To restore the ability of the mobile application to access files on a mobile device, do the following:
  • Install SDK Platform for API 29 in Android Studio used by Mobile Application Builder.
  • Upload the mobile version 8.3.17.80 or later to Mobile Application Builder.
  • Build a mobile application with a new mobile version.
  • Republish the mobile application on Google Play.

+The target Android version is set back to 10.0 (API 29).

The target Android version was 11 (API 30). As a result of changing the target Android version, the mobile application lost access to files on the mobile device.Restored access to files on a mobile device.
Mobile application builder.
Mobile Application Builder now supports Xcode 12.Mobile Application Builder did not support building using Xcode 12.Mobile Application Builder now supports the latest Xcode version.
System requirements.
Mobile platform.
Mobile client.
The mobile version now supports Android 11 and iOS 14.The mobile version did not support Android 11 and iOS 14.The mobile version of 1C:Enterprise now supports the latest mobile operating systems.
Licensing system.
In file mode, it is checked whether there is a feature testing license.

In partictular, using integration services in a file infobase requires a feature testing license.

In client/server mode, the upgrade is ignored.

The feature testing license check depended on the infobase mode:
  • In client/server mode, the check was performed.
  • In file mode, the check was not performed.
Eliminated unexpected system behavior.
Pictures.
When receiving an SVG image from a temporary storage, an infobase or via a direct link, sections with JavaScript are removed from the image.When receiving an SVG image from a temporary storage, an infobase or via a direct link, sections with JavaScript were not removed from the image.Reduced the possibility of destructive actions using JavaScript embedded in an SVG image.
Development tools.
Mobile client.
The mobile client configuration that was signed in version 8.3.16 (and the signature was not changed in version 8.3.17 and later) is accepted by the mobile client in version 8.3.17 and later.

We do not recommend that you change the configuration signature in version 8.3.16 if the configuration is executed on version 8.3.17.

The mobile client configuration that was signed in version 8.3.16 (and the signature was not changed in version 8.3.17 and later) was not accepted by the mobile client in version 8.3.17 and later. Platform version 8.3.17 and later considered such a configuration to be unsigned.As a result, after updating the platform on the server cluster computer up to version 8.3.17, mobile clients running iOS will remain in operation.
Client application.
When using 1C:Enterprise authentication or accessing infobase with thin or web client using HTTP protocol, user password is passed using SHA-256 hash algorythm and AES-256 CBC encoding algorythm..Thin and web clients passed the user password not encrypted when using 1C:Enterprise authentication or accessing infobase with thin or web client using HTTP protocol.Thin and web cliients now use safer authentication when accessing infobase using HTTP protocol.
Mobile device-specific features.
PUSH notifications that are sent from the mobile platform for PC through APNS service now use HTTP/2 protocol, port 443.PUSH notifications that were sent from the mobile platform for PC through APNS service used obsolete binary protocol.PUSH notifications can now be sent through APNS.service again.
Event log.
Server clusters.
Limited the number of event log indexing streams. New technological log event: <EVENTLOG>.Event log indexing could produce heavy system load, especially with a large number of infobases.Reduced the system load caused by event log indexing when the server cluster hosts a large number of infobases.
Web client.
System requirements.
The web client is now supported in the following web browsers:
  • Google Chrome 49 and later running Linux.
  • chromium-gost version 49 and later running Linux, macOS, or Windows.
The web client was not supported in the following web browsers:
  • Google Chrome of any version running Linux.
  • chromium-gost of any version.
Extended the list of web browsers to run the web client.
Event log.
In a file infobase, the event log indexing and the use of an already built index are disabled.In a file infobase, the event log was indexed and an already built index was used in the event log.Decreased infrastructure load, especially for a shared file infobase. Improved client application stability.
Server clusters.
Eliminated the slowdown in user operations when there is insufficient RAM on computers running cluster working processes. The RAM consumption by cluster working processes might increase.When there is insufficient RAM on computers running cluster working processes, there was a significant performance decrease.Eliminated the slowdown in user operations when there is insufficient RAM on computers running cluster working processes.
XML and XDTO support.
Reading a large CDATA section for an XML document with UTF-8 encoding is now faster.Reading a large CDATA section for an XML document with UTF-8 encoding was slow.Improved XML document performance in some cases.
Linux.
Server clusters.
Administration tools.
Implemented operating system authentication via Kerberos protocol for 1C:Enterprise client applications managed by Linux.This feature was not provided.Linux users in a Windows domain network can now use operating system authentication to access infobases that are managed by a Windows server cluster.
Standalone server.
New feature: authentication in the infobase is required to perform operations with it via the standalone server administration utility (ibcmd). It is required for the following commands:
  • Dump infobase to a DT file (infobase dump).
  • Restore infobase from a DT file (infobase restore).
  • Clear infobase (infobase clear).
  • Load configuration (infobase config load).
  • Save configuration (infobase config save).
  • Check infobase (infobase config check).
  • Update database configuration (infobase config apply).
  • Reset to database configuration (infobase config reset).
  • Export configuration to XML files (infobase config export).
  • Import configuration from XML files (infobase config import).
  • If the standalone server administration utility (ibcmd) requires to specify a password to connect to the infobase and it is not specified in the utility parameters, you are prompted to enter a password in the console.
  • New command line parameters for the standalone server administration utility (ibcmd): --user and --password.
Authentication was not required to perform operations with an infobase via the standalone server administration utility (ibcmd). If connection to DBMS administration utility required a password and it was not specified, the administration utility did not prompt you to enter it.Operations with the infobase via the standalone server administration utility (ibcmd) are more secure.
Web client.
System requirements.
Yandex Browser version 22 or later is now supported on Linux, macOS, and Windows.This feature was not provided.Extended list of supported web browsers.
Client application form.
If visibility is disabled for a form table in the client application, calls of the following methods of this table are ignored: Expand(), Collapse(), AddRow(), ChangeRow(), CopyRow(), EndEditRow(), and Refresh(). This update is applied to tables whose visibility was disabled by the user, tables in a collapsed group, and so on.

+

+

If visibility was disabled for a form table in the client application, calls of the following methods of this table raised an exception: Expand(), Collapse(), AddRow(), ChangeRow(), CopyRow(), EndEditRow(), and Refresh(). This behavior was relevant for tables whose visibility was disabled by the user, tables in a collapsed group, and so on.Eliminated unexpected system behavior.
Development tools.
You can control remote debugging and debugging features for separated infobases. To do it, you can specify users who can debug the configuration (broken down by infobases). To connect to the debugger, specify username and password.

New command for the command line of ragent and dbgs utilities: debugServerUsers. For more information about the user description file format, see the documentation.

In the dialog box of Designer parameters, on the Debug tab, the Password input field is removed.

New event log events: Debugging. Debug item attachment, Debugging. Debug item detachment, and Debugging. Expression calculation.

This feature was not provided.

You could specify one password to debug any database served by a cluster.

Advanced development features for applications running in separated infobases.

+

Web client.
System requirements.
In web client, the minimum supported Google Chrome version is 88.

Clipboard operations can be performed in web client without the file system extension in Google Chrome. However, web client must be available over HTTPS or published on a local computer. If these conditions are not met, clipboard operations are unavailable.

In web client, the minimum supported Google Chrome version was 49.

The file system extension had to be installed in Google Chrome to perform clipboard operations in web client.

Ended support for legacy Google Chrome versions.
Administration tools.
New user password features:
  • Set the minimum password complexity with specification of required password characters and password complexity.
  • Set the minimum and maximum password validity period.
  • Prohibit usage of previously used passwords.
  • Group user password rules into password profiles.
  • Assign password profiles to users.
  • Check whether a password corresponds to the current password policies without saving a user (actual or dummy one) to the infobase.
  • Change user passwords with enabled password change prohibition if you have administrative rights.

New global-context methods: SetUsersPasswordsMinValidityPeriod(), GetUsersPasswordsMinValidityPeriod(), SetUsersPasswordsMaxValidityPeriod(), GetUsersPasswordsMaxValidityPeriod(), SetUsersPasswordsRepetitionRestrictionAmongRecent(), GetUsersPasswordsRepetitionRestrictionAmongRecent(), SetPeriodOfWarningAboutUsersPasswordsExpiration(), and GetPeriodOfWarningAboutUsersPasswordsExpiration().

New global-context property: UsersPasswordsPolicies.

New property: AuthenticationSecondFactorSettingsTemplates.UsersPasswordsPolicies.

New properties for the InfobaseUser object: PasswordsPolicyName, PasswordSettingDate, and WrittenPasswordSettingDate.

These features were not provided.

Some of the features could be implemented in 1C:Enterprise language, which allowed bypassing of requirements.

Improved user password features, which resulted in overall better system security.
Licensing system.
The license owner address is hidden from the About... dialog box when the list of active (or activated) licenses is displayed. For licenses displayed in the Infobase and Configuration sections, addresses are not hidden for the rows obtained by previous 1C:Enterprise versions.The license owner address was displayed in license information in the About... dialog box.The license owner address is no longer displayed in license information in the About... dialog box.

+

Table of contents

Transition from the previous version to the version 8.3.17

Table of contents

Version 8.3.16

Version 8.3.16 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.15 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.14 was available.Configurations developed using 1C:Enterprise platform version 8.3.15 or earlier can now run on version 8.3.16 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.16 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.15 after the migration to version 8.3.16, even if you disable the compatibility mode (simply enable it again).
System requirements.
Implemented Programming Training Version running on Linux and macOS.Programming Training Version ran on Windows only.Programming Training Version runs on all supported operating systems.
System requirements.
macOS.
OS X family (version 10.11 or under) is no longer supported. Client application runs on macOS only (version 10.12 or above).Client application could run on OS X (version 10.8 or above).Outdated operating systems are no longer supported.
Server clusters.
Administration tools.
In client/server mode, you can now limit the number of logon attempts with an incorrect password.

The following parameters are implemented for the infobase: maximum number of failed authentication attempts before a user is blocked; a time interval during which a user who made a threshold number of authentication attempts cannot attempt authentication again; username suffixes that should be used if it is necessary to authenticate as a blocked user.

New global context property: AuthenticationLock.

New form to view authentication locks in Designer (Administration – Authentication locks). This command is available only to a user with administrative rights.

Implemented the following event log events:

  • Users. Authentication lock (_$User$_.AuthenticationLock).
  • Users. Authentication unlock (_$User$_.AuthenticationUnlock).
  • Users. Authentication unlock error (_$User$_.AuthenticationUnlockError).

+New data of event log events:

  • Infobase. Infobase parameters change.
  • Session. Authentication.
  • Access. Access (only for a Z version)
  • Access. Access denied.

+In the display form of the list of active users of Designer, you can now view a column with characteristics of user data separation.

This feature was not provided.

The platform did not prevent someone from guessing the password by going through the options.

Reduced the likelihood of guessing the infobase user password by going through the options.
Queries.
New feature: the query language now supports grouping sets.

Upgrade: the query language now supports keywords GROUPING SETS for sentence GROUP BY.

New query language function that allows you to determine whether a function parameter can be grouped: GroupedBy().

This feature was not provided.Upgrade: grouping by several field sets is faster because grouping is performed per table scan.
Charts.
Data composition system.
When using charts, you can now save a map between an object (displayed by different charts) and its color.

For charts displayed on the form, 1C:Enterprise code is required for this. For the data composition system, this feature is available using settings.

A map between an object and its color is saved to the settings system storage.

Implemented the Chart.FillSeriesColors() method.

For objects

DataCompositionOutputParametersValues,

DataCompositionGroupOutputParametersValues, DataCompositionChartOutputParametersValues, and

DataCompositionAreaChartAppearance, implemented properties ChartType.ColorsSaving and ChartType.ColorsSavingKey. New property: ProcessorOfDataCompositionResultOutputToSpreadsheetDocument.AppearanceForValues. New property: DataCompositionAreaChartGroupTemplate.Presentation.

This feature was not provided.

The same object could be displayed by charts with a different color, resulting in bad report readability.

The same object can be displayed by charts with the same color that helps make charts look better and more informative.

+

Collaboration system.
When using the collaboration system, you can now share your PC screen on a video call.

In the web client, screen sharing is available only in Google Chrome and Mozilla Firefox. In the web client, Google Chrome supports sharing of the current web browser tab.

This feature was not provided.Expanded the collaboration system capabilities.
Collaboration system.
On setting the CollaborationSystemMessage.Text property of the FormattedString type from 1C:Enterprise code, appearance is saved (except pictures to be deleted). This message is displayed by the system considering its formatting. A message with appearance cannot be created interactively.

Smileys set by emoticons (Unicode characters) are now supported.

This feature was not provided.New operations with collaboration system messages.
Administration tools.
Server clusters.
You can now get a server cluster version using program administration interfaces. Getting a server cluster version is only available if a server cluster is running 1C:Enterprise version 8.3.11 or above.

Implemented ServerAdministration.GetVersion() method.

Implemented the agent version command of the rac utility.

This feature was not provided.On program administration of the server cluster, you can now determine which features can or cannot be used depending on 1C:Enterprise version the server cluster is running on.
Spreadsheet document.
Formatted document.
Processing PDF documents.
On saving a PDF document, the OpenType font is now available if it is used in appearance of the document to be saved.This feature was not provided. On saving to the PDF format, only TrueType fonts were embedded.Improved compatibility of PDF documents generated by 1C:Enterprise with different PDF document display devices.
Charts.
You can now interactively change values displayed by charts of the following kinds: a line, a step, and an area (including summarized and normalized series). This feature is not provided in 8.3.15 compatibility mode.

Implemented the ValuesEditMode property for Chart and ChartSeries objects. New property: ChartValue.EditMode. New event for the chart form field extension: OnEditValue.

The form field extension event for the OnChangeAreaContent spreadsheet document will be called upon interactive editing of a chart and a Gantt chart inserted into the spreadsheet document. The AdditionalParameters parameter is implemented in the handler.

This change is not implemented in 8.3.15 compatibility mode.

This feature was not provided.

The form field extension event for the OnChangeAreaContent spreadsheet document was not called upon interactive editing of a Gantt chart inserted into the spreadsheet document.

Improved chart interactivity.
Web client.
You can now embed the web client in third-party sites and ensure the web client interacts with these sites.

New global context property: ExternalSiteWindow. Implemented the ClientApplicationMainWindowMode.EmbeddedWorkplace system enumeration value.

Implemented the MainWindowMode command-line command for the client application and web client.

Implemented the following access rights, which allow you to start the client application in a main window mode: StandardMainWindowMode, MainWindowModeWorkplace, MainWindowModeEmbeddedWorkplace, MainWindowModeFullScreenWorkplace, and MainWindowModeKiosk.

Implemented Embedded WebClient API, which allows a site to interact with the web client.

This feature was not provided.

It was impossible to embed the web client in a third-party site.

Advanced web client features.
Spreadsheet document.
Processing PDF documents.
New feature: you can save a spreadsheet document to PDF/A-2 and PDF/A-3 (versions of the PDF/A format used for long-term storage).

New values for the SpreadsheetDocumentFileType system enumeration: PDF_A_2 and PDF_A_3.

Implemented two syntax options for the SpreadsheetDocument.Write() method. Implemented the Attachments parameter for the SpreadsheetDocument.BeginWriting() method.

New objects: ReadPDF and WritePDF.

It was possible to save a spreadsheet document to PDF/A-1 only.Expanded spreadsheet document export features.
Charts of characteristic types.
Implemented the FullDescription() method for ChartOfCharacteristicTypesRef and ChartOfCharacteristicTypesObject objects.This feature was not provided.Unified behavior of the chart of characteristic types and the catalog for getting an item presentation based on hierarchy.
Spreadsheet documents.
New feature: you can write a spreadsheet document (using the SpreadsheetDocument.Write() method in an option for writing to a stream) to a stream as XLSX.It was not possible to write a spreadsheet document (using the SpreadsheetDocument.Write() method in an option for writing to a stream) to a stream as XLSX.Expanded features of spreadsheet document export to streams.
Configuration extensions.
You can now create the following objects in a сonfiguration extension:
  • Constants
  • Functional options and functional option parameters
  • Filter criteria.

+You can now extend the following:

  • Adopted functional options (using own and adopted objects)
  • Adopted filter criteria using attributes of own extension objects.
These features were not provided. Extended configuration extension options.
Managed forms.
New feature: you can generate a planner context menu from 1C:Enterprise code and specify an action called upon clicking (depending on the click area).

New events for the form field extension for the planner field: GenerateCommandsProcessing,

DimensionItemClick,

TimeScaleItemClick,

and WrappedTimeScaleHeaderClick.

New properties for the form field extension for the planner field: TimeScaleItemHyperlink, DimensionItemHyperlink, and

WrappedTimeScaleHeaderHyperlink.

These features were not provided.New planner features.
Managed forms.
New feature: you can use a search string for a form table that displays a value table, a value tree, or a value list.

Search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>.

This change is not implemented in 8.3.15 compatibility mode.

New feature: you can use the Find by current value command in all form tables ignoring сonfiguration compatibility mode.

The search string was available only for form tables that displayed a dynamic list. In other tables, search was done using the standard dialog box, which performed positioning.

Search by current value was not available.

Improved search in tables of managed forms, including a pictorial view of searching in the table.
Data composition system.
Pictures.
New feature: you can use pictures for conditional appearance of reports in the data composition system. New property: DataCompositionAppearance.Picture.

New pictures in the picture library: AppearanceGreenUpTriangle, AppearanceYellowHyphen, AppearanceRedDownTriangle, AppearanceGreenUpArrow, AppearanceGreenUpInclineArrow, AppearanceYellowUpInclineArrow, AppearanceYellowRightArrow, AppearanceYellowDownInclineArrow, AppearanceRedDownArrow, AppearanceRedDownInclineArrow, AppearanceGrayUpArrow, AppearanceGrayUpInclineArrow, AppearanceGrayRightArrow, AppearanceGrayDownInclineArrow, AppearanceGrayDownArrow, AppearanceGreenCircle, AppearanceYellowCircle, AppearanceRedCircle, AppearanceBlackCircle, AppearanceCharCheckBox, AppearanceCharExclamationMark, AppearanceCharCross, AppearanceCheckBox, AppearanceExclamationMark, AppearanceCross, AppearanceGreenFlag, AppearanceYellowFlag, AppearanceRedFlag, AppearanceFullStar, AppearanceHalfFullStar, AppearanceEmptyStar, AppearanceFilledCircle, AppearanceThreeQuartersFilledCircle, AppearanceTwoQuartersFilledCircle, AppearanceOneQuarterFilledCircle, AppearanceEmptyCircle, AppearanceFourFilledBoxes, AppearanceThreeFilledBoxes, AppearanceTwoFilledBoxes, AppearanceOneFilledBox, and AppearanceEmptyBoxes.

In conditional appearance, you can use only the above pictures from the picture library.

If the сonfiguration already has pictures with the same names, a picture from the сonfiguration is added to the collection and a warning is generated upon сonfiguration update.

This feature was not provided. Conditional appearance of the data composition system did not allow you to use pictures for conditional appearance of reports.Specifying pictures in conditional appearance of reports built using the data composition system is now easier.
Pictures.
For common pictures, you can now specify that a common picture is used:
  • To select a picture in a cell, an image, or a header/footer of a spreadsheet document in 1C:Enterprise mode. New property: CommonPicture.ChoiceAvailability.
  • To select to use reports of the data composition system in conditional appearance. New property: CommonPicture.AppearanceAvailability.

Property CommonPicture.ChoiceAvailability is ignored in 8.3.15 compatibility mode. Property CommonPicture.AppearanceAvailability is ignored in 8.3.15 compatibility mode.

This feature was not provided.New feature: you can specify which common pictures can be used when working with a spreadsheet document in 1C:Enterprise mode and conditional appearance. As a result, there are less pictures a user can select from in these situations.
XML and XDTO support.
New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as default or fixed ones.Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as default or fixed ones, errors occurred when checking the XDTO model, and such schemas were not available.Eliminated unexpected system behavior.
Charts.
Data composition system.
You can now build combo charts and display a secondary value scale for the following chart types:
  • Column
  • Bar
  • NormalizedColumn
  • NormalizedBar
  • StackedColumn
  • StackedBar
  • Line
  • Step
  • StackedLine
  • Area
  • StackedArea
  • NormalizedArea
  • Column3D
  • StackedColumn3D
  • NormalizedColumn3D
  • Bar3D
  • StackedBar3D
  • NormalizedBar3D

Implemented animation upon chart value change.

Implemented the SecondaryValuesAxis property for ChartPlotArea and Chart objects. New property: ChartScale.Display. New properties for the ChartSeries object: GraphicalPresentationType, AccumulationType, AccumulationGroup, UsedValuesAxis, ValuesFormatInLabels, PercentageFormatInLabels, and FormatInDataTable.

The ChartSeries.Indicator property is deprecated and supported for compatibility purposes. Use the ChartSeries.GraphicalPresentationType property instead.

The Chart.ChartType property value is Column by default.

The Chart.Outline property value is False by default.

New properties for objects DataCompositionAreaChartGroupAppearance and DataCompositionAppearance: GraphicalPresentationTypeInChart, AccumulationTypeInChart, and UsedValuesAxisInChart. New property: DataCompositionAreaChartGroupAppearance.AccumulationGroupInChart. For objects

DataCompositionOutputParametersValues,

DataCompositionGroupOutputParametersValues, DataCompositionChartOutputParametersValues, and

DataCompositionAreaChartAppearance, implemented parameters ChartType.SecondaryValuesScale and ChartType.SecondaryValuesAxis.

The ChartType.IndicatorInChart parameter is deprecated and supported for compatibility purposes. Use the ChartType.GraphicalPresentationTypeInChart parameter instead.

New parameters for the DataCompositionAreaChartGroupAppearance object: ValuesFormatInChartLabels and FormatInChartDataTable.

This change is not implemented in 8.3.15 compatibility mode. +

It was impossible to build combo charts and display a secondary value scale.

The Chart.ChartType property value is Column3D by default.

The Chart.Outline property value is True by default.

New chart features.
Server clusters.
You can now start backup working processes. A backup working process is started in advance and server cluster overhead is synchronized for it. This feature allows you to reduce the time spent on switching the client application to a new working process in case of unexpected termination of the working process serving this client application.

A flag indicating whether backup is required is set for the infobase. The number of backup working processes is calculated from the Number of infobases per process working server property.

New properties: AdministrationInfobase.WorkingProcessesBackup and AdministrationWorkingProcess.Backup.

The following Java-based methods are implemented in the administration server interface: IWorkingProcessInfo.isReserve(), IInfobaseInfo.getReserveWorkingProcesses(), and IInfobaseInfo.setReserveWorkingProcesses().

The following items are implemented for the cluster service command-line utility (rac):

  • Reserve-working-process parameter for infobase insert and infobase update commands.
  • Reserve-working-processes field for the infobase info command result.
  • Reserve field for the process info command result.
This feature was not provided.

A new working process was started only after the current working process was terminated, which could lead to significant time delays upon client application reconnection. From the user's point of view, it looked like the client application interface froze at the time of connection to a new working process.

Reduced time delays resulting from switching the client application to a new working process. Improved application reactivity. +

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Managed forms.
In the client application form table that displays the value tree (including the All functions dialog box), search using the search string is done considering a parent and by words.

In the history form, record date and time are no longer involved in search.

In the client application form table that displays the value tree, search was done ignoring a parent and by substring.

In the history form, record date and time were involved in search.

Improved search in client application form tables that display trees (including in the All functions dialog box).
Web client.
File operations.
Upgrade: security check of access to the file system and clipboard when accessing the web client in Google Chrome and Mozilla Firefox (including web browser extensions and file system extensions) is updated.

Once the web browser extension and the file system extension are updated, if it is required to get access to the file system, a user will have to confirm that they trust the site (where the web client is published) to use the file system on their local computer. After that, there are no question until this permission is revoked (using settings of the web browser extension). If the user refuses to trust it, the old mechanism for getting permissions is used (a separate request per action).

Clipboard operations are allowed accordingly.

Permissions are stored broken down by site addresses where web clients are published.

In the web client, a separate question was displayed to a user upon each file operation, which was not user-friendly.Simplified file operations in the web client regarding the user permission on operations with the file system and clipboard.
Collaboration system.
New feature: the user history now displays whether this user participates in a context conversation regarding an object associated with a form in the history.

Optimized user history opening.

The user history did not display whether this user participated in a context conversation regarding an object associated with a form.In the history, it is now easier for a user to find object forms, in the context conversation of which this user was a message recipient.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Client application.
Server clusters.
Improved performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster are on the same computer.Performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster were on the same computer was less optimal. Interprocess interactions took more time.Improved performance of 1C:Enterprise running on Windows 8 or above.
Spreadsheet documents.
Reduced amount of RAM used by a spreadsheet document that contains many text cells.A spreadsheet document with many text cells needed more space in RAM.A spreadsheet document now uses smaller amount of RAM.
Server clusters.
Improved performance of the server cluster when working with a large amount of session data. Managed form opening, a context server call, and temporary storage operations take less time now.

New technological log event: <SDGC>.

The server cluster spent more time on handling a large amount of session data. Managed form opening, a context server call, and temporary storage operations took more time.Improved server cluster performance.
Accumulation registers.
Improved performance of a virtual table of accumulation register balance.When using a virtual table of accumulation register balance, more time was spent on getting the query result.Improved performance of a virtual table of accumulation register balance. +
Queries.
Optimized execution of query in client/server infobase mode, that includes the query language operator IN with a list of values, if the left section of IN operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the Undefined value.

This change is not implemented in 8.3.15 compatibility mode.

The query in client/server infobase mode, that includes the query language operator IN with a list of values, if the left section of IN operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the Undefined value, took more time to execute.Optimized execution of queries containing IN operator with composite type fields.
Internet-enabled functionality.
Optimized retrieving of email message headers using the InternetMailMessage.GetHeaderField() method.Retrieving email message headers using the InternetMailMessage.GetHeaderField() method took a considerable amount of time. +Optimized email message headers retrieving.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Data display.
Upgrade: client applications (except the web client) running on macOS, Linux, and Windows are switched to graphics based on the Cairo library.Client applications (except the web client) running on macOS, Linux, and Windows used their own graphics based on different technologies and libraries in each operating system.Unified and optimized user interface display in supported operating systems.
Web client, web service, and HTTP service publishing tools.
In the dialog box for publishing the сonfiguration on a web server, labels now comply with the current client applications of the platform.In the dialog box for publishing the сonfiguration on a web server, labels did not consider the mobile client.The dialog box for publishing the сonfiguration on a web server considers the mobile client.
Full-text search.
New feature: full-text search by hashtag became available (strings of the #Word format, from the # character to the first space).

To apply fuzzy search (both in interactive mode and search from 1C:Enterprise code using the FullTextSearchManager object), use the ~ character.

This change is not implemented in 8.3.15 compatibility mode.

Search by hashtag was not supported but it was possible to find a hashtag value (the word after the # character) in the usual way or by double quoting a hashtag to search for.

The # character was used for fuzzy search. +

You can now hashtag objects involved in full-text search. As a result, it became possible to simply find several different types of objects grouped by hasgtag only.
Access rights.
If the access rights do not allow saving a spreadsheet document, a text document, a graphic chart, a geographical diagram, a package of displayed documents or an HTML document to the file, but after creating these objects, privileged mode was enabled, then the file can be saved.If access rights did not allow saving a spreadsheet document, a text document, a graphic chart, a geographic diagram, a package of displayed documents or an HTML document to a file, then enabling privileged mode was ignored and the the files could not be saved.Eliminated unexpected system behavior.
Input by string.
When using input by string for a managed application, all searched words are highlighted in search results if full-text search is not used for input by string or full-text search failed with an error.

If full-text search in data is used for input by string, the The method of searching for the specified string during the input by string setting is ignored upon successful application of full-text search, the searched text is always split into words, and search is based on the beginning of the words.

This change is not implemented in 8.3.15 compatibility mode.

When using input by string for a managed application, if full-text search was not used for input by string or full-text search failed with an error, two consecutive occurrences of the same string were not highlighted and only the first occurrence of the searched word was highlighted in the first half of results (when searching for one word).Improved search result highlighting for input by string.
Data display.
With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers.With the Windows operating system, there were some issues when working with unavailable printers, such as unexpected shutdown of the client application and a significant slowdown upon client application start.With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers.
Server clusters.
This change is rolled back.

New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is SystemBackgroundJob.RecalcTotals. Implemented the Number of totals recalculation job parameter for the Infobase parameters dialog box. There are 4 recalculation background jobs by default.

New global context methods: GetTotalsRecalculationJobsCount() and SetTotalsRecalculationJobsCount().

Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers.New feature: totals are recalculated faster upon infobase restructuring, testing, and repair.
Automated testing.
You can now use form item additions in automated testing. Implemented the FormItemAdditionToTest object.

For the FormTableToTest object, the result returned by GetSubobjects(), GetObject(), FindObjects(), and FindObject() methods can include objects of the FormItemAdditionToTest type.

For the FormTableToTest.NavigateLevelDown() method, implemented the RowDetails parameter that allows you to specify presentation of a child group to go to.

For the FormTableToTest.NavigateLevelUp() method, implemented the RowDetails parameter that allows you to specify presentation of a parent group to go to.

For the FormTableToTest.Expanded() method, implemented the RowDetails parameter that allows you to specify presentation of a row of a table, for which it is necessary to check whether this row is collapsed or expanded.

For the FormTableToTest.CanExpand() method, implemented the RowDetails parameter that allows you to specify presentation of a table row, for which the expanding feature is being checked.

Implemented the FormFieldToTest.GetStateDisplay() function that returns the current state of a spreadsheet document field.

Implemented the ApplicationToTest.WaitForState() function intended for waiting within the specified time.

Implemented the FormGroupToTest.CurrentOpened() function that returns a group status: collapsed or expanded.

Implemented the FormButtonToTest.CurrentCheckBox() function that indicates whether the button is pressed or displays the check box.

A reference to the function that will return the notification processing result to the platform can be passed to the ExecuteNotificationProcessing() method now. +

These features were not provided.Extended automated testing capabilities. New features of the Taxi interface are considered in the functionality.
Managed forms.
Configuration extensions.
The adopted form editor now displays changed and unchanged adopted form items with different colors.

The form editor command that allows you to display only changed adopted and own form items in the form item tree is now available.

The extension object property panel now displays properties of a сonfiguration object changed in the extension in relation to the extendable сonfiguration with another color.

The extension object property panel now has a command that shows only properties that were changed in relation to the extendable сonfiguration.

In the adopted form editor, it was impossible to hide unchanged adopted items in the form item tree. Form items were not distinguished by color.

In the property panel, it was not possible to quickly distinguish between changed and unchanged properties of an adopted configuration object.

New feature: easier editing of adopted сonfiguration objects.
Dynamic lists.
The dynamic list does not support fields with different expressions for selection and filtering as key fields.

This change is not implemented in 8.3.15 compatibility mode.

It was possible to use fields with different expressions for selection and filtering as the key fields of the dynamic list. In this case, the dynamic list operation could cause various hard-to-diagnose errors.Eliminated unexpected system behavior.
Spreadsheet documents.
When opening a spreadsheet document in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format in 1C:Enterprise, conditional formatting is only imported for the area of the source document that contains data. Conditional formatting import now has reduced RAM consumption.

When viewing a spreadsheet document obtained after import, there may be situations when the formatting of the resulting document differs from the source document (design of the document area that does not contain data).

When opening a spreadsheet document in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format in 1C:Enterprise, conditional formatting was not imported for the whole document. In this case, a session could abnormally terminate due to lack of RAM.Improved 1C:Enterprise stability when importing spreadsheet documents in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format, when conditional formatting is set for the whole sheet, and not just for a meaningful area.
Data composition system.
The type of data composition system field that results from using the query language aggregate functions SUM() and AVERAGE() will be an unlimited length number.

This change is not implemented in 8.3.15 compatibility mode.

The type of data composition system field that resulted from using the query language aggregate functions SUM() and AVERAGE() was the type of field, which was used as parameter for these aggregate functions.Eliminated unexpected system behavior.
DBMS operations.
The data (Purpose field) returned by the GetDBStorageStructureInfo() global context method contains information that describes the tables that are created using the database copy functionality.The data returned by the GetDBStorageStructureInfo() global context method did not contain information that described the tables that are created using the database copy functionality. The Main value was specified as the table purpose for all the tables after using the database copy functionality.Eliminated unexpected system behavior. +
Spreadsheet documents.
When displaying a spreadsheet document containing pictures in cells or pictures of the Picture type:
  • The AutoSizeIgnoreScale value of the PictureSize property of the spreadsheet document area or the spreadsheet document image is interpreted as the AutoSize value.
  • The RealSizeIgnoreScale value of the PictureSize property of the spreadsheet document region or the spreadsheet document image is interpreted as the ActualSize value.

This change is not implemented in 8.3.15 compatibility mode.

When displaying a spreadsheet document containing pictures in cells or pictures of the Picture type, the system behaved as follows:
  • A picture in a cell for which the PictureSize property was set to AutoSizeIgnoreScale or RealSizeIgnoreScale was not displayed.
  • The height of the line, where there is a cell with a picture, for which the PictureSize property is set to AutoSizeIgnoreScale, was calculated based on the actual picture height.
  • In the Taxi interface, for a spreadsheet document picture of the Picture type, for which the PictureSize property is set to AutoSizeIgnoreScale or RealSizeIgnoreScale, the picture was displayed with a smaller size than it should.
Corrected spreadsheet document pictures display.
Client application form.
The addon menu of the Search management form item contains only the appropriate commands, that is: search by current value, advanced search, search history, cancel search).

This change is not implemented in 8.3.15 compatibility mode.

The addon menu of the Search management form item contained all the commands of the linked form table (similar to autofilling the table command bar). Visibility was turned off for "excess" commands.Eliminated unexpected system behavior.
Full-text search.
Server clusters.
When the UpdateIndex() method of the full-text search manager is called in the client/server infobase mode, preparatory actions are performed using the system background job (its parameters are similar to the system indexing background job). This background job runs on the same working server as the full-text search service. When you click the Refresh Index button of the Full-text search management standard function, the system behavior will be the same.

If a single task is configured in the full-text search settings, it will be performed in a separate background job.

When the UpdateIndex() method of the full-text search manager was called in the client/server infobase mode, preparatory actions were performed at the same computer the method was called from.

If a single indexing task was configured in the full-text search settings, it was performed in a common server execution thread.

Improved reliability and speed of full-text search indexing. All the indexing actions are performed on the working server, assigned for running the full-text search service.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Queries.
Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, an exception is thrown.Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, a number where all digits are 9s is put in the query result.Eliminated unexpected system behavior.
Administration tools.
Implemented Java 9 or later support for the administration server interaction interface from Java.The administration server interaction interface from Java did not support Java version 9 or later. Only Java version 1.8 was supported.Implemented support for modern Java versions.
Software licensing.
When running commands, the licensing utility sends unattended statistical information to 1C:Remote service by default. You can now deactivate this action when running one command using the --send-statistics parameter.The licensing utility did not interact with 1C:Remote service.New feature: you can accumulate statistical information about the licensing utility activity.
Functional options.
If a functional option is stored in a catalog, the functional option value is recalculated once a catalog item is deleted.If a functional option was stored in a catalog, the functional option value was not recalculated once a catalog item was deleted and the code could get the old value of the functional option.Eliminated unexpected system behavior.
Web client.
System requirements.
When running on macOS, Google Chrome and Mozilla Firefox can now be used to work in the web client.When running on macOS, only Safari could be used to work in the web client.The list of supported web browsers for macOS is expanded.
Web client.
System requirements.
Ended support of Google Chrome versions 48 and earlier. The web client is supported in Google Chrome versions 49 and later.Google Chrome versions 48 and earlier were supported.Ended support for legacy Google Chrome versions.
Web client.
On macOS, Google Chrome and Mozilla Firefox now support the file system extension and the add-in extension.

Implemented the add-in adapter library for Google Chrome and Mozilla Firefox running on macOS. Changes were made to development technology for add-ins (read more).

On macOS, Google Chrome and Mozilla Firefox did not support the file system extension and the add-in extension.Advanced file operations on macOS using the web client.
File operations.
The following methods are deprecated and supported for compatibility purposes (in all clent applications):
  • InstallFileSystemExtension()
  • AttachFileSystemExtension()
  • InstallCryptoExtension()
  • AttachCryptoExtension()
  • InstallAddIn().

Use asynchronous equivalents of these methods instead.

The following methods could be used to create applied applications:
  • InstallFileSystemExtension()
  • AttachFileSystemExtension()
  • InstallCryptoExtension()
  • AttachCryptoExtension()
  • InstallAddIn().
Deprecated methods are no longer supported.
File operations.
Once the BeginPutFilesToServer() method or the BeginPutFileToServer() method is called, there is no need to wait for the method completion to call these methods again.Once the BeginPutFilesToServer() method or the BeginPutFileToServer() method was called, it was necessary to wait for completion of a previously executed call to call the methods again. A recall attempt led to an error in the thin client or waiting for completion of the previous call in the web client.You can now import several files (or file groups) at the same time.
Database copies.
You can now choose сonfiguration object properties to be passed to a database copy upon enabled standard replication. You can specify the following objects:
  • For reference objects: attributes, tabular sections, and tabular section attributes.
  • For registers: resources and attributes.

Other attributes (standard attributes, register changes, and common attributes included in separators) are always passed.

A query accessing attributes that are outside of the copy is executed on the main database.

If a database copy created in version 8.3.16 with restrictions on a composition of objects to copy is used, this copy will be considered deprecated when trying to use it on previous versions and refilled with data upon synchronization.

New properties for the DatabaseCopyManager object: TabularSectionsUsage, ValueStoragesUsage, UnlimitedLengthStringsUsage, and OtherFieldsUsage.

The following properties of the DatabaseCopyManager object became writable: DBMSType, DatabaseServer, and Database.

Parameters of the DatabaseCopyManager.Add() method became optional.

New properties for the DatabaseCopyContentItem object: Fields, TabularSectionsUsage, ValueStoragesUsage, UnlimitedLengthStringsUsage, and OtherFieldsUsage.

The DatabaseCopyContentItem.Metadata property became writable. The Item parameter of Insert() and Add() methods of the DatabaseCopyContent object is mandatory. This change is not implemented in 8.3.15 compatibility mode.

The database copy management standard data processor is changed. +

All data of the selected сonfiguration objects was transferred to a database copy upon standard replication usage. It was not possuble to manage properties of data to transfer.

The following properties of the DatabaseCopyManager object were read-only: DBMSType, DatabaseServer, and Database.

Parameters of the DatabaseCopyManager.Add() method were mandatory.

The DatabaseCopyContentItem.Metadata property was read-only. The Item parameter of Insert() and Add() methods of the DatabaseCopyContent object was optional.

When generating data for a database copy, you can now set up content and volume of data stored in the database copy more precisely.
External reports and data processors.
The user will only be checked for having the View right for the data processor/report used when calling GetForm() method of the DataProcessorManager and ReportManager objects. The Use right is no longer checked in this case.

There are no checks for access rights when calling the GetForm() method of the DataProcessorManager and ReportManager objects.

This change is not implemented in 8.3.15 compatibility mode.

When calling the GetForm() method of the DataProcessorManager and ReportManager objects an exception was thrown if the user did not have the Use right for the appropriate data processor or report.Eliminated unexpected system behavior.
Data composition system.
Upgrade: you can apply conditional appearance to header areas of resource and totals fields. Conditional appearance can be managed both from 1C:Enterprise code and the selection form of the conditional appearance application area.

Implemented the following properties for the DataCompositionConditionalAppearanceItem object: UseInResourcesFieldsHeader, UseInOverallHeader, and UseInOverallResourcesFieldsHeader. These properties are not available in 8.3.15 compatibility mode.

This change is not implemented in 8.3.15 compatibility mode.

It was impossible to apply conditional appearance to headers of resource and totals fields.Advanced conditional appearance features for reports built using the data composition system.
Dynamic lists.
On getting data, the dynamic list checks whether all filter fields are present in available filter fields. When the first field unavailable for filter is found, an error is generated.

This change is not implemented in 8.3.15 compatibility mode.

On getting data, the dynamic list did not check whether all filter fields were present in available filter fields.Eliminated unexpected system behavior.
Database operations.
In infobase file mode, unique indexes are created the same way they are created in client/server mode of the infobase.

To force generation of indexes, change the compatibility mode and test and repair the infobase with the Restructure infobase tables check box selected..

When the compatibility mode is disabled, while writing data, index keys will be checked for uniqueness for indexes that were rebuilt upon testing and repair.

Upon testing and repair (in any compatibility mode), index key uniqueness is not checked.

This change is not implemented in 8.3.15 compatibility mode.

In infobase file mode, non-unique indexes of infobase tables were created even when unique indexes were created in other supported DBMSs in the same case.

While writing data, 1C:Enterprise did not check index keys for uniqueness, which could cause problems with infobase migration from file mode to client/server mode.

Unified behavior of 1C:Enterprise in both file and client/server modes for operations with unique indexes. Reduced the number of issues that occur when migrating an infobase from file mode to client/server mode.
Dynamic lists.
When you press Enter (or double-click a row) in a row of a table linked to a dynamic list or when you call the ChangeRow() form table method, a form table extension will open a form linked to this row whether or not there is the Change command in the table commands.

This change is not implemented in 8.3.15 compatibility mode.

When you pressed Enter (or double-click a row) in a row of a table linked to a dynamic list or when you called the ChangeRow() form table method, a form table extension will open a form linked to this row:
  • In version from 8.3.11 to 8.3.15 compatibility mode – only if the Change command is available in the table.
  • In version 8.3.10 compatibility mode – whether or not there is the Change command in table commands.
Eliminated unexpected system behavior.
Information registers.
If a record set of an independent information register is written to the infobase without replacement, records will be checked for uniqueness in data import mode (the DataExchange.Import property is True).

Refined the text of the error that occurs when data is not unique.

This change is not implemented in 8.3.15 compatibility mode.

If a record set of an independent information register was written to the infobase without replacement, records were not checked for uniqueness in data import mode (the DataExchange.Import property was True). This behavior could result in data inconsistency.Eliminated unexpected system behavior.
DBMS operations.
The behavior of the IN query language operator with the subquery became the same when using any DBMS.

The results of such queries using IBM DB2, PostgreSQL, or Oracle Database might change. It is recommended that you analyze usage locations of the IN operator with the subquery and rewrite these queries if necessary.

This change is not implemented in 8.3.15 compatibility mode.

The behavior of the IN query language operator with the subquery depended on the DBMS the query was executed on.The result of the IN query language operator with the subquery does not depend on the used DBMS anymore.

When using PostgreSQL, reduced the time spent on executing queries that contain the IN operator with the subquery.

Queries.
Upon addition or subtraction in the query language, if the left operand of the operation could not be NULL but the right operand could be NULL, it is assumed that the operation result can be NULL.Upon addition or subtraction in the query language, if the left operand of the operation could not be NULL but the right operand could be NULL, it was assumed that the operation result could not be NULL.Eliminated unexpected system behavior.
Server clusters.
In client/server mode, you can now specify roles to apply in a session for a security profile when switching to privileged mode. When privileged mode is enabled, roles specified in the security profile will be used in a session. When privileged mode is disabled, they will return to roles specified by a user. If full access to privileged mode is set in the security profile, a set of roles does not change when privileged mode is enabled.

Implemented the Privileged mode roles property for the security profile.

New properties for the AdministrationSecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. New properties for the ISecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode.

The following Java-based properties are implemented in the administration server interface for the ISecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode.

The following parameters of the profile command are implemented for the cluster service command-line utility (rac): privileged-mode-roles and full–privileged-mode.

Properties AdministrationSecurityProfile.PrivilegedModeAllowed and ISecurityProfile.PrivilegedModeInSafeModeAllowed (server cluster administration COM interface and Java-based administration server interface) are deprecated and supported for compatibility purposes only.

This feature was not provided.

It was impossible to explicitly specify a list of roles that would be applied in a session when switching to privileged mode.

Expanded features of security profiles in client/server mode.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Changed presentation of the following chart properties in the property palette:
  • SmoothingMode
  • SmoothingTension
  • Text
  • AutoSeriesSeparation
  • DonutChartInnerRadius
  • MaxSeriesCount
  • MaxSeriesPercentage
  • AutoSeriesText
  • AutoPointText.
  • Smoothing mode. Continuous histogram smoothing mode.
  • Smoothing tension. Tension of a smooth curved line in points of continuous histograms (0–100).
  • Text. A series text to be displayed in the chart.
  • Automatic sector separation. Separation mode of pie chart sectors.
  • Inner radius.
  • Count. Maximum series to display.
  • Size. Percentage of the absolute maximum values for series to display.
  • Automatic series text. Generating the default text for new series.
  • Automatic point text. Generating the default text for new points.
  • Smoothing mode. Series line smoothing mode.
  • Smoothing tension. Tension of a smooth curved line of series (0–100).
  • Text. A series text to be displayed in the chart.
  • Automatic series separation. Automatic separation mode for series of pie and doughnut charts.
  • Inner radius. Inner radius of a doughnut chart in percent of the outer radius.
  • Maximum series – count. Maximum series to display.
  • Maximum series – percentage. Percentage of the absolute maximum values for series to display.
  • Automatic series text. Generating the default text for new series.
  • Automatic point text. Generating the default text for new points.
Name of system full-text search indexing background job.
  • BackgroundJob.FullTextSearchIndexAdditionalUpdate.
  • BackgroundJob.FullTextSearchIndexUpdate.
Infobase setting in a mobile client with an offline operation mode, which enables working with unstable Internet connection.
  • Bad connection.
  • Expect bad connection.
Methods and events of a client application form.
  • FillWhenReopen() method.
  • BeforeReopen() event handler.
  • OnReopen() event handler.
  • FillWhenReopenFromOtherServer() method.
  • BeforeReopenFromOtherServer() event handler.
  • OnReopenFromOtherServer() event handler.
DatabaseCopyManager object property.
  • ValueStoragesUse.
  • ValuesStoragesUsage.
Properties of objects used to manage charts.
  • DataCompositionResultSpreadsheetDocumentOutputProcessor.AppearanceForValues property.
  • DataCompositionResultSpreadsheetDocumentOutputProcessor.ValueAppearance property.
Image library icon.
  • AppearanceBoxesFourFilled.
  • AppearanceBoxesFilled.
PDFAttachmentRelationshipType system enumeration value.
  • NotSpecified.
  • Unspecified.
PDFModificationAccessPermissions system enumeration value.
  • FillAndSign.
  • FillSignAndAnnotate.
  • FillingSigning.
  • FillingSigningAnnotation

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile client.
The mobile client now supports authentication using OpenID Connect protocol. Authentication uses a system web browser of a mobile device.

Authentication using OpenID Connect is supported for iOS 9.0 or higher devices and Android devices that have Google Chrome installed. +

This feature was not provided.The mobile client now supports authentication that was available in thin client and web client.
Mobile client.
A сonfiguration synonym is not checked for matches when you start the mobile client. The mobile client will be started if a сonfiguration name has not changed since mobile application build and a сonfiguration signature matches its digest.Once a сonfiguration synonym changed, it was impossible to use this configuration with the mobile client application that was built with another synonym (for example, which did not have a synonym in any language).You do not now need to rebuild a mobile application of the mobile client when only a сonfiguration synonym changes.
Mobile client.
Mobile application builder.
Implemented a mobile client with the operating offline feature. This client application allows you to use it both online (as a mobile client) and offline (as a standalone mobile application). Implemented option to switch from online to offline mode and back.

Implemented an offline configuration feature that will be available on the mobile device in offline mode. Offline configuration is a subset of the main configuration. The offline configuration may include all metadata that exists in the platform for a PC. Configuration objects may not be a part of an offline configuration. Configuration extensions cannot be included in an offline configuration.

Implemented the MainServer global context property. Implemented the MainServerAvailable() global context method. Implemented the OnMainServerAvailabilityChange() client application module event. The following is implemented for the ClientApplicationForm object:

  • ReopenFromAnotherServer() and FillWhenReopen() methods.
  • OnMainServerAvailabilityChange, BeforeReopening, and OnReopening events.

Implemented the BehaviorWhenMainServerIsUnavailable property for the input field, button, decoration, and table form elements.

Implemented the OfflineConfigurationContents, OfflineConfigurationRestrictionRoles properties for the Configuration object. Implemented the BehaviorWhenMainServerIsUnavailable property for the common command and common form.

Implemented the form preview in the mobile client mode in offline mode for the client application form editor. Implemented the display of elements and attributes that are not available offline on a mobile device in the client application form editor.

Implemented the feature to perform configuration verification in the offline mobile client mode.

Implemented the feature to specify in which mode the mobile client will be started in Designer settings.

Implemented new debugging items for the debugger.

The mobile application builder allows building a mobile client application with the offline mode feature. +

This feature was not provided.

It was possible to create either a standalone mobile application or a mobile client that worked online.

Expanded the options to build mobile applications using 1C:Enterprise.
Mobile platform.
Mobile client.
Mobile application builder.
Mobile device-specific features.
Implemented the feature to automatically manage mobile application data backup using the mobile operating system. Implemented the Backup using OS tools mobile application permission. The backup is performed as follows:
  • Android - Google Drive service or manually using Android Debug Bridge.
  • iOS - Apple iCloud service.
  • Windows - Microsoft OneDrive service.

The mobile application builder uses this permission to correctly configure the mobile application being built. +

This feature was not provided.Automatic mobile application data backup (without user interaction) is now possible. +
Mobile platform.
Mobile client.
Mobile application builder.
Mobile device-specific features.
Implemented the mobile application permission, which allows you to manage the third-party applications installation. This feature is supported by the mobile application builder when building applications for Android.

Implemented ApplicationInstallation permission.

This feature was not provided.

The third-party applications installation has always been permitted.

If the third-party applications installation is not required for the application, you can reduce the total number of permissions that the mobile application requires when running on Android.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Development tools.
You can now export a configuration which size exceeds 2 GB to a 1Cv8.cf file from Designer. Designer version 8.3.16 and later can only be used to import such configuration.When attempting to export a configuration which size exceeds 2 GB to a 1Cv8.cf file, the upload was interrupted with a confusing error message.Exporting very large configurations to a 1Cv8.cf file is now available.
Data display.
GetStringDeclensions() and GetStringDeclensionsByNumber() methods return a maximum of 10 declension variants of the passed phrase.

This change is not implemented in 8.3.15 compatibility mode.

There was no limit for GetStringDeclensions() and GetStringDeclensionsByNumber() methods of the number of the passed phrase declension variants.GetStringDeclensions() and GetStringDeclensionsByNumber() methods performance has been improved due to decreasing the number of declension variants.
Data composition system.
Dynamic lists.
The data composition layout composer adds ordering from the data composition system settings to the top of the ordering list of data composition layout request.

This change is not implemented in 8.3.15 compatibility mode.

The data composition layout composer added ordering from the data composition system settings to the bottom of the ordering list of data composition layout request.Eliminated unexpected system behavior.
Client application form.
Data display.
When automatically calculating the interface element text color, a more contrasting color relative to the element background color is selected.When automatically calculating the interface element text color, a less contrasting color relative to the element background color was selected.Eliminated unexpected system behavior.
Data accelerator.
The RAM consumption for storing variable-length fields (variable-length strings and value storage) in the Data Accelerator has been reduced.

Execution of some types of queries has been optimized.

Data Accelerator required more RAM to store variable-length fields (variable-length strings and a value storage).

Execution of some types of queries was not optimal.

Data Accelerator has been optimized.
Processing PDF documents.
New feature: digital signature in PDF documents. Embedding of a digital signature visual representation into a document is also available.

Implemented PDFSignatureDescription object. LinkType and ContentType properties are implemented for PDFAttachment object. ContentType and LinkType parameters are implemented for PDFAttachmentCollection.Add() method.

ReadPDF object is now available in the thin client and in the web client. File system extension is required to use web client. The following methods are implemented for the ReadPDF object: CheckSignatures(), CheckSignature(), GetSignatureDescription(), StartOpening(), StartRetrievingAttachments(), StartSignaturesCheck(), StartSignatureCheck(), StartRetrievingSignatureDesctiption(), StartClosing().

WritePDF object is now available in the thin client and in the web client. File system extension is required to use web client. WriteSignature(), StartOpening(), StartWritingAttachments(), StartWritingDeletingAttachments(), StartWritingSignature(), StartClosing() methods are implemented for the WritePDF object.

This feature was not provided.

Creating a separate digital signature file was available.

Expanded PDF documents management capabilities. The document consistency can now be secured after signing.
Client application form.
The OnClose event handler called after the ShutdownSystem (False) method has the Shutdown parameter set to True.

This change is not implemented in 8.3.15 compatibility mode.

The OnClose event handler called after the ShutdownSystem (False) method had the Shutdown parameter set to True in the web client and False otherwise.Eliminated unexpected system behavior.
Global search.
If an error occurred while performing the global search, the search result is placed to the GlobalSearchResultElement object, which has the ErrorDetails object placed to the Value property.

When displaying the results, the error will be shown using the SpecialTextColor style color.

Serialization and XDTO serialization has been implemented for the ErrorDetails object.

Errors that occurred while performing a global search were not displayed to the user.Eliminated unexpected system behavior.
Database copies.
The cases of excessive RAM usage when transferring data to a copy (including the Data Accelerator) have been fixed.Cases of excessive RAM usage were possible when transferring data to a copy.Eliminated unexpected system behavior.
Common attributes / Data separation.
When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the DeleteInfobaseData() method will deem the configuration object to be included in the current area if it is separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters.

It is recommended to analyze using the DeleteInfobaseData() method in the separated configurations and refactor this code, if required.

This change is not implemented in 8.3.15 compatibility mode.

When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the DeleteInfobaseData() method deemed the configuration object to have been included in the current area if it was separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters.The approach to determining the data area using the DeleteInfobaseData() method has been changed.
Mobile platform.
Mobile client.
Improved execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android. The size of mobile applications built for Android has slightly increased.Execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android took more time.Optimized 1C:Enterprise mobile version, running on Android.
Mobile client.
In an offline mobile client, a form that reopens after changing the availability of the main server is reopened with the same set of form parameters as the original form.

The documentation contains the recommendation for generation of the offline mobile client home page.

The -MobileStandalone parameter has been implemented for the CheckConfig Designer batch run command, which allows to check the configuration for using an offline mode.

The -RebuildStandaloneCfg parameter is implemented for the IBCheckAndRepair Designer batch mode run command, which allows to regenerate the offline configuration.

In an offline mobile client, a form that reopens after changing the availability of the main server was reopened with the set of parameters that included the original form key parameters only.Improved offline mobile client running.
macOS.
Linux.
Common objects.
The UniqueID object creates version 4 universal unique identifiers (a completely random universal unique identifier) when used on PCs running Linux and macOS.The UniqueID object created version 1 universal unique identifiers (universal unique identifier dependent on time and network adapter MAC) when used on PCs running Linux and macOS.Enabled using the platform’s built-in features if it was required to pass a version 4 universal unique identifier to an external service during integration and the existing universal unique identifier was not suitable for such transfer.
Dynamic lists.
Full-text search.
The " " (space) character is used as a separator only when breaking into words, which is performed at input by string and at search in a dynamic list. The ".", ",","-", "/" and "\" characters are no longer considered as separators and are searched for as regular characters.

Not only the lines between every two separators, but also the lines from each separator to the end of the line are added to the full-text search index during indexing. +

The ".", ",","-", "/" and "\" characters were used as a separators when breaking into words, which is performed at input by string and at search in a dynamic list.Search as you type and in the dynamic list has become better suited to the user's habits.
Mobile client.
It now supports forced use of main server. Use this feature when you start to fill in the infobase of a mobile client with a standalone mode enabled.

SetPreferableMainServerUse()/GetPreferableMainServerUse() global context methods are implemented.

This feature was not provided. +Now, you can avoid access to a local infobase of a mobile client , when you begin to populate this database.
Mobile platform.
Mobile client.
Now you can manage whether a mobile device can enter sleep when the mobile application is running. New global context methods: SetComputerIdlingToSleepProhibition() and GetComputerIdlingToSleepProhibition().This feature was not provided.Now you can block mobile device idling to sleep, which can make it easier to use the mobile application in some usage scenarios.
Mobile client.
Remember Me check box is available in the mobile client authentication dialog box. If this check box is selected and standard authentication is used (without biometrics), authentication data is saved in the mobile device secure storage.

The following commands of the QR-code designed to add an infobase to a mobile client are now supported:

  • DisableUseBiometrics to hide Use Biometrics check box.
  • UseBiometrics to define the state of Use Metrics check box.
  • DisableRememberMe to hide Remember Me check box.
  • RememberMe to define the state of Remember Me check box. +

The following parameters of the /AddInfoBase command of e1c:// schema are supported:

+

  • DisplayAuthDialog to display an authentication dialog box as soon as you start it for the first time.
  • DisableUseBiometrics to hide Use Biometrics check box.
  • UseBiometrics to define the state of Use Metrics check box.
  • DisableRememberMe to hide Remember Me check box.
  • RememberMe to define the state of Remember Me check box.
These features were not provided.Mobile client start settings are now more detailed.
Full-text search.
During infobase data indexing, if the string does not contain any alphanumeric characters, the full-text search index comprises of substrings from each non-alphanumeric character to the end of the line only if the length of the original string is less than 64 characters.During infobase data indexing, if the string did not contain alphanumeric characters, the full-text search index comprised of substrings from each non-alphanumeric character to the end of the line. As a result, data indexing consumed a big amount of RAM.Eliminated unexpected system behavior.
Mobile client.
When executing a mobile client with the option of standalone mode, the 1C:Enterprise language modules are compiled using the following preprocessor commands:
  • MobileClient on client.
  • MobileStandaloneServer on the standalone server.
  • Server on the desktop server.

You can now find out which server is currently used in a client application form and will be called during a server call. The ClientApplicationForm.CurrentFormServer property is implemented. The GetCurrentServer() global context method is implemented. +The StandardProcessing parameter that defines whether the dialog box with the suggestion to reopen the form will appear is implemented for the OnMainServerAvailabilityChange event handler of the client application form. +The MobileClient value, defining the mode of the mobile client session is implemented for the InfobaseSession.ApplicationName property. The ApplicationPresentation() method now supports the MobileClient parameter value.

When executing a mobile client with the option of standalone mode, the 1C:Enterprise language modules were compiled using the following preprocessor commands:
  • MobileApplicationClient on client.
  • MobileApplicationServer on standalone server.
  • Server on the desktop server. +
Preprocessor commands used to distinguish the client-server interaction methods are now easier to understand when using the mobile client with standalone mode option. +It is now easier to determine which server will be used in the form and called during the next server call from the 1C:Enterprise language. +
Collaboration system.
To deploy your own instance of the collaboration system server, you can purchase a specific software Read more. that doesn't require the CORP license.CORP license was required to deploy a collaboration system server instance.To deploy an instance of the collaboration system server, you have to fulfill one of the conditions:
  • Purchase CORP license.
  • Purchase the 1C:Collaboration server. +
Localization.
Localized client application interface for Armenian (hy).This feature was not provided. +1C:Enterprise is now available for Armenian-speaking users. +
Collaboration system.
When displaying a collaboration system message specified by a formatted string, the navigation links from this formatted string are recognized automatically. If a navigation link has an appearance specified (colour, font, etc.), it will not be recognized. +When displaying a collaboration system message specified by a formatted string, the navigation links from this formatted string were not recognized automatically +Eliminated unexpected system behavior. +
DBMS operations.
When using PostgreSQL DBMS in the client-server mode, the infobase restructuring causes the database structure to change. These changes are required to support PostgreSQL 12.

The change does not affect the application operation.

The database structure did not support PostgreSQL 12 DBMS.The database structure supports PostgreSQL 12 DBMS.
Client application form.
MoveUp and MoveDown commands are now available for the form table linked with data of FormDataCollection or ValueList type with the set row filter.

MoveUp and MoveDown commands are available for multiple rows selection in tables linked with data of the ValueList type.

MoveUp and MoveDown commands were unavailable for the form table linked with data of FormDataCollection or ValueList type with the set row filter.

MoveUp and MoveDown commands were not supported for multiple rows selection in tables linked with data of the ValueList type.

Eliminated unexpected system behavior.
System requirements.
Mobile platform.
Mobile client.
Implemented support for Apple iPhone 11 device family.

Implemented support for iOS version 13.

Apple iPhone 11 device family was not supported.

iOS version 13 was not supported.

1C:Enterprise supports new operating systems and devices.
Internet-enabled functionality.
Now the OAuth2 protocol can be used for emails together with the SMTP protocol. The InternetMailProfile.AccessToken property is used for authentication.The OAuth2 protocol was used for emails for the IMAP protocol only.Now email servers with the OAuth2 authentication protocol are supported if you use SMTP.
Collaboration system.
Now you can take advantage of separate settings of notification sounds for messages and video calls in the dialog box of collaboration system settings.

Notification settings from previous versions apply to messages. Video call notifications are enabled by default.

Video call notifications allow playing sound notifications upon:

  • An incoming call.
  • Ending a call.
  • Awaiting for a contact to accept a call.
Separate settings of notification sounds for messages and video calls were not supported in the dialog box of collaboration system settings.Users can mute or unmute video call notifications and default notifications separately. This will reduce missed video calls.
Collaboration system.
Now you can click Add users to video call to add a new user during a video call. The command is now available:
  • In the Conversations form.
  • In the context conversation form.
  • In the user parameters dialog box.
  • In the video call submenu, in the main window title.
During a video call, you needed to click Start a video call to add a new user:
  • In the Conversations form.
  • In the context conversation form.
  • In the user parameters dialog box.
  • In the video call submenu, in the main window title.
Now the name of the command for adding a new user to a video call is more user-friendly.
Client application.
When using thick and thin clients running Windows, changed the view of titles of independent windows (main application window, calendar window, calculator window, system dialog boxes, and other):
  • In remote desktop (RDP) mode, the operating system title is not displayed.
  • For RemoteApp, the operating system title:
When using thick and thin clients running Windows, independent windows (main application window, calendar window, calculator window, system dialog boxes, and other) were always displayed with the operating system title in remote desktop (RDP) mode or RemoteApp mode.Improved appearance of the application. When using client applications in terminal mode, the application appearance is now more user-friendly.
Collaboration system.
Updated the dialog box of collaboration system settings. Settings specified in the dialog box of collaboration system settings are applied at once without clicking any buttons. Now the button that opens the dialog box is at the top of the Conversations window.

Now the dialog box of collaboration system settings has a button that opens the dialog box of device selection where you can:

  • Select a camera you want to use and test it.
  • Select a microphone you want to use and check its signal level.
  • Select a device you want to use to play audio.

+Now you can open the dialog box of device settings during a video call.

In the web client, the dialog box of device settings is displayed in Google Chrome and Mozilla Firefox only if the web client is published using HTTPS protocol (or at localhost). The publication can access the microphone and camera. In the dialog box of device settings, the list of devices and their names can differ from the list of devices and their names in thin and thick client applications (for the same computer).

The button that opened the dialog box of collaboration system settings was at the bottom of the Conversations window. Settings specified in the dialog box of collaboration system settings were applied after clicking OK. Users could not specify the devices used.Improved collaboration system settings if there are several computer devices that can be used for calls (audio and video calls).
Administration tools.
Client application.
Upgrade: on computers running Windows, users without administrative rights can install the client application ("for user" installation option). The application is installed to %LOCALAPPDATA%\Programs.

With this installation option, 1C:Enterprise server cluster cannot be installed as an operating system service.

You can still install client applications in the "for computer" mode (with administrative rights). The "for user" and "for computer" installation options can coexist. Both lists of installed applications will be used upon client application selection.

+We recommend that you check configurations for explicitly specified directories that store the system. Use the BinDir() global context method instead of explicitly specifying the path. +

On computers running Windows, the client application could be installed only if users had administrative rights or it required users to enter an administrator password if they did not have such rights.Now users without administrative rights can install the client application.
Mobile client.
Collaboration system.
For the mobile client, implemented collaboration system video calls. The mobile device position (in front of the eyes or close to an ear) is considered upon video calls.This feature was not provided.Now you can use collaboration system video calls in the mobile client.
Collaboration system.
If the client application is connected to the client application agent, a notification about an incoming video call is shown even if the client application is not running.

If a user accepts an incoming call, the client application is launched. A video call to callers starts automatically here.

If the client application was connected to the client application agent, a notification about an incoming video call was not displayed if the client application was not running on a computer.Users will receive notifications about incoming video calls when the client application is closed. Previously, such video calls were missed.
Client application installation.
If Windows XP or Windows Server 2003 have Windows installer v3.1, 1C:Enterprise can be installed only in the per-machine installation context (providing that the user is granted the Administrator rights). If Windows XP or Windows Server 2003 have Windows installer updated to v4.5, 1C:Enterprise can be installed in the per-user installation context (if the user is not granted the Administrator rights).If Windows XP or Windows Server 2003 had Windows installer v3.1, 1C:Enterprise couldn't be installed raising the error due to the unsupported installer version.Eliminated unexpected system behavior.
Collaboration system.
The header of the client application includes a menu that accommodates all Collaboration System commands. The menu appears only is the infobase in connected to the Collaboration System.

Some command items are clickable only if their features are available. For example, the video call button is faded if the user's machine has no camera.

The Collaboration System buttons were scattered over the interface.Collaboration System user interface is improved.
Pictures.
Mobile platform.
Mobile client.
Upgrade: 1C:Enterprise mobile version now supports multipage TIFF files, just like the personal computer platform.This feature was not provided.Upgrade: 1C:Enterprise mobile version now supports multipage TIFF files.
Collaboration system.
Improved application stability when using video calls of the collaboration system in thin and web clients.

Changes in the dialog box to set up parameters of the used hardware (the Conversations... menu - the Settings menu item - the Settings button) are applied at once without confirming the change.

Application stability was low when using video calls of the collaboration system in thin and web clients. +Improved application stability when using video calls of the collaboration system in thin and web clients.
macOS.
System requirements.
Updated system requirements for the client application running macOS. The client application is supported only on macOS 10, starting from version 10.12 and later.The system requirements for the client application running macOS were version 10.12 and later.Updated system requirements for the client application running macOS.
Server clusters.
When a working process fails, switching the session to a backup working process takes less time.When a working process failed, switching the session to a backup working process took more time.In the backup cluster, working process emergencies are now less visible to users.
Documentation.
The documentation contains a recommendation for using the HTTPs protocol when working with an infobase engaged in commercial operation.The documentation did not contain a recommendation for using the HTTPs protocol when working with an infobase engaged in commercial operation.The documentation recommends using safer methods of working over the Internet.
Regional settings.
Upgrade: in accordance with the Federal Law of the Russian Federation No. 432-FZ, a new time zone is applied for Volgograd oblast. The update is applied to all 1C:Enterprise system components, except for the web client. The web client sets the time in accordance with the time zone information provided by the operating system and web browser. +1C:Enterprise ignored the changes introduced by the Federal Law of the Russian Federation No. 432-FZ.New time zone settings are applied due to the legislation change.
Processing PDF documents.
Spreadsheet document.
For a PDF document, it is now possible to insert an arbitrary image or a spreadsheet document in a specified PDF document area.

New object: DetailsOfPDFObjectToDisplay. New methods for the WritePDF object: WriteObjectToDisplay() and WriteObjectToDisplayAsync().

This feature was not provided.Advanced PDF document features.
Client application.
Client application installation.
Web client.
Platform files and extension files for web browsers, and distribution packages used in Windows are signed only with the SHA256 algorithm.

With Microsoft Internet Explorer (when running Windows XP, Windows Vista, Windows Server 2003, or Windows Server 2008), enable the option to load and attach unsigned add-ons.

We recommend that you use Windows 7 and later (including the web client) to work with 1C:Enterprise.

Platform files and extension files for web browsers, and distribution packages used in Windows were signed with SHA1 and SHA256 algorithms.The outdated and insecure SHA1 cryptographic hash algorithm is no longer supported.
Client application.
Administration tools.
Now you can choose an installation mode for 1C:Enterprise: for all users or for the current user. This feature is implemented both in the interactive mode and as command-line parameters/configuration file parameters.

New InstallForUsers parameter for 1cestart.cfg configuration file. New ALLUSERS command of the startup command line for the setup.exe utility.

The client application installation mode was selected only by the current user access rights. Even when a user knew the administrator password, the installation for all users could be started only when the setup.exe utility was run under an administrator.Simplified 1C:Enterprise platform administration. You can select an installation mode for the client application as required by the current administration policies.
System requirements.
DBMS operations.
The system now supports Postgres Pro DBMS of the following versions (only for x86-64):
  • Postgres Pro 1C 9.6.24.1
  • Postgres Pro 1C 10.19.1
  • Postgres Pro 1C 11.14.1
  • Postgres Pro Standard 9.6.24.1
  • Postgres Pro Standard 10.19.1
  • Postgres Pro Standard 11.14.1
  • Postgres Pro Enterprise 9.6.24.1
  • Postgres Pro Enterprise 10.19.1
  • Postgres Pro Enterprise 11.14.1
These DBMS versions were not supported.

+

Extended list of supported DBMS.

Table of contents

Transition from the previous version to the version 8.3.16

Table of contents

Version 8.3.15

Version 8.3.15 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.14 is now implemented.Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.13 was available.Configurations developed using 1C:Enterprise platform version 8.3.14 or earlier can now run on version 8.3.15 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.15 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.14 after the migration to version 8.3.15, even if you disable the compatibility mode (simply enable it again).
1C:Enterprise script.
If some errors occur, a stack of calls leading up to the error (not related to nested exceptions) is now displayed in detailed error description. +In 1C:Enterprise Development Tools, call stack navigation is now available.If an error message occurred, detailed error description did not include a call stack leading to the line with error (except for nested exceptions).Improved diagnostics of application errors.
Internet-enabled functionality.
Administration tools.
Event log.
Implemented two-factor authentication. +New data for event log events: _$Session$_.Authentication, _$Session$_.AuthenticationError, _$User$_.New, _$User$_.Update. +Implemented the following event log events: _$Session$_.AuthenticationFirstFactor, _$InfoBase$_.SecondFactorAuthTemplateNew, _$InfoBase$_.SecondFactorAuthTemplateUpdate, _$InfoBase$_.SecondFactorAuthTemplateDeleteThis feature was not provided.Expanded user authentication options. More secure user authentication is available now.
Charts.
Data composition system.
New feature: doughnut and 3D doughnut charts. +New properties for the ChartType system enumeration: Donut and Donut3D. +Implemented the +Chart.DonutChartInnerRadius property. +Implemented the ChartType.DonutChartInnerRadius parameter for the following objects: DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance. This feature was not provided.New chart features.
Spreadsheet documents.
Now you can specify a formatted string as a spreadsheet document header or footer. +Included the FormattedString type in types of the following properties of the SpreadsheetDocumentHeaderFooter object: LeftText, CenterText, and RightText. +With an editor of spreadsheet document headers and footers, you can edit a formatted string. When you start editing the relevant field with the header or footer text, the check box of output of the relevant header or footer to the spreadsheet document is selected automatically. Upon exporting a spreadsheet document, formatting of headers and footers is saved in the following formats: PDF (*.pdf), Microsoft Office OpenXML (*.xlsx and *.docx), Microsoft Excel (*.xls), and Open Document Spreadsheet (*.ods). +For more information on how to use a formatted string for displaying headers and footers, see 1C:Enterprise documentationThis feature was not provided.Expanded spreadsheet document export features.
Spreadsheet documents.
New feature: you can save a spreadsheet document to PDF/A-1 (a format for long-term storage). When you save to PDF/A-1 format, remember the following:
  • Document is written as PDF 1.4.
  • Duplex printing is not supported.
  • Transparency is not supported.

Implemented the SpreadsheetDocumentFileType.PDF_A_1 system enumeration value.

This feature was not provided.Expanded spreadsheet document export features.
macOS.
Collaboration system.
Client applications running under macOS now support collaboration system video calls.This feature was not provided.Implemented collaboration system features under macOS.
Data composition system.
New feature: you can save changes upon closing a form for the report settings form and the form for editing a report option. User prompt is generated before saving. The upgrade is valid only if the StandardProcessing parameter of the BeforeClose form event handler is set to True.This feature was not provided. +Upon closing the form, changes in the form were lost.Reduced risk of losing changes made in the report settings form or the report option form in case of incorrect closing of the editing form.
Database copies.
Information registers.
Accumulation registers.
Standard functions.
New feature: you can transfer not all register data but data only for a specific period to a copy for information registers and accumulation registers. This feature is available only for a standard replication. +New property: DatabaseCopyContentItem.Filter. +New feature for the Database copy management standard data processor. You can set filter by a period for information registers and accumulation registers. +New feature: upon defining the query place, you can analyze a period condition in addition to the existing checks.This feature was not provided.Extended database copy management features. Improved performance of the database copy management feature by reducing data passed to a copy.
Database operations.
Common attributes / Data separation.
New feature: you can get the data size that this data occupies in DBMS tables (including a specific data area). Upon calculating the size, the size of data history, extensions, and platform service tables (indexes, etc.) is not considered. +New global context method: GetDataBaseDataSize().This feature was not provided.New feature: you can estimate the size of data available in a database area or table.
Configuration extensions.
New feature: you can mark a managed extension property so that a mismatch of this property in the extended configuration and in the extension will not block the extension use, but a user will get a message stating that the property value in the extension and the property value in the extended configuration do not match.This feature was not provided.New feature: informing of changes of some extended configuration properties is available. Changing such properties does not block extension use, but this change must be processed by the extension developer separately.
Configuration extensions.
Development tools.
New feature: you can map extended configuration objects and extensions by IDs. Implemented the feature helping to resolve conflicts upon rename conflicts. +Mapping objects by IDs can be disabled. +New property for the configuration extension: Support mapping to extended configuration objects by internal IDs. New property for adopted extension objects: Extended configuration object.Extended configuration objects and extensions were mapped only by names.Simplified diagnostics of renaming an extended configuration object adopted to an extension. Now there is a feature for resolving conflicts upon such rename.
Configuration extensions.
Upon creating a new extension, the Compatibility mode extension property is no longer a managed property.Upon creating a new extension, the Compatibility mode extension property was a managed property.Simplified development and applicability of extensions.
Data display.
New pictures are added to the picture library: Notify, DontNotify, DontDisturb, and SendMessage.The listed pictures were not available in the picture library.The picture library is upgraded.
Configuration extensions.
New feature: you can adapt extended configuration methods. An extended method is fully copied to an extension where changed code is enclosed by preprocessor directives. +During application, it is checked whether the extended method is not changed in relation to the method in the extension. +New annotation: ChangeAndValidate. New preprocessor directives: Delete and Insert. +You can change one method only in one extension. If two extensions that extend the same method using the ChangeAndValidate annotation are found, only one extension will be applied to the infobase. +If a method change in the extended configuration is found, three-way merge using an external application only is available. If an external application for comparing and merging modules is not configured in Designer, merge will be unavailable.Making changes to the method with control of module source code consistency was unavailable.Simplified extended configuration method extension if a small method change is required.
Web client.
When you start the web client on mobile devices, there is no message prompting that the used web browser version is not supported. New feature: partial support of the web client on mobile devices. Full support of the web client on mobile devices is not implemented.

Fixed problems that occur in the web client on mobile devices in main scenarios.

Web client was supported on iPad tablets only.Web client is partially available on mobile devices.
Common objects.
New feature: upon solving a system of linear equations, you can search for connected components of various types for graphs built based on a system of linear equations. +Implemented the ComponentsGetMethod parameter of the SolvingLinearEquationsSystems.GetConnectedComponents() method. In 8.3.14 version compatibility mode, this parameter value will be StronglyConnectedComponentsWithoutLinkRequirementWithinComponents.This feature was not provided.Advanced features for solving a system of linear equations.
Collaboration system.
New link to collaboration system messages.

Implemented the CollaborationSystemStandardCommand.GetMessageURL system enumeration value.

This feature was not provided.Now you can obtain links to specific collaboration system messages.
Managed forms.
New feature: a flag field of a client application form can be displayed as an off-on switch. New property of the CheckBoxType.Switch system enumeration. +In version 8.3.7 or earlier compatibility mode and in platform version earlier than 8.3.15, the CheckBoxType property value set to the Switch value is the Auto value.This feature was not provided.Extended system presentation features.
Managed forms.
The client application displays a text document, a spreadsheet document, a graphical schema, and a picture in the client application system form. This is available in the following cases:
  • When you create or open a document using the File menu.
  • When you call the Show() method of the relevant 1C:Enterprise language object or the ShowValue() method for the Picture type object.
  • When you drag a file from the operating system.
  • When you open a collaboration system attachment.

A form with a displayed spreadsheet document or graphical schema has a command bar making editing of the relevant document easier. +New events for a form field extension for a spreadsheet document, a text document, and a graphical schema: BeforeWrite, AfterWrite and BeforePrint. +This change is not implemented in version 8.3.14 compatibility mode.

The client application displayed a text document, a spreadsheet document, a graphical schema, and a picture in special forms. Such forms did not have command bars.Editing platform documents is now more convenient and intuitive. You can now process saving and printing of a text document, a spreadsheet document, and a graphical schema.
Managed forms.
Implemented the option to manage the command home position in the command bar: +
  • In the More actions menu only.
  • In command bar only.
  • Both (a command bar and the More actions menu).
  • Determine automatically.

New form button property: LocationInCommandBar. +The OnlyInAllActions form button property is deprecated and supported for compatibility purposes only. Implemented automatic filling of the LocationInCommandBar property based on the OnlyInAllActions property. +Now this mode is available for the client application form button when there is no more than one button linked to one command inside the automatically filled group. +New client application button property: CommandUniqueness. +New property for the picture field extension and the Picture kind decoration: Scale. This property is ignored in version 8.3.6 or earlier compatibility mode.

For a client application form command, only an indication that a command was located either in the command bar or in the More actions menu was available.Improved options for creating command interface of the client application form.
Data display.
New pictures are added to the picture library: ZoomOut and ZoomIn.The listed pictures were not available in the picture library.The picture library is upgraded.
Managed forms.
The following features are available for the Planner object:
  • Control of planner item representation if there is not enough space in the field: show all items by changing the line height or saving the line height, and show the More actions menu. Implemented the Planner.ItemsBehaviorOnLackOfSpace property.
  • You can set the minimum column height and width of the planner. As a result, instead of constant reduction of planner items, it will be possible to save the minimum item size and add a scroll bar if items do not fit the form field. New properties for the Planner object: ColumnMinWidth, AutoColumnMinWidth, RowMinHeight, and AutoRowMinHeight.
  • Freeze a dimension title and a time scale of the planner. Fixed objects will be visible for a user upon scrolling the planner. New properties for the Planner object: FixDimensionsHeader and FixTimeScaleHeader.
These features were not provided.New planner features.
Collaboration system.
New feature: you can define a list of selecting collaboration system users upon creating a context conversation message, a noncontext conversation message, or a video call. You can now create a form of selecting collaboration system users. +New event for the ClientApplicationForm object and client application module: CollaborationSystemUserAutoComplete. +New event for the ClientApplicationForm object and client application module: CollaborationSystemUserChoiceFormGetProcessing. +New сonfiguration property: DefaultCollaborationSystemUserChoiceForm. +You can now get a context conversation ID in the client application form (on the client application side). Implemented the BeginGettingConversation() method.There was no option to override a list of selecting collaboration system users upon selecting a user. +Earlier, you could get a context conversation ID on the server side only.New collaboration system operations for selecting users upon creating messages, conversations, and video calls.
Interface.
Updated the Taxi interface. New appearance includes the following main changes:
  • Main application window (running under Windows) has no title by default.
  • Created the main panel containing access to primary tools of the command interface.
  • Tools panel commands are reallocated between other interface items.
  • The tools panel is no longer available as a separate panel.
  • The system command bar is no longer available.
  • Changed the main menu components and location.
  • Changed the appearance of auxiliary windows and dialog boxes.
  • Created a global search bar displayed in the main panel of the main application window. Global search bar is unavailable in the following main window modes: kiosk, workplace, and full-screen workplace. You can set up search behavior using 1C:Enterprise language. Implemented the GlobalSearch global context property. New application module events: OnGlobalSearch and OnGlobalSearchResultChoice.
  • New feature: using the search bar, you can open a link, an external resource URL, perform arithmetic operations, and so on.
  • New command Search everywhere in the context menu of some form items (with supported selection). The search is carried out using the search bar.
  • New Get link button in the auxiliary window title.

Implemented the StrFindAndHighlightByAppearance() global context method that allows you to highlight some substrings in the string.

The ClientApplicationInterfaceContentSettingsItem object cannot be created for the ToolsPanel panel. The tools panel is ignored in the settings of the main application window panels.

New methods for the ClientApplication object: GetOSTitleRepresentation() and SetOSTitleRepresentation().

The Default search form сonfiguration property is deprecated. We recommend that you use global search feature instead. +

The Taxi interface had different appearance.Improved application navigation, increased usability, and developed the interface in accordance with modern trends in interface creation.
Spreadsheet documents.
Upon editing spreadsheet document headers and footers, automatic calculation of the page field size is available now if the specified header or footer cannot be placed in the current page field sizes. To calculate the size, click Ok in the headers and footers editing form and page parameter setting form. +New feature: you can get the header or footer size. New feature: you can get the page field size. +New methods for the SpreadsheetDocument object: CalculateHeaderSize(), CalculateFooterSize(), GetPrinterTopMarginSize(), GetPrinterBottomMarginSize(), GetPrinterLeftMarginSize(), and GetPrinterRightMarginSize().This feature was not provided. +Earlier, you could pick the size of fields, headers, and footers only manually or iteratively.New feature: spreadsheet document page fields can be set automatically according to the specified header or footer.
Full-text search.
Implemented search by meaningful word parts. In search results, a word is now highlighted if it has a meaningful part. +New feature: you can specify meaningful word parts in user dictionaries of full-text search. New item for a description file of a user dictionary of full-text search: <Roots>. +To enable search by meaningful word parts, rebuild a full-text search index. +It works automatically if the Russian language is selected in regional infobase settings or a user dictionary of full-text search with a list of meaningful word parts is specified for the infobase. +New methods for full-text search manager: GetSeparationOfCompositeWordsMode() and SetSeparationOfCompositeWordsMode().This feature was not provided.Improved full-text search usability.
Dumping configurations to files/Restoring configurations from files.
If you need to dump configuration information (the DumpConfigToFiles command of Designer batch mode) in a file with objects to dump (the listFiles dump command parameter), specify the Configuration ID. There is no need to specify a configuration name.If you needed to dump configuration information (the DumpConfigToFiles command of Designer batch mode) in a file with objects to dump (the listFiles dump command parameter), you needed to specify the Configuration ID and a configuration name (dot-separated).Simplified configuration dump to XML files.
Collaboration system.
Now you can block a collaboration system user. A blocked user cannot interact with the collaboration system. Now you can determine a linked infobase user by a collaboration system user.

New properties for the CollaborationSystemUser object: IsLocked and InfoBaseUserID. Implemented the GetUsers() method for the collaboration system manager.

Standard data processor of collaboration system management supports blocking and unblocking of collaboration system users. +

These features were not provided.New operations with collaboration system users. Now you can disable a user from the collaboration system, for example, if a user is fired.
Data display.
New pictures are added to the picture library: ExclamationDialog, QuestionDialog, StopDialog, and InformationDialog.The 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

FunctionalityAfterBeforeResult of changes
Dynamic lists.
Managed forms.
Typing a text in a form table linked to a dynamic list does not lead to an input focus change and search start if the following conditions are met: +
  • Form item addition Search bar is available in the form.
  • For the form table, the Search upon character input property is set to Do not use.

This change is not implemented in version 8.3.14 compatibility mode.

Typing a text in a form table linked to a dynamic list led to an input focus change and search start if the following conditions are met:
  • Form item addition Search bar is available in the form.
  • For the form table, the Search upon character input property is set to Do not use.
Eliminated unexpected system behavior.
Standard functions.
For the Active users standard function, the list update button is moved to the beginning of the list form command bar.For the Active users standard function, the list update button was located at the end of the list form command bar.Unified list update command location in various forms of standard functions.
Standard functions.
Server clusters.
New standard function: Server management. This function is similar to the cluster management console. It requires a server cluster administration server for all servers to be administered. Server operations are carried out using the ServerAdministration object. For a list of functional differences between the standard function and the cluster console, see 1C:Enterprise documentation. The standard function system requirements are the same as the system requirements of the ServerAdministration object.This feature was not provided. +Interactive server cluster administration was available from the cluster management console only.Interactive server cluster administration is now available not only under Windows. Cluster administration tools are available in the client application using the All functions dialog box.
Standard functions.
Data history.
Implemented the standard function that allows you to view data history, set an arbitrary filter, and update data history interactively.Viewing data history of a certain data object only was available in the platform. Custom filter setup to view history was unavailable.Extended interactive data history operations.
Managed forms.
Interface.
Collaboration system.
Upon form scaling, the scale is shown on a logarithmic scale. 100% value is in the middle of the scale. +New feature: you can click a middle button to:
  • Close search state items (in a dynamic list).
  • Remove recipients from collaboration system context conversations.
  • Remove attachments from unsent collaboration system messages.
Upon form scaling, the scale was shown on a linear scale. 100% value was at the beginning of the scale. +You could close search state items (in a dynamic list), remove recipients from context conversations of the collaboration system, and +remove attachments from unsent messages of the collaboration system only using the required object control (X in the right part of the item).Improved application interface usability.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Queries.
New feature: the query language now has optimized calculations of expressions being virtual table parameters. This optimization is similar to optimization of standard query language expressions. +This change is not implemented in version 8.3.14 compatibility mode.The query language did not have optimized calculations of expressions being virtual table parameters.Eliminated unexpected system behavior.
Linux.
Optimized use of RAM on Linux.RAM was used less effectively on Linux.Decreased RAM fragmentation and, as a result, decreased the amount of used RAM on Linux. Slightly improved application performance.

+

Queries.
Server clusters.
Optimized execution of a query containing constant values in the selection list. Constant values from the query body are implemented by query parameters. This reduces the amount of plan recompilation in DBMS and, as a result, improves performance of the same queries if only their constant value is different. +This feature was not provided.

Constant values were not used by parameters and were used directly in the query body.

Execution time of queries containing constant values is reduced in some cases. In particular, recalculation of register totals can take less time in client/server mode.
Managed locks.
Improved performance of the managed lock manager upon transaction completion if there are a lot of transactions that locked the key range of one space.The managed lock manager spent more time on transaction completion if there were a lot of transactions that locked the key range of one space.Parallel operation is improved in case of similar load generated by numerous sessions.
Configuration comparison and merging.
Optimized comparison/merge of configurations.Comparison and merge of configurations took more time.Comparison and merge of configurations is now faster.
Queries.
If the query text contains a condition with two constant expressions and each expression is not a string, the condition will be replaced with an expression result before passing the query to DBMS.

+

This change is not implemented in version 8.3.14 compatibility mode.

Conditions which consisted of constant expressions were not simplified.In some cases, query performance is improved.
Binary data.
Buffers used with objects of the FileStream type are reset only if the FileStream.ResetBuffers() method is executed explicitly.Buffers used with objects of the FileStream type were reset:
  • Upon executing the FileStream.ResetBuffers() method explicitly.
  • Upon calling the FileStream.Close() method.
  • Upon deleting the FileStream object.
Decreased load on a disk drive upon intensive operations with the FileStream type objects.
Data composition system.
Improved performance of the Value() function of the data composition system expression language. The Value() function of the data composition system expression language worked more slowly.Improved performance of the Value() function of the data composition system expression language.
DBMS operations.
Queries.
Upon query execution, faster creation of a temporary table from a value table passed as a query parameter is available now.Upon query execution, creation of a temporary table from a value table passed as a query parameter took longer time.Upgrade: faster creation of a temporary table based on a value table using the query language.
Client application installation.
System requirements.
Removed Microsoft VC++ Runtime Redistributable Package from thin client distribution package (for Windows).Microsoft VC++ Runtime Redistributable Package was inside thin client distribution package (for Windows).Reduced thin client distribution package for Windows.
System requirements.
Removed Microsoft Windows Installer 3.0 Package from platform distribution package (for Windows).Microsoft Windows Installer 3.0 Package was inside platform distribution package (for Windows).Reduced platform distribution package for Windows.
Data composition system.
Composer of data composition system template considers to be used only those fields that are used in the conditional appearance item of data composition only when this conditional appearance item is applied at least to one of the displayed fields (also upon applying conditional appearance to all fields). If conditional appearance item is not applied to any field, used fields are considered to be unused and are not added to the resulting query of the data composition template. +Fields, which are not used in conditional appearance, are not added to the data acquisition query. +This change is not implemented in version 8.3.14 compatibility mode.Composer of data composition system template considered to be used all fields in conditional appearance item even if this conditional appearance item was not applied to any field. +All fields, which were formally used in conditional appearance, were added to the data acquisition query.Improved generation of the query of data composition system data acquisition.
Queries.
If a query with merges contains a false condition, the part of the merge with the false condition is not passed to DBMS. False conditions are detected only for Number or enumeration data type. +Upon merge optimization, the platform can, if necessary, add a requirement for obtaining different records to the resulting query. +This change is not implemented in version 8.3.14 compatibility mode.This feature was not provided.In some cases, query time will be decreased.
Server clusters.
Improved client connection transfer to a new working process upon automatic restart of the working process.Client connection transfer to a new working process upon automatic restart of the working process took more time.Transfer of existing sessions to a new working process now takes less time. Decreased (or totally eliminated) client application delay upon transfer. Significantly improved client application operation in interactive mode in this case.
Accounting registers.
Improved performance of virtual tables of the accounting register, updated totals upon writing register records, and recalculated accounting register totals. +Increased stored data volume and slightly increased record set storage time. +To make accounting register performance increase noticeable, disable the compatibility mode. Accounting registers will be restructured. If infobase size exceeds 10 GB, it is recommended that you use optimized tool of database configuration update for restructuring. +This change is not implemented in version 8.3.14 compatibility mode.Operations with virtual tables of accounting register, update of totals upon writing register records, and recalculation of accounting register totals took more time.Data acquisition from accounting registers is faster now.
Accounting registers.
Queries.
Improved query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: Recorder IN (subquery). +This change is not implemented in version 8.3.14 compatibility mode.Query to accounting register if the query contains a condition of including the recorder in a list generated under a subquery: Recorder IN (subquery), poor performance.Improved data acquisition from the accounting register in some cases.
Queries.
If you execute a query in the infobase file mode with data from two tables and these tables are connected with an internal connection and there are indexes of link fields in both tables, then the first iteration is performed for the table with less records.Number of records in tables was not analyzed upon executing a query in the infobase file mode with data from two tables and these tables were connected with an internal connection and there were indexes of link fields in both tables.In some cases, improved query performance in the infobase file mode.
Data composition system.
Improved generation of data composition system template if a data composition schema query contains a lot of unions (400 or more unions).Generation of data composition system template took a significant amount of time if a data composition schema query contained a lot of unions (400 or more unions).Improved performance of the data composition system if there are a lot of unions in a data composition schema query.
Server clusters.
DBMS operations.
Upgrade for PostgreSQL DBMS: better posting of large documents in the accounting register and improved RecordsWithExtDimensions virtual table.Posting of large documents in the accounting register and operations with the RecordsWithExtDimensions virtual table took more time if PostgreSQL DBMS was used.Optimized use of the accounting register if PostgreSQL DBMS is used.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult 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.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Data composition system.
Composer of data composition template does not use the presentation expression specified for the calculated field upon generating an expression of group and total records for calculated fields being resources. Thus, the presentation expression for calculated fields being resources will be displayed in the report in detailed records only. +This change is not implemented in version 8.3.14 compatibility mode.Composer of data composition template used an expression of the calculated field presentation being a resource in detailed, group, and total records.Behavior of composer of data composition template is the same for calculated fields, data set fields, and calculated resource fields.
Queries.
Data composition system.
Right joins are not replaced automatically with similar left joins upon processing query text with the query constructor, query scheme, data composition system, and report builder. +This change is not implemented in version 8.3.14 compatibility mode.Right joins were replaced automatically with similar left joins upon processing query text with the query constructor, data composition system, and report builder. If conversion failed to be performed, the connection was removed from the query.Eliminated system behavior which could lead to an incorrect query.
File operations.
Web client.
Implemented the BeginGetFileFromServer() and BeginGetFilesFromServer() global context methods. In the interactive mode, methods do not require installing a file system extension on web client. New feature: you can get several files from the server as an archive. +The BeginRequestingUserPermission() method allows you to request user permission for new methods. +The GetFile(), BeginGettingFiles(), and RequestUserPermission() methods are deprecated and supported for compatibility purposes. +It is recommended that you use new methods in the application.Current methods of receiving files from the server were not logical. Method of receiving several files from the server (BeginGettingFiles()) in the web client required a file system extension.Getting files from the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode.
File operations.
Web client.
Implemented the BeginPutFileToServer() and BeginPutFilesToServer() global context methods. In the interactive mode, the methods do not require installation of a file system extension on web client. New feature: displayed progress of placing a file to the server. New feature: cancel placing a file to the server. New feature: simultaneous transfer of several files from a client computer to the server. Files being transferred are specified using the file search string.

The BeginRequestingUserPermission() method allows you to request user permission for new methods.

The BeginPutFile(), BeginPuttingFiles(), and RequestUserPermission() methods are deprecated and supported for compatibility purposes.

It is recommended that you use new methods in the application.

Existing methods of transferring files to the server (BeginPutFile(), BeginPuttingFiles()) did not allow to cancel placing files during transfer and display the transfer progress.Putting files to the server is now more transparent and convenient. Now a file system extension is no longer required to use the web client in the interactive mode.
Database operations.
Common attributes / Data separation.
1C:Enterprise script.
Method FindMarkedForDeletion() will search all available objects of the current data area only if the Undefined value is passed as a value of the first and the second method parameters. +This change is not implemented in version 8.3.14 compatibility mode.Method FindMarkedForDeletion() searched all available objects of the current data area only if the Undefined value was passed as a value of the first method parameter only.Unified set of parameters and behavior of methods with similar actions.
Queries.
Query language behavior changes if: query is a merge of several queries, which are applied to a unified query and each merge query uses the TOP keyword. In this case, each query in the merge turns into a nested query with ordering. If any of the nested query does not have the TOP keyword, subquery is not built by ordering. +It is recommended that you analyze when queries that meet these conditions are used. When the compatibility mode is disabled, performance result of such queries can be different from the performance result of this query in compatibility mode. +This change is not implemented in version 8.3.14 compatibility mode.Query language behavior if: query was a merge of several queries, which were applied to a unified query and each merge query used the TOP keyword, depended on the infobase option: +
  • For file mode: first ordering, then selection of top records.
  • For client/server mode: first selection of the top ones (for each simple query). Ordering was not executed for simple queries. Ordering was executed only for merge result. Result repeatability was not guaranteed as the top items were selected from the query without ordering.
Implemented similar behavior of a query containing merge, ordering, and the TOP keyword in various infobase mode options.
Server clusters.
Upon editing a server cluster resource consumption counter, the counter is reset only if the Group property is changed.

Implemented reset of a resource consumption counter instance:

  • The Delete command is implemented for a resource consumption counter instance.
  • The clear command is implemented for the rac counter command.
  • The IAgentAdminConnection.clearAccumulatedValues() method is implemented for Java interface of server cluster administration.
  • The AdministrationResourceConsumptionCounter.ClearAccumulatedValues() method is implemented in 1C:Enterprise language.

Now you can get a list of resource consumption counter values:

  • The accumalated-values command is implemented for the rac counter command.
  • The IAgentAdminConnection.getAccumulatedResourceConsumptionCounterValues() method is implemented for Java interface of server cluster administration.
  • The AdministrationResourceConsumptionCounter.GetAccumulatedValues() method is implemented in 1C:Enterprise language.

For a resource consumption counter instance, a field containing measurement time is implemented. To get measurement time:

  • The time property is implemented in the rac counter command output.
  • The IresourceConsumptionCounterValue.getTime() method is implemented for Java interface of server cluster administration.
  • The AdministrationResourceConsumptionCounter.Time property is implemented in 1C:Enterprise language.
Upon editing a server cluster resource consumption counter, the counter was reset if any of its properties were changed.

Other features were not provided.

Improved administration of server cluster resource consumption. Simplified setting of counters and resource consumption restrictions. Now you can analyze changes of accumulated data.
Data composition system.
Functional options.
In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check includes checking that the field is not disabled with a functional option. +This change is not implemented in version 8.3.14 compatibility mode.In the data composition system, for the field separated by dot from the temporary table field or nested query, availability check did not include checking that the field is not disabled with a functional option. If a temporary table field or a nested query field was available, it was considered that all fields available via "." (dot) would also be available.Eliminated unexpected system behavior.
Data composition system.
Charts of characteristic types.
In the data composition system, a characteristic value type is considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). If a value, which does not match the used characteristic value type, is written in the infobase, then NULL will be used instead. +It is recommended that you analyze additional characteristics in the data composition system and make sure that the actual characteristic value type matches the type. +This change is not implemented in version 8.3.14 compatibility mode.In the data composition system, a characteristic value type is not considered upon getting a characteristic value (for any purpose, for example, sorting or filtering by it). Even if a value, which does not match the used characteristic value type, is written in the infobase, it will be used.Improved performance of the data composition system with additional characteristics (charts of characteristic types) by reducing the number of tables used in queries.
Server clusters.
Changed rules and settings of 1C:Enterprise server cluster monitoring system. Optimized use of server RAM. In particular, both working process parameters and cluster manager parameters are used when determining the amount of used memory.

New feature: server cluster setting, which allows you to specify whether a process dump is to be created when critical memory amount is exceeded.

New feature: working server properties that describe a temporarily allowable amount of process memory, a time interval that describes exceeding time of a temporarily allowable amount of process memory, and a critical memory amount.

The following settings are removed from the cluster properties:

  • Allowed total memory.
  • Period of exceeding the memory threshold.
  • Threshold of server error variation.

Settings that describe the amount of working process memory up to which server performance is considered to be sufficient, and the maximum working process memory are removed from the working process properties.

However, the removed parameters will be saved in the cluster settings and used in a previous version of 1C:Enterprise.

If you create a new cluster, some parameters will have the following default values:

  • Force close corrupted processes – enabled.
  • Close corrupted processes in 60 seconds.

Upon creating a new working server, 256 connections per process will be established by default.

If the removed parameters are changed in the cluster settings, it is recommended that you review the cluster settings and adjust them if necessary.

Implemented the following objects:

  • AdministrationCluster.WriteDumpWhenTerminatingByMemoryLimit property.
  • TemporaryAllowedProcessesTotalMemory property for CriticalProcessesTotalMemory object, and TemporaryAllowedProcessesTotalMemoryExcessTimeLimit property for the AdministrationWorkServer object.
  • IClusterInfo.KillByMemoryWithDump property.
  • CriticalProcessesTotalMemory, TemporaryAllowedProcessesTotalMemory, and TemporaryAllowedProcessesTotalMemoryTimeLimit properties for the IWorkingServerInfo object.

The following Java-based tools are implemented in the administration server interface:

  • IsClusterRecyclingKillByMemoryWithDump() and setClusterRecyclingKillByMemoryWithDump() methods of the IClusterInfo interface.
  • GetCriticalProcessesTotalMemory(), setCriticalProcessesTotalMemory(), getTemporaryAllowedProcessesTotalMemory(), setTemporaryAllowedProcessesTotalMemory(), getTemporaryAllowedProcessesTotalMemoryTimeLimit(), and setTemporaryAllowedProcessesTotalMemoryTimeLimit() methods of the IWorkingServerInfo interface.

For the cluster service command-line utility (rac):

  • Implemented the kill-by-memory-with-dump field for the cluster info command output.
  • Implemented the kill-by-memory-with-dump parameter for the following commands: cluster update and cluster insert.
  • Implemented the following command-line parameters for server insert and server update commands: critical-total-memory, temporary-allowed-total-memory, and temporary-allowed-total-memory-time-limit.

The following properties are deprecated and supported for compatibility and interaction with previous cluster versions:

  • ProcessMemoryLimit, MaxMemoryTimeLimit, and ProcessErrorCountLimit properties of the AdministrationCluster object.
  • MaxMemorySize, MaxMemoryTimeLimit, and ErrorsCountThreshold properties of the IClusterInfo object. +
Server cluster monitoring logic was different. Only working process parameters were used when determining the amount of used RAM. Maximum 128 connections per process were offered by default.Optimized use of RAM by a server cluster.
Server clusters.
Upgrade: load balancing upon creating a new connection to the server cluster is updated. Upgrade: the algorithm to assess working process performance is updated.Load balancing mechanism did not process some situations well enough. In particular, there was non-optimal working process load and load redistribution took a long time.New connections will use available resources more evenly. Load redistribution among server clusters will be faster. Improved load balancing upon mass connections and disconnections of users to/from the server cluster.
Data history.
The version difference form contains information on moved rows in object tabular sections. A row number before and after movement is shown. +After calling the GetVersionDifference() method, the following information will be available for the moved row:
  • Property LineNumberAfterVersionChange is a new row number (after movement).
  • Property LineNumberBeforeVersionChange is an old row number (before movement).
In the version difference form, the row number after change was adjusted considering actions performed between the first movement and the second movement, and the row number before change contained the row number in the version after change.Eliminated unexpected system behavior.
Data history.
Upon using data history, now you can perform actions once a data version is written. New object manager module event (for objects that support data history): AfterWriteDataHistoryVersionsProcessing. New property available for objects that support data history: WriteDataHistory.AfterWriteDataHistoryProcessing. Use it to manage the need to call the AfterWriteDataHistoryVersionsProcessing event handler. Objects that require processing after writing data history are stored in a special queue. New method available for deleting objects from this queue: DataHistory.DeleteFromAfterWriteVersionsProcessing(). +New configuration object property: ExecuteAfterWriteDataHistoryVersionProcessing. +Now you can update data history once an object is written. History will be updated by a background job once an object write transaction is complete. New property: WriteDataHistory.UpdateHistoryImmediatelyAfterWrite. +New configuration object property: UpdateDataHistoryImmediatelyAfterWrite. +New data history manager method: ExecuteAfterWriteVersionsProcessing(). +Now you can add new fields and tabular sections to a data history record. Tabular sections can be added only to those objects where metadata has tabular sections. New property: WriteDataHistory.AdditionalData. The GetMetadata() method (by a data version) of the data history manager returns information considering added properties and tabular sections. New methods for the WriteDataHistory object: AddAdditionalData() and AddAdditionalDataFieldPresentation(). +Now you can cancel a data history record. New property: WriteDataHistoryParameters.Cancel. +Implemented the WriteDataHistory.VersionComment property for a version comment record. +The following methods of objects that support data history are deprecated and supported for compatibility purposes only: SetDataHistoryVersionComment() and GetDataHistoryVersionComment(). +New parameters available for the UpdateHistory() method (in all syntax options) of the data history manager: ExecuteAfterWriteVersionsProcessing and AutoDeleteFromAfterWriteVersionsProcessing. +Implemented manager module for constants. +New system background jobs for processing after recording versions and for updating data history after recording.These features were not provided.Extended data history features.
Queries.
Data composition system.
If the LIKE operation is used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified inside the brackets using the ESCAPE keyword, works correctly.

This change is not implemented in version 8.3.14 compatibility mode.

If the LIKE operation was used in the query language (also upon calculating a function in the TOTALS sentence) or the data composition system expression language in the infobase file mode, a special character specified using the ESCAPE keyword did not function inside the brackets. +Eliminated unexpected system behavior.
File infobase Queries.
In the file infobase, an addition operation and a subtraction operation of the query language are changed. Upon calculating length and precision of an operation type, preference is given to length rather than precision if the total length of 38 characters is exceeded.

Therefore, if two numeric fields, the first of which has 20 characters and 0 precision and the second of which has 30 characters and 20 precision, are added together or subtracted, the resulting length will be 38 and the precision will be 18. If the second field contains a number with the last precision digits, the number will be cut by precision digits.

Example:

  • If you add 1,000,000,000,000,000,000 and 0.00000000000000000001, you get 1,000,000,000,000,000,000.
  • If you add 1 and 0.00000000000000000001, you get 1.
  • If you subtract 0.99999999999999999999 from 2,000,000,000,000,000,000, you get 1,999,999,999,999,999,999.

This change is not implemented in version 8.3.14 compatibility mode.

Upon calculating length and precision of an operation type, preference was given to precision rather than length if the total length of 38 characters was exceeded.

Therefore, if two numeric fields, the first of which had 20 characters and 0 precision and the second of which had 30 characters and 20 precision, were added together or subtracted, the resulting length would be 38 and the precision would be 20. Because of that, if the first number contained 20 characters in the integral part, a digit overflow error occurred as a result. This would be expressed by a number containing 9 in all parts.

Example:

  • If you add 1,000,000,000,000,000,000 and 0.00000000000000000001, you get 999,999,999,999,999,999.99999999999999999999.
  • If you add 1 and 0.00000000000000000001, you get 1.00000000000000000001.
  • If you subtract 0.99999999999999999999 from 2,000,000,000,000,000,000 you get 999,999,999,999,999,999.99999999999999999999.
Eliminated unexpected system behavior.
Collaboration system.
New feature: now you can register (and unregister) an infobase in the collaboration system on 1C:Enterprise server.

New methods for the collaboration system manager: ExecuteInfoBaseRegistration() and CancelInfoBaseRegistration().

Earlier, you could register and unregister an infobase in the collaboration system on 1C:Enterprise client only.Extended administrative actions in the collaboration system.
Managed forms.
Data composition system.
Upon opening conditional appearance settings (saved in previous platform versions) with disabled compatibility mode, the following conditional appearance parameters of a form or a report will be set to default values:
  • Conditional appearance items of a form (the DataCompositionParameterValue object): Line, Color, and Font.
  • Conditional appearance items of a report (the DataCompositionAppearance object collection): Line, Color, Font, VerticalAlign, HorizontalAlign, Placement, TextPositionRelativeToPicture, and PictureSize.

Changes are applied if values of these conditional appearance parameters are specified as a string and not values of a particular type.

We recommend that you analyze where the above mentioned conditional appearance parameters are used and eliminate places where the parameters are set as a string.

This change is not implemented in version 8.3.14 compatibility mode.

For some form or report conditional appearance parameters (the DataCompositionAppearance object collection), you could specify values (the DataCompositionParameterValue object) not only as values of particular types but also as a string. These parameters were the following:
  • Conditional appearance items of a form: Line, Color, and Font.
  • Conditional appearance items of a report: Line, Color, Font, VerticalAlign, HorizontalAlign, Placement, TextPositionRelativeToPicture, and PictureSize.

You could see the following behavior:

  • In conditional appearance of reports and upon reading parameter values from XML, a string was converted to a value matching the parameter type. Parameters were used with the values resulted from the conversion.
  • In conditional appearance of dynamic lists, a string was not converted to a value. Default parameter values were used.
  • In conditional appearance of forms (in thin client), a string was converted to a value. Parameters were used with the values resulted from the conversion.
  • In conditional appearance of forms (in thin client), a string was not converted to a value. Default parameter values were used. In version 8.3.14, an error occurred in that case.
Eliminated unexpected system behavior.
Data composition system.
Upon calculating values of the data composition system fields listed below, the principle is applied: a if value of the resource, from which this field is received, is equal to 0 in the current grouping, the field value is also 0. These fields are the following:
  • % total
  • % in grouping
  • % in hierarchy group
  • % in row or series
  • % in column or point
  • % in row or series grouping
  • % in column or point grouping
  • % in row or series group
  • % in column or point hierarchy group

This change is not implemented in version 8.3.14 compatibility mode.

Upon calculating values of the following data composition system fields:
  • % total
  • % in grouping
  • % in hierarchy group
  • % in row or series
  • % in column or point
  • % in row or series grouping
  • % in column or point grouping
  • % in row or series group
  • % in column or point hierarchy group

you could see the following behavior: values were always divided by a parent grouping value or grand total, except for cases when the resource value in the grouping was equal to NULL. As a result, an exception could be thrown due to division by 0.

Eliminated unexpected system behavior.
Charts.
Upon assigning a new value to the Chart.DataSource property, first, the existing points and series are deleted, and then the new ones are created according to the new data source. After a new value is assigned, the current selection is cleared.

We recommend that you remember the current selection before setting new data and restore it if necessary.

This change is not implemented in version 8.3.14 compatibility mode.

Upon assigning a new value to the Chart.DataSource property, the existing points and series were not deleted and the selection was not cleared.Eliminated unexpected system behavior.

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile client.
Development tools.
In the form editor preview panel, rounded screen corners and displays with a cutout are supported now (for mobile devices on iOS). +iPhone models X/XS/XS Max/XR are added to the list of devices for preview in the form editor.This feature was not provided.Designing forms for the latest iPhone devices is easier now.
Mobile device-specific features.
Mobile client.
Mobile platform.
Now you can put a stamp on a photo indicating a photo date and time, as well as a custom text. +New object: PhotoStamp. +Implemented the Stamp parameter of the MultimediaTools.MakePhoto() method. This feature was not provided.Expanded photo management capabilities.
Mobile device-specific features.
Mobile platform.
Mobile client.
For mobile applications on Android, the sound is recorded in MPEG4 using AAC codec. +For mobile applications on any mobile operating system, the sound is recorded in stereo, the bitrate is 128 kbps, and the sample rate is 44 kHz. +The MultimediaTools.MakeAudioRecording() method returns the MultimediaData object where the file extension is set to m4a and the MIME type is set to audio/mp4.The sound quality and the MultimediaTools.MakeAudioRecording() method result depended on the used operating system: +
  • Android: 3gp and mono; the sample rate was 8 kHz. 3gp extension and audio/3gp MIME type.
  • iOS: m4a and stereo; the sample rate was 44 kHz. m4a extension and audio/mp4 MIME type.
  • Windows: m4a and mono; the sound quality was selected automatically. aac extension and audio/aac MIME type.
Unified audio information recording result on different mobile operating systems. +You can listen to a sound recording made in 1C:Enterprise mobile platform using standard tools of operating systems on personal computers.
Background and scheduled jobs.
Mobile client.
Now you can use the scheduled job dialog on the mobile client. New object available on the mobile client: ScheduledJobDialog. Editing a schedule for a scheduled job was not available on mobile client.Now you can edit a schedule for a scheduled job on mobile client.
Mobile client.
Mobile application builder.
In mobile client, you can add an infobase to the list by scanning a QR code. This feature is available if the mobile client application is permitted to add an infobase with a custom address.

This feature is also available in mobile version for developers.

In mobile application builder, you can allow users to add infobases using QR codes.

In addresses related to schema e1c://, you can use the following commands:

  • /AddByQRCode to start QR code scanning.
  • /AddInfoBase to add the infobase to the infobase list of the client application.
This feature was not provided.Advanced features for adding infobases to the list in mobile client or mobile platform. Simplified procedure of adding infobases.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Database copies.
Initial population of a database copy is faster now if source data includes documents generating records in registers and containing a large number of rows in tabular sections.Initial population of a database copy took more time if source data included documents generating records in registers and containing a large number of rows in tabular sections.Upgrade: faster initial population of a database copy.
Collaboration system.
On overriding the selection list of collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as No notification) is passed as a special value of the ChoiceData parameter of the CollaborationSystemUserAutoComplete data processor.

A special value can be created using the constructor of the CollaborationSystemUserID object without specifying a collaboration system user ID.

The Undefined value is no longer allowed as a value of the ChoiceData parameter of the CollaborationSystemUserID data processor.

On overriding the list of selecting collaboration system users, on creating a context conversation message, the need to disable a user notification (displayed in the user interface as No notification) was passed as the Undefined value, which prevented distinguishing notification disable and closing the user selection form without any choice.Eliminated unexpected system behavior.
Managed locks.
In client/server mode, a pessimistic object lock will be unconditionally released by the server cluster if the following conditions are met:
  • There is an attempt to release an object lock set by another user (in a remote client application).
  • The collaboration system is used to release the lock.
  • The remote client application did not release the lock 5 seconds after sending the collaboration system message.
In client/server mode, an attempt to release a pessimistic object lock resulted in the message stating that editing was not possible if the following conditions were met:
  • There was an attempt to release an object lock set by another user (in a remote client application).
  • The collaboration system was used to release the lock.
  • The remote client application did not release the lock 5 seconds after sending the collaboration system message.
Eliminated unexpected system behavior.
Server clusters.
Improved failover cluster reliability.Failover cluster was unreliable.Improved failover cluster reliability.
Mobile client.
Mobile platform.
Mobile application builder.
1C:Enterprise mobile platform running Android now supports 64-bit processors.Mobile application builder creates 4 versions of application that targets Android upon building:
  • 32-bit x86 application
  • 32-bit ARM application
  • 64-bit x86_64 application
  • 64-bit ARM64 application.

+

You can now publish 64-bit applications in Google Play.

Changed files in the following mobile version distribution archive: mobile.zip. +

Mobile platform 1C:Enterprise running Android supported 32-bit processors only. Mobile application builder could not build and publish 64-bit mobile application versions in Google Play.Expanded list of supported processor architectures for a mobile version running Android.

Built mobile applications running Android are larger now. Built mobile applications running Android now perform faster.

Mobile platform.
Mobile client.
Mobile application builder.
Some single mobile application permissions were replaced by multiple permissions in order to meet requirements of application store owners.

+

The Telephony permission is replaced with: +Dialing +Read the phone log +Call handling +Automatically send text messages +Get text messages +Text message log. +The Media permission is replaced with: +Camera +Microphone +Music library +Picture and video library +Audio and video playback. +New permissions are grouped by purpose and functional cohesion.

Configurations exported by version 8.3.14 or earlier versions cannot be built using mobile version 8.3.15 or higher. The reverse is also true.

Mobile application permissions had a different composition.Mobile application permissions include changed requirements of application store owners.
Mobile platform.
Mobile client.
Mobile application builder.
In Designer, you can now edit request bodies of permissions that are required by the mobile application. Request bodies of permissions that have an applied meaning for the user are editable.

Mobile application builder allows you to build mobile applications that contain both configurations with the specified permission request bodies and configurations without them (exported in previous 1C:Enterprise platform versions).

Permission request bodies were not editable in Designer.You can now specify permission request bodies that meet the mobile application requirements as accurately as possible.
Mobile platform.
Mobile client.
Global search.
Upgrade: global search is now available in 1C:Enterprise mobile version.This feature was not supported in the mobile version.Upgrade: 1C:Enterprise mobile version now has the features that were implemented earlier in 1C:Enterprise version for a personal computer.
Development tools.
Implemented the following changes in Syntax Assistant:
  • Deprecated objects (properties, functions, procedures, etc.) are not deleted from Syntax Assistant but saved to it.
  • Accessibility of deprecated objects (objects that are not yet available or not recommended for use in the current compatibility mode) in Syntax Assistant tree can be managed using the check box in Syntax Assistant settings: Display deprecated objects.
  • Upgrade: an addition version, a depreciation version, and a version where significant information about an object was last edited can be displayed.
  • For deprecated objects, objects recommended for usage instead of the deprecated object can be displayed now.
  • The syntax assistant font is the default font of the WebKit library used to display HTML documents.
  • For Syntax Assistant content window, the width limit is 1,000 pixels.
  • Decreased indents before and after bulleted lists.

+

Regardless of the state of the Display deprecated objects setting check box, search using Ctrl+F1 always results in information about a Syntax Assistant object being displayed.

Addition version information is filled in for all objects of Syntax Assistant. Deletion version information is filled in for all objects of Syntax Assistant. Objects recommended for replacement are filled in only if the object was declared deprecated in version 8.3.14 and above.

Specified changes in Syntax Assistant are valid starting from version 8.3.15 and above.

Syntax Assistant did not have any information about object versions (of addition, depreciation, or change) and objects that are recommended for usage instead of the deprecated ones. Deprecated objects were deleted from Syntax Assistant. It was impossible to access such objects.Syntax Assistant became more informative and useful for developers.
Mobile platform.
Mobile client.
Mobile device-specific features.
You can now use additional authentication to access mobile application features. Authentication is done by the used mobile operating system and includes authentication using biometrics (a fingerprint, face recognition, or iris recognition) or a password (pattern lock and so on). New global context property: AdditionalUserValidation.

Upgrade: safe storage of confidential information on a user mobile device. Information is protected by the mobile operating system. You can now manage the need for additional authentication to access confidential information. New global context property: SecureStore.

These features were not provided.Added functionality of 1C:Enterprise mobile version for additional user authentication and confidential information storage.
Mobile client.
Biometric authentication for simplified login to the application is now available in the mobile client.

Use biometrics check box should be enabled on the mobile devices that support biometric authentication, in the mobile client infobase properties, and in the dialog boxes for entering the username and password generated by the mobile client.

This feature was not provided.Authentication to an application on devices that support biometric authentication can now be simplified.
Client application installation.
Windows client application installer now supports Vietnamese language.The Windows client application installer did not support Vietnamese.Eliminated unexpected system behavior.
Data history.
Implemented the following features for standard Data history processor:
  • Starting object queue data processor after writing versions.
  • Removing objects from the object data processor queue after writing versions.

+These features are available from the data processor form using the More - Data history management command.

These features were not provided.The standard data processor supports new features of the data history component previously implemented in the platform.
Collaboration system.
Client application form.
When calling the BeginGetConversation() form method, a context conversation is created if the resulting context conversation is missing by the time the method is called.When calling the BeginGetConversation() form method, the context conversation was not created.When calling the BeginGetConversation() form method, a context conversation is automatically created if it was not created before..
Documentation.
The documents state that 1C:Enterprise can operate with clusters that are created using PostgreSQL DBMS versions listed in the system requirements for the platform.The list of PostgreSQL DBMS versions using which a cluster is created to operate with 1C:Enterprise was specified incorrectly.Fixed the error in the documents.
Server clusters.
Optimized the final step of load balancing algorithm (in the selection mode with a performance priority) when the workflows selected in the previous steps differ in available performance.The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase.Optimized load balancing algorithm in a server cluster.
Web client, web service, and HTTP service publishing tools.
The documents contain information on configuring web servers for the correct background jobs feature operation in the file infobase.The documents did not contain information on configuring web servers for the correct operation of the background jobs feature in the file infobase.Updated platform documents.
File operations.
When using the BeginPutFile()/BeginPuttingFiles() methods, the downloaded file(s) are split into parts and the transfer to the server is performed in parts. As a result, the user interface remains operational.

Also implemented the option to start putting new files, even if the previously started putting of files is not yet complete.

When using the BeginPutFile()/BeginPuttingFiles() methods, the uploaded file/files were transferred fully. The client application did not respond to user actions during the transfer.

It was impossible to start putting a new file until the previously started putting of one or more files was completed.

Eliminated unexpected system behavior.
Calculation registers.
Applied objects.
Implemented the feature to include sequences and recalculations in the common attributes.

This change is not implemented in version 8.3.14 compatibility mode. +

This feature was not provided.Expanded the structure of configuration objects, which may be part of common attributes.
Software licensing.
Starting the client application and Designer on PCs running on Linux or macOS when using basic configurations has been accelerated for cases, when the PC has a large number of disk partitions or processor cores.

The list of key hardware parameters used when activating the base software license on Linux and macOS is aligned with the list of key parameters in Windows.

Starting the client application and Designer on PCs running Linux and macOS when using basic configurations when the PC had a large number of disk partitions or processor cores took a long time.

The list of key hardware parameters used when activating the base software license on Linux and macOS was different from the list of key parameters in Windows.

Starting the client application and Designer when using the basic configuration in Linux and macOS has been accelerated.
Mobile client.
The TextDocument object is now available in mobile client.The TextDocument object was not available in mobile client.Added new mobile client features.
Server clusters.
The Critical amount of process memory, Temporarily allowed amount of process memory, and Period of exceeding the process memory threshold parameters can be changed with a PROF license.

However, these parameters only affect the restart of processes. The effect of these parameters on the server calls interruption is only supported for CORP licenses.

If the server is running with a PROF license, the limit memory size, after which the client’s server call is interrupted, is defined as 80% of the physical memory of the computer, regardless of the Temporarily allowed amount of process memory parameter value.

The Critical amount of process memory, Temporarily allowed amount of process memory, and Period of exceeding the process memory threshold parameters could only be changed with a CORP license.Restarting the working processes depending on the amount of RAM used is now possible for a server cluster running PROF license.
Client application form.
Interface.
Alt+L shortcut is now used for the Search everywhere command of the form elements context menu.Ctrl+Shift+C shortcut was used for the Search everywhere command of the form elements context menu.Fixed the conflict between the platform feature keyboard shortcut and the established keyboard shortcuts of typical applications.
Interface.
The form menu is added in the Taxi interface. It is called by the three dots button, located in the top right section of the form (except for the dialog boxes generated by the Question(), ShowQuestion(), Warning() and ShowWarning() methods). The home page displays a single form menu. The form menu items depend on the current (active) form element:
  • The File menu is available if save and print commands are available for the current element.
  • Search commands are displayed if search or replace is supported for the current element. Search commands will not be displayed if the current form element is a table that displays a dynamic list or form data collection.
  • Clipboard commands are displayed if the current element supports the clipboard.
  • If the current element supports cancel and return commands, these commands are available in the form menu.
  • The command for displaying properties is available when viewing the properties of the current element is available.
  • The special paste command is displayed if special pasting is available (in thin and thick client applications only).
  • The command to configure the form navigation panel is displayed only if this feature is available.
  • The Messages command is displayed if messages were displayed in the form.
  • Commands for merging and docking windows are not displayed in the form menu if the form is displayed in an auxiliary window.

+The following changes have been made to the Service and Settings menu:

  • The window merging and docking commands have been removed from the Windows menu.
  • The commands for displaying the message window and settings of the form navigation panel have been removed from the Settings menu.
  • The save, print (and print settings) commands only affect the current (active) element of the current client application form.

+Clipboard commands for numbers (put in the clipboard, add to/subtract from the clipboard) can be displayed in the main application window or in the auxiliary application window title. To enable/disable these commands, use the Show, M, M+, M- command in the Service and Settings menu.

Alt+F keyboard shortcut opens the advanced search dialog box in the form table that displays a dynamic list. +

There was no form menu. Form menu commands were located in the Service and Settings menu.Improved navigation in the application.
Full-text search.
Fixed the problem of searching for words ending in "*" using full-text search.

If the platform can detect that the current full-text search index is incorrect, it will automatically delete it.

We recommend to clear and rebuild the full-text search index when upgrading to version 8.3.15.

Searching words ending in "*" using full-text search was not available.Eliminated unexpected system behavior.
Administration tools.
The 1C:Enterprise distribution package now includes files that enable the installer operation on Windows XP (the names of such files have the _xp suffix).

The 1C:Enterprise installers now use the UTF-8 encoding on Windows. The 1C:Enterprise installer on Windows XP use the ANSI encoding.

The 1C:Enterprise installer on Windows XP does not support Vietnamese language.

Provided that Windows XP is not used, we recommend to exclude the files of distribution package for Windows XP when updating the 1C:Enterprise through web server.

The 1C:Enterprise installer could display some national symbols incorrectly on Windows XP.There is now a separate distribution package for obsolete Windows XP.
Spreadsheet documents.
Search control commands are now available in the More menu of the report form and the spreadsheet document form.

Commands for working with table and editing commands are no longer available in the More menu of a spreadsheet document. +

Search control commands were only available in the report form and spreadsheet document menu.

Commands for working with table and editing commands were available in the More menu of a spreadsheet document form. The same commands were available in the form menu.

The distribution of commands between the form menu and the More menu in the report and spreadsheet document forms has become more logical and understandable.
Interface.
Save and print settings commands are no longer available in the Service and Settings - File menu.Save and print settings commands were available in the Service and Settings - File menu.Removed duplication of commands in various application menus.
Interface.
Zoom command was moved to the form menu.Zoom command was available in Service and Settings menu.The form context command is now available in the form directly.
Administration tools.
The system integrity control utility is implemented by making calculating the hash function of files through the SHA-256 and GOST R 31.11-2012 (512 bit) algorithms possible.

In the make utility's operating mode the --method parameter is implemented. Now you can specify the algorithm used in the hash function calculation.

+

+

To calculate the hash function of the files, the system integrity control utility was using the SHA-1 algorithm.Now you can use stronger algorithms to calculate the hash functions.
Data history.
The data history update is now performed faster (with the DataHistory.UpdateHistory() method) in case there is a large number of versions that need to be transferred to the data history.The data history update (with the DataHistory.UpdateHistory() method) took a very long time in case there is a large number of versions in the system that need to be transferred to the data history. +Data history update is improved. The data history can be updated in the background.
Full-text search.
Reduced the time of the full-text search index generation. Reduced disk space requirements of the full-text search index. +If you enter a search string consisting of one or two chars and the "*" substitution char (any sequence of chars), an error may occur with the suggestion to refine the search string (if the search result is large). +Full-text search index generation took more time. The index required more disk space. +If you entered a search string consisting of one or two chars and the "*" substitution char (any sequence of chars), an error with the suggestion to refine the search string (if the search result is large) did not occurr. +The full-text search index generation is now faster. Reduced disk space requirements of the full-text search index. +
Database configuration update.
Restructuring of the database table will not be performed if all the following conditions are met:
  • The optimized mechanism of restructuring (mode v2) is used.
  • Microsoft SQL Server DBMS is used.
  • The object has subordinate objects (attributes, dimensions, etc.) of value storage, string of unlimited length or date type.
  • Such objects were included in version 8.3.7 and earlier compatibility mode.
  • In version 8.3.8 and later compatibility mode these objects were not restructured.
  • All changes in the configuration object are not applied to the attributes of the above-mentioned types.

If all the above-mentioned conditions are met, the optimized restructuring mechanism will only process the actual changes (if possible) without the complete restructuring of the database table. +The non-optimized infobase restructuring mechanism performed the complete database restructuring after any changes made in the configuration object metadata.

The database table was restructured if all the following conditions were met simultaneously:
  • The optimized mechanism of restructuring (mode v2) was used.
  • Microsoft SQL Server DBMS was used.
  • The object had subordinate objects (attributes, dimensions, etc.) of value storage, string of unlimited length or date type.
  • Such objects were included in version 8.3.7 and earlier compatibility mode.
  • In version 8.3.8 and later compatibility mode these objects were not restructured.
  • All changes in the configuration object were not applied to the attributes of the above-mentioned types. +
In some cases the optimized mechanism of restructuring will update the database tables much faster than the previous one. +
Technological log.
The description of CLSTR event properties was updated in the documentation.The documentation contained an obsolete CLSTR event properties description.Documentation was updated.
Client application form.
Command interface.
Added the following buttons to the client application form header: Save, Print, and Print Preview. These buttons and the File form submenu are displayed if there is at least one visible form field of the following types:
  • Spreadsheet document field
  • Text document field
  • Graphical schema field
  • HTML document field
  • Formatted document field
  • Geographical schema field
  • Planner field

+Save and print commands are available if there is at least one form field of one of above-mentioned types that supports these commands.

The form menu can now be called by pressing Alt + -.

The Save, Print, and Print Preview commands were displayed in the system command bar and in the main menu. These commands were available if the current form item or a single visible form item supported these commands and was of one of the following types:
  • Spreadsheet document field
  • Text document field
  • Graphical schema field
  • HTML document field
  • Formatted document field
  • Geographical schema field
  • Planner field +
Simplified interaction with the form items that support save and print options.
Mobile platform.
Mobile client.
System requirements.
The iOs 7.x versions are no longer supported. The earliest supported iOS version is 8.0.The iOS 7.x versions were supported.Ended support for legacy iOS versions. Apple iPhone 4 is no longer supported.
Configuration extensions.
Base configurations can now use extensions. The extension and the base configuration must be signed with the same key.

Added the /SignCfg command for Designer batch mode.

Added the sign-cfg parameter of the config mode for Designer agent mode.

Extensions were not supported by the base configurations.Base configurations developers can now release configuration fixes using extensions.
Web client, web service, and HTTP service publishing tools.
You cannot publish the web service on Apache web server if the web server bitness does not match the Designer bitness.During the web service publication there was no check that Apache web server bitness match the Designer bitness.There are less unexpected errors during the publication caused by the Apache web server bitness and the Designer bitness mismatch.
Administration tools.
You can now update your client application through a web server with the PROF license.CORP license was required to update the client application through a web server.Simplified the update of client applications through a web server.
Server clusters.
Now the cluster monitoring system analyzes both memory usage settings specified in the cluster settings and memory space occupied by every working process:
  • If memory consumption exceeds 80% of the virtual address space, the working process will be terminated in normal mode.
  • If memory consumption exceeds 95% of the virtual address space, the working process will be terminated abnormally.

+The cluster mechanisms that use data on available RAM consider changes made to the RAM size while the computer is operating. For example, if you change parameters of the virtual machine where the server cluster runs.

The cluster monitoring system did not analyze memory space occupied by every working process.

The cluster mechanisms that used data on available RAM relied on RAM data that was retrieved once upon the cluster start.

Improved server cluster stability if the 32-bit 1C:Enterprise server cluster runs 64-bit operating systems.
Spreadsheet documents.
Spreadsheet documents created in 1C:Enterprise v8.3.17 are supported.Spreadsheet documents created in 1C:Enterprise v8.3.17 were not supported.Eliminated unexpected system behavior.
Pictures.
Multipage TIFF files are supported.

New methods: Picture.FramesNumber() and PictureToProcess.GetPictures().

New picture constructor for the PictureToProcess object, which takes an array of pictures as the argument and the resulting picture format as the parameter. New parameters for the PictureToProcess object: Frames and Format. +Implemented the CurrentFrameNumber property and the FramesNumber() method for the form field extension of the client application for a picture.

Only the first frame of a multipage TIFF file could be unloaded.Multipage TIFF files are supported.
Client application.
Administration tools.
In the dialog box where you enter your username or password, you can now place hyperlinks to navigate to the help page and recover your password.

You can recover your password on the website, via email, or using the OpenID provider tools. New feature: each infobase user can recover their password. A configured system does not require human involvement to recover the user password.

New properties for the InfobaseUser object: EmailAddress and CannotRecoverPassword.

New global context property: AdditionalAuthenticationSettings.

Implemented the following event log events: Session. Attempting to recover the password, Session. An error occurred while attempting to recover the password, Infobase. Changing additional authentication settings, Infobase. An error occurred while changing additional authentication settings.

The user password could be recovered with infobase administrator involvement only.Now it is easier for a user to recover their password. Password recovery no longer requires direct administrator involvement.
Dynamic lists.
Data composition system.
Eliminated the error restoring data composition system settings and dynamic list settings when the settings were saved in version 8.3.16 or later but configuration compatibility mode was set to Version 8.3.15. +If configuration compatibility mode was set to Version 8.3.15 and data composition system settings or dynamic list settings were saved in platform version 8.3.16 or later, it was not possible to restore the settings.Eliminated unexpected system behavior.
Client application.
Client application installation.
Administration tools.
You can now distribute the client application via the web server using web server extensions, without configuring the default.vrd file. The client application distribution package will be searched in the distr directory of the version whose web server extension is running on the web server.

Implemented new versions of client application distribution packages that can be installed in addition to the full-fledged distribution package of 1C:Enterprise and contain packaged distribution packages of client applications. This option for delivering client applications is supported only for Windows and macOS

This feature was not provided.

The client application distribution package could be obtained from the web server only after the default.vrd file was configured correctly.

It is now easier to configure distribution of client application distribution packages when updating the 1C:Enterprise system version. +

Table of contents

Transition from the previous version to the version 8.3.15

Table of contents

Version 8.3.14

Version 8.3.14 includes known bug fixes and functionality modifications. +

Improved database configuration update mechanism graduated out of beta.

Windows-based 64-bit client application (thin client, thick client, and Designer) graduated out of beta.

+

The mobile client has graduated out of beta.

The Windows-compatible mobile platform has graduated out of beta. +

Thin client for macOS graduated out of beta. Thick client and Designer for macOS are still in beta testing.

The term "managed application" is replaced with the term "client application." Unless necessary, the term "managed" is no longer used in V8Update file, help files, and documentation. For example, "managed application" is replaced with "client application" and "managed form input field extension" is replaced with "form input field extension." The renaming is applied to related UI texts in client applications and Designer.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.13 is now implemented.Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.12 was implemented.Configurations developed using 1C:Enterprise platform version 8.3.13 or earlier can run on version 8.3.14 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.14 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.13 after the migration to version 8.3.14, even if you have disabled the compatibility mode (simply enable it again). +
Server clusters.
New standalone 1C:Enterprise server. It can handle client applications that operate an infobase over HTTP protocol.

The standalone server provides HTTP connection, the web-server is no longer required. The standalone server uses computer resources more efficiently.

A single instance of the standalone server provides access to a singe infobase. The standalone server does not support the Designer mode. You can operate the standalone server by the command-line utility. The standalone server supports both file and client/server mode of infobase.

It can handle up to 3 client applications in file mode (without sessions of background jobs, web-services etc.) without server license. It requires a server license of any type in other cases.

The standalone server has some limited functionality. For more info see documentation.

The standalone server provides some inbound administrative tools.

This feature is provided solely for beta testing purpose. +

This feature was not provided.The new 1C:Enterprise architecture improves the stability and effectiveness of server operations.
Database copies.
Server clusters.
DBMS operations.
Copies of tables that can intensify the DBMS load when used in reports or queries now can be stored in an external database (external to the 1C:Enterprise database). The feature is supported only in client/server mode.

You can define which database will be addressed by a specific report or query.

Table copies can be stored in a DBMS of any supported type. The server cluster DBMS type can differ from a database copy DBMS type.

The synchronization between the server cluster database and a database copy can be carried out by the means of DBMS or 1C:Enterprise.

New global context property: DatabaseCopies. New Query object properties: RequiredDataRelevance and RequiredDataRelevanceTime. New QueryResult object properties: DataIsRelevant, DataRelevanceTime, and DatabaseCopy. New DataCompositionOutputParameterValues object properties: RequiredDataRelevance, RequiredDataRelevanceTime, DataRelevanceOutput, and DatabaseCopyOutput. New functions of the data composition system expression language: DataIsRelevant(), DataRelevanceTime(), and DatabaseCopy().

New system background jobs: Initial population of a database copy and Database copy notification handler.

New cluster services: Database copy service and Database copy time service.

New standard function: Database copy management.

New technological log event: <DBCOPIES>.

The database copy feature requires a CORP license.

This feature is provided solely for beta testing purpose.

This feature was not provided.New feature: infobase load can be distributed among a few physical DBMS. For example, the main database can process all document entries, and the database copies can process reports and queries that significantly affect the database performance.
Server clusters.
System requirements.
New feature: the accelerator of analytical report generation (Data accelerator). It is possible due to a new server cluster service, which acts as a database stored in RAM. Data accelerator is based on the database copy engine.

New server cluster service: Data accelerator service.

Data accelerator runs only on 64-bit operating systems. It does not support Windows XP and Windows Vista.

The database copy feature requires a CORP license.

This feature is provided solely for beta testing purpose. The Data accelerator service requires a beta testing license. It is not available without a beta testing license.

This feature was not provided.The generation time of complicated analytical reports is significantly reduced. +
Collaboration system.
The collaboration system supports file operations. Collaboration system servers support the following file storages: Amazon S3, Google Cloud and other storages based on Amazon S3 protocol.

The following limitations can be set on collaboration system servers:

  • Maximum attachment file size.
  • Total size of daily uploaded files.
  • Total size of daily received files.

New property: CollaborationSystemMessage.Attachments. New collaboration system methods: AttachmentsSupported(), AttachCommandsGenerationHandler(), and DetachCommandsGenerationHandler().

This feature was not provided.Expanded collaboration system capabilities.
Collaboration system.
Upgrade: more than two people can join a video conference. Participants can join and leave a conference at any moment. Upgrade: it is possible to establish video conferences between 1C:Enterprise 8.3.13 and 8.3.14. In this case, only one-on-one video conference is possible.This feature was not provided.

Only video calls (one-on-one video conferences) were possible.

Expanded collaboration system capabilities.
Development tools.
New features for Designer agent mode (similar to the features provided by Designer command line):
  • Dump a mobile platform configuration to XML files.
  • Generate a mobile client signature.
  • Dump a mobile client configuration.
  • Dump a configuration or extension to a file.
  • Restore a configuration or extension from a file.
  • Disable configuration support.
  • Dump an infobase.
  • Restore an infobase.
  • Delete infobase data.

New features for Designer agent mode (not available in other modes):

  • Create an empty extension.
  • Delete an extension.
  • Get extension properties.
  • Set extension properties.

New feature: show status of time-consuming operations in agent mode (for some commands).

Upgrade: more errors are described by specific code in error-type field.

Upgrade: messages returned after a command execution in agent mode contain more details.

These features were not provided.New features for Designer in agent mode.
Server clusters.
Administration tools.
New feature: you can administer server clusters using 1C:Enterprise language. The administration is based on ras server, without using COM technology. The cluster supports servers with 1C:Enterprise versions different from the client application version. The administration tools are available from the thin client and from the server.

New object: ServerAdministration.

This feature was not provided.

Server cluster administration was available from 1C:Enterprise language only over COM connections on a server running on Windows. Server administration required a 1C:Enterprise version identical to the server version.

You can implement cross-platform administration interfaces for 1C:Enterprise server clusters with the client application version different from the server cluster version. You can implement cluster consoles for Linux. It is not necessary to use the cluster console that requires Microsoft Management Console.
Data display.
New feature: number-noun agreement. New global context method: GetStringDeclensionsByNumber().This feature was not provided.Generating sentences with numbers (in words or figures) is more convenient.
Common objects.
New feature: solving systems of linear equations. New object: SolvingLinearEquationsSystemsThis feature was not provided.Solving large systems of linear equations takes less time.
Data display.
New picture added to the picture library: Attach.The picture was not available in the library.The picture library is upgraded.
Configuration extensions.
New feature: an adopted enumeration value set can be extended.

When an extension with an extended enumeration value set is deleted, the infobase object attributes that stored the deleted values take a blank reference to the enumeration as their values.

This feature was not provided.Enumeration management is upgraded.
Configuration extensions.
New property for metadata objects adopted to extensions: Comment. The property is intended solely for developers and ignored when building the final configuration or during extension applicability tests.This feature was not provided.Developers can describe the purpose of extension objects using built-in means.
Configuration extensions.
Common objects.
You can create native session parameters in a configuration extension. They can be included in access restriction text.This feature was not provided. Extended configuration extension options.
Calculation registers.
New feature: you can get the effective period of a calculation register record set before the set is written. New method for calculation register record sets: GetAdjustedEffectivePeriod().The effective period could be calculated only after a calculation register record set was written. Due to reducing the number of writing operations, parallel register calculations and performance are improved in certain scenarios.
Server clusters.
New filters for resource consumption counters: by safe mode and by security profile.

New comparison operator for filtering resource consumption counters: inequality.

New resource consumption counter filter feature: a number of conditions with the same filter type can be combined using the AND operator.

These features were not provided.Advanced performance analysis for applications running in client/server mode.
Data composition system.
The data composition system can display pictures stored in the infobase. Reports can include both pictures specified as URLs and pictures stored in attributes of ValueStorage type.

New properties of DataCompositionAppearance and DataCompositionAreaTemplateTableCellAppearance objects: PictureOutput, PictureSize, TextPositionRelativeToPicture, PictureHorizontalAlign, and PictureVerticalAlign.

The default behavior is not changed in Version 8.3.13 compatibility mode.

The data composition system did not provide means for displaying pictures stored in the infobase.New formatting options for the data composition system.
Charts.
New feature: editing sets of chart series and points. New methods for ChartPoints and ChartSeriesCollection objects: Insert(), Move(), Delete(), and Clear().This feature was not provided.

To edit a point or value, one had to refill all chart data.

New chart features.

For example, you can create autoscrolling charts where the first point of a chart is removed and the last one is added with a certain period.

Client application.
Batch mode is implemented for the thin and thick clients. The batch mode is available from the start of a client application till the completion of the BeforeStart handler in the application module. Then the batch mode is turned off automatically. The batch mode suppresses all system dialog boxes.

The /DisableStartupDialogs command-line option switches a client application to the batch mode. For more information about the batch mode, see 1C:Enterprise documentation.

New global context method: ProhibitFormOpening().

You can add the option that enables batch mode to client application startup parameters in Designer.

Runtime errors in the RunApp() or BeginRunningApplication() method generate exceptions in batch mode.

This feature was not provided.

Only Designer supported the batch mode.

Runtime errors in the RunApp() or BeginRunningApplication() method generated dialog boxes with error descriptions on the server.

Client application startup scenarios where you can suppress opening dialog boxes that normally block programmatic handling of startup issues are now possible.
System requirements.
New feature: software license for beta testing. The license is complementary to 1C:Enterprise server license. Beta testing license cannot replace a 1C:Enterprise server licence. The number of beta testing licenses must be equal to or greater than the number of server licenses for the server cluster that runs the tests.

If a new feature requires a beta testing license, it is mentioned in the feature announcement.

To apply for a beta testing license, send your request to betaplatform@1c.ru.

Licensing utility now supports feature testing licenses. +

Feature beta testing did not require special licenses.In some cases, feature beta testing requires beta testing licenses.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Web client.
The web client does not support configurations with Version 8.2 interface. The web client does not support switching between Version 8.2 and Taxi interfaces. Command-line options itdi and itaxi are ignored. The options are considered obsolete and not recommended for use. Regardless of the value of the ClientSettings.ClientApplicationInterfaceVariant property, the Taxi interface is used. The web client supported Version 8.2 interface.Support of obsolete client application interface type is discontinued. Web client stability is improved.
Collaboration system.
Upgrade: a user can separately turn off the camera or microphone during a video call.When a user turned off the camera during a video call, the microphone turned off automatically.Eliminated unexpected system behavior.
Command interface.
Upgrade: if a section or command interface command has a help topic, its tooltip does not contain the "Help" hyperlink.

The help topics are still available from the help window.

In the current section functions panel and the functions menu, lists and configuration objects have tooltips with their explanations or extended presentations.

The tooltip behavior was as follows:
  • If a section had a help topic, the tooltip for the section in the sections panel contained the "Help" hyperlink.
  • If a command had a help topic, the tooltip for the command in the current section functions panel contained the "Help" hyperlink.
  • The functions menu commands did not have tooltips.
  • In the web client, section tooltips in the sections panel contained the section synonyms, not the explanations.
  • In the web client, in the current section functions panel, tooltips of lists and objects contained the command synonyms, not the explanations or extended presentations of lists and objects.
Faster command interface displaying in the thin client. Standardized view of section and command tooltips in different client applications
Configuration extensions.
Web client.
In the web client, if an infobase contains extensions, browsers cache pictures according to the following rules:
  • Extended configuration pictures are cached for all sessions of the infobase.
  • Extension pictures are cached for each session.
In the web client, if an infobase contains extensions, browsers cached all configuration pictures for each session.Eliminated unexpected system behavior.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Charts.
Upgrade: improved performance of charts that contain large data sets.

We recommend that you analyze charts in your applications and refactor them as follows:

  • The initial data population is performed on the server.
  • Major data changes (including data repopulations) are performed on the server.
  • Minor data changes can be performed on the client.
Inefficient performance of charts that contained large data sets.Improved performance of charts that contain large data sets.
Administration tools.
Upgrade: the user list in Designer opens faster. The improvement is noticeable if the list contains many users and roles. +In an infobase that contained many users and roles, the user list opened slowly.The user list opens faster.
Accounting registers.
Accumulation registers.
Upgrade: faster totals recalculation for accounting registers and accumulation registers in the following cases:
  • During Verify and repair operation in Designer.
  • Using the RecalcTotals() method when the following conditions are met:
Totals recalculation for accounting registers and accumulation registers took a significant amount of time.Totals recalculation for accounting registers and accumulation registers takes less time.
Full-text search.
Upgrade: faster search for expressions like "word*" when an application has many instances of "word". Upgrade: exceeding search word threshold is less likely for expressions like "word*".

This upgrade is ignored in 8.3.13 version compatibility mode.

Search for expressions like "word*" could fail due to exceeding search word threshold error.Optimization of full-text search.
DBMS operations.
Upgrade: faster restructuring of infobases based on Microsoft SQL Server and IBM Db2.Restructuring of infobases based on Microsoft SQL Server and IBM Db2 took more time.Faster restructuring of infobases based on Microsoft SQL Server and IBM Db2.
DBMS operations.
Upgrade: simultaneous release of a number of connections with Microsoft SQL Server is less likely, which improves TempDB performance.There was a possibility of simultaneous release of a number of connections with Microsoft SQL Server, which significantly reduced TempDB performance.Optimized operation of TempDB on Microsoft SQL Server.
Calculation registers.
New feature: clustered index by recorder for calculation registers. An index is rebuilt during calculation register restructuring or during Verify and repair operation.

Upon deleting records from an effective period table, if there is no filter by register dimensions, the deletion query does not require establishing connection to the main register table.

Clustered index was not available for calculation registers.

Upon deleting records from an effective period table, if there was no filter by register dimensions, the deletion query always established connection to the main register table.

Reduced possibility of table lock upon deleting calculation register effective period records.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Client applications.
New feature: the thin client (connected over HTTP/HTTPS) supports all OpenID authentication providers that support OpenID Connect protocol.This feature was not provided.

Only the web client supported such OpenID authentication providers.

New user authentication option for the thin client.
Client application.
New feature: user authentication with Unified System for Identification and Authentication (USIA) in the web client or thin client (connected over HTTP/HTTPS).

New properties in OpenID Connect provider description in the default.vrd file (the <providers> element): dialect and crypto.

In the thin client, authentication with USIA is possible only if the infobase is published on an Apache web server.

This feature was not provided.New user authentication option.
Queries.
Data composition system.
New feature: when managing queries with the QuerySchema object, you can use the query language extension for the data composition system.

New property: QuerySchema.DataCompositionMode. New properties for the QuerySchemaSelectQuery object: DataCompositionSelectionFields and Characteristics. New property: QuerySchemaSelectOperator.DataCompositionFilterExpression. New property: QuerySchemaTable.DataCompositionParameters.

New feature: query wizard in 1C:Enterprise mode supports the query language extension for the data composition system.

New property: QueryWizard.DataCompositionMode.

The QuerySchema object did not support the query extension for the data composition system.

Query wizard in 1C:Enterprise mode did not support the query language extension for the data composition system.

New features for queries in 1C:Enterprise mode related to the extension for the data composition system.
Server clusters.
Upgrade: on cluster manager crash the details of the running and completed background jobs are saved. Scheduled jobs starting and processing is not interrupted.Cluster manager crash caused the following:
  • For all infobases, the details of the running and completed background jobs were lost, as well as background job-related messages.
  • If a client application was waiting for background jobs to complete, it stopped responding for indefinite period.
  • Execution of scheduled job stopped for one minute, till the data was reread from the infobases.
Improved fault tolerance of server cluster operations related to background and scheduled jobs. Users of applications that run background or scheduled jobs do not notice cluster manager crashes.
Dynamic lists.
New feature: you can specify fields that will be used as selection key fields. New properties for the DynamicList object: KeyType and KeyFields. New object: DynamicListRowKey. New feature: dynamic list query settings dialog box allows customization of the fields that form row keys.

This feature is ignored in 8.3.7 version compatibility mode.

We recommend that you revise all dynamic lists (excluding RecordsWithExtDimensions, TasksByPerformer, filter criterion, and information register slice tables) with no main table specified or where the main table is a virtual table without a key toward using keys of Field value or Row key types.

This feature was not provided.

Key fields were defined by the main dynamic list table.

New feature for dynamic lists with no main table. Improved performance of dynamic lists with no main table. For example, now such dynamic lists support groupings.
Development tools.
New feature: in Designer agent mode, names of user working directories contain numeric codes. The directory–user mapping is stored in agentbasedir.json file located in the agent working directory (the AgentBaseDir command-line option).In Designer agent mode, names of user working directories contained the usernames.Working directory names do not reveal the names of the users that work in Designer agent mode. Shorter paths to user working directories. +
Configuration extensions.
Upgrade: when a form is adopted by an extension, only form items are adopted. After adoption, you can edit all item properties from an extension using the form editor. By default, other form objects (such as attributes, commands, and parameters) are not adopted, so they are not editable. To edit such objects, you must include them in the extension.

When a form is adopted, the parent configuration object of the form is not adopted.

The upgrade does not affect the forms adopted to extensions in the previous 1C:Enterprise versions.

When a form was adopted by an extension, the parent configuration object and all the extension objects were adopted.Managing adopted configuration object forms is more convenient. Adjusting extensions to new configuration versions is more convenient.
Charts.
Data composition system.
Upgrade: when you print a report, each chart fits one page. Upon printing, the data composition system output processor sets StayWithNext property value to True for the spreadsheet document rows that follow the chart.

This upgrade is ignored in 8.3.13 version compatibility mode.

In a printed report, a chart could be ripped by a page break.Printed reports are more readable.
Managed forms.
Upgrade: in the thin, thick, and web clients, a form unlocks objects in one minute after the modification flag is cleared.In the thin, thick, and web client, a form unlocked objects after the form had been closed.Parallel operation is improved in some cases.
Charts.
The algorithm that calculates the plot area size for a pie chart is revised. It reserves more space for highlighting the sector where the pointer is.

This upgrade is ignored in 8.3.13 version compatibility mode.

The plot area of a pie chart occupied all available space. This might cause cropping of the highlighted sector area.Eliminated unexpected system behavior.
Configuration extensions.
Upgrade: when a configuration extension is applied, the number of parameters and Val keyword before event handler parameters are not checked.When a configuration extension was applied, the number of parameters and Val keyword before event handler parameters were checked. The number of parameters in an extension had to match the number of parameters in an extended configuration.Extension behavior complies with the platform behavior for the main configuration. Upon an event handler call, the number of parameters is not checked.
Data composition system.
Upgrade: upon data composition template generation, a field alias includes the source field alias and the field details (the presentation of the field attribute, the aggregate function, and so on).

This upgrade is ignored in 8.3.13 version compatibility mode.

Upon data composition template generation, default query wizard naming rules were applied to create a field alias.A field content is more transparent by its alias.
Pictures.
New feature: support of GIF pictures with "XMP DataXMP" extension.This feature was not provided.Extended list of supported picture formats. 1C:Enterprise supports GIF pictures created with Adobe tools.
DBMS operations.
Technological log.
Upgrade: for PostgreSQL DBMS, the technological log (<plansql> event) keeps query plans for UPDATE, DELETE, and INSERT queries.For PostgreSQL DBMS, the technological log (<plansql> event) kept query plans only for SELECT queries.Analyzing applications based on PostgreSQL DBMS is more convenient. +
Development tools.
Upgrade: upon comparing configuration modules, you can see which methods are unchanged but moved to another preprocessor instruction or region. +Upon comparing configuration modules, methods that were unchanged but moved to another preprocessor instruction or region were displayed as changed, which could be misleading.Module comparison is more transparent and convenient.
Spreadsheet documents.
Charts.
When a spreadsheet document is displayed in the edit mode in the thin client, thick client, or Designer, pointing to a chart area opens its properties.When a spreadsheet document was displayed in the edit mode in the thin client, thick client, or Designer, opening chart area properties required the following steps: first double-click the chart, and then point to the area.Simplified interaction with charts embedded to spreadsheet documents.
Database configuration update.
New feature: critical errors of the optimized database configuration update mechanism are displayed in Designer and in the <EXCP> event of the technological log.Critical errors of the optimized database configuration update mechanism were not displayed in Designer or in the <EXCP> event of the technological log.Improved diagnostics of critical errors in the optimized database configuration update mechanism.
Spreadsheet documents.
Upgrade: data import from Microsoft Office OpenXML (Microsoft Excel 2007 or later) and ODT (OpenDocument) files is updated. Some bugs related to import from these file types are fixed.Importing data from Microsoft Office OpenXML (Microsoft Excel 2007 or later) and ODT (OpenDocument) files could cause errors.Eliminated unexpected system behavior.
Spreadsheet documents.
Upgrade: when exporting a spreadsheet document from an XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) file, if a shape or picture text in the source spreadsheet is blank or contains only spaces, a drawing of Text type is not created in the target spreadsheet.

This upgrade is ignored in 8.3.13 version compatibility mode.

When importing a spreadsheet document from an XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and later), or ODS (OpenDocument) file, the following behavior occurred:
  • For shapes, if the text was blank, the import was not performed; if the text contained only spaces, the import was performed.
  • For pictures, if the text was blank or contained only spaces, the import was performed.
Eliminated unexpected system behavior.
Dumping configurations to files/Restoring configurations from files.
When the configuration root is restored from XML partially and there is no external property file with support settings, the restore settings will be cleared. The configuration support will disabled as a result.When the configuration root was restored from XML partially and there was no external property file with support settings, the restore settings remained intact. The configuration support mode remained intact as well.Eliminated unexpected system behavior.
Spreadsheet documents.
Upgrade: for spreadsheet document drawings that are comments, the DrawingType property value is SpreadsheetDocumentDrawingType.Comment.

This upgrade is ignored in 8.3.13 version compatibility mode.

For spreadsheet document drawings that were comments, the DrawingType property value was SpreadsheetDocumentDrawingType.Text.Eliminated unexpected system behavior.
Spreadsheet documents.
Text is displayed correctly in spreadsheet document cells with "Justify" alignment.

This upgrade is ignored in 8.3.13 version compatibility mode.

Text in spreadsheet document cells with "Justify" alignment looked as text with "Left" alignment.Eliminated unexpected system behavior.
Data composition system.
The data composition system template generator outputs resource field groupings to templates even if a predefined template describes the output of the parent grouping and resources are not specified in the selected fields of the parent grouping but specified in the fields of the child grouping.

This might change the look of some reports.

This upgrade is ignored in 8.3.13 version compatibility mode.

The data composition system template generator did not output resource field groupings to templates if a predefined template described the output of the parent grouping and resources were not specified in the selected fields of the parent grouping but were specified in the fields of the child grouping. +Eliminated unexpected system behavior.
Technological log.
New technological log properties for DBMS access events (DB2, DBMSSQL, DBPOSTGRS, and DBORACLE) and EXCP and SDBL events: Dbms, Database, and DBCopy.This feature was not provided.More convenient DBMS selection diagnostics when managing database copies.
Development tools.
Upgrade: when comparing configurations, you can view the detailed differences in help topics. Upgrade: you can compare help topics in selected language, similar to other platform multilingual tools.When comparing configurations, you could only see if the help topics were different, without any details on the differences.Comparing help topics in configurations is more convenient.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Administration tools.
Software licensing.
New feature: ring command-line utility and its license module are provided as a standalone distribution package (1C:Enterprise licensing utility). The distribution package supports Windows 7 and later, and Linux x86 and x86-64.

The distribution archive names comply with the following pattern: 1c-enterprise-license-tools-a.b.c+d-os-arch.zip. The archive is included into 1C:Enterprise distribution package.

The distribution packages of the ring utility and its license module are no longer stored to the ExtDst directory.

You can find 1C:Enterprise installer documentation on the ITS DVD Read more..

The ring utility and its license module were a part of 1C:Enterprise distribution package and were stored to the ExtDst directory. The installation of the ring utility was available only after the installation of 1C:Enterprise.Distribution and update of the ring utility and its license module are more convenient. To install or update the licensing utility, you do not have to install the entire 1C:Enterprise.
Software licensing.
New feature: upon activating ("activate" command) a software license and upon creating a response file ("acquire" command) with the ring utility, you can specify an alternative Licensing Center. A Licensing Center can be set in the ExternalResourcesMode parameter of the conf.cfg file.

New parameter for the "ring license activate" and "ring license acquire" commands: --conf-location, which is used to specify the directory for the conf.cfg file.

This feature was not provided.

Only one Licensing Center was available.

Licensing Center selection is similar to selection of other internet resources required by 1C:Enterprise. The system behavior is more consistent.
Internet-enabled functionality.
Data display.
New feature: client applications that run on Windows use WebKit library to manage help, Syntax Assistant, HTML document fields, planner, formatted documents, and HTML document editor. In these cases, Microsoft Internet Explorer is no longer applicable.

WebKit is included into 1C:Enterprise distribution package and does not require separate installation.

The HTMLDocumentField.Document property value type is ExternalObject. The DOM model that can be accessed by this property is changed.

We recommend that you review the use of HTMLDocumentField form item in your applications and update applications that use features specific for Microsoft Internet Explorer.

Client applications that ran on Windows used Microsoft Internet Explorer to manage help, Syntax Assistant, HTML document fields, planner, formatted documents, and HTML document editor.Managing HTML documents is more consistent, regardless of the operating system.
Infobase operations.
New feature to ensure the correct identification of two-digit years: the first year of the century. The default first year of the century is changed from 1930 to 1950, meaning 49 is identified as 2049 and 50 as 1950. In a separated infobase, each data area defined by a set of independent separators has its own first year of the century.

New global context methods: SetInfobaseBeginningOfCentury(), GetInfobaseBeginningOfCentury(), and SessionBeginningOfCentury().

The default first year of the century to identify two-digit years was 1930. The year could not be changed.System behavior related to two-digit years is more transparent. You can customize the first year of the century.
Web client.
Development tools.
Upgrade: for a file infobase published on a web server, connecting the web client to the infobase in debug mode is only allowed if the infobase was published with the option that allows debugging. Otherwise, debugging is not available.

To debug an application using the web client with a file infobase, you have to republish the infobase with debugging allowed.

Debugging applications using the web client with a file infobase was available regardless of the debugging status in the infobase publishing settings.Eliminated unexpected system behavior.
Configuration extensions.
Access rights.
New pattern of roles–extensions interaction:
  • Users have access to all extension objects if the extension and the extended configuration do not contain roles.
  • "Set rights for new objects" role property in the extended configuration also covers the extension objects.
  • "Set rights for attributes and tabular sections by default" role property in the extended configuration also covers the extension objects.
  • "Set rights for native attributes and tabular sections by default" role property in the extension's native role also covers attributes and tabular sections of the adopted extension objects.

+Adopt roles into extensions only when you need to set the extension object rights that do not match the extended configuration's default rights.

Upgrade: DefaultRoles property can be expanded.

This pattern is ignored in 8.3.13 version compatibility mode.

Old pattern of roles–extensions interaction:
  • Users had access to all extension objects if the extension did not contain roles.
  • To set rights for extension objects (including attributes and tabular sections) you had to adopt all roles you needed to change into the extension.
More convenient roles–extensions interaction pattern. The interaction logic is more transparent.
Charts.
Data composition system.
New chart tooltip types and view options. New feature: reference lines and tooltips can be displayed at the same time.

New properties for the Chart object: ChartValuesTooltipDisplayMode, ValueTooltipFillType, PointsPopUpReferenceLineRepresentation, and ValuesPopUpReferenceLineRepresentation.

New feature: chart items can be selected manually or programmatically. A selection can include nonadjacent items.

New property for the Chart object: SelectionMode. New event and methods for chart field extensions of field forms. Event: OnActivate. Methods: GetSelectedItems() and SetSelectedItems(). New methods for the SpreadsheetDocumentDrawing object: GetSelectedItems() and SetSelectedItems().

New properties for the DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance objects: ChartType.ValueTooltipDisplayMode, ChartType.ChartValuesTooltipFillType, ChartType.PointsPopUpReferenceLineRepresentation, ChartType.ValuesPopUpReferenceLineRepresentation, and ChartType.SelectionMode.

The following chart features were available:
  • Upon hovering over a chart item, display a tooltip.
  • Upon double-clicking a chart item, trigger the Selection event.
  • Upon double-clicking a chart value, point, or series with details, trigger the DetailProcessing event.
Improved chart interactivity.
Managed forms.
Upgrade: if a form input field contains a value of reference type, its ChoiceFoldersAndItems property value set to Auto is interpreted as Items.

This upgrade is ignored in 8.3.13 version compatibility mode.

If a form input field contained a value of reference type, its ChoiceFoldersAndItems property value set to Auto was interpreted as FoldersAndItems.Eliminated unexpected system behavior.
Data composition system.
Upgrade: upon generation of a data set selection query, the data composition template generator makes an attempt to aggregate the data using the DBMS query language. Query language functions applied to a single field for data aggregation: SUM(), MINIMUM(), and MAXIMUM().

New property that manages aggregate calculation with query language: DataCompositionSchemaDataSetQuery.UseQueryGroupsIfPossible.

This upgrade is ignored in 8.3.13 version compatibility mode.

The data composition system did not use grouping to aggregate data in queries, unless it was explicitly specified by the GROUP BY clause.Improved data acquisition by the data composition system in some cases.
Data composition system.
New comparison algorithm for arrays, value tables, and other nonprimitive types in the data composition system:
  • For arrays, the algorithm output is the result of element-by-element comparison.
  • For value tables, the algorithm output is the result of element-by-element comparison.
  • For objects of types other than primitive, reference, array, and value table types, the following comparison algorithm is applied:

    • +

    This upgrade is ignored in 8.3.13 version compatibility mode.

The algorithm output for objects of the same type (including arrays and value tables, excluding objects of primitive type and reference type) was comparison of the object RAM addresses. +Eliminated unexpected system behavior.
Server clusters.
Administration tools.
New properties for the IClusterInfo object: ErrorsCountThreshold (the number of server errors that is considered critical) and KillProblemProcesses (force closes corrupted processes).This feature was not provided.Eliminated unexpected system behavior.
Queries.
Upgrade: if a query selection list does not contain tabular section attributes, but the query contains a comparison of tabular section attributes combined with "AND" operator, the conditions are applied together to each tabular section row.

This upgrade is ignored in 8.3.13 version compatibility mode.

If a query selection list did not contain tabular section attributes, but the query contained a comparison of tabular section attributes combined with "AND" operator, the conditions were applied separately, which could lead to incorrect comparison results.Eliminated unexpected system behavior.
Pictures.
New feature: you can use 1C:Enterprise language to change picture parameters, such as format, size, DPI, and color depth. New picture management logic:
  • The Picture object contains only picture details and supports picture reading and writing.
  • New object for picture editing: PictureToProcess.

New methods for the Picture object: Width(), Height(), ColorDepth(), GrayScale(), HorizontalDensity(), VerticalDensity(), and FileSize().

The Picture.Convert() method is deprecated. The PictureProcessor object is deprecated. All PictureProcessor object's methods have matching PictureToProcess object's methods.

We recommend that you analyze your applications and replace the deprecated methods and objects with the new ones.

These features were not provided.

The only editable picture parameter was picture format.

You can change the parameters of any picture stored in an infobase, for example when you need to send it to a third party having specific requirements to pictures.

Table of contents

Renamed objects

ObjectThe old nameThe new name
The name of the type that describes client application forms.
  • ManagedForm.
  • ClientApplicationForm.
Spreadsheet document form field extension handler that is called upon an area selection in a spreadsheet document or an action in a chart.

In 8.3.13 version compatibility mode, the renaming is ignored.

We recommend that you analyze your applications and rename handlers of this type.

  • OnActivateArea().
  • OnActivate().
Columns on Data composition tab, Query wizard.Use subordinate fieldsUse attributes

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile platform.
Development tools.
New feature for the mobile platform: report generation based on the data composition system (including data composition system settings dialog boxes).

New configuration properties for mobile applications: Default report form, Default report settings form, and Default report option form.

Upgrade: data composition system settings forms are adjusted for mobile devices.

This feature was not provided.

The mobile platform did not support reports. The data composition system supported only preprogrammed reports without user interaction.

The mobile platform supports reports, including user interaction (users can customize reports).
Mobile platform.
Mobile client.
Mobile application builder.
Upgrade: you can turn off some advertising features when building a mobile application. To turn off the features, clear the Ads check box in the mobile application permissions.This feature was not provided.Publishing mobile applications in app stores is more convenient.
Mobile platform.
Mobile client.
New objects available in the mobile version of 1C:Enterprise: FontChooseDialog and ColorChooseDialog.These objects were not provided in the mobile version of 1C:Enterprise.Advanced color and font features in the mobile version of 1C:Enterprise.
Mobile platform.
Mobile application builder.
Upgrade: faster creation of an infobase at the first start of a mobile application. The upgrade is valid only if the mobile application has been built by exporting (file 1cema.zip) from Designer v. 8.3.14.

New format of exporting configurations from Designer. Export to an .xml file is no longer supported.

Mobile application builder versions 2.0.8 and earlier do not support configurations exported in the new format. +

Creation of an infobase at the first start of a mobile application took more time.Faster creation of an infobase at the first start of a mobile application.
Mobile device-specific features.
Mobile platform.
New feature for Windows-based mobile applications: support of in-app purchase service (Windows InAppPurchase).

New property: InAppPurchaseService.WindowsInAppPurchase. New feature for the InAppPurchaseReceipt object: a constructor. +

Only iOS and Android-based mobile applications supported in-app purchase services. Windows-based mobile applications support in-app purchase services.
Mobile platform.
Mobile client.
Mobile device-specific features.
New feature: integrate rewarded video ads.

New feature: get rewarded video ad status.

New methods for the AdRepresentationManager object: GetAdStatus(), SetRewardedVideoID(), GetRewardedVideoID(), ShowRewardedVideo(), StartRewardedVideoDownloading(), StartAdBannerDownloading(), and StartRewardedVideoDownloading().

This feature was not provided.Advanced advertising features for mobile applications.
Data display.
New mobile platform feature: custom styles and style elements. The feature is available for configurations imported from 1C:Enterprise platform version 8.3.14 and later.

Mobile application color scheme ignores the NavigationColor, AuxiliaryNavigationColor, and ImportantColor style properties.

This feature was not provided.New options for mobile application appearance management. +

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Queries.
Clarified the error message that appears during an attempt to create a temporary table if the specified temporary table manager has already been closed. The new error text is Cannot use a closed temporary table manager.The error message that appeared at an attempt to create a temporary table if the specified temporary table manager had already been closed might mislead users. The error text was Temporary table manager is not set.Eliminated unexpected system behavior.
Data composition system.
When the data composition system template generator outputs fields to chart grouping templates, it applies conditional appearance to all of the fields. As a result, in reports based on data composition schemas the conditional appearance applied to resource fields is also applied to charts.

This might change the look of reports containing charts with resources that have conditional appearance.

When the data composition system template generator output fields to chart grouping templates, it applied conditional appearance only to nonresource fields.Eliminated unexpected system behavior.
Data composition system.
If a report is displayed in compact mode, reports opened using the Drill down command are also displayed in compact mode.

A setting that shows whether the result is displayed in compact mode is available. The name of the setting key is client application-specific.

New report form parameter: ResultViewMode. Use it to explicitly specify the report view mode.

New method: GetRecommendedCompactWidth(). It returns spreadsheet document cell width. The ConvertToCompactMode() method of spreadsheet document takes its return value as a parameter.

Reports opened using the Drill down command did not inherit the main report mode (compact or normal).Reports opened in the client application using the Drill down command inherit the main report mode.
macOS.
Client application.
Administration tools.
New feature: distribution packages for the thin client running on macOS.

New feature: users can select the version and type of client applications running on macOS.

New feature: uninstall wizard for client applications.

New directory tree in macOS Applications directory.

New directories for some 1C:Enterprise application files.

New feature: you can create self-extracting installers (DMG images) for client applications. The archive can contain 1cestart.cfg configuration file that contains setup, runtime, and update settings. The executable files support macOS only. New utility: 1CEClientSetupMake.

Self-extracting installers for macOS were not provided. Users could not select client application version. Users could select client application type only within one version.

File tree in Application directory was different.

1CEClientSetupMake utility was not provided.

Administration of client applications on macOS is more convenient.
macOS.
Client application.
Administration tools.
New feature: client applications on macOS can be updated over the network. New field in the dialog window for publishing applications on web server where you can specify the path to the client application distribution package. Fields that contain paths to the client application on Windows renamed according to the bitness.

New conf.cfg configuration file parameters: PublishDistributiveLocationMacOS64, PublishDistributiveLocationWindows32, and PublishDistributiveLocationWindows64. The conf.cfg configuration file parameters PublishDistributiveLocation32 and PublishDistributiveLocation64 are obsolete.

New attributes for <point> item of default.vrd configuration file: pubdstmac64, pubdstwin32, and pubdstwin64. The attributes for <point> item of default.vrd configuration file pubdst, pubdst32, and pubdst64 are obsolete.

New feature: 1C:Enterprise on macOS supports launchers stored on network drives.

Upgrade: the web service that receives client application distribution packages supports macOS.

These features were not provided.Client application update is more convenient.
Server clusters.
Standalone server.
New parameters for the standalone server configuration file that define path to client application distribution package on Windows and macOS: win32, win64, and mac64. The parameters x86 and x86_64 are obsolete.The standalone server configuration file supported only Windows operating system.The standalone server configuration file supports macOS operating system.
XML and XDTO support.
Upgrade: the result of a spreadsheet document serialization does not depend on whether the document was transferred between a client and a server. The resulting document always has the same structure.

The upgrade does not affect the appearance of spreadsheet documents and usage of 1C:Enterprise language to manage them.

This upgrade is ignored in 8.3.13 version compatibility mode.

The result of a spreadsheet document serialization depended on whether the document had been transferred between a client and a server. The resulting documents could have different structures.Comparison of spreadsheet documents serialized to XML documents is more convenient.
Mobile client.
Collaboration system.
New feature: the mobile client supports file transfer over the collaboration system.This feature was not provided.New collaboration system features for the mobile client.
Mobile platform.
Mobile application builder.
New configuration export format for the Mobile application builder. The format is supported by the Mobile application builder version 2.0.9 or later. Version 2.0.8 and earlier do not support new format.

Upgrade: faster initial start of mobile applications built with Designer version 8.3.14.

These features were not provided.

The initial mobile application start took more time.

Faster initial start of mobile applications exported in new format.
Mobile application builder.
New feature: you can specify the default application presentation in multiple languages for mobile applications that contain multiple configurations. The default presentation is automatically applied to all new versions of this mobile application.Each new version of a mobile application that contained multiple configurations was based on the first configuration added to the build. Developers had to change the presentation manually.Developing mobile applications that contain multiple configurations is more convenient.
Spreadsheet documents.
Linux.
Server clusters.
Upgrade: 1C:Enterprise server clusters running on Linux process spreadsheet documents faster.1C:Enterprise server clusters running on Linux took more time to process spreadsheet documents.Improved performance of 1C:Enterprise server clusters running on Linux in processing spreadsheet documents.
DBMS operations.
Upgrade: for PostgreSQL DBMS on Windows, the limitation of 1,200 simultaneously open files per PostgreSQL process is removed (the max_files_per_process DBMS parameter).For PostgreSQL on Windows, the limitation of 1,200 simultaneously open files per PostgreSQL process was applied.Improved PostgreSQL DMBS performance with large-size configurations, such as 1C:ERP.
Dumping configurations to files/Restoring configurations from files.
Upgrade: when exporting a configuration to files with 1C:Enterprise version 8.3.14 or later (export format 2.8 or later), the name of the spreadsheet document form field extension event that is called upon selection a spreadsheet document area or upon any operation with the chart is OnActivate regardless of the compatibility mode.

When exporting a configuration to files in export format 2.8 or earlier, the even name OnActivate is equivalent to the event name OnActivateArea.

The name of the spreadsheet document form field extension event that was called upon selection a spreadsheet document area or upon any operation with the chart depended on the compatibility mode.The form item event name does not depend on the compatibility mode. +
Dynamic lists.
Upgrade: in the thin client, users can perform search in a dynamic list composite column by part of the string and by the substring.In the thin client, users could not perform search in a dynamic list composite column by part of the string and by the substring.Eliminated unexpected system behavior.
Mobile application builder.
Upgrade: the Mobile application builder defines the amount of RAM the Java process requires to build Android mobile applications more precisely.

If you use a 32-bit Java version to build an application in a 64-bit environment, a log record that suggests to specify the 64-bit Java in the Mobile application builder settings is created.

In some cases, the Mobile application builder defined incorrect amount of RAM the Java process required to build Android mobile applications. This could lead to build errors due to insufficient memory.

If you used a 32-bit Java version to build an application in a 64-bit environment, a log record that suggests to specify the 64-bit Java in the Mobile application builder settings was not created.

Fixed some bugs that caused insufficient memory errors during Android application building.
Managed forms.
Upgrade: for the Taxi interface on the thin and thick client, if a form field is in the list selection mode, StartChoice event handler ignores standard processing, and the choice list is empty, the drop-down list is always collapsed. The upgrade is ignored in the web client.

This upgrade is ignored in 8.3.13 version compatibility mode.

For the Taxi interface in the thin and thick client, if a form field was in the list selection mode, StartChoice event handler ignored standard processing, and the choice list was empty, the drop-down list was expanded and filled with the choice list values.

In the web client, under the same conditions, the list was always collapsed.

Eliminated unexpected system behavior.
Configuration extensions.
New configuration extension property: DefaultRoles. With this property, you can specify the roles that define accessibility of extension objects when the user list is empty.

New configuration extension property: ForceDefaultRolesForAllUsers. With this property, you can assign all users in an attached extension with the rights defined by the extension default roles. You can edit the property in Designer (extension list) or with the standard extension management function.

When you manage user access rights in Designer, the full name of the role added by an extension is displayed.

When an extension is created, a special role that grants access rights to all objects of the extension is created automatically. DefaultRoles property value is set to this role. You can edit the role without any limitations.

If an extension is attached to a file database in safe mode, access rights to extended configuration objects cannot be granted. This upgrade is ignored in 8.3.13 version compatibility mode.

Developers could not specify default role lists for configuration extensions.

When developers managed user access rights in Designer, the full name of the role added by an extension was unavailable.

When an extension was created, a special role that granted access rights to all objects of the extension was not created.

If an extension was attached to a file database in safe mode, access rights to extended configuration objects could be granted.

Сonfiguration extension access right management is more convenient.
Mobile platform.
Mobile client.
Mobile device-specific features.
Mobile application builder.
New push notification service that supports Windows Push Notification Services (WNS) and Firebase Cloud Messaging (FCM).

The Mobile application builder supports new push notification options.

This feature was not provided.

The notification service supported only Google Cloud Messaging (GCM) and Apple Push Notification Service (APNs).

The notification service is now compliant to the mobile version of 1C:Enterprise.
Mobile platform.
Mobile client.
New features: the mobile version of 1C:Enterprise supports groups for pop-up forms and forms with United property set to False.These features were not provided. +Form management in the mobile version of 1C:Enterprise is more flexible.
Queries.
Upgrade: the query language ValueType() function applied to an expression that contains the IsFolder field returns the correct value.

This upgrade is ignored in 8.3.13 version compatibility mode.

The query language ValueType() function applied to an expression that contained the IsFolder field returned an incorrect value. Result was calculated as if the IsFolder field value contained an inverted value.Eliminated unexpected system behavior.
Queries.
Upgrade: if a parameter expression of the query language ValueType() function contains a virtual field and a primitive type value, the function returns a correct value.

This upgrade is ignored in 8.3.13 version compatibility mode.

If a parameter expression of the query language ValueType() function contained a virtual field and a primitive type value, the function returned an incorrect value.Eliminated unexpected system behavior.
Collaboration system.
Upgrade: user search in the collaboration system is performed only by the beginning of words.

The search algorithm for headings of noncontext group conversations and participant lists of one-to-on conversations is improved. Conversations in search results are ranked higher if they have:

  • Recent messages (the message date is concerned).
  • The search string is at the beginning of the word.
User search in the collaboration system used the string-matching algorithm.

Search result was ranked in the same order order the conversations had been found in the database.

The search algorithm in the collaboration system is improved.
Mobile platform.
Mobile client.
Mobile application builder.
System requirements.
Windows 8.1 and Windows Phone 8.1 operating systems are no longer supported by 1C:Enterprise mobile platform.

New: Windows 10 operating system is supported for ARM architecture.

Upgrade: components of a distribution package of 1C:Enterprise mobile platform is changed (mobile.zip file).

Mobile application builder can no longer build mobile applications for Windows 8.1 and Windows Phone 8.1 using 1C:Enterprise mobile platform 8.3.14 and later.

1C:Enterprise mobile platform supported Windows 8.1 and Windows Phone 8.1.

1C:Enterprise mobile platform did not support Windows 10 for ARM architecture.

A list of supported Windows versions is updated.
Server clusters.
New property AdministrationClusterManager.ClusterManagerID.This feature was not provided.Now you can unambiguously identify a cluster manager upon using the ServerAdministration object.
Data composition system.
Upon adding a filter to query of composition schema data set that includes unions, the filter is necessarily added to every part of the union if automatic filling of available fields is enabled for the data set or the field, to which the filter is applied, is accessed via the point from the field available for filtering.

Besides, if the filter item group contained a field that was not available in one of unions and another field that was available, and if all fields were available in another part of the union, the filter would be applied to the part where it was unavailable, and all unavailable fields would be replaced by NULL.

If a query with unions is used in a report or a dynamic list, and it is required that filter for a particular field is included only in certain union parts, it is recommend that you disable automatic filling of available fields for the data set and add the required field only to the union parts you need.

This upgrade is ignored in 8.3.13 version compatibility mode.

Whenever a filter was added to a query of composition schema data set that included unions, this filter was necessarily added to every part of the union if it could be included at least in one part of the union. In union parts, in which the filter could not be used as fields used in the filter were missing, these fields were replaced by NULL in conditions being added.

Besides, if a filter item group contained a field, which was unavailable in one of the unions, and another field, which was available, and all fields were available in another part of the union, then such filter was applied outside query, on the level of data set of a data composition template.

Now you can create reports, which use queries with unions and in which the filter by some fields can be applied not to all queries inside the union.
Data accelerator.
Queries.
New feature: now Data accelerator supports queries containing the IN HIERARCHY expression.Data accelerator did not support queries containing the IN HIERARCHY expression. +Advanced features of Data accelerator.
Pictures.
The ColorDepth system enumeration is available in Russian in Version 8.3.14 or later compatibility mode only.

In Version 8.3.13 or earlier compatibility mode, this enumeration is available only in the English ColorDepth option.

The ColorDepth system enumeration was available in Russian in any compatibility mode.Resolved the conflict between platform IDs and names of variables of released applications.
Mobile application builder.
Full number of a mobile application built by the Mobile application builder and designed for Windows always has "0" as a last digit in the full application version number.Full number of a mobile application built by the Mobile application builder and designed for Windows had the current build number, which was unique within one mobile application, as a last digit in the full application version number.Now the Mobile application builder meets Windows Store requirements for the version number of a mobile application being published.
Mobile application builder.
Mobile client.
Now you can specify the following upon setting up a mobile client application builder:
  • Server certificate validation method.
  • Сertificate used for server authentication.
  • Сertificate used for client identification.

You can use the specified features if the address of an infobase or a web service with a shared infobase list starts with the "https://" prefix. Otherwise, certificate operations are not available.

This feature was not provided.Now you can use the mobile client if accessing an infobase requires secure connection and placing the required certificates on end-user mobile devices is not available.
XML and XDTO support.
New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as default or fixed ones.Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as default or fixed ones, errors occurred when checking the XDTO model, and such schemas were not available.Eliminated unexpected system behavior.
Data accelerator.
Queries.
New feature: now Data accelerator supports queries using tabular sections and the RECORDAUTONUMBER() query language function.Data accelerator did not support queries using tabular sections and the RECORDAUTONUMBER() query language function.Advanced features of Data accelerator.
Localization.
Localized client application interface for Italian (it).This feature was not provided.1C:Enterprise is available to Italian-speaking users.
Interface.
New feature: search bar is available in the All functions dialog box. Search begins when you try to type a search expression in the сonfiguration object tree. The whole list of objects in the dialog box is searched, regardless of whether the branches of the сonfiguration object tree are expanded or not. You can enter several search words in the search bar. In this case, the search will be done using all entered words of the search query. You can also access the search bar by pressing Ctrl+F.

To search using the standard dialog box, press Alt+F. Only expanded branches of the сonfiguration object tree are searched.

Search in the All functions dialog box was available only using the standard search dialog box, which searched only expanded branches of the сonfiguration object tree. This dialog box was accessible by pressing Ctrl+F. In the All functions dialog box, search by several words was not available. +The search in the All functions dialog box is much easier now. +
Software licensing.
Security profiles are not technically blocked in 1C:Enterprise when a PROF license is used. To use security profiles, the user must still have a CORP license.Security profiles were technically blocked in 1C:Enterprise when a PROF license was used.Changed functions in CORP licenses, whose availability is checked technically.
System requirements.
DBMS operations.
PostgreSQL 9.6.6 from AstraLinux Special Edition 1.6 is supported now if the en_US.UTF8 locale is set up in this operating system.PostgreSQL 9.6.6 from AstraLinux Special Edition 1.6 was not supported.Extended list of supported DBMS.
Mobile client.
Collaboration system push notifications are sent to a mobile device using Firebase Cloud Messaging.Collaboration system push notifications were sent to a mobile device using Google Cloud Messaging.Outdated technology of push notification delivery in the collaboration system is no longer used. Upgrade: faster delivery of push notifications from the collaboration system to client mobile devices.
Mobile platform.
Mobile client.
If case of unexpected shutdown of the mobile application, you will be taken to the application list.If case of unexpected shutdown of the mobile application, the mobile application itself was shut down. As a result, it was impossible to restore an infobase from a backup (when using a mobile platform) or change connection settings (when using a mobile client).Improved behavior of the mobile application in case of unexpected shutdown.
Mobile platform.
Mobile client.
Mobile Application Builder.
1C:Enterprise mobile platform now supports 1244x2208 and 2208x1244 splash screens when running Android OS.

Splash screen support of this size is now included in Mobile Application Builder.

1C:Enterprise mobile platform did not support 1244x2208 and 2208x1244 splash screens when running Android OS.

Mobile Application Builder did not support this size for splash screen.

Implemented splash screen support for high-resolution screens when running Android OS. +
Development tools.
Mobile platform.
Mobile client.
You can now create a configuration file of the mobile platform in zip format only. You can no longer create an xml configuration file. The change relates to exporting with both the Designer interactive mode and the Designer command line (/MobileAppWriteFile option).The configuration file of the mobile platform could have zip or xml format.Configuration export format for the 1C:Enterprise mobile platform has changed. +
DBMS operations.
PostgreSQL 10.8 is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 10.9 is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 10.10 is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
Administration tools.
Software licensing.
The 1C:Enterprise licensing utility distribution package includes the following utilities versions:
  • Ring command line utility - version 0.17.0+1.
  • License module - version 0.12.0+3.
  • 1C:Enterprise installer - version 1.6.0+4. +
The 1C:Enterprise licensing utility distribution package included the previous versions of utilities.Minor errors and typos fixed.
Mobile platform.
Documentation.
The documentation describes the directory structure created when publishing a mobile application on a web server with Designer. It also describes the MIME types that the web server must support to be capable of hosting mobile application configurations and application debugging.The documentation did not contain information about data located on the web server after publishing the mobile application with Designer.Updated platform documentation.
Collaboration system.
Implemented the CollaborationSystemAttachment.ContentRemoved property to display the fact of deleting the attachment from the 1C:Enterprise file storage.

Updated the messages displayed when transferring the file with the collaboration system failed.

There was no way to detect from the 1C:Enterprise language that the attachment was removed from the collaboration system file storage.You can now detect that the attachment was removed from the collaboration system file storage.
Collaboration system.
If the 1C:Dialog service is used to operate the collaboration system, the file transfer has the following limitations: Read more.Conditions of storing files in the 1C:Dialog service were not defined.Conditions of storing files in the 1C:Dialog service are now defined.
DBMS operations.
System requirements.
The server cluster can only interact with Oracle Database DBMS provided that Instant Client 10.2.0.5 is installed on the cluster computer.

Oracle Database client libraries were excluded from 1C:Enterprise distribution package.

Oracle Database client libraries were included in 1C:Enterprise distribution package.

The server cluster was able to interact with Oracle Database DBMS with no additional software required.

The 1C:Enterprise distribution package content was changed.

+

System requirements.
Mobile platform.
Mobile client.
Android version 4.0 is no longer supported. +Android version 4.0 was supported. +Ended support for legacy Android versions. +
DBMS operations.
System requirements.
PostgreSQL DBMS 11.5 (x86-64) is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
Mobile application builder.
The mobile application builder supports Firebase Cloud Messaging push notifications (FCM, for Android) and Windows Push Notification Services (WNS, for Windows) when working through 1C:Enterprise secondary service (https://pushnotifications.1c.com). +Google Cloud Messaging service for sending push notifications (GCM, for Android) is disabled when using the 1C:Enterprise secondary service (https://pushnotifications.1c.com) with the mobile application builder. +When using the 1C:Enterprise secondary service (https://pushnotifications.1c.com) with the mobile applications builder, the Apple Push Notification Service (APNs, for iOS) and Google Cloud Messaging (GCM, for Android) were actually available. +When using the 1C:Enterprise secondary service (https://pushnotifications.1c.com) from the mobile applications builder, the builder actually supports the features of the service. +
Development tools.
macOS.
The HASP key driver distribution package has been excluded from the client applications distribution package for macOS. To install the security key driver, you will need to download it from Gemalto website first.The client applications distribution package for macOS included the HASP key driver distribution package.Compliance with Apple requirements is now available. Creating the 1C:Enterprise distribution package, which can be installed on macOS version 10.15 and later, is not available without such compliance.
DBMS operations.
PostgreSQL 10.12 is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 11,7 is now supported.

+

This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
System requirements.
Administration.
1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.92.1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 7.63.1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.
Interface.
The About... window includes the hyperlink Add-in licenses, which opens the list of the third-party add-ins used in 1C:Enterprise.The About... window didn't provide the information about the third-party add-ins used in 1C:Enterprise.Conformity with GNU LGPL v2.1.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
  • Postgres Pro 1C 9.6.18.1,
  • Postgres Pro 1C 10.13.1,
  • Postgres Pro 1C 11.8.1,
  • Postgres Pro Standard 9.6.18.1,
  • Postgres Pro Standard 10.13.1,
  • Postgres Pro Standard 11.8.1,
  • Postgres Pro Enterprise 9.6.18.1,
  • Postgres Pro Enterprise 10.13.1,
  • Postgres Pro Enterprise 11.8.1.
The following Postgres Pro DBMS versions were not supported:
  • Postgres Pro 1C 9.6.18.1,
  • Postgres Pro 1C 10.13.1,
  • Postgres Pro 1C 11.8.1,
  • Postgres Pro Standard 9.6.18.1,
  • Postgres Pro Standard 10.13.1,
  • Postgres Pro Standard 11.8.1,
  • Postgres Pro Enterprise 9.6.18.1,
  • Postgres Pro Enterprise 10.13.1,
  • Postgres Pro Enterprise 11.8.1.
Extended list of supported DBMS.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
  • Postgres Pro 1C 9.6.19.1,
  • Postgres Pro 1C 10.14.1,
  • Postgres Pro 1C 11.9.1,
  • Postgres Pro Standard 9.6.19.1,
  • Postgres Pro Standard 10.14.1,
  • Postgres Pro Standard 11.9.1,
  • Postgres Pro Enterprise 9.6.19.1,
  • Postgres Pro Enterprise 10.14.1,
  • Postgres Pro Enterprise 11.9.1.
The following Postgres Pro DBMS versions were not supported:
  • Postgres Pro 1C 9.6.19.1,
  • Postgres Pro 1C 10.14.1,
  • Postgres Pro 1C 11.9.1,
  • Postgres Pro Standard 9.6.19.1,
  • Postgres Pro Standard 10.14.1,
  • Postgres Pro Standard 11.9.1,
  • Postgres Pro Enterprise 9.6.19.1,
  • Postgres Pro Enterprise 10.14.1,
  • Postgres Pro Enterprise 11.9.1.
Extended list of supported DBMS.
DBMS operations.
PostgreSQL 10.13 (x86-64) is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 11,8 (x86-64) is now supported.

+

This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 12,3 (x86-64) is now supported.

+

This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 10.14 (x86-64) is now supported.This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 11,9 (x86-64) is now supported.

+

This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.
DBMS operations.
PostgreSQL 12,4 (x86-64) is now supported.

+

This PostgreSQL DBMS version was not supported.More PostgreSQL DBMS versions are now supported.

Table of contents

Transition from the previous version to the version 8.3.14

Table of contents

Version 8.3.13

Version 8.3.13 includes known bug fixes and functionality modifications. +

Finished the beta testing of the Designer agent mode.

The local collaboration system server feature graduated from beta. Local collaboration servers require COPR-level client and server licenses.Read more.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.12 is now implemented.Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.11 was implemented.Configurations developed using 1C:Enterprise platform version 8.3.12 or earlier can run on version 8.3.13 without any changes to configuration or to data structures. This allows for transition to version 8.3.13 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.12 after the transition to version 8.3.13, even if you disabled the compatibility mode (if you did, enable it again).
DBMS operations.
System requirements.
PostgreSQL version 10 is supported.PostgreSQL version 10 was not supported.The list of supported DBMS is extended.
Collaboration system.
Implemented 1C:Enterprise. Startup and notifications application. It provides the following features:
  • A single notification center for all client applications (including the web client).
  • Displaying notifications from applications that are not running (available for infobases connected to the agent).
  • Opening a specific conversation when a client application is started or a client application window is maximized.
  • Disabling notifications from a specific infobase.
  • Quick access to 1C:Enterprise applications.

+The application is available for Windows and Linux, and also for Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer. Implemented the option to display the new messages from the collaboration system and the notification center when starting a client application.

Implemented the DisplayUserNotificationList command-line option of the client application startup in the thin, thick, and web clients.

Notifications from a specific application were displayed on a computer only if the application was running on that computer.The collaboration system notifications from a specific application are available even if the application is not running.
Web client.
In the web client an option to specify the OpenID authentication provider (or the list of providers) is implemented. Each specified provider must support the OpenID Connect protocol.

The openidconnect parameter is added to the default.vrd file.

Implemented the OidcSelectedProvider command-line option in the web client.

This feature is not available if the infobase is published from Designer.

This feature is available in the web client only.

This feature was not provided.

Only the 1C:Enterprise infobase could be used as the OpenID authentication provider in the web client.

Expanded the authentication options list in the web client.
Automated testing.
For TestedFormDecoration and TestedFormField objects, implemented the ClickFormattedStringHyperlink() method. The method emulates clicking a hyperlink in a formatted string.This feature was not provided.Extended automated testing capabilities.
InterfaceConfiguration extensions.
Mobile platform.
Mobile client.
Implemented the option to create custom styles and style elements.

The DefaultStyle configuration property is now available in the managed application.

Styles and Style elements are now available in the Common metadata tree branch.

Implemented the following system colors:

  • NavigationColor
  • AuxiliaryNavigationColor
  • ActivityColor
  • ImportantColor
  • AccentColor

In version 8.3.12 compatibility mode, style elements of Color and Font type that are included in a style retain their values, provided that the style was not used in the ordinary application and the values of those style elements were not changed.

The color of several interface items was slightly changed.

In configuration extensions, you can create and adopt styles and style elements. Configuration extensions can override the DefaultStyle property.

This feature was not provided.New options for client application appearance management.
Client application.
The application startup splash can be disabled now. Implemented the DisableSplash command-line option. It is available in the thin, thick and web client.This feature was not provided.

The application startup splash could not be disabled. +

Extended capabilities for 1C:Enterprise integration with third-party systems.
Configuration extensions.
The following objects can now be created in the configuration extension:
  • chart of characteristic types
  • chart of accounts
  • chart of calculation types
  • accumulation register
  • accounting register
  • calculation register

Configuration extension native accumulation registers do not support aggregates.

The records of native and adopted configuration extension documents can now include the configuration extension native registers.

This feature was not provided. Extended configuration extension usage options.
Data display.
Implemented the text declension feature. Implemented the GetStringDeclensions() global context method.This feature was not provided.1C:Enterprise is now capable of declining various texts, for example, in reports and documents.
Background and scheduled jobs.
Implemented the option to wait for the completion of one or several background jobs within the specified period. For BackgroundJob and BackgroundJobsManager objects, implemented WaitForExecutionCompletion() method.

The WaitForCompletion() method is deprecated.

We recommend that you review your algorithms that involve background jobs.

The message informing about waiting for the completion of a background job that is missing from the lists of running and completed jobs is more accurate.

1C:Enterprise can detect situations where the current user that does not have the Administration access right attempts to wait for the completion of a background job started by another user.

This feature was not provided.

Waiting for completion of one or several background jobs was available. If the background job completed abnormally, an exception was thrown.

The message informing about waiting for the completion of a background job that did not exist was not clear.

Simplified waiting for background job completion. Simplified other operations performing while waiting for background job completion.
Server clusters.
New feature: evaluation of CPU load in the current session. The following time spans are available:
  • The current server call
  • The last 5 minutes
  • The entire session

New session properties for the rac utility: cpu-time-current, cpu-time-5min-last, and cpu-time-total. New properties of the ISessionInfo object: cpuTimeCurrent, cpuTimeLast5Min, and cpuTimeAll.

New property of the <CALL> event: CpuTime. It stores the duration of a completed server call (in milliseconds).

New feature: developers can create custom resource consumption counters with multiple indicators, such as CPU time, memory usage, and disk I/O data volume.

The cluster console now supports resource consumption counter management.

New rac utility commands:

  • counter update. Create or edit a resource counter.
  • counter remove. Delete a resource counter.
  • counter values. Display the current counter values.
  • counter list. Display the settings of the selected counter.

Implemented the option to run the following session management operations upon reaching the specified resource consumption values:

  • Terminate both the server call and the session.
  • Terminate the server call without terminating the session (if possible).
  • Decrease the priority of the server call thread.
  • Write the details to the technological log (<ATTN> event).

You can specify resource consumption limits in the cluster console.

New rac utility commands:

  • limit update. Add a limit.
  • limit list. Display the list of limits.

New feature: developers can manage resource consumption with Java interface for 1C:Enterprise server cluster administration (read more). +Resource consumption level feature requires CORP license.

These features were not provided.You can set the resource load limits on the computer with cluster server. Improved system reliability.
Data composition system.
Implemented the DataCompositionUserSettings.GetMainSettingsByUserSettingID() method. This method returns the array of main settings by the user setting ID. It can be used to specify user settings properties that are otherwise read-only.This feature was not provided.Simplified access to user settings of the data composition system.
Spreadsheet documents.
Implemented the option to optimize the view of spreadsheet documents that do not fit the screen width (mostly on mobile devices). The optimization eliminates the need for horizontal scrolling.

For spreadsheet document, implemented GetCompactDocument() method. It returns the compact version of a spreadsheet document. For spreadsheet document, implemented SetAutoWidth() method. It sets the horizontal stretching mode for spreadsheet document columns.

For spreadsheet document, implemented ConvertToCompactMode() and RevertToDefaultMode() methods. They respectively create and delete a copy of a spreadsheet document that fits the width of a small screen. When a spreadsheet document is printed or saved, the original non-optimized spreadsheet document is used as a source.

Implemented the ResultViewMode property of the report managed form field extension. It allows you to manage the report transformation. Implemented the Compact Mode command of the report managed form field extension. It allows you to edit the ResultViewMode property value.

The current report view modes for the mobile client and other client applications are separately stored in the system settings storage.

These features were not provided.

The spreadsheet document could not be transformed to fit the width of the small screen.

Improved spreadsheet document appearance on a small screen (for example the mobile device screen).
Metadata objects.
The option to analyze metadata, stored in .cf or .cfe file, is implemented. Implemented the ConfigurationMetadataObject constructor.

You can now get the configuration name, version, and vendor from the .cf or .cfe file. Implemented the ConfigurationDescription object.

You can now get the list of versions, suitable for the update, and the resulting version number from a .cfu file. Implemented the ConfigurationUpdateDescription object.

This feature was not provided.

The information about the configuration or the configuration update was not available.

Simplified development of automated configuration updating and distribution packages creating tools.
Configuration extensions.
The following configuration properties can now be adopted:
  • main section picture
  • splash
  • logo

You can now adopt the Picture type objects by replacing the current picture.

The following configuration extension properties can now be specified:

  • brief extension information
  • detailed extension information
  • extension copyright
  • vendor information address
  • extension information address.
These features were not provided. Extended configuration extension usage options.
Configuration extensions.
Data exchange.
The extension native exchange plan can now include adopted objects.

You can now adopt the exchange plan data (create exchange plan attributes, tabular sections, and tabular section attributes).

The extension native exchange plan could include the extension native objects only.

The exchange plan data could not be adopted.

More configuration extension management options.
Data history.
You can now override default data history forms. Added the following properties of the Configuration object:
  • DefaultDataHistoryChangeHistoryForm
  • DefaultDataHistoryDataVersionForm
  • DefaultDataHistoryVersionDifferenceForm.

+

Implemented DataHistoryVersionFilterDialog and DataHistoryUsersChooseDialog objects.

Default data history forms overriding was not available.Extended data history options.
Internet-enabled functionality.
Implemented the following HTML document options:
  • Delete all document items of a certain category. Implemented the HTMLDocument.DeleteByCategory() method.
  • Get a string with all readable text from the document. Implemented the HTMLDocument.ExtractPlainText() method.
  • Select all document items by a specific filter. Implemented the HTMLDocument.FindByFilter() method.
  • Delete all document items by a specific filter. Implemented the HTMLDocument.DeleteByFilter() method.
These features were not provided.

The only available option was to cycle HTML document DOM model and perform actions with its items.

Simplified and improved the HTML document performance in particular scenarios (for example if you want to delete all <script> tags)
Internet-enabled functionality.
Emails can now use OAuth2 protocol together with IMAP protocol.

Implemented the following InternetMailProfile object properties: TokenAuthentication and AccessToken.

This feature was not provided.The email servers with the OAuth2 authentication protocol are now supported.
Queries.
A field with consequently increasing unique values can now be added to the temporary table.

Implemented the RECORDAUTONUMBER() query language function. It is available for a temporary table only.

The RECORDAUTONUMBER() function is not supported in the following cases:

  • there is a UNION keyword on the top level
  • query does not create a temporary table
  • outside the selection list
  • in expressions.
This feature was not provided.Simplified adding the unique field with consequently increasing values to a temporary table.
Automated testing.
Implemented the following options of the spreadsheet document extension of the TestedFormField object:
  • Getting the number of columns that contain data. Implemented the GetDocumentDataAreaHorizontalSize() method.
  • Getting the number of rows that contain data. Implemented the GetDocumentDataAreaVerticalSize() method.
These features were not provided.Extended automated testing capabilities.
Data history.
The option to handle the data version restoration in the object module and in the managed form module is now available.

If a form displays one of the older object version, the version number is displayed in the form header.

Implemented a dynamic list command that displays the selected object data history (if supported). It is available for users with ViewDataHistory access right.

Implemented the VersionNumberSwitchToDataHistoryVersion managed form parameter.

Implemented the GenerateFromDataHistoryVersionProcessing() event handler in the following modules:

  • catalog object module
  • document object module
  • chart of accounts object module
  • business process object module
  • task object module
  • information register record set module.

+

This handler is called when the object is generated based on the data history version.

The developer could not handle the object version restoration.

The object history could be displayed in the object form or the register record form only.

Extended data history options. Improved data history security.
Data display.
New pictures were added to the picture library: Conversations, NewConversation, Notifications.The listed pictures were not available in the picture library.More content for the picture library.
Data history.
Implemented the data history of exchange plans, charts of calculation types, and constants.This feature was not provided.Data history is now available for more objects.
Applied objects.
Implemented the ConstantValueKey object.

Implemented the CreateConstantValueKey() method of the constant manager.

This feature was not provided.Expanded constant management capabilities.
Development tools.
Implemented the option to create a macOS-compatible distribution package.

The application distribution package now includes the .zip archive that contains the distribution file and the installer executable files for each supported operating system (Windows, Linux, macOS). The executable files now have the right parameters (Linux, macOS), so you can now unpack the distribution package and install the applicaton.

Implemented the CreativeDistributivePackage command-line option of the Designer batch mode. The CreateDistributive command-line option of the Designer batch mode is deprecated.

Creating an application distribution package for Windows and Linux only was allowed. The application could not be installed on macOS.

There was no option to create an application distribution package with correct executable files for each supported operating system. You had to specify the correct parameter in the Linux executable file to install the application.

You can now install the application on any supported operating system.

The distribution package is now compatible to any supported operating system.

System requirements.
Configuration repositories.
Implemented the 64-bit configuration repository server on Linux.There was only the 32-bit configuration repository server available on Linux.The functionality of configuration repository server is now fully available on 64-bit Linux.
Data history.
Implemented the option to force the update of data history of specific infobase object. Imolemented the UpdateHistory() method of the DataHistory object.This feature was not provided.

The data history update was available for all infobase objects at once only. If a specific object data history form was opened, some versions might not be displayed.

The specific object data history form now displays the full history.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Collaboration system.
Converstation participants receive notifications in the conversation form if one of them is typing a message.

The following user statuses are now available: offline, away, do not disturb, and online. The Away status is available in thick and thin clients on Windows only.

Updated the new message notification.

You can now start a conversation with user from the user information form.

Updated the collaboration system main window.

Updated Collaboration system management standard function. Updated registration and cancelling registration forms.

These features were not provided.Improved the collaboration system interface.
Interface.
Implemented the following changes In the Taxi interface:
  • Managed form cell indents are reduced proportionally to the managed form scale if it is less than 100%. Implemented the factor of proportionality.
  • When the managed form scale is 80%, the table row height equals to the table row height in the compact mode, depending on the font and the screen DPI.
  • Reduced left and right table cell indents.
  • Reduced left and right indents of spreadsheet document columns generated by the Output list command.
The Taxi interface behaved the following way:
  • There was no factor of proportionality in reducing the managed form table cell indents.
  • Left and right table cell indents were wider.
  • Left and right indents of a spreadsheet document columns generated by the Output list command, were wider.
Improved the spreadsheet document and managed form table appearance in managed form with custom scale.
Interface.
All incorrect links are displayed as a link (not link's presentation). When the user favorites settings dialog box is closed, incorrect links remain in the favorites list and can be used or edited.

Implemented the URLPresentation.Presentation() method.

The GetURLsPresentations() method always returns the array of URLPresentation objects. Each URLPresentation object in this array will have different values depending on the link.

This change is not implemented in version 8.3.12 compatibility mode.

Incorrect links had a blank interface presentation and were not available.

They were deleted from the user work history after the user favorites settings dialog box was closed.

The GetURLsPresentations() method applied to an incorrect link returned Undefined.

Improved links performance.
Web client.
Spreadsheet documents.
Eliminated spreadsheet document printing faults in the web client if the HTML print method is selected.A spreadsheet document might be printed with faults in the web client if the HTML print method was selected.Eliminated unexpected system behavior.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Information registers.
Implemented the cluster index based on dimensions of slice first and slice last physical tables of an information register. Index structure description Read more..

Disabled index uniqueness verification.

Optimized performance of queries operating with slice tables.

This index can be built the following ways:

  • restructuring the information register
  • database restructuring when the verification and repair operation is performed. +
Physical slice first and slice last tables were not indexed.

The performance of the queries operating with slice tables was not optimal.

Improved physical slice tables performance in configurations with large number of users. Eliminated deadlocks when updating the physical slice tables.
Full-text search.
Reduced the size of temporary files created during the update of full-text search index. This change affects infobases with many separators the most.

The new temporary file format is used when the compatibility mode is disabled.

This change is not implemented in version 8.3.12 compatibility mode.

Temporary files created during the update of full-text search index were significantly larger.Reduced the disk space allocated for a full-text search index generating when the infobase contains many separators.
DBMS operations.
Improved performance of virtual turnover tables of accumulation and accounting registers when they are grouped by day, month, or year, or when the BeginOfPeriod() query language function is used.

This change is available in all supported DBMS, except for Microsoft SQL Server versions earlier than 2012.

Performance of virtual turnover tables of accumulation and accounting registers when they were grouped by day, month, or year, or when the BeginOfPeriod() query language function was used, was suboptimal.Improved performance of virtual turnover tables of accumulation and accounting registers.
Common objects.
Improved performance of the following ValueTreeRowCollection object methods: Remove(), Insert(), Index(), and Move(). The performance of the following ValueTreeRowCollection object methods was insufficient: Remove(), Insert(), Index(), and Move().Improved performance of the value tree rows from 1C:Enterprise script.
External reports and data processors.
Improved performance of loading external reports and data processors opened by large number of users.Loading external reports and data processors opened by large number of users was longer.Improved performance of loading external reports and data processors opened by large number of users.
Background and scheduled jobs.
Configuration extensions.
Improved performance of second and further background job startups if they use the same set of configuration extensions. This change is available In file mode.In file mode second and further background job startups were longer even if they used the same set of configuration extensions.Improved background job startups in the file mode if they are operating with configuration extensions.
Common objects.
Optimized filling and deleting rows of a table of values.Filling and deleting rows of a table of values were longer.Improved table of values performance.
Web client.
Optimized page titles (tabs) rendering in the web client.Page titles (tabs) rendering in the web client was slow and suboptimal.Eliminated unexpected system behavior.
Common attributes / Data separation.
Improved opening forms performance in a configuration that uses common attributes.Forms opened relatively slow if a configuration used common attributes.Forms in a configuration that uses common attributes now open faster.
Data composition system.
Sometimes the data composition system template composer attempts to sort the data set by the DBMS means. The data composition system does not use it's own means in these cases. But the composition result may be incorrect because the row comparison operations are different in various DBMS and 1C:Enterprise platform.

This change is not implemented in version 8.3.12 compatibility mode.

Data composition system template composer always sorts the data set by the data composition system means.Improved the sorting performance during the report building in some scenarios.
Data composition system.
Improved the data composition system template generation if the data composition schema is composed of many queries that generate temporary tables with many fields that are not used in the composition process.The data composition system template generation process was longer if the data composition schema was composed of many queries that generated temporary tables with many fields that were not used in the composition process.Improved complex reports with many temporary tables building performance.
Queries.
If a query contains an IN subquery then a join with table from the IN subquery is used instead. This change is performed only if it does not affect the query result.

This change is not implemented in version 8.3.12 compatibility mode.

If a query contained an IN subquery, the DBMS always used this subquery.Improved the DBMS query plan in some scenarios.
Development tools.
Server clusters.
Improved the configuration database update performance when it is initiated from a debug session in client/server mode.The configuration database update was longer when it was initiated from a debug session in client/server mode.Improved the configuration database update performance when it is initiated from a debug session in client/server mode.
Spreadsheet documents.
Improved the CheckPut() method performance if a spreadsheet document contains multiple sheets.The CheckPut() method performance for a spreadsheet document with many sheets was insufficient. Improved performance of spreadsheet document display.
Spreadsheet documents.
Improved copying to clipboard performance. Improved the GetArea() spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting.Copying to clipboard performance and the GetArea() spreadsheet document method performance when applied to the spreadsheet document area with multiple rows with custom column formatting were insufficientImproved performance of obtaining the spreadsheet document area with multiple rows with custom column formatting.
Spreadsheet documents.
Web client.
Improved performance of spreadsheet document groups collapsing and expanding in the web client.The collapsing and expanding of spreadsheet document groups in the web client was longer.Improved spreadsheet document performance in the web client.
Background and scheduled jobs.
Improved the background jobs execution and waiting for their completion.The background jobs execution and waiting for their completion were longer.The background jobs execution and waiting for their completion are now faster.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Collaboration system.
Implemented the correct data area switching when a collaboration server is used. If the new data area is already registered in the collaboration server, this registration will be used.This feature was not provided.

The reconnection to the collaboration server was not performed if the data area was switched. +

Eliminated unexpected system behavior.
Managed forms.
Changed the selected row view of the managed form table in the Taxi interface. The current row color now affects the selected row view.The current row color did not affect the selected row view in the Taxi interface.Improved the selected row view of the managed form table in the Taxi interface.
Development tools.
Modules locked with password are ignored in the Designer batch mode.

A diagnostic message is displayed instead. +

When modules locked with password were accessed in the Designer batch mode, the password request dialog box might be displayed.Eliminated all interactive actions in the Designer batch mode, which does not support them.
Data display.
If the space is used as a group separator in the format string wizard the resulting format string the will use the nonbreaking space instead.If the space was used as a group separator in the format string wizard the space was used in the resulting format string too.Eliminated unexpected system behavior.

Decreased number of issues caused by the incorrect group separator.

Collaboration system.
Implemented noncontext conversations with two participants (face-to-face). Other users can not take part in such conversations.

Implemented the CollaborationSystemConversation.Group and CollaborationSystemConversationsFilter.Group properties.

Implemented the capability to combine subscribers applications (infobases or data areas). Implemented the capability to match users of different applications. Implemented the capability to combine context conversations from different applications. Only the subscriber owner can perform the listed above actions.

The Collaboration system management standard function can now merge applications, cancel applications merging, match users and context conversations.

Implemented the CollaborationSystemUser.MappingKey property. Implemented the following methods of the collaboration system manager:

  • CurrentApplicationID()
  • GetApplication()
  • GetSubscriberApplications()
  • SetSubscriberApplicationLinks()
  • CancelSubscriberApplicationLinks()
  • GetSubscriberApplicationLinks().
These features were not provided.

The collaboration might be established only within a single subscriber application. +

Expanded the collaboration system capabilities.
Development tools.
Error and warnings that are generated by the metadata check, are now displayed as dbstru type messages.

Implemented the DBRestuctError value for the error-type message. It describes the infobase restructuring error.

Implemented the CommandFormatError value for the error-type message. It describes the invalid command format error. +

Error and warnings that were generated by the metadata check, were displayed as log type messages.Improved the diagnostics of issues that occur in the Designer agent mode.
Data composition system.
The composite type child fields are available in user settings if the user has the View right to at least one table of that type and the field itself. The composite type child field can be used in filters, sorting, conditional appearance and other available user settings.

Implemented the RestrictGettingFieldsByRefByViewRight property of the DataCompositionProcessor.Initialize() method.

This change is not implemented in version 8.3.12 compatibility mode.

If the user did not have the View right to at least one table of the composite type, there were no child fields of the locked type in the user settings.The user can now obtain the child fields data that he has a View right on.
Charts.
The following options are now available in the chart type input field:
  • The picture of a selected chart type is displayed in the input field.
  • The picture of chart type is displayed in the chart type selection list.
  • Implemented the autoselection when typing the chart name.
  • Implemented the input field selection button that opens the chart type selection dialog box.

Implemented the ChartTypeChooseDialog object.

This change is not implemented in version 8.3.12 compatibility mode.

The chart type input field behavior was the following:
  • There was no selected chart type picture in the input field.
  • There was no chart type picture in the selection list.
  • There was no autoselection when typing the chart name.
  • There was no selection button that opened the chart type selection dialog box.
Improved the chart type selection in some scenarios.
Collaboration system.
The video call can not be performed if one of the participants do not have the microphone available. The appropriate message is generated.

The collaboration system displays the microphone and camera diagnostic icons during the conversation.

The hardware diagnostics was not performed before and during the video call.Eliminated unexpected system behavior.
Development tools.
The attribute or the tabular section can not be named Presentation if it is stored in the database.

This change is not implemented in version 8.3.12 compatibility mode.

An attribute or a tabular section could be named Presentation, but this might cause different issues.Eliminated unexpected system behavior.
Managed forms.
Implemented the following changes, when managed form tabs are displayed to the left or right of the Pages item:
  • The height of tabs headers is not affected by the form height. You can now scroll tabs headers vertically if they do not fit the form height.
  • You can use the wheel button to scroll tabs headers.
  • You can now use touchscreen to scroll tabs headers in the thin client on Windows.
When managed form tabs were displayed to the left or right of the Pages, the tabs headers height was decreased to fit the form height. +Eliminated unexpected system behavior.
Managed forms.
Mobile client.
The different form Auto values of managed form table HeightControlVariant property can now be used in configurations with version 8.3.7 or earlier compatibility mode.The different form Auto values of managed form table HeightControlVariant property were used in configurations with version 8.3.10 or earlier compatibility mode.Options of controlling the height of managed form table are now compliant with the mobile client.
Managed forms.
Dynamic lists.
If the main table of the dynamic list has both groups and elements, the form conditional appearance is applied to columns that are not linked with the main table, regardless whether the current row displays either an element or a group of the main table.

This change is not implemented in version 8.3.12 compatibility mode.

If the main table of the dynamic list had both groups and elements, the form conditional appearance was applied to columns that were not linked with the main table, in the following way:
  • to a column that displays the common field (not expresiion) provided that the current row displays the main table element.
  • otherwise the form conditional appearance is applied when the current row displays the main table group.
Eliminated unexpected system behavior.
Accounting registers.
If the Period adjustment property of an accounting register is greater than 0, the PeriodAdjustment standard attribute is displayed in the edit standard attributes form and becomes available in the StandardAttributes collection of the AccountingRegister metadata object (there is no PeriodAdjustment attribute in the StandardAttributes collection in version 8.3.12 compatibility mode). +The PeriodAdjustment standard attribute was not displayed in the edit standard attributes form and was not available in the StandardAttributes collection of the AccountingRegister metadata object.Eliminated unexpected system behavior.
Database configuration update.
If an infobase compatibility mode is Version 8.3.10 or earlier and its database configuration was changed in 1C:Enterprise version 8.3.10 or earlier, the chance of getting a message about incomplete configuration structure conversion when opening the infobase in a client application version 8.3.13 is reduced.If an infobase compatibility mode was Version 8.3.10 or earlier and its database configuration was changed in 1C:Enterprise version 8.3.10 or earlier, an attempt to open the infobase in a client application version 8.3.11 could not be completed. It returned a message about incomplete configuration structure conversion. The only way to recover the infobase was to open it in Designer version 8.3.11 or later and run infobase restructuring.Smoother migration from 1C:Enterprise version 8.3.10 to later versions.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Data composition system.
Charts.
The processor of data composition result output sets the automatic column width calculation for all cells in the spreadsheet document area that contains a chart.

This change is not implemented in version 8.3.12 compatibility mode.

The processor of data composition result output did not set the automatic column width calculation for all cells in the spreadsheet document area that contained a chart.Eliminated unexpected system behavior.
Data composition system.
If the predefined grouping templates are used during the table columns output, then the grand totals template height is automatically calculated to fit all resource headers. The template generator automatically increases the predefined grouping template height If it is less than the grand totals template height.

This change is not implemented in version 8.3.12 compatibility mode.

If the predefined grouping templates were used in the table columns output and the grand totals template height was greater than the predefined grouping templates height, some resource headers might not be displayed in the grand totals template.Eliminated unexpected system behavior.
Collaboration system.
Implemented the CollaborationSystemManager.IsEnabled() method. It returns the following flags:
  • The infobase is registered in the collaboration service.
  • The infobase registration is active.
  • There are collaboration system users in the infobase.

The CollaborationSystemManager.InfoBaseRegistered() method returns whether the infobase is registered in the collaboration service and the registration is active. This change is not implemented in version 8.3.12 compatibility mode.

The CollaborationSystemManager.InfoBaseRegistered() method returned the following flags:
  • The infobase was registered in the collaboration service.
  • The infobase registration was active.
  • There were collaboration system users in the infobase.
You can now get the information about the infobase registration and the collaboration system availability separately.
Spreadsheet documents.
The spreadsheet document width and height (PageHeight and PageWidth properties) are limited to 5000 mm.

This change is not implemented in version 8.3.12 compatibility mode.

The spreadsheet document width and height (PageHeight and PageWidth properties) were unlimited.Eliminated problems of the spreadsheet document with large pages export to other formats.
Data composition system.
If an unavailable property of a data composition system object is accessed, an exception is thrown.
  • The UserSettingPresentation property of DataCompositionFilter, DataCompositionSelectedFields, DataCompositionConditionalAppearance objects.
  • The UserSettingPresentation, Presentation, LeftValue, Application, Parent properties of the DataCompositionFilterItem object.
  • The UserSettingPresentation, Presentation, Application, Parent, GroupType, Items properties of the DataCompositionFilterItemGroup object.
  • The UserSettingPresentation, Presentation, Fields, Filter, UseInGroup, UseInHeader, UseInFieldsHeader, UseInHierarchicalGroup, UseInOverall, UseInFilter, UseInParameters properties of the DataCompositionConditionalAppearanceItem object.
  • The UserSettingPresentation, NestedParameterValues, Parent, Parameter (only when setting the property value) properties of the DataCompositionSettingsParameterValue object.
  • The UserSettingPresentation, ID, Name, Choice, Filter, OutputParameters, GroupFields, Order, Parent, State, Structure, ConditionalAppearance properties of the DataCompositionGroup, DataCompositionTableGroup, DataCompositionChartGroup objects.
  • The UserSettingPresentation, Choice, ID, Name, Columns, OutputParameters, Parent, Strings, ConditionalAppearance properties of the DataCompositionTable object.
  • The UserSettingPresentation, Choice, ID, Name, OutputParameters, Parent, Sreies, Points, ConditionalAppearance properties of the DataCompositionChart object.
  • The UserSettingPresentation, ID, ObjectID, Name, Settings, Parent properties of the DataCompositionNestedObjectSettings object.
  • The UserSettingPresentation and ViewMode properties of the DataCompositionSettingStructureItemCollection object. This change is available only if the parent of the DataCompositionSettingStructureItemCollection object is a DataCompositionSettingStructure type object that is included in the DataCompositionUserSettingsItemCollection collection.

This change is not implemented in version 8.3.12 compatibility mode. +

Accessing the listed above properties of the user settings objects was meaningless and did not throw an exception.Eliminated the incorrect accessing to data composition system object properties.
Background and scheduled jobs.
The maximum size of serialized background job parameters is 1 GB. Otherwise an exception is thrown.

If the version 8.3.12 compatibility mode is set, an exception is thrown if the size of serialized background job parameters is greater than 2 GB.

If the size of serialized background job parameters was greater than 2 GB the session was abnormally terminated.Improved background jobs stability. Decreased the background job impact on the system performance if very large parameters were sent.
Dynamic lists.
The OnChange event occurs once per deleting dynamic list rows in the thin client.

This change is not implemented in version 8.3.12 compatibility mode.

The OnChange event might occur multiple times when dynamic list rows were deleted in the thin client. The number of event calls depended on the deleted rows number:
  • less or equal to 100 rows. The number of event calls was equal to the rows number.
  • more than 100 rows. The event was called once.
Eliminated unexpected system behavior.
Common objects.
The Font object constructor returns the Common style text font if the FontName constructor parameter is not specified.

This change is not implemented in version 8.3.12 compatibility mode.

The Font object constructor returned Dialog and menu font if the FontName constructor parameter was not specified. +Eliminated unexpected system behavior.
System requirements.
Linux.
The ImageMagick library from the 1C:Enterprise platform distribution package is used.The ImageMagick library from the operating system was used.Reduced the number of issues that might arise due to the incorrect ImageMagic library version in the operating system.
Managed forms.
The AddRow(), ChangeRow(), CopyRow() and EndEditRow() methods of the ManagedFormTable object do not perform any actions if their related interactive commands are not available.

This change is not implemented in version 8.3.12 compatibility mode.

The behavior of the AddRow(), ChangeRow(), CopyRow() and EndEditRow() methods of the ManagedFormTable object depended on the client application type.

In the thin client they performed the related actions. +In the web client no actions were performed.

Eliminated unexpected system behavior.
Development tools.
The English version of ID, attribute name and metadata object name is now saved in the configuration merge settings file.

The following actions are performed when reading the configuration merge settings file: attempt to read IDs in English. If failed, attemt to read IDs in Russian.

The version of ID, attribute name and metadata object name that were saved in the configuration merge settings file, depended on the configuration script variant.The result of the configuration merge settings loading does not depend on the configuration script variant.
Web client.
File operations.
Improved web client file operations.

Implemented the new file selection dialog box. It supports multiple file choice and dragging. The file system extension is not required for this dialog box.

Implemented the limited editing of the file selection dialog box BeginPutFile() and BeginPuttingFiles() methods.

The BeginPutFile() method does not require the file system extension installed.

Added the option to manage specific parameters of files before transfering them to server. Implemented the BeforeBeginPuttingFilesNotificationDescriprion parameter of the BeginPutFile() and BeginPuttingFiles() methods.

Implemented the FullName and FileID properties of the TransferredFileDescription object. The Name property of the TransferredFileDescription contains only the transferred file name. The BeginPutFile() method allows other calls and methods in the thin client. This change is not implemented in version 8.3.12 compatibility mode. +You can now drag files on the following form items: managed form field extension for a picture, managed form decoration extension for a picture, and managed form table. Implemented the FileDragMode property of the listed above managed form items. Implemented the FileRef object.

The PutFile(), PutFiles(), and GetFiles() methods are deprecated.

It is recommended to rework file operations in applications that use the web client.

The file operations in the web client were limited if the file system extension was not installed.

In the thin client, while the BeginPutFile() method was being executed, calls of other methods were not allowed.

The TransferredFileDescription.Name property contained the full file name.

Expanded the file operations in the web client that do not require the file system extension installed. The web client supports and handles the file dragging.
Charts.
If the chart data contains non-numeric values (NULL or Undefined), the chart behavior can be specified. Implemented the NonnumericValueUse and PointsConnectionAcrossSkippedValues properties of the Chart object.

Implemented the ChartType.NonnumericValueUse and ChartType.PointsConnectionAcrossSkippedValues properties of the following objects: DataCompositionOutputParameterValues, DataCompositionChartOutputParameterValues, DataCompositionAreaTemplateChartAppearance.

If displaying of a series marker is disabled (ChartMarkerType.None is set) and a series value in some point is separated (values in the next and previous points are omitted), then this value is displayed as a circle. The width of the circle line equals to the series line width. Chart lines connections are now rounded. This change is not implemented in version 8.3.12 compatibility mode.

The chart behavior could not be specified if the chart data contained non-numeric values.

If displaying of a series marker was disabled (ChartMarkerType.None was set) and a series value in some point was separated (values in the next and previous points were omitted), then this value was not displayed on a chart.

The chart lines connection was not rounded.

Expanded operations with charts.
Automated testing.
The TestedFormTable.Expand() method can now expand subordinate nodes on the next level of the selected node only. Implemented the WithSubordinates parameter of the TestedFormTable.Expand() method.

This change is not implemented in version 8.3.12 compatibility mode. +It is recommended to review and rework all code fragments with the TestedFormTable.Expand() method.

The TestedFormTable.Expand() method expanded the selected node and all subordinate nodes.The automated testing features now correspond the 1C:Enterprise platform capabilities.
Data composition system.
Dynamic lists.
External data sources.
If a dynamic list field in a report may be NULL, the following ordering rule is applied to that field: NULL values come first.

If a dynamic list field is based on an external data source table field, and the external data source contains the CASE ... WHEN selection that might return NULL, the following ordering rule is applied to that field: NULL values come first.

This change is not implemented in version 8.3.12 compatibility mode.

If a dynamic list was ordered by a field that might be NULL , rows with NULL and with the default field type value were placed together.

If a dynamic list was ordered by a field that was based on the external data source table of any type, the final ordering depended on the DBMS type.

Dynamic list ordering by the field that might be NULL rule is now the same as the other objects ordering rule.
Managed forms.
When the AutoMarkIncomplete property of a managed form table is set to True, the MarkIncomplete property of that table obtains the correct value after the script execution.

This change is not implemented in version 8.3.12 compatibility mode.

The MarkIncomplete property of a managed form table was refreshed only when the table was refreshed or the current table cell was changed. +Eliminated unexpected system behavior.
Queries.
The IS NULL function returns FALSE if it is applied to the combination of virtual fields. The IS NULL function returns TRUE if it is applied to the combination of virtual fields and the expression without virtual fields that returns NULL. The IS NULL function returns FALSE if it is applied to the combination of virtual fields and the expression without virtual fields that does not return NULL.

This change is not implemented in version 8.3.12 compatibility mode.

It is recommended to review all IS NULL functions in existing applications.

The IS NULL function returned FALSE if it was applied to the combination of virtual fields or to the combination of virtual fields and the expression without virtual fields.Eliminated unexpected system behavior.
File operations.
Server clusters.
If a security profile that blocks access to the file system is set in the infobase, the TempFilesDir() and GetTempFileName() global context methods return paths with separators, provided by the current operating system.If a security profile that blocked access to the file system was set in the infobase, the TempFilesDir() and GetTempFileName() global context methods returned paths with separators, provided by the Linux operating system.Eliminated unexpected system behavior.
File operations.
If the parameter of the following File object methods is set to date before the January 1, 1601 in the Windows operating system, these methods throw the File access denied exception:
  • SetModificationTime()
  • SetModificationUniversalTime()
  • BeginSettingModificationTime()
  • BeginSettingModificationUniversalTime().

All errors of File object methods throw the same exception.

If the parameter of the following File object methods was set to date before the January 1, 1601 in the Windows operating system, these methods returned the random date:
  • SetModificationTime()
  • SetModificationUniversalTime()
  • BeginSettingModificationTime()
  • BeginSettingModificationUniversalTime().
Eliminated unexpected system behavior.
Data composition system.
If the CASE operation is used in the data composition system calculated expression, and the resulting field type is unknown (it is a values table field or the field type is not specified) and the ELSE section contains the Undefined value, the result field type in the result values collection will be set to Custom (the type description will be blank).

This change is not implemented in version 8.3.12 compatibility mode.

If the CASE operation was used in the data composition system calculated expression, and the resulting field type was unknown (it was a values table field or the field type was not specified) and the ELSE section contained the Undefined value, the result field type in the result values collection would be NULL.Eliminated unexpected system behavior.
Managed forms.
Only methods with the Export keyword are available in expressions containing ThisObject. This change affects from module as well as other modules, where ThisObject is passed.

This change is not implemented in version 8.3.12 compatibility mode.

All methods were available in expressions containing ThisObject.Eliminated unexpected system behavior.
Data composition system.
If a filter with the filled/not filled comparison type is used in the data composition system settings and this filter is applied to the calculated field, which type is custom, Characteristics type, or any reference type, then the filter will consider types, included in the Characteristic, custom type or any reference type.

This change is not implemented in version 8.3.12 compatibility mode.

If a filter with the filled/not filled comparison type was used in the data composition system settings and this filter was applied to the calculated field, which type was custom, Characteristics type, or any reference type, then the filter ignored types, included in the Characteristic, custom type or any reference type.Eliminated unexpected system behavior.
Queries.
If a temporary table is created by the INTO clause, the temporary table field with NULL value has a compound data type. This compound data type includes the following types:
  • Number with 1.0 precision
  • String of 1 character
  • DateTime
  • Boolean
  • NULL

+

It is recommended to review all temporary table fields that might have NULL value.

This change is not implemented in version 8.3.12 compatibility mode.

If a temporary table was created by the INTO clause, the temporary table field with NULL value had NULL type.Temporary table fields with NULL values are now available in expressions that do not support NULL value. The CAST() function can be used in such cases.
Functional options.
If a functional option value is stored in a periodic information register resource, it is obtained from the slice last. The date from the functional option Period parameter, or the current date (if the functional option Period parameter is not specified) is used as a slice last date.

This change is not implemented in version 8.3.12 compatibility mode.

If a functional option value was stored in a periodic information register resource, it was calculated by the logical OR operation across all stored resource values, if only the Period parameter was specified.Eliminated unexpected system behavior.

The system behavior is now compliant to documentation.

Managed forms.
Managed form table rows are filtered if there are multiple filter items and the first item filter value is Undefined.

This change is not implemented in version 8.3.12 compatibility mode. +

Managed form table rows were not filtered if there were multiple filter items and the first item filter value was Undefined.Eliminated unexpected system behavior.

Table of contents

Renamed objects

ObjectThe old nameThe new name
The getting/setting HTML document methods of formatted document extension of the TestedFormField object.

The former names are supported for compatibility purposes.

  • GetHTML()
  • SetHTML()
  • GetDocumentHTML()
  • SetDocumentHTML()

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Mobile device-specific features.
Push notifications on Android use Firebase Cloud Messaging service. It is recommended to transfer push notifications to this platform in current applications.

Implemented the DeliverableNotificationSubscriberType.FCM enumeration value.

The Google Cloud Messaging service is supported for compatibility purposes and is not recommended for use.

The DeliverableNotificationSubscriberType.GCM value is obsolete and supported for compatibility purposes. The GoogleCloudApplicationNumber parameter of the ReceiveNotificationSubscriberID() method is optional on Android.

Push notifications on Android used Google Cloud Messaging service.The legacy push notifications delivery service is no longer used. Transfered to the latest version of the service.
Mobile device-specific features.
Mobile platform.
Mobile client.
Implemented the capability of managing the camera backlight interactively (on Android and Windows Phone) and from the 1C:Enterprise script (on all mobile operating systems).

Implemented the DeviceTools global context property. Implemented the CameraBacklightType parameter of the MultimediaTools.MakePhoto() method.

You can now use a camera flash as a flashlight. Implemented the DeviceTools global context property. Implemented the FlashlightSupported() and TurnFlashlightOn() methods of the device tools manager.

Managing the camera backlight from the 1C:Enterprise script was not available.

Interactive managing of the camera backlight was available only on iOS.

There was no option to use a camera flash as a flashlight.

Extended the mobile device camera operations.
Spreadsheet documents.
Mobile platform.
A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.A PDF type document generated on the mobile platform was less similar to the same PDF type document generated on PC. +A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.
Mobile device-specific features.
Mobile client.
Mobile platform.
Implemented acquiring purchase receipts feature in 1C:Enterprise mobile version. It is now available to validate the purchase receipt on a mobile device.

Implemented the following InAppPurchasesManager object methods:

  • PurchaseHistorySupported()
  • GetPurchaseHistory()
  • GetInAppPurchaseReceipts()
  • GetInAppPurchaseReceiptsData().

+

The InAppPurchasesManager object is now available in the mobile client and in the mobile platform client. Implemented the InAppPurchasesValidationManager.ValidateInAppPurchaseReceiptAtMobileDevice() method on the mobile client and on the mobile platform client.

The global context InAppPurchasesValidation property is now available on the mobile client and on the mobile platform client.

Acquiring the list of internal purchases is now available in the mobile application builder purchase emulator.

Acquiring purchase receipts feature was not available.

The InAppPurchasesValidationManager object and the InAppPurchasesValidation global context property were available only on the server of the PC platform.

Improved the internal purchases feature, provided by the appropriate application store.
Mobile platform.
Implemented the following form control properties:
  • DisplayImportance for all controls
  • CurrentRowUse and TableBehaviorOnHorizontalCompression for a form table.

+Implemented input hints for multiline input fields.

These features were available in the mobile client only.Managed forms are now displayed the same way in different 1C:Enterprise mobile versions.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Interface.
In Taxi interface the command check in the menu now displays the same way in different displaying options and different client application types.The command check in the menu could be different depending on displaying options and client application types.The command check in the menu now displays the same way.
Data composition system.
If a filter is added to a query of composition schema data set that includes union, this filter is added to every part of the union. If a particular union part does not contain a field that is used in the filter, this field is replaced by NULL.

This change is not implemented in version 8.3.12 compatibility mode.

If a filter was added to a query of composition schema data set that includes union, this filter was added to parts of the union that contained the field that was used in the filter. +Unified filter operations in data composition system between the union data set and query data set, where the query contained a union.
Internet-enabled functionality.
The parameters of the following FTPConnection object methods were renamed in the Syntax Assistant: Get() and Put().

This change is available in the Syntax Assistant only.

The parameters of the following FTPConnection object methods were different in the Syntax Assistant: Get() and Put().The names of the FTP methods parameters became more clear.
Mobile device-specific features.
Mobile platform.
Mobile client.
The DeliverableNotification.Title value is now displayed when a notification is shown on iOS version 8.2 and later mobile device.The DeliverableNotification.Title value was available on Android only.Improved notifications on iOS.
Collaboration system.
Mobile platform.
Mobile client.
The collaboration system notifications now contain the sender name. The noncontext conversation title is displayed in the notification title. +The collaboration system notifications did not contain the sender name. The noncontext conversation title was displayed both in the notification title and text.Improved collaboration system notifications.
Internet-enabled functionality.
macOS certificate store is now supported.

New objects: MacOSCertificationAuthorityCertificates, MacOSCertificateSelectMode, and MacOSClientCertificate.

macOS certificate store support is added to object OSCertificationAuthorityCertificates.

New -macos parameter for /HttpsCA and /HttpsCert command-line options of the client application.

New technological log event: <MACCERT>.

macOS certificate store was not supported. Secured connection was only available if certificates were stored in files.You can use the system certificate store to establish secured connection on macOS.
Collaboration system.
The client application agent supports multiple versions of the collaboration system server's exchange protocol.

New 1ceclac application is provided. The client application agent's directory structure is changed.

The client application agent supports a single version of the collaboration system server's exchange protocol.The client application agent supports the previous versions of the collaboration system server's exchange protocol. +
Dynamic lists.
The following restrictions apply to search in dynamic lists:
  • The search string cannot exceed 1000 characters.
  • The search string cannot contain more that 20 words.

If the search string does not comply with the listed requirements, an exception is generated. For details on splitting the search string into words, see 1C:Enterprise documentation.

There were no restrictions to search in dynamic lists.Improved application server reliability when searching in dynamic lists.
Dynamic lists.
Data composition system.
When opening report forms or dynamic list forms, if user settings are not available in the storage, the system performs the following actions:
  • Items with unavailable or missing fields are deleted from the main dynamic list settings and report option settings that are marked as user settings.
  • Items with unavailable or missing fields are deleted from the default user settings.
  • BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers are executed.

New UseDefaultSettings parameter for BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers.

The Set default settings command of report and dynamic list forms performs the following actions:

  • Items with unavailable or missing fields are deleted from the main dynamic list settings and report option settings that are marked as user settings.
  • Items with unavailable or missing fields are deleted from the default user settings.
  • If the user settings of a dynamic list or a report option were not changed on the client (interactively or from 1C:Enterprise language) since the form was opened, the current user settings are deleted from the system storage when the form is closed

Method DataCompositionSettingsComposer.Refresh() with parameter DataCompositionSettingsRefreshMethod.Full performs the following actions: sets the Use flag to False for main settings items that lost their linking to available fields, and deletes items of main settings and user settings that are marked as user settings but contain fields absent from the collection of available fields or not available for the current functional options and rights.

This change is not implemented in version 8.3.12 compatibility mode.

When opening report forms or dynamic list forms, if user settings were not available in the storage, the system performed the following actions:
  • Items with unavailable or missing fields were not deleted from the main dynamic list settings and report option settings that were marked as user settings.
  • Items with unavailable or missing fields were not deleted from the default user settings.
  • BeforeLoadUserSettingsAtServer and OnLoadUserSettingsAtServer event handlers were not executed.

The Set default settings command of report and dynamic list forms had the following behavior:

  • Items with unavailable or missing fields were not deleted from the main dynamic list settings and report option settings that were marked as user settings.
  • Items with unavailable or missing fields were not deleted from the default user settings.
  • If the user settings of a dynamic list or a report option were not changed on the client (interactively or from 1C:Enterprise language) since the form was opened, the default settings generated based on the main dynamic list settings or on the current report option settings were saved as user settings when the form was closed.

Method DataCompositionSettingsComposer.Refresh() with parameter DataCompositionSettingsRefreshMethod.Full set the Use flag to False for main settings items that lost their linking to available fields.

Unavailable fields cannot be added to the default user settings of reports or dynamic lists.
Data analysis.
If a data set contains an even number of elements, its median is calculated as the arithmetic mean of the two middle elements of the ordered set. In particular, this rule applies to data sets that contain two elements.

This change is not implemented in version 8.3.12 compatibility mode.

If a data set contained an even number of elements, its median was calculated as follows:
  • For data sets with more than 2 elements, the arithmetic mean of the two middle elements of the ordered set.
  • For data sets with 2 elements, the value of the second element.
Eliminated unexpected system behavior.
Internet-enabled functionality.
For SMTP operations, added support of NOTIFY parameter of RCPT command and RET parameter of MAIL command. This provides support for mail delivery receipts described in RFC 1891.

InternetMailMessage.DeliveryReceiptAddresses property is deprecated. This property is only available in Version 8.3.12 compatibility mode.

Note that some SMTP server implementations or some of their settings can prevent receiving mail delivery receipts.

It is recommended that you do not use DeliveryReceiptAddresses property of InternetMailMessage object. Use the following properties instead:

  • ReadReceiptAddresses and RequestReadReceipt to receive read receipts.
  • RequestDeliveryReceipt to receive delivery receipts.
Instead of delivery receipts, read receipts were generated.Eliminated unexpected system behavior.

Both delivery and read receipts are now available.

Internet-enabled functionality.
If a mailbox does not contain any messages matching the IDs specified in the parameter of InternetMail.GetMessagesFlags() method, the method returns a blank map.

This change is not implemented in version 8.3.12 compatibility mode.

If a mailbox did not contain any messages matching the IDs specified in the parameter of InternetMail.GetMessagesFlags() method, the method generated an exception.Eliminated unexpected system behavior.
Spreadsheet documents.
An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection generates an exception. Only spreadsheet documents without pictures can be saved in this format.An attempt to save a spreadsheet document with pictures in 1C:Enterprise 7.7 format on a server or in an external connection resulted in generation of a corrupted document that could not be opened. +Eliminated unexpected system behavior.
Managed forms.
If the Width property of a form field is not 0 and horizontal stretching is not applied, this property defines the field width without the input field buttons (Select, Clear, and others). The resulting field width is equal to the sum of the Width value and all button widths.

This change is not implemented in version 8.3.12 compatibility mode.

If the Width property of a form field was not 0 and horizontal stretching was not applied, this property defined the field width as follows:
  • If input field buttons were available, it defined the field width without the buttons.
  • If input field buttons were not available, the actual width was slightly greater than the specified one.

Thus, adding or removing input field buttons could change the field width.

Eliminated unexpected system behavior.
Collaboration system.
If several applications share a collaboration server, the message counter of the client application agent is incremented once per message.If several applications shared a collaboration server, the message counter of the client application agent was incremented several times (once per application). +Eliminated unexpected system behavior.
Add-ins.
macOS.
Client applications running on macOS now support add-ins based on Native API.

The add-in technology documentation and examples are updated accordingly (read more).

Client applications running on macOS did not support add-ins based on Native API.Client applications running on macOS now support add-ins.
Add-ins.
Mobile platform.
Mobile client.
For add-ins intended to run on iOS, you can specify a set of properties to be included in the application properties (file info.plist). The properties required by the add-in are added by the Mobile application builder.

The add-in technology documentation is updated. (read more)

This feature was not provided.

Add-ins could not add properties to the info.plist file.

Development of add-ins intended to run on iOS is more convenient. +
Collaboration system.
Client application.
When a collaboration system notification is deleted from the notification center, the conversation is marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list.When a collaboration system notification was deleted from the notification center, the conversation was not marked as read. Deleting a notification here means either deleting a single notification or clearing the notification list.The collaboration system behavior is more logical and predictable.
Data composition system.
XML and XDTO support.
When XDTO deserialization is applied to data composition parameters, only parameters that are included in the list of the available parameters of the current platform version are deserialized. No deserialization attempts are performed for parameters that are not included in the list of available ones. This ensures successful restoration of parameters.When XDTO deserialization was applied to data composition parameters, the platform attempted to deserialize all of the serialized parameters. Attempts to restore data composition settings using an earlier platform version where the list included parameters unavailable in the current version generate errors.You can use an earlier platform version to restore data composition schemas and data composition settings saved in a later platform version. At that, data composition parameters available only in the later version are ignored.
Mobile client.
Server clusters.
Data history.
If mobile client version 8.3.12 is connected to a 1C:Enterprise server 8.3.13:
  • An attempt to view the change history always opens the default change history form.
  • An attempt to view the change history of a constant returns an error.

If mobile client version 8.3.13 is connected to a 1C:Enterprise server 8.3.12, an attempt to view the change history always opens the default change history form.

If mobile client version 8.3.12 was connected to a 1C:Enterprise server 8.3.13, the change history was unavailable.Eliminated unexpected system behavior. +
DBMS operations.
System requirements.
PostgreSQL version 10.3 is supported.PostgreSQL version 10.3 was not supported.Extended list of supported DBMS.
Managed forms.
Client application.
If a form table does not have a current row (for example, it is blank) and a column group is hidden from the table header, its parent column group is also hidden from the header.

If a form table has a current row and a column group is shown in the header, its nested column group is shown in the header only if the current row contains cells that belong to the nested group.

This change is not implemented in version 8.3.12 compatibility mode.

If a form table did not have a current row (for example, it was blank) and a column group was hidden from the table header, its parent column group was shown in the header as a blank column.

If a form table had a current row and a column group was shown in the header, its nested column groups were always shown in the header.

Eliminated unexpected system behavior.
Data composition system.
Predefined resource templates that describe intersections of table row groupings (template type: Title or Footer) with table column groupings (template type: Grand Total Title or Grand Total Footer) are displayed in a report even if the resource fields are not displayed in the table columns.

This change is not implemented in version 8.3.12 compatibility mode.

In data composition system tables, if resource fields were not displayed in table columns, predefined resource templates were not displayed for row totals.Eliminated unexpected system behavior.
Data history.
In a data structure that is generated by the DataHistoryManager.GetVersionDiff() method and describes moving a table row:
  • The RowNumberInBeforeChangeVersion property contains the number that the row had before applying any of the version changes.
  • The RowNumberInAfterChangeVersion contains the number that the row has after applying all of the version changes.

This change is also applied to the standard version difference report.

In a data structure that was generated by the DataHistoryManager.GetVersionDiff() method and described moving a table row:
  • The RowNumberInBeforeChangeVersion property contained the number that the row had after applying all of the previous changes but before applying the current change.
  • The RowNumberInAfterChangeVersion contained the number that the row had after applying the current change.
Eliminated unexpected system behavior.

The row numbering is now more intuitive.

Cryptography support.
An interactive mode of password-related operations is implemented for the cryptography manager. If the cryptography manager is initialized in the interactive mode, the password to access the private key that is defined in the object is ignored, and the user is asked to enter the password. The option to remember the password is implemented. The interactive mode of the cryptography manager is supported only on the client. An attempt to use the interactive mode on the server generates an error.

InteractiveModeUse parameter is implemented for CryptoManager constructor and CryptoManager.BeginInitialization() method.

We recommend that you analyse the cases where the cryptography manager is used and implement interactive mode on the client to improve the user experience.

The only way to specify the password to access a private key was through the cryptography manager property. Users could not set the password themselves.More secure and user-friendly mode of managing private key passwords is implemented.
Managed forms.
If a form input field contains modified data and it is not the current form item, an attempt to set its Visible, Enabled, or EditText property to False or set its ReadOnly property to True results in the following:
  • TextEditEnd event handler is called.
  • After the TextEditEnd event handler is completed, if the StandardProcessing parameter is set to True:

+

  • If a valid value is generated from the field text, the OnChange event handler is called.
  • If a valid value cannot be generated from the field text, the input field value is set to the value of the attribute linked to the input field.

+

  • After the TextEditEnd event handler is completed, if the StandardProcessing parameter is set to False and a valid value cannot be generated from the field text, the input field value is set to the value of the attribute linked to the input field. +

If a form input field contains unmodified data and it is not the current form item, an attempt to set its Visible, Enabled, or EditText property to False or set its ReadOnly property value to True results in closing the drop-down list (if the list was open). +This change is not implemented in version 8.3.13 compatibility mode.

+

Setting the Visible property of an input field to False results in the following:
  • If the field is linked to a text value, its value is generated from the field text and then the OnChange event handler is called.
  • If the field is linked to a reference value and a user has not finished filling it, the resulting field state might be inconsistent.
Eliminated unexpected system behavior.
Mobile client.
Internet-enabled functionality.
Mobile clients can connect to infobases over HTTPS. The infobase access parameters of the mobile client now include the client certificate source and the server certificate verification options.

The client certificate source can be an application certificate store or a file (for iOS and Android).

The source of root certificates for server certificate verification can be a system certificate store, application certificate store, or file (for iOS and Android).

This feature was not provided.Added new mobile client features.
Mobile client.
Managed forms.
In the mobile client, customization of form command bars is implemented. A new form property: MobileDeviceFormCommandBarContent.

In the mobile client, the property content (unless it is blank) is displayed in the form command bar, replacing the default command bar. Including a form command bar into the MobileDeviceFormCommandBarContent property content is not supported.

If a form group title is defined but not displayed, the title is considered when generating the title of an automatically collapsed group on the mobile client.

In the mobile client, form command bar customization was not supported.

If a form group title was defined but not displayed, the title was not considered when generating the title of an automatically collapsed group on the mobile client.

Form customization on the mobile client is upgraded. +
DBMS operations.
System requirements.
PostgreSQL version 10.5 (for 32-bit and 64-bit operating systems) is supported.PostgreSQL version 10.5 was not supported.Extended list of supported DBMS.
Mobile client.
Collaboration system.
New features for the mobile client:
  • Someone-is-typing indicator.
  • One-on-one voice calls.
  • User status. Users with "Do not disturb" status do not receive push notifications.

New objects supported by the mobile client:

  • CollaborationSystemConversation.Group property.
  • CurrentApplicationID() method.

The version of the collaboration system on the mobile client is defined by the collaboration system version on the 1C:Enterprise server.

Mobile client collaboration system features are defined by the collaboration system version on the 1C:Enterprise server and do not depend on the server version.

These features were not provided.The collaboration system features on the mobile client match the features on the thin client. +
System requirements.
Mobile platform.
Mobile client.
The mobile version of 1C:Enterprise supports Android 9, iOS 12, and the following Apple devices: iPhone Xs, Xs Max, and Xr.The mobile version of 1C:Enterprise did not support Android 9 and iOS 12.

The mobile version of 1C:Enterprise did not support iPhone Xs, Xs Max, and Xr.

1C:Enterprise supports new operating systems and devices.
Mobile application builder.
New: now you can manage permissions of mobile applications running under Android OS even more accurately if it is required to grant Telephony permission in the application.

If the permission is required, then the builder prompts you to define which permission out of 6 ones is required by the mobile application.

If the application required the Telephony permission, the mobile application builder provided the mobile application with 6 permissions at once.Requirements for permissions that appeared in a new edition of Google Play developer rules are considered. Now you can define only the permissions required by the mobile application.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented:
  • Postgres Pro 1C 9.4.19,
  • Postgres Pro 1C 9.6.11,
  • Postgres Pro 1C 10.6,
  • Postgres Pro Enterprise 9.6.11,
  • Postgres Pro Enterprise 10.3.3,
  • Postgres Pro Enterprise 10.6,
  • Postgres Pro Standard 10.6.
The following Postgres Pro DBMS versions were not supported:
  • Postgres Pro 1C 9.4.19,
  • Postgres Pro 1C 9.6.11,
  • Postgres Pro 1C 10.6,
  • Postgres Pro Enterprise 9.6.11,
  • Postgres Pro Enterprise 10.3.3,
  • Postgres Pro Enterprise 10.6,
  • Postgres Pro Standard 10.6.
Extended list of supported DBMS.
Localization.
Localized client application interface for Spanish (es).This feature was not provided.1C:Enterprise is available to Spanish-speaking users.
Localization.
Localized client application interface for Greek (el).This feature was not provided.1C:Enterprise is available to Greek-speaking users.
HTML support.
Upon reading an HTML document using the HTMLReader object (using the OpenFile(), OpenStream(), and SetString() methods), document parsing will be stopped when the nesting reaches 1,024 tags. The user will get access to a part of the document only.Upon reading an HTML document using the HTMLReader object, there were no restrictions on the number of nested tags, which might lead to abnormal shutdown.Upgrade: better system reliability upon parsing HTML documents with high tag nesting.
DBMS operations.
The following DBMS are now supported (64-bit versions only):
  • PostgresPro PostgreSQL 10.9.1.
  • PostgresPro PostgreSQL 11.4.1.
  • PostgresPro Standard 9.6.14.1.
  • PostgresPro Standard 10.9.1.
  • PostgresPro Standard 11.4.1.
  • PostgresPro Enterprise 9.6.14.1.
  • PostgresPro Enterprise 10.9.1.
  • PostgresPro Enterprise 11.4.1.
  • PostgresPro Enterprise 11.4.2.
These PostgresPro DBMS versions were not supported.More PostgresPro DBMS versions are now supported.
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
  • Postgres Pro 1C 9.6.16,
  • Postgres Pro 1C 10.11.1,
  • Postgres Pro 1C 11.6.1,
  • Postgres Pro Standard 9.6.16,
  • Postgres Pro Standard 10.11.1,
  • Postgres Pro Standard 11.6.1,
  • Postgres Pro Enterprise 9.6.16,
  • Postgres Pro Enterprise 10.11.1,
  • Postgres Pro Enterprise 11.6.1.
The following Postgres Pro DBMS versions were not supported:
  • Postgres Pro 1C 9.6.16,
  • Postgres Pro 1C 10.11.1,
  • Postgres Pro 1C 11.6.1,
  • Postgres Pro Standard 9.6.16,
  • Postgres Pro Standard 10.11.1,
  • Postgres Pro Standard 11.6.1,
  • Postgres Pro Enterprise 9.6.16,
  • Postgres Pro Enterprise 10.11.1,
  • Postgres Pro Enterprise 11.6.1.
Extended list of supported DBMS.
Mobile platform.
When creating a secure OpenSSL connection, server certificate validation is performed using the certificates installed on the mobile device if the value of the CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection constructor is Undefined or is of the OSCertificationAuthorityCertificates type. +When creating a secure OpenSSL connection, server certificate validation was not performed if the value of the CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection constructor was Undefined or was of the OSCertificationAuthorityCertificates type. +Eliminated unexpected system behavior. +
System requirements.
DBMS operations.
Support of the following Postgres Pro DBMS versions is implemented (x86-64 architecture only):
  • Postgres Pro 1C 9.6.17,
  • Postgres Pro 1C 10.12.1,
  • Postgres Pro 1C 11.7.1,
  • Postgres Pro Standard 9.6.17,
  • Postgres Pro Standard 10.12.1,
  • Postgres Pro Standard 11.7.1,
  • Postgres Pro Enterprise 9.6.17,
  • Postgres Pro Enterprise 10.12.1,
  • Postgres Pro Enterprise 11.7.1.
The following Postgres Pro DBMS versions were not supported:
  • Postgres Pro 1C 9.6.17,
  • Postgres Pro 1C 10.12.1,
  • Postgres Pro 1C 11.7.1,
  • Postgres Pro Standard 9.6.17,
  • Postgres Pro Standard 10.12.1,
  • Postgres Pro Standard 11.7.1,
  • Postgres Pro Enterprise 9.6.17,
  • Postgres Pro Enterprise 10.12.1,
  • Postgres Pro Enterprise 11.7.1.
Extended list of supported DBMS.

Table of contents

Transition from the previous version to the version 8.3.13

Table of contents

Version 8.3.12

Version 8.3.12 includes known bug fixes and functionality modifications. +

Before adapting an application to the mobile client, we recommend that you read the ITS article Read more..

Finished the beta testing of the application debug by HTTP protocol option.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.11 is now implemented.Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.10 was implemented.Configurations developed using 1C:Enterprise platform version 8.3.11 or earlier can run on version 8.3.12 without any changes to configuration or to data structures. This allows for transition to version 8.3.12 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.11 after the transition to version 8.3.12, even if you disabled the compatibility mode (if you did, enable it again).
Client application.
On 64-bit Windows, you can set the bitness of a client application at application startup.

In the Startup window settings dialog box, the option to specify the application bitness is implemented. This value is stored to the DefalutVersion parameter of 1CEStart.cfg file.

In the infobase properties, the option to specify the bitness of the client application used with this infobase is implemented. This value is stored to the AppArch parameter of ibases.v8i file. +The command-line option /AppArch is implemented for the thin and thick client applications.

This feature was not provided.

On 64-bit Windows, users could not select the bitness of client applications.

On 64-bit Windows, the option to select the bitness of a client application is implemented.

You can explicitly specify a 32-bit application in scenarios where a 64-bit application cannot work properly (for example, in a scenario where 64-bit add-ins are not available).

Configuration extensions.
The option to select the application area of configuration extensions, as well as activate or deactivate them, is implemented.

The following application areas are available: the current data area and the entire infobase.

When an extension is deactivated, it is not deleted from an infobase.

For ConfigurationExtension object, implemented Scope and Active properties.

The extension activation order is changed. Extensions that are applied to the entire infobase are activated first.

These features were not provided.

Extensions were always attached to specific data areas.

Disabling extensions without deleting them was not available.

More configuration extension management options.

You can add configuration extensions to all of the infibase data areas at once. You can use this feature to apply hotfixes.

Collaboration system.
Automatic conversion of character sequences to pictures ("smileys") is implemented.

Sound alerts for the following events are implemented: new message, incoming call, waiting for reply to a video call, and end of video call.

Links to conversations, getting links to conversations, and opening links to conversations (both interactively and using GotoURL() method) are implemented. The option to add such links to Favorites is implemented. The option to get presentations of such links using GetURLsPresentations() method is implemented. In conversation messages, links to conversations are displayed as hyperlinks.

In the thin and thick clients for Windows, taskbar blinking upon receiving a notification is implemented.

In the main collaboration system form, a context menu is implemented for the conversation list. A context menu is implemented for collaboration system messages.

For noncontext conversations, service collaboration system messages are implemented for the following events: conversation topic changed, a user joined/left a conversation. The search ignores service messages.

The conversation participant list view is changed.

Special marking for unsent outgoing messages is implemented.

The collaboration system settings dialog box is implemented.

The user picture (avatar) editor is implemented.

The message list view is changed.

These features were not provided.Improved collaboration system usability.
Data history.
Support of data history for charts of accounts and charts of characteristic types is implemented.

For ChartOfAccountsObject and ChartOfCharacteristicTypesObject objects, methods SetDataHistoryVersionComment() and GetDataHistoryVersionComment() are implemented.

This feature was not provided.Data history is now available for more objects.
Configuration extensions.
For native and adopted extension objects, the option to generate records in all adopted registers is implemented, except for turnover accumulation registers with aggregates.This feature was not provided.

Extension documents could generate records only in native information registers available in the extension.

Extended configuration extension capabilities.
Configuration extensions.
Development tools.
Settings storage.
The option to store configuration extensions in configuration repositories is implemented. All of the Designer batch mode command-line options that are related to configuration repositories support configuration extensions.

For Designer batch mode, the following changes are implemented:

  • -Extension parameter is implemented for the following command-line options: СonfigurationRepositoryAddUser, ConfigurationRepositoryBindCfg, ConfigurationRepositoryDumpCfg, ConfigurationRepositoryClearCache, ConfigurationRepositoryClearGlobalCache, ConfigurationRepositoryClearLocalCache, ConfigurationRepositoryCommit, ConfigurationRepositoryCopyUsers, ConfigurationRepositoryCreate, ConfigurationRepositoryLock, ConfigurationRepositoryOptimizeData, ConfigurationRepositoryReport, ConfigurationRepositorySetLabel, ConfigurationRepositoryUpdateCfg, ConfigurationRepositoryUnbindCfg, and ConfigurationRepositoryUnlock.
  • ExtensionConfigurationRepository value is implemented for -FirstConfigurationType and -SecondConfigurationType parameters of CompareCfg command-line option.
  • -FirstName, -FirstFile, -FirstVersion, -FirstName, -FirstFile, and -FirstVersion parameters are implemented for CompareCfg command-line option.
This feature was not provided.

Configuration extensions could not be stored in configuration repositories, making development unnecessarily complicated.

Simplified group development and versioning of configuration extensions.
Configuration extensions.
Creation of enumerations in configuration extensions is now supported.This feature was not provided.Extended configuration extension capabilities.
Internet-enabled functionality.
Moving email messages between IMAP mailboxes is now supported. Method InternetMail.MoveToMailbox() is implemented.

Getting and setting flags of IMAP email messages is implemented. For InternetMail object, methods GetMessageFlags() and SetMessageFlags() are implemented.

These features were not provided.Extended support of IMAP email operations.
Charts.
Data composition system.
Highlighting specific chart intervals and values is implemented. This feature is available for the following chart types: stock, open-high-low-close, all types of column charts, all types of bar charts (except for bar graph), line, step, stacked line, area (all types), scatter, bubble, radar (all types), and gauge. +

For Chart object, the following properties are implemented: ColorPaletteDescription, DataIntervalsColorPaletteDescription, ValueDataLines, PointDataLines, ValueDataIntervals, and PointDataIntervals.

For ChartLabelArea, the following properties are implemented: Orientation and Angle.

For data composition system objects DataCompositionOutputParameterValues,

DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, the following parameters are implemented: ChartType.ColorPaletteDescription, ChartType.DataIntervalsColorPaletteDescription, ChartType.ValueDataLines, ChartType.PointDataLines, ChartType.ValueDataIntervals, and ChartType.PointDataIntervals.

The following properties and methods of Chart object are obsolete and not recommended for use: ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, GradientPaletteMaxColors, GetPalette(), and SetPalette().

This feature was not provided.Additional chart layout features are introduced.
Spreadsheet documents.
Implemented representable document batch export to the following formats: XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later), and ODT (OpenDocument). You can export each spreadsheet document of the batch to a separate sheet of the resulting document.

Implemented RepresentableDocumentBatchItem.Title property. Use it to specify the sheet name.

Implemented Write() and BeginWriting() methods of RepresentableDocumentBatch object.

This feature was not provided.You can save several 1C:Enterprise spreadsheet documents to the resulting XLS, XLSX, or ODT document.
Full-text search.
Server clusters.
Technological log.
In client/server mode, the option to set the number of background jobs that update the full-text search index is implemented. You can use requirements of functionality purpose to set the number of background jobs that update the full-text search index.

For FullTextSearchManager object, the following methods are implemented: SetIndexingJobsCount() and GetIndexingJobsCount().

For FTEXTUpd technological log event, the following properties are implemented: MinDataId, MemoryUsed, BackgroundJobCreated, JobCanceledByLoadLimit, TotalJobsCount, and FailedJobsCount.

This feature was not provided.

The update of the full-text search index was always performed as a single background job.

Improved performance of full-text search index updates (especially in scenarios with full index rebuilding).
Configuration extensions.
Distributed infobases.
Support of configuration extensions in distributed infobases is implemented.

For exchange plans, IncludeConfigurationExtensions property is implemented.

For configuration extrensions, UseInDistributedInfobase and MasterNode properties are implemented.

This feature was not provided.Extended configuration extension usage options. You can manage the replication of configuration extensions in distributed infobases.
Charts.
In charts, the option to manage automatic calculation of header, legend, and plot area sizes and positions is implemented. For ChartLegendArea, GanttChartLegendArea, PivotChartLegendArea, ChartPlotArea, GanttChartPlotArea, PivotChartPlotArea, ChartTitleArea, GanttChartTitleArea, and PivotChartTitleArea objects, property Placement is implemented.

Property ShowLegend of Chart, GanttChart, and PivotChart objects is deprecated.

Property ShowTitle of Chart, GanttChart, and PivotChart objects is deprecated.

Charts only provided the option to manage header and legend view.Improved chart customization options.
Queries.
In the query language, extended support of UUID and ValueStorage types.

The option to create temporary tables based on value tables that contain columns of these types is implemented.

The option to use fields and expressions of UUID type in queries where IN is applied to a selection of multiple fields is implemented.

This feature was not provided.Extended query language capabilities.
Data composition system.
In data composition settings, the option to use a period addition in scenarios where the reporting period does not match a regular calendar period is implemented. You can specify month size, either a calendar month or "4-5-5". In the latter case, a year is divided into 4 quarters. Each quarter has two 4-week months and the third 5-week month. +For system enumeration DataCompositionPeriodAdditionType, the following values are implemented:
  • YearFromBeginningOfPeriod
  • DayFromBeginningOfPeriod
  • QuarterFromBeginningOfPeriod
  • MonthFromBeginningOfPeriod
  • MinuteFromBeginningOfPeriod
  • WeekFromBeginningOfPeriod
  • HalfYearFromBeginningOfPeriod
  • HourFromBeginningOfPeriod
  • YearFromBeginningOfPeriod445
  • QuarterFromBeginningOfPeriod445
  • MonthFromBeginningOfPeriod445
  • HalfYearFromBeginningOfPeriod445
The data composition system always used period additions based on calendar beginning of quarter or year.Simplified reporting in scenarios where the reporting period does not match a regular calendar period.
Managed forms.
For managed forms, collapsible pop-up groups are implemented. When a pop-up group is collapsed, a form displays its title; clicking the title opens a pop-up window, which contains all of the group items. In a form, you can view the content of a single pop-up group at a time.

The option to toggle the state of collapsible and pop-up groups from 1C:Enterprise script is implemented.

The following system enumeration value is implemented: UsualGroupBehavior.PopUp.

For managed form group extensions for usual groups, the following methods are implemented: IsHidden(), Show(), and Hide().

For managed form group extensions, HiddenViewTitleBackgroundColor property is implemented.

These features were not provided.New options for grouping managed form items.
Database configuration update.
In the optimized restructuring mechanism (version 2), added the support of restructuring configuration objects having at least one extension (that extends data) attached in any of the data areas. This is only applicable to restructuring main database configurations. Restructuring that is performed during extension updates does not use the optimized restructuring mechanism (version 2).This feature was not provided.

For main database configurations, if any of the areas had an extension (that extended data) attached, the regular restructuring mechanism (version 1) was used.

Improved interaction between platform mechanisms.
Automated testing.
For TestedFormField objects that represent form items of radio button, input field, and label (with hyperlink flag set) types, method GetDisplayedText() is implemented. It gets the text displayed on the item.

For TestedFormField objects that represent form items of radio button and input field types, method GetChoiceListPresentation() is implemented. It gets a fixed array that contains presentations of the form item choice list.

This feature was not provided.Extended automated testing capabilities.
Mobile client.
Implemented the mobile client, which is equivalent to the thin client running on a mobile device. Its interface is similar to mobile platform interface. The mobile client supports only HTTP connections to infobases. It does not support TCP connections. The exact match between the mobile client version and the server (or the web server extension) version is not required.

The mobile client provides online access to the majority of the features available in the thin client and in the web client. The mobile client supports all mobile device-specific features, such as camera, location, and notifications.

The collaboration system uses push notifications to deliver messages. Messages are delivered even if applications that generated them are not running or inactive.

Mobile client applications are always built to run with a specific list of configurations. Changing the assortment of configuration objects in an infobase connected to a mobile client application is not supported. You can modify a configuration without modifying the assortment of its objects. If the assortment of objects changes, you have to republish the mobile application. A mobile client application cannot run with configurations that are not in the list because of application store requirements. The mobile client uses digital configuration signatures to check whether a configuration is in the list.

Implemented automatic adjustment of configuration forms to mobile device screens. You can use new form item properties to modify the adjustment rules. In the managed form editor, implemented the form preview for mobile client mode.

In the mobile client, the list of home page forms is identical to that of the thin and web clients (but different from the list of home page forms of the mobile platform). When you start an application, it displays the first form in the list, while the other forms are available through a menu.

The mobile client supports add-ins.

The mobile client does not support interactive opening of external reports and data processors.

The mobile client can run configurations with compatibility mode Version 8.3.7 or later.

In Designer, implemented commands for interactive start of the mobile client on a mobile device.

The mobile application builder can now build mobile client applications. You can select the type of application to build: a mobile client application or a mobile platform application.

Implemented MobileClient access right. Implemented MobileClient preprocessor command. In the Syntax Assistant, implemented a new availability option for objects, properties, and methods.

For managed forms, implemented CollapseItemsByImportance property. For managed form items, implemented DisplayImportance property. It affects the adjustments of the form layout. For managed form tables, implemented CurrentRowUse and BehaviorOnHorizontalCompression properties. For form groups, implemented CurrentRowUse and AssociatedTable properties. For Designer batch mode, implemented the following command-line options and parameters: MobileClientWriteFile and MobileClientDigiSign options -MobileClient parameter for CheckModules and CheckConfig options -MobileClientDigiSign parameter for CheckConfig option

Changed the content of the mobile platform distribution package (mobile.zip). Now it contains the mobile client files required to develop and build mobile applications, as well as distribute them through application stores.

This feature is included for beta testing purpose only. +

This feature was not provided.

The mobile platform was capable of running specialized offline applications.

Mobile devices can be used in the new way now. You can now work online with all application features that were available on the thin client and on the web client without the significant configuration refactoring.
Administration tools.
In Designer batch mode, for command-line options CreateDistributionFiles and CreateDistributive, implemented parameter WarningAsError.This feature was not provided.You can apply stricter validation rules (treat all warnings as errors) to generation of application distribution kits.
Server clusters.
Implemented new values for session and connection attributes. They indicate the duration of cluster service calls initiated by a session or a connection. They are available in all administrative tools: the cluster console, COM connection, Java administrative API, and the administration server.

Implemented the following IInfoBaseConnectionInfo object and ISessionInfo object properties:

  • durationCurrentService – the current cluster service operation time
  • CurrentServiceName – the current service name
  • durationLast5MinService – the total duration of cluster service calls within the last 5 minutes
  • durationAllService – the total duration of cluster service calls since the beginning of the session or the connection

Added the same attributes to the session list, connection list, and the connection properties dialog box in the cluster console.

Added the following parameters of connection list commands and session list commands for the cluster service command-line utility (rac): duration-current-service, current-service-name, duration-last-5min-service, and duration-all-service.

This feature was not provided.The duration of cluster service calls initiated by a specific connection or a specific session is now available.
System requirements.
Client application.
The client application for Linux needs the 1.4.3 version or higher of the webkitgtk-3.0 library installed.The client application for Linux needed the 1.4.3 version or higher of the webkitgtk-1.0 library installed.Unified the Linux and MacOs client applications operation.
Add-ins.
Implemented the new global context method DynamicAddInInstallationSupported(). It shows whether the add-in loading is available from the current infobase.

The dynamic add-in loading is available only on Android mobile devices. Otherwise add-ins should be included in the mobile application and are available only from the Add-in type configuration templates.

The dynamic add-in loading is available in the thick client, in the thin client, and in the web client (this behavior did not change).

Add-ins were available only from the mobile application and you could not load them from the infobase.

You could not define the availability of dynamic add-in loading feature.

Now you can get the availability of dynamic add-in loading feature.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Managed forms.
Keyboard navigation is now available for managed form decorations and fields, provided that they do not have the Hyperlink flag set and they display FormattedString values.

Keyboard navigation provides the option to move between hyperlinks available in a formatted string.

This feature was not provided.Improved managed form usability.
Web client.
Spreadsheet documents.
In the web client, implemented all of the interactive spreadsheet document editing features that are available in other clients.

Implemented the following spreadsheet document commands: AlignPictureLeft, AlignPictureCenter, AlignPictureRight, AlignPictureTop, AlignPictureMiddle, AlignPictureBottom, PicturesEqualWidth, PicturesEqualHeight, PicturesEqualSize, DistributePicturesVertically, DistributePicturesHorizontally, BringPictureForward, SendPictureBack, PringPictureToFront, and SendPictureToBack.

The options for interactive editing of spreadsheet documents were limited.

The availability of interactive commands that affected spreadsheet document view was limited.

Displaying row and column headers and grid lines was not supported.

Extended interactive spreadsheet document operations in the web client.
Spreadsheet documents.
In the thin client, in the paste special dialog box for spreadsheet documents, the option to include or exclude the following items is implemented:
  • Merged cells
  • Cell pictures
  • Drawings
  • Row and column groups
  • Header and footer

In this dialog box, the All check box is replaced with buttons that select and clear all of the check boxes available in the dialog box.

In the thin client, the paste special dialog box for spreadsheet documents did not provide the option to include or exclude the following items:
  • Merged cells
  • Cell pictures
  • Drawings
  • Row and column groups
  • Header and footer

In this dialog box, the All check box was available.

Extended paste special options for spreadsheet documents.
Interface.
In actions panel and navigation panel customization forms, the correct picture is set for Move to group command.In actions panel and navigation panel customization forms, the picture of Move to group command was incorrect.Eliminated unexpected system behavior.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Client application.
The client application interface rendering is now faster.

The client application load on the operating system is reduced.

The client application interface rendering was slower and used more operating system resources.Improved client application usability.
Background and scheduled jobs.
Background jobs now start faster.Background job startup took more time.Background jobs now start faster.
Binary data.
Optimized performance and memory usage of the following 1C:Enterprise script function:
  • GetStringFromBinaryData();
  • GetStringFromBinaryDataBuffer();
  • GetHexStringFromBinaryData();
  • GetHexStringFromBinaryDataBuffer();
  • GetBase64StringFromBinaryData();
  • GetBase64StringFromBinaryDataBuffer().
The performance and memory usage of the following 1C:Enterprise script functions were insufficient:
  • GetStringFromBinaryData();
  • GetStringFromBinaryDataBuffer();
  • GetHexStringFromBinaryData();
  • GetHexStringFromBinaryDataBuffer();
  • GetBase64StringFromBinaryData();
  • GetBase64StringFromBinaryDataBuffer().
Improved performance and stability of several functions that process binary data.
Configuration extensions.
Reduced database configuration update time for configuration extensions that do not affect the database structure.The database configuration update time was longer if the configuration extension did not affect the database structure.Reduced database configuration update time if the update includes applying changes to the configuration extensions that do not affect the database structure.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Charts.
The option to display Gantt chart intervals that would occupy less than 2 pixels in the current chart scale is implemented. They are displayed as 2-pixel intervals.In some cases, Gantt chart intervals that would occupy less than 2 pixels in the current chart scale were not displayed.Eliminated unexpected system behavior.
Data composition system.
The value of ResourcesAutoPosition data composition system parameter does not affect how column totals are displayed in data composition system reports.

This change is not implemented in 8.3.11 compatibility mode.

In data composition system report spreadsheets, column totals were not displayed if ResourcesAutoPosition data composition system parameter was set to DontUse.Eliminated unexpected system behavior.
Development tools.
In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object is more detailed. The report includes the list of added and removed packages (with package names included) and their namespace data.In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object was less detailed.Eliminated unexpected system behavior.
Charts.
Spreadsheet documents.
In black-and-white view mode:
  • Charts are displayed in black-and-white mode.
  • Geographical schemas are displayed in black-and-white mode.
  • Pictures and OLE objects are displayed in grayscale.

In black-and-white printing mode:

  • Charts are printed in black-and-white mode (this behavior is not changed).
  • Geographical schemas are printed in black-and-white mode (this behavior is not changed).
  • Pictures and OLE objects are displayed in grayscale.

This change is not implemented in 8.3.11 compatibility mode.

In black-and-white view mode:
  • Charts were displayed in full color.
  • Geographical schemas were displayed in full color.
  • OLE objects were displayed in full color.
  • SVG, EMF, and WMF pictures were displayed in full color.
  • Other pictures were displayed in grayscale.

In black-and-white printing mode:

  • Charts were printed in black-and-white mode.
  • Geographical schemas were printed in black-and-white mode.
  • OLE objects were printed in full color.
  • SVG, EMF, and WMF pictures were printed in full color.
  • Other pictures were printed in grayscale.
For spreadsheet document objects, eliminated differences between black-and-white view and black-and-white printing.
Charts.
The background patterns used in black-and-white chart printing are based on original chart colors. If a pattern based on an original color is already in use, the next available pattern is used instead. The total number of available patterns in increased to 27.

This change is not implemented in 8.3.11 compatibility mode.

The background patterns used in black-and-white chart printing were based on original chart colors (no check for duplicate patterns). The total number of available patterns was 12.Improved chart view for black-and-white printing.
External data sources.
During a configuration update, the platform checks whether the Group property of external data source cube commands and external data source dimension table commands is filled. If the property is not filled, the update is canceled.

This change is not implemented in 8.3.11 compatibility mode.

During a configuration update, the platform did not check whether the Group property of external data source cube commands and external data source dimension table commands was filled.Eliminated unexpected system behavior.
Data history.
Configuration extensions.
Support of data history is added to native and adopted extension objects.Native and adopted extension objects did not support data history.Data history is available for configuration extensions.
Spreadsheet documents.
In spreadsheet document headers and footers, the option to specify the first page number is implemented.

The following property is implemented: SpreadsheetDocument.FirstPageNumber. In the spreadsheet document headers and footers dialog box, the option to specify the first page number is implemented.

When a spreadsheet document is exported to OpenXML or OpenDocument format, the first page number is exported to the respective document property.

This feature was not provided.

The number of the first page was always 1.

You can generate spreadsheet documents that match the requirements of regulatory authorities.
Internet-enabled functionality.
The platform no longer uses the imaplib library.

The behavior of InternetMail object is not changed. The functionality previously provided by the library is now provided by the platform.

1C:Enterprise used the imaplib library, which provided a part of InternetMail object functionality in compatibility modes Version 8.3.5 and earlier.Improved platform stability and security.
Full-text search.
Interface.
The standard full-text search form is updated.

The History picture is added to the picture library.

The standard full-text search form looked differently.Improved usability of the standard full-text search form.
Development tools.
The following features are added to the managed form editor:
  • In the device selection menu (for mobile device view), the current device is marked.
  • In the scale selection menu (for mobile device view), the current scale is marked. Scale options similar to scale options for personal computers are implemented in this menu.
  • In the scale selection menu (for personal computer view), the current scale is marked.
  • In the resolution selection menu (for personal computer view), the following features are implemented:
    • Information about the current resolution.
    • The option to select a display (the one where the Designer window is displayed).
    • Information about typical DPI for each resolution.
    • The option to select display resolutions 4K (3840*2160 pixels) and 5K (5120*2880 pixels).
These features were not provided.Improved form editor usability.
Data composition system.
If a query parameter belongs to a query language expression that has a name, or the parameter is an independent expression, it is available for use in data composition system data parameteres (however, it is not visible to end users).

This change is not implemented in 8.3.11 compatibility mode.

If a query parameter belonged to a query language expression that had a name, or the parameter was an independent expression, it was not included in the list of available data parameters of the data composition system.Eliminated unexpected system behavior.
Dynamic lists.
If a column of a table linked to a dynamic list belongs to a column group with In cell grouping, in a document generated using the Output list command, the column header is taken from the managed form table column header.

This change is not implemented in 8.3.11 compatibility mode.

If a column of a table linked to a dynamic list belonged to a column group with In cell grouping, in a document generated using the Output list command, the column header was:
  • In the thin client, the form table column name.
  • In the web client, the form table column header.
Eliminated unexpected system behavior.
Automated testing.
The option to set and get timeouts for automated testing operations is implemented.

For TestedApplication object, methods SetActionTimeout() and GetActionTimeout() are implemented.

Clarified wordings of error messages related to attempts to connect to and/or operate applications being tested.

The option to set and get timeouts for automated testing operations was not available.

Wordings of error messages related to attempts to connect to and/or operate applications being tested were less detailed and less accurate.

You can set timeouts for automated testing operations.

Improved diagnostics for automated testing errors.

Spreadsheet documents.
If a spreadsheet document has docked rows or columns, the lines that outline the docked areas are only displayed after the document has been scrolled vertically (for rows) or horizontally (for columns).

This change is not implemented in 8.3.11 compatibility mode.

If a spreadsheet document had docked rows or columns, the lines that outlined the docked areas were always displayed.Improved report view.
Managed forms.
If the width specified for a managed form group is less than the total width of its subordinate items (at their minimum possible sizes), the specified width value is ignored. Instead, the width is calculated as follows:
  • For vertical groupings, the maximum value among the minimum width values of subordinate items.
  • For horizontal groupings, the sum of minimum width values of all subordinate items plus the total width of gaps between them.

This change is not implemented in 8.3.11 compatibility mode.

If the width specified for a managed form group was too small and some of the subordinate items could not fit even at their minimum possible sizes, the group still had the specified width.Eliminated unexpected system behavior.
Queries.
An attempt to execute a query that contains a nested query with AUTOORDER keyword generates the following error: Nested queries cannot contain AUTOORDER operation.An attempt to execute a query that contained a nested query with AUTOORDER keyword generated the following error: Nested queries cannot contain ORDER BY operation without TOP construction.The error message is more accurate.
Configuration extensions.
Notifications related to applying configuration extensions have Important status. Therefore, they are available in the notification center and users who miss them can read them later.Notifications related to applying configuration extensions had Information status. Therefore, they were not available in the notification center and, if errors occurred when applying configuration extensions, users who missed the notifications at the time they were generated missed them completely.Better diagnostics of errors related to applying configuration extensions.
Data composition system.
Dynamic lists.
When a new parameter that is a part of IN clause is added to a data set query, the data composition schema wizard automatically sets the option to use a value list as the parameter value.

If a description of a query parameter that is a part of IN clause is missing from a data composition schema, the option to use a value list as the parameter value is automatically added to the available parameter of the source of available data composition settings.

If a parameter of a dynamic list query is a part of IN clause, you can assign a value of value list type to this parameter in the dynamic list composition settings, and the dynamic list will pass the correct value list to the query.

This change is not implemented in 8.3.11 compatibility mode.

The data composition schema wizard did not automatically set the option to use a value list as the value of a data composition schema parameter.

If a parameter description was missing from a data composition schema, only a single value could be used as the parameter value.

Dynamic lists processed query parameters of value list type incorrectly.

Eliminated unexpected system behavior.

Improved data composition system behavior in scenarios where queries use value lists to set filters.

Data composition system.
In the data composition system, header templates (available for reports, tables, groupings, and charts) are not followed by blank line templates. As a result, a table or a chart header is always followed by a single blank line.

This change is not implemented in 8.3.11 compatibility mode.

In the data composition system, header templates (available for reports, tables, groupings, and charts) were followed by blank line templates. As a result, a table or a chart header was always followed by two blank lines.Eliminated unexpected system behavior.

A table or a chart header is now followed by a single blank line instead of two blank lines.

Standard functions.
In the standard full-text search management function, the option to set the maximum size of objects to be indexed and the option to set the number of background jobs used for indexing are implemented.

To set these parameters, use the dialog box that is opened using the Additional parameters button of the standard full-text search management function form.

This feature was not provided.You can specify additional parameters for full-text search indexing.
Spreadsheet documents.
In the thin client, when a spreadsheet document is saved to a PDF file, if the spreadsheet page size is not specified, the page size setting of the current printer is used instead.

This change is not implemented in 8.3.11 compatibility mode.

In the thin client, when a spreadsheet document was saved to a PDF file, if the spreadsheet page size was not specified, size A4 was used instead.Eliminated unexpected system behavior.
Data display.
In Designer, thin client, and thick client, in the font selection dialog box, when you select a font by name (for example, "Arial"), the Scale value is applied to the resulting font.

This change is not implemented in 8.3.11 compatibility mode.

In Designer, thin client, and thick client, in the font selection dialog box, when font was selected by name (for example, "Arial"), the Scale value was not applied to the resulting font.Eliminated unexpected system behavior.
Data composition system.
In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag does not set that flag to its parent parameter.

This change is not implemented in 8.3.11 compatibility mode.

In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag also set that flag to its parent parameter.Eliminated unexpected system behavior.
Managed forms.
In the property palette, the field linked to the font property displays the font name, style, appearance (bold, italic, or strikethrough), and scale.In the property palette, the field linked to the font property displays the font name and style.You can view the current font parameters in the property palette, without opening the font dialog box.
Managed forms.
Implemented the new AlwaysHorizontal value of the ChildFormItemsGroup system enum.

The Horizontal value of the ChildFormItemsGroup system enum is deprecated

If the Horizontal value is used in the application, the PC platform wil use the AlwaysHorizontal value, and the mobile platform – the HorizontalIfPossible value instead.

We recommend to replace the Horizontal by the HorizontalIfPossible value in applications in most cases. The AlwaysHorizontal value should be used only if a group must be horizontal on any screen, including mobile device screens. For example, if there is a group with an input field and a button with a picture and without text, linked to this field.

The following options of horizontal alignment of forms and form groups were available: Horizontal and HorizontalIfPossible.The smooth conversion of previously created form to the mobile client usage is available.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Settings storage.
If a report form is opened with UserSettingsKey parameter specified and UserSettings parameter missing:
  • If settings with the specified key are found in the user settings storage, these settings are loaded.
  • Otherwise the default user settings for the current report option are loaded.

This change is not implemented in 8.3.11 compatibility mode.

If a report form was opened with UserSettingsKey parameter specified and UserSettings parameter missing:
  • If user settings for the current report option were found in the system settings storage, these settings were loaded.
  • Otherwise, if settings with the specified key were found in the user settings storage, these settings were loaded.
  • Otherwise the default user settings for the current report option were loaded.
Eliminated unexpected system behavior.
Client application installation.
1C:Enterprise launcher searches for distribution packages of new 1C:Enterprise versions in the following directories: Setup (32-bit platform) and Setup64full (64-bit platform).1C:Enterprise launcher searched for distribution packages of new 1C:Enterprise versions only in directories that contained specific versions (ignoring subdirectories).Automatic client application updates support scenarios where client applications are both 32-bit and 64-bit.
Charts.
When OnIntervalEditEnd handler of a form item that displays a Gantt charts is executed:
  • The chart interval is passed to Interval handler parameter.
  • If CancelEdit handler parameter is set to False, all of the interval values are applied to the chart.
  • If CancelEdit handler parameter is set to True, interval properties Begin and End are not applied to the chart, while the rest of the interval properties are applied.

This change is not implemented in 8.3.11 compatibility mode.

When OnIntervalEditEnd handler of a form item that displays a Gantt charts was executed:
  • A copy of the chart interval was passed to Interval handler parameter.
  • The changes made in the passed interval were not applied to the chart.
The behavior of OnIntervalEditEnd handler of form items that display Gantt charts is more logical.
Event log.
Interactive editing of event log format is implemented.

The new event log event _$InfoBase$_.EventLogSettingsUpdate indicates the format change.

In file infobases, changing event log format requires exclusive infobase access.

Global context method ClearEventLog() is deprecated and only applicable to logs that have SQLite format. It is recommended that you do not use this method. +If selection from event log records takes a long time, you can abort it by deleting the session that initiated the selection.

The following limitations are applied to time-consuming selections from the event log:

  • In a nonseparated infobase: 4 sessions.
  • In a separated infobase: 1 session per data area.

The default event log format (the one that is selected in newly created infobases) is sequential format.

Interactive editing of event log format was not available.

The default event log format (the one that was selected in newly created infobases) was SQLite format.

Interactive selection of event log format is now available.

Applications no longer stop responding when performing time-consuming selections from the event log.

Temporary storages.
If the Address parameter of PutToTempStorage() method contains a value that was previously used in DeleteFromTempStorage() method, an exception is generated.

This change is not implemented in 8.3.11 compatibility mode.

If an Address parameter value was previously used in PutToTempStorage() method and then in DeleteFromTempStorage() method, an attempt to use the value in PutToTempStorage() method again was only successful if it was a UUID of a form that was open at that time.Eliminated unexpected system behavior.
Charts.
The algorithm of displaying stacked charts that have negative values is changed:
  • For charts that support base values:
    • For each point, calculate two sums: one less than the base value, the other one greater than the base value.
    • Before stacking, subtract the base value from the current value.
    • Stack the resulting value to one of the sums, depending on its sign.
  • For charts that do not support base values:
    • For each point, calculate two sums: a negative one and a positive one.
    • Stack the current value to one of the sums, based on its sign.
  • For each point, display two chart columns that represent the two sums.

This change is not implemented in 8.3.11 compatibility mode.

In stacked charts, each point had a single column that represented the sum of all values (calculated with appropriate signs).Eliminated unexpected system behavior.
Data composition system.
In data composition settings composer, when the source of user-defined settings is specified, if a data parameter value contains an array and the option to use a value list in this parameter is enabled, the parameter value is set to a value list containing all of the values from the source array.

This change is not implemented in 8.3.11 compatibility mode.

In data composition settings composer, when the source of user-defined settings was specified, if a data parameter value contained an array and the option to use a value list in this parameter was enabled, the parameter value was set to a value list containing a single value (the default value for the parameter value type).Eliminated unexpected system behavior.
Managed forms.
When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath are set from 1C:Enterprise script or a configuration with these properties is loaded from a file, if any of these properties contains a path that refers to a form item that has a row index, an error is generated.

This change is not implemented in 8.3.11 compatibility mode.

+

When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath were set from 1C:Enterprise script or a configuration with these properties was loaded from a file, if any of these properties contained a path that referred to a form item that had a row index, no errors were generated. Such property values were set but they were actually ignored.Eliminated unexpected system behavior.
Dynamic lists.
In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) are not available for filtering, sorting, or grouping.

This change is not implemented in 8.3.11 compatibility mode.

In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) were available for filtering, sorting, or grouping. However, an attempt to set a filter by a value of such field returned an error.Eliminated unexpected system behavior.
Data composition system.
If an expression of a calculated data composition system field is empty, NULL is substituted for the field value in detailed records.

This change is not implemented in 8.3.11 compatibility mode.

If an expression of a calculated data composition system field was empty, an attempt to use the field in detailed records generated a "field not found" error.Eliminated unexpected system behavior.

The system behavior is improved in scenarios where a user selects a custom field with no expression specified.

Data composition system.
If calculation of EvalExpression() function result includes division by 0, the result of the expression calculated with this function is Division by zero.

This change is not implemented in 8.3.11 compatibility mode.

If calculation of EvalExpression() function result included division by 0, the expression calculated with this function was fully calculated (Division by zero was used as the function result).Eliminated unexpected system behavior. +
Settings storage.
Each operation with the standard settings storage includes a check for SaveUserData access right.

Calls of StandardSettingsStorageManager.SetDescription() method include a check for SaveUserData access right.

Operations with the standard settings storage included checks for SaveUserData access right only if they were performed from 1C:Enterprise script.

Calls of StandardSettingsStorageManager.SetDescription() method did not include a check for SaveUserData access right.

Eliminated unexpected system behavior. In particular, commands related to dynamic list settings are no longer available to users that do not have SaveUserData access right.
Data composition system.
Items of conditional appearance of data composition system are applied using the following rules:
  • More specific conditional appearance items have higher priorities (this behavior did not change).For example, if a report, a table, and a table grouping have conditional appearances, they are prioritized as follows: table grouping (the highest priority), table, and report (the lowest priority).
  • Parts of a conditional appearance item are prioritized in accordance with their relative positions in the list: the lower the position, the higher the priority.

This change is not implemented in version 8.3.11 compatibility mode. +

Items of conditional appearance of data composition system were applied using the following rules:
  • More specific conditional appearance items had higher priorities.
  • Parts of a conditional appearance item were prioritized in accordance with their relative positions in the list—the lower the position, the higher the priority.The only exception to this rule was the list of conditional appearance items that included parts with specified filters and specified or unspecified formatted fields. In this case the conditional appearance items with formatted fields specified were applied first.
Eliminated unexpected system behavior.
Data composition system.
In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field affects the filter presentation.

This change is not implemented in version 8.3.11 compatibility mode.

In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field did not affect the filter presentation.Improved filter presentations in dynamic lists and data composition system-based reports.
Infobase operations.
When administrative infobase parameters are set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior is different from that of the previous versions. For details, see 1C:Enterprise documentation.When administrative infobase parameters were set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior was different. This behavior was not documented.Setting administrative infobase parameters is more intuitive and predictable.
Interface.
In managed applications, calls of SwitchInterface() global context method are ignored in all client modes. We recommend that you do not use ordinary forms in managed client application mode. This change is not implemented in version 8.3.11 compatibility mode.In managed applications, calls of SwitchInterface() global context method displayed command bars.Eliminated unexpected system behavior.
1C:Enterprise script.
When CurrentLanguage() global context function is called on the server, in the thick client, or in an external connection, it returns the interface language of the current user. If the current user is not specified, or the interface language is not specified, or the specified interface language is not included in the configuration, the function returns the default configuration language.

The CurrentLanguage() function behavior is now uniform across all modes.

This change is not implemented in version 8.3.11 compatibility mode.

When CurrentLanguage() global context function was called on the server, in the thick client, or in an external connection, if the interface language specified for the current user was not included in the configuration, the function returned Undefined.

The CurrentLanguage() function behavior on the client and on the server was not uniform.

Eliminated unexpected system behavior.
Data composition system.
In a nested query included in the right part of a left join, its WHERE section does not include an explicitly specified field, and the parent query includes a different field with the same data composition name, the template composer does not include the filter to the nested query.

To preserve the previous query behavior, explicitly specify a field in the WHERE section.

This change is not implemented in version 8.3.11 compatibility mode.

When filling available data set fields, the template composer always included the filter in the nested query.The result of automatic filling of available data set fields is more predictable.
Internet-enabled functionality.
In InternetMail.Logon() method, implemented authentication request with the user name and password if APOP authentication fails.The InternetMail.Logon() method generated an exception if APOP authentication failed. The authentication attempt with the user name and password was not performed.The user authentication on the mail server better complies with RFC 1939 standard.
Managed forms.
In OpenForm() method, changed the algorithm of searching for an open form instance.
  • When a data processor form or a report form is opened, the search algorithm analyzes the owner of that form.
  • When a main object form specified in the configuration or the overriding form specified in FormGetProcessing() handler is opened, if its owner is not specified, the owner window is not blocked, and a form instance is already open, the search will find it (in the thin and web clients).

This change is not implemented in version 8.3.11 compatibility mode.

The following algorithm of searching for an open form instance was used.
  • When a data processor form or a report form was opened, the search algorithm did not analyze the owner of that form.
  • When a main object form specified in the configuration or the overriding form specified in FormGetProcessing() handler was opened, if its owner was not specified, the owner window was not blocked, and a form instance was already open, a new form instance was opened (in the thin and web clients).
Eliminated unexpected system behavior. Unified the algorithm that searches for an open form in different client application modes.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Parameters of CompareCfg command-line option of Designer batch mode that define the first and second configurations to be used in a comparison.
  • FirstConfigurationKey
  • SecondConfigurationKey
  • FirstConfigurationType
  • SecondConfigurationType
Batch Designer mode command-line options that apply to mobile device applications. The former names are supported for compatibility purposes.
  • MAUpdatePublication;
  • MAWriteFile.
  • MobileAppUpdatePublication;
  • MobileAppWriteFile.
Configuration and managed form use purposes. The former names are supported for compatibility purposes.
  • MobileDevice
  • PersonalComputer
  • MobilePlatformApplication
  • PlatformApplication
Spreadsheet document command groups.

This change is not implemented in version 8.3.11 compatibility mode.

  • Print
  • View
  • Format
  • Font
  • Borders
  • Alignment
  • Groups
  • Names
  • PrintOptions
  • Pictures
  • Alignment1
  • Size
  • Distribute
  • Order
  • Comments
  • Cells
  • Merging
  • Insert
  • InsertCells
  • InsertColumns
  • ShowHideCells
  • Sizes
  • Other
  • Other1
  • Other2
  • Other3
  • CommandsPrint
  • CommandsView
  • CommandsFormat
  • CommandsFont
  • CommandsBorders
  • CommandsAlignment
  • CommandsGroups
  • CommandsNames
  • CommandsPrintOptions
  • CommandsPictures
  • CommandsPisturesAlignment
  • CommandsSize
  • CommandsDistribute
  • CommandsOrder
  • CommandsComments
  • CommandsCells
  • CommandsMerging
  • CommandsInsert
  • CommandsInsertCells
  • CommandsInsertColumns
  • CommandsShowHideCells
  • CommandsSizes
  • CommandsOther
  • CommandsOtherUndo
  • CommandsOtherClipboard
  • CommandsOtherProperties

Table of contents

Mobile version of "1C:Enterprise"

FunctionalityAfterBeforeResult of changes
Managed forms.
On Android, context menus are displayed next to the items where they belong. Opening a context menu does not change the form layout.The context menu was displayed at the top of a form. Opening a context menu changed the form layout and repositioned form items.On Android, improved usability of accessing context menus of form items.
Mobile device-specific features.
Optimized MultimediaData object generation algorithm used during device camera operations.The MultimediaData object generation algorithm used during device camera operations was not optimal.Improved performance of device camera operations in mobile applications.
Interface.
Changed the calendar view on mobile devices:
  • Better visibility of the current date
  • Implemented switching between single and multiple date choices
  • Added the context menu
  • Added the Choice event
The calendar view on the mobile device was different:
  • The current date marking was more subtle
  • Switching between single and multiple date choices was unavailable (only multiple date choice was available)
  • No context menu
  • No Choice event
Improved calendar usability on mobile devices.

Table of contents

Library updates + +

Table of contents

Demo configuration changes

Table of contents

Changes made after the publication of the version + +

FunctionalityAfterBeforeResult of changes
Web client.
Implemented the following features for file system extensions for Google Chrome and Mozilla Firefox:
  • Web server certificate authentication (users are prompted to select the authentication certificate).
  • Operating system authentication in the following scenario: a computer that runs the web client is not included in a domain, and the web server supports operating system authentication (users are prompted to specify the domain user name and password).
File system extensions for Google Chrome and Mozilla Firefox did not support the following:
  • Web server certificate authentication.
  • Operating system authentication in the following scenario: a computer that runs the web client is not included in a domain, and the web server supports operating system authentication.
Improved secure connection support. Improved web client security.
Web client.
In the web client, dragging spreadsheet document cells and pictures is implemented. If Ctrl is held down, they are copied, otherwise they are moved.

The web client behavior is now identical to the thin client behavior.

This change is not implemented in version 8.3.11 compatibility mode.

In the web client, dragging spreadsheet document cells and pictures was not supported.New interactive spreadsheet document operations in the web client.
Automated testing.
If TestedFormField or a similar object is retrieved using FindObject() or FindObjects() method, its TitleText property always stores the title value set in Designer.

This change is not implemented in version 8.3.11 compatibility mode.

If TestedFormField or a similar object was retrieved using FindObject() or FindObjects() method, if its title was explicitly specified in the form editor, a colon might be missing from the title.Eliminated unexpected system behavior.
Managed forms.
Changing the Enabled property of managed form item groups and form items in managed form tables does not require server calls.

Setting the Visible property of an input field to False results in the following:

  • If the field is linked to a text value, its value is generated from the field text and then the OnChange event handler is called.
  • If the field is linked to a reference value and a user has not finished filling it, the resulting field state might be inconsistent.

This change is not implemented in 8.3.11 version compatibility mode.

Changing the Enabled property of managed form item groups and form items in managed form tables required a server call.

Setting the Visible property of an input field to False resulted in the following:

  • If the field was linked to a text value, its value was generated from the field text, but the OnChange event handler was not called.
  • If the field was linked to a reference value, its previous value was restored.
Changing the visibility of some managed form items is optimized.
Mobile platform.
Mobile client.
Implemented the following features of the applications list in the mobile client and mobile application main menu:
  • custom list ordering;
  • alphabetical list ordering;
  • common infobase list operations (only for the web client).

Command-line parameters can be specified for each application in the applications list. The following command-line parameters are available in the mobile application and mobile client: N, P, ClearCache, C, WSA, OIDA, Autooff, DisableStartupMessahes, Z, UsePrivilegedMode, HttpsForceSSLv3, HttpsForceTLS1_0, O, L, VL, WSN, WSP, and URL. Implemented the application startup according with the set of supported command-line parameters.

These features were not provided.New application list management operations. You can now specify command-line options to fine tune the application behavior at startup.
Managed forms.
In the mobile platform and in all client applications, if a form control that has minimum width does not fit the form, the control width is reduced below the minimum.

This change is not implemented in version 8.3.11 compatibility mode.

If a form control that had minimum width did not fit the form, the control width was not reduced below the minimum.Eliminated unexpected system behavior.
Data composition system.
Rows and columns can be docked when generating a grouping header template based on a predefined template.

Columns are docked (FixLeft property of a data composition template area cell is set) if the FixLeft report setting is not set or is set to Auto. Rows are docked (FixTop property is set) if the FixTop report setting is not set or is set to Auto.

This change is not implemented in version 8.3.11 compatibility mode.

Rows and columns were never docked when generating a grouping header template based on a predefined template. Eliminated unexpected system behavior.
Queries.
If a query contains a UNION expression without the ALL keyword, a CAST AS Reference operation will return a single string with NULL value.

ISNULL() function applied to a CAST AS Reference expression returns the correct result.

This change is not implemented in version 8.3.11 compatibility mode

If a query contained a UNION expression without the ALL keyword, a CAST AS Reference operation might return multiple strings with NULL value.

ISNULL() function applied to a CAST AS Reference expression might return an incorrect result.

Eliminated unexpected system behavior.
Collaboration system.
Clarified some of the collaboration system error messages.Some of the collaboration system error messages were less clear.The collaboration system error messages are more clear now.
Data composition system.
In the settings composer of the data composition system, when the source of available settings is specified, if a parameter value is a fixed array and the parameter can store a value list, the value list that includes all the values from the initial fixed array is stored to the parameter.

This change is not implemented in version 8.3.11 compatibility mode

In the settings composer of the data composition system, when the source of available settings was specified, if a parameter value was a fixed array and the parameter could store a value list, a value list containing a single element with the default value of the parameter type was stored to the parameter.Eliminated unexpected system behavior.
Managed forms.
Unified and improved appearance of managed form control tooltips that have ToolTipRepresentation property set to Button. This change is implemented for various types of managed form controls.The appearance of managed form control tooltips that had ToolTipRepresentation property set to Button was not unified across different control types.Unified tooltip appearance for various types of form controls.
Mobile platform.
Mobile client.
Managed forms.
Internet-enabled functionality.
In mobile applications, for managed form field extension for an HTML document field, the Document property is now available.

In mobile applications, for EventData parameter of OnClick event handler of managed form field extension for an HTML document field, Document and Href parameters are now available.

Mobile platform notifications about calls of methods and properties that do not exist may be different from PC platform notifications.

These features were not provided.

On mobile devices, HTML documents displayed in forms were inaccessible.

Extended HTML document capabilities for the mobile platform.
DBMS operations.
System requirements.
Support of Microsoft SQL Server 2017 is implemented.Microsoft SQL Server 2017 was not supported.Support of Microsoft SQL Server 2017 is implemented.
Development tools.
For TextColor and BackColor properties of managed form buttons, both the property palette and the color selection dialog box now display the actual color values (if these properties are set to Auto or to any of the system style items). +For TextColor and BackColor properties of managed form buttons, both the property palette and the color selection dialog box displayed the color of the system style item (if these properties were set to Auto or to any of the system style items).The property palette now displays property values more accurately.
Localization.
The French localization of the client applications is available.This feature was not provided.1C:Enterprise is available to French-speaking users.
Mobile client.
The information in the About dialog box in the mobile client was expanded.There was less information in the About dialog box in the mobile client.The About dialog box in the mobile client is now closer to the About dialog box in the thin client.
Mobile platform.
Mobile client.
Collaboration system.
Implemented the feature of receiving and processing push notifications from the collaboration system. The mobile device application should be built with push notifications extension enabled. Notifications are generated by the pushnotifications.1c.com service from 1C company. The registration in service is performed automatically.The collaboration system did not generate mobile push notifications.Reduced risk of missing the collaboration system notification when the application is not running, or is hidden, or when the user is operating in another infobase within a single application.
Internet-enabled functionality.
Implemented the feature of including external providers in the OpenID authentication process.

For the specifics of external providers usage, refer to the documentation.

This feature was not provided.Improved the OpenID authentication support.
Mobile platform.
Mobile client.
The iPhone X screen is now supported in the 1C:Enterprise mobile version.This feature was not provided.The 1C:Enterprise mobile version interface is adapted to iPhone X.
Internet-enabled functionality.
1C:Enterprise 8 now supports cryptographic algorithms that meet the GOST R 34.10-2012 and 34.11-2012 requirements.This feature was not provided.Internet resources that demand the GOST R 34.10-2012 and 34.11-2012 compliance are now available in 1C:Enterprise 8.
Mobile platform.
Mobile client.
Mobile device-specific features.
1C:Enterprise platform does not support barcode scanning, making photos and videos on Windows Desktop.

The following methods of the MultimediaTools object return False on Windows Desktop: BarcodeScanningSupported(), PhotoSupported(), VideoRecordingSupported().

The following methods of the MultimediaTools object returned True on Windows Desktop: BarcodeScanningSupported(), PhotoSupported(), VideoRecordingSupported().Eliminated unexpected system behavior.
Pictures.
If the name of the picture from a picture library equals to the name of the configuration common picture, a warning will be generated during the database update. The database update process will not be interrupted. When accessing the picture by name, the configuration picture returns.

When this warning appears, it is recommended to review picture names in the configuration.

If the name of a picture from a picture library was equal to the name of a configuration common picture, the database update could not be performed.The database update is now available if the name of a picture from a picture library is equal to the name of a configuration common picture.
Mobile platform.
Mobile client.
Administration tools.
The 1C:Enterprise 8 mobile platform now supports OS authentication.

The HTTPConnection object constructor supports the UseOSAuthentication parameter.

This feature was not provided.The 1C:Enterprise 8 mobile platform is now sufficient when the OS authentication is required.
Data display.
Mobile client.
The 1C:Enterprise mobile platform now displays messages of the same style as other mobile messages. Messages are generated by the ShowUserNotification() method with the UserNotificationStatus parameter set to UserNotificationStatus.Information.If a message was generated by the ShowUserNotification() method with the UserNotificationStatus parameter set to UserNotificationStatus.Information, this message was not displayed.Extended capabilities of the ShowUserNotification() method in the mobile client.
Mobile platform.
Mobile client.
Managed forms.
The command set and the appearance of the context menu of a managed form table row was changed in the 1C:Enterprise mobile version.The command set and the appearance of the context menu of a managed form table row in the 1C:Enterprise mobile version were different.Improved the 1C:Enterprise mobile interface.
Internet-enabled functionality.
Improved the analysis of the root certificate revocation.

Implemented the option to specify the behavior of the platform when the root certificate revocation can not be verified unambiguously. Implemented the IgnoreServerCertificatesChainRevocationSoftFail parameter of the conf.cfg file.

These changes are available in all Internet-enabled features of 1C:Enterprise platform.

The analysis of the root certificate revocation was the same regardless of the reason why the remote node was not validated.

There was no option to specify the platform behavior when the root certificate revocation could not be verified unambiguously.

Improved diagnostics of Internet-enabled functionality. In some cases the option to specify the platform behavior is now available.
Mobile platform.
Implemented the database file validation in the verify and repair feature of the mobile platform.

This feature checks whether the database file is corrupted and prompts several solutions.

These features were not provided.

The verify and repair feature could not validate the database file.

If the database file was corrupted the session was abnormally terminated.

Improved the database file diagnostics capabilities.
Configuration extensions.
If the active extension changes the database structure it can not be deleted. If you want to delete the extension you shoud deactivate it first. You will be prompted to confirm the deletion of the inactive extension that changes the database structure.

Implemented the ConfigurationExtension.ModifiesDataStructure() method, which shows whether the configuration extension changes the database structure.

When the extension that changed the database structure was deleted no actions preventing the extension data loss were performed.Reduced risk of configuration extension data loss.
Mobile client.
Mobile application builder.
A web page where user can register in the infobase (or service) can now be specified in the mobile client. This page can be reached either automatically (if there are no registered infobases in the mobile client) or manually.

You can now specify an URL with the personal account of services that contain infobases for the mobile client.

The mobile client can now retrieve shared infobase lists from the server through special web services. You can specify multiple addresses of the same server, as well as addresses of multiple servers.

The following options are now available when building a mobile application:

  • Specifying starting page that will be displayed if the mobile client infobase list is empty.
  • Specifying a custom URL in the infobase list. This URL will be displayed by the internal mobile client features.
  • Specifying multiple web services that return shared infobase lists.
  • Entering a custom web service URL to retrieve a shared infobase list.

The e1c:// type hyperlinks are now supported as a starting page and an infobase list element in the mobile client.

Implemented the AddToStartCfg command-line option for the mobile client. It adds an infobase in the mobile client infobase list. It can be placed in web pages, specified during the mobile application customization.

OpenID authentication is not supported for accessing web-servers with shared infobase lists.

These features were not provided.The registration of an infobase or a web service in the mobile client became more clear and simple.
Event log.
Implemented the following events:
  • Managing users:
    • Error adding a user (_$User$_.NewError),
    • Error changing a user (_$User$_.UpdateError),
    • Error deleting a user (_$User$_.DeleteError).
  • Infobase operations:
    • Truncate event log (_$InfoBase$_.EventLogReduce),
    • Error truncating event log (_$InfoBase$_.EventLogReduceError),
    • Error changing event log parameters (_$InfoBase$_.EventLogSettingsUpdateError),
    • Error changing infobase parameters (_$InfoBase$_.InfoBaseAdmParamsUpdateError),
    • Start dumping infobase to file (_$InfoBase$_.DumpStart),
    • End dumping infobase to file (_$InfoBase$_.DumpFinish),
    • Error dumping infobase to file (_$InfoBase$_.DumpError),
    • Start restoring infobase from file (_$InfoBase$_.RestoreStart),
    • End restoring infobase from file (_$InfoBase$_.RestoreFinish),
    • Error restoring infobase from file (_$InfoBase$_.RestoreError),
    • Error updating database configuration (_$InfoBase$_.DBConfigUpdateError),
    • Error updating extension database configuration (_$InfoBase$_.DBConfigExtensionUpdateError).

Extended the list of data types that are handled by the following events: _$Access$_.AccessDenied, _$InfoBase$_.EventLogSettingsUpdate.

New events require the DataAdministration access right to view, except managing users events and the following ones: $InfoBase$_.DBConfigUpdateError, and _$InfoBase$_.DBConfigExtensionUpdateError.

There were less registered events and less handled data types.Improved logging events.
Data composition system.
Charts.
Some of the output parameters of the data composition system are only saved if their Use flag is set (the exact list of parameters depends on the configuration compatibility mode).
  • In compatibility mode Version 8.3.10 or earlier: ChartType.PointsScale, ChartType.ValuesScale, and ChartType.SeriesScale.
  • In compatibility mode Version 8.3.11 or earlier: ChartType.ColorPaletteDescription, ChartType.ReferenceBandsColorPaletteDescription, ChartType.ValuesReferenceLines, ChartType.ValuesReferenceBands, ChartType.PointsReferenceLines, ChartType.PointsReferenceBands. +
All of the changes in the output parameters of the data composition system were saved. This could cause issues at opening data composition settings in the earlier versions of 1C:Enterprise.Data composition settings related to charts are now usable in the earlier platform versions.
Web client.
The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins is available in the add-on store https://addons.mozilla.org. The add-on is automatically updated to newer versions as they appear in the store.The Mozilla Firefox add-on that provides access to 1C:Enterprise extensions and 1C:Enterprise add-ins was not available in the add-on store https://addons.mozilla.org. The add-on updates were delivered and installed with new 1C:Enterprise versions.Updates of the Mozilla Firefox add-on are now transparent to users.
Mobile client.
Mobile platform.
Managed forms.
In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields is now available (if their contentEditable property allows editing). At that, all formatted document functionality is supported.In the mobile version of 1C:Enterprise, in HTML document fields, full-featured editing of HTML page input fields was not available (if their contentEditable property allowed editing). +Extended HTML document functionality in the mobile version of 1C:Enterprise.
Software licensing.
Software licenses can be associated with dongles.

Human-readable information about the license is added to the bottom of activated software license files. Such files are compatible with the earlier 1C:Enterprise versions. +

Software licenses could not be associated with dongles.

Activated software license files did not contain human-readable information about the license.

The software licensing features are upgraded.
Software licensing.
New license type: 1C:Enterprise server CORP license. Implemeted a check for the CORP license if a feature requires it. The following features are available for CORP licenses:
  • More than 12 physical CPU cores
  • More than 500 simultaneous client application sessions (including Designer and external connection sessions)

The following CORP license types are available:

  • Software: for a 64-bit server; number of users: 1, 5, 10, 20, 50, 100, 300, 500, or 1000.
  • Hardware: for a 64-bit server; number of users: 50, 100, 300, 500, or 1000.

Licensing utility now supports CORP licenses.

New command: ring license update. The command updates all licenses located in the storage.

Having a CORP license was a legal requirement, not a technical requirement.A new license type: CORP. +
Internet-enabled functionality.
Add-ins.
Cryptography support.
File operations.
Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer are converted into .exe files. Distribution packages in .cab format are considered obsolete, although supported.

The add-in technology documentation is updated. (read more)

Distribution packages of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer were provided in .cab files. +Installation of the file system extension, the cryptography extension, and the add-in extension for Microsoft Internet Explorer is more convenient.
System requirements.
Linux.
The following Linux distribution packages are supported:
  • ALT Linux SPT 7
  • ALT Server 8
  • ALT Workstation K 8
  • ALT Workstation 8
  • ALT Education 8
  • ALT SP 8

Both 32-bit and 64-bit distribution packages are supported. 1C:Enterprise server clusters and client applications are supported. +

The distribution packages were not supported.Extended list of supported Linux distribution packages.
Internet-enabled functionality.
Upgrade: the credentials used as a basis for WS-reference and WSDefinition objects are only sent to the primary resource that provides a WSDL definition. If the downloaded schema requires schemas from other secondary resources, they are accessed anonymously.The credentials that had been used as a basis for WS-reference and WSDefinition objects were used to access all resources that provided WSDL definitions.To download a web service definition, if a web server requires authorization, the credentials are sent only to the primary resource selected to download the schema.
Command interface.
Upgrade: for the "All functions" dialog box in the thick and thin client applications, the search by the first characters is disabled. To open the search box, press Ctrl+F. To move to the next search result, press F3. To move to the previous search result, press Ctrl+F3.In the "All functions" dialog box, there were two ways to start a search:
  • By opening the search box with Ctrl+F (in all client applications).
  • By typing the search text in the list of configuration objects (in the thick and thin client applications). The web client did not support search by typing the search text in the list of configuration objects.
Eliminated unexpected system behavior.
Regional settings.
Upgrade: in accordance with the Federal Law of the Russian Federation No. 368-FZ, a new time zone is applied for Volgograd oblast. The update is applied to all 1C:Enterprise system components, except for the web client. The web client sets the time in accordance with the time zone information provided by the operating system and web browser. +1C:Enterprise ignored the changes introduced by the Federal Law of the Russian Federation No. 368-FZ.New time zone settings are applied due to the legislation change.
Configuration comparison and merging.
New feature: on comparing two configurations, the command order changes are displayed for the commands stored in standard command groups.On comparing two configurations, the command order changes were not displayed for the commands stored in standard command groups. Therefore, the changes were not applied to the resulting configuration.Eliminated unexpected system behavior.
Mobile application builder.
Upgrade: Mobile application builder successfully builds applications when an add-in is missing for some mobile operating systems supported by the mobile application. It records warnings about missing add-ins to the mobile application building log.

When a mobile application attempts to access a missing add-in, an exception is generated.

Mobile application builder did not allow building applications when an add-in was missing for a mobile operating system supported by the mobile application.You can build a mobile application if there is an add-in that is not required on some operating systems supported by the mobile application. +
Mobile client.
Data history.
Upgrade: the Change history command is hidden from context menus of dynamic lists in the mobile client version 8.3.12 connected to 1C:Enterprise server version 8.3.13 or later.Two Change history commands were displayed in the context menus of dynamic lists in the mobile client version 8.3.12 connected to 1C:Enterprise server version 8.3.13 or later. Both commands were unavailable.Eliminated unexpected system behavior.
Client application.
Upgrade: client applications require less RAM to handle pictures.Client applications required more RAM to handle pictures.RAM consumption by client applications when handling pictures is optimized.
Server clusters.
Upgrade: occasional performance degradation of loaded server clusters is fixed.Occasionally, performance degradation of loaded server clusters occurred.Server cluster performance is more stable.
System requirements.
Linux.
Upgrade: new approach to Linux OS distribution support. 1C:Enterprise supports only distributions listed in the system requirements. In general, the client-supported distribution list matches the server-supported distribution list, but there might be some exceptions. The list of supported Linux distributions is up-to-date.The list of supported Linux distributions was not up-to-date.The list of supported Linux distributions is brought up-to-date.
Mobile client.
Upgrade: when you use iOS mobile application home page to add an application, the compatibility check is based on the digital signatures of all configurations included in the mobile application build.When developers used iOS mobile application home page to add a new application, the application failed.You can use iOS mobile application home page to add new applications based on the configurations included in the mobile client application.
Mobile client.
New feature: the favorites setting form contains hint text on how to use this form.

Upgrade: If a mobile client form has a link, the More actions menu always contains the commands Add to favorites and Get link.

New command in the Get link dialog box that adds a link to the favorites.

The favorites setting form did not contain hint text on how to use this form.

If a mobile client form had a link, then:

  • The commands Add to favorites and Get link were added to the More actions menu only if the following conditions were met: The form had a blank command bar and the command bar had a non-blank More actions menu.
  • The commands Add to favorites and Get link were unavailable if the form had no command bar or if the command bar contained only one command.

Command of adding a link to the favorites was not available in the dialog box of the Add to favorites command.

Mobile client interface is improved. +
Mobile client.
Upgrade: the table row rearrangement command is automatically added to the table context menu instead of commands of moving rows up and down (even if command bar autofill is disabled).

Upgrade: if the multiple choice is set for a table (even if command bar autofill is disabled), the command of selecting several table rows is automatically added to the table context menu and table command bar.

The table row rearrangement command was added to the table context menu only if the context menu had been filled automatically or manually.

Command of selecting several table rows was added to the table context menu and the table command bar only if the table context menu and the table command bar had been filled automatically or manually.

Mobile client interface is improved.

Table of contents

Transition from the previous version to the version 8.3.12

Table of contents

Version 8.3.11

Version 8.3.11 includes known bug fixes and functionality modifications. +

Performance optimization for user work history is included in the list of changes implemented in 1C:Enterprise version 8.3.8.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.10 is now implemented.Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.9 was implemented.Configurations developed using 1C:Enterprise platform version 8.3.10 or earlier can run on version 8.3.11 without any changes to configuration or to data structures. This allows for transition to version 8.3.11 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.10 after the transition to version 8.3.11, even if you disabled the compatibility mode (if you did, enable it again).
Configuration comparison and merging.
Merging composite types and the contents of exchange plans, subsystems, and functional options is implemented. Viewing the differences in these objects is available both in interactive mode (in a dialog box) and in a configuration comparison report.

Automatic merging of composite types and the contents of exchange plans, subsystems, and functional options is implemented, with the option to specify the configuration that has priority.

The format of the file that stores configuration comparison and merging settings is changed.

Merging composite types and the contents of exchange plans, subsystems, and functional options was not available. Available options included taking the entire object from the configuration being loaded or keeping the existing objects without changing them.Simplified configuration comparison and merging.
Data history.
The history of database object changes is implemented. The Data history property is implemented for the following configuration objects: catalogs, documents, business processes, tasks, and information registers. The option to keep the history of attributes of these objects (including standard attributes and tabular sections), common attributes (except for data separators), and information register resources is implemented. The options to view and edit data change history, add comments to data history records, and revert to a specific data version are implemented.

Native objects of configuration extensions do not support data history.

The following access rights are implemented: ReadDataHistory, ReadDataHistoryOfMissingData, UpdateDataHistory, UpdateDataHistoryOfMissingData, UpdateSettingsDataHistory, UpdateDataHistoryVersionComment, ViewDataHistory, EditDataHistoryVersionComment, and SwitchToDataHistoryVersion.

The global context property DataHistory is implemented. It provides access to the data history from 1C:Enterprise script.

The user interface that provides access to data history is implemented.

This feature was not provided. Implementation of a change history based on built-in 1C:Enterprise tools was possible.The data history is now available as a platform-level feature. This simplifies application development and support.
Development tools.
In the managed form editor, the option to preview a form as it would look on a mobile application is implemented. This option is available in configuration compatibility mode Version 8.3.7 or later.In the managed form editor, the option to preview a form as it would look on a mobile application was not available. The preview always displayed a form as it would look on a PC.Improved form development tools for configurations that run on mobile devices.
Binary data.
A set of functions that perform bitwise operations on integer numbers is implemented. They treat numbers as unsigned 32-bit numbers. The following global context methods are implemented: CheckBit(), CheckByBitMask(), SetBit(), BitwiseAnd(), BitwiseOr(), BitwiseNot(), BitwiseAndNot(), BitwiseXor(), BitwiseShiftRight(), and BitwiseShiftLeft().

This change is not implemented in 8.3.10 compatibility mode.

1C:Enterprise only provided methods for logical operations with data stored in binary data buffers.Simplified usage of bitwise operations with numerical operands.
Database configuration update.
Server clusters.
New infobase restructuring algorithm is implemented. It features the following major differences from the previous algorithm:
  • It only processes physical database tables that were changed.
  • It performs as many changes as possible without copying tables or replicating data between the copies.
  • If replication between table versions is necessary, it is always performed using DBMS tools.

This feature has beta status. The new restructuring algorithm is only used in client/server mode with Microsoft SQL Server or PostgreSQL DBMS.

The new restructuring algorithm requires Java 1.8 to be installed on the computer that runs 1C:Enterprise server.

For the conf.cfg file, new parameters JavaHome, JavaOpts, and UpdateDBCfg are implemented.

This feature was not provided.The new algorithm significantly improves the performance of infobase restructuring. This reduces the maintenance downtime during application updates on production servers.
Data display.
Dynamic lists.
For the format string parameter of Format() function, the option to include a number format template is implemented. The new NF format string parameter is implemented for this purpose. The template specifies the position of a number in a string.

The search in dynamic lists is based on the format specified for list columns. The search results are highlighted even in cells that contain string constants before and/or after the number.

This change is not implemented in 8.3.10 compatibility mode.

These features were not provided.You can display formatted values with measurement units in charts and in other interface items that support format strings.
Development tools.
In batch Designer mode, the configuration check includes the option to check configuration modules for synchronous method calls.

For /CheckConfig command-line option, the -CheckUseSynchronousCalls parameter is implemented. If you specify this parameter, you also have to specify the -ExtendedModulesCheck parameter for this command-line option.

The option to check configuration modules for synchronous method calls during a configuration check initiated from batch Designer mode was not available. This option was only available if Designer was running in interactive mode.Eliminated unexpected system behavior.
Web services and HTTP services.
Configuration extensions.
For native configuration extension objects of web service and HTTP service types, support of configurable session reuse is implemented.For native configuration extension objects of web service and HTTP service types, configurable session reuse was not available.Unified platform behavior for accessing similar mechanisms from a configuration and from an extension.
Collaboration system.
Sending messages from a 1C:Enterprise server to a client application is implemented. A configured collaboration system operates as transport for message exchange purposes. Client applications can get messages both synchronously and asynchronously, depending on the server call type: a regular call or a background job. +For collaboration system manager, the following methods are implemented: CreateUser(), DeleteMessage(), BeginAttachNewMessagesHandler(), BeginDetachNewMessagesHandler(), and a new variant of GetConversation() method. For CollaborationSystemConversation object, Key and Visible properties are implemented. For CollaborationSystemConversationsFilter object, Key and Displayed properties are implemented. The CollaborationSystemMessage object and some of its properties (Author, Date, ID, Recipients, and Text) are now available on the client. For CollaborationSystemMessage object, Data and Conversation properties are implemented. Objects CollaborationSystemConversationID and CollaborationSystemMessageID are are now available on the client. Objects CollaborationSystemUserID and CollaborationSystemUserIDCollection, their properties, and their methods are now available on the client.This feature was not provided.

The CollaborationSystemMessage object and some of its properties (Author, Date, ID, Recipients, and Text) were only available on 1C:Enterprise server. Objects CollaborationSystemConversationID and CollaborationSystemMessageID were only available on 1C:Enterprise server. Objects CollaborationSystemUserID and CollaborationSystemUserIDCollection, their properties, and their methods were only available on 1C:Enterprise server.

You can implement client notifications for events that occur on 1C:Enterprise server.
Collaboration system.
The option to attach a handler that is executed after sending a collaboration system message is implemented. A message can now include hyperlinks; clicking a hyperlink executes the handler or a standard action assigned to the hyperlink .

For CollaborationSystemManager object, the following methods are implemented: AttachAfterMessageSendHandler(), DetachAfterMessageSendHandler(), AttachMessageActionHandler(), and DetachMessageActionHandler(). The CollaborationSystemMessage.Actions property is implemented.

CollaborationSystemConversation and CollaborationSystemConversationContext objects are now available in client applications.

These features were not provided. CollaborationSystemConversation and CollaborationSystemConversationContext objects were only available on 1C:Enterprise server.

+

Expanded collaboration system capabilities. You can implement automatic replies to incoming messages.
Queries.
For QuerySchemaQueryBatch, QuerySchemaOperators, QuerySchemaColumns, QuerySchemaIndexExpression, QuerySchemaOrderExpression, and QuerySchemaTotalCalculationFields objects, the MoveTo() method is implemented. It moves a collection element to the specified position.This feature was not provided.Expanded development tools for some collections related to query schemas.
Configuration extensions.
Applied objects.
In configuration extensions, support of native catalogs, documents, exchange plans, and information registers is implemented.

For adopted catalogs and documents, the option to add attributes and tabular setions in extensions is implemented.

A native exchange plan can only include native extension objects. A native exchange plan cannot be used in a distributed infobase. The option to add native extension objects to adopted exchange plans is implemented.

The full list of limitations is provided in the documentation.

Deleting an extension deletes all data that was added to native extension objects from the infobase.

These features were not provided.Expanded configuration extension capabilities.

An extension attached to an infobase can store its data in the infobase.

Information registers.
For InformationRegisterRecordKey object, the option to get the related metadata object is implemented. The method InformationRegisterRecordKey.Metadata() is implemented.

This change is not implemented in 8.3.10 compatibility mode.

Getting the related metadata object directly from the InformationRegisterRecordKey object was not available.Getting metadata related to information register record keys is now similar to getting metadata from other configuration objects.
Charts.
For stock charts, support of the following properties of ValuesAxis object is implemented: MinValueDetectionMethod, MinValue, MaxValueDetectionMethod, and MaxValue.

This change is not implemented in 8.3.10 compatibility mode.

For stock charts, values of the following properties of ValuesAxis object did not affect the chart view: MinValueDetectionMethod, MinValue, MaxValueDetectionMethod, and MaxValue.Improved stock chart display options.
Standard functions.
Event log.
In the event log, for Users.Add and Users.Modify events, OpenIDAuthentication and UnsafeOperationProtection properties are implemented (in the Data field of the log record).

For Users.Add and Users.Modify events, the log viewer now displays OpenID authentication and Unsafe operation protection properties.

This change is not implemented in 8.3.10 compatibility mode.

For events that described adding or modifying a user, the OpenID authentication flag and unsafe operation protection flag were recorded to the event log but were not available for viewing.Eliminated unexpected system behavior. You can access data that was previously unavailable.
Software licensing.
In the license acquisition wizard, selecting a country from a list is implemented.In the license acquisition wizard, one could enter any word as a country name.Eliminated issues that occurred due to entering incorrect country name during software license acquisition.
DBMS operations.
System requirements.
Support of Oracle Database version 11.2.0.4 (Linux) is implemented. It is only supported with patch 20954292.

Oracle Database version 11.2.0.4 (Windows) is only supported with patches 24591646 and 24591637.

Oracle Database version 11.2.0.4 (Linux) was not supported.

Oracle Database version 11.2.0.4 (Windows) was supported without the requirement to install any patches.

Extended list of supported Oracle Database versions.
Technological log.
<WINCERT> technological log event is implemented. It is intended for investigating errors related to certificate validation using Windows API methods.

This event can only be generated on Windows.

This feature was not provided.Simplified investigation of errors related to certificate validation on Windows.
Collaboration system.
Local collaboration system server is now available.

The server is provided as a standalone distribution package, it requires separate installation.

This feature is currently in beta status.

This feature was not provided. The collaboration system only worked over 1cDialog.com service.You can install and use a local collaboration system server.
Software licensing.
System requirements.
If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later is considered valid when verified with ring license command with validate option.

Using --validate parameter with activate or prepare-request option returns an error if a run-time error occurs when attempting to retrieve any of the key parameters. The behavior of these options when they are used without this parameter is not changed.

The license command requires ring utility version 0.8.

If one of the key computer parameters was changed, a license activated on 1C:Enterpirse 8.2.15 or later was considered invalid when verified with ring license command with validate option.

If a run-time error occured when attempting to retrieve any of the key parameters, the license was activated successfully and the corresponding license fields were filled with blank values, making the license impossible to use.

The license command required ring utility version 0.6.

Eliminated unexpected system behavior.
DBMS operations.
System requirements.
Support of PostgreSQL version 9.4.5 from AstraLinux Special Edition 1.5 is implemented, starting with 1C:Enterprise version 8.3.11.3034.PostgreSQL version 9.4.5 from AstraLinux Special Edition 1.5 was not supported.Extended list of supported DBMS.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Managed forms.
Improved usability of line selection in managed form tables. You can use Ctrl and Shift keys, as well as mouse buttons, to select table lines.

This change is not implemented in 8.3.10 compatibility mode.

The only way to select multiple lines in a managed form table was clicking each line while holding down Ctrl.Improved usability of line selection in managed form tables.
Web client.
A single application can be accessed from multiple web browser tabs.An attempt to run a second application instance in a second web browser tab generated an error.The platform supports running multiple web client sessions in a single web browser.
Client application installation.
Implemented a unified name "access application" for all client application types in messages displayed during client application update over HTTP.In messages displayed during client application update over HTTP, two terms were alternately used for client application: "data viewer" and "access program".Unified terminology in messages related to access application update over HTTP.
Managed forms.
Data display.
When a managed form table is exported using the Output list command:
  • The view of blank values of Number and Date type in the resulting document exactly matches their view in the form.
  • If the table is exported to a text document, tab characters separate all columns of the resulting document.

This change is not implemented in 8.3.10 compatibility mode.

When a managed form table was exported using the Output list command:
  • The view of blank values of Number and Date type in the resulting document might not exactly match their view in the form.
  • If the table was exported to a text document, tab characters were only added after the first column that contained a nonblank value.
Eliminated unexpected system behavior.
Managed forms.
Data display.
When a managed form table with multiple lines selected is exported using the Output list command (with the Selected items only check box selected):
  • The lines are exported in their original order.
  • If the table displays a dynamic list in Hierarchical list or Tree mode, all of the selected lines are exported, regardless of their positions in the list hierarchy.

The performance of the Output list command (with the Selected items only check box selected) is improved in the following scenario: the table displays a dynamic list, a large number of lines is selected, and the dynamic list query is not efficient.

This change is not implemented in 8.3.10 compatibility mode.

When a managed form table with multiple lines selected was exported using the Output list command (with the Selected items only check box selected):
  • The lines were exported in the order they were selected.
  • If the table displayed a dynamic list in Hierarchical list or Tree mode, some of the lines were not exported.

The performance of the Output list command (with the Selected items only check box selected) was insufficient in the following scenario: the table displayed a dynamic list, a large number of lines was selected, and the dynamic list query was not efficient.

Improved alrogithm of exporting a managed form table to a spreadsheet or text document.
Collaboration system.
The recipient selection procedure in context conversation messages is modified. If the sender does not want to notify any of the users who can see the message (i.e. users having the right to access the object that provides the context), they must explicitly select No notification.

Sending a message to an empty list of recipients is not allowed.

Sending a context message with an empty list of recipients was possible.Improved notification usability.
Spreadsheet documents.
The commands that perform the following operations are added to the Table section of the main application menu:
  • Align pictures (Alignment section)
  • Resize pictures (Size section)
  • Auto space multiple pictures (Distribute section)
  • Order pictures (Order section)
These commands were not available in managed client applications.Added support of interactive operations with pictures to managed applications.
Collaboration system.
During video calls in the thin and web clients, 1C:Enterprise performs the diagnostics of Internet connection quality. If the quality is insufficient, 1C:Enterprise displays the diagnostics report over the video feed.During video calls, if the Internet connection quality was insufficient, 1C:Enterprise did not display any diagnostics data. In some cases the picture might freeze without any explanations.Diagnostics of Internet connection quality during collaboration system video calls are implemented.
Standard functions.
If an application does not contain any objects that can be involved in totals management, when you attempt open the totals management dialog box in ordinary application mode (Main menu – Operations – Totals management), 1C:Enterprise displays a diagnostics message instead of the dialog box.If an application did not contain any objects that could be involved in totals management, an attempt open the totals management dialog box in ordinary application mode (Main menu – Operations – Totals management) did not open the dialog box and no diagnostics messages were displayed.Improved 1C:Enterprise usability.
Managed forms.
The tab order of managed form groups does not depend on the United property value of subordinate groups. It depends on group settings (horizontal or vertical).

This change is not implemented in 8.3.10 compatibility mode.

+

The tab order of managed form groups depended on the United property value of subordinate groups. Groups where United was set to False were ignored, their settings did not affect the tab order.Eliminated unexpected system behavior.
Client application.
Pressing F1 or using Help menu command always opens identical help pages regardless of client application or interface mode.Pressing F1 or using Help menu command might open different help pages depending on client application, interface mode, or help opening method.Eliminated unexpected system behavior.
Collaboration system.
If forced switching to the recipients field of a context collaboration system conversation is performed (after an attempt to send a message without any recipients specified), once a user selects a recipient, the focus is set to the message text field.If forced switching to the recipients field of a context collaboration system conversation was performed (after an attempt to send a message without any recipients specified), once a user selected a recipient (i.e. selected any option except for No notification), the focus stayed in the recipients field.Improved interface for sending messages in context collaboration system conversations.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
DBMS operations.
Queries.
In applications that use PostgreSQL DBMS, the conversion of LIKE `TEXT%` query language operation to an SQL query operation is optimized. +This change is not implemented in 8.3.10 compatibility mode. In applications that used PostgreSQL DBMS, the conversion of LIKE `TEXT%` query language operation to an SQL query operation was not optimal.In applications that use PostgreSQL DBMS, improved performance of search by beginning of a string in the query language.
Full-text search.
The access rights verification for full-text search results is optimized in scenarios where the search returns over 100 results.

This change is not implemented in 8.3.10 compatibility mode.

The performance of access rights verification for full-text search results in scenarios where the search returned over 100 results was insufficient.Reduced time of getting full-text search results for users with access right restrictions in scenarios where the search returns over 100 results.
Spreadsheet documents.
The performance of CheckPut() method of spreadsheet document is improved.The performance of CheckPut() method of spreadsheet document was insufficient.Faster data output to a spreadsheet document in scenarios that include the check whether the output area fits a single page.
External reports and data processors.
Server clusters.
Client application.
Improved performance of loading external reports and data processors in client applications and on 1C:Enterprise server. Intensive work with external reports and data processors does not cause lags.The performance of loading external reports and data processors in client applications and on 1C:Enterprise server was insufficient. Intensive work with external reports and data processors caused lags.Eliminated 1C:Enterprise server lags in scenarios that involve inrtensive work with external reports and data processors.
Internet-enabled functionality.
Improved 1C:Enterprise performance and scalability in scenarios that involve using HTTPConnection and FTPConnection objects on 1C:Enterprise server (if these connections belong to different sessions).

+

1C:Enterprise performance was significantly reduced in scenarios that involved using HTTPConnection and FTPConnection objects on 1C:Enterprise server (if these connections belonged to different sessions).Improved 1C:Enterprise server performance in scenarios that involve multiple HTTP or FTP connections from different sessions.
DBMS operations.
Improved performance of operations with temporary tables in scenarios that involve the following Microsoft SQL Server versions:
  • 2012, version 11.0.5548.0 or earlier
  • 2014, version 12.0.2430.0 or earlier
  • 2016
The performance of operations with temporary tables in scenarios that involved some Microsoft SQL Server versions was insufficient.Improved performance of operations with temporary tables in scenarios that involve some Microsoft SQL Server versions.
Cryptography support.
Internet-enabled functionality.
On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions.On Windows, the performance of cryptography operations and operations over SSL and TLS protocols was insufficient in scenarios where these operations were running simultaneously in a large number of sessions.On Windows, improved the performance of cryptography operations and operations over SSL and TLS protocols in scenarios where these operations are running simultaneously in a large number of sessions.
Background and scheduled jobs.
Configuration extensions.
The performance of starting background jobs is improved in infobases that run in file mode and use extensions.The performance of starting background jobs in infobases that ran in file mode and used extensions was insufficient.Eliminated unexpected system behavior.
Development tools.
The performance of the following Designer operations is improved:
  • Opening 1C:Enterprise script editor
  • Extended module check
The performance of the following Designer operations was insufficient:
  • Opening 1C:Enterprise script editor
  • Extended module check
Improved perfromance of frequently used development tools.
System requirements.
The size of executable files of 1C:Enterprise is reduced.Executable files of 1C:Enterprise required more disk space.Reduced 1C:Enterprise requirements to available disk space.
Development tools.
In 1C:Enterprise script editor, the performance of the following operations is improved:
  • Opening large modules
  • Opening context help
  • Switching to method or variable declaration
  • Module syntax check
For large modules, the performance of 1C:Enterprise script editor was insufficient.Improved usability for application developers.
Infobase operations.
Improved the performance of loading infobases from .dt files in systems that use IBM DB2.Loading infobases from .dt files in systems that used IBM DB2 took more time.Reduced time of moving infobases in systems that use IBM DB2.
Managed locks.
Server clusters.
The 1C:Enterprise server performance in scenarios with simultaneous posting of large documents (dozens of thousands of lines) is improved.Simultaneous posting of large documents (dozens of thousands of lines) could hang the server cluster.Improved performance of 1C:Enterprise server under heavy load.
Spreadsheet documents.
The performance of drawing spreadsheet documents with a lot of pictures in hidden rows is improved.Drawing spreadsheet documents with a lot of pictures in hidden rows took more time.Improved performance of operations with spreadsheet documents that contain a lot of pictures in hidden rows.
DBMS operations.
Optimized operations with large temporary tables in PostgreSQL.The performance of operations with large temporary tables in PostgreSQL was insufficient.Improved performance of operations with large temporary tables in PostgreSQL.
DBMS operations.
Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.

The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient.Improved performance of temporary table operations.
Infobase operations.
In file infobases that contain large amounts of metadata, improved performance of metadata restructuring. The performance of restructuring data tables has not changed.In file infobases that contained large amounts of metadata, metadata resturcturing took more time.If a configuration contains a large amount of metadata and its metadata structure has changed, the performance of restructuring file infobases based on this configuration is improved.
Managed forms.
Improved performance of adding lines to form attributes of FormDataTree type in the thick and thin clients. The peformance improvement is most noticeable in trees that contain large numbers of lines.Adding lines to form attributes of FormDataTree type took more time in trees that contained large numbers of lines.Improved performance of operations with form data.
Dynamic lists.
Improved performance of opening forms that contain dynamic lists.Opening forms that contained dynamic lists took more time.Improved performance of opening forms that contain dynamic lists.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Client application.
When 1C:Enterprise opens an infobase that is not registered in its infobase list, it creates a directory for storing the service data of the infobase. It creates an individual directory with a unique name for each infobase connection string and each infobase user. The maximum number of directories is 20.When 1C:Enterprise opened an infobase that was not registered in its infobase list, it used a directory with a predefined name for storing the service data of all such infobases: 00000000-0000-0000-0000-00000000000.The service data of infobases that are not registered in the infobase list is stored in dedicated directories. This facilitates disk space management and prevents the growth of a single directory.
Development tools.
When a custom command of a metadata object is renamed, the platform checks whether the new name exactly matches the name of any standard command of that metadata object. The platform also performs this check during the configuration logical integrity check.This feature was not provided.

Names of custom commands of a metadata object could exactly match the names of its standard commands.

Eliminated unexpected system behavior.
Charts.
The chart scale view settings are expanded, they now include scale view, color, and position, scale label angle, grid line visibility and color, and more.

For ChartScale object, the following properties are implemented: GridLinesShowMode, GridLine, GridLineColor, LabelFont, LabelColor, LabelOrientation, MaxLabelRows, LabelAngle, LabelFormat, ScaleLocation, ScaleLine, ScaleLineColor, ScaleStep, ScaleMarkLocation, and ScaleLabelLocation.

The following properties of ChartPlotArea object are deprecated, they are supported solely for compatibility purposes:

  • ShowSeriesScaleLabels. Use SeriesScale.ScaleLabelLocation instead.
  • ShowPointsScaleLabels. Use PointsScale.ScaleLabelLocation instead.
  • ShowValuesScaleLabels. Use ValuesScale.ScaleLabelLocation instead.
  • ShowScaleValueLines. Use ValuesScale.GridLinesShowMode instead.
  • ValueScaleFormat. Use ValuesScale.LabelFormat instead.
  • LabelsOrientation. Use PointsScale.LabelOrientation instead.

In version 8.3.10 compatibility mode, the following properties are hidden from the property palette and do not affect the chart view:

  • LabelAngle
  • ScaleLocation
  • MaxLabelRows
  • ScaleMarkLocation
  • ScaleLabelLocation
These features were not provided.

The chart scale view settings were simpler.

Expanded chart view options.
Full-text search.
The following full-text search features are implemented:
  • In privileged mode, the platform does not check the access rights for objects processed by full-text search.
  • The option to specify whether full-text search gets object presentations is implemented. The FullTextSearchList.GetPresentation property is implemented. The platform always checks the access rights for the object fields that form the presentation, regardless of the value of this property.
  • The platform always checks the access rights for the object fields that form the object description, regardless of the value of FullTextSearchList.GetDescription property.

To apply these changes, disable the compatibility mode and rebuild the full-text search index. Previous 1C:Enterprise versions cannot work with indexes built in version 8.3.11 with compatibility mode disabled. +This change is not implemented in 8.3.10 compatibility mode.

Full-text search worked as follows:
  • In privileged mode, the platform checked the access rights for objects processed by full-text search.
  • The platform did not check the access rights for object fields that formed the presentation if FullTextSearchList.GetDescription property was set to False.
Optimized full-text search.
Data composition system.
Spreadsheet documents.
In the data compostion system, nested charts and tables of the resulting spreadsheet document are located in spreadsheet document groupings. The data composition system template composer creates blank templates with VerticalLevel property set. These templates follow the templates of charts and tables located in groupings.

This change is not implemented in 8.3.10 compatibility mode.

In the data compostion system, the resulting spreadsheet document did not contain groupings for charts and nested tables that did not have row groupings. The template composer did not create blank templates with VerticalLevel property set that followed the chart templates. For tables located in groupings, the composer created blank templates with VerticalLevel set to 0.Eliminated unexpected system behavior.
XML and XDTO support.
The option to download XSD documents that import schemas that require HTTP requests to external servers (with redirects) is implemented.

This change is not implemented in 8.3.10 compatibility mode.

The option to download XSD documents that imported schemas that required HTTP requests to external servers (with redirects) was not available.Eliminated unexpected system behavior.
Development tools.
Client application.
In the search and replace dialog box of the text editor, the following behavior of the Replace button is implemented:
  • If the selected text fragment matches the search string, replace it and search for the next occurrence.
  • Otherwise search for the next occurrence. Clicking Replace again replaces it.
In the search and replace dialog box of the text editor, clicking the Replace button searched for the next occurrence of the search string. Clicking Replace again replaced it.Eliminated unexpected system behavior.
Spreadsheet documents.
In the dialog box for setting a spreadsheet document area name, the default name is generated in the language that matches the current 1C:Enterprise script variant.

This change is not implemented in 8.3.10 compatibility mode.

In the dialog box for setting a spreadsheet document area name, the default name was generated in the language that matched the client application interface language.Eliminated unexpected system behavior.
Development tools.
During the creation of a configuration update file, the message stating that the configuration update requires 1C:Enterprise version 8.3.9.2033 or later is no longer displayed.During the creation of a configuration update file, the message stating that the configuration update required 1C:Enterprise version 8.3.9.2033 or later was displayed.Removed a message that is no longer relevant.
XML and XDTO support.
When an XSD schema is imported to an XDTO package, for references to global elements and attributes, the default and fixed properties are imported to DefaultValue and Fixed properties, regardless of the element or attribute declaration type.When an XSD schema was imported to an XDTO package, for references to global elements and attributes, the default and fixed properties that were specified locally were not imported.Eliminated unexpected system behavior.
Dynamic lists.
If a dynamic list contains PredefinedDataName and DataVersion fields, the following rules apply to these fields:
  • Only the following comparison types are available: Equal to, Not equal, In list, Not in list, Filled, and Empty.
  • Search through the search field of the dynamic list is not supported.
  • Advanced search is only available by exact match.
If a dynamic list contained PredefinedDataName and DataVersion fields, the following rules applied to these fields:
  • All comparison types were available.
  • Search through the search field of the dynamic list generated an error.
  • Advanced search allowed selection of any search type but generated an error if search at beginning of line or anywhere in the line was selected.
Eliminated unexpected system behavior.
1C:Enterprise script.
The option to omit a notification description handler is implemented. Use this option in scenarios where you would create an empty handler (because the result of the execution of an asynchronous method is not important and only the handler for the method errors is important).

Now you can omit any parameter of the NotifyDescription constructor.

A handler for asynchronous method errors could only be created together with an empty handler for the method execution result.Simplified handling of asynchronous method errors.
ZIP archive operations.
When 1C:Enterprise accesses a file name using the properties of ZipFileEntry object (this includes the scenario when a file is being written to the disk), it replaces invalid characters with underscores (_). The list of invalid characters includes all characters that are not allowed in Windows file names. 1C:Enterprise makes the replacement on all operating systems.This change is not implemented in 8.3.10 compatibility mode.

To provide access to the original file names (before the character replacement), the following properties are implemented for ZipFileEntry object: OriginalFullName, OriginalName, OriginalPath, OriginalExtension, and OriginalBaseName.

If a name of a file stored in a ZIP archive contained invalid characters, the name was truncated, leaving only the part before the first invalid character. The list of invalid characters included all characters that were not allowed in Windows file names. This might cause issues when extracting files whose names contained invalid characters.Any file can be successfully extracted from a ZIP archive on any operating system. The names of the extracted files might change,
Data display.
Spreadsheet documents.
The look of a spreadsheet document containing SVG pictures in the thin client exactly matches the look of that document in the following cases:
  • In the web client
  • When exported to HTML5 format
The look of a spreadsheet document containing SVG pictures in the thin client could differ from the look of that document in the following cases:
  • In the web client
  • When exported to HTML5 format
Unified look of spreadsheet documents in various client applications and export formats.
Infobase operations.
Server clusters.
In client/server mode, the reliability of the following operations is improved:
  • Restructure database configuration
  • Create initial image of a distributed infobase
  • Restore infobase from a .dt file
In client/server mode, the following operations might cause issues:
  • Restructure database configuration
  • Create initial image of a distributed infobase
  • Restore infobase from a .dt file
Improved reliability of some operations in client/server mode.
Spreadsheet documents.
Web client.
When a spreadsheet document is exported to PDF format, the resulting document includes the page size and orientation (PickTrayByPDFSize property of a PDF document).

If you need to print the resulting document on custom-size paper from a web browser, it is recommended that you set the PrintAccuracy property of the spreadsheet document to Accurate. In Microsoft Internet Explorer, you do not need to use this property.

When a spreadsheet document was exported to PDF format, the resulting document did not include the page size and orientation. Printing the resulting document required a manual check of paper size and orientation in the PDF viewer.Eliminated unexpected system behavior.
Common objects.
Configuration properties.
If you access the UsePurpose property of the entire configuration or a managed form from 1C:Enterprise script, it has Undefined value.When the UsePurpose property of the entire configuration or a managed form was accessed from 1C:Enterprise script, it had FixedArray type, with the selected values as array elements.Eliminated unexpected system behavior. The behavior of this property is now similar to the behavior of other properties that do not affect application functionality in 1C:Enterprise mode.
Web client.
In the web client, the performance of opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, is improved.In the web client, opening system dialog boxes, as well as dialog boxes opened using ShowQueryBox() and ShowMessageBox() methods, took more time.Improved performance and reliability of the window subsystem of the web client.
Spreadsheet documents.
In spreadsheet documents, there is no spacing between pictures and their borders.

This change is not implemented in 8.3.10 compatibility mode.

In spreadsheet documents, unexprected spacing might appear between pictures and their borders.Eliminated unexpected system behavior.
Full-text search.
Morphological full-text search by attribute name is now supported.

It is recommended that you rebuild the full-text search index in order to use this feature.

This change is not implemented in 8.3.10 compatibility mode.

Morphological full-text search by attribute name was not supported.Full-text search by attribute name is more user-friendly.
Data exchange.
ThisNode() method of ExchangePlan object always returns a reference to the exchange plan item with ThisNode property set to True.

This change is not implemented in 8.3.10 compatibility mode.

ThisNode() method of ExchangePlan object did not always return a reference to the exchange plan item with ThisNode property set to True.Eliminated unexpected system behavior.
Queries.
In the query language, if a CASE operation includes a nested CASE operation or ISNULL() function, which uses both a virtual field and a nonvirtual field, the CASE calculation result is correct.In the query language, if a CASE operation included a nested CASE operation or ISNULL() function, which used both a virtual field and a nonvirtual field, the CASE calculation result was incorrect and this might cause an unexpected shutdown.Eliminated unexpected system behavior.
Charts.
The chart view in the thin client and web client is unified:
  • Area sizes specified in the form attribute always affect the chart view.
  • Chart behavior is unified across client applications.
  • Area sizes used to draw a chart exactly match the area sizes retrieved using 1C:Enterprise script.

This change is not implemented in 8.3.10 compatibility mode.

The chart views in the thin client and web client were different:
  • Area sizes specified in the form attribute did not always affect the chart view.
  • Chart behavior was not unified across client applications.
  • Area sizes used to draw a chart did not exactly match the area sizes retrieved using 1C:Enterprise script.
Eliminated unexpected system behavior. The chart view is more predictable.
Development tools.
During application debug, you can access variable properties (provided that it has properties) even if the variable presentation is not available.During application debug, if a variable presentation was not available, the variable properties were also not available.Eliminated unexpected system behavior.
Dumping configurations to files/Restoring configurations from files.
Intertactive export of configurations to files is always performed in hierarchical format. The flat format is only supported in batch Designer mode.

It is recommended that you always use the hierarchical format.

The interactive export of configurations to files offered a choice between flat and hierarchical formats.The option to export configuration files in flat format is disabled due to possible issues. For example, transferring exported files between different file systems might be difficult.
Development tools.
During debugging over TCP, debugger no longer stops responding while calculating an expression or editing a variable value.During debugging over TCP, debugger might stop responding while calculating an expression or editing a variable value.Application debugging over TCP is more predictable and reliable.
Client application.
In the Start menu, a single shortcut combines 32-bit and 64-bit versions of 1C:Enterprise.

1C:Enterprise installation on a computer with any operation system of Windows family adds all of the available 1C:Enterprise shortcuts to the Start menu.

Pinning a running 1C:Enterprise application to the taskbar actually pins a shortcut to file 1cestart.exe. If multiple 1C:Enterprise applications are running, they are combined into a single taskbar shortcut.

The jump list is only available if the shortcut to 1cestart.exe is pinned to the taskbar.

The Start menu included two 1C:Enterprise shortcuts: one for the 32-bit version and the other one for the 64-bit version.

1C:Enterprise installation on Windows 8 or later did not add all of the available 1C:Enterprise shortcuts to the Start menu.

Pinning a running 1C:Enterprise application to the taskbar pinned exactly that application. If multiple 1C:Enterprise applications were running, they were combined in this shortcut.

The jump list was available for any 1C:Enterprise-related shortcut.

All of the 1C:Enterprise components are available on the Start menu. The jump list behaviour is more predictable.
Data composition system.
The parsing algorithm of data composition system queries validates comparison operations that include String parameters of unlimited length. The parsing is performed when the data composition system wizard is opened and when a schema-based source of available settings is initialized (opening reports also includes this operation).The parsing algorithm of data composition system queries that included String parameters of unlimited length generated errors stating that using strings of unlimited length in queries was not allowed.Eliminated unexpected system behavior.
Collaboration system.
In the collaboration system, video calls use peer-to-peer connections instead of using a central server. The central server is only required to establish connections between the conversation participants.In the collaboration system, video calls always used the central server and did not use peer-to-peer connections.Reduced load on the central server of the collaboration system. If conversation participants belong to a local network, the video call traffic is limited to local network.
Collaboration system.
If 1C:Enterprise connects to the collaboration server through a proxy server, it gets the proxy server settings from the operating system settings or from inetcfg.xml configuration file. NTLM authentication at proxy servers is not supported.Connection to the collaboration server through a proxy server was not supported.Simplified collaboration system setup in scenarios that include a proxy server.
Information registers.
When an information register record set is written using InformationRegisterRecordSet.Write(), Undefined value is not ignored when setting a managed lock.

This change is not implemented in 8.3.10 compatibility mode.

When an information register record set was written using InformationRegisterRecordSet.Write(), Undefined value was ignored when setting a managed lock. This resulted in locking excessive data.Improved parallel writing of information register record sets when multiple users write dimensions of composite types where dimension values can be blank.
Localization.
Support of Kazakh user interface (kk language code) is restored.Support of Kazakh user interface was not available.1C:Enterprise now provides the option to use Kazakh user interface.
Localization.
The French interface language (language code: fr) is not supported.The French interface language (language code: fr) was supported.The French interface language is not supported.
Server clusters.
On Linux, the working process parameter Memory occupied is calculated based on VmRSS (resident set size) value.

The value of Memory occupied parameter in absolute terms is reduced and it is more accurate.

It is recommended that you revise the working process restart options in the working server properties.

On Linux, the working process parameter Memory occupied was calculated based on VmSize (virtual memory usage) value.

+

+

On Linux, the cluster monitoring system uses a parameter that provides more accurate data.
Localization.
Entering Russian Ruble symbol (₽, ISO 4217 643) from the keyboard is supported.This feature was not provided.Eliminated unexpected system behavior.
Applied objects.
When floating point numbers are converted between 1C:Enterprise format and external formats, the accuracy of their presentations is never lost.

In scenarios where previously accuracy losses were possible, the conversion algorithm does not depend on the operating system.

When floating point numbers were converted between 1C:Enterprise format and external formats, accuracy losses were possible.

In scenarios where accuracy losses were possible, the conversion algorithm depended on the operation system.

Reduced number of scenarios where conversion of floating point numbers with significant digits in their fractional parts between 1C:Enterprise format and external formats (such as XSL file format) introduces accuracy losses.
Linux.
Improved reliability of the Linux version of 1C:Enterprise in some scenarios.In some scenarios, reliability of the Linux version of 1C:Enterprise was insufficient.Improved stability of the Linux version of 1C:Enterprise.
Technological log.
Updated the <ADMIN> event content and description in the documentation and in the technological log configuration file editor. (read more)The <ADMIN> event content and description in the documentation and in the technological log configuration file editor were incorrect.The technological log configuration file editor is now up-to-date.
Database configuration update.
The Cannot reference table... error never occurs after clicking the Accept button in the Restructure data window. Previously this prevented database configuration update.

This error message appears before you have the option to click the Accept button. To eliminate the issue that causes the error message, run infobase verification and repair.

The Cannot reference table... error might occur after clicking the Accept button in the Restructure data window. This prevented database configuration update.Eliminated unexpected system behavior.
Dynamic lists.
When you press Enter (or double-click) in a row of a table linked to a dynamic list or when you call the ChangeRow() form table method, a form table extension will open a form linked to this row only if there is the Change command in the commands.

This change is not implemented in 8.3.10 compatibility mode.

When you pressed Enter (or double-clicked) in a row of a table linked to a dynamic list or when you called the ChangeRow() form table method, a form table extension opened a form linked to this row in any case.Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Internet-enabled functionality.
Web client.
System requirements.
The web client no longer supports Microsoft Internet Explorer versions 8 and 9.The web client supported Microsoft Internet Explorer versions 8 and 9.Legacy versions of Microsoft web browser are no longer supported. +
1C:Enterprise script.
Development tools.
In the thin and web clients, detection of attempts to assign a value to a nondeclared variable whose name matches a common module name is implemented. As a result, in this scenario the value is not assigned and an error message is generated.

This change is not implemented in 8.3.10 compatibility mode.

In the thin and web clients, attempts to assign a value to a nondeclared variable whose name matched a common module name were not detected. In the web client, this caused an unexpected shutdown of the client application.Eliminated unexpected system behavior.
Queries.
The Move() method of QuerySchemaQueryBatch, QuerySchemaOperators, QuerySchemaColumns, QuerySchemaIndexExpressions, QuerySchemaOrderExpressions, and QuerySchemaTotalCalculationFields objects shifts the specified collection element by the specified number of positions.

This change is not implemented in 8.3.10 compatibility mode.

The behavior of the Move() method was different from the standard one:
  • For QuerySchemaQueryBatch and QuerySchemaOperators objects, the method moved the element found by index specified in the first parameter to the position that was calculated as a maximum of the first and second parameters.
  • For QuerySchemaColumns, QuerySchemaIndexExpressions, QuerySchemaOrderExpressions, and QuerySchemaTotalCalculationFields objects, the method moved the element found by index specified in the first parameter to the position specified in the second method parameter.
The behavior of the Move() methods is unified with the behavior of Move() methods in other collections.
Managed forms.
Dynamic lists.
Access rights.
Upgrade: if the current user does not have enough rights to access form items related to commands of table or form extensions for dynamic lists, the items are hidden, regardless of the method used to add them (explicitly by application developers or automatically by the extensions).

Upgrade: the following commands are removed from the managed form table context menu: OutputList, ListSettings, LoadDynamicListSettings, SaveDynamicListSettings, DynamicListStandardSettings, List, HierarchicalList, and Tree. Upgrade: the submenu Generate is always added as the last menu item regardless of the hierarchy.

Upgrade: advanced search commands and list settings commands are added to tables that contain a dynamic list with the main table, filter criterion, or enumeration.

Upgrade: upon a form creation, if a table is removed, all commands related to the table are also removed. It happens, for example, when the user does not have the right to view the main table of the dynamic list related to the form table.

This change is not implemented in 8.3.10 compatibility mode.

If the current user did not have enough rights to access form items related to commands of table or form extensions for dynamic lists, the items were hidden only if they were added automatically by the extensions. If they were added explicitly by application developers, they were still visible (but unavailable to the user).

If the managed form table displayed a dynamic list without the main table, the following commands were added to the context menu: OutputList, ListSettings, LoadDynamicListSettings, SaveDynamicListSettings, and DynamicListStandardSettings. If the managed form table displayed a dynamic list with the main table that supported hierarchy, the following commands were added to the context menu: List, HierarchicalList, and Tree. The submenu Generate was added to different parts of the context menu depending on the displayed table.

Advanced search commands and list settings commands were not added to tables that contained a dynamic list with the main table, filter criterion, or enumeration.

Upon a form creation, if a table is removed, most of commands related to the table were also removed. However, one command (usually, Update) was never removed.

Eliminated unexpected system behavior.
Dynamic lists.
You can hide folder pictures in hierarchical dynamic lists. To hide the pictures, clear the RowPictureDataPath property of the table that displays the hierarchical dynamic list.

This change is not implemented in 8.3.10 compatibility mode.

Hiding folder pictures in hierarchical dynamic lists was not available. Clearing the RowPictureDataPath property of the table that displayed the hierarchical dynamic list did not hide the pictures.Eliminated unexpected system behavior.
Client application installation.
The timeout for downloading a client application distribution kit over HTTP is removed.

You can cancel downloading by clicking Cancel in the dialog box that displays the progress.

Downloading a client application distribution kit over HTTP was terminated if it took more than 600 seconds.Downloading a client application distribution kit using a slow connection channel is now possible.
Common objects.
In the TextReader object constructor, if LineSplitter parameter is omitted, this is treated as setting it to Chars.LF. If ConvertibleSplitterOfLines parameter is omitted, this is treated as setting it to Chars.LF + Chars.CR.

This change is not implemented in 8.3.10 compatibility mode.

In the TextReader object constructor, if LineSplitter or ConvertibleSplitterOfLines parameter was omitted, this was treated as setting it to a blank string.Eliminated unexpected system behavior. The values of omitted parameters now match the Syntax Assistant descriptions.
Infobase operations.
A composite index that includes attributes with Index property set to Index with additional ordering no longer depends on the attribute order. The order of the atttributes in the index is fixed.

The index is rebuilt during the first object restructuring after disabling compatibility mode. +This change is not implemented in 8.3.10 compatibility mode.

A composite index that included attributes with Index property set to Index with additional ordering depended on the attribute order. If the order was changed, the platform rebuilt the index.The effect of the attribute order on the database index structure is reduced.
Queries.
The attempt to execute a query that contains MIN() or MAX() aggregate function with the following parameter types generates an error:
  • UUID and system enumeration
  • UUID and any primitive type
  • System enumeration and any primitive type

This change is not implemented in 8.3.10 compatibility mode.

The attempt to execute a query that contained MIN() or MAX() aggregate function with the following parameter types did not generate an error:
  • UUID and system enumeration
  • UUID and any primitive type
  • System enumeration and any primitive type

Such a query might return an incorrect result or cause an unexpected shutdown.

Eliminated unexpected system behavior.
Queries.
A query that contains ISNULL() or CASE() operation that applies to result of MAX() or MIN() function (provided that parameters of these functions include values of UUID type or system enumerations, and provided that the other operand of ISNULL() or CASE() is a value of primitive type or another system enumeration) returns the correct result.

This change is not implemented in 8.3.10 compatibility mode.

A query that contained ISNULL() or CASE() operation that applied to result of MAX() or MIN() function (provided that parameters of these functions included values of UUID type or system enumerations, and provided that the other operand of ISNULL() or CASE() was a value of primitive type or another system enumeration) returned UNDEFINED.Eliminated unexpected system behavior.
Charts.
In charts that use the default palette, the default colors of chart scales and series are changed. New system enumeration value is implemented: ChartColorPalette.SoftAdaptive.

This change is not implemented in 8.3.10 compatibility mode.

In charts that used the default palette, the default colors of chart scales and series were different.Imoroved view of charts with default settings.
Managed forms.
In the standard processing of a ChoiceDataGetProcessing event handler of configuration object managers, correct handling of Undefined value of Parameters.SearchString parameter is implemented. If this value is set to Undefined, the system behavior is similar to quick choice, it returns the list of all database items for this configuration object.

This change is not implemented in 8.3.10 compatibility mode.

In the standard processing of a ChoiceDataGetProcessing event handler of configuration object managers, if Parameters.SearchString parameter was set to Undefined, it was treated as an empty search string.Eliminated unexpected system behavior.
Queries.
In the Parameters collection of the Query object, the parameter type used in a comparison operation (>, >=, <, <=, =, <>) applies to both operation parameters, however, their type qualifiers do not have to be identical. For example, if the first parameter is a string, you can specify a string of unlimited length as a second parameter.

This change is not implemented in 8.3.10 compatibility mode.

In the Parameters collection of the Query object, the parameter type used in a comparison operation (>, >=, <, <=, =, <>) and its type qualifier were applied to both operation parameters.Eliminated unexpected system behavior.
Data composition system.
When you add a condition with Empty comparison type to a query, the data composition system adds the condition to a nested query in the right part of a left join only if it cannot add the condition to the parent query. Otherwise, it never adds such conditions to nested queries.

This change is not implemented in 8.3.10 compatibility mode.

When a condition was added to a query, the data composition system always attempted to add the condition to a nested query. If the nested query was located in the right part of a left join, the condition was duplicated in the parent query.When a query includes a nested query located in the right part of a left join, the data composition system provides a more predictable result.
File operations.
The CreateDirectory() and BeginCreatingDirectory() methods generate exceptions if the directory name contains invalid characters.

This change is not implemented in 8.3.10 compatibility mode.

The CreateDirectory() and BeginCreatingDirectory() methods did not analyze the directory name. If the directory name contained invalid characters, the directory was not created and no error messages were generated.1C:Enterprise checks whether the names of directories to be created are valid.
Managed forms.
A managed form group with HorizontalAlignInGroup property set to Center is centered relative to the parent group.

This change is not implemented in 8.3.10 compatibility mode.

A managed form group with HorizontalAlignInGroup property set to Center was aligned left relative to the parent group.Eliminated unexpected system behavior.
Managed forms.
If ShapeRepresentation property of a managed form button is set to None and its BackColor property is set to any value except Auto, the button has transparent background.

This change is not implemented in 8.3.10 compatibility mode.

If ShapeRepresentation property of a managed form button was set to None and its BackColor property was set to any value except Auto, the button background color was taken from the BackColor property.Eliminated unexpected system behavior.
Web client, web service, and HTTP service publishing tools.
If an application is published to a web server using webinst utility with -descriptor option, the pubdst, pubdst32, and pubdst64 attributes of the root point element are copied from the publication template to the resulting default.vrd file.If an application was published to a web server using webinst utility with -descriptor option, the pubdst, pubdst32, and pubdst64 attributes of the root point element were not copied from the publication template to the resulting default.vrd file.Eliminated unexpected system behavior.
Documentation.
The description of SessionParameters.Clear() method in Syntax Assistant now states that calling this method requires the right to change all session parameters that are used in the method (possibly all parameters available in the session).The description of SessionParameters.Clear() method in Syntax Assistant was incorrect.The Syntax Assistant topic is now up-to-date.
Managed forms.
If a managed form attribute is created using 1C:Enterprise script, it can be accessed only with ThisObject. prefix.

This change is not implemented in 8.3.10 compatibility mode.

In some scenarios, managed form attributes created using 1C:Enterprise script could be accessed without ThisObject. prefix.Eliminated unexpected system behavior.
Administration tools.
New version of Java-based 1C:Enterprise Administrative Service API, which is compatible with 1C:Enterprise 8.3.11, is available (read more).The previous version of Java-based 1C:Enterprise Administrative Service API was compatible with 1C:Enterprise versions 8.3.10 and earlier.You can select Java-based 1C:Enterprise Administrative Service API version that is compatible with your 1C:Enterprise version.
System requirements.
The minimum system requirements for some operating systems of Windows family have changed:
  • Windows XP Service Pack 3
  • Windows Vista Service Pack 2
  • Windows 7 Service Pack 1
  • Windows Server 2008 Service Pack 2
  • Windows Server 2008R2 Service Pack 1

The system requirements for other Windows versions have not changed.

If an operating system does not match the requirements, 1C:Enterprise generates a warning with a recommendation to install the required update.

If you choose the installation option that does not have user interface and the operating system does not match the requirements, the cluster console and the COM connection module are not registered.

1C:Enterprise distribution package for Windows includes Visual C++ Redistributable for Visual Studio 2015.

1CEClientMakeSetup utility requires Visual C++ Redistributable to generate distribution packages for platform versions 8.3.11 and later.

The minimum system requirements for some operating systems of Windows family were:
  • Windows XP Service Pack 3 (the installer did not check whether the service pack was installed)
  • Windows Vista
  • Windows 7
  • Windows Server 2008
  • Windows Server 2008R2
The platform installer installs the required redistributables and displays warnings about unsupported operating systems.
Server clusters.
Administration tools.
You can use server cluster administration tools (both Java-based and administration server-based) for administering any 1C:Enterprise server cluster version, starting with 8.3.9. You can even use features that are not available in some administration server (ras) versions and server cluster versions.Server cluster administration tools (both Java-based and administration server-based) were compatible only with 1C:Enterprise server clusters that had the same version. In most cases, exact version matches were required.Simplified server cluster administration. Reduced cost of adapting the administrative infrastructure to new 1C:Enterprise server cluster versions.
Collaboration system.
 +

Creating a displayed context conversation with a specific list of participants from 1C:Enterprise script is not supported. In this scenario, the CollaborationSystemConversation.Write() method throws an exception.

Creating a displayed context conversation with a specific list of participants was allowed.Eliminated unexpected system behavior.
Internet-enabled functionality.
Security profile restrictions do not impact the following objects:
  • OpenSSLSecureConnection
  • OSCertificationAuthorityCertificates
  • WindowsCertificationAuthorityCertificates
  • LinuxCertificationAuthorityCertificates
  • WindowsClientCertificate
If a security profile was applied, the following objects were not available:
  • OpenSSLSecureConnection
  • OSCertificationAuthorityCertificates
  • WindowsCertificationAuthorityCertificates
  • LinuxCertificationAuthorityCertificates
  • WindowsClientCertificate
Eliminated unexpected system behavior.

Table of contents

Renamed objects

ObjectThe old nameThe new name
The name of CREATEINFOBASE command-line option parameter that specifies whether the infobase is added to the infobase list. The previous name is supported for compatibility purposes.
  • AddInList.
  • AddToList.
Name of the property of ChartPlotArea object. The previous name is supported for compatibility purposes.
  • ShowScale
  • ShowScales
Data composition system output parameter property ChartType.ChartBubbleSizing.

In 8.3.10 compatibility mode, the old name is used (in 1C:Enterprise language and when writing the parameter to an XML file).

  • ChartType.ChartBubbleSizing.
  • ChartType.BubbleSizing.

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Mobile device-specific features.
The following permissions are implemented for iOS mobile applications:
  • Background location. The mobile application gets location data even when it is inactive.
  • Background audio playback. The mobile application plays audio even when it is inactive.
  • File exchange with PC. Use this permission for mobile applications that exchange files through iTunes.
These features were not provided.Expanded settings for iOS mobile applications.
Managed forms.
In the mobile platform, the object that visualizes planner data (the planner) is now available.

For the object usage specifics, see the documentation.

The planner was only available on the platform for personal computer.Expanded data presentation options on mobile devices.
Mobile device-specific features.
Support of local and push notifications is added to the mobile platform for Windows. 1C:Enterprise uses Windows Notification Services for this purpose. The notification sending service provided by 1C Company does not support Windows Notification Services.

The system enumeration value DeliverableNotificationSubscriberType.WNS is implemented.The DeliverableNotificationSendManager.GetAccessToken() method is implemented.

Notification sending errors are returned in the return value of DeliverableNotificationSendManager.Send() method.This change is not implemented in 8.3.10 compatibility mode.

The system enumeration DeliverableNotificationSendErrorType is implemented. The DeliverableNotificationSendIssueInformation object is implemented.

For DeliverableNotificationSendManager.Send() method, the DeliverableNotificationSendIssuesInformation parameter is implemented.

The option to get a local notification when a device is crossing a geofence border is implemented.

Support of local and push notifications was only available for iOS and Android devices.

Notification sending errors generated exceptions.

Standard user notifications are now available on mobile Windows devices. Both mobile applications and desktop applications can generate notifications (local and push notifications, respectively).
System requirements.
Support for Android versions earlier than 4.0 is ended. The earliest supported API version is API 14 (Androuid 4.0).Android versions with API 9 (Android 2.3) or later were supported.Ended support for legacy Android versions.
Print tools.
Spreadsheet documents.
In the mobile platform, support of batch printing is implemented.This feature was not provided.Batch printing is now available in the mobile platform.
File operations.
On the mobile platform, the file selection dialog box now supports multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method are now case-insensitive. The file selection dialog box and FindFiles() method now support iOS and Android wildcards.The file selection dialog box did not support multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method were case-sensitive. The file selection dialog box and FindFiles() method did not support iOS and Android wildcards.Expanded file operation tools in the mobile platform. These tools are unified with file operation tools available in the desktop platform.
Formatted documents.
The mobile platform now supports FormattedDocument object (and can display formatted documents in managed forms).This feature was not provided.Expanded support of formatted text in mobile applications.
Mobile device-specific features.
On the mobile platform for Windows (except Windows 8.1), support of map operations is implemented. The following methods are now available: ShowOnMap(), GetAddressByLocation(), and GetLocationByAddress().

Global context method MapRepresentationSupported() is implemented.

Map operations were not supported on Windows mobile devices.Extended mobile platform capabilities on Windows. Determining whether map operations are available is standardized with other operations that might be unavailable on some devices or operating systems.
Mobile applications.
When a configuration that was saved using an earlier 1C:Enterprise version for personal computer is loaded to a mobile application, the mobile device displays a warning and provides the option to cancel the operation.When a configuration was loaded on a mobile device, 1C:Enterprise did not check whether the configuration was saved using an earlier 1C:Enterprise version for personal computer.Implemented diagnostics of potential compatibility issues between the mobile platform and the configuration to be loaded (in scenarios where the configuration was saved using an earlier 1C:Enterprise version for personal computer).
Mobile device-specific features.
On Android devices, the following operations with SMS messages are implemented:
  • Get SMS log and check whether getting the log is allowed. For TelephonyTools object, methods SMSLogSupported() and GetSMSLog() are implemented.The SMSLog object is implemented.
  • Filter SMS messages.
  • Create a message based on another message. The wizard that creates an SMS message based on an SMS log entry is implemented.

On Android devices, in method SMSLog.FindRecords(), ungrouped filter items are combined using AND operator.

On Android devices, access to SMS message log was not provided.

On Android devices, in method SMSLog.FindRecords(), ungrouped filter items were combined using OR operator. +

Introduced advanced SMS management tools on Android devices.

The behavior of the filter used in a search in the SMS message log is unified with other filters.

Database configuration update.
In built mobile applications, the message stating that unused data will be deleted is no longer displayed after configuration updates.

The mobile platform for developers displays a message stating that the update changes metadata structure (only when it actually changes it).

The developers are now responsible for preventing data losses caused by configuration updates.

If a configuration update changed metadata structure, a message stating that unused data will be deleted was displayed after the update.

The message was displayed both in built mobile applications and in the mobile platform for developers.

Configuration updates are now less distressing to end users. In patricular, end users do not get a message that their data will be lost (which was not always true). At the same time, developers must be more cautious when implementing configuration changes that might cause losses or user data.
Mobile device-specific features.
Universal date type values are now used in the following properties: CallLogRecord.Date, CalendarEventData.Start, and CalendarEventData.End.

This change is not implemented in version 8.3.10 compatibility mode.

Local date type values were used in the following properties: CallLogRecord.Date, CalendarEventData.Start, and CalendarEventData.End.Date presentation now meets the general requirements of 1C:Enterprise platform.
Mobile device-specific features.
The split screen implemented in Android 7 is no longer supported in the mobile platform.The split screen implemented in Android 7 was supported incorrectly.Eliminated unexpected system behavior.
Mobile device-specific features.
The mobile application now contains a set of predefined messages that describe mobile application demands on different permissions. They are displayed when a specific permission is required.

Developers cannot modify these messages.

If a specific permission was required for a mobile application, a user prompt contained only the name of the permission and response variants.There was no reason of permission demand stated in the prompt.The mobile application permission prompts now meet the requirements of application stores and provide more information about the required permission.

Table of contents

Library updates + +

Table of contents

Transition from the previous version to the version 8.3.11

Table of contents

Version 8.3.10

Version 8.3.10 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
For configuration property Compatibility mode, new value Version 8.3.9 is now implemented.Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.8 was implemented.Configurations developed in version 8.3.9 or earlier now run in version 8.3.10 without requiring any changes to configuration or to data structures. This allows for transition to version 8.3.10 in two stages: first, version update is applied (without any changes to configuration); then, any needed changes are applied and compatibility mode is disabled. This also allows using version 8.3.9 for infobase operations, if necessary, after transition to version 8.3.10. Compatibility mode must be enabled to use version 8.3.9. If you disabled it, enable it again.
Web client, web service, and HTTP service publishing tools.
In the "publish to web server" dialog box, parameters related to OpenID authentication are now on a separate tab. +In the "publish to web server" dialog box, also implemented entering a list of URLs that can be used for user redirection after OpenID authentication.The only method of specifying a list of URLs that can be used for user redirection after OpenID authentication was to edit default.vrd file manually.When publishing to web servers, you can interactlvely specify all of the parameters defined in default.vrd file.
Client application installation.
Rules for detecting computers with Ukrainian language pack are improved. When a 1C:Enterprise client application is being installed on Windows, the installer language and the default platform language are set to Ukrainian if at least two of the following conditions are met:
  • The home location specified in the operating system settings is Ukraine.
  • Ukrainian keyboard layout is installed.
  • Ukrainian hryvnia (UAH) is selected as the currency unit.
  • Ukrainian locale is selected in the operating system settings.
  • Ukrainian is set as the default operating system language.
When a 1C:Enterprise client application was being installed on Windows, the default platform language was set to Ukrainian only if the primary operating system language was Ukrainian. The only way to run the installer in Urkainian was using the /luk command-line option.Improved 1C:Enterprise installer usability for Ukrainian speakers.
1C:Enterprise script.
Administration tools.
Implemented functionality for collecting information on circular references during 1C:Enterprise script execution. Using this feature may result in reduced application performance. It is recommended that you use this feature for testing purposes only. +Implemented global context method CheckScriptCircularRefs(). For technological log settings file (logcfg.xml), implemented item <SCRIPTCIRCREFS>. Implemented technological log event <SCRIPTCIRCREFS>. +Implemented command-line option for the thin client and thick client startup: /EnableCheckScriptCircularRefs. Implemented command-line parameter for 1C:Enterprise server startup: -EnableCheckScriptCircularRefs. +In the dialog box used to specify client application startup parameters from Designer, implemented parameter Detect 1C:Enterprise script circular references. +Implemented parameter EnableCheckScriptCircularRefs in file conf.cfg. +If 1C:Enterprise is started with option/parameter EnableCheckScriptCircularRefs, discovery of any circular reference will result in unrecoverable error containing information on the discovered circular reference.This feature was not provided.Diagnostics of circular reference usage in 1C:Enterprise script is now more intuitive.
Configuration extensions.
In module editor, implemented functionality for adding a specific method to extension (when working with a configuration being extended). +In module editor, implemented navigation from annotation of extending method to method being extended (when working with an extension). +Implemented keyboard shortcut Alt+Shift+F2 for command Add to extension. Keyboard shortcut Alt+F2 for this command is now disabled.User-friendly functionality for adding methods to extensions was not available. +Navigation from annotation of extending method to method being extended was not available. +Keyboard shortcut Alt+F2 was used for command Add to extension.Creating 1C:Enterprise script-based module extensions is now more ergonomic.
Dynamic lists.
Implemented additional processing for data received by a dynamic list before the data is displayed. Implemented event OnGetDataAtServer. +In version 8.3.7 compatibility mode, behavior remained unchanged.This feature was not provided.It is now easier to use dynamic lists to output linked data that was previously extremely difficult or impossible to obtain through dynamic list query.
Managed forms.
Implemented arbitrary scaling of managed forms in Taxi interface. If compact display mode is set at application level, interactive scaling is disabled. Form size settings are saved per DPI value and per form scale value. Implemented managed form property Scale, command Change scale in client application menu View, and system command bar button used to open the scale change dialog box. This change is not implemented in 8.3.6 compatibility mode. +Implemented support for picture variant sets in client applications for PC (thick client, thin client, and web client). +Added variants of system pictures used for client applications. +Implemented new resolutions for picture variants: bldpi (85% scale), aldpi (125% scale), amdpi (175% scale), and udpi (400% scale). In picture variant set manifest, implemented choice of target interface for each variant. To define size of picture variants more precisely, implemented parameters for height and width of each variant in picture variant set manifest. +For system enumeration PictureSize, implemented values RealSizeIgnoreScale and AutoSizeIgnoreScale.This feature was not provided. Compact viewing mode was available at form level and at application level (through 1C:Enterprise script). +Picture variant sets were supported in mobile application only.Interface customization is now more user-friendly.
1C:Enterprise script.
Implemented generation of text strings whose content depends on a number specified in a string. Examples: 1st week of the month, 2nd week of the month. Implemented the StringWithNumber() function. +The following langauges are supported: Azerbaijanian, Belarusian, Chinese, Bulgarian, English, Estonian, Finnish, French, Georgian, German, Hungarian, Kazakh, Kyrgyz, Latvian, Lithuanian, Polish, Romanian, Russian, Turkish, Turkmenian, Ukrainian, and Vietnamese,This feature was not provided.Generation of text strings whose content depends on a number specified in a string is now streamlined.
Spreadsheet documents.
Implemented getting data area size value during import from third-party spreadsheet formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument). +For object SpreadsheetDocument, implemented methods GetDataAreaHorizontalSize() and GetDataAreaVerticalSize().This feature was not provided.It is now easier to import documents in third-party spreadsheet formats without clearly defined boundaries of imported data area.
Development tools.
OData interface.
Implemented server debug item Standard OData interface intended for debugging 1C:Enterprise script running during queries to standard OData interface. +Changed debug item sorting rules that apply to debug item lists (for HTTP debug protocol). Changed auto attachment dialog box (for TCP debug protocol). Debugging of 1C:Enterprise script running at the server side during infobase calls through standard OData interface was not supported. Debug item sorting rules that apply to debug item lists (for HTTP debug protocol) were different. Auto attachment dialog box for TCP debug protocol displayed debug items in a different order. It is now easier to debug 1C:Enterprise scripts using standard OData interface.
Managed forms.
The option to manage height for managed form tables that display data other than dynamic lists is implemented. This includes the option to have table height resized automatically based on the amount of data displayed. The HeightControlVariant managed form table property is implemented.

This change is not implemented in 8.3.9 compatibility mode.

This option was not provided on the desktop platform. It was only available on the mobile platform. The HeightControlVariant managed form table property was ignored on the desktop platform.The option to add a form table that does not display dynamic list data and still is automatically resized based on the number of rows is implemented. This reduces the number of scroll bars and saves form space.
Software licensing.
Technological log.
For technological log, implemented registration of events associated with:
  • Granting and releasing licenses (both software and HASP)
  • Granting licenses to base versions
  • Regular checks for discrepancies between the actual hardware and the list of hardware components stated in a license

Implemented technological log event <LIC>.

The <HASP> technological log event allows to analyze technological aspects of HASP management only (HASP interface calls); it does not allow to monitor granted or released licenses with HASP keys.

This feature was not provided. Only the option to check HASP key operations using the <HASP> event was provided.Easier investigation of license-related issues.
Data composition system.
Values of type DataComposionSchemaNestedDataSet can now be added to collection DataComposionSchemaDataSetFields. Implemented values of type DataComposionSchemaDataSetFields to be used in methods Add() and Insert() of object DataComposionSchemaDataSetFields.Values of type DataComposionSchemaNestedDataSet could not be added to collection DataComposionSchemaDataSetFields.Now it is possible to create a data composition schema with nested data sets using 1C:Enterprise script.
Managed forms.
Implemented control of planner interval background color in accordance with values of measurements associated with this interval. +Implemented property PlannerBackgroundInterval.DimensionValues.Planner interval background color management based on the values of dimensions associated with this interval was not available. Planner interval background color could only be changed for date intervals.Visual customization of planner is enriched.
Development tools.
Implemented option for running Designer in agent mode. This is a variation of batch mode where Designer operates as an SSH or SFTP server and accepts commands sent through these protocols. +While in agent mode, Designer can only work with a single infobase at a time. If access to multiple infobases is required, it is recommended that you run several instances of Designer in agent mode. +Implemented command-line options for batch mode: /AgentMode, /AgentPort, /AgentListenAddress, /AgentSSHHostKey, /AgentSSHHostKeyAuto, and /AgentBaseDir. +Changed behavior of command-line options /Visible and /LoadConfigFromFiles when used in agent mode. +If you need a client application to connect to SSH or SFTP servers, you can now use any application with SSH/SFTP functionality that supports text command exchange with SSH and SFTP servers (examples: putty, winscp, MobaXTerm). +This functionality is currently available in beta status.This feature was not provided.Designer connectivity automation capabilities are now expanded. Response time of Designer is improved because a separate instance of Designer is no longer started on each call.
Formatted documents.
Implemented saving formatted documents in PDF format (both in interactive mode and by using method FormattedDocument.Write()) . +Implemented value FormattedDocumentFileType.PDF.This feature was not provided. Formatted documents could be only saved in HTML format or as plain text without formatting.Formatted document management capabilities are now expanded.
Spreadsheet documents.
Implemented 1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents. +For object SpreadsheetDocument, implemented properties ShowRowAndColumnNames and ShowCellNames. +In spreadsheet document editor menu (in 1C:Enterprise mode), implemented commands for defining view of named areas and for assigning area names. 1C:Enterprise script-based management of how row, column, and cell names are displayed in spreadsheet documents was unavailable.It is now easier to organize editing of spreadsheet documents containing named areas.
Technological log.
Implemented logging of events that occur upon initial connection of 1C:Enterprise server to Microsoft SQL Server database. The events are saved in the technological log. The logging is based on event <DBMSSQLCONN>.This feature was not provided.It is now easier to investigate incidents associated with loss of connection between 1C:Enterprise server and Microsoft SQL Server database.
Configuration extensions.
The help available in a configuration being extended includes reference information on extension objects. +The reference information on the extension is included in the help search results.This feature was not provided. Reference information implemented in a configuration extension was missing from the help tree and could not be accessed through searching.Eliminated unexpected system behavior. Reference information from an extension is included in the help available in the configuration being extended, making it easier to use the resulting configuration.
Spreadsheet documents.
When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that match sheets of the original document are marked up as named row ranges. Names of sheets of the original document are converted into range names so as to satisfy rules of 1C:Enterprise script ID generation.

When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided are imported normally and areas defining these sheets are given automatically generated names. This change is not implemented in 8.3.9 compatibility mode. +

When importing spreadsheet documents from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files, areas of the resulting document that matched sheets of the original document were not marked up.

When importing spreadsheet documents from Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) files, sheets with no names provided were not imported.

+

+

It is now easier to process spreadsheet documents created by importing multipage XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 and earlier), or ODS (OpenDocument) files. It is now easier to recognize pages of the imported documents.
Configuration extensions.
For configuration extensions, implemented configuration extension purposes: Patch, Customization, and AddOn.

Extensions are applied in the following order:

  • All extensions with purpose Patch
  • All extensions with purpose Customization
  • All extensions with purpose AddOn

Multiple extensions with the same purpose are applied in no specific order. +Purpose of extensions that are already loaded to the infobase is automatically set to Customization. +Implemented property ConfigurationExtension.Purpose.

This feature was not provided. +All extensions were applied with the same priority.

+

It is now possible to sort extensions by function. It is now easier to understand the purpose of any extension.
Configuration extensions.
Spreadsheet documents.
Implemented extensions for spreadsheet documents. +Implemented merging of spreadsheet documents during configuration update that uses a file in .cf or .cfu format.The spreadsheet document extension feature was not provided.

The feature allowing spreadsheet document merging during configuration update was not provided.

Configuration extension offers more features now. +Additional spreadsheet document management features are now provided for supported configurations.
Pictures.
Implemented getting a specific picture from a picture variant collection based on DPI, display scale factor, and template picture flag. +For methods Convert(), Write(), GetBinaryData(), and FileNameFilter() of Picture object , implemented parameters AllVariants and SelectVariant.Platform behavior upon attempt to get a specific picture from a picture variant collection was not defined. This activity could result in system failure.Eliminated unexpected system behavior. +Getting a specific picture (best matching the current display mode) from a picture variant collection is now supported.
Charts.
Now fractional values can be used to define boundaries of gauge chart bands. +This change is not implemented in 8.3.9 compatibility mode.Fractional values could not be used to define boundaries of gauge chart bands.An additional chart appearance control feature is now implemented.
Charts.
Data composition system.
Implemented the following chart display options (also available in data composition system):
  • Displaying trendlines
  • Customizing appearance of series in charts
  • Customizing appearance of series in chart legends

Implemented system enumerations ChartTrendlineApproximationType, ChartTrendlineFactor, StockChartUsedPointValue, ShowInChart, and ShowInChartLegend. For system enumeration ChartLabelLocation, implemented values: Auto, TopLeft, BottomLeft, TopRight, BottomRight, TopAndLeftSpecified, and EmptySpace. For system enumeration ChartMarkerType, implemented values Alternation and Auto. +Implemented objects ChartLabelArea and ChartTrendline.

For object ChartSeries, implemented properties Trendlines, ShowGraphicalDataRepresentationInChart, and +ShowGraphicalDataRepresentationInChartLegend. +For property ChartSeries.Marker, the default value is set to Auto. This change is not implemented in 8.3.9 compatibility mode. +For objects DataCompositionAreaTemplateChartGroupAppearance and DataCompositionAppearance, implemented parameters ChartTrendline, +ShowGraphicalDataRepresentationInChart, and +ShowGraphicalDataRepresentationInChartLegend.

These features were not provided. +Value of property ChartSeries.Marker was set to Rect, Circle, or Rhomb, based on series number.Additional chart features, related to appearance control and analytics, are now implemented.
Charts.
Data composition system.
Implemented new chart types: scatter chart and bubble chart. For Chart object, implemented properties BubbleSizeCommonSeries, BubbleSizeValueSource, DefaultBubbleSize, MinBubbleSize, MaxBubbleSize, ChartBubbleSizing, and BubbleChartNegativeValuesShowMode.

Implemented the following chart management features:

  • Selecting data source for point axis. For Chart object , implemented properties PointsAxisValuesSource and PointsAxisSeries.
  • Managing chart axis display options. For Chart object, implemented properties ValuesAxis and PointsAxis.
  • Specifying fractional values for minimum and maximum chart values. Specifyimng the method used to determine minimum and maximum chart values. This change is not implemented in 8.3.9 compatibility mode.
  • Managing line connections between chart dots (where possible). Implemented property Chart.PointsConnection.
  • Use automated calculation of chart transparency. For system enumeration ChartSemitransparencyMode, implemented value AutoCalculate.

Expanded set of values that can be used in chart labels. For ChartLabelType system enumeration, implemented values ValueSize, SeriesSize, SeriesValueSize, SeriesPointSize, SeriesPointValueSize, PointSize, and PointValueSize.

For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.ValuesAxis, ChartType.PointsAxis, ChartType.PointsAxisValuesSource, ChartType.PointsAxisSeries, ChartType.BubbleSizeValueSource, ChartType.BubbleSizeCommonSeries, ChartType.DefaultBubbleSize, ChartType.MinBubbleSize, ChartType.MaxBubbleSize, ChartType.ChartBubbleSizing, ChartType.BubbleChartNegativeValuesShowMode, and ChartType.PointsConnection. For data composition system object DataCompositionAreaTemplateChartGroupAppearance, implemented properties PutOnPointsAxis and UseAsCommonBubbleSizeSeries. +Properties AutoMaxValue and AutoMinValue are now deprecated and supported for compatibility purposes only.

These features were not provided. +Scatter charts and bubble charts were not implemented. +Fractional values could not be used for properties MinValue and MaxValue of Chart object. Properties AutoMinValue and AutoMaxValue were used for calculating minimum and maximum chart values. Additional chart features are now implemented.
Charts.
Data composition system.
Implemented custom labels for chart scales. For ChartPlotArea object, implemented properties PointsScale, ValuesScale, and SeriesScale. +For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.PointsScale, ChartType.ValuesScale, and ChartType.SeriesScale.These features were not provided.Additional chart appearance control features are now implemented.
Charts.
Data composition system.
Implemented custom point display order for bar charts. For Charts object, implemented property BarChartPointsOrder. This change is not implemented in 8.3.9 compatibility mode.

For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameter ChartType.BarChartPointsOrder.

These features were not provided. +Points in bar charts were always displayed in bottom-to-top order (the first point at the bottom of the chart).Additional chart appearance control features are now implemented.
Data composition system.
Charts.
Implemented customization of scale lines, scale color, series markers, series indicators, and series line types when displaying charts. +For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ChartType.ScaleLines and ChartType.ScaleColor. +For data composition system objects DataCompositionAreaTemplateChartGroupAppearance and DataCompositionAppearance, implemented properties LineInChart, MarkerInChart, and IndicatorInChart.These features were not provided.Additional features of chart appearance control through data composition system are now implemented.
Collaboration system.
Implemented the "collaboration system" feature that supports interaction between the server, client applications, and users of a single infobase. The collaboration system simplifies automation of enterprise business processes and provides an easy way to establish work-related communication. 1C:Enterprise application uses can exchange text messages and call each other (audio calls with optional video feed). Text conversations can be related to specific infobase objects (context conversations) or not related to any object (noncontext conversations). Access to conversations is allowed or denied based on the object access rights.

Implemented Collaboration system management standard function.

Implemented notifications about new messages.

Implemented conversation management using 1C:Enterprise script tools. Implemented CollaborationSystem global context property. For ManagedForm object, implemented ConversationsRepresentation property. This property is not available in 8.3.9 compatibility mode. Implemented CollaborationSystemInfoBaseRegistration access right.

The web client supports the collaboration system if it runs in one of the following browsers: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge, or Microsoft Internet Eхplorer version 10.0 or later.

All of the messages are stored on the collaboration system server. To start using the collaboration system, you have to register your infobase on the collaboration system server. Initially the server is available as the 1cDialog.com service hosted by 1C Company. Note that in order to use the collaboration system you have to open Internet access to wss://1cdialog.com.

A distribution kit for a local collaboration system server will be available in a future release.

Therefore, you will have a choice between using 1cDialog.com service and running a local server.

Using calls is limited during the beta testing period. Call usage instructions will be available separately.

This feature currently has beta status. The service access terms will be available separately. The email message with the registration code sent from 1cDialog.com when you request registration in the service will include instructions for enabling video calls.

This feature was not provided.The new feature provides 1C:Enterprise application users with communication options that are tightly integrated into the application interface and business logic.
Dumping configurations to files/Restoring configurations from files.
Implemented partial dump of the configuration being edited to XML files. During partial dump, only objects that were modified since the previous dump are dumped. The file ConfigDumpInfo.xml containing information about all dumped configuration objects is created. This file also contains internal versions of all dumped objects. An object is not dumped during a partial dump if its version numbers in Designer and in file ConfigDumpInfo.xml are identical. +Moreover, a file containing information about the differences between the current and the previous dump can be generated. +When restoring data from XML files, users can specify that the file containing information about dumped configuration objects must be updated. In this case, information matching the configuration state after it is restored is saved to this file. +For Designer batch mode command-line option /DumpConfigToFiles, implemented parameters update, force, getChanges, configDumpInfoForChanges, and listFile. +For Designer batch mode command-line option /LoadConfigFromFiles, implemented parameter updateConfigDumpInfo.Partial dump of configurations to XML files was not supported. Only full configuration dump was implemented.Dumping configurations to XML files is now faster. especially dumping very large configurations with minor changes.
Dynamic lists.
Implemented management of availability of dynamic list fields (including subordinate fields) for use in groupings, filters, and order settings. Implemented methods SetRestrictionsForUseInGroup(), SetRestrictionsForUseInOrder(), SetRestrictionsForUseInFilter(), GetRestrictionsForUseInGroup(), GetRestrictionsForUseInOrder(), and GetRestrictionsForUseInFilter().These features were not provided.Now developers can explicitly prohibit groupings, ordering, and filtering for fields not intended for these operations.
Window-based interface.
Dumping configurations to files/Restoring configurations from files.
Implemented visibility management for managed form title. Implemented property ManagedForm.ShowTitle. +Implemented visibility management for form closing button. Implemented property ManagedForm.ShowCloseButton. +Implemented selection of main application window display mode.
  • Normal. Default display mode for main application window.
  • Workstation. Many items on the system commands area are hidden; all panes in the main application window are hidden; navigation buttons on the home page (including the home page label) are hidden; some of the keyboard shortcuts are disabled.
  • Full-screen workstation. Same as Workstation mode but the application window is displayed in full-screen mode.
  • Kiosk. Same as Full-screen workstation mode but the About button and the hyperlink with user name located in the system commands area are hidden.

Implemented global context property ClientApplication that provides access to client application settings (such as getting and changing the client application window title). For metadata object that describes the configuration, implemented property MainClientApplicationWindowMode.

Changed version number of format used for dumping configurations to files.

The following global context methods are now deprecated. It is recommended that you do not use any of these: SetShortApplicationCaption(), GetShortApplicationCaption(), SetClientApplicationCaption(), GetClientApplicationCaption(), ClientApplicationBaseFontCurrentVariant(), and ClientApplicationInterfaceCurrentVariant(). +The above features are available in Taxi interface.

These features were not provided.Expanded capabilities of client application appearance management. Now a specific interface can be enabled (cashier's interface, self-service kiosk, and more).
Configuration extensions.
Common attributes / Data separation.
Implemented a flag specifying whether a common attribute used as a separator can separate configuration extensions. For CommonAttribute configuration object, implemented property ConfigurationExtensionsSeparation. +It is recommended that you disable extension separation for separators in Independent and shared mode.Any configuration separators could be used to separate configuration extensions. Disabling extension separation was not possible if data separation was enabled at infobase level.Now developers have control over separation of configuration extensions to be used in the infobase. For example, a configuration developer can specify that none of the separators available in the application can be used to separate configuration extensions.
Client application.
For the thin and thick client applications that directly connect to a 1C:Enterprise server, the disconnection monitoring mechanism is implemented. If a server connection issue is detected, the client application automatically attempts to reestablish the connection and repeat the server call. If the connection cannot be established, the application is shut down.

The following timeouts are applied:

  • Thin client: ping every 3 seconds, wait for connection for 15 seconds.
  • Thick client: ping every 12 seconds, wait for connection for 60 seconds.

The timeout values cannot be changed.

If any server connection issues occurred in the thin or thick client application that was directly connected to a 1C:Enterprise server, the client application might stop responding for a long period (several minutes). That period was defined by TCP stack settings in the operating system.Improved reliability of client applications that directly connect to a 1C:Enterprise server. Reduced chance of situations when an application stops responding.
DBMS operations.
System requirements.
Support of PostgreSQL version 9.6 is implemented.This PostgreSQL version was not supported.Extended list of supported PostgreSQL versions.
DBMS operations.
System requirements.
Support of Postgres Pro Enterprise version 9.6 is implemented (only in managed lock management mode).Postgres Pro Enterprise was not supported.Extended list of supported DBMS versions.
System requirements.
Web client.
Ended support of Mozilla Firefox versions 51 and earlier.Mozilla Firefox versions 51 and earlier were supported.Ended support for legacy Mozilla Firefox versions.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Web client.
Spreadsheet documents.
Implemented automated marking of blank fields when entering data into spreadsheet documents in the web client.Automated marking of blank fields was not performed when entering data into spreadsheet documents in the web client.Eliminated unexpected system behavior.
Managed forms.
Implemented changes to calculation of page tab size and the appearance of page tabs in vertical mode. +

Implemented scaling of pictures in page tabs when changing DPI (both for thin client and thick client). This change is not implemented in 8.3.9 compatibility mode.

Implemented slight size and position changes for several types of managed form items.

Changed appearance of slider (both in Taxi interface and in the web client with Version 8.2 interface). The slider appearance in the web client differs from its appearance in the thick and thin clients.

The size of the colored picture used for input fields that display data of Color type differs between the web client and the thick/thin clients.

Changed appearance of system forms (in Taxi interface for both thick and thin clients) for better conformity with general visual interface style.

Increased hit boxes for icons that collapse and expand tree nodes in tables (in Taxi interface).

Improved appearance of controls for non-standard DPI values. +Modified size calculation for slider fields in forms.

The interface appearance was different. Pictures in page tabs were not resized when changing DPI (both for thin client and thick client).Improved appearance of client applications.
Managed forms.
Changed appearance of form navigation panel in Taxi interface. In Russian localization, the name of panel item Main is now slightly changed. +All commands are displayed in the form navigation panel. Full names are displayed for all of the panel commands. If a command does not fit the form actions panel, the command is displayed in the More menu.Appearance of form navigation panel was different. In Russian localization, the name of panel item Main was slightly different. +The following rule was in force when displaying commands: if the Important group contained more than two commands, only two commands were displayed on the navigation panel. Commands that did not fit the form navigation panel were available through the More menu. +Long names were shortened and marked with ellipses (...) both in the thick and thin clients.Application UI was improved.
Interface.
The opened items panel was redesigned in Taxi interface:
  • The width of each panel item now depends on the window title.
  • If the panel is horizontal, one line is used to display the title; if the panel is vertical, an unlimited number of lines can be used.
  • If the panel is horizontal, the control item used to access the full list of open windows is located in the right section of the panel.
  • If the panel is vertical, a scroll bar might be displayed. In this case, the panel and the work area of the main window can be scrolled separately.
  • Implemented closing windows by clicking the wheel button on a corresponding item on the opened items panel.
  • Implemented multiple window closing methods in the context menu of a panel item.
  • Implemented dragging windows within the panel to change their order.
  • If the opened items panel is displayed, the home page button is hidden from the work area of the main window.
Appearance and functionality of the opened items panel (in Taxi interface) were different:
  • The width of each panel item was fixed regardless of the item content.
  • If the panel was horizontal, one or two lines were used to display the item title.
  • Windows could not be closed by clicking the wheel button on a corresponding item on the opened items panel.
  • The window order on the opened items panel could not be changed interactively.
  • The home page button was always displayed in the work area of the main window.
It is now easier to use the opened items panel in Taxi interface.
Spreadsheet documents.
Web client.
All border types are now displayed in spreadsheet documents opened in the web client. Appearance of border lines of spreadsheet documents opened in the web client depends on the browser and may differ from appearance of border lines of spreadsheet documents opened in the thick or thin client.Only border lines of these types were displayed for spreadsheet document cells: Solid, Dotted, and None. All other line types were replaced by the above types as follows:
  • Line type Double was replaced by Solid.
  • Line types ThinDashed, ThickDashed, and LargeDashed were replaced by type Dotted.
Eliminated unexpected system behavior. Border lines of spreadsheet documents opened in the web client now more closely conform to border lines of spreadsheet documents opened in the thick or thin client.
Managed forms.
If the freeze area of a managed form table exceeds the visible area of the table, column freeze is canceled automatically.

This change is not implemented in 8.3.9 compatibility mode.

If the freeze area exceeded the size of the whole table, the table could not be scrolled horizontally.It is now easier to work with tables in small forms.
Data composition system.
In the "Main" data composition appearance template used in Taxi interface, text color is set to Auto for all template areas except the report header.

This change is not implemented in 8.3.9 compatibility mode +

In the "Main" data composition appearance template used in Taxi interface, gray text color was used for some of the template areas (except the report header).Now optimal text color is chosen whenever a report is displayed or printed, improving readability.
Dynamic lists.
Implemented sorting for dynamic lists by clicking any column header in the table displaying dynamic list data, provided that the query text contains aggregate functions and GROUP BY expressions.

This change is not implemented in 8.3.7 compatibility mode.

Dynamic list sorting by clicking any column header in the table displaying dynamic list data was not supported, regardless of whether the query text contained aggregate functions or GROUP BY expressions.Behavior of tables displaying dynamic list data is now more intuitive and predictable.
Managed forms.
In the thin and thick clients, the wheel button scrolls a form item where mouse cursor is currently located (provided that such form item is scrollable). The form item is scrolled regardless of whether it has received input focus. +After the form item is fully scrolled, the parent form item starts scrolling (provided that it is scrollable).In the thin and thick clients, the wheel button only scrolled active form items. +In the web client, the wheel button scrolled both active and nonactive form items.Managed form navigation is now more user-friendly. +Unified scrolling behavior between the web client, the thin client, and the thick client.
Client application.
Data display.
All standard pictures used by client applications are implemented as sets of pictures optimized for a variety of DPI and display scale values. +Standard pictures are redesigned.Standard pictures used by client applications were not optimized for current DPI and display scale values. Therefore, applying non-standard DPI could result in blurry standard pictures. Optimized appearance of client interface for non-standard DPI and display scale values.
Client application installation.
If any issue occurs during the thin client update over HTTP, you have the option to get the name of the file that cannot be updated. This option is provided in the following scenarios:
  • The archive is corrupted or has invalid structure (the archive file name is provided).
  • One of the distribution kit files has invalid digital signature (the name of this file is provided).
If any issue occurred during the thin client update over HTTP, the option to get the name of the file that cannot be updated was not available. In particular, there was no way to get the file name of a corrupted archive of the name of the file that had invalid digital signature.

+

Improved issue diagnostics during the thin client update over HTTP.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Server clusters.
 Improved server cluster scalability for the following cases:
  • Servers run on processors with a large number of cores.
  • A large number of users is served.
  • Internal data exchange between the client and the server is compressed.

Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries.

Poor server cluster scalability was observed in the following cases:
  • Servers run on processors with a large number of cores.
  • A large number of users is served.
  • Internal data exchange between the client and the server is compressed.

1C:Enterprise server used a significant amount of RAM to run applications that utilized batch queries.

Improved 1C:Enterprise server cluster scalability.
Встроенный язык.
Faster 1C:Enterprise script execution by 1C:Enterprise server.The performance of 1C:Enterprise script execution by 1C:Enterprise server was insufficient.Optimized 1C:Enterprise script execution by 1C:Enterprise server.
Data composition system.
Faster initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields.The performance of initialization of data composition settings composer by source of available data composition settings when using schemas with a large number of calculated fields was insufficient.Improved performance of data composition system initialization in several scenarios.
Server clusters.
Reduced amount of RAM used by 1C:Enterprise server to run applications that utilize batch queries.Significant amount of RAM was used by 1C:Enterprise server to run applications that utilize batch queries.Optimized amount of RAM used by 1C:Enterprise server to run batch queries.
Configuration repositories.
Optimized updating of local cache of configuration storage when putting objects into storage and getting objects from storage.The performance of putting objects into configuration storage and getting objects from storage was insufficient.Putting objects into configuration storage and getting objects from storage is now faster.
Development tools.
Implemented retention of module search index between Designer sessions. Reduced time required for initial generation of module search index. Significantly reduced time required for module search index generation during all subsequent Designer sessions. +Running Designer with command-line option /ClearCache clears the module search index.Module search index was not retained between Designer sessions. Index generation required significant time.It is now easier to work with large configurations.
1C:Enterprise script.
When searching for strings in a value table using the FindRows() method, the index is only analyzed for column content matches between the search parameters and the index. The relative order of columns in the search parameters or in the index is ignored during the search.When searching for strings in a value table using the FindRows() method, the index was only used if the relative order of columns in the search parameters matched the index column order.Using the index to search value tables by multiple columns is now faster.
Full-text search.
Optimized full-text search index generation and update.The performance of initial generation and updates of full-text search index was insufficient.Updating the full-text search index is now faster.
DBMS operations.
Queries.
Improved processing speed of queries containing keyword DISTINCT that get a large number of records (in file infobases).Processing speed of queries containing keyword DISTINCT that get a large number of records (in file infobases) was insufficient.Getting large lists of unique records from file infobases is now faster.
DBMS operations.
Queries.
Faster deletion of large record sets from file infobases. +Faster recalculation of totals for tables with a large number of records in file infobases.The following operations in file infobases were insufficiently fast:
  • Deleting large record sets
  • Recalculating totals for tables with a large number of records
File infobases now work faster in some scenarios.
Dynamic lists.
Improved performance when getting data displayed as dynamic list with conditional formatting.

+

The performance of getting data displayed as dynamic list with conditional formatting was insufficientl.The performance of dynamic lists with conditional formatting is now improved.
Dynamic lists.
Faster opening of forms containing dynamic lists with complex queries.The performance of opening forms containing dynamic lists with complex queries was insufficient.Forms containing dynamic lists with complex queries now open faster.
Dynamic lists.
For dynamic lists, implemented the option to enable or disable getting presentations for values of reference types that are not displayed in the form or are associated with invisible form items. Presentations of key field values for dynamic lists in selection mode are obtained regardless. +Implemented dynamic list property GetInvisibleFieldPresentations.

This change is not implemented in 8.3.7 compatibility mode.

In dynamic lists, presentations were obtained for all reference type values to be sent to client side.Dynamic lists can now be displayed faster in some cases.
Data composition system.
Optimized RAM usage when composing data composition templates with large queries in data composition schema.RAM usage when composing data composition templates with large queries in data composition schema was sub-optimal.Composing data composition templates with large queries in data composition schema now requires less RAM.
Infobase operations.
Slightly improved thin client startup time in file infobases when working with large configurations.Startup time of the thin client in file infobases when working with large configurations was insufficient.Startup time of the thin client in file infobases when working with large configurations is now improved.
Configuration repositories.
Optimized object lock and release operations in configuration repositories. +Changed internal format of locked object data storage for infobases connected to repositories. +The data storage format is changed after the data storage optimization operation is completed using the Local repository data usage settings dialog box. This optimization is only available if the configuration was bound to a configuration repository in an earlier platform version. +To use the optimized infobase in an earlier platform version, rebind the infobase to the configuration repository in an earlier platform version. +The performance of object lock and release operations in configuration repositories was insufficient.Working with configuration repositories that store large configurations is now faster.
Client application.
Improved startup time of client applications after dynamic update.Client applications required longer time to start after dynamic update.Improved startup time of client applications after dynamic update.
Web services and HTTP services.
Every time a method of a web or HTTP service is called, the compiled service module is cashed.Every time a method of a web or HTTP service was called, the service module was compiled.Improved system performace in scenarios that include a large number of web or HTTP services calls.
Accounting registers.
DBMS operations.
Improved performance of the following accounting register record set operations for infobases running in file mode or in client/server mode with PostgreSQL:
  • Write a record set
  • Read a record set
  • Open a record set form
The performance of the following accounting register record set operations was insufficient in infobases running in file mode or in client/server mode with PostgreSQL:
  • Write a record set
  • Read a record set
  • Open a record set form
Optimized accounting register operations for some DBMS.
DBMS operations.
Optimized query plan generation for PostgreSQL version 9.6.3. This improves the performance of complex queries that use data access restriction templates.

Optimization is available for PostgreSQL versions 9.6.3-2.1C and later.

In PostgreSQL, performance of complex queries that used data access restriction templates was insufficient, in some cases applications might stop responding during query execution.Improved performance of PostgreSQL operations initiated from 1C:Enterprise.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Background and scheduled jobs.
Server clusters.
Changed approach to storing background and scheduled job execution history. In client/server mode, the stored history data was broken down by infobase. The following history data is stored for each infobase:
  • Up to 1 000 1C:Enterprise script-based background jobs
  • Up to 1 0000 scheduled jobs
  • Up to 1 000 system background jobs (i.e. background jobs created by system)

For each job (background, scheduled, or system background), information about at least 3 latest job executions is saved, if possible. The three executions limit can be reduced if over 1 000 records are created for any given job type.

In file mode, the stored job history data was broken down by infobase. In client/server mode, the stored job history data was broken down by server cluster. In both cases, data was stored on the total of 1 000 jobs, regardless of job type (background, scheduled, or system background).Improved diagnostics of background and scheduled job execution when a large amount of jobs is present in the system. Reduced risk of information about rarely used 1C:Enterprise script-based background jobs being superseded by information about a large amount of scheduled jobs or system background jobs.
Data display.
Charts.
For objects Chart, GanttChart, PivotChart, and Dendrogram, the default value of Font property of subordinate objects describing specific chart areas is set to Auto, meaning Normal text font. +When the web client is running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format include checks for OS-based substitutions of chart fonts. If the OS substitutes chart fonts, the resulting files include the names of the fonts that are actually used. +When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts are not substituted by Arial; instead, the names of the fonts that are actually used are determined. +For objects Chart, GanttChart, PivotChart, and Dendrogram, the default value of Font property of subordinate objects describing specific chart areas was set to Text font. +When the web client was running on Windows, the procedures of displaying charts in the web client, exporting spreadsheet documents containing charts to HTML5 format, and exporting charts to SVG format included exporting fonts "as is", without attempting to determine which fonts were actually used. +When exporting spreadsheet documents to HTML format and displaying spreadsheet documents in the web client, system fonts were substituted by Arial.Unified fonts used to display charts across client applications, including the web client running in a variety of web browsers. Unified fonts used to display spreadsheet documents across client applications. +When exporting spreadsheet documents containing charts, original fonts used to display the charts are retained.
Binary data.
Binary data management capabilities are now expanded. Implemented bilateral conversion between binary data and the following data types: binary data array, string, binary data buffer, Base64 string, hexadecimal string, and binary data as string.

Implemented binary data usage in methods and constructors that previously supported files only. +Implemented bitwise operations (AND, OR, NOT, XOR, NAND, and inversion) for binary data stored in a binary data buffer. +Implemented binary data exchange with add-ins for add-in developers (also available in the web client). +Implemented getting bulk permissions when working with binary data in the web client. +

Implemented direct copying of binary data from DataReader object to DataWriter object.

Implemented global context methods ConcatBinaryData(), SplitBinaryData(), GetBinaryDataFromString(), GetBinaryDataBufferFromString(), GetStringFromBinaryData(), GetStringFromBinaryDataBuffer(), GetBinaryDataFromBase64String(), GetBinaryDataBufferFromBase64String(), GetBase64StringFromBinaryData(), GetBase64BinaryDataFromBinaryData(), GetBinaryDataFromBase64BinaryData(), GetBase64BinaryDataBufferFromBinaryDataBuffer(), GetBinaryDataBufferFromBase64BinaryDataBuffer(), GetBinaryDataFromHexString(), GetBinaryDataBufferFromHexString(), GetHexStringFromBinaryData(), GetHexStringFromBinaryDataBuffer(), GetHexBinaryDataFromBinaryData(), GetBinaryDataFromHexBinaryData(), GetHexBinaryDataBufferFromBinaryDataBuffer(), GetBinaryDataBufferFromHexBinaryDataBuffer(), GetBinaryDataFromBinaryDataBuffer(), GetBinaryDataBufferFromBinaryData(), NumberFromHexString(), and NumberFromBinaryString(). +Implemented the option to use binary data streams:

  • In TextReader, TextWriter, ZipFileReader, and ZipFileWriter object constructors
  • In Open() method of TextReader, TextWriter, ZipFileWriter, and ZipFileReader objects
  • In Write() method of TextDocument, SpreadsheetDocument, FormattedDocument, GeographicalSchema, and Picture objects
  • In Put() method of FTPConnection object
  • In Read() method of TextDocument, SpreadsheetDocument, and GeographicalSchema objects
  • In the following methods of CryptoManager object: Encrypt(), Decrypt(), Sign(), and VerifySignature()
  • In method CryptoCertificate.Unload()
  • In method DataHashing.Append()
  • In method FTPConnection.Get()

Implemented OpenStream() method for objects HTMLReader, HTMLWriter, JSONReader, JSONWriter, FastInfosetReader, FastInfosetWriter, XMLReader, and XMLWriter.

Implemented GetBodyAsStream() method for objects HTTPRequest, HTTPResponse, HTTPServiceRequest, and HTTPServiceResponse. +Implemented method ConversionToCanonicalXML.CanonicalizeToStream().

For XSLTransform object, implemented methods LoadXSLStyleSheet() and Transform().

Implemented method ZipFileWriter.GetBinaryData().

For BinaryDataBuffer object, implemented methods WriteBitwiseAnd(), WriteBitwiseOr(), WriteBitwiseXor(), WriteBitwiseAndNot(), and Invert().

For DataReader object, implemented methods CopyTo() and BeginCopyTo().

For methods CopyTo() and BeginCopyTo() of Stream object, changed the purpose of the second method parameter and the return value: the number of bytes to be copied is passed as the second parameter, and the return value is the actual number of copied bytes. The buffer size is defined automatically. The method descriptions are now uniform with the similar methods of DataReader object. This change is not implemented in 8.3.9 compatibility mode.

For methods CopyTo() and BeginCopyingTo() of Stream object, the size of buffer used for copying was passed as the second parameter, and return values were not available.It is now easier to use binary data for a range of applied tasks.
Event log.
In the event log (opened from a file or otherwise), each data presentation string recorded to the log when an event was registered is only displayed to users that have the right to view this data or Administration right. If a user does not have Administration right and the data presentation is probably unavailable to them, the saved data presentation is hidden from this user. +If the Data field of an event log record contains a reference and a user probably has no rights to view the related data object, the Data presentation field is blank.Access rights of the current user were not checked when displaying presentation of event log data. Users with restricted rights no longer can access data objects that are unavailable to them by accessing presentations of unavailable objects that were saved earlier.
Development tools.
In the call stack window of the debugger, implemented correct display of method parameters containing extremely long text strings or multiline strings. In this case, the presentation is based on the initial 20 characters of the parameter string appended with ellipsis (...), continued with other parameters and the closing bracket of the method.In the call stack window of the debugger, method parameters containing extremely long text strings or multiline strings were displayed incorrectly: text presentations of the following parameters (if any) and the closing bracket of the method were missing.The accuracy of data in the call stack window is improved.
Spreadsheet documents.
When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, only right-aligned cell text is converted into numeric format. The content of cells without right alignment is saved as text. +This change is not implemented in 8.3.9 compatibility mode.When exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats, cell text was converted into numeric format regardless of text alignment.Exporting spreadsheet documents to XLS (Microsoft Excel 97-2003) or Microsoft Office OpenXML (Microsoft Excel 2007- 2010) formats is improved.
Print tools.
Implemented settings for default page size during printing (including printing to PDF file). This feature is available both for the web client and for documents generated by scheduled jobs. Implemented the PrintSettings object. +In the web client parameters dialog box, implemented Default page size settings item. +This change is not implemented in 8.3.9 compatibility mode.A4 format was used as the default paper size. +In the web client parameters dialog box, Default page size settings item was not available.When printing a document (or saving it to a PDF file) in the web client, the paper size set for the current client application is used for pagination purposes. Thus, the resulting document better satisfies user expectations. +This functionality is now also available for the documents generated by scheduled jobs.
Data composition system.
When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration are automatically removed from the schema and settings.When loading data composition schema and data composition settings in interactive mode, style colors and fonts not available in the current configuration caused XDTO data conversion errors.

+

Now data composition schema and data composition settings containing style colors and fonts not available in the current configuration can be used.
Dynamic lists.
Content of System fields folder cannot be used as selection fields in dynamic lists. +If a dynamic list has no main table specified or the specified main table is missing a dynamic list key field, grouping fields cannot be set up for this dynamic list.

This change is not implemented in 8.3.9 compatibility mode.

Content of System fields folder could be used as selection fields in dynamic lists. +If a dynamic list had no main table specified or the specified main table was missing a dynamic list key field, grouping fields could be set up for this dynamic list, resulting in data retrieval error.Eliminated unexpected system behavior. Dynamic lists are more reliable now.
Dynamic lists.
The following properties of DynamicList object are unavailable in the thick client: DynamicDataRead, MainTable, CustomQuery, and QueryText. +Assigning values to managed form attributes of DynamicList type is not allowed. +Passing attributes of DynamicList type as method parameters or return values in client/server interactions is not allowed. +This change is not implemented in 8.3.9 compatibility mode.The following properties of DynamicList object were available in the thick client: DynamicDataRead, MainTable, CustomQuery, and QueryText. However, changing their values did not affect the dynamic lists in any way. +Assigning values to managed form attributes of DynamicList type was allowed. However, further behavior was not defined. +Passing attributes of DynamicList type as method parameters or return values in client/server interactions was allowed. However, further behavior was not defined.Dynamic lists are more reliable now. The listed cases of dynamic list misuse are no longer supported.
Charts.
Series data (marker) in a chart legend depends on the appearance of the series in the chart (line color, line style, and marker).

This change is not implemented in 8.3.9 compatibility mode.

Series data in chart legend was always represented by a square marker of color matching color of the series in the chart.Chart readability is now improved (best results for charts printed in black and white).
Data composition system.
Templates of resources created at intersection with matching predefined templates of grouping titles are initially blank. +This change is not implemented in 8.3.9 compatibility mode.Resources were displayed in templates of resources created at intersection with matching predefined templates of grouping titles. Eliminated unexpected system behavior.
Cryptography support.
If a serial number of a certificate starts with a set high bit, a leading zero byte is appended to the serial number. +This change is not implemented in 8.3.8 compatibility mode.A leading zero byte was not appended to serial numbers of certificates.Defects in encryption management logic are corrected.
Dynamic lists.
Implemented disabling auto filling of available fields in dynamic lists. This option is only available for dynamic lists generated using custom queries. +The system behavior is identical to the similar data composition schema option. +Implemented dynamic list property AutoFillAvailableFields. +This change is not implemented in 8.3.7 compatibility mode.Auto filling of all available fields was enabled for all dynamic list queries. Availability of the list fields can now be changed by the extension of the query language for data composition schema.
Charts.
Data composition system.
Implemented management of series display order in chart legends (also available in the data composition system). +Implemented property Chart.SeriesOrderInLegend. +For ChartType appearance item of DataCompositionAreaTemplateChartAppearance, DataCompositionChartOutputParameterValues, DataCompositionOutputParameterValues, and DataCompositionGroupOutputParameterValues objects, implemented parameter SeriesOrderInLegend. +This change is not implemented in 8.3.9 compatibility mode.Series display order in chart legends could not be changed.Additional chart display features are now implemented.
Development tools.
The user is asked if they want to save their work whenever they attempt to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. The user was not asked if they want to save their work whenever they attempted to close the query expression editor dialog box (in the query wizard) by pressing Esc or clicking the Close button (X) after making changes to the expression in the editor. This behavior resulted in loss of user work.Eliminated unexpected system behavior. +Reduced risk of loss of user work when editing query expressions.
Development tools.
Improved diagnostics and system behavior when an invalid or missing manifest is discovered in a picture archive:
  • Archive validation is performed during the import in interactive mode
  • Pictures with invalid or missing manifests are not displayed in Designer
  • Accessing the archive from 1C:Enterprise script generates an error more closely related to the actual problem
The system behavior was different when an invalid or missing manifest was discovered in the picture archive:
  • Archive validation was not performed during the import in interactive mode
  • Attempts to display the picture in Designer or to call it from 1C:Enterprise script could result in abnormal termination or a vaguely described error
Improved diagnostics and system reliability when accessing picture archives with invalid or missing manifests. +
Dumping configurations to files/Restoring configurations from files.
During full restoration of a configuration from files, the following rules apply:
  • Configurations that are not covered by support and not connected to configuration repositories can be restored without any restrictions (as before).
  • Configurations that are connected to configuration repositories cannot be restored (the corresponding menu item is disabled).
  • Configurations that are covered by support can be restored provided that:
    • Editing is allowed.
    • All configuration objects can be edited.

During partial restoration of a configuration from files, the following rules apply: +

  • Configurations can only be restored if all objects to be restored are locked in the configuration repository.
  • Configurations can be restored if all objects to be restored can be edited (for configurations that are covered by support).
Dumping and restoring configurations from files were executed regardless of whether a configuration is covered by support or connected to a configuration repository.Eliminated issues that occurred when attempting to restore a configuration that is covered by support or connected to the configuration repository from files.
Dynamic lists.
Improved algorithm for searching through search boxes of dynamic lists:
  • Implemented searching for full dates (including both date and time)
  • Implemented searching for numbers with integer and fractional parts by entering integer part only
  • Better readability of search results

This change is not implemented in 8.3.9 compatibility mode.

Searching through search boxes of dynamic lists was implemented as follows:
  • Searching for full dates (including both date and time) resulted in a separate search for date and a separate search for the string containing time data
  • Searching for values similar to numbers with integer and fractional parts resulted in a separate search for the integer part and a separate search for the fractional part, with AND conjunction
  • Search results could be displayed inaccurately + +
Improved searching using search boxes of dynamic lists.
Dynamic lists.
Fields that cannot be used in filters are not available in the advanced search dialog box of dynamic lists (i.e. not displayed in the Search in field list). +If the current column of the table associated with the dynamic list displays a field that cannot be used in filters, the command that starts the search by current value is not available.Fields that could be used in filters were available in the advanced search dialog box of dynamic lists (i.e. displayed in the Search in field list). +Availability of the command that starts the search by current value was not affected by whether the field displayed in the current column of dynamic list can be used in filters. Eliminated unexpected system behavior.
Administration tools.
During the verification and repair of a file infobase, infobase table records are deleted if their keys become non-unique after the records are modified. At that, a diagnostic message is displayed in the message window.

+

+

+

During the verification and repair of a file infobase, keys of infobase table records were not checked for uniqueness after the records were modified. This could result in records with non-unique keys occurring in the infobase. To remedy this, it was necessary to run the infobase verification and repair procedure once more.Unified behavior of infobase verification and repair procedure between file and client/server infobase modes.
1C:Enterprise script.
Enumerations are present in type selection dialog boxes and type description dialog boxes for all client applications running in managed application mode. +This change is not implemented in 8.3.9 compatibility mode. Enumerations were not present in type selection dialog boxes and type description dialog boxes for thick client and thin client applications running in managed application mode. +However, enumerations were present in these dialog boxes for the web client.Eliminated unexpected system behavior.
Spreadsheet documents.
When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings starts with a lowercase letter: sharedStrings.xml. +This change is not implemented in 8.3.9 compatibility mode.When exporting spreadsheet documents to Microsoft Office OpenXML (Microsoft Excel 2007 and earlier) format, the name of XML component of shared strings started with an uppercase letter: SharedStrings.xml.The platform behavior now conforms to OpenXML standard. Improved compatibility with case-sensitive systems parsing OpenXML files.
Managed forms.
Dynamic lists.
Implemented the Main attribute flag for managed form attribute of DataCompositionSettingsComposer type. In this case, Managed form extension for settings composer serves as form extension. +The User-defined settings group form property and OnUpdateUserSettingSetAtServer event handler are now available for the form.Managed form property Main attribute was only set for automatically generated forms of dynamic list settings. Developers were not allowed to create these forms.Developers can now create all-purpose data composition settings editing forms.
Development tools.
When comparing and merging modules (without using third-party tools), placement of methods in areas defined by preprocessor instructions (#Region, #If) is taken into account. +Areas defined by preprocessor instructions are isolated as separate entities (together with procedures and functions). For these areas, implemented specifying the merging parameters.This feature was not provided. +The preprocessor instructions were processed as comments linked to the procedures they preceded. +Module merging could result in corrupted structure of blocks defined by preprocessor instructions.Module merging performed by native Designer tools is now more reliable and user-friendly.
Managed forms.
The navigation panel of the item form of an hierarchical catalog or chart of characteristic types contains:
  • Commands used to access subordinate catalogs with item hierarchy or item and folder hierarchy (no changes since the earlier versions)
  • Commands used to access information registers whose leading dimension type matches the type of catalog or chart of characteristic types, and whose property Select folders and items for this dimension is set to Items or Folders and items

The navigation panel of the group form of an hierarchical catalog or chart of characteristic types contains:

  • Commands used to access subordinate catalogs with folder hierarchy or item and folder hierarchy
  • Commands used to access information registers whose leading dimension type matches the type of catalog or chart of characteristic types, and whose property Select folders and items for this dimension is set to Items or Folders and items

+

This change is not implemented in 8.3.9 compatibility mode.

All commands used to access subordinate catalogs were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access subordinate catalogs. +All commands used to access information registers were located in the navigation panel of the item form of an hierarchical catalog or chart of characteristic types. The navigation panels of group forms of these configuration objects did not contain any of the commands used to access information registers. Eliminated unexpected system behavior.
Development tools.
Dumping configurations to files/Restoring configurations from files.
In the "dump configuration to files" feature, changed the dump format of information about dynamic lists located in managed forms. +It is recommended that you dump all forms containing dynamic lists once more.In the "dump configuration to files" feature, the dump format of information about dynamic lists located in managed forms was different.In the "dump configuration to files" feature, the format of resulting XML files is improved.
Database configuration update.
Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs are not displayed when updating database configuration.Messages about creation and deletion of options tables for charts of characteristic types, charts of accounts, charts of calculation types, and catalogs were displayed when updating database configuration.Messages that contain no useful information for the user are no longer displayed when updating database configuration.
Charts.
 +

Expanded set of palettes that can be used to customize chart colors. The palettes can contain either fixed color sets or color sets that vary depending on the quantity of series. Implemented creation of custom color sets for charts. For ChartColorPalette system enumeration, implemented values Auto, Custom, Gradient, Blue, Orange, Green, Yellow, Gray, Warm, Cold, Bright, Soft, and Pastel. +For Chart object, implemented the following:

  • Properties GradientPaletteStartColor, GradientPaletteEndColor, and GradientPaletteMaxColors
  • Methods GetPalette() and SetPalette()

For ChartType appearance item of data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, implemented parameters ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, and GradientPaletteMaxColors +

Only two palettes (with 8 and 32 colors respectively) were available for picking chart colors. Creation of custom chart color palettes was not supported.Additional chart appearance features are now implemented.
Data composition system.
When data composition output processor outputs merged cells to a spreadsheet document, width of the columns containing merged cells is adjusted in order to minimize height of the content of these cells. +This change is not implemented in 8.3.9 compatibility mode. When data composition processor outputted merged cells to a spreadsheet document, width of the columns containing merged cells was not adjusted in some cases. This could result in inappropriately narrow columns. Calculation of width of spreadsheet document columns containing merged cells performed by data composition output processor is improved in some cases.
Accounting registers.
The PointInTimeWithPeriodAdjustment type is available in the thin and web clients.The PointInTimeWithPeriodAdjustment type was available only in the thick client and only on the server.Eliminated unexpected system behavior.
Spreadsheet documents.
For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format is added to the Paste special operation.For spreadsheet documents, the option to paste data that has XLS (Microsoft Excel 97-2003) or ODS (OpenDocument Spreadsheet) format was not available.The Paste special operation now supports selection from all spreadsheet formats that support pasting.
Spreadsheet documents.
Data composition system.
For spreadsheet documents, the option to automatically adapt column width to the display area is implemented (both for viewing and printing). For SpreadsheetDocumentRange and DataCompositionAreaTemplateTableCellAppearance objects, implemented properties HorizontalStretch and WidthWeightFactor. For DataCompositionAppearance object, implemented appearance parameters HorizontalStretch and WidthWeightFactor.

When the data composition system displays a chart in a spreadsheet document, it automatically sizes the chart to fit the display area width.

This change is not implemented in 8.3.9 compatibility mode.

Spreadsheet document column width could not be adapted to the display area width.

When the data composition system displayed a chart in a spreadsheet document, the chart had fixed width.

Improved options for adapting spreadsheed documents to the display area.
Spreadsheet documents.
For form field extension for a spreadsheet document field, the following improvements are implemented:
  • More options for cell selection visibility. You can completely hide the cell selection, or you can make the cell selection visible only when multiple cells are selected (Show selection property). For SelectionShowMode system enumeration, implemented properties DontShow, WhenMultipleCellsSelected, and WhenMultipleCellsSelectedWhenActive.
  • More options for scroll bar visibility: you can have scroll bars displayed only when necessary. The type of VerticalScrollBar и HorizontalScrollBar properties is changed to ScrollBarUse.
  • The option to change the shape of pointer located in a form field extension for a spreadsheet document field. The pointer shape can change depending on the spreadsheet document area where it is located. Implemented property PointerType.
  • The behavior of arrow keys depends on the Show selection property value. If this property is set to Do not show, the arrow keys scroll the spreadsheet document. If this property is set to any of When multiple cells... values, pressing the arrow keys while holding down Shift changes the selection size, and pressing arrow keys without holding down Shift scrolls the spreadsheet document (while keeping the selection).
The following options were available for form field extension for a spreadsheet document field:
  • The selection was either always visible or visible when a cell was activated.
  • The scroll bars were always visible or always hidden. Making scroll bars visible when necessary was not available.
  • The pointer shape in a spreadsheet document always depended on the content of the cell where is was located.
  • The behavior of arrow keys in a spreadsheet document did not depend on any properties of form field extension for a spreadsheet document field.
Extended display options for spreadsheet documents embedded in managed forms.
Managed forms.
In managed form tables, improved algorithm for automatic column width calculation based on the font settings.

This change is not implemented in 8.3.9 compatibility mode.

The algorithm for automatic column width calculation based on the font settings sometimes generated poor results.Improved view of managed form tables.
Dumping configurations to files/Restoring configurations from files.
When restoring help topics from XML files, 1C:Enterprise does not check whether the language of the help topics (Language configuration object) is available in the configuration.When restoring help topics from XML files, 1C:Enterprise did not restore the help topics whose language (Language configuration object) was not available in the configuration.Simplified dumping and restoration of configurations, external reports, and external data processors to or from XML files.
Development tools.
Configuration extensions.
Configuration extension bookmarks, breakpoints, and performance measurements are stored with extension names.Configuration extension bookmarks, breakpoints, and performance measurements were stored with internal extension IDs.Support for future integration of extension debugging with 1C:Enterprise Development Tools.
macOS.
Spreadsheet documents.
Implemented export of spreadsheet documents to PDF format on macOS.An attempt to export a spreadsheet document to PDF format on macOS generated an error.Eliminated unexpected system behavior.
Operating system.
The time zone detection algorithm on Windows is modified. Now the time zone is determined as follows:
  • Get time zone presentation using Windows API.
  • Search Windows registry for time zone ID by presentation.
  • Use ICU library to determine time zone by ID.
  • If the time zone cannot be determined using this algorithm, try the previous algorithm.
The platform used the following time zone detection algorithm on Windows:
  • Get time zone ID from Windows registry.
  • Use ICU library to determine time zone by ID.
  • If the time zone with this ID is not found in ICU, get time zone using Windows API.
  • Apply time zone parameters (offset, daylight saving time, and so on) and search ICU for a matching time zone.
The session time zone is determined correctly on Windows terminal servers.
DBMS operations.
If 1C:Enterprise is running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it supports setting lock waiting time. The waiting time is retrieved from the infobase parameters, just like in configurations that use other DBMS types.If 1C:Enterprise was running in managed lock mode (in client/server mode) with PostgreSQL version 9.3 or later, it did not support setting lock waiting time. In configurations that used PostgreSQL, setting lock waiting time was only supported in automatic lock mode. +In configurations that used PostgreSQL, operations with lock waiting time in managed mode are identical to operations with lock waiting time in configurations that use other DBMS.
Charts.
Spreadsheet documents.
When a spreadsheet document that contains a chart is saved to a file, automatically assigned point colors, series colors, and series markers are stored in the format supported by earlier 1C:Enterprise versions. This ensures that the colors and markers are displayed correctly in earlier 1C:Enterprise versions.When a spreadsheet document that contained a chart was saved to a file, automatically assigned colors and markers were stored in the format that was not supported by earlier 1C:Enterprise versions. This might significantly alter the chart look in earlier 1C:Enterprise versions.The look of spreadsheet documents with charts in earlier 1C:Enterprise versions is very similar to their look in 1C:Enterprise version 8.3.10 or later.
Internet-enabled functionality.
The DigiCert certifying center root certificate was added to the cacert.pem file (root certificates file), included in the platform.The DigiCert certifying center root certificate was not included in the cacert.pem file (root certificates file).

+

1C:Enterprise applications can now connect to 1C company services. Service infrastructure update is needed.
External reports and data processors.
The option to disable the warning of the unsafe operation protection system when you create an external report or data processor object is implemented (use it when you are sure that the file specified in the method parameter contains trusted script).

For the Create() method of ExternalReportsManager and ExternalDataProcessorsManager objects, the UnsafeOperationProtection parameter is implemented.

This feature was not provided.When adding an external report or an external data processor from a file, you can specify that the file contains trusted script and therefore does not require displaying the unsafe operation protection system warning.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Managed forms.
When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event BeforeCollapse is generated for each node being collapsed throughout the hierarchy. +This change is not implemented in 8.3.9 compatibility mode.When collapsing a node of a value tree with subordinate items that is displayed in a managed form, event BeforeCollapse was only generated for top-level tree items.Eliminated unexpected system behavior. +Value tree items to be collapsed are now defined more precisely in interactive mode.
Access rights.
Calling the AccessRight() method generates an exception if the access right being checked cannot be applied to a metadata object. +This change is not implemented in 8.3.9 compatibility mode.Calling the AccessRight() method always returned True if the access right being checked could not be applied to a metadata object. +Eliminated unexpected system behavior.
Data composition system.
Data composition schema parameters whose types contain only types disabled by functional options are added to the list of available data composition schema parameters with disabled visibility. Therefore, these parameters cannot be edited by users but can still be accessed from 1C:Enterprise script. Moreover, these parameters are not added to the list of available parameter fields. +When a report option is loaded, the usage flag is cleared for the data parameters disabled by functional options. +The DataCompositionSettingsComposer.Refresh() method disables the Use property of data parameters disabled by functional options. +This change is not implemented in 8.3.9 compatibility mode.Functional options did not affect the visibility of data composition parameters. +When a report option was loaded, the usage flag was not cleared for the data parameters disabled by functional options. +The DataCompositionSettingsComposer.Refresh() method did not modify the Use property of data parameters disabled by functional options.Management of report parameters of types disabled by functional options is now more user-friendly.
HTML support.
For HTMLDocumentShell object, implemented property TemplateLanguageCode. If this property is set, the following methods of this object return a result for the specified language: GetCOMObject(), GetHTMLDocument(), and GetText().Selection of language to be used in return values of HTMLDocumentShell object methods was not available for HTML templates. Now HTML templates can be used for languages that do not match the language of the current session.
System requirements.
Changed presentation of Microsoft Windows version, starting from Windows Vista, in SystemInfo.OSVersion property. The property text contains the user presentation of the operating system name, as well as technical information (version, build number, and so on). +This change is not implemented in 8.3.9 compatibility mode.Presentation of Microsoft Windows version, starting from Windows Vista, in SystemInfo.OSVersion property did not contain the user presentation of operating system name.Information about Microsoft Windows version stored in SystemInfo.OSVersion property (for systems running on Microsoft Windows) now offers better readability.
Web services and HTTP services.
Internet-enabled functionality.
When method HTTPConnection.CallHTTPMethod() is called, its parameter HTTPMethod must comply with RFC 7230 Read more.. If this requirement is not met, an exception is raised. +This change is not implemented in 8.3.9 compatibility mode.When method HTTPConnection.CallHTTPMethod() was called, its parameter HTTPMethod could take up any value.The behavior of 1C:Enterprise better complies with RFC standards now.
DBMS operations.
When a 1C:Enterprise application runs in client/server mode using a Microsoft SQL Server database, a query containing expression CAST(... AS STRING(...)) adds trailing space characters to the operation result until it reaches the required length. +This change is not implemented in 8.3.9 compatibility mode.When a 1C:Enterprise application ran in client/server mode using a Microsoft SQL Server database, a query containing expression CAST(... AS STRING(...)) did not add trailing space characters to the operation result until it reached the required length.1C:Enterprise behavior is now uniform across all supported databases.
XML and XDTO support.
Serialization of a ValueList object using the XDTOFactory.WriteXML() method creates an XML document based on the schema used for serialization of this object with XDTOSerializer.WriteXML() method.

Due to this change:

  • Value lists serialized in version 8.3.10 cannot be read in version 8.3.6 or earlier but can be read in version 8.3.7 or later by using XDTOFactory
  • Value lists serialized in version 8.3.10 can be read in version 8.3.6 or earlier by using XDTOSerializer
  • Value lists serialized in versions 8.3.7 to 8.3.9 can be read in any version. +
Serialization of a ValueList object using the XDTOFactory.WriteXML() method created an XML document that did not match the schema used for serialization of this object with XDTOSerializer.WriteXML() method.Eliminated unexpected system behavior.
Managed forms.
If a hyperlink is displayed in a managed form table cell and Read only mode is set for this table cell, double-clicking this cell results in raising the Selection table event once. +This change is not implemented in 8.3.9 compatibility mode.If a hyperlink was displayed in a managed form table cell and Read only mode was set for this table cell, double-clicking this cell resulted in raising two Selection table events.Eliminated unexpected system behavior.
Development tools.
For event subscriptions, implemented the match check for events and source types. The check is performed prior to saving the configuration. If the event does not match the source type, an error is generated and the configuration is not saved. +This change is not implemented in 8.3.9 compatibility modeFor event subscriptions, the match check for events and source types was not performed. Eliminated unexpected system behavior.
Queries.
An error is generated during query analysis if the expression following the temporary table name does not contain the field name. +This change is not implemented in 8.3.9 compatibility mode.During query analysis, if the expression following the temporary table name did not contain the field name, the name of the first field of the temporary table was used instead. Eliminated unexpected system behavior.
Spreadsheet documents.
When displaying spreadsheet documents in Taxi interface, the Auto text color is selected as follows:
  • For displaying on monitors: style-based color for text editing
  • For printing: black

This change is not implemented in 8.3.9 compatibility mode.

When displaying spreadsheet documents in Taxi interface, black was always used as the Auto text color. Eliminated unexpected system behavior.
Managed forms.
For attributes of String or Number type displayed in a managed form input field with list selection mode enabled:
  • Restrictions to the length of string that can be entered are removed
  • The input field displaying this data is automatically stretched horizontally

This change is not implemented in 8.3.9 compatibility mode.

When editing values of Number type in a managed form input field with list selection mode enabled, number qualifiers configured for the attribute were affecting format of the text being edited. Improved usability of text input fields.
Spreadsheet documents.
When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ is not removed from the result. +This change is not implemented in 8.3.9 compatibility mode.When processing a template in a spreadsheet document cell, content located between the final section [] and an escaped character [ was removed from the result.Eliminated unexpected system behavior.
Internet-enabled functionality.
When 1C:Enterprise is running on Microsoft Windows, web server certificate checks are performed for all chains of trusted certificates registered in the Windows trusted certificate store.When 1C:Enterprise was running on Microsoft Windows, web server certificate checks could fail if a trusted parent certificate of the certificate being checked was not registered in the trusted certificate store.Eliminated situations that could occur on Microsoft Windows when 1C:Enterprise failed to check a web server certificate via HTTPS/FTPS if the server certificate publisher was not included in the list of trusted root certificates.
Full-text search.
If a full-text search query generates multiple intermediate results and the search result contains under 1 mln records, the user gets the search result. This change is not implemented in 8.3.9 compatibility mode. +To enable this feature, set the configuration compatibility mode to None and update the full-text search index. +The later a data item was modified, the higher in the full-text search results it is displayed (within a single configuration object, such as a document type). If a full-text search query generated multiple intermediate results, the error stating that there are too many search results was displayed to the user. Full-text search now returns results when searching for several words that commonly occur separately but rarely occur together.
Client application installation.
Searching the distribution kit directories for new 1C:Enterprise versions when opening the infobase list window is now faster. The search is performed for the names of distribution kit directories. +Distribution kit type and bitness are determined based on the name of .msi file:
  • 1CEnterprise 8.msi — 32-bit version, full distribution kit
  • 1CEnterprise 8 Thin client.msi — 32-bit version, thin client
  • 1CEnterprise 8 (x86-64).msi — 64-bit version, full distribution kit
  • 1CEnterprise 8 Thin client (x86-64).msi — 64-bit version, thin client

Searching the distribution kit directories for new 1C:Enterprise versions was insufficiently fast because it relied on data stored in properties of .msi files.The infobase list dialog box now opens faster if the Install new application versions automatically check box is selected in the dialog box settings.
Managed forms.
When attempting to create a managed form group with an invalid value of Type property using 1C:Enterprise script, an exception is raised. +This change is not implemented in 8.3.9 compatibility mode.When attempting to create a managed form group with an invalid value of Type property using 1C:Enterprise script, the system behavior was not defined and could result in abnormal termination. Eliminated unexpected system behavior.
Data composition system.
Implemented setting expressions simultaneously both for detailed records and totals records of user-defined fields of the data composition system. Implemented the same for user-defined field presentations in detailed records and totals records of the data composition system. +For DataCompositionUserFieldExpression object, implemented methods SetExpressions() and SetExpressionsPresentation(). +Methods SetDetailRecordExpression(), SetTotalRecordExpression(), SetDetailRecordExpressionPresentation(), and SetTotalRecordExpressionPresentation() are now deprecated and supported for compatibility purposes only. It is recommended that you do not use any of these. Expressions of user-defined fields of the data composition system for detailed records and totals records were set by different methods. Presentations of user-defined fields of the data composition system for detailed records and totals records were also set by different methods. Eliminated unexpected system behavior. +User-defined fields of the data composition system that contain deleted or renamed query fields in both expressions are now editable.
Data composition system.
When automatically filling available fields of query data set for virtual tables of information registers, dimension fields become available for filtering based on virtual table parameters. +This change is not implemented in 8.3.9 compatibility mode. +When automatically filling available fields of query data set for virtual tables of information registers, dimension fields did not become available for filtering based on virtual table parameters.Getting data from information registers through the data composition system is now more efficient when virtual tables of information registers are used.
Queries.
When adding filter expressions to a query by using QuerySchemaExpression object constructor, the filter expressions are added without conversion. +This change is not implemented in 8.3.9 compatibility mode. When adding filter expressions to a query by using QuerySchemaExpression object constructor, the filter expressions were corrupted due to conversion.Eliminated unexpected system behavior.
Configuration repositories.
New configuration repositories are created in version 8.3.8 format, with page size 8192 bytes.

You can use the cnvdbfl utility to change configuration repository format from version 8.2.14 to version 8.3.8 and vice versa.

The configuration repository database was created in version 8.2.14 format.You can set the configuration repository format to version 8.3.8. Repositories that have this format can store larger reporitory history.
Accounting registers.
If an accounting register resource value is associated with the accounting flag for a chart of accounts, values of this resource in Balance, Turnovers, BalanceAndTurnovers, and DrCrTurnovers virtual tables depend on the status of this accounting flag for each account. If the accounting flag is set, the resource value has Number type. If the accounting flag is cleared, the resource has value is NULL. +This change is not implemented in 8.3.9 compatibility mode. Virtual tables of accounting registers (Balance, Turnovers, BalanceAndTurnovers, and DrCrTurnovers) could return non-NULL values of accounting register resources associated with accounting flags for accounts where these accounting flags were disabled.Eliminated unexpected system behavior.
Web client.
Client application.
Interface.
Managed forms.
Applied objects.
Ended support of modal windows in the web client, regardless of web browser used. Any modal method call performed by an application now raises an exception. +For the thin client and web client, ended support of document posting performed in the mode interactively specified by the user. Accessing a document with such posting mode now raises an exception. The system enumeration value PostingModeUse.Ask is no longer supported by the thin client and web client. +The window opening option (Window parameter) is now ignored when used in methods OpenForm() and GetForm(), and when used as a structure property value CommandExecuteParameters.Window (with type defined by system enumeration WindowOpenVariant). In the thin client, the Window parameter is ignored when the compatibility mode is disabled. The system enumeration WindowOpenVariant is excluded from the Syntax Assistant. +In the thin client and web client, forms can no longer be opened in separate windows when Forms in tabs interface mode is enabled. +In the web client, ended support of interface mode Forms in separate windows. In the thin client, interface mode Forms in separate windows cannot be enabled through the client application parameters dialog box. In the web client, ended support of the web client command-line parameter isdi. +The check whether popup windows are blocked is not performed when starting the web client. +Windows that locked other windows were supported in the web client. +Document posting mode could be specified by the user interactively, as a part of the posting procedure. +In the thin client and web client, forms could be opened in separate windows when interface mode Forms in tabs was enabled. +In the web client, interface mode Forms in separate windows was supported.Ended support of interface mode not supported by the current web browsers.
Interface.
Data display.
For global context method ShowUserNotification(), implemented parameters UserNotificationStatus and UniquenessKey. The parameter of URL method is renamed to ActionOnClick.

The look of notifications with Information status is slightly changed. In Taxi interface, notifications with Important status are redesigned, including the following changes:

  • Displaying multiple notifications simultaneously
  • Displaying notifications while the main application window is minimized
  • Refreshing the notification window until the user closes it
  • Reacting to the user clicking the notification window

Implemented notification management through the notification center. Dragging the notification window is not supported. +

For the specifics of notification behavior depending on the operating system and the client application, refer to the documentation.

These features were not provided. +Capabilities of global context method ShowUserNotification() were limited.Notifications with Important status are implemented. They are displayed even if the application window is inactive.
Charts.
Spreadsheet documents.
Implemented the availability to open details for Gannt charts displayed in spreadsheet documents. The procedure is identical to opening details for Gannt charts displayed in managed forms.

For spreadsheet document event handlers DetailProcessing and AdditionalDetailProcessing, implemented parameter AdditionalParameters. This parameter stores the date that is used as an input parameter for retrieving the details. This change is not implemented in 8.3.9 compatibility mode. +The context menu of Gantt charts in spreadsheet documents now opens on releasing the right mouse button. This change is not implemented in 8.3.9 compatibility mode.

Any attempt to access details for a Gantt chart in a spreadsheet document resulted in opening a window containing a noninteractive list of details. +Spreadsheet document event handlers DetailProcessing and AdditionalDetailProcessing had only two parameters (and did not have the AdditionalParameters parameter). +The context menu of Gantt charts embedded in spreadsheet documents opened on clicking the right mouse button.Eliminated unexpected system behavior. +The behavior of Gantt chart details in spreadsheet document is now standardized.
Charts.
Web client.
If chart properties Adjust series and Adjust points are set to False, series colors or point colors now use the custom color palette in the thin client. This change is not implemented in the web client . +This change is not implemented in 8.3.9 compatibility mode.

+

+

If chart properties Adjust series and Adjust points were set to False, series colors or point colors used the default color palette in the thin client, and the custom color palette in the web client.Eliminated inconsistencies in chart appearance between the web client and thin client.
Charts.
During chart deserialization, if Adjust series or Adjust points property is set to False, series colors or point colors use the custom color palette (they are set once the palette is loaded). +This change is not implemented in 8.3.9 compatibility mode.During chart deserialization, if Adjust series or Adjust points property is set to False, series colors or point colors used the default color palette.Eliminated unexpected system behavior.
Charts.
During interactive chart editing, if Adjust series or Adjust points property is set to False, the following operations are performed:
  • Parameters controlling the appearance of series or points are set to default values
  • The chart is redrawn.

This change is not implemented in 8.3.9 compatibility mode.

During interactive chart editing, parameters controlling appearance of series or points were not set to default values if Adjust series or Adjust points property was set to False.Eliminated unexpected system behavior.
Charts.
If Adjust series or Adjust points chart property is set to False, any attempt to change series properties or point properties for this chart by using 1C:Enterprise script raises an exception. +This change is not implemented in 8.3.9 compatibility mode. +Attempts to change a series or point property for a chart by using 1C:Enterprise script did not raise an exception if Adjust series or Adjust points chart property was set to False. The property was set for series or point instead.Invalid chart use is not allowed now
Common objects.
In a value table generated using the Unload() method of a tabular section of any object, names of predefined columns are generated in 1C:Enterprise script language variant specified in the Script variant configuration property.

This change is not implemented in 8.3.9 compatibility mode.

In a value table generated using the Unload() method of a tabular section of any object, predefined column names could be accessed in the following 1C:Enterprise script language variants:
  • If the resulting value table was not transferred between the client and the server, both English and Russian.
  • If the resulting value table was transferred between the client and the server, English only.
Eliminated unexpected system behavior.
Background and scheduled jobs.
Common attributes / Data separation.
When a background job is started with a uniqueness key specified, the key uniqueness is verified within the area described by the current set of separators. For each unique set of separators, you can run a single background job with a uniqueness key specified.

This change is not implemented in 8.3.9 compatibility mode. +

When a background job was started with a uniqueness key specified, the key uniqueness was verified within the entire infobase, regardless of the separator values.You can run a background job in each unique data area. For example, you can run long calculations in different areas of a separated infobase and avoid conflicts related to duplicate uniqueness keys.
Managed forms.
If the Cancel parameter of OnOpen managed form handler is set to True, once the handler execution is completed, the memory occupied by the form is cleared, all related resources (temporary storage, locks, and so on) are released, and idle handlers are disabled.

This change is not implemented in 8.3.9 compatibility mode.

If the Cancel parameter of OnOpen managed form handler was set to True, once the handler execution was completed, in some scenarios the memory occupied by the form was not cleared. Consequently, all related resources (temporary storage, locks, and so on) were not released, and idle handlers were not disabled.Eliminated unexpected system behavior.
Managed forms.
Implemented the option to apply through alignment (Through alignment property) to managed form groups with United property set to False.

This change is not implemented in 8.3.9 compatibility mode.

For managed form groups with United property set to False, the value of the Through alignment property was ignored.Eliminated unexpected system behavior.
Linux.
System requirements.
1C:Enterprise system requirements for Linux computers are modified. The freetype library is now included in 1C:Enterprise distribution kit and excluded from the list of libraries whose availability is verified at 1C:Enterprise startup.The freetype library was not included in 1C:Enterprise distribution kit. Its availability was verified at 1C:Enterprise startup.The system requirements for Linux computers are simplified.
Managed forms.
If FixingInTable property of a managed form table column group is set to Left or Right, all of the columns belonging to the group are fixed, as well as all other columns with this property set to Left or Right.

This change is not implemented in 8.3.9 compatibility mode.

If FixingInTable property of a managed form table column group was set to Left or Right, only columns to the left or to the right of the group, respectively, were fixed. The columns included in the group were not fixed.Eliminated unexpected system behavior.
Managed forms.
If a managed group form of "command bar" type has GroupVerticalAlign property set to Auto and it belongs to a group or form with ChildItemsVerticalAlign property set to Auto, the command bar is displayed at the top of the parent group (just below the last item).

This change is not implemented in 8.3.9 compatibility mode.

If a managed group form of "command bar" type had GroupVerticalAlign property set to Auto and it belonged to a group or form with ChildItemsVerticalAlign property set to Auto, the command bar was displayed at the bottom of the parent group.Eliminated unexpected system behavior.
Dynamic lists.
In dynamic list search field, values that can be interpreted as numbers in exponential notation are treated as strings (the platform searches for the specified string).

This change is not implemented in 8.3.9 compatibility mode.

In dynamic list search field, values that could be interpreted as numbers in exponential notation were treated as numbers (the platform searched for the number).Eliminated unexpected system behavior.
Data composition system.
The Use property of data parameters that can be edited by users but are disabled by functional options is disabled in the following scenarios:
  • Loading a report option
  • Calling DataCompositionSettingsComposer.Refresh()

This change is not implemented in 8.3.9 compatibility mode.

The Use property of data parameters that were disabled by functional options was disabled in the following scenarios:
  • Loading a report option
  • Calling DataCompositionSettingsComposer.Refresh()
Improved compatibility with data composition system queries created using previous 1C:Enterprise versions.
1C:Enterprise script.
Web client.
In the web client, Title() function only converts strings that contain only Latin characters (A-Z, a-z), numbers, and special characters.

In other client applications and on the server, Title() function behavior remains unchanged: the conversion rules are defined in the Unicode standard.

In the web client, Title() function always returned the source string.Corrected the behavior of Title() function.
System requirements.
Administration.
1C:Enterprise distribution packages for Windows and macOS include HASP Device Driver 7.63.1C:Enterprise distribution packages for Windows and macOS included HASP Device Driver 6.60 or 7.60.1C:Enterprise distribution packages include a later (more secure) version of HASP Device Driver.
Applied objects.
After restructuring a chart of calculation types, the order of lines in tabular sections of predefined calculation types changes.The order of lines in tabular sections of predefined calculation types was different.Changed line order in tabular sections of predefined charts of calculations types. If your application algorithms depend on the line order, we recommend that you eliminate the dependencies.
Add-ins.
System requirements.
The add-in development technology now supports Web Extensions API for Mozilla Firefox. It is recommended that you rebuild add-in distribution packages for Mozilla Firefox with new template projects. The resulting add-ins will be compatible with the same 1C:Enterprise 8 versions as before.

Updated the template project included in the add-in development technology (read more)

The add-in development technology did not support Web Extensions API for Mozilla Firefox.The add-in development technology is adapted to new Mozilla Firefox requirements. Mozilla Firefox versions 57 and later do not support add-ins that use other interfaces rather then Web Extensions API.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Method StrStartWith(). The previous name is now deprecated and supported for compatibility purposes only.
  • StrStartWith().
  • StrStartsWith().
XSL stylesheet loading methods of XSLTransform object.

The previous names are now deprecated and supported for compatibility purposes only.

  • LoadFromString()
  • LoadFromNode()
  • LoadFromFile()
  • LoadXSLStylesheetFromString()
  • LoadXSLStylesheetFromNode()
  • LoadXSLStylesheetFromFile()
Names of debug items used in file infobases.
  • For Web services: Server (file-based variant)
  • For HTTP services: Server (file-based variant)
  • For Web services: Web service
  • For HTTP services: HTTP service
Titles in the sections panel settings dialog box.
  • Available sections
  • Selected commands
  • Available sections: (added trailing character «:»)
  • Selected sections
Changed presentation of spreadsheet document menu commands used for named area display management.
  • Show Named Rows/Columns
  • Show Named Cells
  • Show row and column names
  • Show cell names
Presentations of configuration storage compatibility mode values.
  • Version 8.3.2
  • Version 8.3.3
  • Version 8.3.2 or eralier
  • Versions 8.3.3 - 8.3.5
Property InfoBaseUser.UnsafeActionProtection. The previous name is now deprecated and supported for compatibility purposes only.
  • UnsafeActionProtection.
  • UnsafeOperationProtection.
Object UnsafeActionProtectionDescription. The previous name is now deprecated and supported for compatibility purposes only.
  • UnsafeActionProtectionDescription.
  • UnsafeOperationProtectionDescription.
Property UnsafeActionProtectionDescription.WarnAboutUnsafeActions. The previous name is now deprecated and supported for compatibility purposes only.
  • WarnAboutUnsafeActions.
  • UnsafeOperationWarnings.
The system enumeration that defines the height of a managed form table is renamed. The previous name is now deprecated and supported for compatibility purposes only.
  • HeightControlVariant.
  • ItemHeightControlVariant.

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Mobile device-specific features.
Implemented the following location features:
  • Selecting a location provider either from the global list of providers, or from the list of providers available now
  • Checking if location service is enabled
  • Geofence management

Implemented the Geofence object. Implemented LocationRelativeToGeofence system enumeration. Implemented LocationProviderInformation.Available property. Implemented AvailableOnly parameter for the following methods of LocationTools object: GetProviders(), GetProvider(), GetMostAccurateProvider(), and GetMostPowerSavingProvider(). For LocationTools object , implemented methods: LocationDataUseEnabled(), AttachProvidersAvailabilityChangeHandler(), DetachProvidersAvailabilityChangeHandler(), EnableGeofencesMonitoring(), GetMonitoredGeofences(), GetMonitoredGeofence(), DisableGeofencesMonitoring(), DisableAllGeofencesMonitoring(), and AttachMonitoredGeofencesBordersCrossingDetectionHandler().

These features were not provided.Location management capabilities are now expanded. For example, predefined actions can be performed when a mobile device reaches a specific location.
Binary data.
Implemented binary data management capabilities for the mobile platform.This feature was not provided. Binary data management capabilities were only available for the PC platform.Binary data management capabilities are now implemented for the mobile platform.
Internet-enabled functionality.
Implemented check whether a mobile device is in roaming mode. The Internet connection change handler is called when the roaming mode status is changed. +Implemented method InternetConnectionInformation.GetRoamingUsage().Check whether a mobile device is in roaming mode was not implemented.A variety of actions can be performed when roaming mode is enabled on a mobile device. For example, access to mobile Internet can be restricted or prohibited due to high Internet charges in roaming.
Internet-enabled functionality.
For mobile platforms running on Windows, implemented secured connection management capabilities.Secured connection management capabilities were not available for mobile platforms running on Windows.Mobile platforms running on Windows can now access resources that require secured connection.
Cryptography support.
Implemented encryption operations for the mobile platform. The mobile platform behavior is identical to that of the thin client. Details of the encryption operations are described in the documentation. +Implemented CryptoManager.ShowCertificateList() method. Implemented CryptoKeysContainer object. Changed behavior of the following methods of CryptoCertificateStore object on the mobile platform: Add(), Delete(), BeginAdding(), and BeginDeleting().Encryption operations were not implemented for the mobile platform.On the mobile platform, you can implement a check whether a document stored locally was modified. Sensitive data and documents can now be securely sent through open channels thanks to encryption capabilities.
Mobile device-specific features.
For the mobile platform, implemented a check whether contacts and calendars can be added or edited. +For ContactManager object, implemented methods ContactEditingSupported() and ContactsAddingSupported(). +For CalendarsManager object, implemented methods CalendarEditingSupported() and CalendarsAddingSupported(). +The CalendarManager.CalendarEditingSupported property is now deprecated and supported for compatibility purposes only. +For 1C:Enterprise applications running on Windows, the CalendarManager.EventEditingSupported() method always returns False.The check whether contacts can be added or edited was not implemented. +The check whether calendars can be added or edited was implemented in a different way.Unified contacts and calendar management as related to adding and editing objects.
Mobile device-specific features.
Implemented new configuration permission: Ads. This permission is only used by the mobile application builder when selecting a mobile platform version for iOS to be used in the builds. If the Ads permission is used in the configuration export file, The app uses ads check box is unavailable in the mobile configuration form of the mobile application builder.The permission specifying that ads are allowed for a mobile application was not implemented in the configuration. Instead, The app uses ads check box in the mobile application builder was used for this purpose.Now the mobile application builder can be forced to use an advertisement-enabled mobile platform version for iOS in the builds.
File operations.
For the mobile platform, implemented getting thumbnails for pictures and video files stored in the corresponding libraries of the mobile device. This feature requires the file path to start with content: schema. +For File object , implemented methods GetMobileDeviceLibraryFileThumbnail() and BeginGetMobileDeviceLibraryFileThumbnail().This feature was not provided.

It was possible to fully load a picture or video file into memory when a thumbnail could be used instead

Optimized mobile device memory use when loading pictures or video files from the corresponding libraries of the mobile device. Reduced risk of insufficient memory error for mobile applications that load a large number of pictures or video files from the corresponding libraries of the mobile device.
Managed locks.
Implemented data lock management for mobile platforms. +Implemented global context methods LockDataForEdit(), UnlockDataForEdit(), SetLockWaitTime(), and GetLockWaitTime(). +Implemented methods IsLocked(), Lock(), and Unlock() for objects CatalogObject, DocumentObject, and ExchangePlanObject. +Implemented method AccumulationRegisterRecordSet.LockForUpdate(). +Implemented method ManagedForm.LockFormDataForEdit(). +Implemented DataLock and DataLockItem objects. +For Document, Catalog, and ExchangePlan configuration objects, implemented the DataLockFields property. For Configuration, Document, Catalog, ExchangePlan, Constant, Sequence, AccumulationRegister, and InformationRegister configuration objects, implemented DataLockControlMode property.Managed lock support was not provided on the mobile platform.Object lock management during background job execution on the mobile platform is now available.
File operations.
Implemented getting a file mask that describes all files, as well as getting a file path separator character, regardless of the mobile operating system where 1C:Enterprise is running. +Implemented methods GetAllFilesMask(), GetClientAllFilesMask(), GetServerAllFilesMask(), GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator(). +Implemented method BeginGettingMobileDeviceLibraryDir().Getting a file mask that describes all files and getting a file path separator character regardless of the mobile operating system used was not supported.File operations in mobile applications are nearly operating system-agnostic now.
System requirements.
Implemented Android 7.0 support. Implemented multiwindow mode for Android 7.0. +For Android versions 6.0 or earlier:
  • Introduced a new API for operations with the mobile device camera
  • Implemented dynamic resolutions
Multiwindow mode was not supported for Android 7.0. Dynamic resolutions were not supported for Android versions 6.0 or earlier. Dynamic resolution management was not supported for Android versions 6.0 or earlier. Improved support of Android versions 6.0 and earlier.
Mobile device-specific features.
Implemented barcode scanning capability for mobile devices running Windows 10. Barcode scanning is not supported for mobile devices running Windows 8.1 or earlier. +For devices running Windows 10, implemented availability of MultimediaTools.ShowBarcodeScanning() method, while MultimediaTools.BarcodeScanningSupported() method returns a value specifying whether barcode scanning functionality is available. +For successful barcode scanning, continuous auto focus mode must be supported for the primary device camera.Barcode scanning was not supported for mobile devices running Windows.Expanded mobile platform capabilities for devices running Windows 10.
Managed forms.
For the mobile platform, implemented form field extension for the calendar field. The form field extension for the calendar field does not support dragging. +This feature was not provided. Expanded Data type data management capabilities for mobile platform forms.
Print tools.
Printing is now supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64).Printing was not supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64).Extended mobile application capabilities on Windows.
Mobile applications.
Hardware rendering support is implemented for user interface on Android devices.This feature was not provided.Improved performance of user interface generation on Android devices.
Mobile application builder.
In the mobile application builder, automatic deletion of obsolete data is implemented. Obsolete data is defined as mobile application builds and mobile platforms that were last changed (or imported) before a specific date. This date is calculated as follows: current date minus the specified number of days (the gap size). You can specify custom gaps for mobile application builds and mobile platforms.

Default values:

  • 90 days for mobile application builds
  • 180 days for mobile platform files

If you set the gap size to 0, obsolete objects are never deleted.

When you attempt to use an obsolete object, the mobile application builder prompts you to rebuild the mobile application or reimport the mobile platform.

+

The mobile application builder did not provide tools for automatic deletion of obsolete objects.You have the option to keep the size of the mobile application builder infobase within reasonable limits, avoiding significant growth of the disk space occupied by this infobase.
Mobile application builder.
The requirements to Android SDK components used to build mobile applications are defined by the requirements of the mobile platform version used to build the applications.

The builder uses the latest Android API Level available on the computer, provided that the API Level meets the mobile platform requirements. The requirements to other Android SDK components are defined by Android API Level requirements.

If the mobile platform was loaded in a previous builder version, the builder requires Android API Level version 24 or later.

The following Android SDK components were required to build mobile applications for Android:
  • Android API Level version 23 or later
  • Android Tools version 20.0.3 or later
  • Android Platform Tools version 14 or later
  • Android Build Tools version 19.0.0 or later

These requirements were applied regardless of the mobile platform versions used to build mobile applications. They were hardcoded in the mobile application builder.

The requirements to mobile application build infrastructure for Android are defined by the mobile platform version, instead of the requirements hardcoded in the mobile application builder.
Mobile application builder.
In mobile application builder, Gradle tool now can be used to build mobile applications. On Android SDK version 26 or later, you can build mobile applications using no other tools besides Gradle.

You can specify two Android SDK paths in the builder settings: one for version 25 or ealier and the other one for version 26 or later. Therefore, you can build mobile applications that require any specific Android SDK version.

Building with Gradle requires Java 8 on the computer that runs mobile application builder. It does not require Apache Ant.

Mobile application builder did not support building mobile applications with Gradle tool.Building mobile applications that use new Android SDK versions is now available.
Mobile applications.
Since mobile platform version 8.3.10.71, only building mobile applications with Gradle tool is supported. Use mobile application builder provided as a part of the mobile platform distribution package to build mobile applications.

Since mobile platform version 8.3.10.71, Apache Ant is not required for building mobile applications.

Mobile platform versions earlier that 8.3.10.71 did not support Gradle. Building the mobile platform required Apache Ant.The mobile application building procedure is modified to comply with the changes in the recommended application building procedure for Android.
System requirements.
Mobile application builder.
In the mobile platform, implemented iOS 11 support.

Extended graphical asset collection for mobile applications that run on iOS 11.

The mobile application builder supports the new graphical asset collection and building applications for iOS 11.

The mobile platform did not support iOS 11.Implemented support of the latest operation system for Apple devices.
Error handling.
In the event of unexpected shutdown of a mobile application on Android, 1C:Enterprise displays a dialog box with a detailed error description, with the option to copy the error description to the clipboard.In the event of unexpected shutdown of a mobile application on Android, no error details were displayed.Simplified diagnostics of unexpected shutdown causes. Applications users can send error details to mobile application developers.
Interface.
Mobile platform.
A spreadsheet document now supports the Output right on a mobile device. If the Output right is disabled, the following functions are not available: copying to clipboard, printing and saving the displayed data.A spreadsheet document did not support the Output right on a mobile device. The following functions were always available: copying to clipboard, printing and saving the displayed data.Eliminated unexpected system behavior.

Table of contents

Library updates + +

Table of contents

Transition from the previous version to the version 8.3.10

Table of contents

Version 8.3.9

Version 8.3.9 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.8 is added to the list of available values of the Compatibility mode property.Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, 8.3.6, and 8.3.7.In version 8.3.9 you can run configurations created in version 8.3.8 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.9 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also gives you the option to use version 8.3.8 for working with the infobase even after the transition to version 8.3.9. You can use this option both before and after removing the compatibility mode (in the latter case you have to turn the compatibility mode back on).
Configuration extensions.
1C:Enterprise script.
In configuration extensions, the option to adopt the following objects is implemented:
  • Common modules
  • Object modules for all object types
  • Manager modules for all object types
  • Session module
  • Managed application module
  • External connection module
  • Command modules

The option to adopt ordinary form modules and ordinary application modules is not available.Therefore, you can adopt any module except for modules that are used solely in ordinary applications.

The following operations are now available:

  • Call any methods of the extended module from the extending module
  • Add event handlers to adopted modules of abovementioned types

Export methods and variables of the extended module form the uniform context of the extended module.

Adopted form modules are now handled differently.

You have the option to allow or deny extending all modules of abovementioned types (the all module extensions security profile property). You have the option to provide a list of modules where extension is allowed (the Modules available for extension property) or where extension is denied (the Modules not available for extension property).

You have the option to create common modules in configuration extensions.

For ISecurityProfile object, the following properties are implemented: AllModulesExtension, ModulesAvailableForExtension, and ModulesNotAvailableForExtension (software administration of server clusters based on COM objects).

For ISecurityProfile interface, the following methods are implemented: getAllModulesExtension(), setAllModulesExtension(), getModulesAvailableForExtension(), setModulesAvailableForExtension(), getModulesNotAvailableForExtension(), and setModulesNotAvailableForExtension() (Java interface for server administration).

In the server cluster command-line utility (rac), for the profile command, the following parameters are implemented: all-modules-extension, modules-available-for-extension, and modules-not-available-for-extension.

The option to adopt modules was not available, except for form modules. The option to create common modules in configuration extensions was not available.

Adopted form modules were handled differently.

The option to specify which modules can be extended was not available.

The configuration extensions feature now provides the option to extend all 1C:Enterprise script modules, except for those used solely in ordinary applications.

New security profile options related to configuration extensions.

Web services and HTTP services.
OData interface.
Configuration extensions.
Server clusters.
The option to manage session lifetime when using Internet services and the standard OData interface is implemented:
  • Automatic reuse of the current session when a new request comes from the same user.
  • Session lifetime management using HTTP request headers.

For web services and HTTP services, the ReuseSessions and SessionMaxAge properties are implemented. If a web service or HTTP service is a native configuration extension object, these properties are read-only.

The following additions to the default.vrd file are implemented:

  • <standardOData> element, which is subordinate to <point> element.
  • reuseSessions, sessionMaxAge, poolTimeout, and poolSize attributes for <point> and <service> elements.

The enableStandardOData attribute of the <point> element is deprecated.

If a web service or an HTTP service is a native configuration extension object and it is either not published in the default.vrd file or published without the session reuse option, session reuses are not available for that service.

A server cluster service that manages the automatic pool of reused sessions is implemented. The service name is SessionReuseService (Session reuse service).

This feature was not provided. A new session was created for each Internet service call and each standard OData interface query.Improved performance of Internet services and the standard OData interface.
Formatted documents.
The behavior of the Tab key is changed:
  • If a text is selected or the cursor is located at the beginning of a paragraph, pressing Tab increases the indent.
  • Otherwise pressing Tab adds a tab character.

The FormattedDocumentBookmark object is linked to a character within a paragraph, not to a character position. If a text is changed, the bookmark position better matches its original position.

Pressing Tab always increased the indent. The FormattedDocumentBookmark object was linked to a character position within a paragraph.Formatted document behavior better meets user expectations.
Binary data.
Tools for operations with binary data are implemented. They provide the following options:
  • Specifying byte order
  • Operations with memory buffer that stores binary data
  • File operations where files are treated as binary data
  • Byte-by-byte data access
  • Reading and writing some data types (String and Number).

The following objects are implemented: BinaryDataBuffer, Stream, FileStream, MemoryStream, DataReader, DataWriter, ReadDataResult, FileStreamsManager. +The BinaryData.Size() method is now available in the web client.

For the BinaryData.Write() method, the option to write data to a stream is implemented.

The OpenStreamForRead() method is implemented, it opens a stream for reading binary data specified in the BinaryData object.

These options were not provided. The only available options were reading files from disk and writing files to disk without any means to perform any other operations with those files.Extented capabilities for operations with binary data.
Pictures.
Support of vector images in SVG format is implemented. The PictureFormat.SVG system enumeration value is implemented. The picture editor in Designer does not support editing pictures that have SVG format. The specifics of SVG format support are described in the documentation.This feature was not provided.Extended list of supported picture formats. You have the option to use scalable pictures that can be displayed in areas of any size.
Administration tools.
For the /regserver client application command-line option (registration of COM objects), the following optional parameters are implemented:
  • -AllUsers. Perform registration for all computer users.
  • -CurrentUser. Perform registration for the current user.
  • -Auto. Automatically select registration mode based on the user rights, without displaying any questions.

The behavior of the /regserver option without parameters is not changed.

When a client application was started with the /regserver command-line option (registration of COM objects), it attempted to perform the registration for all users. If the current user did not have the rights for this, they were prompted to confirm the registration for the current user.Simpler usage of the /regserver command-line option in 1C:Enterprise batch startup mode.
XML and XDTO support.
Support of Canonical XML 1.1 specification is implemented.

The ConversionToCanonicalXML object is implemented. For the XMLCanonicalizationType system enumeration, the following values are implemented: XMLCanonicalization1_1 and XMLCanonicalization1_1WithComments.

The XMLCanonicalizingWriter and DOMCanonicalization objects are deprecated. These objects do not support Canonical XML 1.1 specification.

Only Canonical XML 1.0 specification was supported.Extended capabilities for integration with third-party systems.
DBMS operations.
Administration tools.
The option to attempt the restoration of database structure from Designer batch mode command line is implemented. The /IBRestoreIntegrity Designer command-line option is implemented.

Running Designer with the /IBRestoreIntegrity parameter is recommended if a previous database configuration update (performed either interactively or in batch mode) have not been completed successfully because of unexpected Designer shutdown or power outage.

This feature was not provided.Improved infobase fault tolerance in scenarios that include database configuration update.
Predefined data.
Event log.
Recording events related to predefined data restructuring to the event log is implemented. This includes the following events:
  • Infobase.Set predefined data update
  • Infobase.Predefined data update
  • Data.Set predefined data initialization
  • Data.Initialize predefined data
  • Data.Add predefined data
  • Data.Modify predefined data
  • Data.Delete predefined data
  • Data.Initialize predefined data, data not found
This feature was not provided.Simplified diagnostics of predefined data issues.
Spreadsheet documents.
The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format includes the export of pictures stored in spreadsheet document cells.

This change is not implemented in 8.3.8 compatibility mode.

The export of spreadsheet documents to Microsoft Office OpenXML (Microsoft Word 2007- 2010) format did not include the export of pictures stored in spreadsheet document cells.Spreadsheet documents exported to Microsoft Word better match the original spreadsheet documents.
Internet-enabled functionality.
The following algorithms can be used together with TLS protocol: GOST R 34.10-2001, GOST R 34.10-94, GOST R 34.11-94, and GOST 28147-89.

GOST R 34.10-2012 and GOST R 34.11-2012 algorithms are not supported.

This feature was not provided.Internet services that use the listed GOST algorithms together with TLS protocol are now supported.
OData interface.
For the standard OData interface, the option to get the following data is implemented:
  • Predefined data item flag and name.
  • Data attribute presentations. The ____Presentation field name suffix is used for getting presentations. Presentation fields are only available for use in the $select operator and only if you specify them explicitly.
  • Specific attributes of tabular sections or record sets (in the $select operator).
These features were not provided.Extended capabilities of the standard OData interface.
OData interface.
For queries to the standard OData interface, support of the $expand operator is implemented. This gives you the option to include referenced entities in the response body.This feature was not provided.The option to get values of referenced entities together with the main query result is implemented, which eliminates the need to use a separate query for each referenced entity.
Dynamic lists.
The following changes are made in the dynamic list query builder:
  • The option to edit batch queries is implemented (the Query batch wizard page).
  • Specifying the number of selected records is not supported but disabling this query option is supported.
  • When the query builder is closed, it checks the query for the TOP keyword and, if the keyword is present, reports that.

This change is not implemented in 8.3.8 compatibility mode.

The dynamic list query builder did not provide the option to edit batch queries. The option to specify the number of selected records was available but this number was never used.The option to edit query batches using the dynamic list query builder is implemented. Better error diagnostics for dynamic list queries.
Configuration extensions.
The option to change access rights (including data access restrictions) in adopted roles is implemented.

The option to add roles to configuration extensions is implemented, this requires the use of 1C:Enterprise script. In Designer, the only operation available for such roles is deletion.

The option to apply data access restirictions added in a configuration extension to the resulting configuration is implemented through the use of security profiles (the access rights extension property).

For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the technology of programmatic cluster administration based on COM objects).

For the ISecurityProfile object, the RightExtension and RightExtensionDefinitionRoles properties are implemented (for the Java administration server interface).

For the server cluster command-line utility (rac), the right-extension and right-extension-definition-roles parameters of the profile command are implemented.

In configuration extensions, only the option to set access rights for native extension objects in adopted roles was available. The option to change rights in adopted roles was not available.Significant improvements for access right management in configuration extensions.
Configuration extensions.
Development tools.
The following options to check the applicability of a configuration extension without running an applied solution with this extension are implemented:
  • The Check applicability command in the Configuration extensions window
  • 1C:Enterprise script methods
  • Designer batch mode option

When a client application is started, extension compatibility issues are no longer displayed in the message window. Instead, they are added to the information for technical support (which is available from the About 1C:Enterprise window). If any compatibility issues are encountered, a warning dialog box is also displayed, with a link to the full list of issues.

For the ConfigurationExtensions object, the CheckCanApplyAll() and GetSessionApplicationIssuesInformation() methods are implemented. For the ConfigurationExtension object, the CheckCanApply() method is implemented.

For Designer batch mode, the /CheckCanApplyConfigurationExtensions command-line option is implemented.

For the Configuration extension management standard function, the Check applicability when adding and loading extensions check box is implemented.

These features were not provided.

When an extension was attached, the diagnostics messages were displayed in the message window.

Improved diagnostics for configuration extension attachment issues. The option to automate the diagnostics by running them in the batch mode is implemented.
Event log.
When the event log is exported to an XML file, the state of predefined data update is exported as the value of the Data field.

The PredefinedDataUpdate system enumeration is now available in the thin and web clients.

This feature was not provided.The event log export to an XML file is adjusted to reflect the new events.
Localization.
The French localization of the client applications is available.This feature was not provided.1C:Enterprise is available to French-speaking users.
Localization.
The Hungarian localization of the client applications is available.This feature was not provided.The Hungarian platform interface is available. 1C:Enterprise is available to Hungarian-speaking users.
Configuration extensions.
Development tools.
The ConfigurationExtensionsManager.ExecuteBackgroundJobWithoutExtensions() method is implemented. It runs a background job without extensions (configuration extensions available in the database are not applied in the background job session).

For all metadata objects, the ChangedByConfigurationExtensions() method is implemented. It defines whether a configuration object is available in the current session.

This feature was not provided.Simplified 1C:Enterprise script-based operations with configuration extensions.
DBMS operations.
System requirements.
Microsoft SQL Server 2016 DBMS is now supported (including its Linux version).Microsoft SQL Server 2016 DBMS was not supported.Microsoft SQL Server 2016 DBMS is now supported.
Client application.
System requirements.
A 64-bit client application for Windows is implemented. It includes the thin client (also available as a standalone distribution kit), the thick client, and Designer. The current client application status is beta.

When you start a client application, the 32-bit version has priority because most of the add-ins are not yet available for the 64-bit version of 1C:Enteprise platform. Automatic client application updates also install 32-bit versions (provided that the 32-bit versions are available in the distribution kit directories). +The 64-bit client installer is similar to the 32-bit client installer.

We recommend that you do not install both 64-bit 1C:Enterprise server and applications from the full 64-bit 1C:Enterprise distribution kit on a single computer.

Only 32-bit versions of Windows client applications (including Designer) were available.

1C:Enterprise server was the only 1C:Enterprise component that had a 64-bit version.

Support of 64-bit Windows versions is implemented.

Issues caused by insufficient memory for operations with large configurations (such as comparing and merging configurations) are eliminated.

Accounting registers.
Database operations.
Before you start infobase verification and repair in the interactive mode, 1C:Enterprise displays a recommendation to create an infobase backup.

Infobase restructuring and infobase verification and repair now include a check for the following: the table of accounting register extra dimension values contains records that do not have matching records in the main accounting register table (lost extra dimensions). During the repair, lost extra dimensions are deleted from the table of accounting register extra dimension values if the following conditions are met: +

  • The Verify and repair mode is selected.
  • The Check logical infobase integrity option is selected.

During the restructuring, the check is performed if any of the following entities change:

  • The totals splitting flag
  • The set of recorders
  • The maximum number of extra dimensions
  • The type of characteristic value in a chart of characteristic types that is used to specify extra dimensions for a chart of accounts.

If lost extra dimensions are found during the restructuring, the restructuring is stopped and 1C:Enterprise displays a recommendation to perform infobase verification and repair.

The check for lost extra dimensions during the infobase verification and repair is implemented. If extra dimensions are lost, it is recommended that you restore the infobase from a backup. The check is performed if the following conditions are met:

  • The Verify and repair mode is selected.
  • The following options are selected: Check logical infobase integrity, Check referential infobase integrity, Recalculate totals, and Restructure infobase tables.
The diagnostics of extra dimension inconsistencies was insufficient.Diagnostics and repair of accounting register logical integrity issues that can result in data losses is implemented.
Administration tools.
The rules for generation of application and shortcut names displayed in the Windows Start menu are modified. The new name template is Application name (full version number).

In Windows version 8 or later, the 1C:Enterprise 8 folder contains all installed applications (and shortcuts) with their version numbers.

In Windows version 7 or earlier, the 1C:Enterprise 8 folder contains folders for each version number. Each of these folders contains all installed applications (and shortcuts) for a specific version, with their names generated according to the abovementioned rule.

The names of installed applications (and shortcuts) did not include the full system version number.Simplified navigation in the Start menu on Windows version 8 and later. Application names now contain full version numbers.
Accounting registers.
Dumping configurations to files/Restoring configurations from files.
The option to create an accounting register record that only affects the opening balance of a single period and does not affect the closing balance of the previous period is implemented. The implementation is based on the new "period adjustment" concept. A period adjustment is a number that represents the number of time intervals within a single second. The maximum number of intervals is 1000. If a record belongs to any period adjustment interval, the record does not affect the closing balance of a period but affects the opening balance of the next period and does not affect the turnovers of both periods. A register record that belongs to a period adjustment interval only affects turnovers if the turnover period includes the entire point in time of that register record. Now the point in time can inlcude not only the date, time, and recorder, but also a period adjustment.

For the accounting register configuration object, the Period adjustment length property is implemented. If this property is set to 0, the register does not use period adjustments.

The PeriodAdjustment property is implemented for AccountingRegisterRecord and AccountingRegisterSelection objects. This property is also available in the main accounting register table, the extra dimensions table, and the virtual table of register records with extra dimensions.

The PeriodAdjustment value is implemented for the Periodicity parameter of the following virtual tables of accounting registers: Turnovers, DrCrTurnovers, and BalanceAndTurnovers.

The PointInTimeWithPeriodAdjustment object is implemented.

The XML dump format version is changed.

If a configuration contains at least one accounting register with period adjustment enabled (the value of the Period adjustment length property is not 0), this makes the infobase incompatible with the earlier 1C:Enterprise versions, including earlier builds of 1C:Enterprise 8.3.9. When you attempt to open such an infobase with 1C:Enterprise version 8.3.9.2015 or earlier, 1C:Enterprise displays the message Configuration structure is incompatible with the current program version and shuts down.

To restore the compatibility, you have to delete all of the accounting registers with period adjustment, or set their Period adjustment length to 0.

This feature was not provided.

The option to create an accounting register record that only affected the opening balance of a single period and did not affect the closing balance of the previous period was not available.

You can implement certain operations related to opening balance corrections at period boundaries.
DBMS operations.
System requirements.
Support of Oracle Database version 11.2.0.4 (Windows) is implemented.This Oracle Database version was not supported.Extended list of supported Oracle Database versions.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Client application.
All of the common report forms use the following help topic priorities:
  • Report help
  • Form help
  • Report form help provided by the platform

This change is not implemented in 8.3.8 compatibility mode.

Common report froms used the following help topic priorities:
  • Form help
  • Report help
  • Report form help provided by the platform
Help topics are displayed in more logical order.
Interface.
Client application.
For thin client running on Windows operating system, touch screen support is implemented.

Support of scrolling with 2-finger gestures in all directions is implemented for all controls that have scroll bars.

The effect of 1-finger gestures depends on control type:

  • Horizontal gesture:
    • Scrolling in spreadsheet documents, tables, or forms
    • Selection in text documents, multiline text boxes, formatted documents, planner fields, and HTML document fields
    • Selection or dragging in graphical and geographical schemas
  • Vertical gesture:
    • Selection or dragging in geographical schemаs
    • Scrolling in other form controls that support vertical scrolling

The tap detection area is expanded for the following controls:

  • Check boxes in form tables
  • Buttons that expand or collapse tree branches in form tables
  • Buttons that move through hierarchical lists in form tables
  • Hyperlinks in command bars
  • Buttons with hidden borders
  • Cells in form field extensions for period fields

For graphical schemas, support of scaling using the scaling gesture is implemented.

For tapping form buttons and command bar buttons, a visual effect is implemented.

The touch screen support was limited.Improved 1C:Enterprise usability for touch monitors.
Spreadsheet documents.
In spreadsheet documents, if a search string can be converted to a number, 1C:Enterprise determines the number of digits in that number. Then it searches exactly for the specified number, without further simplifications or conversions. The search does not ignore strings with leading zeros.

This change is not implemented in 8.3.8 compatibility mode.

In spreadsheet documents, for searches by number, 1C:Enterprise did not determine the number of digits in that number. Strings with leading zeros were not converted to numbers.Better algorithm for searching spreadsheet documents for numeric values.
Web client.
File system extension and cryptography extension are compatible with Mozilla Firefox version 51 and later. The extensions are automatically updated first time they are accessed (after the platform update).File system extension and cryptography extension were not compatible with Mozilla Firefox version 51 and later.Eliminated unexpected system behavior.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Development tools.
The performance of the following Designer operations is improved:
  • Module check
  • Configuration check
The performance of module and configuration checks was insufficient.Improved usability for developers of large applied solutions.
1C:Enterprise script.
The performance of 1C:Enterprise script execution is slightly improved in the thin and thick client applications.The performance of 1C:Enterprise script execution in client applications was insufficient.Improved performance of 1C:Enterprise script execution in the thin and thick client applications.
Common objects.
The performance of updating value table column cells in columns that are not a part of any value table index is improved.Redundant rebuilding of value table indexes was performed in the event of updating a cell in a column that was not a part of any value table index.Improved performance for bulk value changes in columns that are not part of any value table index.
Data exchange.
Server clusters.
The following operations that are performed during the creation of an initial infobase image in client/server mode are optimized: reading accumulation register and information register record sets, and reading calculation register record sets that do not feature action period.

The time required to create an initial image of a client/server infobase is significantly reduced.

The performance of creation of an initial image in a client/server infobase was insufficient.Improved performance of infobase preparation for new distributed infobase nodes.
Command interface.
Development tools.
Improved performance of opening the configuration command interface editor form.The performance of opening the configuration command interface editor form was insufficient.Better usability of editing the configuration command inerface.
DBMS operations.
Server clusters.
The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS is modified. This reduces PostgreSQL memory usage.

If a 1C:Enterprise server cluster connection to PostgreSQL DBMS is idle for 30 minutes, it is released.

The algorithm of 1C:Enteprise server cluster operations with PostgreSQL DBMS caused increased PostgreSQL memory usage.

1C:Enterprise server cluster did not release idle connections to PostgreSQL DBMS.

+

Reduced PostgreSQL memory usage for operations with 1C:Enterprise server cluster.
Development tools.
Infobase configuration update is optimized. Configuration comparison in scenarios where objects are mapped by their names is optimized.The performance of infobase configuration update was insufficient.Improved performance of configuration updates.
DBMS operations.
Temporary table operations are optimized in scenarios that use PostgreSQL DBMS.The performance of temporary table operations in scenarios that used PostgreSQL DBMS was insufficient.Improved performance in multiuser mode in scenarios that use PostgreSQL.
Web services and HTTP services.
Sending large files (tens and hundreds of megabytes) over HTTP services is optimized.The performance of sending large files (tens and hundreds of megabytes) over HTTP services was insufficient.Improved performance of sending large files over HTTP services.
DBMS operations.
Optimized temporary table operations in scenarios that use Microsoft SQL Server and include high load on 1C:Enterprise and active usage of temporary tables. Pauses during the closing of DBMS connections are eliminated.The performance of temporary table operations in scenarios that used Microsoft SQL Server and included high load on 1C:Enterprise and active usage of temporary tables was insufficient.Improved performance in multiuser mode in scenarios that use Microsoft SQL Server.

+

DBMS operations.
In the file mode, queries are optimized for scenarios where an applied solution has separators but actually contains a single data area.

To apply this optimization to an existing infobase, perform infobase verification and repair with the Reindex infobase tables check box selected. Once the restructuring is completed, the optimization is applied to all restructured objects.

In the file mode, in scenarios where an applied solution had separators but actually contained a single data area, the performance of queries was insufficient.Improved file infobase performance in scenarios where an applied solution has separators but actually contains a single data area.
Development tools.
Command interface.
Reduced time of displaying changes in configuration objects that affect the configuration command interface. Such changes cause the immediate update of the active form editor, while other form editors are updated when they are activated.Changes in configuration objects that affected the configuration command interface caused the update of all open form editors.Improved Designer performance during the update of properties of configuration objects that affect the command interface.
Formatted documents.
The performance of formatted documents is improved.The performance of formatted documents was insufficient.Improved performance of operations with large texts.
Managed locks.
Absorption of managed locks is implemented (when two managed locks are applied at the same time, only one will take effect). A lock that does not have all lock areas specified absorbs a lock that has more lock areas specified, provided that the values in their common areas match.

If lock escalation causes a conflict with other locks, the escalation is not performed and an attempt to set the requested lock is made instead. This can lead to a total of more than 100 000 locks in a single area.

In scenarios where a single transaction uses a large number of managed locks with slight differences (for example, a single dimension varies), it is recommended that you set a single managed lock where the value of that dimension is not set.

Lock absorption was not performed. If lock escalation caused a conflict with other locks, the transaction that attempted to escalate the lock was canceled.Reduced number of locks and reduced amount of memory used by the cluster manager.

Improved system reliability in scenarios with large numbers of simultaneous locks.

DBMS operations.
Calculation registers.
When deleting records belonging to the actual action period, recording of register sets of calculation registers that support actual action period is performed within several queries, which reduces the chance of escalating the lock to the table level. This does not increase the record set execution time.When deleting records belonging to the actual action period, recording of register sets of calculation registers that supported actual action period was performed within a single query, which could cause lock escalation to the table level.Reduced chance of table lock, which gives more options for performing parallel operations.
Calculation registers.
The index of the actual action period table of a calculation register is complemented by the start date and end date fields, and the index is now clustered. This reduces the chance of lock escalation to the table level when writing record sets of calculation registers that support action period.

For the chart of calculation types table that stores serial numbers of calculation type displacements, a nonunique index by displacement number is implemented. As a result, simultaneous editing of a single chart of calculation types in different data areas of a separated infobase never requires waiting for lock releases.

To apply this optimization to existing infobases, perform the infobase verification and repair operation with the Restructure infobase tables option selected.

+

The index of the actual action period table of a calculation register did not include the start date and end date fields, and the index was not clustered.

For the chart of calculation types table that stored serial numbers of calculation type displacements, a nonunique index by displacement number was not available.

Improved calculation register performance in large and separated databases.

In large databases and especially separated databases, reduced number of table-level locks for the following tables: actual action period table of a calculation register and table that stores serial numbers of calculation type displacements. +

Managed forms.
Development tools.
The first opening of managed form editor in Designer is faster.The first opening of managed form editor in Designer took significant time.Reduced waiting time in managed form development.
Information registers.
Faster writing of information register record sets that have slice first or slice last options enabled.

Faster execution of SliceFirst() and SliceLast() information register manager methods.

The performance of writing information register record sets that had slice first or slice last options enabled and the performance of SliceFirst() and SliceLast() information register manager methods was insufficient.Improved performance of information registers with slice first or slice last options enabled.
Interface.
Managed forms.
Functional options.
The performance of RefreshInterface(), SetInterfaceFunctionalOptionParameters(), and SetFormFunctionalOptionParameters() methods is improved. Delays introduced by these methods in applications with multiple simultaneous user connections are eliminated.The performance of RefreshInterface(), SetInterfaceFunctionalOptionParameters(), and SetFormFunctionalOptionParameters() methods was insufficient. The performance was reduced in applications that called these methods in scenarios with multiple simultaneous user connections.Streamlined operations in applications that use functional options.
Managed forms.
Mobile applications.
In the mobile platform, the performance of operations with large spreadsheet documents is improved.In the mobile platform, the performance of operations with large spreadsheet documents was insufficient.Improved performance of operations with large spreadsheet documents on mobile devices.
DBMS operations.
The performance degradation of Microsoft SQL Server 2014 caused by interaction between 1C:Enterprise server and Microsoft SQL Server 2014 is eliminated. 1C:Enterprise server now forces setting TRACE FLAG 4199 for each Microsoft SQL Server 2014 connection. To be able to set the flag, the account that the 1C:Enterprise server uses to connect to the DMBS must have administrator rights.

If TRACE FLAG 4199 is set for the entire database, 1C:Enterprise server does not set it for each connection.

In some scenarions interaction between 1C:Enterprise server and Microsoft SQL Server 2014 reduced Microsoft SQL Server 2014 performance. 1C:Enteprise server did not force setting TRACE FLAG 4199 and did not check whether this flag was set for the entire database.In some scenarions the performance of operations involving Microsoft SQL Server 2014 is improved.
DBMS operations.
For PostgreSQL, reduced the overhead expenses for processing temporary tables.For PostgreSQL, processing temporary tables took a lot of time.For PostgreSQL, improved the performance of transactions that actively use temporary tables.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Internet-enabled functionality.
The option to choose FTPES for communication with FTP servers is implemented. For the constructor of the FTPConnection object, the SecureConnectionLevel property is implemented. This property defines the secure connection requirements to the FTP server.

If the parameters of the FTPConnection constructor do not have the required types, an exception is thrown. This change is not implemented in 8.3.8 compatibility mode.

All FTP server operations were performed over FTPS.

If the parameters of the FTPConnection constructor did not have the required types, an attempt to convert them to the required types was performed.

Extended secure connection management capabilities for FTP server operations.
Managed forms.
Clicking a managed form table cell that displays a picture with a hyperlink (the CellHyperlink property is set to True) calls the Selection event of the form table.

This change is not implemented in 8.3.8 compatibility mode.

Clicking a managed form table cell that displayed a picture with a hyperlink (the CellHyperlink property was set to True) did not call the Selection event of the form table.Eliminated unexpected system behavior.

Unified system behavior for different object types that can be displayed in a form table.

Print tools.
The option to use duplex printing settings of the printer is implemented. The system enumeration value DuplexPrintingType.UsePrinterSettings is implemented.

The DuplexPrinting property of spreadsheet documents, graphical schemas, representable document batches, and text documents has the following default value:

  • DoNotUse (for 8.3.8 compatibility mode)
  • UsePrinterSettings (when no compatibility mode is set and for 8.2.16 or earlier compatibility mode)

Printing spreadsheet documents and representable document batches from the web client to a PDF document and saving a spreadsheet document to a PDF document transfers the DuplexPrinting and PagePlacementAlternation property values to the corresponding PDF document properties. If the PDF viewer software supports these properties, they are applied when the document is printed. If the PDF viewer software does not support these properties, use the print software settings or printer settings for duplex printing.

Duplex printing settings of the printer were ignored during the printing of spreadsheet documents, graphical schemas, representable document batches, and text documents.Improved document printing options.
Data composition system.
When the data composition schema wizard is opened, data set fields with duplicate names are deleted, leaving only the first one.When the data composition schema wizard was opened, duplicate data set fields were not deleted.Eliminated unexpected system behavior.
Technological log.
Debugger exceptions that are thrown during the startup of the debug server (dbgs) are now saved to the technological log. The <EXCP> event is used for that logging.Debugger exceptions that are thrown during the startup of the debug server (dbgs) were not logged.Better error diagnostics for the startup of the debug server (dbgs).
Predefined data.
Development tools.
If the result of merging configurations would include predefined data items with duplicate names, a numeric suffix is added to the item taken from the source with lesser priority.The result of merging configurations could include predefined data items with duplicate names. +Eliminated unexpected system behavior.
1C:Enterprise script.
For the StrTemplate() method, the syntax option with a substitution token %(N) is implemented. You can specify a substitution number in parentheses after the percent. With this syntax you can specify a number right after the substitution token in a template string.Eliminated unexpected system behavior.You can create template strings where the substitution token is followed by a numeric character.
Development tools.
During the configuration check and refactoring, the search for calls of deprecated synchronous methods does not check the modules that cannot be executed at the client application side. In other modules the search ignores client script parts marked with preprocessor insrtructions and compilation directives.During the configuration check and refactoring, the search for calls of deprecated synchronous methods ignored the execution context of modules and methods.Reduced number of false warnings while searching for calls of deprecated synchronous methods during the configuration check and refactoring.
Web client, web service, and HTTP service publishing tools.
If an attempt of publishing to a web server using an account that does not have administrative rights is made:
  • Designer displays a warning dialog box, providing the options to continue the operation or cancel it.
  • The execution of the webinst utility is not interrupted, but it displays a warning.
If an attempt of publishing to a web server using an account that does not have administrative rights was made, no diagnostics was performed.Better diagnostics for publishing to the web sever.
XML and XDTO support.
When an XDTO package is deleted, 1C:Enterprise checks whether the package is used in web services. If web services that use the package are found, a warning with a web service list is displayed.When an XDTO package was deleted, 1C:Enterprise did not check whether the package was used in web services,Eliminated situations where a web service stopped working due to deletion of an XDTO package.
Managed forms.
The option to set the focus to command bars that do not contain form item commands of contain commands from multiple sources using Tab or Shift+Tab is implemented.

In the calendar used to enter a date in a text box, selection of the current date by clicking the Today hyperlink is implemented.

In the thin and thick clients, in the calendar used to enter a date in a text box, selecting a date that does not belong to the current month adds this date to the text box.

The option to set the focus to command bars that did not contain form item commands of contained commands from multiple sources using Tab or Shift+Tab was not available.

In the calendar used to enter a date in a text box, clicking the Today hyperlink set the focus to the current day of the month in the month currently selected in the calendar.

In the thin and thick clients, selecting a date that did not belong to the current month activated the selected month in the calendar field. In the web client, this added the selected date to the text box.

Eliminated unexpected user interface behavior in some scenarios.

Unified system behavior in different client applications.

Configuration repositories.
When you store an object to a configuration repository, the repository server checks the integrity of object data. In the event of integrity violation an exception is generated and the object is not stored.The configuration repository server did not check the integrity of stored object data.Reduced chance of storing corrupted configuration object data to a repository.
Database configuration update.
During a dynamic update, deletion of configuration objects that do not prevent the update and are absent from the new configuration is handled correctly. These objects are only deleted during the exclusive update.

This change is not implemented in 8.3.8 compatibility mode.

Deletion of configuration objects that did not prevent the update and were absent from the new configuration was performed immediately, during a dynamic update.Reduced number of issues that might arise during a dynamic update if some objects were deleted from the new configuration.
Web services and HTTP services.
Internet-enabled functionality.
This change is rolled back.

The URI string encoding (either with the EncodeString() function or with internal platform algorithms) replaces the percent sign (%) with %25.

This change is not implemented in 8.3.8 compatibility mode.

The URI string encoding (either with the EncodeString() function or with internal platform algorithms) did not replace the percent sign (%) with %25. It was left "as is."RFC 3986 recommendations for URI string encoding are implemented.
Localization.
In the number-to-words conversion algorithm for Azerbaijani language, a typo is corrected. This affects the numbers beginning with "two" and "twenty."The number-to-words conversion algorithm for Azerbaijani language had a typo. This affected the numbers beginning with "two" and "twenty."Eliminated unexpected system behavior.
Development tools.
In the debugger, when a collection (for example, a value table) is being viewed in a new window, its columns are no longer sorted in alphabetical order.In the debugger, when a collection (for example, a value table) was being viewed in a new window, its columns were sorted in alphabetical order. This behavior occurred in 1C:Enterprise versions 8.3.7 and 8.3.8.Eliminated unexpected system behavior.
Common attributes / Data separation.
Configuration extensions.
The data deleted by EraseInfoBaseData() method now includes configuration extensions for the entire infobase or for a specific area, depending on the call parameters.The EraseInfoBaseData() method did not delete configuration extensions.The EraseInfoBaseData() method clears more data.
Dynamic lists.
Server clusters.
In a dynamic list search box, if you enter a value that can be interpreted as a date with year specified as a 1-digit or 2-digit number, the year is converted to this century year. This prevents the error that occurs when you use Microsoft SQL Server with a zero date offset.In a dynamic list search box, if you entered a value that could be interpreted as a date with year specified as a 1-digit or 2-digit number, the year was not converted to this century year. In 1C:Enterprise that used Microsoft SQL Server with a zero date offset, this search scenario returned an error.The dynamic list error that occurred if a date was entered in a search box in 1C:Enterprise that used Microsoft SQL Server with a zero date offset is eliminated.
Spreadsheet documents.
When a spreadsheet document is exported to Microsoft Excel 97 or later format, if it contains cells with multiline text that is aligned centrally and does not fit a cell, the cell is merged. It is horizontal merging that spreads equally to both sides of the cell so that the entire text fits the new merged cell. The columns overlapped by the left and right borders of the merged cell are split into two columns.

The resulting document in Microsoft Excel format better matches the original document.

This change is not implemented in 8.3.8 compatibility mode.

When a spreadsheet document was exported to Microsoft Excel 97 or later format, if it contained cells with multiline text that were aligned centrally and did not fit the cell, such cells were not merged.When a spreadsheet document is exported to Microsoft Excel format, the resulting document better matches the original document.
Development tools.
If programmatic access to Microsoft Internet Explorer browser clipboard is disabled by the Allow Programmatic clipboard access security option, an attempt to use the Copy command of the Syntax Assistant context menu results in a notification that the clipboard is not available, which includes a workaround recommendation (use a keyboard shortcut).If the Allow Programmatic clipboard access security option in Microsoft Internet Explorer was disabled, the Copy command of the Syntax Assistant context menu did not work.Better diagnostics of unexpected system behavior.
Managed forms.
For groups with titles that display data, the support of Format property in both interface modes (Taxi and Version 8.2) is implemented.

This change is not implemented in 8.3.8 compatibility mode.

For groups with titles that display data, the Format property was not supported in some interface modes. This property had some implementation differences between the thin and web clients.Uniform behavior of the thin and web clients. Eliminated unexpected system behavior.
Development tools.
The option to update configurations that include constant forms using update (.cfu) files is restored.

The option to update configurations using update (.cfu) files is implemented for scenarios where only the Use always flag in constant forms was changed.

In some scenarios, if the Use always flag in a constant form was changed in a new configuration, this caused configuration update issues.Eliminated the issues that appeared during the update of configurations that included constant forms with update (.cfu) files.
Development tools.
 +

If the size of the file that stores new and changed objects, which is created during the generation of a .cfu update file, exceeds 2 GB, the update file is generated in the new format. If you are creating the update file manually, you get a notification about the new format in a dialog box. If you are creating the update file in batch mode, the notificaton is added to the service message file (/out comand-line option).

Update files that have new format can only be used in 1C:Enterprise versions 8.3.9.2033 and later.

If you attempt to use an update file in an earlier 1C:Enterprise version, you get a message about incorrect data storage format.

You can use 1C:Enterprise versions 8.3.9.2033 and later to apply any updates, regardless of their file format.

If the size of the file that stored new and changed objects, which was created during the generation of a .cfu update file, exceeded 2 GB, the update file could not be generated. 1C:Enteprise supports very large update files (.cfu).
Print tools.
The RepresentableDocumentBatch.Print() method splits batches into multiple jobs (in all application types except for the web client). It uses the document batch properties, such as the printer, page orientation, or duplex printing, to generate the jobs (and split document batches).The RepresentableDocumentBatch.Print() method printed the entire document batch as a single job (in all application types except for the web client). This might cause issues when the documents were to be printed on different printers or with different print settings because jobs always apply the same settings to all its documents.Eliminated document batch printing issues caused by differences of document print settings (such as the printer, page orientation, or duplex printing).
Operating system.
1C:Enterprise behavior changed in scenarios that involve switching the computer to sleep mode. 1C:Enterprise prevents switching to the sleep mode if:
  • It uses a hardware protection key
  • It runs in file mode and its database file is located on a network resource
1C:Enterprise prevented switching to sleep mode if:
  • It used a hardware protection key
  • It ran in file mode and its database file was located on a network resource
  • It ran in client/server mode.
Power saving schemes applied when 1C:Enterprise runs are changed.
Infobase operations.
Dumping an infobase to a .dt file is not interrupted if any issues related to the internal infobase structure are encountered.Dumping an infobase to a .dt file was interrupted if any issues related to the internal infobase structure were encountered.Minor infobase data structure issues, which do not impact 1C:Enterprise functionality, no longer block dumping infobases to files.

+

JSON support.
Improved reliability of JSON operations.JSON operations might cause unexpected shutdown.Eliminated unexpected system behavior.
Server clusters.
When the Secure connection cluster property value is changed, this takes effect after restarting the cluster processes. It is recommended that you restart the cluster after changing the Secure connection property value.An attempt to change the Secure connection cluster property value generated an error and the value was not changed.Eliminated unexpected system behavior.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
1C:Enterprise script.
During the compilation of 1C:Enteprise script texts, unknown compilation directives cause errors.

This change is not implemented in 8.3.8 compatibility mode.

Unknown compilation directives did not cause compilation errors.Better control of source texts. Reduced number of issues that are hard to detect (typos in compilation directives).
Queries.
When a transaction is rolled back from the temporary table manager, all temporary tables created within the transaction are deleted. In file databases, temporary tables created within a query transaction are not available in that query after rolling the transaction back (this behavior is now uniform with scenarios that use other DMBS).

This change is not implemented in 8.3.8 compatibility mode.

When a transaction was rolled back from the temporary table manager, temporary tables created within the transaction were not deleted. In file databases, the option to use temporary tables created in a transaction that was rolled back was available. In scenarios that used other DBMS, this option was not available.Uniform 1C:Enterprise behavior in scenarios that use different DBMS.
Navigation links.
An attempt to execute the GetURL() method for a value that cannot provide an URL generates an exception.

This change is not implemented in 8.3.8 compatibility mode.

An attempt to execute the GetURL() method for a value that cannot provide an URL had the following result:
  • In the thin client, the method returned a blank string.
  • In the web client, an exception was generated.
Unified system behavior in different client applications.
Window-based interface.
Error handling.
If the Timeout parameter of the DoQueryBox(), ShowQueryBox(), DoMessageBox(), or ShowMessageBox() method has a negative value, an exception is generated.

This change is not implemented in 8.3.8 compatibility mode.

If the Timeout parameter of the DoQueryBox(), ShowQueryBox(), DoMessageBox(), or ShowMessageBox() method had a negative value:
  • In the thin client, the timeout was counted from 4 294 967 295.
  • In the web client, the value was not substituted.
Eliminated unexpected system behavior. Unified system behavior in different client applications.
Managed forms.
The option to monitor the usage of context server calls (including implicit calls) in form event handlers where such calls are prohibited at run time is implemented. +If you enable this option, diagnostics messages are added to the message window.

To enable or disable this option, use the /EnableCheckServerCalls command-line option of the client application. The option to run the client application from Designer is implemented, with this command-line option available.

A tool for monitoring the usage of context server calls in form event handlers where such calls were prohibited was not available.Improved diagnostics of incorrect usage of 1C:Enterprise programming interfaces.
DBMS operations.
If a parameter of the In operation of the query language is a value table with a column of String type longer that 1024 characters or BinaryData type longer that 2048 bytes, an exception is generated during the query execution.If a parameter of the In operation of the query language was a value table with a column of String type longer that 1024 characters or BinaryData type longer that 2048 bytes, the query might or might not be executed, depending on the DBMS.More predictable query results on different DBMS. Improved system reliability.
Client application.
Managed forms.
At the thick client startup, the Synchronous call usage mode for platform extensions and add-ins configuration property is ignored and all synchronous methods are executed without any warnings or exceptions.

When the thick client is started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls option is not passed to the client. The behavior of the thin client and the web client in this scenario is not changed.

The behaviour of configuration verification and refactoring is not changed: they display warnings for all synchronous methods calls and recommend conversion to asynchronous methods.

At the thick client startup, the Synchronous call usage mode for platform extensions and add-ins configuration property was not ignored.

When the thick client was started from Designer, the /EnableCheckExtensionsAndAddInsSyncCalls option was passed to the client.

Removed checks for synchronous method calls in applied solutions intended to run in thick client only.
Queries.
During the query generation, the query builder (in Designer and in the thick client) and the QuerySchema object (in the thick client) generate aliases for all fields of the first query (in a set of unions) for each query in a batch.

This change is not implemented in 8.Х.Х repository compatibility mode. +

During the query generation, the query builder (in Designer and in the thick client) and the QuerySchema object (in the thick client) generated aliases only for expression fields and for fields used for ordering and totals calculation.Unified behavior of query builder and the QuerySchema object in different client applications.
Managed forms.
The following object keys are used for storing desktop separator positions:
  • HomePage/WindowSettings
  • HomePage/Taxi/WindowSettings

Once you turn the compatibility mode off, the keys are renamed. If you set the compatibility mode to Version 8.3.8, the initial names are applied again.

When you export a configuration to a set of XML files, the file that stores the HomePageWorkingArea property (former StartPageWorkingArea property) has a different name.

This change is not implemented in 8.3.8 compatibility mode.

The following object keys were used for storing desktop separator positions:
  • StartPage/WindowSettings;
  • StartPage/Taxi/WindowSettings.
The object key names better reflect their purpose.
Spreadsheet documents.
If auto grouping or rows is enabled, new groupings inherit the name and visibility from the area that is displayed in the grouping header area.

This change is not implemented in 8.3.8 compatibility mode.

If auto grouping or rows was enabled, new groupings inherited the name and visibility from the area that was displayed inside the grouping.Eliminated unexpected system behavior.
Common objects.
If the DBMSNames parameter of the GetDBStorageStructureInfo() method

has a value of non-Boolean type, an exception is generated.

This change is not implemented in 8.3.7 compatibility mode.

A value of any type could be passed to the DBMSNames parameter of the GetDBStorageStructureInfo() method.Eliminated unexpected system behavior.
Spreadsheet documents.
In spreadsheet documents, when a text is displayed with nonhorizontal orientation, it has the same font size as regular text.

This change is not implemented in 8.3.8 compatibility mode.

In spreadsheet documents, when a text was displayed with nonhorizontal orientation, it had bigger font size than regular text.Eliminated unexpected system behavior.
DBMS operations.
Changing the data lock timeout in the Infobase options dialog box in Designer requires administrative rights in a nonseparated session and sets exclusive infobase access mode. If an exclusive lock cannot be set, a message with a list of sessions preventing the lock is displayed, it includes the retry option.

The SetLockWaitTime() method requires administrative rights in a nonseparated session, sets an exclusive database lock (if it was not set earlier), and throws an exception if the exclusive lock cannot be set.

The change of the data lock timeout is applied immediately to all DBMS except IBM DB2. Changing the lock timeout in IDB DB2 requires a database restart.

Changing the data lock timeout in the Infobase options dialog box or using the SetLockWaitTime() 1C:Enterprise script method was allowed in infobases running in shared mode.Eliminated the issues related to database operations that appeared in some scenarios.
XML and XDTO support.
For the XMLWriter.OpenFile() method, the AddBOM parameter is implemented. It shows whether the resulting file includes a BOM.This feature was not provided.Integration with systems that do not expect BOMs in their input XML files is now available.
Administration tools.
System requirements.
In the file infobase, the check for client application versions is implemented. Access to the infobase is only allowed if the versions of all client applications match. If the versions do not match, an error is displayed.An attempt to access an infobase using multiple versions from the following list generated an exception: 8.2.19 to 8.3.4, 8.3.6, and 8.3.7.

In some cases simultaneous access to a single infobase with different platform versions was allowed, where one version was 8.2.18 or earlier and the other one was in range 8.3.1-8.3.3.

Increased reliability of file infobases. Simultaneous access to a single infobase using different 1C:Enterprise versions is not allowed.
ZIP archive operations.
The path separator of the ZipFileEntry object depends on the operating system.

This change is not implemented in 8.3.8 compatibility mode.

The path separator of the ZipFileEntry object was always a slash mark (/) and did not depend on the operating system.ZIP file operations use the same file path separators as other file operations.
Data composition system.
When data composition template composer generates parameter names, it does not assign parameter names that are already used in the data composition schema.

This change is not implemented in 8.3.8 compatibility mode.

When data composition template composer generated parameter names, it could assign parameter names that were already used in the data composition schema.Eliminated unexpected system behavior.
Administration tools.
When 1C:Enterprise establishes a secure connection (HTTPS) to the Licensing Center, it automatically selects the root certificate store of the operating system.

If the Internet connection uses a proxy server that decrypts secure connection (HTTPS) traffic, the system administrator must add the certificates that sign the proxy server certificate to the trusted root certificate store of the operating system.

When 1C:Enterprise established a secure connection (HTTPS) to the Licensing Center, it searched the file cacert.pem for a secure connection certificate.Reduced number of issues related to interaction with the Licensing Center.
Configuration extensions.
For the execution of some configuration object handlers and subscriptions, disabling the safe mode is implemented. Once a handler or subscription is executed, the safe mode and the security profile are restored.

You can disable the safe mode manually using the SetSafeModeDisabled() and GetSafeModeDisabled() global context methods. These methods are not available in configuration extensions.

The list of handlers where the safe mode is automaticly disabled is provided in the documentation.

The option to disable the safe mode using 1C:Enterprise script tools was not provided.You have the option to access objects that have events that require privileged mode in their object modules from configuration extensions and external data processors executed in safe mode.
Internet-enabled functionality.
TLS 1.2 protocol is used to establish secure connection because it provides additional security. You can force the use of TLS 1.0 protocol when establishing thin client connection to a web server using the command-line option /HttpsForceTLS1_0.

HTTPConnection, FTPConnection, and WSProxy objects automatically select TLS 1.2 protocol, regardless of the specified client certificate source.

For the conf.cfg configuration file, the ForceTLS1_0 parameter is implemented.

Simultaneous use of /HttpsForceTLS1_0 and /HttpsForceSSLv3 command-line options in the thin client is not supported.

TLS 1.0 protocol was used to establish secure connections.Increased security of thin client Internet connections.
Internet-enabled functionality.
If an SMTP server cannot send an email message to one or several recipients, the InternetMail.Send() method returns a map where recipients are keys and SMTP server diagnostic messages are values.

This change is not implemented in 8.3.8 compatibility mode.

If an SMTP server could not send an email message to one or several recipients, the InternetMail.Send() method generated an exception.You can determine which recipients cannot be reached by email and view the reasons provided by the SMTP server.
Development tools.
Configuration properties.
Dumping configurations to files/Restoring configurations from files.
When a configuration is exported to files, the format of Compatibility mode configuration property in the resulting file is different. The new format eliminates possible loss of compatibility mode data during the import.When a configuration with Compatibility mode property set to Do not use was exported to files, the property value was exported as Do not use. Then, if that configuration was imported using a later 1C:Enterprise version, the imported compatibility mode value was incorrect.Eliminated the chance to lose compatibility mode data after exporting and importing a configuration.

Eliminated unexpected system behavior.

Spreadsheet documents.
The FillPropertyValues() method applied to a spreadsheet document copies the Template property of the spreadsheet document.

This change is not implemented in 8.3.8 compatibility mode.

The FillPropertyValues() method applied to a spreadsheet document did not copy the Template property of the spreadsheet document.The behavior implemented earlier to streamline migration to the previous version is no longer supported.
Administration tools.
Database operations.
In the file mode, the default format of new databases is 8.3.8.In the file mode, the default format of new databases was 8.2.14.The optimized file database format implemented in platform version 8.3.8 becomes the default one.
Internet-enabled functionality.
The Port property of FTPConnection object and the Port parameter of its constructor have the Number type.

This change is not implemented in 8.3.8 compatibility mode.

The Port property of FTPConnection object and the Port property of its constructor had String type. The constructor parameter accepted any data that could be converted to Number type.Eliminated unexpected system behavior.
Database operations.
After calling the GetDBStorageStructureInfo() method, tables that do not have presentations in the query language have empty strings for their names (TableName property) and their field names (FieldName property).

This change is not implemented in 8.3.8 compatibility mode.

After calling the GetDBStorageStructureInfo() method, tables that did not have presentations in the query language had their table name (TableName property) and field name (FieldName property) values equal to virtual table presentations.Eliminated unexpected system behavior.
HTML support.
Reading and writing XML documents containing <?xml does not generate an error message.

This change is not implemented in 8.3.8 compatibility mode.

Reading and writing XML documents containing <?xml generated an error message.Eliminated unexpected system behavior.
ZIP archive operations.
File names in ZIP archives are written in UTF8 encoding.

For the ZipFileWriter object constructor and the Open() method of the ZipFileWriter object, parameters that define file name encoding in ZIP archives are implemented. These parameters override the FileNamesEncodingInZipFile parameter in the conf.cfg file.

The default value of the FileNamesEncodingInZipFile parameter in the conf.cfg file is UTF8.

This change is not implemented in 8.3.8 compatibility mode.

File names in ZIP archives were written in UTF8 encoding and the current operating system encoding.

1C:Enterprise script did not provide methods to specify encoding of file names in ZIP archives.

The default value of the FileNamesEncodingInZipFile parameter in the conf.cfg file was OSEncodingWithUTF8.

1C:Enterprise script provides methods to specify the encoding of file names in 1C:Enterprise-generated ZIP archives.
Dynamic lists.
Dynamic list fields included in conditional form appearance item filters are always passed to the client, regardless of the value of the Use always field property or the availability of a visible linked column.

This change is not implemented in 8.3.7 compatibility mode.

Dynamic list fields included in conditional form appearance item filters were not automatically passed to the client. To ensure correct functioning of conditional appearance items, developers had to set the Use always property for such fields.Better usability for 1C:Enterprise developers.
Dynamic lists.
The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved by using conditional dynamic list appearance is added to the documentation.The recommendation to avoid using conditional form appearance for customizing dynamic list appearance if the desired effect can be achieved by using conditional dynamic list appearance was not available in the documentation.1C:Enterprise documentation is improved.
Data composition system.
In the composition of a data composition system template, the following operations are performed using additional data sets that are automatically generated by a template composer:
  • Getting fields
  • Applying filters to fields received using "." (dot) from fields that contain aggregate functions and are obtained from a query

This change is not implemented in 8.3.8 compatibility mode.

In the composition of a data composition system template, the following operations were performed within a query:

+

  • Getting fields
  • Applying filters to fields received using "." (dot) from fields that contain aggregate functions and are obtained from a query

This might generate incorrect results or errors. +

Eliminated unexpected system behavior.
Data composition system.
In data composition schema templates, when parameters that can have both English and Russian names are generated, their names are generated in the language of the current 1C:Enterprise script variant.

This change is not implemented in 8.3.8 compatibility mode.

In data composition schema templates, when parameters that could have both English and Russian names were generated, their names were always generated in English.You can use Russian names of data composition schema parameters, which match the parameter names that are automatically retrieved from virtual tables.
Managed forms.
1C:Enterprise behavior in the following scenario is changed: a user types something in a text box and then clicks a decoration hyperlink without exiting the text box, which initiates a context server call. The new behavior consists of the following steps:
  • Call the OnChange event handler for the text box.
  • Call the URLProcessing event handler for the decoration.
  • The text box displays the typed text.

This change is not implemented in 8.3.8 compatibility mode.

+

1C:Enterprise behavior in the following scenario was different: a user types something in a text box and then clicks a decoration hyperlink without exiting the text box, which initiates a context server call. The previous behavior consisted of the following steps:

+

  • In the thin and thick clients:
    • Call the URLProcessing event handler for the decoration.
    • The text box displays the text that was there before typing.
  • In the web client:
    • Call the URLProcessing event handler for the decoration.
    • The text box displays the typed text.
Eliminated unexpected system behavior. Unified behavior of client applications.
Client application.
Client application installation.
Add-ins.
Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented:
  • On Windows, the file system extension and cryptography extension installers for Google Chrome and Mozilla Firefox are converted to .exe format and signed with both SHA-1 and SHA-256.
  • It is recommended that you sign client application installer 1CEClientSetup.exe with both SHA-1 and SHA-256.
On Windows, the file system extension and cryptography extension installers for Google Chrome and Mozilla Firefox were delivered as .msi files signed with SHA-1.The platform executable files are verified on all supported operating systems of Windows family.
Automated testing.
The TestedFormButton.Click() method generates an error if the button specified in this method is not visible.

This change is not implemented in 8.3.8 compatibility mode.

The TestedFormButton.Click() method did not generate an error if the button specified in this method was not visible.Eliminated unexpected system behavior.

The automated testing only performs the actions that are available to users in interactive mode.

Table of contents

Renamed objects

ObjectThe old nameThe new name
The StartPageForms object is renamed. The former name is supported for compatibility purposes.
  • StartPageForms.
  • HomePageForms.
The StartPageSettings object is renamed. The former name is supported for compatibility purposes.
  • StartPageSettings.
  • HomePageSettings.
The StartPageWorkingArea object is renamed. The former name is supported for compatibility purposes.
  • StartPageWorkingArea.
  • HomePageWorkingArea.
The ClientApplicationWindow.StartPage property is renamed. The former name is supported for compatibility purposes.
  • StartPage.
  • HomePage.
The TestedClientApplicationWindow.StartPage property is implemented. The former name is supported for compatibility purposes.
  • StartPage.
  • HomePage.
Name of the system enumeration that lists item and title alignment options.
  • ItemsAndTitlesAlign.
  • ItemsAndTitlesAlignVariant.
The value of the Purpose column of the ExtensionInfo value table returned by GetDBStorageStructureInfo() method.

This change is not implemented in 8.3.8 compatibility mode.

  • Main.
  • ConfigurationExtensionsInformation.
The value of the Purpose column of the ODataSettings value table returned by GetDBStorageStructureInfo() method.

This change is not implemented in 8.3.8 compatibility mode.

  • Main.
  • StandardODataInterfaceOptions

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
File operations.
Multimedia support.
On the mobile platform, the FileDialog object is available. For the dialog limitations on specific mobile operating systems, see the Syntax Assistant. For mobile devices, the option to select files interactively is implemented for the following methods: GetFile(), GetFiles(), PutFile(), and PutFiles().

The File.GetMobileDeviceLibraryFilePresentation() method is implemented. It returns the file presentation for displaying on the mobile device.

You can use mobile device library file names (with the content: schema) in constructors of the following objects: File, BinaryData, Picture, and MobileDeviceApplicationRun. You can use them as parameters for the following global context methods: RunApp(), GotoURL(), FileCopy(), MoveFile(), DeleteFiles(), and FindFiles(). On iOS and Android, you can also use them as parameters for the following methods of the MultimediaTools object: PlayAudio() and GetAudioDuration().

The MobileDeviceLibraryDir() global context method is implemented. It returns a path to a mobile device library (a picture, audio, or video library).

The FileDialog object was not available on the mobile platform.Interactive file operations are implemented for the mobile platform.
Mobile device-specific features.
For Android operating system, the option to process incoming call data using 1C:Enterprise script tools is implemented.

For the TelephonyTools object, the CallsHandlingSupported(), AttachCallsHandler(), and DetachCallsHandler() methods are implemented. The TelephonyTools.CallsHandlingSupported() method returns True on Android only.

This feature was not provided on the mobile platform.The option to process incoming call data in mobile applications using 1C:Enterprise script tools is now available on Android operating system.
Mobile device-specific features.
Extended multimedia options for the mobile platform:
  • The option to play a sound or vibration alert is implemented. The MultimediaTools.PlaySoundAlert() method is implemented.
  • The option to play audio data of various types is implemented. Playing is performed using the default application provided with the operating system. The option to stop playing is implemented. For the MultimediaTools object, the PlayAudio(), StopAudioPlayback(), and GetAudioDuration() methods are implemented.
  • The option to read text using the screen reader provided with the operating system is implemented. The option to stop reading is implemented. For the MultimediaTools object, the PlayText(), StopTextPlayback(), and TextPlaybackSupported() methods are implemented.
These features were not provided on the mobile platform.Extended multimedia support.
Data composition system.
On the mobile platform, the support of data composition system is implemented, except for the objects that allow user interaction. Therefore, all data composition system operations are performed using 1C:Enterprise script tools.

In Designer, the option to create data composition schemas for reports that run in mobile applications is implemented.

This feature was not provided on the mobile platform.Extended report development capabilities on the mobile platform.
Add-ins.
On the mobile platform, add-in support is implemented. It uses the NativeAPI technology.

You can export a mobile configuration from Designer to 1cema.zip format, which includes the add-ins used in the configuration.

When you connect a mobile device using Android Debug Bridge (ADB), add-ins are copied to the device.

In the mobile application builder, the option to build applications with add-ins is implemented.

Add-in development technology documentation and examples are updated (read more).

The mobile platform did not support this feature.You have the option to expand mobile platform functionality when its standard features do not cover your needs.
Managed forms.
The following features are implemented for the mobile platform:
  • Display a command bar button as a hyperlink.
  • Set horizontal picture alignment on a managed form button.
  • Set gaps between command bar buttons.
  • Set command bar button shapes (except for buttons located in popups).
  • Set the view of managed form buttons.
  • For text boxes, support of CreateButton and ChoiceButtonRepresentation properties is implemented.
  • For text boxes, support of EditTextChange and Creating events is implemented.

Support of BorderColor, BackColor, TitleTextColor, and TitleFont properties is implemented for buttons of CommandBarButton and CommandBarHyperlink type and for form group extensions for popups.

This feature was not provided on the mobile platform.The set of features available on the mobile platform is closer to the set of features available on the desktop platform.
Internet-enabled functionality.
The option to check the availability of data transfer network in mobile applications is implemented.

The InternetConnectionInformation global context property is implemented.

This feature was not provided on the mobile platform.The option to analyze available data transfer methods and choose the optimal strategy for operations with external data is implemented.
JSON support.
The mobile platform now supports JSON operations. Serialization of XDTO documents to JSON objects is not supported.This feature was not provided on the mobile platform.Simplified integration with applications (including web applications) that use JSON data format. The option to store data in JSON format (for example, instead of XML format) is implemented.
Internet-enabled functionality.
The behavior of the OpenSSLSecureConnection object is unified with that of the PC platform.
  • If the CertificationAuthorityCertificates parameter of the object constructor is not specified, the certificate is not checked.
  • If the CertificationAuthorityCertificates parameter of the object constructor is specified, the check uses the root certificates installed on the device.

The OSCertificationAuthorityCertificates object is now available on the mobile platform.

This change is not implemented in 8.3.8 compatibility mode.

The certificate check always used the root certificates installed on the mobile device. The CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection object constructor was ignored.Unified behavior of the mobile platform and the PC platform.

Eliminated unexpected system behavior.

Mobile device-specific features.
The option to check the availability of operations with global contact keys, calendars, and calendar events on different mobile operating systems is implemented.

For the ContactManager object, the GlobalContactsKeySupported() method is implemented.

For the CalendarsManager object, the GlobalCalendarsKeysSupported() and GlobalEventsKeysSupported() methods are implemented.

The GlobalContactKey parameter of the AccountContactData object constructor is no longer supported. The values of properties that describe global contact keys, calendars, and calendar events depend on the result of the function that checks the availability of global key operations. If global key operations are not supported, requests to these values return blank strings.

Availability of LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects on the mobile application server is implemented.

The availability of global contact keys, events, and calendar events depended on the platform where a mobile application was running. Developers had no means to check whether operations with global keys from 1C:Enterprise script were supported.

The LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects were not available on the mobile application server.

The mobile platform behavior is unified with the general behavior of applications that have features that are not available on some mobile devices or operating systems.
Predefined data.
In the mobile platform, support of the following global context methods is implemented: InitializePredefinedData(), SetInfoBasePredefinedDataUpdate(), and GetInfoBasePredefinedData(). This feature was not provided on the mobile platform.Unified desktop and mobile platform features related to predefined data.
Managed forms.
New managed form interface features in the mobile platform. Now you can:
  • Create collapsible groups.
  • Manage Pages form item visibility if it is displayed either as the current page or as tabs. In this scenario you can use 1C:Enterprise script to switch between the current page and the tabs. The CurrentPagesState property is implemented.
  • Manage visibility of open and clear buttons in text boxes. The AutoShowClearButton and AutoShowOpenButton properties are implemented for managed form text boxes.
  • Manage multiline text box height. The HeightControlVariant property is implemented for managed form text boxes.
  • Switch form items to edit mode. The ManagedForm.BeginEditingItem() method is implemented.
  • Manage some service options for text boxes, such as:
    • Auto correction. The AutoCorrectionOnTextInput property is implemented.
    • Spell checking. The SpellCheckingOnTextInput property is implemented.
    • Auto capitalization. The AutoCapitalizationOnTextInput property is implemented.
    • Manage the keybord type used to input data. The SpecialTextInputMode property is implemented.
    • Change the label of the return keyboard button. The OnScreenKeyboardReturnKeyText property is implemented.
  • Manage form table height if data displayed in the table is not a dynamic list. The HeightControlVariant property is implemented.
  • Manage the search string position. You can specify whether the search string is displayed in the form header or appears after a user swipes down a table title.

Command bar commands are no longer included in the More menu.

Table row context menu commands can be moved to the More menu if they do not fit the screen.

Fixed spreadsheet document areas are displayed in a new way.

These features were not provided.
  • Command bar commands were duplicated as items of the More menu.
  • 1C:Enterprise attempted to display all table row context menu commands on the screen.
  • Fixed spreadsheet document areas were displayed differently.
The mobile platform interface is closer to the modern interface development standards.
Mobile device-specific features.
The implementation of the Beep() method is now uniform with the implementation of the MultimediaTools.PlaySoundAlert(SoundAlert.Default).The Beep() method did not perform any actions.You can use the Beep() method to play the default sound alert of a mobile device.
Administration tools.
For mobile applications, the following features are implemented:
  • Infobase verification and repair.
  • Infobase backup.
  • The option to run an automated backup before the application update, so that you can restore the infobase if any issues occur during the update. This option is enabled by default.
  • The option to schedule automated infobase backups is implemented.

The backups are stored to the mobile device storage.

These options are available in the application settings dialog box (the Administration button in this dialog box).

This feature was not provided.Additional options for mobile application administrators.
Mobile device-specific features.
The 1C:Enterprise mobile platform does not support Apple iAd any more as the service is officially shut down. Google AdMob advertisement service is supported for both iOS and Android devices.

In Mobile application builder, you can specify that your application uses ads, and the builder picks the appropriate mobile platform for building the application based on the option that you select.

You do not have to modify your iOS applications that support both services but the applications that support only Apple iAd require modification.

The 1C:Enterprise mobile platform supported Apple iAd and Google AdMob.The Apple iAd service, which is now obsolete, is not supported.
Mobile application builder.
Mobile application builder can create application builds for OS emulators.Mobile application builder could not create application builds for OS emulators.More options for iOS application developers.

Table of contents

Library updates + +

Table of contents

Transition from the previous version to the version 8.3.9

Table of contents

Version 8.3.8

Version 8.3.8 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.7 is added to the list of available values of the Compatibility mode property.Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, and 8.3.6.In version 8.3.8 you can run configurations created in version 8.3.7 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.8 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.7 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Internet-enabled functionality.
Support of Linux trusted certificate directories (/etc/ssl/certs and /etc/pki/tls/certs) is implemented. The OSCertificationAuthorityCertificates object enabling cross-OS certificate operations is implemented. The LinuxCertificationAuthorityCertificates object caching certificate data on Linux operating system is implemented. It is recommended that you use the OSCertificationAuthorityCertificates object.

The CertificationAuthorityCertificates parameter of OpenSSLSecureConnection object constructor accepts objects of OSCertificationAuthorityCertificates and LinuxCertificationAuthorityCertificates types.

NSS certificates are no longer supported.

On Linux operating system, the platform used NSS certificate store.On Linux operating system, in the thin client, the option to access infobases published on resources that require clent certificates is implemented.
Web client, web service, and HTTP service publishing tools.
System requirements.
Support of Apache 2.4 is implemented for Windows and Linux.

For the webinst utility, the -apache24 key is implemented. +

This feature was not provided.

Apache versions 2.0 and 2.2 were supported.

Extended list of supported web servers.
Automated testing.
The About 1C:Enterprise window and the title of the client application window indicate whether the client application is a test manager or a test client.

The TestedApplication.SetFileDialogResult() method is implemented, it provides the result of an operation performed in the file selection dialog box.

The resulting collection of the TestedApplication.GetChildObjects() method now inlcudes windows that contain text or spreadsheet documents.

The TestedForm.ExecuteChoiceFromList() method is implemented, it selects a value from the list opened using the ManagedForm.ChooseFromList() method.

The TestedForm.ExecuteChoiceFromMenu() method is implemented, it selects a value from the menu opened using the ManagedForm.ChooseFromMenu() method.

For the TestedFormField object, the support of form field extension for a text document is implemented.

For the TestedFormField object, the support of form field extension for a formatted document is implemented. For the TestedFormField object, the following methods are implemented: GetHTML() (returns the formatted document content) and InputHTML() (emulates entering text to the formatted document).

The TestedFormField.WriteContentToFile() method is implemented, it writes the document file to the hard disk (same as the Save command). The method is available for spreadsheet document, text document, and formatted document extensions.

These features were not provided.Extended automated testing capabilities.
Development tools.
The option to save and restore the settings in the configuration comparison and merging window is implemented. A check box that manages automatic automatic saving of the form settings is implemented.

The module comparison and merging form is refactored. Now it includes a command bar with the editor commands.

The filter settings now include the Show only properties that were changed twice option.

These features were not provided.Improved usability for applied solution developers who often perform comparison and merging of configurations with custom settings.
Development tools.
The following operations are now available as command-line options for batch Designer startup mode:
  • Compare configurations (/CompareCfg)
  • Merge configurations (/MergeCfg)
  • Lock objects in a configuration repository (/ConfigurationRepositoryLock).
  • Release objects in a configuration repository(/ConfigurationRepositoryUnlock).
  • Store modified objects to a configuration repository (/ConfigurationRepositoryCommit).
  • Label a repository version (/ConfigurationRepositorySetLabel).

The following parameters are implemented for /UpdateCfg command-line option of batch Designer startup:

  • -DumpListOfTwiceChangedProperties. Generates the list of properties that were changed twice.
  • -IncludeObjectsByUnresolvedRefs. If the settings include objects that are not in the list of objects to be merged and are not available in the main configuration, but these objects are referred from objects that are in the list, mark them for merging and attempt to continue the merging.
  • -ClearUnresolvedRefs. Clear references to objects that are not in the list of objects to be merged.
  • -Settings. Use the merge settings from the specified file.
  • -force. Automatically resolve merge issues. This affects the platform behavior in the following cases: locked objects are found; properties that were changed twice and do not have the merge mode specified are found; or a warning about deletion of objects refered by objects that do not participate in the merging is issued.

For /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup, the -objects parameter is implemented. This parameter specifies that the operation is performed for a specific set of configuration objects.

These features were not provided.

The /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup was only applicable to the entire configuration.

Simplified automatic update of applied solutions.
Queries.
For the query debug, the following operations are inplemented: viewing the list of temporary tables, the structure of temporary tables, and the contents of temporary tables. The Query.ExecuteBatchWithIntermediateData() method is implemented. The TempTablesManager.Tables property is implemented.This feature was not provided.Extended applied solution debug capabilities, especially when debugging complex batch queries.
External data sources.
The ExternalDataSourceManager.TransactionActive() method is implemented. It determines whether an external data source has a transaction in progress.This feature was not provided.The option to determine whether an external data source has a transaction is progress is now available.
Web services and HTTP services.
Support of web services that support MTOM standard is implemented (read more).This feature was not provided. Web services that supported MTOM standard were not supported.Extended capabilities for 1C:Enterprise integration with third-party systems. Integration with web services that support optimized transfer of binary data is available, which reduces the network traffic and RAM usage.
OData interface.
The following improvements to the standard OData interface are implemented:
  • Filter by composite type
  • Lambda expressions
  • New query options for filtering the received data:
    • $skip. Skips several first records in the query result
    • $inlinecount. Includes the size of the resulting selection to the query result
    • $orderby. Sets the order of records in the query result
    • $count. Returns the number or records in the query
  • More functions can be used in queries:
    • Functions that process string values
    • Functions that process date and time values
    • Function that checks whether a value has the specified type
    • Functions that convert types
The standard OData interface provided more limited functionality1C:Enterprise object presentations better conform to the OData standard requirements.
Configuration extensions.
Development tools.
The ConfigurationExtension() method is implemented for configuration objects. It is used to determine the configuration extension where the object belongs.

For ConfigurationExtensionsManager.Get() method, the ConfigExtensionSource parameter is implemented. If specifies which list of extensions is retrieved (database extensions only; extensions available in the current session; or extensions that were disabled or did not pass the check at the attachment stage).

This feature was not provided.Simplified configuration extension operations in 1C:Enterprise script.
Configuration extensions.
The ConfigurationExtensionCompatibilityMode property of configuration extensions is implemented. This property is used to limit the extension functionality to ensure its compatibility with a specific version of 1C:Enterprise platform, while leaving the option to edit the extension using a later 1C:Enterprise platform version, which provides more features for configuration extensions.The option to create the following objects in configuration extensions is implemented:
  • Common templates
  • Common commands
  • Common pictures
  • Attributes, tabular sections, and attributes of adopted tabular sections for:
    • Reports
    • Data processors
  • Forms, templates, and commands of adopted objects:
    • Exchange plans
    • Filter criteria
    • Settings storage
    • Catalogs
    • Documents
    • Document journals
    • Enumerations
    • Reports
    • Data processors
    • Accounting registers
    • Accumulation registers
    • Calculation registers
    • Information registers
    • Charts of characteristic types
    • Charts of accounts
    • Charts of calculation types
    • Business processes
    • Tasks
    • External data sources:
      • Tables
      • Cubes
      • Dimension tables

In configuration extensions, the option to change the properties of adopted configuration objects, which describe both main and auxiliary forms, is implemented.

For adopted reports, the option to change the Main data composition schema property is implemented.

In configuration extensions, changing the Picture property of subsystems, command groups, commands, and common commands is available.

In the module editor, the context help is only displayed for objects included in the current extension.

These features were not provided. In the module editor, the context help was displayed for both the original configuration and the extension.Extended configuration extension capabilities.
Development tools.
Dumping/loading configurations to files.
The option to export external reports and data processors to XML files is implemented. In Designer, the following File menu commands provide this option: Save, Save as, and Save copy. After the export, changing the object type (external report to external data processor or vice versa) is not available. The import is available using the Open command of the File menu.

In the external report or data processor editor dialog box, the options to export the report or data processor to files and import it from files are implemented. The export and import commands are available on the Actions menu of the dialog box.

The option to compare an external report or data processor with an external report or data processor stored in XML files is implemented. In the external report or data processor editor dialog box, the following Actions menu command provides this option: Compare and merge with external report or data processor.

The option to export and import external reports or data processors to or from XML files using the command-line options of Designer batch mode is implemented. The /DumpExternalDataProcessorOrReportsToFiles and /LoadExternalDataProcessorOrReportsFromFiles keys are implemented.

Export to both flat and hierarchical file structures is supported. The export is only available in export format version 2.0. The import format is determined automatically during the import.

These features were not provided. External reports and data processors could only be saved in binary format.Extended capabilities for external report and data processor operations in scenarios that use external version control systems. The option to use external tools for creating and editing external reports and data processors is implemented.
Dynamic lists.
For dynamic lists, support of batch queries is implemented. The dynamic list query builder does not support editing batch queries.

This change is not implemented in 8.3.7 repository compatibility mode.

Dynamic lists did not support batch queries.Extended dynamic list capabilities.
Development tools.
In the Syntax Assistant, more information is added to the description of the HTTP service request handler method. This includes the parameter type and the return value type.In the Syntax Assistant, some information was missing from the description of the HTTP service request handler method. It did not provide the parameter type and the return value type.Easier developer access to critical information.
Data display.
Managed forms.
For the StyleColors system enumeration, the following values are implemented:
  • ButtonBorderColor (for form buttons and command bar buttons)
  • TableHeaderBackColor (for table header background)
  • TableHeaderTextColor (for table header text)
  • TableFooterBackColor (for table footer background)
  • TableFooterTextColor (for table footer text)
The following values of the StyleColors system enumeration were used to format form items:
  • BorderColor (for form buttons and command bar buttons)
  • ButtonBackColor (for table header background)
  • ButtonTextColor (for table header text)
  • ButtonBackColor (for table footer background)
  • ButtonTextColor (for table footer text)
Extended style item usage options.
Data display.
Managed forms.
The sizes of form buttons and command bar buttons are changed.

This change is not implemented in 8.3.7 compatibility mode.

Form buttons and command bar buttons had different sizes.Improved button layout.
Technological log.
For the <CALL> technological log event, the Usr property is implemented. It stores the name of the authenticated infobase user.The Usr property of the <CALL> technological log event was not available,The <CALL> technological log event is more informative now.
ZIP archive operations.
 +

For the conf.cfg configuration file, the FileNamesEncodingInZipFile parameter is implemented. It specifies the file name encoding in 1C:Enterprise-generated ZIP archives. It can have one of the following values: UTF8 (UTF8 only) and OSEncodingWithUTF8 (both UTF8 and the operating system encoding). +If the parameter value is UTF8, the ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, display file names with non-English characters inside the archives incorrectly. The built-in decompression program from OS X displays such file names correctly.

If the parameter value is OSEncodingWithUTF8, the built-in decompression program from OS X displays file names with non-English characters incorrectly but other decompression programs display them correctly.

File names in 1C:Enterprise-generated ZIP archives were always stored in both UTF8 encoding and operating system encoding.The option to specify encoding for the file names in 1C:Enterprise-generated ZIP archives is implemented.
DBMS operations.
System requirements.
IBM DB2 11.1 DBMS is now supported.IBM DB2 11.1 DBMS was not supported.IBM DB2 11.1 DBMS is now supported.
Administration tools.
The administration console utility (1cv8a) is available. It includes some of verification and repair features that are available in Designer. You can use the utility to speed up certain operations:
  • Verify and repair exchange plan node tables
  • Verify and repair hash fields in infobase tables

The utility is available for the following operating systems:

  • Windows. Installed as a part of the Administration of 1C:Enterprise server component.
  • Linux. Installed unconditionally as a part of the 1c_enterprise83-client-8.3.* package that depends on the 1c_enterprise83-server-8.3.* package of the same version.
  • macOS. Installed unconditionally as a part of 1C:Enterprise.
This feature was not provided.

Some of the utility features were available as part of the Verify and repair feature in Designer but they took much more time.

Now you do not have to start Designer to fix some of the infobase issues. This can save valuable time because the utility only processes objects with issues detected and performs a limited set of repair operations.
1C:Enterprise script.
Configuration extensions.
Administration tools.
Unsafe operation protection is implemented. When a potentially unsafe operation is attempted, 1C:Enterprise displays a warning that contains its description and why it might be unsafe. Potentially unsafe operations include:

  • Loading an external report, an external data processor, or a configuration extension
  • Loading or updating a configuration or an extension
  • Attempting the following operations from an external report, an external data processor, or a configuration extension:
    • Run an operating system command
    • Manage users
    • Load an add-in

You have the option to allow or deny a potentially unsafe operation. In some scenarios you have to retry the operation after allowing it.

When you load or update a configuration from a .cfu file, 1C:Enterprise adds the warning to existing Designer dialog boxes.

The InfoBaseUser.UnsafeActionProtection property is implemented. The ConfigurationExtension.UnsafeActionProtection property is implemented. For the Connect() method of ExternalReports and ExternalDataProcessors objects, the UnsafeActionProtection parameter is implemented. In the configuration extension management dialog boxes (both in Designer and in the standard functions), the Unsafe operation protection check box is implemented.

You can define the list of infobases where unsafe operation protection is disabled. For the conf.cfg file, the DisableUnsafeActionProtection parameter is implemented.

Unsafe operation protection was not available. Administrators could prohibit running external reports or data processors using security profiles.Increased security when running potentially unsafe script.
1C:Enterprise script.
Configuration extensions,.
External reports and data processors.
Administration tools.
In the thin and thick client applications, if unsafe operation protection triggers, once the unsafe operation is completed, the application execution continues as if it was not paused. If the user prohibits the unsafe operation, the platform generates an exception that can be caught using 1C:Enterprise script.

The web client and server behavior is not changed.

In the thin and thick client applications, if unsafe operation protection triggered during the execution of the client script, the platform paused the script execution and prompted the user to allow or prohibit the operation. Regardless of the user choice, the script execution was not resumed and the user had to restart the operation.Simplified application behavior in scenarios where unsafe operation protection triggers in a thin or thick client application.
System requirements.
1C:Enterprise now supports Microsoft Windows Server 2016 (x86-64).1C:Enterprise did not support Microsoft Windows Server 2016 (x86-64).The list of supported operating systems is extended.
System requirements.
Astra Linux Special Edition 1.5 is supported.This release was not supported.New Linux release is supported.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Interface.
In the Taxi interface, the appearance of scroll bars is changed.In the Taxi interface, scroll bars had a different appearance.Better visibility of scroll bars in managed forms.
Interface.
In the search dialog box that can be opened from a managed form table linked to a FormDataCollection attribute, the order of fields is changed: the Search in field comes before the Find field.In the search dialog box that could be opened from a managed form table linked to a FormDataCollection attribute, the Find field came before the Search in field.Unified look and feel of search dialog boxes in managed form fields linked to various data types.
Managed forms.
In the Taxi interface, the following keyboard shortcuts are implemented for the managed form navigation panel:
  • Go to panel: Alt + 4.
  • Go to next/previous panel item: Tab/Shift + Tab or Left Arrow/Right Arrow. Upon reaching the first/last item, the focus does not move to the last/first item.
  • Go to the first panel item: Home.
  • Go to the last panel item: End.
  • Exit panel navigation mode: Esc.
In the Taxi interface, keyboard shortcuts for moving through navigation panel items were not available.

+

Improved usability of 1C:Enterprise client applications that use the Taxi interface.
Interface.
In the Taxi interface, in dynamic lists, the vertical scrollbar is replaced with a set of buttons (go to beginning, go to end, page up, and page down) located at the right bottom part of the table linked to a dynamic list.Tables linked to dynamic lists had vertical scroll bars that did not provide comfortable navigation.Improved navigation in dynamic lists.
Interface.
Dynamic lists.
The following commands are added to the context menu of a table linked to a dynamic list whose main table is a document list or a document journal: Post and Clear posting.For a table linked to a dynamic list whose main table was a document list or a document journal, the Post and Clear posting commands were only available on the More menu.

+

Simplified posting and clearing posting in dynamic lists.
Interface.
Dynamic lists.
The context menu of a managed form table that is linked to the main attribute of a managed list form having the Generate command now includes a Generate submenu.The generation commands were only available in the command bar of a managed form table linked to the main attribute of a managed list form.Simplified document generation based on dynamic lists.

+

Interface.
In the thick and thin clients, in the managed mode, the option to add a search string to the system command area is removed from all interface modes.The option to add a search string to a system command area was available.Removed a feature that was no longer in use.
Interface.
The system command area displays the current user name. It is a hyperlink that opens a dialog box with the user info. The dialog box includes the option to log out of the client application. If the user is authenticated using OpenID, this also cancels OpenID authentication (so that a single command both exits the application and cancels OpenID authentication). If the infobase does not have users, the user name is not displayed.

The option to specify the URL that is opened after the exit from the web client in the .vrd file is implemented (you can also specify the URL in the publishing settings dialog box in Designer, and then the platform writes it to the .vrd file). The <exitURL> element of the <point> element of default.vrd file is implemented.

This change is not implemented in 8.3.7 compatibility mode.

The exit command and the cancel OpenID authentication command were available on the File menu.Client application behavior is closer to the standard behavior of web applications.
Web client.
Managed forms.
In the web client, streamlined the undo operation in text document fields and input fields.

In Safari web browser for Apple iPad, the undo operation is applied to an entire word (and not to each of its characters), just like it is implemented in other web browsers.

In the web client, the undo and redo operations were not optimal.Improved usability of text operations in the web client.
Client application.
On Windows 7 and later and on Linux with Unity desktop shell, support of jump lists is implemented. The last used infobases are automatically added to a jump list, so that a user can open these infobases without opening the 1C:Enterprise start dialog box.

On Windows 7 and later, the option to define buttons that are displayed in the application preview taskbar window (using 1C:Enterprise script) is implemented. This is similar to Windows Media Player buttons in its preview window.

On Windows 7 and later and on Linux with Unity desktop shell, the option to define a picture or a number to be displayed at the bottom right corner of the application taskbar icon (using 1C:Enterprise script) is implemented.

On Windows XP and later and on Linux with Unity desktop shell, the option to enable blinking of a taskbar application icon (using 1C:Enterprise script) is implemented.

The OSTaskbarManager object is implemented. +

This feature was not provided.Inproved usability of 1C:Enterprise applications on some operating systems.
Client application.
Interface.
1C:Enterprise user interface now has screen reader support, which provides accessibility for blind and visually impaired people. This option is available on Windows XP or later. It uses the NVDA screen reader software (read more).

Screen reader support is only available for managed forms, in the thick and thin clients that use the Taxi interface.

This feature was not provided.Improved 1C:Enterprise usability for blind and visually impaired people due to screen reader support.
Dynamic lists.
In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) is implemented.

Adding subordinate fields is available for fields whose type includes at least one reference type.

In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) was not available.Improved data display capabilities in dynamic lists.
Web client.
File operations.
In the web client, a CreateDirectory() or BeginCreatingDirectory() method call includes the question to the user: Do you want to create the DirectoryName directory?

In the RequestUserPermission() and BeginRequestingUserPermission() method calls, this confirmation is included in the final question to the user (provided that the confirmation is needed).

In the web client, directories were created without user confirmation.The platform behavior conforms to the general security recommendations for file operations in the web client.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Server clusters.
Optimized operations with session data. The lags experienced by end users during the periods of high load on the session data storage in client/server mode are eliminated.Operations with session data required optimization. End users experienced lags during the periods of high load on the session data storage in client/server mode.Improved 1C:Enterprise usability.
Interface.
The impact on the total number of opened forms to the opening of new forms is reduced.The impact on the total number of opened forms to the opening of new forms was significant.Streamlined form opening when many other forms are open.
Queries.
In the query language, <EXPRESSION> OR TRUE expressions are optimized.

This change is not implemented in 8.3.7 compatibility mode.

The query language did not feature additional optimization of query texts.In some scenarios, the optimization increases the performance of dynamic lists and access restriction queries because the DMBS generates a simpler query plan.
Development tools.
The dump configuration to files and restore configuration from files operations are optimized for scenarios where the configuration includes a large number of managed forms.The performance of dump configuration to files and restore configuration from files operations was insufficient.In scenarios where the configuration is stored in an external system, improved performance of data exchange between the infobase and that system.
Database operations.
File infobase operations are optimized in the scenario where all of the following conditions are met:
  • A single client application accesses the infobase (Designer counts as a client application, too).
  • The client application and the database are located on different computers.
  • Both computers support SMB 2.1 protocol (operating system Windows 7 or later).
  • A significant number of database write transactions are performed.
In the specified scenario, the file infobase performance was insufficient.Improved performance of database configuration updates for file infobases in the scenario where Designer and the database are located on different computers.
Data exchange.
The performance of initial infobase image creation is improved.

The performance or reading records from independent nonperiodic information registers during the initial image creation is improved.

The performance of initial infobase image creation was insufficient.Faster creation of subordinate node infobases in distributed infobases.
DBMS operations.
Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized.The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient.Improved performance of temporary table operations.
DBMS operations.
In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) have a different execution algorithm when applied to lists containing more than 100 records.

This change is not implemented in 8.3.7 compatibility mode.

+

+

+

In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) had a different execution algorithm when applied to lists containing more than 1000 records.Improved performance for some scenarios that include access to Oracle Database DBMS.
Administration tools.
Technological log.
Server clusters.
DBMS operations.
Getting DBMS lock data is optimized. The time required for getting the data does not depend on the number of infobases in the cluster.

The server cluster service that collects DBMS lock data is implemented. It is named AuxiliaryService (Utility cluster service).

The option to manage the collection of DBMS lock data is implemented in the technological log (<DBMSLOCKS> element). Enabling the data collection increases the DBMS load.

The time required for getting DBMS lock data depended on the number of infobases in the cluster.

The option to manage the collection of DBMS lock data using the technological log was not available.

+

Extended database diagnostics.
Administration tools.
Database operations.
In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (1Cv8.1CD) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes.

If you set the page size for a database having version 8.3.8 format to 8192 bytes or more, the internal database file size cannot exceed 6 GB.

1C:Enterprise version 8.3.8 can open infobases created in the earlier 1C:Enteprise versions (and having version 8.2.14 database format) without changing their compatibility modes.

By default, new infobases have version 8.2.14 format. For the conf.cfg file, the DBFormatVersion parameter is implemented. It defines the format of newly created file-mode infobases.

For the infobase connection string, the DBFormat and DBPageSize parameters are implemented. They define the format and page size for new infobases.

To migrate data between infobase formats, you can use a .dt file (provided that the target infobase has the required format) or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion.

All infobases had the same format (version 8.2.14). Pages of the infobase file had fixed size: 4096 bytes. The option to change the size was not available. The internal database file size could not exceed 4 GB.For infobases with large page sizes, the infobase opening time is reduced and the performance of some queries is improved.
Server clusters.
Reduced size of session data on the hard disk. Session data is stored in the server cluster in compressed form.Session data was stored in the server cluster in uncompressed form.The space occupied by internal cluster data is reduced. Some of the internal cluster operations are streamlined.
Client application.
Faster thin client startup in the file mode.The performance of the thin client startup in the file mode was insufficient.Faster thin client startup in the file mode.
Database operations.
Restructuring of separated hierarchical catalogs is optimized.The performance of restructuring separated hierarchical catalogs was insufficient.The performance of restructuring separated hierarchical catalogs is improved.
Database operations.
The RAM usage is reduced for restructuring a database that contains large amounts of binary data in file mode.Restructuring a database that contained large amounts of binary data in file mode might result in an unexpected shutdown due to insufficient RAM.Improved system stability for database restructuring in file mode.
Interface.
Server clusters.
For 1C:Enterprise installations that use Microsoft SQL Server, improved performance of opening user work history.

The performance improvement will take effect after you perform the following steps:

  • Set the compatibility mode to version 8.3.8 or later.
  • Perform complete infobase restructuring or dump the infobase to a .dt file and then restore it.
For 1C:Enterprise installations that used Microsoft SQL Server, opening user work history was slower.Improved performance of opening user work history.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Software licensing.
Administration tools.
The command-line utility for software license management (which includes license activation, getting license data, getting the list of licenses, and more) is implemented. The utility is delivered in two distribution packages, which are located in the ExtDst subdirectory of the platform version directory (provided that the thick client or 1C:Enterprise server is installed for this platform version). The utility is not installed automatically. In order to use it, you have to install it first. The utility is available for Windows operating system (both architectures) and for Linux operating system (both architectures, as .deb- and .rpm packages).

To access the utility, use the ring license command. The utility requires Java version 8. The detailed utility description is available in 1C:Enterprise documentation.

Software license activation was only available in the interactive mode. No other software management options were available.Simplified software license management on the end-user computer.
Managed forms.
During the automatic generation of managed form items, the names of items that match the CreateByParameter and ShowInList commands are generated according to the following template: <Form><CommandName><ConfigurationObjectName>.

This change is not implemented in 8.3.7 compatibility mode.

During the automatic generation of managed form items, the names of items that matched the CreateByParameter and ShowInList commands were generated according to the following template: <Form><CommandName><SequentialNumber>.

+

Better usability for applied solution developers.
Managed forms.
In a managed form, the width of a drop-down list of an input field is adjusted according to the width of data displayed in that list.

Pressing the Home or End key (as a single key or with any modifier keys) is handled directly in the input field.

In a managed form, each drop-down list of an input field had a fixed width set by the platform or by a developer.

Pressing the Home or End key (as a single key or with any modifier keys) in an input field had no effect.

Improved usability of input fields in drop-down lists.
Development tools.
The following features are implemented in the compare and merge modules window :
  • Module line numbers
  • Synchronization between the comparison window and the merge result editor window
  • The editor window functionality is closer to that of 1C:Enterprise script editor window
  • Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging)
  • The window title displays the module name

The following features are implemented in the window that displays the result of merging with a third-party tool:

  • The editor window functionality is closer to that of 1C:Enterprise script editor window
  • Context help is available in the editor window. The context includes the main configuration (before merging) and the current module (after merging)

When a supported configuration is being updated, the compare and merge configurations window has a new filter option: Show only properties with merge conflicts. The filter displays the objects that are not merged with a third-party tool.

This feature was not provided.Improved usability for developers working on applied solution update functionality.
Development tools.
The Explanation field of the property palette displays Russian property names only when the Russian 1C:Enterprise script variant or the Russian platform interface is selected.The Explanation field of the property palette always displayed both Russian and English property names.

+

Improved Designer usability for English-speaking developers.
Web client.
Spreadsheet documents.
In the web client, the option to display a background picture and a pattern in a spreadsheet document cell is implemented.In the web client, displaying background pictures and patterns in spreadsheet document cells was not supported.Extended spreadsheet document style options in the web client.
Data display.
Spreadsheet documents.
In spreadsheet documents exported to PDF format, font substitution for characters that are not available in the current font is implemented.

This change is not implemented in 8.3.7 compatibility mode.

+

In spreadsheet documents exported to PDF format, characters that were not available in the current font were displayed as missing characters (squares).In spreadsheet documents exported to PDF format, non-English characters are displayed correctly.
Spreadsheet documents.
When a spreadsheet document is exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells is implemented.

This option is not available when exporting spreadsheet documents to XLS (Microsoft Excel 95) format.

This change is not implemented in 8.3.7 compatibility mode.

When a spreadsheet document was exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells was not supported.Better conversion of spreadsheet documents to Microsoft Excel and ODS formats.
Configuration extensions.
When an attribute of composite type that does not include references to configuration objects is adopted, the composite type is fully adopted. During the next adoption attempt, the composite type is supplemented with the set of types from the main configuration.

When an attribute of composite type that includes references to configuration objects (nonprimitive types) is adopted, it is adopted as AnyRef. During the next adoption attempt, the AnyRef type is only added if the type is no longer composite and does not include CatalogRef, DocumentRef, and similar types.

When a configuration extension is attached, the following rules apply:

  • If an extension configuration attribute type includes AnyRef, this requires the matching main configuration attribute type to include any reference.
  • If an extension configuration attribute type includes CatalogRef, DocumentRef, and similar types, this requires the matching main configuration attribute to include any reference type of that kind.

If an attribute of composite type cannot include AnyRef type, any composite type adopted for this attribute is adopted with a single Arbitrary type. Such attributes cannot cause configuration extension attachment errors.

When a composite type was adopted, primitive types were always adopted, and a single type from the configuration object reference types was adopted.

When a configuration extension was attached, the following rule applied: if an extension attribute type included composite types, this required the matching main configuration attribute to include exactly the same composite types.

Simplified usage of composite types in configuration extensions.
Web services and HTTP services.
During a web service call, if an internal server infrastructure error that is not related to SOAP occurs, the error message contains the correct diagnostics text. The web service call error message is more detailed and can include data from the faultfactor (Node) and Role tags of the web service response.During a web service call, if an internal server infrastructure error that was not related to SOAP occurred, an incorrect error message was displayed, and the information about the actual error cause was lost.

The web service call error message did not include additional details from the web service response.

+

The web service call error message is more detailed, which simplifies error diagnostics.
Background and scheduled jobs.
When a client application is started with a file infobase, there is a 2-minute delay before starting the execution of scheduled jobs.When a client application was started with a file infobase, there was a 1-minute delay before starting the execution of scheduled jobs.Faster startup of client applications in file mode.
Web client, web service, and HTTP service publishing tools.
When a user disables publishing to a web server from Designer, they are prompted to restart the web server.When a user disabled publishing to a web server from Designer, they were not prompted to restart the web server.Users are given better understanding of the disable publishing operation, since the publishing is actually disabled when the server is restarted.
Development tools.
In Designer, the option to customize the background of the context method parameter help is implemented.

In the context help, links to the Syntax Assistant have the Identifiers color and normal text has the Miscellaneous color.

In the context help, links to the Syntax Assistant had the default Identifiers color and normal text had the default Miscellaneous color.You can customize the context help of method parameters to make it readable when the module editor color scheme has dark background.
XML and XDTO support.
Web services and HTTP services.
In the XDTO model, new properties are implemented. They ensure correct processing of XSD schemas with any combinations of the following attribute values: elementFormQualified (Qualified element form package property), attributeFormQualified (Qualified attribute form package property), and form (property of the Qualified element).

The XDTO package editor provides the option to view and edit the new properties. In Version 8.3.7 or earlier compatibility mode, the new properties have their default values.

When processing XSD schemas, the XDTO model ignored actual values of elementFormDefault and attributeFormDefault attributes. It also ignored the form attribute of XSD schema elements and attributes. Instead, it always used the following values:
  • elementFormDefault was always qualified.
  • attributeFormDefault was always unqualified.

+

Extended list of web services that are compatible with 1C:Enteprise as they are, without any manual corrections to their descriptions.
Administration tools.
The wizards used to add and edit infobases are refactored, the number of wizard pages is reduced.

Automatic detection of the infobase connection type is implemented, based on the string stored in the clipboard or the string entered in the Specify infobase name field. This includes the detection of the path to a file infobase or the URL for accessing an infobase running on a web server. Once the infobase type is detected, all of the related wizard fields are filled in.

The wizards used to add and edit infobases were more complex and had more pages.Simplified adding of infobases to the list.
Managed forms.
If an input field of a managed form displays ValueList data, the value list form that is opened for editing the data gets the following properties from the input field:
  • ChoiceParameters, supplemented with values based on the ChoiceParameterLinks property
  • ChoiceForm (in the web client)
  • ChoiceFoldersAndItems (in the web client)
  • Mask
  • EditFormat
  • QuickChoice
  • TypeLink
If an input field of a managed form displayed ValueList data, the value list form that was opened for editing the data received the following properties from the input field:
  • ChoiceParameters, not supplemented with values based on the ChoiceParameterLinks property
  • ChoiceForm (thin client only)
  • ChoiceFoldersAndItems (thin client only)
Eliminated unexpected system behavior.
Full-text search.
Input by string.
Dynamic lists.
Input by string and full-text search in dynamic lists find data that is not yet indexed for the full-text search.Input by string and full-text search in dynamic lists did not find data that was not yet indexed for the full-text search.Data that is not yet indexed for the full-text search is included in full-text search results and input by string results.
Managed forms.
In the Taxi interface, the appearance of managed form buttons and command bar buttons is changed.

For the CommandBarButton and CommandBarHyperlink buttons, support of the following properties is implemented: BackColor, TextColor, Font, BorderColor (except CommandBarHyperlink buttons). For form group extension submenus, support of the following properties is implemented: BorderColor, BackColor, TitleTextColor, and TitleFont. This change is not implemented in version 8.3.7 compatibility mode and in version 8.2 interface compatibility mode.

For the standard Copy command of dynamic list table extension:

  • The Auto value of Representation property is equivalent to Picture.
  • The Auto value of OnlyInAllActions property is equivalent to No.

For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property is equivalent to No. These commands are included in a compact button group. +

This change is not implemented in version 8.3.7 compatibility mode.

In version 8.3.7 compatibility mode with compact interface the button height in the thin client differs from the button height in the web client.

In the Taxi interface, the appearance of managed form buttons and command bar buttons was different.

The CommandBarButton buttons had BackColor, TextColor, Font, and BorderColor properties, which were never used. Form group extension submenus had BorderColor, BackColor, TitleTextColor, and TitleFont properties, which were never used.

For the standard Copy command of dynamic list table extension:

  • The Auto value of Representation property was equivalent to Text.
  • The Auto value of OnlyInAllActions property was equivalent to Yes.

For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property was equivalent to Yes.

Improved form creation capabilities in the Taxi interface.

The default location of some frequently used buttons (Copy in dynamic lists and row movement commands in other tables) changed from the More menu to the command bar.

Managed forms.
The option to display command bar commands as hyperlinks is implemented. Pop-up menus do not support displaying commands as hyperlinks. For the FormButtonType enumeration, the CommandBarHyperlink value is implemented. In 8.3.7 compatibility mode, the FormButtonType.CommandBarHyperlink value is treated as FormButtonType.CommandBarButton.

In the Taxi interface, the option to set horizontal picture alignment for managed form buttons is implemented. Pop-up menus do not support this feature. For managed form buttons, the PictureLocation property is implemented. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.

The option to set command bar button spacing is implemeneted. Managed form group extension for a button group is implemented. Pop-up menus do not support this feature. The ButtonGroupRepresentation system enumeration is implemented. In 8.3.7 compatibility mode and version 8.2 interface compatibility mode, the button spacing value is ignored.

The option to set button shape (except pop-up menu buttons) is implemented. For managed form buttons and form group extensions for popups, the Shape property is implemented. Pop-up menu commands do not support this property. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.

The option to set managed form button shape is implemented. For managed form buttons and form group extensions for popups, the ShapeRepresentation property is implemented. The ButtonShapeRepresentation system enumeration is implemented. Pop-up menu commands do not support this feature. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode.

Command bar commands could not be displayed as hyperlinks.

The option to set horizontal picture alignment for managed form buttons was not available.

The option to set command bar button spacing was not available.

The option to set button shape was not available.

The option to set command bar button appearance was not available.

More managed form appearance options in the Taxi interface.
Managed forms.
Recommendations about the usage of user messages are added to the documentation. The recommendations are aimed to reduce the chance of situations where users cannot read the displayed messages.The documentation did not contain the recommendations aimed to reduce the chance of situations where users cannot read the displayed messages.The documentation is improved.
Software licensing.
Updates of Windows 10 operating system never deactivate software licenses. +The software licensing system was not fully compatible with Windows 10. Updates of Windows 10 could deactivate a software license.Improved compatibility of the software licensing system with Windows 10.
Localization.
The Kazakh interface language (language code: kk) is not supported.The Kazakh interface language (language code: kk) was supported.The Kazakh interface language is not supported.
Regional settings.
For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ (Zabaikalye Territory), 27-FZ (Astrakhan Region), 57-FZ (Altai Territory), 58-FZ (Republic of Altai), 59-FZ (Sakhalin Region), 69-FZ (Ulyanovsk Region), 87-FZ (Magadan Region), 109-FZ (Tomsk Region), 271-FZ (Novosibirsk Region), and 395-FZ (Saratov Region). This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, 87-FZ, 109-FZ, 271-FZ, and 395-FZ.The time offset changes introduced by the new law are implemented.
Spreadsheet documents.
Text copied from Microsoft Excel speadsheet cells is fully pasted to 1C:Enterprise spreadsheet cells, regardless of its length.Text copied from Microsoft Excel spreadsheet cells and pasted to 1C:Enterprise spreadsheet cells was cut, only the first 255 characters were copied.Eliminated unexpected system behavior.
Spreadsheet documents.
Improved processing of data having date and time format during the import from Microsoft Excel:
  • For standard Microsoft Excel formats, matching 1C:Enterprise format strings are applied.
  • 1C:Enterprise format strings are defined based on the locale codes explicitly specified in Microsoft Excel format strings.
  • The date type uses the first short date format separator found in the infobase.
  • Dates where the month is specified by its first letter are converted to 1C:Enteprise dates having short month presentation.

This change is not implemented in 8.3.7 compatibility mode.

Processing of data having date and time format during the import from Microsoft Excel was performed as follows:
  • A fixed list of standard Microsoft Excel formats was applied.
  • Locale codes explicitly specified in Microsoft Excel format strings were ignored. The current infobase settings were used instead.
  • The date type always used the slach (/) separator.
  • Dates where the month was specified by its first letter were converted to dates having full month presentation.
Improved accuracy of date and time import from Microsoft Excel.
Web services and HTTP services.
For configurations that include HTTP services, setting compatibility mode to Version 8.3.4 or earlier is allowed.

If your configuration includes HTTP services and you previously opened it with 1C:Enterprise Designer 8.3.4, when you open it with 1C:Enterprise 8.3.8, perform the following steps:

  • Create any configuration object.
  • Save the infobase configuration.
  • Delete that configuration object.
  • Save the infobase configuration.
In 1C:Enterprise 8.3.7 or earlier, if a configuration included HTTP services, setting its compatibility mode to Version 8.3.4 or earlier was not allowed.You can add HTTP services to configurations that run in compatibility mode Version 8.3.4 or earlier.
Client application.
Internet-enabled functionality.
You have the option to select the set of external resources that the platofrm uses (in ExternalResourcesMode parameter of conf.cfg configuration file). +If this parameter is not specified, the platform selects its value automatically.This feature was not provided.You have the option to select the set of external resources that the platofrm uses.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Internet-enabled functionality.
The NSSSecureConnection object and NSS certificates are no longer available for use in 1C:Enterprise script.1C:Enterprise supported NSS certificates in 8.3.6 compatibility mode.Support of NSS certificates is discontinued.
Internet-enabled functionality.
Support of TLS protocol versions 1.1 and 1.2 is implemented for scenarios where the client certificate is not specified in the connection settings. The SSL protocol version 3.0 is only used when the client application is started with /HttpsForceSSLv3 command-line option. In all other scenarios SSL version 3.0 is not used.

1C:Enterprise ignores the AllowSSLv3 parameter in conf.cfg file.

The InternetMail object does not support SSL version 3.0.

1C:Enterprise only supported TLS protocol version 1.0.

The AllowSSLv3 parameter was available for use in conf.cfg file.

The InternetMail object supported SSL version 3.0.

+

Increased security of connections established by client applications for Internet operations.
Internet-enabled functionality.
The platform no longer uses cacert.pem file for creating HTTPS/FTPS connections.

The platform uses the root certificate store of the operating system for creating HTTPS/FTPS connections.

This change is not implemented in 8.3.7 compatibility mode.

The platform used cacert.pem file for creating HTTPS/FTPS connections in scenarios where no certificate stores were specified explicitly.The outdated technology is no longer supported.
Managed forms.
For managed forms, the option to update data presentations only for the specified set of form items is implemented. For the RefreshDataRepresentation() method, the UpdateItems parameter is implemented. For the EditTextUpdate system enumeration, the Always value is implemented.The option to specify a set of form items when updating data presentations using the RefreshDataRepresentation() method was not available.Form data can be updated in idle handlers without losing the text being edited in a text box.
Dumping/loading configurations to files.
The dump of the Source property of the FormItemAddition object to a file is more human-readable.

You can restore configuration from files having both property dump formats.

The dump of the Source property of the FormItemAddition object to a file was less human-readable.Dumping configurations to files produces files that are more human-readable.
XML and XDTO support.
Development tools.
Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) is much more detailed.

During the creation of WSDefinitions object, exceptions are raised if the used WSDL description has errors.

The WSDL description used to create WSDefinitions or WSReference objects must comply with the following rules:

  • Its first tag is <definitions>.
  • It includes the targetNamespace attribute of the <xs:schema> element.
  • If it does not comply with the rules, an exception is raised.

This change is not implemented in 8.3.7 compatibility mode.

Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) was not sufficiently detailed.

During the creation of WSDefinitions object, if the used WSDL description had errors, invalid elements were ignored.

If the first tag of the WSDL description used to create WSDefinitions or WSReference objects was not <definitions>, empty web service description objects were created.

If the WSDL description used to create WSDefinitions or WSReference objects did not include the targetNamespace attribute of the <xs:schema> element, the platform set a pseudorandom namespace.

Better diagnostics for WSDL description operations.
Queries.
If a constant stores a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that includes a request to the Value field returns a value of that type.

This change is not implemented in 8.3.7 compatibility mode.

If a constant stored a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that included a request to the Value field returned a value of BinaryData type.Eliminated unexpected system behavior.
Print tools.
The following behavior of the RepresentableDocumentBatch.Print() method is implemented:
  • On Windows:
    • Create a single printer job.
    • Output the entire batch to a file, prompt for the file name before the output.
  • On Linux:
    • If all documents in the batch have identical print settings, use the Windows scenario.
    • If the print settings are different, create a printer job for each document.

This change is not implemented in 8.3.7 compatibility mode.

The RepresentableDocumentBatch.Title, property is implemented. It is used for generating the batch presentation.

The RepresentableDocumentBatch.Print() method created a job for each document in a batch.Improved printing of document batches.
Data composition system.
Text and Format conditional appearance items are applied to fields of chart grouping templates of data composition systems regardless of the previous Format value (even if the previous value is taken from the data composition system). Text conditional appearance item has higher priority than Format conditional appearance.

This change is not implemented in 8.3.7 compatibility mode.

Text and Format conditional appearance items were applied to fields of chart grouping templates of data composition systems only if the Format conditional appearance was not applied to those fields earlier.Eliminated unexpected system behavior.
Data composition system.
The MarkNegatives conditional appearance property is only used if this property is set to True and the Use conditional appearance property is also set to True.

This change is not implemented in 8.3.7 compatibility mode.

The MarkNegatives conditional appearance property was only used if the Use conditional appearance property was set to True.Eliminated unexpected system behavior.
Data composition system.
In the query language, the CASE operation result is based on all expression types from all THEN branches of that expression.

This change is not implemented in 8.3.7 compatibility mode.

In the query language, the calculation of CASE operation result ignored all THEN branches that included constant expressions with NULL values.Eliminated unexpected system behavior.
Full-text search.
The option to set a size limit for data indexed for the full-text search is implemented. The default size limit is 1 MB.

For the FullTextSearchManager object, the SetMaxIndexedDataSize() and GetMaxIndexedDataSize() methods are implemented.

The <FTEXTSKIP> technological log event is implemented.

This change is not implemented in 8.3.7 compatibility mode. +

The option to set a size limit for data indexed for the full-text search was not available. All infobase data was indexed.You can limit the full-text search scope by excluding large blocks of data you do not need to search. This increases the performance of full-text search indexing and reduces the index size.
Client application.
Internet-enabled functionality.
Administration tools.
The algorithm that retrieves the list of infobases and platform updates over HTTPS no longer uses the cacert.pem file, which is included in the platform distribution kit.

On Linux, the platform gets certificates from the certification centers specified in the operating system. On Windows, the platrorm uses the operating system root certificate store.

On Windows, the platform used the cacert.pem file and the operating system root certificate store in order to check an HTTPS connection.

On Linux, the platform used the cacert.pem file only.

Simplified administration of platform update over HTTPS.
Linux.
System requirements.
The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system is refactored. The fontconfig library is used to get the list of fonts. This library is included in the system requirements.

The list of directories used for storing fonts is removed from 1C:Enterprise documentation.

The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system used a fixed directory list, which was described in 1C:Enterprise documentation.

The fontconfig library was not used for getting the list of fonts.

Extended the list of fonts available to 1C:Enterprise on Linux operating system. Simplified 1C:Enterprise administration.
System requirements.
The type specified for a data composition schema parameter affects the type of query fields that use this parameter.

This change is not implemented in 8.3.7 compatibility mode.

The type specified for a data composition schema parameter did not affect the type of query fields that used this parameter.Data displayed in reports better matches the input parameters.
Dynamic lists.
The dynamic list implementation is refactored in order to increase its quality. The list of virtual dynamic list fields that are not available for use in filter, grouping, and order settings is extended.

If the main dynamic list table does not have key fields (according to 1C:Enterprise script object model) and a grouping is set for this table, an error is generated.

When a filter, sorting, or grouping by a field that is not included in a query is specified using 1C:Enterprise script, an error informing that the field is not found is displayed.

The list of restrictions to queries used to generate dynamic lists is modified.

Dynamic list sorting specifics are described in the documentation.

The description of algorithms that dynamic lists use for getting data is changed.

The standard row picture is generated based on the standard attributes. If a query includes fields whose aliases are identical to standard attribute names and these fields store other data, these fields are not used in standard picture generation.

If a dynamic list filter cannot be converted to a query language expression, an error is generated.

Dynamic list column data that is not displayed and does not have the Use always property set is not sent to the client. Client access to such columns is not available.

If a dynamic list column has the Use always property but the current user does not have the View right for that column, the column data is not sent to the client. Client access to such columns (using the CurrentData property or the RowData() method) is not available.

Automatic dynamic list filters for standard Owner, Parent, Date, Period, and IsFolder fields are applied using data composition system tools.

Automatic dynamic list filters for key fields can be applied using data composition system tools or using direct addition of main table filter conditions to query texts.

When a filter is applied using data composition system tools, it can be applied in nested queries and virtual table parameters. This can significantly change the dynamic list data selection result (compared to the result obtained in 8.3.7 compatibility mode).

The detailed description of all the changes listed above is included in the documentation.

This change is not implemented in 8.3.7 compatibility mode.

The following virtual fields were not available in dynamic list sorting and grouping settings: DataVersion, PredefinedDataName, tabular sections fields, and fields having the following types: Type, String (unlimited length), and BinaryData (unlimited length).

The list of restrictions to the grouping and ordering settings was different and it was not full.

If the main dynamic list table did not have key fields (according to 1C:Enterprise script object model) and a grouping was set for this table, the content of data to be displayed was undefined.

When a filter by a field that was not included in a query text was set, the filter might be applied without displaying any errors, or ignored. If grouping or sorting by a field that was not included in a query was specified using 1C:Enterprise script, the field was ignored. +The list of restrictions to queries used to generate dynamic lists was different.

The list of dynamic list sorting specifics was not documented. +The description of algorithms that dynamic lists used for getting data was different.

If a dynamic list query had fields with aliases matching the names of standard attributes used to generate standard row pictures, they were used in the generation of standard pictures (except the IsFolder attribute). +If a dynamic list filter could not be converted to a query language expression, the filter was applied by data composition schema processor after getting the data, and this might reduce the amount of displayed data.

If dynamic list settings included grouping or sorting fields that were unavailable (before applying rights and functional options), these fields were ignored. +

In some scenarios dynamic list column data that was not displayed and did not have the Use always property set was sent to the client.

If dynamic list column had the Use always property but the current user did not have the View right for that column, the column data was sent to the client. In this scenario the default values of specific data types were used as column values.

Automatic dynamic list filters for key fields and for standard Owner, Parent, Date, Period, and IsFolder fields were applied by direct addition of their conditions to query texts.

Improved quality and reliability of dynamic lists. More details about dynamic list specifics are added to the documentation.
Background and scheduled jobs.
When a nonserializable value is passed to BackgroundJobs.Execute() method as a background job parameter, the background job is not started and an exception is raised.

This change is not implemented in 8.3.7 compatibility mode.

When a nonserializable value was passed to the BackgroundJobs.Execute() method as a background job parameter, the background job was started and the Undefined value was stored to that parameter. This did not raise any exceptions.The start of background jobs complies with the global error diagnostic rules.
Administration tools.
During an unexpected shutdown of the thin client, the dump generation includes taking a screenshot (prntscrn attribute of dump element of logcfg.xml file).

+

During an unexpected shutdown of the thin client, the dump generation did not include taking a screenshot.Eliminated unexpected system behavior.
Queries.
The result of division by NULL is treated as a number of unspecified length . This number cannot be used in operations that do not accept numeric operands (such as AND, OR, NOT).

This change is not implemented in 8.3.7 compatibility mode.

The result of division by NULL was not treated as a number and therefore could be used in operations that did not accept numeric operands (such as AND, OR, NOT).Eliminated unexpected system behavior.
Managed forms.
Interface.
The approach to processing the closing of applications and managed forms is changed:
  • The new "exit application" mode is implemented. It requires special processing in the BeforeClose and OnClose managed form event handlers.
  • Opening windows and executing server calls is not allowed in BeforeExit and OnExit managed application event handlers, and also in BeforeClose and OnClose managed form event handlers (provided that the form is in the "exit application" mode).
  • The option to generate a text message prompting the user to confirm or cancel the exit is implemented (in the web client all messages are combined in a single dialog box).

This approach is described in detail in the documentation.

For BeforeClose managed form event handler, the Exit and WarningText parameters are implemented. For OnClose managed form event handler, the Exit parameter is implemented. If BeforeClose or OnClose managed form event handler has the Exit parameter, in version 8.3.7 compatibility mode the parameter is set to Undefined. For BeforeExit managed application module event handler, the WarningText parameter is implemented.

This change is not implemented in 8.3.7 compatibility mode.

Depending on the modality usage mode, different approaches to closing managed forms and the main application window were used.

In some scenarios (especially in the web client) these approaches led to errors that were hard to detect and fix.

Unified approach to closing forms and the main application window, which provides acceptable user interaction capabilities in all client applications.

The implemented platform behavior conforms to the methodology and technical requirements of modern web browsers.

Administration tools.
Client application installation.
When an infobase that has a platform version specified in a local or global list of infobases is started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version is performed regardless of the presence of /AppAutoCheckVersion command-line option. If a version that is not available on the local computer is specified and this version cannot be installed, an attempt to run the infobase with the latest 1C:Enterprise version is made

During the client application update over HTTP, the check for operating system user right to perform this operation is disabled. If the user does not have sufficient rights for installing the client application, the UAC dialog box prompting to confirm the installation on behalf of a user that has administrative rights is displayed. Error diagnostics during the download and installation of the client application distribution kit over HTTP is improved.

In the /AppAutoCheckVersion command-line option, you can explicitly specify whether the search for a specific 1C:Enteprise version is performed.

When an infobase was started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version was only performed if the command line included the /AppAutoCheckVersion option. +During the client application update over HTTP, the check for operating system user right to perform this operation was performed.The usability of selection and update of the client application used to access a specific infobase is improved.

Improved reliability of automatic thin client updates over HTTP.

Administration tools.
When the thin client is installed from a custom distribution kit, a single 1cestart shortcut is created in the 1C:Enterprise folder.When the thin client was installed from a custom distribution kit, the 1C:Enterprise folder included 1cestart shortcut and the Advanced folder with subfolders for each installed 1C:Enterprise version.Reduced number of 1C:Enterprise startup options available after the installation of the thin client.
Administration tools.
In the client application startup command line, the rules for parsing mandatory parameters are modified. If an option that has a mandatory parameter is specified, the parameter must be also specified (or the option must be omitted). Parameters beginning with slash marks "/" are allowed.In the client application startup command line, the rules for parsing mandatory parameters were different. Mandatory option parameters could be omitted. Parameters beginning with slash marks "/" (full file name on Linux) could be treated as command-line options.Eliminated unexpected system behavior.
Administration tools.
1C:Enterprise documentation and Designer help include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode, which were previously missing.

For the infobase creation mode (CREATEINFOBASE), new /DumpResult option is implemented. It enables writing the operation result to a file.

In the file mode, batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option automatically creates an infobase if the database file is not available in the directory.

1C:Enterprise documentation and Designer help did not include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode.

In the file mode, during the batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option, if the dababase file was not found in the specified directory, the user was asked for the confirmation of further actions.

Improved 1C:Enterprise documentation and Designer help. Simplified batch Designer startup in some usage scenarios.
Data composition system.
If a data set field of a data composition schema has an ordering expression specified and the data composition settings include ordering by this field (Descending), the direction speficied in the ordering expression is reversed.

This change is not implemented in 8.3.7 compatibility mode.

If a data set field of a data composition schema had an ordering expression specified, ordering for this field was always taken from the ordering expression, while the direction specified in the field settings was ignored.Eliminated unexpected system behavior.
Managed locks.
Accounting registers.
Managed locks that are set for writing accounting register records in the LockForUpdate mode are set by values of nonturnover extra dimensions only.

When you set a lock for further operations with balances, it is recommended that you do not specify turnover extra dimension values (you can use the LockForUpdate property or explicitly use a managed lock). When you set a lock for further operations with turnovers, specify all the required extra dimenstion values, including the values of turnover extra dimensions (use the managed lock explicitly).

This change is not implemented in version 8.3.7 compatibility mode.

Managed locks that were set for writing accounting register records in the LockForUpdate mode included locks by all extra dimension values.The behavior of LockForUpdate property of accounting register object is better suited for solving typical tasks. In the LockForUpdate mode, the resulting lock does not inlcude turnover extra dimensions, which fits the frequently used scenarios where the lock is used to check the balances but not the turnovers.
Queries.
In a query, if a single system enumeration is retrieved and it is not combined with other types, the GROUP BY operation groups the values of this field regardless of the enumeration value source.

A similar behavior is implemented for UUIDs and references to external data source tables.

This change is not implemented in 8.3.7 compatibility mode.

In a query, if a single system enumeration was retrieved and it was not combined with other types, the GROUP BY operation might not group the values of this field (depending on the enumeration value source).Eliminated unexpected system behavior.
DBMS operations.
For Microsoft SQL Server DMBS, types of table fields that store some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) are changed. New field types are used if no compatibility mode is selected and only after restructuring configuration objects.

To perform database table restructuring with modification of field types, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair).

This change is not implemented in 8.3.7 compatibility mode.

For Microsoft SQL Server DMBS, table fields that stored some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) had different types.Better mapping between the stored types and Microsoft SQL Server table field types.
DBMS operations.
For all DBMS, the structure of indexes by fields of composite type is modified. This reduces the total number of indexes. Such indexes are built if no compatibility mode is selected and only after restructuring configuration objects.

To perform database table restructuring with index update, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair).

This change is not implemented in 8.3.7 compatibility mode.

For all DBMS, the structure of indexes by fields of composite type was different.Reduced number of indexes for tables storing objects with fields of composite types. This increases the performance of operations with these object types.
Configuration extensions.
When a background job is executed, all the configuration extensions available in the session that startes the job are also attached in the background job session. This change is not implemented in 8.3.7 compatibility mode.

For ConfigurationExtensionsManager object, the ExecuteBackgroundJobWithDatabaseExtensions method is implemented. It duplicates the background job execution procedure implemented in earlier 1C:Enterprise versions.

When a background job was executed, all the configuration extensions available in the infobase were attached in the background job session.Background job execution environment is closer to the parent session environment.
Managed forms.
In the thick and thin clients, when a user starts typing in a cell of a managed form table, the AutoComplete event is fired.

This change is not implemented in version 8.3.7 compatibility mode.

In the thick and thin clients, when a user starts typing in a cell of a managed form table, the StartChoice event is fired.The behavior of the input field in the scenario where a user starts typing in a table cell is uniform with other input scenarios.
Technological log.
The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file is added to the documentation. Adding more than 20 <LOG> elements can impact the platform performance.The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file was absent from the documentation.The recommendation to avoid inefficient technological log usage scenarios is added to the documentation.
Automated testing.
A sections panel that is not displayed in the main window because it contains no items is no longer included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method.A sections panel that was not displayed in the main window because it contained no items was included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method.Eliminated unexpected system behavior.
Automated testing.
The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list (instead of accessing it by index) is added to the documentation.The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list was absent from the documentation.Improved 1C:Enterprise documentation.
Managed forms.
The OnClose event handler and the notification specified in the OnCloseNotifyDescription form property are not called when a managed form is closed using the Close() method called in the OnOpen event handler.

This change is not implemented in 8.3.5 compatibility mode.

When a managed form was closed using the Close() method called in the OnOpen event handler:
  • In the web client, the OnClose event handler and the notification specified in the OnCloseNotifyDescription form property were not called.
  • In the thin client, the OnClose event handler and the notification specified in the OnCloseNotifyDescription form property were called.
Unified client application behavior.
Managed forms.
The documentation describes the following platform behavior: when a value is assigned to a variable that is not declared earlier and has a name identical to a property name available in the current context, this can generate a runtime error or a configuration check error. It is recommended that you declare variables with such names using the Var operator to eliminate possible errors.The documentation did not contain a clear description of this scenario.The documentation contains a clear description of a possible scenario and provides recommendations for eliminating possible issues.
Window-based interface.
The order of elements in the collection returned by the GetWindows() method is changed. The documentation and the Syntax Assistant state that the order of elements in that collection does not follow any specific rule and application algorithms must not rely on that order.The documentation did not state that the order of items in the collection returned by the GetWindows() method does not follow any specific rule.The documentation provides more detail about the GetWindows() method.
XML and XDTO support.
An attempt to write an invalid qualified element name generates an exception.

This change is not implemented in 8.3.6 and 8.3.7 compatibility modes.

An attempt to write an invalid qualified element name did not generate an exception. This might produce an invalid XML file.Eliminated unexpected system behavior introduced in version 8.3.6.
Dynamic lists.
If the current user does not have the View right for a dynamic list key field, an attempt to get dynamic list data generates an access violation error.

Information for technical support includes the list of fields that cannot be accessed due to insufficient rights.

This change is not implemented in 8.3.7 compatibility mode.

If the current user did not have the View right for dynamic list key fields, this did not affect the list availability. If a form had conditional formatting based on these key fields, it could not be opened.Eliminated unexpected system behavior.
Data exchange.
Unexpected system behavior during the writing of ThisNode exchange plan object, which was found in 1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861, is eliminated.

If you migrate to a new 1C:Enterprise version:

  • From version 8.3.7 or earlier, no action is reqiured.
  • From version in range 8.3.8.1606 - 8.3.8.1861, it is recommended that after the migration you perform infobase verification and repair with the Check logical infobase integrity check box selected, or use the administration console utility (1cv8a) to verify and repair the infobase.

If your infobase contains objects that refer to exchange plan items and they can contain references to ThisNode item, it is recommended that you correct the references using the Replace references to incorrect ThisNode records data processor (read more). The data processor can use the result provided by the administration console (recommended) of the exchange plan record deletion marks as an input.

It is recommended that you run the cluster administration console (1cv8a) in verification and repair mode, with report generation enabled. Then use the report as an input for the Replace references to incorrect ThisNode records data processor.

1C:Enterprise versions 8.3.8.1606 - 8.3.8.1861 generated incorrect exchange plan records for ThisNode element. This might result in a variety of errors, such as the following:
  • Duplicating ThisNode records
  • Missing ThisNode records
  • Unexpected shutdown when opening an exchange plan list form
  • And more

1C:Enteprise versions 8.3.7 and earlier did not have this issue.

Eliminated unexpected system behavior.
Dynamic lists.
In the source of available data composition system settings for dynamic lists, the following fields are not available for filtering, sorting, or grouping:
  • Fields subordinate to fields that represent aggregate functions of the query language
  • Fields subordinate to fields from other (external) data sources
  • Subordinate characteristic fields of tabular section fields

The search initiated by typing a search string excludes reference fields that represent aggregate functions of the query language.

This change is not implemented in 8.3.7 compatibility mode.

In the source of available data composition settings for dynamic lists, the following fields were available for filtering, sorting, or grouping:
  • Fields subordinate to fields that represented aggregate functions of the query language
  • Fields subordinate to fields from other (external) data sources
  • Subordinate characteristic fields of tabular section fields

When a filter by any of these fields was applied, a dynamic list might display incorrect data (some data or all data might be missing).

An attempt to search in reference fields that represented aggregate functions of the query language initiated by typing a search string might generate errors. If errors we not generated, a dynamic list might display incorrect data (some data or all data might be missing).

The search intiated by typing a search string in dynamic lists is improved.

Reduced number of errors that did not have clear descriptions.

Dynamic lists.
In 1C:Enterprise mode, in a dynamic list with a custom query and the main table specified, the availability of main table fields and their subordinate fields for filtering does not depend on the availability of these fields in the dynamic list query. If main table fields are absent from the query text, they are added implicitly.

If a dynamic list query text includes a field with alias identical to an alias of a main table field, this field is used in the filter, regardless of whether the fields themselves are identical.

Fields having multiple paths (in different 1C:Enterprise script languages) are only available in the current 1C:Enterprise script language.

This change is not implemented in 8.3.7 and earlier compatibility modes.

Only fields available in a query text and standard main table fields (such as Ref) were available for filtering. A filter that included unavailable fields with names indentical to main table field names might be applied without any errors generated.For a dynamic list with a custom query and the main table specified, you can include main table fields that are absent from the query text in choice parameters and choice parameter links.
Accumulation registers.
Accounting registers.
Eliminated unexpected system behavior during the calculation of accumulation register and accounting register totals in scenarios where a dimension list includes a dimension of String type and an index by dimensions includes more that 16 database fields.

When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (read more). The data processor determines whether additional actions are required.

If they are required, after the migration perform infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected, or use the cluster administration console (1cv8a). The latter option is recommended because it is faster.

Accumulation register and accounting register totals might be calculated incorrectly in scenarios where a dimension list included a dimension of String type and an index by dimensions included more that 16 database fields.Eliminated unexpected system behavior.
Internet-enabled functionality.
Web client, web service, and HTTP service publishing tools.
The option to block redirection to potentially harmful sites after completing an OpenID provider operation is implemented. In the default.vrd file, the <returnto> element (subordinate to <provider> element) is implemented. It contains the list of allowed redirection URLs.

Note that publishing OpenID providers from Designer does not support <returnto> elements (existing elements of this type are deleted and new ones are not generated). You have to add these elements manually.

If you migrate to a new 1C:Enterprise verson, requests to OpenID providers that include the openid.return_to parameter will return HTTP error 400.

To eliminate this issue, in the default.vrd file, add the required number of <returnto> elements with available redirection URLs.

The option to affect redirection after completing OpenID provider operations was not provided.Improved security of OpenID provider operations.
System requirements.
The list of supported operating systems and web browsers is changed:
  • Thin client, thick client, web client, and 1C:Enterprise server (Windows versions):
    • Windows XP Service Pack 3
    • Windows Vista or later with the latest updates
    • Windows Server 2003 or later with the latest updates
  • On Windows and Linux, Mozilla Firefox versions 38 and later are supported.
The list of supported operating systems and web browsers was different:
  • Thin client, thick client, web client, and 1C:Enterprise server (Windows versions):
    • Windows XP (no Service Pack 3 requirement)
    • Windows Vista or later (no latest updates requirement)
    • Windows Server 2003 (no latest updates requirement)
  • On Windows and Linux, Mozilla Firefox versions 17 and later were supported.
1C:Enterprise requires more secure versions of operating systems of Windows family.
Client application.
Client application installation.
Add-ins.
Since Windows versions 2008 R2 and later stop trusting SHA-1 certificates in January 2017, the following changes are implemented:
  • .msi and .mst files included in 1C:Enterprise platform distribution kit are signed with SHA-256; all other files are signed with both SHA-1 and SHA-256.
  • The add-in development technology documentation (read more) now includes the following recommendations: sign add-in installer files with both SHA-1 and SHA-256; sign .msi files with SHA-256.
All files included in 1C:Enterprise platform distribution kit were signed with SHA-1.

The following recommendations were not available in the add-in development technology documentation (read more):

  • Sign add-in installer files with both SHA-1 and SHA-256.
  • Sign .msi files with SHA-256.
The platform executable files are verified on all supported operating systems of Windows family.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Synchronous call usage mode for platform extensions and add-ins property name.
  • SynchronousExtensionAndAddInCallUseMode.
  • SynchronousPlatformExtensionAndAddInCallUseMode.
Directory name parameter in BeginCreatingDirectory() method.
  • Directory.
  • DirectoryName.
The update start button in the client application update over HTTP dialog box.
  • Update.
  • Update and run.

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Development tools.
Mobile application builder.
In the mobile platform, support of in-app billing services is added. This includes Apple In-App Purchase (for iOS) and Google Play In-App Billing (for Android). Support of in-app billing for Windows is not provided. The In-app purchases mobile application permission is implemented.

The InAppPurchases, InAppPurchase, InAppPurchaseReceipt, and InAppPurchasesValidation objects are implemented.

In the desktop platform, the InAppPurchasesValidation object is implemented. It is intended for testing in-app purchase algorithms.

In the mobile platform for developers, a service providing an API similar to Google Play In-App Billing is implemented for Android operating system. It is intended for debugging in-app purchase algorithms.

The option to test the full purchase cycle is implemented. This includes the purchase creation and the emulation of some related scenarios. The HTTP service (named PurchaseTest) and the testing tools are provided by the mobile application builder.

The mobile application builder supports building mobile applications with in-app purchases.

This feature was not provided.The option to implement purchases and subscriptions in mobile applications is available. You can create applications with paid features.
Development tools.
Mobile application builder.
For mobile applications, the option to display ads is implemented. It uses iAd service (for iOS) and AdMob service (for Android). Displaying ads on Windows is not supported.

The AdRepresentation object is implemented.

Mobile application builder supports applications that display ads.

This feature was not provided.The option to create mobile applications with advertising monetization model is available.
Spreadsheet documents.
Exporting spreadsheet documents fo PDF format is implemented.This feature was not provided.More options for data presentation in mobile applications.
Data display.
On Android version 4.1 or later, numbers are displayed correctly if the NG parameter of the Format function contains two groups.On Android version 4.1 or later, numbers were displayed incorrectly if the NG parameter of the Format function contained two groups.Eliminated unexpected system behavior.
File operations.
In the mobile platform, support of asynchronous file operation methods is implemented (this includes global context methods and the File object).This feature was not supported by the mobile platform.Improved parallel code implementation for both mobile and desktop platforms.
Full-text search.
On the mobile platform, support of FullTextSearchManager.CheckIndex() method is implemented.

In the Syntax Assistant, methods of FullTextSearchManager object are marked as available on the mobile platform.

This feature was not supported by the mobile platform.

The Syntax Assistant erroneously stated that methods of the FullTextSearchManager object were not available on the mobile platform.

Extended full-text search support on the mobile platform. The Syntax Assistant description is up-to-date.
Internet-enabled functionality.
On the mobile platform, when specifying request body as a string for an HTTPRequest or HTTPServiceResponse object, you have the option to include BOM characters to the request or exclude them.

On the mobile platform, the ByteOrderMarkUsage system enumeration is implemented.

This feature was not supported by the mobile platform.Simplified mobile application integration with systems that do not expect BOM characters in HTTP requests.
Common objects.
The MobileDeviceApplicationRun object is now available on iOS and Windows platforms. The MobileDeviceApplicationRun.RunningSupported method is implemented to test the availability of this feature. Developers can use this method to determine whether their mobile devices support running external applications.The MobileDeviceApplicationRun object was not available on iOS and Windows platforms.The platform behavior related to functionalities that are not available on some mobile devices or operating systems is unified across all platforms.

+

Managed forms.
In the Syntax Assistant, more information is added to the descriptions of Activate by default and Default button managed form items.

The Unfilled selection mode property of managed form input fields is available in mobile platform forms.

The Row selection mode property of managed form tables is no longer available in mobile platform forms. +

+

The information in the Syntax Assistant was outdated.

The availability of some properties of managed form input fields did not match the capabilities of the mobile platform.

Designer and Syntax Assistant now match the capabilities of the mobile platform.
Mobile application builder.
Data storage structure implemented in the mobile application builder is modified. When the mobile application builder is started for the first time after the update, the data conversion may take significant time.Data storage structure implemented in the mobile application builder was different.Data storage structure implemented in the mobile application builder is now more efficient.
Development tools.
When a debug server that does not support HTTP is specified in a mobile application, the error message clearly explains the problem: The mobile platform only supports debugging over HTTP.When a debug server that did not support HTTP was specified in a mobile application, the error message did not clearly explain the problem.Better problem diagnostics during mobile applicatiobn development.
Print tools.
In the mobile platform, the design of the page setup form is changed:
  • The ОК button is moved to the window header.
  • The duplicate Scale header is removed.
In the mobile platform, the design of the page setup form was different:
  • The ОК button was located inside a form.
  • The Scale header was duplicated.
Improved design of the page setup form.
Mobile device-specific features.
On iOS devices, receiving location updates when an application is running in background is not supported.The option to receive location updates when an application is running in background on iOS devices was not documented.Clarified the specifics of using mobile applications on iOS devices.

Table of contents

Library updates + +

Table of contents

Transition from the previous version to the version 8.3.8

Table of contents

Version 8.3.7

Version 8.3.7 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.6 is added to the list of available values of the Compatibility mode property. +Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4 and 8.3.5. +In version 8.3.7 you can run configurations created in version 8.3.6 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.7 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.6 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
ZIP archive operations.
The ZipFileWriter and ZipFileReader objects are revised to improve stability during intense simultaneous work of a large number of users and to eliminate the issue with national characters in file names.

ZIP archive support is implemented using the zipArchive library. The ZIPCompressionMethod.BZIP2 system enumeration value is implemented.

The ZipFileWriter and ZipFileReader objects had an issue related to intense simultaneous work of a large number of users, and an issue related to national characters in file names.

The Info-ZIP library was used for ZIP archive support. The BZIP2 compression method was not supported.

Improved support of ZIP archives (including the support of national characters in file names). You can use the prevalent archive file format on Linux.
Development tools.
 Configuration support settings management is available in Designer batch mode. The /ManageCfgSupport command-line option is implemented for Designer batch mode.This feature was not provided.

Configuration support settings management was only available in the interactive mode.

Simplified automated building and testing of applied solutions.
Internet-enabled functionality.
Web services and HTTP services.
You can use OS authentication for Internet operations and web services. When a WS-reference is created in Designer, the OS authentication option cannot be disabled.

When the list of infobases is retrieved using a web service, OS authentication is used, unless the URL contains authentication data.

OS authentication is not supported on Linux.

For the InternetProxy object, the option to enable or disable OS authentication for each protocol is implemented. This change is not implemented in 8.3.6 compatibility mode.

The UseOSAuthentication parameter is implemented for constructors of the following objects: HTTPConnection, WSDefinitions, and WSProxy.

The UseOSAuthentication property is implemented for the following objects: HTTPConnection and WSProxy.

For the WSReferenceManager.CreateWSProxy() method, the UseOSAuthentication option is implemented.

For the InternetProxy.Set() method, the UseOSAuthentication option is implemented.

For the InternetProxy object, the UseOSAuthentication() method is implemented.

OS authentication was not implemented for Internet operations and web services.

OS authentication was never used for retrieving a list of infobases using a web service.

For the InternetProxy object, basic authentication was used, provided that the user name and password were set.

Extended capabilities for web service operations, Internet operations, and retrieving the list of infobases in corporate environments.
Web services and HTTP services.
You can use a web service whose address is different from the address specified in a WSDL file imported to the applied solution (a WS-reference object).

For the WSProxy object constructor, the Location parameter is implemented.

For the WSReferenceManager.CreateWSProxy() method, the Location parameter is implemented.

This feature was not provided.

A web service could be used only if it was located at the address specified in a WSDL file imported to the applied solution (a WS reference configuration object).

New usage options for Web services in scenarios where a web service has a fixed interface but can be located at different addresses in the Internet. For example, you can use a web service of some broadly used applied solution.
JSON support.
XML and XDTO support.
XDTO objects can be serialized to JSON.This feature was not provided.

Only streaming API and object model were supported for JSON.

Simplified usage of JSON format for exchange between various 1C:Enterprise-based systems.
JSON support.
When data is written in JSON format, slash marks (/) can be escaped.

For the JSONWriterSettings constructor, the EscapeSlash parameter is implemented. For the JSONWriterSettings object, the EscapeSlash property is implemented.

The EscapeSlash property is used by the JSONWriter.WriteValue() method.

The option to enable or disable escape of slash marks in JSON operations was not available.Better compatibility with external systems that use exchange in JSON format.
Localization.
The NumberInWords() and PeriodPresentation() global context methods support the Azerbaijani language. The language code is az. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant.The NumberInWords() and PeriodPresentation() global context methods did not support the Azerbaijani language.Simplified implementation of data presentation for Azerbaijani-speaking users.
Localization.
The NumberInWords() and PeriodPresentation() global context methods support the Turkish language. The language code is tr. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant.The NumberInWords() and PeriodPresentation() global context methods did not support the Turkish language.Simplified implementation of data presentation for Turkish-speaking users.
Localization.
The NumberInWords() and PeriodPresentation() global context methods support the Hungarian language. The language code is hu. The format of the NumerationItemOptions parameter of the NumberInWords() method for this language is described in the Syntax Assistant.The NumberInWords() and PeriodPresentation() global context methods did not support the Hungarian language.Simplified implementation of data presentation for Hungarian-speaking users.
Spreadsheet documents.
When a spreadsheet document is exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, the following print settings are exported to the resulting file:
  • Margin sizes
  • Header sizes
  • Page orientation
  • Page size
  • Scale
  • Black-and-white option
  • Print area
  • Columns and rows that are repeated on each page
  • Header text

This change is not implemented in 8.3.6 compatibility mode.

When a spreadsheet document was exported to XLS (Microsoft Excel 97-2003) format, Microsoft Office OpenXML (Microsoft Excel 2007- 2010) format, or ODS (OpenDocument Spreadsheet) format, its print settings were not exported.More accurate export of spreadsheet documents to popular spreadsheet document formats.
Configuration extensions.
In configuration extensions, you can create WS references, XDTO packages, web services, and HTTP services.

You can publish Internet services belonging to configuration extensions to web servers.

In the default.vrd file, the publishExtensionsByDefault attribute is implemented for ws and

httpServices elements.

This feature was not provided.New functionality introduced for configuration extensions.
OData interface.
You can use independent information registers that do not have dimensions in the standard OData interface. The SurrogateKey property is implemented.This feature was not provided.The 1C:Enterprise object implementation better complies with the OData standard.
Background and scheduled jobs.
You can quickly determine whether the current session is a background job session.

The GetCurrentInfoBaseSession() global context method is implemented. The InfoBaseSession.GetBackgroundJob() method is implemented.

This feature was not provided.

The only way to determine the session type was getting all infobase sessions and iterating through them.

Optimized procedure for determining whether the current session is a background job session. This is handy in such scenarios as dividing initialization scripts for client applications and background jobs.
DBMS operations.
Dumping an infobase to a .dt file is interrupted if any issues related to the internal infobase structure are encountered.Dumping an infobase to a .dt file did not include a verification of the internal infobase structure.Reduced chance of obtaining a .dt file that cannot be loaded.
Common objects.
The option to read and write data in a scenario where synchronous calls are not allowed is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, GraphicalSchema, and RepresentableDocumentBatch (write operation only).

The BeginWriting() method is implemented for the following objects: TextDocument, SpreadsheetDocument, FormattedDocument, and GraphicalSchema.

The BeginReading() method is implemented for the following objects: TextDocument and GraphicalSchema.

The RepresentableDocumentBatch.BeginWritingFileForPrinting method is implemented.

These features were not provided.The missing functionality is implemented for compatibility with the recent Google Chrome changes.
Cryptography support.
For the Issuer and Subject properties of the CryptoCertificate object the option to get access to all certificate fields that describe issuer and subject is implemented.

For the Issuer and Subject properties of the CryptoCertificate object the Street field is implemented.

Each of the Issuer and Subject structure fields of the CryptoCertificate object is accessible by:

  • Mnemonic key (for example, CN)
  • UUID key (for example, OID2_5_4_3 for the CN field).
The Issuer and Subject properties of the CryptoCertificate object did not provide access to all certificate fields.All certificate fields can be accessed, even those that are present due to regulator requirements.
DBMS operations.
When the platform attempts to build an index by more than 3 string fields in Oracle DBMS, it automatically creates V81C_INDEX_BIG tablespace.When the platform attempted to build an index by more than 3 string fields in Oracle DBMS, if V81C_INDEX_BIG tablespace was missing, an error was generated. Creating the tablespace manually eliminated the error.The need to create the tablespace manualy is eliminated.
Configuration extensions.
Predefined data.
The option to adopt predefined data items is implemented for configuration extensions. This makes the following operations available: check extensions for availability of predefined data items, check whether extension exchange plan content and object registration rules include predefined data items, and use extension predefined items in the query builder.This feature was not provided.Expanded configuration extension functionality.
Development tools.
The option to dump configurations to hierarchical file structures, as well as restore them from such file structures, is implemented.

Name length for new configuration objects is limited by 80 characters. Existing configuration objects can have names longer than 80 characters until you attempt to edit their names.

1C:Enterprise script modules are dumped to .bsl files.

In the dump configuration files dialog box you can select the dump format: flat or hierarchical.

The Format parameter is implemented for /DumpConfigToFiles Designer batch mode command-line option. The new parameter describes the dump format.

By default configurations are dumped to hierarchical file structures.

+

Configurations were always dumped to flat file structures.

No length restrictions were applied to configuration object names.

1C:Enterprise script modules were dumped to .txt files.

Chance of configuration dump procedure being terminated due to length of the output file path and name exceeding the file system limits is significantly reduced (file names are derived from configuration object names).
Development tools.
A configuration can be partially restored from files. The following operations are available: adding, modifying, deleting, and renaming configuration objects and modifying some properties of configuration objects (such as their modules or help topics).

You can simultaneously load a configuration from files and update database configuration.

For the /LoadConfigFromFiles Designer batch mode command-line option, the following parameters are implemented: -files (files to load) and -listfile (file containing a list of files to load).

In the technological log, the CONFLOADFROMFILES event is implemented.

This feature was not provided.

Only restoring the entire configuration from files was available.

Better performance of configuration updates in scenarios where a configuration is stored in an external system.
Development tools.
New debug option is available: debugging over HTTP. Developers can select this option in Designer.

The dialog box with automatic debug item attachment settings is refactored.

Debug server (dbgs) is implemented, it can be started from the command line, and also as an operating system service. The new debug protocol is not supported on Linux servers in the scenario where 1C:Enterprise starts automatically during operating system startup.

The following command-line options are implemented for the server agent (ragent): /debug, /debugServerAddr, /debugServerPort, and /debugServerPwd.

For the client application the following command-line option is implemented: /debug.

In default.vrd file, for the <debug> element, the protocol attribute is implemented.

In comcntrcfg.xml file, for the <config> element, the protocol attribute is implemented.

This option is implemented as beta version.

A single debug option was available.You can debug applied solutions when HTTP is the only available connection protocol. This expands Debugger functionality.
Localization.
The option to localize only a part of 1C:Enterprise platform interface required for a specific applied solution is implemented. Localization tools that support this option are available upon request from 1C Company at MAIL:int@1c.com. This option has the following limitations:
  • Pictures cannot be localized.
  • The option to build a platform distribution kit is not provided.
Only the full localization option was available. Localizations were always delivered as part of the platform distribution kit.The option to localize the platform interface for specific applied solutions or specific delpoyments is implemented. This option is in demand by users whose native languages are not included in the list of platform localization languages.
Development tools.
Designer help includes the list of executable files of predefined external tools used for comparing and merging modules. It is recommended that you specify these names in the settings for comparing and merging modules with external tools.Designer help did not include executable file names of predefined external tools used for comparing and merging modules.Improved Designer help.
Dumping/loading configurations to files.
Versioning is implemented for the format of dumping configurations to files. 1C:Enterprise 8.3.6 has dump format version 1.0, and 1C:Enteprise version 8.3.7 has dump format version 2.0.

If the dump files do not include a version number, they are treated as version 1.0-compliant.

Files are always dumped in the format that matches the 1C:Enterprise platform version.

A configuration can be restored from files only if the version of the files is earlier than or equal to the version supported by the 1C:Enterprise platform.

Versioning was not available for the format of dumping configurations to files.Some issues related to the incompatibility of dump files generated by different 1C:Enterprise versions are eliminated.
Dumping/loading configurations to files.
The method of dumping the Parameter property of the Button managed form item to files is changed. If the Parameter value references a configuration object, the full name of that configuration object is dumped to files.The Parameter property of the Button managed form item was dumped as a UUID of the configuration object type if the Parameter property referenced a configuration object.Eliminated the configuration dump format inconsistency.
Administration tools.
Applied solution license validity check is implemented at 1C:Enterprise platform level. The check is performed for applied solutions running in file mode, and it is also performed on the server for 1C:Enterprise 8.3 Server MINI. The license validity check is not performed for applied solutions that use the base version of 1C:Enterprise. The check involves an Internet connection to the Update Validation Center.

The result of the check is displayed in the About 1C:Enterprise dialog box.

The Designer interface includes new commands related to this functionality. +The following global context methods are implemented: GetConfigurationID, GetLicensingClientName, GetLicensingClientAdditionalParameter, SetLicensingClientParameters, +AttachLicensingClientParametersRequestHandler, and +DetachLicensingClientParametersRequestHandler.

For the conf.cfg configuration file, the LicConfigDebugTimeouts parameter is implemented. The parameter is used to reduce the check interval.

The implementations of this functionality are subject to future announcement.

This feature was not provided.The option to perform a license validity check after updating an applied solution is implemented.
DBMS operations.
Support of Oracle Database version 12.1.0.2 (Linux) is implemented.This Oracle Database version was not supported.Extended list of supported Oracle Database versions.
Designer.
Client application.
Cross-platform architecture.
System requirements.
The client application for OS X 10.8 or later is available (64-bit version only). It supports the following features:
  • Thin client, thick client, and Designer
  • File and client/server modes

Running 1C:Enterprise server on OS X is not supported. The limitations of the OS X client application are provided in the documentation.

Installation and simultaneous work of multiple 1C:Enteprise versions is supported. +

This option is implemented as beta version.

Infobase access via a web client was available on OS X.You can develop applied solutions and run client applications on OS X.
System requirements.
Astra Linux Special Edition 1.4 is supported.This release was not supported.New Linux release is supported.
Add-ins.
The English description of the add-in development technology is provided as an HTML document. This document is available for download for each platform version as a part of 1C:Enterprise platform 8.3 Add-in technology archive.The description of the add-in development technology available for download as a part of 1C:Enterprise was only provided in Russian. +Better accessibility of add-in development documentation.
ZIP archive operations.
File names in ZIP archives generated by 1C:Enterprise have both UTF-8 encoding and the current operating system encoding (if is not UTF-8).

The ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly.

File names in ZIP archives generated by 1C:Enterprise had UTF-8 encoding only.

The ZipFileReader object in 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs in Windows XP/2003/2008/7, displayed file names with non-English characters inside ZIP archives incorrectly.

The ZipFileReader object from 1C:Enterprise version 8.3.6 or later, as well as built-in decompression programs from Windows XP/2003/2008/7, read ZIP archives correctly even when the file names inside the archives contain non-English characters. Note that the built-in decompression program for OS X displays file names in such archives incorrectly.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Interface.
In the Taxi interface, when an item is deleted from the Favorites list, a modal confirmation dialog box is no longer displayed. After the deletion, a link for restoring the deleted item is displayed in the Favorites panel.In the Taxi interface, when an item was deleted from the Favorites list, a modal confirmation dialog box was displayed.The Favorites pane functionality is fully supported in web browsers that do not support modal dialog boxes.
Interface.
In the Taxi interface, you can pin forms in the main window work area (so that a form is always available). You can also combine two forms in order to have them always displayed together when any of the two forms is opened.

In the system menu, context menu of the opened windows panel, and form title context menu, the corresponding commands are implemented.

This feature was not provided.Improved platform usability. For example, users have the option to compare two instances of a single report featuring different periods.
Data display.
Web service authentication error messages no longer contain HTML text returned by the web server, at no cost to message information value.Web service authentication error messages contained HTML text returned by the web server. +All information that was not user-friendly is removed from web service authentication error messages
Interface.
Replacement of style elements with actual fonts and colors is improved in some scenarios.In some scenarios, replacement of style elements with actual fonts and colors was performed incorrectly.Eliminated unexpected system behavior.
Client application.
The client application help includes the description of the keyboard shortcut Ctrl+Shift+H, which opens the history panel.Description of this shortcut was not available in the client application help.Client application help is up-tp-date.
Web client.
In Google Chrome web browser, access to clipboard using context menu commands is implemented (in addition to the previously available keyboard shortcuts).

This options requires installing a browser extension. The web client propmts the user to install the extension first time they attempt to access the clipboard using context menu commands. If the extension is not installed, the clipboard can be only accessed using keyboard shortcuts.

In Google Chrome web browser, the clipboard could only be accessed using keyboard shortcuts.

Clipboard access using context menu commands was not supported.

Improved web client usability in Google Chrome.
Web client.
New version of the browser extension for Mozilla Firefox is available. The extension only supports asynchronous operations. The synchronous methods are no longer supported.Another version of browser extension for Mozilla Firefox was available. It supported synchronous operations.Support of Mozilla Firefox versions 40 and later, which do not support synchronous operations (just like Google Chrome versions 45 and later), is implemented.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Development tools.
The performance of the following Designer operations is improved:
  • Opening a subsystem editor window
  • Including an object into a subsystem
  • Setting a filter by subsystem in the configuration tree window
The performance of some Designer operations was insufficient.Streamlined execution of some Designer operations.
Geographical schemas.
The following geographical schema operations are optimized:
  • Loading and rendering geographical schemas
  • Selecting an object in a geographical schema field
The performance of some geographical schema operations was insufficient.Improved usability of geographical schemas.
Full-text search.
Improved performance of full-text search and of building the full-text search index.Insufficient performance of full-text search and of building the full-text search index.Improved performance of full-text search and of building the full-text search index. The improvement is noticeable if the infobase contains indexed objects with a large number of words.
Full-text search.
Dynamic lists.
In dynamic lists, the performance of the search initiated from the search string is improved in the following scenario: the full-text search is enabled for the dynamic list main table and filters with Equal to comparison type are applied to the main table fields. In dynamic lists, the performance of the search initiated from the search string was insufficient.In dynamic lists, improved performance of the search initiated from the search string.
Queries.
When a query that accesses only tabular section data is executed, the retrieved table is not joined to the parent object table.When a query that accessed only tabular section data was executed, the retrieved table was automatically joined to the parent object table.Eliminated unexpected system behavior.
DBMS operations.
Improved performance of reading objects of the following types from DBMS: DocumentObject, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ChartOfCharacteristicTypesObject, ExchangePlanObject, and ChartOfAccountsObject. Reading any of these objects is followed by implicit transaction creation only if the object has tabular sections and "dirty read" outside of transactions is allowed in the DBMS.Reading objects of the following types from the DBMS was followed by implicit transaction creation if the object had tabular sections: DocumentObject, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ChartOfCharacteristicTypesObject, ExchangePlanObject, and ChartOfAccountsObject.The following values are reduced:
  • Number of data lock waits in the file DBMS.
  • Time required for loading an infobase object from a DBMS in the client/server mode.
  • Number of waits due to internal 1C:Enterprise server locks during bulk reading of infobase objects from a DBMS.
  • DBMS load (due to a significant decrease of the number of transactions).
Managed forms.
Improved performance of managed form conditional appearance. Faster opening of managed forms with a large number of conditional appearance items.Insufficient performance of managed form conditional appearance.Improved performance of opening managed forms, especially for file mode infobases and on low-performance computers.
Predefined data.
Improved performance of retrieving predefined data using the PredefinedValue() method.Insufficient performance of retrieving predefined data using the PredefinedValue() method. Improved performance of processing predefined data.
Development tools.
The configuration database update time is reduced for configurations that include a large number of roles, provided that the update does not require database restructuring.The configuration database update required significant time for configurations that included a large number of roles, provided that the update did not require database restructuring.Reduced database configuration update time.
Managed forms.
1C:Enterprise script.
The performance of opening managed forms is improved in the thin client and web client.The performance of opening managed forms in the thin client and web client was insufficient.Improved platform performance.
Platform algorithms.
Internal caching algorithms of 1C:Enterprise are optimized. This improves the performance of many 1C:Enterprise features, including the following:
  • Form opening
  • Queries
  • Functional options
  • Predefined data
  • Reusable return values
  • Data access using "." (dot)
System performance was suboptimal.Improved platform performance, especially for infobases running in the file mode and on computers with limited RAM (less than 4 GB).
Data access restrictions.
Query execution is optimized for users that do not have full rights in configurations that use access restrictions and have a large number of roles. The query execution time is not significantly affected by the number of roles assigned to a user.Query execution time was insufficient for users that did not have full rights in configurations that used access restrictions. The query execution time was significantly affected by the number of roles assigned to a user.Improved performance of configurations with a large number of roles (including form opening performance).
Dynamic lists.
Full-text search.
When a dynamic list is searched from a search box by fields that do not belong to the main dynamic list table, full-text search by source objects of the fields is performed first. Fields of objects where nothing is found by the full-text search are excluded from further search.When a dynamic list was searched from a search box, additional conditions were applied to all fields displayed in the table linked to the dynamic list.Improved performance of search in dynamic lists in some usage scenarios.
Queries.
In the query language, expressions that include both comparison operators and CASE operators that return only constant values are optimized. The optimization simplifies expressions or their parts.In the query language, optimization was not available for expressions that included both comparison operators and CASE operators that returned only constant values.Improved query performance in some scenarios.
Full-text search.
The performance of the input by string feature is improved. The full-text search index data structure is modified. Full-text search index is created in the new format. To convert the index to the new format, clear the index, ensure that the Compatibility mode configuration property is set to Do not use, and then generate the index.

The <INPUTBYSTRING> technological log event is implemented, it is used for monitoring events related to input by string.

This change is not implemented in 8.3.6 compatibility mode.

The performance of the input by string feature was insufficient. Full-text search index had a different format.Improved performance of the input by string feature, which, in turn, improves the usability of all platform objects that use this feature.
Automated testing.
In the web client running in the testing client mode, the performance of test scenario commands is improved.In the web client running in the testing client mode, the performance of test scenario commands was insufficient.Improved performance of automated testing in the web client.
Data exchange.
Common attributes / Data separation.
Improved performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image includes a register that is included in independent separator content (provided that separator is not used in the current session).The performance of initial infobase image creation in scenarios where the exchange plan used to create the initial image included a register that was included in independent separator content (provided that separator was not used in the current session) was insufficient.Improved performance of initial image creation in some scenarios.
Common objects.
The algorithms of the following methods are optimized: QuerySchemaAvailableTables.Find(), QuerySchemaSources.Add(), and QuerySchemaTableParameters.Count().The performance of QuerySchemaAvailableTables.Find(), QuerySchemaSources.Add(), and QuerySchemaTableParameters.Count() methods was insufficient.Improved performance of query schema operations in 1C:Enterprise script.
Development tools.
Operations in the configuration command interface editor form are optimized for scenarios with a large number of roles. The performance of moving table rows is improved.The performance of operations in the configuration command interface editor form was insufficient in scenarios with a large number of roles.Improved usability for application developers that edit the command interface of configurations with a large number of roles.
DBMS operations.
Calculation registers.
Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets are deleted, deletion of records storing actual action periods is performed faster.

This change is not implemented in 8.3.6 compatibility mode.

Both in PostgreSQL and IBM DB2, in scenarios where large calculation register record sets were deleted, deletion of records storing actual action periods was impaired.Both in PostgreSQL and IBM DB2, optimized deletion of large calculation register record sets.
Spreadsheet documents.
The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side is improved.The performance of setting the size and position of spreadsheet document pictures at 1C:Enterprise server side was insufficient.Improved performance of spreadsheet document generation in scenarios where the size and position of spreadsheet document pictures are set from 1C:Enterprise script.
Managed forms.
Web client.
Server clusters.
The performance of opening managed forms is improved in the following scenario: the web client is running in client/server mode and the server cluster is deployed on a Linux computer.The performance of opening managed forms was insufficient in the following scenario: the web client was running in client/server mode and the server cluster was deployed on a Linux computer.Improved web client performance for Linux server clusters.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Managed forms.
The Create menu (in a document journal form) does not contain document types disabled by functional options.

The Show in list menu (in a document form) does not contain list forms disabled by functional options.

The Create menu (in a document journal form) contained document types disabled by functional options.

The Show in list menu (in a document form) contained list forms disabled by functional options.

Eliminated unexpected system behavior.
Server clusters.
In client/server mode, dynamic updates do not require restarting Designer.

When a scheduled job is started or completed in an infobase, this does not affect the performance of other infobases in the cluster.

Improved system reliability in the following scenarios:

  • Database configuration update
  • Background jobs
  • Dynamic update
In client/server mode, dynamic updates required restarting Designer.

When a scheduled job was started or completed in an infobase, this affected the performance of other infobases in the cluster.

The system reliability was insufficient in several scenarios.

Increased stability and reliability of server clusters.
Predefined data.
During infobase verification and repair operations, the platform checks whether the main table of an object (catalog, chart of characteristic types, chart of calculation types, or chart of accounts) contains no more than 1 record for each predefined item in each area. If a duplicate item is found, a predefined item mark is removed from it and a deletion mark is set instead.This feature was not provided.Improved infobase verification and repair operation.
External data sources.
Table fields and cube table dimension fields of external data sources can have NULL values only if the NULL allowed check box is selected in the object settings. For external data source cube table fields NULL values are always allowed.

This change is not implemented in 8.3.6 compatibility mode.

All external data source table fields could have NULL values.Improved performance of sorting dynamic lists by fields whose ability to store NULL values is specified correctly.
Data composition system.
In a data composition schema, if a query with a nested query is used in a data set, selected fields of the nested query are available for filtering, provided that these fields are not used in aggregate functions of the parent query.

This change is not implemented in 8.3.6 compatibility mode.

In a data composition schema, if a query with a nested query was used in a data set, selected fields of the nested query were not available for filtering (except virtual table parameters).In a data composition schema, the generation of a resulting query is optimized for scenarios that utilize nested queries with filters by nested query fields.
Infobase verification and repair.
Common attributes / Data separation.
Infobase verification and repair can detect and repair the following issue: objects linked to some tabular section rows are absent from the infobase. The search and restoration are performed taking into account all independent separators that include the missing objects.This feature was not provided. Improved infobase verification and repair procedure.
Dynamic lists.
In dynamic lists, search by reference fields with custom presentations is performed by fields that form the presentation. Such fields are obtained with the help of the PresentationFieldsGetProcessing() handler.In dynamic lists, search by reference type fields with custom presentation was performed only by fields used in default presentation.Improved search by reference fields with custom presentations in dynamic lists.
Managed forms.
Command interface.
In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command is executed from the navigation panel, the Uniqueness command handler parameter is assigned a BOOLEAN value (TRUE if the command is executed through the Open new item context menu command, otherwise FALSE).

In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command is executed from a form navigation panel, the uniqueness of the form being opened is not set.

This change is not implemented in 8.3.6 compatibility mode and in the Forms in separate windows mode.

In the thin client, in the Taxi interface or in the Forms in tabs mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was set to the main window identifier. In the web client, in the Taxi interface or in the Forms in tabs mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was assigned a BOOLEAN value.

In the thin and web clients, in the Taxi interface or in the Forms in tabs mode, when a command was executed from a form navigation panel, the Uniqueness command handler parameter was set to the main window identifier.

In the Forms in separate windows mode, when a command was executed from the navigation panel, the Uniqueness command handler parameter was set to the main window identifier.

In the Forms in separate windows mode, when a command was executed from a form navigation panel, the Uniqueness command handler parameter was set to the main window identifier.

Unified platform behavior in various client applications and usage scenarios.
Server clusters.
For the ragent, rmngr, and rphost commands, which start server cluster processes, the pingPeriod and pingTimeout command-line options are implemented.

In default.vrd file, for the pool item, the serverPingPeriod and serverPingTimeout attributes are implemented.

In the web server publishing dialog box, the Check period and Check timeout properties are implemented.

In the technological log, for the CONN event, the list of logged events related to the detection of connection losses between processes in a single cluster is extended.

A less-efficient algorithm was used for detection of connection losses in a cluster.Improved server cluster stability, faster and more efficient detection of connection losses in a cluster.
Full-text search.
Dynamic lists.
Server clusters.
When a form that contains a dynamic list is closed, the server cluster is notified about that in order to cancel the background job that performs search in the list (if it was initiated earlier).When a form that contained a dynamic list was closed, the server cluster was not notified about that. If a background job that performed search in the list was running at the moment of closing, it was not interrupted once the form was closed. Instead, it continued running till the completion.Eliminated unexpected system behavior. Reduced server cluster load in some scenarios.
Development tools.
In Designer, the П shortcut is removed from the Move up and Move down commands in the Russian interface (it was assigned to both commands previously). Other keyboard shortcuts for these commands are still in effect, as well as the actions associated with these commands.In Designer, the П keyboard shortcut was assigned to both Move up and Move down commands in the Russian interface.Eliminated unexpected system behavior.
Data composition system.
Presentations of filter items displayed in reports is changed.

If a report includes a filter item from the user settings and the user settings item presentation is specified for this filter item, the presentation is used for displaying the filter in the resulting report.

This change does not affect reports that include filter items that do not belong to user settings. It also does not affect filter items that do not have user settings item presentations specified.

This change is not implemented in 8.3.6 compatibility mode.

If a report included a filter item whose presentation was specified, only this presentation was displayed in the report. Otherwise the filter item was displayed in the following format: <Left value> <Comparison type> <Right value>.Filter list presentations in reports are easier to read.
Spreadsheet documents.
The spreadsheet document behavior is modified in scenarios where a rectangular area of cells is inserted or deleted (interactively or using 1C:Enterprise script). If an area being moved overlaps an area of merged cells and the merged area is not fully included into the area being moved, the merging is removed and the cells previously included in the merged area inherit the formatting of the merged area.

This change is not implemented in 8.3.6 compatibility mode.

When a rectangular area of cells was inserted or deleted, merged cells that partially overlapped the area being moved were not modified.Eliminated unexpected spreadsheet document behavior.
DBMS operations.
In Oracle Database DBMS an index created for a temporary table that includes more than three dimensions of String type, each of them containing at least 60 characters, might be truncated (with the last fields discarded) if the index key length does not fit the block size.In Oracle Database DBMS an index created for a temporary table that included more than three dimensions of String type resulted in unexpected system shutdown due to DBMS error.Eliminated unexpected system behavior. Improved system reliability.
Administration tools.
The following requirement is described in the documentation: when an application is updated over HTTP or HTTPS, all .mst, .msi, and .cab files in the distribution kit .zip archive must have a digital signature. The signature is verified on the computer where the application is installed. Thew documentation did not include the file digital signature requirement.Documentation issue corrected.
Development tools.
Setting a correspondence between Debugger and a debug item no longer requires the exact match of infobase connection strings in Debugger and in the debug item.

The option to edit a variable value during debugging is implemented.

The option to view all local variables of a method being debugged in a dedicated window is implemented.

The state of folders (expanded or collapsed) in the immediate window and in the local varibles window is preserved when switching to the next debug step.

If you use the Break command (Shift+F5) to close an application being debugged, the modal exit confirmation dialog box is never displayed.

Setting a correspondence between Debugger and a debug item required the exact match of infobase connection strings in Debugger and in the debug item.

The option to edit a variable value during debugging was not provided.

The option to view all local variables of a method being debugged in a dedicated window was not provided.

The state of folders (expanded or collapsed) in the immediate window and in the local varibles window was not preserved when switching to the next debug step.

Using the Break command (Shift+F5) to close an application being debugged sometimes opened the modal exit confirmation dialog box.

Expanded debug functionality.
Data composition system.
The overall columns of a data composition system table display the titles of grouped resource fields if grouping templates are specified for the table columns.

This change is not implemented in 8.3.6 compatibility mode.

The overall columns in the data composition system table header did not display the titles of grouped resource fields if grouping templates were specified for the table columns.Eliminated unexpected system behavior.
Common objects.
Development tools.
The Language code property of the Language configuration object cannot contain the following characters: #, *, |, \, :, ", <, >, ?, /.The Language code property of the Language configuration object could not contain the # character.Chance of configuration dump procedure being terminated due to incorrect generation of the file name (which is based on the language code) is reduced.
Command interface.
In the thin client, in the Forms in separate windows mode, if a navigation command handler includes the GotoURL() global context method with a navigation point reference parameter, after the command execution the current navigation point is set to this command.

+

In the thin client, in the Forms in separate windows mode, if a navigation command handler included the GotoURL() global context method with a navigation point reference parameter, after the command execution the current navigation point was set to the point passed in the parameter.Eliminated unexpected system behavior.
Managed forms.
In the thin client, the Window property of managed form object is read-only.

This change is not implemented in 8.3.6 compatibility mode.

In the thin client, the Window property of managed form object was available for both reading and writing. In the web client, the Window property of managed form object was read-only.Unified system behavior in different client applications.
Information registers.
For periodic information registers with resources or attributes indexed, the structure of the index of the slice first/last table is changed. If the information register periodicity is set to By recorder position, register dimensions are added to the index. If the periodicity has any other value, the index is not unique.

When the Compatibility mode configuration property is set to None, the platform performs the restructuring of the slice tables.

This change is not implemented in 8.3.6 compatibility mode.

For periodic information registers with periodicity set to By recorder position, register dimensions were not included in the index of slice first/last tables. For periodic information registers with other periodicity values, the index of slice tables was unique. +An nonunique index issue is eliminated.
Predefined data.
The configuration check that is always performed before database configuration update includes a check for duplicate predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update.

This change is not implemented in 8.3.6 compatibility mode.

The configuration check that was always performed before database configuration update included a check for duplicate predefined item names, however, duplicate names did not prevent the database configuration from updating.Improved reliability of configuration updates for configurations that include predefined data.
Technological log.
Logging of debugger exceptions in the technological log is implemented. The <EXCP> event is used for that logging.Logging of debugger exceptions was not performed.Better debugger error diagnostics.
Administration tools.
The infobase verification and repair procedure no longer includes a check for spaces at the end of attribute values that have String type and variable length.The infobase verification and repair procedure included a check for spaces at the end of attribute values that had String type and variable length.Eliminated unexpected system behavior.
Regional settings.
For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ, and 87-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, 69-FZ. and 87-FZ.The time offset changes introduced by the new law are implemented.

Table of contents

Changes that require modification of configuration and administrative settings

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

This change is not implemented in 8.3.6 compatibility mode.

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

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

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

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

+

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

Eliminated unexpected system behavior.

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

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

The SpreadsheetDocument.Template property is implemented.

This change is not implemented in 8.3.6 compatibility mode.

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

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

When the platform displayed a spreadsheet document:

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

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

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

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

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

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

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

These features were not provided.

The QuerySchemaNestedTable.Fields property had QuerySchemaExpressions type.

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

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

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

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

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

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

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

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

This change is not implemented in 8.3.6 compatibility mode.

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

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

Table of contents

Renamed objects

ObjectThe old nameThe new name
Spreadsheet document property that describes the language for displaying and editing the document. The former name is supported for compatibility purposes.
  • TemplateLanguageCode.
  • LanguageCode.
Presentations of automatically generated graphical schema field command groups. The command groups are displayed in the form customization dialog box in 1C:Enterprise mode.
  • Size and alignment group (contains the Align left command)
  • Size and alignment group (contains the Align top command)
  • Group group (contains the Auto space: horizontal command)
  • Group group (contains the Bring to front command)
  • Group group (contains the Send to back command)
  • Horizontal alignment
  • Vertical alignment
  • Distribute
  • Bring forward
  • Send backward

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Development tools.
The option to debug configurations on the mobile platform is implemented. The debugging can only be performed over HTTP (you can select this option in Designer).This feature was not provided.Streamlined development of applied solutions for the mobile platform.
Print tools.
The Print mobile application extension, which is used for printing from mobile applications, is implemented.

The mobile application builder supports building mobile applications that require this extension.

This feature was not provided.Reduced list of required permissions for mobile applications that do not require printing.
Spreadsheet documents.
The brightness of frozen spreadsheet document areas is reduced by 2.5%.The brightness of frozen spreadsheet document areas was reduced by 10%.Better look and feel of spreadsheet documents with frozen areas.
1C:Enterprise script.
The following string processing functions previously available for the personal computer platform are now implemented for the mobile platform: StrTemplate(), StrCompare(), StrStartWith(), StrEndsWith(), StrFind(), SrtSplit(), and StrConcat().

The SearchDirection system enumeration is implemented.

This feature was not provided.Unified string processing for the personal computer platform and the mobile platform.
Managed forms.
The Representation property of a managed form button located in a form title command bar affects the button view. When the platform defines the button view, it ignores the properties of the command linked to the button.The Representation property of a managed form button located in a form title command bar did not affect the button view. When the platform defined the button view, it ignored the properties of the command linked to the button.You can manage the view of buttons located in form title command bars using the button properties.
Special tools.
For the TelephonyTools.NumberDialingSupported() method the DirectCall parameter is implemented. The parameter streamlines the check for number dialing support.The TelephonyTools.NumberDialingSupported() method did not support any check options.Унифицирована возможность проверки работы со специальными возможностями на мобильной платформе.
System requirements.
Support of Windows Phone operating system version 8.1 or later (ARM and x86 architectures) and touch devices that run Windows version 8.1 or later (ARM and x86) is implemented.

The mobile platform for Windows Phone supports all mobile platform features available on other operating systems, excluding:

  • Conversion of geographical coordinates to addresses and back, and ShowOnMap() global context method
  • Barcode scanning
  • Phone call log
  • Printing
  • Receiving text messages
  • Notifications
  • Contacts
  • Calendars

The mobile platform specifics are described in the documentation.

The mobile platform distribution file mobile.zip is complemented with new data.

This option is implemented as beta version.

This feature was not provided.Extended support of operating systems for mobile and touch devices.
Mobile application builder.
Mobile application builder for Windows Phone operating system is implemented. It supports Windows Phone 8.1 or later.

New builder parameters are added:

  • The option to build applications for Windows operating system
  • Support of graphic assets required for Windows operating system

Publishing of built applications to Windows Store is not supported.

When loading mobile platform data from the mobile.zip file to mobile platform builder, you have the option to load only mobile operating systems that are present in the archive.

The option to specify different application IDs for different mobile operating systems is supported.

The option to export developer certificates from the mobile application builder database is implemented.

Mobile application builder did not support Windows operating system.

Attempts to load the mobile platform from the mobile.zip file to mobile application builder were only successful if the file contained platform versions for both Android and iOS.

A single mobile application ID was assigned for Android and iOS builds.

Exporting developer cerificates from the mobile application builder database was not supported.

Mobile application builder supports Windows operating system, and features other improvements.
Command interface.
Managed forms.
On the mobile platform, the Show in list command, which was perviously available only on the personal computer platofrm, is implemented.

The ManagedForm.ExecuteNavigation() method and the NavigationProcessing managed form event are implemented.

This feature was not provided.The interfaces of the mobile and personal computer platforms are unified.
Web services and HTTP services.
On the mobile platform, the option to use a web service whose address does not match the address specified in a WSDL file imported to the applied solution (WS-reference configuration object) is implemented.This feature was not provided.Web servfice operations on the mobile and personal computer platforms are unified.
Managed forms.
On the mobile platform, the option to use a selection list to provide a value for a managed form input field that displays date and time is implemented.On the mobile platform, drop-down lists were not available.On the mobile platform, the option to use drop-down lists in the input fields that display date and time is now available.
Managed forms.
The option to switch between the input fields using the Enter button of the virtual keyboard (i.e. without closing the keyboard) is implemented. The option to switch between the input fields using Tab/Shift+Tab keys of a physical keyboard connected via Bluetooth is also implemented.The option to switch between the input fields without closing the virtual keyboard was not available. To switch between the fields, a mobile application user had to close the keyboard, then switch to another field, and then open the keyboard.Improved mobile application usability is scenarios where multiple input fields are available in a single form.

Table of contents

Library updates + +

Table of contents

Transition from the previous version to the version 8.3.7

Table of contents

Version 8.3.6

Version 8.3.6 includes known bug fixes and functionality modifications. +

To obtain a link to an entry of the V8Update file, double-click any of the entry lines. This opens a pop-up window with the link available for copying to the clipboard. This feature is only available if JavaScript is enabled.

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.5 is added to the list of available values of the Compatibility mode property. +Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3 and 8.3.4. +In version 8.3.6 you can run configurations created in version 8.3.5 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.6 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.5 for working with the infobase even after the transition to version 8.3.6. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on). +
Development tools.
In Designer, in module text, bookmarks can be preserved between different work and module editing sessions.

To access the full list of bookmarks, on the Edit menu, click Bookmarks.

This feature was not provided.Improved Designer usability,
Development tools.
When renaming a configuration object, you have the option to update the object name usage instances in the entire configuration.

When deleting a configuration object, you have the option to search for the object name usage instances in the entire configuration.

When modifying or deleting a managed form item, attribute, or parameter, the check for usage instances of its name in the form module is performed. When renaming an item, attribute, or parameter, you have the option to update its name usage instances in the form module.

The Find references to object operation now includes the search in module texts.

You can specify whether you want to use these options in the Designer options window.

These features were not provided.Reduced chance of making errors when renaming or deleting configuration objects. Improved usability for developers.
Managed forms.
Planner (a visual tool for managing schedule data) is implemented. A new "planner field" type is implemented for managed form fields. The Planner object is implemented.

In the TimeScalePosition system enumeration, the following values are implemented: Left and Right (when applied to a Gantt chart, both are treated as Top).

This feature was not provided.Improved user experience for scheduling (appointments, calendars, and so on).
Configuration repositories.
In Designer batch mode, you can bind an infobase that is not yet bound to the configuration repository (command-line option /ConfigurationRepositoryBindCfg).This feature was not provided.

Infobases could be bound to repositories only interactively.

You can automate more configuration repository operations.
Command interface.
Managed forms.
For managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, tasks, and information register records, the Show in list command is implemented.

For managed forms, the ExecuteNavigation() method and NavigationProcessing event handler are implemented.

This feature was not provided.Improved system usability for automatic object selection in a list being opened.
System enumerations.
Client application.
For the SectionsPanelRepresentation system enumeration, the following values are implemented: PictureOnTopAndText and PictureOnLeftAndText.

In the client application, in the sections panel editor, the following section view features are available:

  • In Version 8.2 interface compatibility mode:
    • Picture
    • Text
    • PictureAndText
  • In Taxi interface compatibility mode:
    • Picture
    • Text
    • PictureAndText
    • PictureOnTopAndText
For the SectionsPanelRepresentation system enumeration, the following values were available: Picture, Text, PictureAndText. +

Extended section view capabilities for the sections panel in the Taxi interface.

Managed forms.
The option to specify a graphical schema field as a source of command bar and managed form button commands is implemented.

The only commands available in the web client are print and preview.

In the Russian interface some of the graphical schema commands are renamed to the following:

  • Выровнять по левому краю
  • Выровнять по правому краю
  • Выровнять по верхнему краю
  • Выровнять по нижнему краю
  • Переместить вперед
  • Выровнять по центру
  • Выровнять по середине
The option to specify a graphical schema field as a source of command bar and managed form button commands was not provided.

In the Russian interface some of the graphical schema commands had different names: +

  • Выровнять влево
  • Выровнять вправо
  • Выровнять вверх
  • Выровнять вниз
  • Переместить вверх
  • Выровнять по центру горизонтально
  • Выровнять по центру вертикально
Increased graphical schema usability.
Administration tools.
An object integrity check utility is implemented. It checks the state of file system objects and database objects used by 1C:Enterprise and monitors their changes.

The 32-bit and 64-bit versions of the utility are available for Windows and Linux operating systems.

This feature was not provided.

File change monitoring was only available using third-party tools. Monitoring of database object changes was not available.

The option to perform system integrity checks to provide protection against unauthorized modifications is implemented.
Internet-enabled functionality.
For the Get() method of the InternetMail object, the MarkAsRead parameter is implemented. This parameter only makes sense when the platfrom uses IMAP for email operations.

If the platform uses POP3, an attempt to use this parameter when it is set to False generates an exception.

The platform behavior in 8.3.5 compatibility mode is not changed (for the part where the parameter is set to False).

If the platform used IMAP for email operations, the execution of the Get() method of the InternetMail object gave different results depending on the value of the ArrayOfMessageHeadersOrIdentifies parameter.
  • If the parameter was not specified, the flag indicating whether a message was read was not set for messages retrieved from the mail server.
  • If the parameter was specified, the flag was set.
Eliminated inconsistency in the platform behavior during email operations that use IMAP.
Technological log.
For the SCALL and CALL technological log events, new IName and MName fields are implemented. They store additional internal system call data. 1C Company experts might use that data while handling support requests.This feature was not provided.The technological log provides additional data that can be helpful for solving complex issues.
Dynamic lists.
The option to get data from a dynamic list (adjusted for column visibility settings and search options applied) is implemented.

The following methods are implemented for the managed form table extension for dynamic lists:

  • GetPerformingDataCompositionScheme()
  • GetPerformingDataCompositionSettings()
This feature was not provided.The option to get dynamic list data that is visible to a user for future processing is available.
Data composition system.
The following subordinate fields are implemented for data composition system fields that have Data among their types: BegOfDay, BegOfWeek, BegOfTenDays, BegOfMonth, BegOfQuarter, BegOfHalfYear, BegOfYear, EndOfDay, EndOfWeek, EndOfTenDays, EndOfMonth, EndOfQuarter, EndOfHalfYear, EndOfYear, Day, WeekDay, WeekDayName, DayOfYear, WeekOfYear, Month, MonthName, Quarter, Year, BegOfMinute, BegOfHour, EndOfMinute, EndOfHour, Minute, and Hour.This feature was not provided. One could use user-defined expression fields to retrieve this data.Simplified end-user operations with fields that include date and time.
1C:Enterprise script.
The following string processing functions are implemented:
  • StrTemplate() - replaces variables (such as %1) in a template string by actual values.
  • StrCompare() - performs lexicographic comparison of strings, case-insensitive.
  • StrstartWith() - checks whether a string begins with a substring.
  • StrEndsWith() - checks whether a string ends with a substring.
  • StrFind() - searches for a substring in both directions, anywhere in the line.
  • SrtSplit() - splits a string into substrings based on the specified delimiter.
  • StrConcat() - merges strings included in the array of substrings.

The SearchDirection system enumeration is implemented.

The Find() function is declared obsolete, it is supported for compatibility purposes.

This change is not implemented in 8.3.5 compatibility mode.

This feature was not provided.

Developers had the option to implement the functionality introduced in the new functions using 1C:Enterprise script.

Simplified implementation of some standard string processing algorithms.
Web client.
Storing accumulated web client statistics is implemented. This feature is intended for 1C Company experts. To enable it, run the web client with the SYSTEMWEBCLIENTSTAT command-line option.This feature was not provided.The set of tools intended for platform performance quality control is expanded with a new tool.
Spreadsheet documents.
Importing data from XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument) formats to spreadsheet documents is implemented. This operation can be performed both interactively and from 1C:Enterprise script.

The SpreadsheetDocumentValueReadingMode system enumeration is implemented. For the Read() method of the SpreadsheetDocument object, the ValueReadingMode parameter is implemented.

Support of pasting areas copied to the clipboard from Microsoft Excel and OpenOffice Calc documents is implemented.

This feature was not provided.Simplified data import from spreadsheet documents of the following formats: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010), and ODS (OpenDocument).
Data composition system.
Dynamic lists.
For the DataCompositionSettingsComposer object. the GetAvailableSettingsSource() method is implemented.This feature was not provided.Simplified access to the available settings source of a data composer from another data composer. For example, you can use this feature when you open a new data composition settings editor form that uses the same source as the previous form.
Internet-enabled functionality.
Web services and HTTP services.
You can process JSON data using both stream and object approaches.

The following objects can be serialized to or deserialized from JSON: primitive types, Array, FixedArray, Structure, FixedStructure, Map, and FixedMap.

The JSONReader and JSONWriter objects are implemented. The WriteJSON(), ReadJSON(), WriteJSONDate(), and ReadJSONDate() global context methods are implemented.

This feature was not provided.

One could implement processing JSON data using 1C:Enterprise script tools.

Simplified interaction with applications (including web applications) that use JSON data format.

You can store various data types in JSON format, which provides an alternative to other formats, such as XML.

Web services and HTTP services.
Web services and HTTP services.

For the standard OData interface, getting responses in JSON format is implemented.

This feature was not provided. +For the standard OData interface, responses were only available in Atom format. +The OData format is supported in more detail.

Using JSON format minimizes the volume of data transferred between the client and the server.

Queries.
You can use logical expressions in descriptions of selection fields and in query result filter expressions (in the WHERE clause).This feature was not provided.

If a logical expression was required for describing a selection field, you had to use a selection clause.

Logical expressions in the WHERE clause could be connected only by AND, OR, and NOT logical operators, and they could not be composite.

Simplified writing and understanding of complex queries.
Server clusters.
Administration tools.
The automatic server cluster status monitoring feature is implemented. This includes monitoring of several cluster parameters and termination of processes that might cause any issues. The central cluster server agent performs the monitoring. The monitoring results are recorded to the technological log.

For the cluster, the Server errors threshold and Terminate corrupted processes properties are implemented.

For the IServerAgentConnection object, the SetClusterRecyclingErrorsCountTheshold() and SetClusterRecyclingKillProblemProcesses() methods are implemented.

For the rac utility, the --errors-count-threshold and --kill-problem-processes command-line options are implemented.

For the technological log, the ATTN event is implemented.

Automatic server cluster status monitoring was not provided.Increased server cluster reliability by timely detection and termination of processes that might cause issues.
Automated testing.
The automated testing supports the Taxi interface. New automated testing features are added:
  • For the TestedClientApplicationWindow, the StartPage property is implemented.
  • Navigation between windows is implemented. For the TestedClientApplicationWindow object, the GotoStartPage(), GotoNextWindow(), GotoPreviousWindow(), and CloseUserMessagesPanel() methods are implemented.
  • New options for testing managed form fields:
  • Create an item. For the TestedFormField object, the Create() method is implemented.
  • Cancel editing field data. For the TestedFormField object, the CancelEdit() method is implemented.
  • Open a drop-down list, wait for drop-down list generation, and select a list item. For the TestedFormField object, the OpenDropList(), CloseDropList(), ExecuteChoiceFromDropList(), WaitForDropListGeneration(), and DropListIsOpen() methods are implemented.

+

The automated testing did not support the Taxi interface.The automated testing can be used with the Taxi interface.
Data composition system.
Dynamic lists.
Items of report user settings and dynamic list user settings can be linked to managed form tables.

For the DataCompositionUserSettings object, the Filter, Order, Selection, ConditionalAppearance, and Structure columns are implemented.

The report user settings form and the dynamic list user settings form are modified: instead of text boxes with the option to open editors (filter, order, and so on), tabs with tables are implemented to provide uniformity with the data composition schema editor in Designer.

The Settings command of the report form is displayed in the main form command bar.

Items of user report settings and dynamic list settings could be linked only to managed form text boxes.

The report and dynamic list user settings forms had a different layout.

The Settings command of the report form was available in the More menu.

Improved standard report and dynamic list user settings form.
Managed forms.
For the Enum metadata object, the ChoiceHistoryOnInput property is implemented. This property defines whether the choice history of a text box linked to an attribute of enumeration type is displayed and saved.

For enumerations whose values can be selected in a form, the input history is displayed and saved automatically.

This change is not implemented in 8.3.5 compatibility mode.

This feature was not provided.

The choice history for a text box linked to an attribute of enumeration type was neither displayed nor saved.

 +

You can specify whether the choice history for a text box linked to an attribute of enumeration type is displayed and saved.

Data composition system.
For the DataCompositionDetailsFieldValues object a constructor is implemented.The DataCompositionDetailsFieldValues object did not have a constructor.You can fill detailed data using 1C:Enterprise script.
Web services and HTTP services.
For the HTTPConnection object, you can call any HTTP methods (passing the method name as a string). In order to simplify the usage of PATCH and HEAD HTTP methods, the Patch() and Head() methods are implemented for the HTTPConnection object.These features were not provided.

The HTTPConnection object could only be used to call the GET, PUT, POST, and DELETE methods.

Easier access to the full range of HTTP methods from applied solutions.
Server clusters.
Administration tools.
External session management functionality is extended. Methods that are called when a session is hibernated or restored from hibernation are implemented. You can specify a timeout for the external session management web service response.

For the external session management web service, the onHibernateSession() and onWakeupSession() methods are implemented.

For external session management web service connection string, the optional parameters are implemented: tout sets an external session management web service response timeout, and wsver specifies the external session management web service interface version. The new features are only available if the wsver parameter is set to 2.

These features were not provided.The web service behavior is uniform with the licensing subsystem behavior.
XML and XDTO support.
FastInfoSet operations are refactored.FastInfoSet operations had a different implementation.Improved stability of FastInfoSet operations.
Full-text search.
The full-text search index integrity check is implemented. For the full text search manager, the CheckIndex() method is implemented.

The full-text search index update operations are recorded to the tecnological log. In the tecnological log, the FTEXTCheck and FTEXTUpd events are implemented. In the technological log the ftextupd item is implemented.

These features were not provided.Improved stability of full-text search. +An invalid full-text search index can be rebuilt.
Queries.
For the QuerySchemaTempTableDescription object, the TableName property is implemented. You can specify a temporary table name in the query builder.

For the QuerySchemaSources object, the Alias parameter of the Add() method is implemented.

These features were not provided.Improved functionality of the query software model.
Development tools.
Common attributes / Data separation.
Configuration extensions.
More options for modification of applied solutions (including cloud systems) without disabling their support. You can create configuration extensions and use them to implement applied solution modifications (which do not affect the data structure), so that the applied solution support is not disabled, and all modifications take place in a dedicated object (extension), which is easily connected to and disconnected from the applied solution.

You can use extensions to modify forms, create reports and data processors, and create new subsystems. You can apply a configuration extension both in 1C:Enterprise mode and in Designer. You can specify a custom extension set for each separated infobase area.

This feature was not provided. Applied solution developers could create external reports and data processors and modify the applied solution configuration, which resulted in disabling support and did not allow making modifications in different areas of a separated infobase.The new feature is intended for making small configuration modifications at the deployment stage (including modifications of separated infobases and cloud systems) more easily and with less dependence on vendor configuration modifications.
Data display.
New pictures are added to the picture library: GoForward, GoBack, GoToBegin, GoToEnd, Today, ShowInList.The listed pictures were not available in the picture library.More content for the picture library.
Database configuration updates.
The documentation describes Designer batch mode command-line options that manage background and dynamic database configuration updates.The new Designer batch mode command-line options that manage background and dynamic database configuration updates were not listed in the documentation.Fixed documentation error.
System requirements.
Web client.
Support of Microsoft Windows 10 operating system is implemented.

Support of Microsoft Information Services 10.0 web server is implemented.

Support of Microsoft Edge web browser is implemented, with the following limitations:

  • Add-ins are not supported
  • File system extension is not available
  • Cryptography extension is not available
Microsoft Windows 10 operating system was not supported.

Microsoft Information Services 10.0 web server was not supported.

Microsoft Edge web browser was not supported.

Extended list of supported operating systems and web browsers.
DBMS operations.
Support of PostgreSQL version 9.4 is implemented.This PostgreSQL version was not supported.Extended list of supported PostgreSQL versions.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Command interface.
In the Taxi interface, in the functions menu, you can search for commands by their presentations. The search is performed in all sections (not only in the commands of the current section).

Commands for specifying navigation and action panel settings are moved to the submenu to the right of the search field.

In the Taxi interface, pressing F10 opens the functions menu.

The option to search for a command by a part of its presentation was not provided.

Commands for specifying navigation and action panel settings were displayed as links in the right part of the functions menu.

In the Taxi interface, pressing F10 opened the main menu.

Improved usability of the function menu.
Managed forms.
If all of the managed form command bar buttons have their OnlyInAllActions parameters set to False and some of these buttons do not fit the command bar width, the More button is added to the command bar, with a submenu that contains all of the command bar commands.If all of the managed form command bar buttons had their OnlyInAllActions parameters set to False and some of these buttons did not fit the command bar width, there was no way to access the commands that did not fit.If the command bar has small size, all of its commands are still available.
Client application.
You can fully replace the splash screen that is displayed during the startup of the thin, thick, and web clients.

To replace a splash screen in your applied solution, submit a request to 1C Company

This feature was not provided.In particular cases, you can use a splash screen that is fully customized by the company that uses the applied solution, provided that the splash screen is approved by 1C Company.
Web client.
Web browser pop-up windows are no longer displayed during the printing of spreadsheet documents.When spreadsheet documents were being printed, web browser pop-up windows were displayed.Simplified printing of spreadsheet documents for end users.

In the Taxi or Forms in tabs interface mode, if the applied solution does not use modal calls, it does not require additional web browser setup.

Managed forms.
In managed forms, if the Create command is available for a text box, it is present in the context menu of the text box.The Create command was never present in text box context menus.Improved usability of text boxes.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Full-text search.
The full-text search algorithm is optimized for scenarios where a search string is used multiple times (for example, getting the next batch of search results).

The full-text search algorithm is optimized for scenarios where a user does not have access rights for some objects returned by the search.

The full-text search performance was insufficient.Improved full-text search performance for infobases containing a large number of items, and also in scenarios where a user does not have access rights for some objects returned by the search.
Full-text search.
Optimized memory usage for fuzzy search (the search that uses the # operator). The search for similar words is optimized.Fuzzy search might cause a memory overflow which, in turn, caused the system shutdown.

The search for similar words might take a long time.

Increased stability of the fuzzy search in scenarios where the full text search index has a large size.
Web client.
The web client performance is improved in the following scenarios:
  • Loading web client,. including scenarios with slow connection
  • Opening forms
  • General performance improvements in a variety of scenarios

The web client now uses Google Closure Compiler. +

The web client performance was insufficient.Improved web client performance.
1C:Enterprise script.
The loading time of 1C:Enterprise script modules is slightly reduced.The loading of 1C:Enterprise script modules was not fast enough.Slightly reduced startup time for applied solutions that include a large number of 1C:Enterprise script modules.
Client application.
The startup time of the client application (before the authentication dialog appears) is slightly reduced.The client application startup was not fast enough.Slightly reduced startup time of the client application.
Configuration repositories.
The performance of the following operations is improved:
  • Creating a repository
  • First connection to a repository
  • Storing objects in a repository
  • Updating objects from a repository
  • Updating configuration from a repository

The performance of compatibility mode change operations is improved.

The 1C:Enterprise version 8.3.3 compatibility mode is implemented for configuration repositories.

The configuration repository performance is improved in scenarios where the configuration repository compatibility mode is set to Do no use.

The performance of configuration repository operations was insufficient.Improved configuration repository performance.
Managed forms.
The strong data compression algorithm for large data volumes (more than 64 KB) transferred between the client and the server (or a web server extension) is optimized. This slightly reduces the time required to open managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.The strong data compression algorithm was less efficient.Slightly reduced time of opening managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.
Web services and HTTP services.
Faster processing of requests that call the standard OData interface.Performance of requests that called the standard OData interface was insufficient.The performance of operations with the standard OData interface is improved.
Managed forms.
Improved performance of opening managed forms in the following scenarios:
  • A form has a large number of items.
  • A form has a large number of attributes.
  • The list of attributes and form items is significantly changed using 1C:Enterprise script.
  • A large number of users are working with managed forms.
The performance of opening managed forms in the listed scenarios was lower.Improved usability of managed forms.
Managed forms.
Managed form conditional appearance is optimized.The performance of managed form conditional appearance was lower.Improved usability of managed forms with conditional appearance.
Development tools.
Performance of base configuration updates (update configuration from file, load configuration from file, and get specific configuration version from configuration repository) is improved.Performance of base configuration updates was insufficient.Better usability for developers.
DBMS operations.
Administration tools.
For the file mode, the option to restructure the infobase so that all data required to open the infobase is at the beginning of the 1Cv8.1CD file is implemented. This improves the performance of infobase opening.

This type of restructuring is performed during the compressing of infobase tables (which is available from a Designer dialog box and as a command-line option), or during infobase verification with the chdfl utility with the Correct errors check box selected.

It is recommended that you always perform this optimization after you make any configuration changes (and the associated infobase restructuring) that result in database structure changes.

Internal information required for opening an infobase was evenly distibuted within the 1Cv8.1CD infobase file.Improved performance of opening file infobases, especially in scenarios where the infobase is located on a network resource.
DBMS operations.
In client/server mode with PostgreSQL DMBS, the query that is executed when deleting records from tables of extra dimensions of accounting registers is optimized.In client/server mode with PostgreSQL DMBS, the performance of the query that was executed when deleting records from tables of extra dimensions of accounting registers was insufficient.Improved performance of deleting accounting register records.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Client application.
When a client application is restarted with the /AppAutoCheckMode key, the platform checks the user rights for running the client application. If the user attempts to start the application in the ordinary mode and does not have the right to run the thick client, they are not allowed to access the infobase. In other scenarios the client application that suits the selected start mode best is selected.When a client application was restarted with the /AppAutoCheckMode key, the platform did not check the user rights for running the client application.The client application selection algorithm is improved.
Managed forms.
If editing text in a form field extension for a text box is not allowed (the TextEdit property is set to False), the drop-down list of that box does not display the text "Enter the search string".The drop-down list always displayed the text "Enter the search string".The recommendation to perform an action that is not allowed is no longer displayed.
Development tools.
During the merging of configurations you can modify the results of module merging. You can use external software (not incorporated in Designer) for comparing and merging module texts.

You can specify the external software in the Designer options dialog box.

Ready-to-use settings are available for the following external software:

  • For Windows: Araxis Merge, KDiff3, TortoiseMerge, Perforce P4Merge, and DiffMerge
  • For Linux: KDiff3 and Perforce P4Merge

You can specify settings for external software that is not on the list.

The results of module merging could not be modified while merging configurations.

Only built-in Designer features were available for comparing and merging module texts.

Developers can use any tool that they find convenient for comparing and merging module texts. They can make changes during the merging of configurations (with the help of external software).
Development tools.
Improved setup for the comparison and merging of managed forms. You can specify the comparison and merging rules for a form and for its module directly in the comparison and merging dialog box.The comparison and merging rules for managed forms were specified in another dialog box. Also, the rules for the form itself and for its module were separated.Simplified setup for the comparison and merging of managed forms and their modules.
Development tools.
The following features are implemented in the managed form editor:
  • If the Title property of a managed form is not empty, its value is displayed in the window title in the preview area.
  • Clicking a title if the preview area selects the entire form. Right-clicking the title opens the form context menu.
The window title bar in the preview area of the form editor did not have any functionality.Improved usability of the form preview area in the managed form editor.
Internet-enabled functionality.
Automatic selection of text encoding in email messages containing national characters is implemented. The automatic selection is only performed when the text contains national characters but their encoding is not specified, which does not comply with the standard. This applies to the following email message parts:
  • Message headers
  • Message body
  • Message header parameter values, such as attachment file name.
Email message text was displayed in incorrect encoding when no encoding was specified.Email messages that do not comply with the standard are processed correctly.
Background and scheduled jobs.
The duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases is reduced. Now the duration of the first access is approximately the same as the duration of subsequent accesses.The long duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases might cause the user interface to stop responding until loading the backgound job scheduler was complete.Reduced duration of the first access to the background job manager (the BackgroundJobs global context property) in file infobases.

Faster start of client applications in the file mode (when the background job manager is accessed during the startup).

Background and scheduled jobs.
In file infobases, if a client application that performs background jobs is closed, the background jobs are terminated after a 30-second timeout. When a job is terminated, a_$Job$_.Terminate event is recorded to the event log.In file infobases, if the platform could not complete background jobs correctly, it displayed a message prompting the user to choose between waiting and terminating the jobs.Eliminated unexpected (and not user-friendly) system behavior.
Error handling.
When properties or methods of MetadataObject objects related to external reports or data processors that are no longer available are accessed, the platform generates an exception.When properties or methods of MetadataObject objects related to external reports or data processors that were no longer available were accessed, the platform was shut down unexpectedly.Improved system stability.
Development tools.
Internet-enabled functionality.
The following information is added to the Syntax Assistant:
  • SSL is supported for POP3 and SMTP.
  • Secure connection does not support checking server and client certificates.
  • Descriptions of the InternetMail object methods that require IMAP connection now reflect that fact.
  • The list of fields filled in the GetHeaders() method of the InternetMail object is provided.
The Syntax Assistant did not contain this information.Improved Syntax Assistant quality.
Spreadsheet documents.
When a spreadsheet document is exported to Microsoft Excel 2007-2010 format, its comments are converted to Excel table comments.

This change is not implemented in 8.3.5 compatibility mode.

When a spreadsheet document was exported to Microsoft Excel 2007-2010 format, its comments were converted to Excel pictures.Better conversion of spreadsheet document items to Microsoft Excel format.
Background and scheduled jobs.
When a client application is started with a file infobase, there is a 1-minute delay before starting the execution of scheduled jobs.When a client application was started with a file infobase, there was no delay before starting the execution of scheduled jobs.Faster startup of client applications in file mode.
Defined types.
During the update of a supported configuration you have the option to merge the following properties with priorities: the Type property of the DefinedType configuration property and the Type property of the ChartOfCharacteristicTypes object.This feature was not provided.Improved algorithm for comparing and merging defined types, which simplifies usage of those types in library development tasks.
Managed forms.
Presentations of items found during the input by string with full-text search enabled are identical to presentations of items found with full-text search disabled.

The order of items in drop-down lists generated by the input by string feature with full-text search enabled matches the order of items returned by the full-text search algorithm.

The algorithm that generates presentations for Task objects in drop-down lists generated by the input by string feature is modified.

Presentations of items found during the input by string with full-text search enabled were different from presentations of items found with full-text search disabled.

The order of items in drop-down lists generated by the input by string feature with full-text search enabled was not defined.

The algorithm that generated presentations for Task objects in drop-down lists generated by the input by string feature was different.

Improved usability of the input by string feature. Unified generation of presentations for search results.
Configuration repositories.
The configuration repository window now displays names of computers where objects are locked.The configuration repository window displayed the name of the computer that the current user used for their first connection to the repository.Eliminated unexpected system behavior.
Internet-enabled functionality.
For the InternetMailMessage object, the PostingDateOffset property is implemented.This feature was not provided.You can define the true date of sending an email message.
Dynamic lists.
When a form is opened, the Period property of managed form table extension for dynamic lists and the Representation property of a form table linked to a dynamic list are loaded simultaneously with dynamic list user settings.

It is recommended that you get the Period property in the OnLoadUserSettingsAtServer managed form event handler.

This change is not implemented in 8.3.5 compatibility mode.

The Period property of managed form table extension was obtained from the user settings before the execution of the OnCreateAtServer managed form event handler.

The Representation property of a form table linked to a dynamic list was obtained from the client settings during the form opening.

 +

The Period and Representation properties are stored in a similar way to other dynamic list settings, which simplifies operations with these properties using 1C:Enterprise script.

Spreadsheet documents.
When nonempty spreadsheet document cells with Placement properties are set to Auto are displayed, the cells are not merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document.When nonempty spreadsheet document cells with Placement properties set to Auto were displayed, the cells were merged up to the next filled cell or up to the horizontal boundary of the spreadsheet document.The spreadsheet document view in the web client is now closer to the spreadsheet document view in the thin client.
DBMS operations.
In the client/server mode with Oracle Database DBMS, executing a query that contains a subquery in the SELECT section and also an aggregate function adds a GROUP BY section with a constant, provided that such section is not yet present in the query.In the client/server mode with Oracle Database DBMS, executing a query that contained a subquery in the SELECT section and also an aggregate function resulted in the ORA-937 run-time error.Improved stability of Oracle Database operations.
Managed forms.
The prevention of unexpected working process or client application shutdown due to managed form operation issues (loss of synchronization between the client and server parts of form data) is implemented. When an issue is detected, only the affected session is closed, and the working process that processes the session is not shut down. By default, the issue details are recorded to the technological log.A loss of synchronization between the client and server parts of form data could result in a shutdown of the client application or a working process that processed the affected session. +

Improved 1C:Enterprise server stability during managed form operations.

DBMS operations.
The chance of deadlocks in queries that include comparisons with UNDEFINED is reduced.The chance of deadlocks in queries that included comparisons with UNDEFINED was higher.Increased system stability. Reduced chance of deadlocks that do not have obvious reasons.
Client application.
Managed forms.
Data display.
For client applications that run on Windows operating systems, Windows scaling is supported. If a custom DPI value is set, interface items are scaled correctly, except pictures that might look a bit blurry.Client applications that run on Windows operating systems had scaling issues.Eliminated unexpected system behavior in scenarios where a user sets a custom DPI value for their display.
Configuration repositories.
When a user cancels binding to a configuration repository or when an infobase bound to a repository changes location, the dialog box stating that unbinding from the repository is required is no longer displayed.

To unbind a configuration from a repository, you can use the corresponding Designer command.

When a user canceled binding to a configuration repository or when an infobase bound to a repository changed location, the dialog box stating that unbinding from the repository was required was always displayed.Improved usability of configuration repositories in some scenarios.
Command interface.
The visibility settings for commands in subordinate subsystems are no longer lost when command interface settings of a subsystem that contains subordinate subsystems are copied using the Load() and Save() methods of the StandardSettingsStorageManager object.When command interface settings of a subsystem that contained subordinate subsystems were copied using the Load() and Save() methods of the StandardSettingsStorageManager object, the visibility settings of commands in subordinate subsystems were lost.Eliminated unexpected system behavior.
Web client.
Spreadsheet documents.
In the web client, the option to select pictures in spreadsheet documents is implemented, and when they are selected, the respective event is called.

Improved representation of pictures in spreadsheet documents when viewed in the web client:

  • Cells overlapped by a picture are not merged.
  • Text and pictures in spreadsheet document cells can overlap each other.
  • Eliminated issues that appeared when picture borders were close to cell borders.
 +

Selecting pictures in spreadsheet documents was not supported. Spreadsheet documents had some picture-related issues.

Improved quality of displaying spreadsheet documents with pictures in the web client.
Development tools.
Mobile application.
The picture editor dialog box in Designer supports editing template pictures and the new picture variants format that includes a manifest.

Template pictures are used in applied solution development for the mobile platform.

Editing template pictures and the new picture variants format that includes a manifest were not supported.Template picture support is implemented.
DBMS operations.
The DBMS request that the platform generates based on the VALUETYPE function of the query language is simplified.The DBMS request based on the VALUETYPE function was more complicated.Eliminated issueds that occured when DBMS could not process a complex request.
Development tools.
During configuration merging and during configuration repository operations, the platform does not perform refactoring operations that are normally performed when configuration objects are renamed or deleted.During configuration merging and during configuration repository operations, the platform performed refactoring operations that were normally performed when configuration objects were renamed or deleted.Eliminated unexpected system behavior.

Operations whose results were ignored are not performed.

1C:Enterprise script.
If an object is passed to a method written in 1C:Enterprise script and its set of properties is changed during the method execution but the property names are not changed, the object property calls are executed correctly. In particular, when a method being executed adds a property, calls of other properties are executed correctly. If any property names are modified, object property calls might not be executed correctly.

This change is not implemented in 8.3.5 compatibility mode.

If an object was passed to a method written in 1C:Enterprise script, the method called object properties by their numbers, which were defined at the moment the method was called. If a property number was changed during the method execution (for example, a new property was added), this was not taken into account and the property call was performed using the old number.Improved system reliability and reduced chance of errors when a set of properties is changed during method execution.
Managed forms.
In the thin client, formatted strings that are defined during the generation of a drop-down list are displayed accordingly to their formatting if the text box is linked to an attribute of complex type and this attribute has the Undefined value.In the thick client, formatted strings that were defined during the generation of drop-down lists were displayed without formatting if the text box was linked to an attribute of complex type and this attribute had the Undefined value.Eliminated unexpected system behavior.
Web client.
Managed forms.
In the web client, drop-down lists have the same color scheme as in other client applications.In the web client, drop-down lists had a color scheme different from the color scheme used in other client applications.In the web client, drop-down list appearance is uniform with other client applications.
Web client.
In the web client, the appearance of the following interface items is almost identical to their appearance in the thin client:
  • form button
  • command bar button
  • command bar
  • separator +
In the web client, the appearance of the following interface items was different from their appearance in the thin client:
  • form button
  • command bar button
  • command bar
  • separator
Uniform client application appearance.
Command interface.
When a user command group is deleted, standard commands that belong to the group are automatically moved to the default standard group specified for those commands.

This change is not implemented in 8.3.6 compatibility mode.

When a user command group was deleted, standard commands that belonged to the group were no longer available in the command interface.Eliminated unexpected system behavior.
Event log.
The UnloadEventLog() method truncates the event time passed to it to an integer number of seconds.

When a filter by time is applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() method), an event is included in the result even if the millisecond part of the actual event time exceeds the millisecond part of the time specified in the filter.

The UnloadEventLog() method provided the event time with millisecond accuracy. When a filter by time was applied to the event log (UnloadEventLog(), CopyEventLog(), or ClearEventLog() methods), an event was included in the result only if the exact condition was met (including the millisecond part).Eliminated unexpected system behavior.

The behavior of the .lgd log is uniform with that of the .lgf log (regarding the event time presentation and filter functionality).

Print tools.
Spreadsheet documents.
The algorithm that calculates spreadsheet document column width for printing is modified. The printed document column width more closely matches the on-screen column width. The chance is noticeable in spreadsheet documents with background pictures.

This change is not implemented in 8.3.5 compatibility mode.

+

For spreadsheet documents, the printed document column width did not exactly match the on-screen column width.

+

Improved print layout of spreadsheet documents.
Regional settings.
For Russia, a single one-hour time zone shift is applied in line with Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.The platform did not reflect the changes introduced by Federal Laws 453-FZ, 27-FZ, 57-FZ, 58-FZ, 59-FZ, and 69-FZ.The time offset changes introduced by the new law are implemented.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Internet-enabled functionality.
Future 1C:Enterprise versions will not support NSS certificates and related objects, regardless of the compatibility mode.

The NSSSecureConnection object will be unavailable for use in 1C:Enterprise script and in thin client HTTPS connection settings.

1C:Enterprise system supports NSS certificates.Future platform versions will not support NSS certificates.
Automated testing.
For the TestedFormGroup object, the CurrentVisible() function returns False if the object is linked to form group, which is inactive page located in a page group where tabs are not displayed.

This change is not implemented in 8.3.5 compatibility mode.

For the TestedFormGroup object, the CurrentVisible() function returned True if the object was linked to a form group, which was an inactive page located in a page group where tabs were not displayed.The automated testing feature emulates the system functioning and provides form item status data more accurately.
Managed forms.
For managed form attributes of spreadsheet document, graphical schema, and text document types, calling the Show() method raises an exception.

This change is not implemented in 8.3.5 compatibility mode.

The system behavior depended on the attribute location on a form and the client application type:
  • The attribute is linked to a managed form item:
    • Thin client:
      • Spreadsheet document: the current form is activated.
      • Graphical scheme: a new form with a copy of the scheme is opened.
      • Text document: a new form with a copy of the document is opened.
    • Web client:
      • For attributes of any type (spreadsheet document, graphical schema, or text document) the current form is activated.
    • The attribute is not linked to a managed form item:
    • Thin client:
      • For attributes of any type (spreadsheet document, graphical schema, or text document), a form with a copy of the document is opened.
    • Web client:
      • Spreadsheet document: a new form with a copy of the document is opened.
      • Graphical scheme: the current form is activated.
      • Text document: the current form is activated.
Unified behavior of various objects in different client applications.
Managed forms.
In the thin and thick clients, buttons (or hyperlinks) located in managed forms become unavailable when commands (or hyperlinks) linked to these buttons become unavailable.

This change is not implemented in 8.3.5 compatibility mode.

In the thin and thick clients, buttons (or hyperlinks) located in managed forms stayed available even when commands (or hyperlinks) linked to these buttons were unavailable.The system behaves as expected.

Unified system behavior in different client applications.

Managed forms.
When an item is created in the drop-down list of a text box, you can verify whether the created item matches the choice parameters used for opening the new item form. If the item does not match the choice parameters, a diagnostic message is displayed and the created item is not placed in the text box.

The verification is implemented for managed form extensions for objects, catalogs, documents, charts of characteristic types, business processes, and tasks.

The following features are implemented:

  • ChoiceParameters standard property of the managed form extension
  • ChoiceParameters property of the managed form extension
  • ChoiceAvailable property of the managed form extension
  • ValueChoice event of the managed form extension

The ChoiceParameters and ChoiceAvailable properties of the managed form extension are not available in version 8.3.5 compatibility mode.

A new item that did not match the choice parameters specified for a text box could be created and selected in the text box.Reduced chance of creating items (from a text box choice list) that do not match the choice parameters specified for the text box.
Managed locks.
The Period field whose value is specified in a periodic information register record set filter is included in the set of managed lock fields for read and write operations on record set data.

This change is not implemented in 8.3.5 compatibility mode.

The Period field was not included in the set of managed lock fields for read and write operations on periodic information register record set data.Improved user experience for periodic information register operations. Reduced chance of deadlocks.
Common attributes / Data separation.
Information registers.
When an information register data set is recorded, the default values of independent and shared separators that include the information register are replaced by the separator values set in the current session.

If a separator value is not identical to the default value of that separator type or is not equal to the separator value set in the current session, an error is generated.

This change is not implemented in 8.3.5 compatibility mode.

When an information register data set was recorded, the default values of independent and shared separators that included the information register were always replaced by the separator values set in the current sessionEliminated unexpected system behavior.
Internet-enabled functionality.
When the InternetMail object is used for interaction with a Microsoft Exchange server, if the filter criterion string value (the Filter parameter of the GetHeaders() and GetUIDL() methods of the InternetMail object) only includes US-ASCII characters, the platform notifies the Exchange server about this in addition to passing the string to the server. Otherwise the platform passes a UTF-8-encoded string.

If the filter criterion string value passed to the Exchange server contains not only US-ASCII characters (for example, it includes Cyrillic characters), an error is generated.

This change is not implemented in 8.3.5 compatibility mode.

The GetHeaders() and GetUIDL() methods of the InternetMail object always returned an empty array when a string value of the Filter parameter was used in interactions with Microsoft Exchange.Improved compatibility with Microsoft Exchange during operations with the InternetMail object. You can search in the filter criterion string if all its characters belong to the US-ASCII encoding.
Internet-enabled functionality.
The libetpan library is used to work with IMAP, SMTP, and POP3.

This change is not implemented in 8.3.5 compatibility mode.

The UW IMAP toolkit library was used to work with IMAP, SMTP, and POP3.Improved performance and stability of email management features.
Internet-enabled functionality.
During the creation of an InternetProxy object on Linux operating systems, if the DefaultProxy constructor parameter value is True and the platform cannot find the file inetcfg.xml, the constructor uses the values of the following operating system environment variables: http_proxy, https_proxy, ftp_proxy, ftps_proxy, and all_proxy.

The methods of the HTTPConnection and FTPConnection objects do not attempt to determine the proxy server settings. Instead, they use the settings stored in the Proxy property of the respective object.

For the Set() method of the InternetProxy object, the User and Password parameters are implemented. For the InternetProxy object, the User and Password methods are implemented. The User and Password properties of the InternetProxy object are declared obsolete, they are suported for compatibility purposes.

This change is not implemented in 8.3.5 compatibility mode. +

Environment variables were never used for creation of InternetProxy objects on Linux operating systems. If the proxy server parameters were not specified during the creation of HTTPConnection and FTPConnection objects, methods of these objects attempted to retrieve the proxy server settings from environment varaibles.Eliminated the difference in platform behavior on Windows and Linux operating systems. Eliminated unintuitive platform behavior where methods of HTTPConnection and FTPConnection objects attempted to determine the proxy server settings.
Client application.
Idle handlers are not called while a client application is locked using the LockApplication() global context method or the Temporary lock command.

This change is not implemented in 8.3.5 compatibility mode.

Locking a client application using the LockApplication() global context method or the Temporary lock command did not affect the execution of idle handlers.Increased system security.
xBase support.
If an error occurs during a .dbf file operation performed using the XBase object, an exception is generated. +This change is not implemented in 8.3.5 compatibility mode.If an error occurred during a .dbf file operation performed using the XBase object, dialog boxes were generated.Eliminated scenarios that looked as if the platform stopped responding (for example, errors generated by .dbf file operations at 1C:Enterprise server side).
Managed forms.
For the TypeLink object constructor, you can specify the first parameter (DataPath) as an empty string.The TypeLink object constructor did not accept an empty string as the DataPath parameter value.You can clear the TypeLink property of a managed form field by replacing its value with a new object of that type that does not have the data path specified.
External data sources.
For the ExternalDataSourceTableObject, the GetChangeableFields() and SetChangeableFields() methods are implemented. These methods are intended both for restricting the list of writable external data table fields and for expanding that list with fields have the read-only flag set in the configuration (the ReadOnly property set to True). The GetFieldsToWrite() and SetFieldsToWrite() methods are declared obsolete, they are supported for compatibility purposes.The GetFieldsToWrite() and SetFieldsToWrite() methods only provided the option to reduce the number of fields that were recorded to external data source tables. The option to record data to fields that are marked as read-only in Designer was not provided.The platform supports custom algorithms for external data source management. For example, data that is normally not recorded to external data source table fields can now be recorded using a custom algorithm.
Administration tools.
When a list of infobases is updated or when a client application distribution kit is downloaded via the Internet, the root certificates of certification authorities are obtained from the Windows certificate store.When a list of infobases was updated or when a client application distribution kit was downloaded via the Internet, the root certificates of certification authorities were only obtained from the cacert.pem file.Improved usability of self-signed certificates in the enterprise environment.
Server clusters.
You can specify the user on whose behalf the cluster manager (rmngr) is started, and it can be different from the user on whose behalf the cluster agent (ragent) is started.

You can specify users on whose behalf the cluster manager (rmngr) and working processes (rphost) is started for each cluster on a given computer.

You can specify a custom cluster register directory for each cluster manager (rmngr) on a given computer.

The following parameters and parameter groups are implemented for the swpuser.ini file:

  • the rmngr_user and rmngr_pass parameters
  • the registry parameter
  • the <PortName:> parameter group, which can contain all of the swpuser.ini file parameters.
Only the user on whose behalf the working process (rphost) was started could be changed.You can increase server cluster security in scenarios like this: service users use their own applied solutions, external data processors, and add-ins whose access to the server cluster computer infrastructure should be restricted.
Data access restrictions.
Access restriction template parameters that are specified in comments are not replaced by actual values when the template is applied.

This change is not implemented in 8.3.5 compatibility mode.

Access restriction template parameters that were specified in comments were not replaced by actual values when the template was applied.Increased stability of the access restriction system in some scenarios.
Data composition system.
The option to use nested reports during the export of data composition result to a value collection is implemented.

Columns with duplicate names are never created during the export.

This change is not implemented in 8.3.5 compatibility mode.

The option to use nested reports during the export of data composition result to a value collection was not available.

The check for duplicate column names was never performed during the export, so columns with duplicate names might be created.

Extended data composition system functionality.
Data composition system.
When additional data is displayed for hierarchical records, hierarchical record data is used.

This change is not implemented in 8.2.16 compatibility mode.

+

When additional data was displayed for hierarchical records, the detailed record data was used.Reports display expected data: if a report contains a table with hierarchical groupings in its rows, the data obtained from the hierarchical records is displayed in the columns of additional data for hierarchical grouping rows, not from the detailed records, as it was implemented earlier.
Data composition system.
The value assigned to the Text conditional appearance parameter, which is enabled, is applied to fields of predefined grouping templates and fields of data composition system reports.

This change is not implemented in 8.3.5 compatibility mode.

The value assigned to the Text conditional appearance parameter, which was enabled, was not applied to fields of predefined grouping templates or fields of data composition system reports.Predefined grouping templates can be used together with the Text parameter of data composition conditional appearance.
Data composition system.
The appearance of cells that store parent grouping fields is based on the field expressions obtained for the current grouping.

This change is not implemented in 8.3.5 compatibility mode.

The appearance of cells that stored parent grouping fields was based on the field expressions obtained for the parent grouping.The cell appearance is formed as expected.
Dynamic lists.
If the platform cannot generate the list of available dynamic list settings, an exception is generated and the form is not generated.

This change is not implemented in 8.3.5 compatibility mode.

If the platform could not generate the list of available dynamic list settings, no exceptions were generated and the managed form continued functioning as if the dynamic list data source did not have any fields available. All of the form items related to dynamic list data disappeared from the managed form.Improved error diagnostics during dynamic list operations.
Data composition system.
The data composition template composer uses detailed data set fields for hierarchical grouping records. You can use the EvalExpression() function for getting hierarchical record values within aggregate functions.

This change is not implemented in 8.3.5 compatibility mode.

The data composition template composer used hierarchical data set fields for hierarchical records (provided that the fields were available in the set).You can use all detailed record fields in aggregate functions calculated for hierarchical records.
1C:Enterprise script.
The FindMarkedForDeletion() method only processes data available to the current user.

In the Syntax Assistant, the descriptions of the FindByRef() and DeleteObjects() methods are modified to describe their actual behavior.

This change is not implemented in 8.3.5 compatibility mode.

The FindMarkedForDeletion() method did not check data access rights. If access was denied, a run-time error was generated.

In the Syntax Assistant, the descriptions of the FindByRef() and DeleteObjects() methods did not describe their actual behavior.

The generation of run-time errors during the search for objects marked for deletion is eliminated in scenarios where the user does not have access rights for all objects involved in the search.

The description of the system behavior is now correct.

Managed forms.
In the thin client, in the OnOpen managed form event handler, if the Cancel parameter is set to TRUE, the OnClose event handler and the notification set in the OnCloseNotifyDescription managed form property are not called.

This change is not implemented in 8.3.5 compatibility mode.

In the OnOpen managed form event handler, if the Cancel parameter was set to TRUE, the OnClose event handler and the notification specified in the OnCloseNotifyDescription managed form property had the following behavior:
  • they were called in the thin client;
  • they were not called in the web client.
Uniform system behavior across multiple client applications.
Automated testing.
New automated testing features:
  • Operations with performance indicators. For the TestedApplication object, the GetAccumulatedPerformanceIndicators() and ClearAccumulatedPerformanceIndicators() methods are implemented.
  • Support of the following managed form items: progress bar fields and track bar fields. The Tumbler radio button field type is now supported.
  • Extended managed form table operations:
    • Deletion mark management. For the TestedFormTable object, the SwitchRowDeleteMark() method is implemented.
    • Setting row selection and getting selected rows. For the TestedFormTable object, the SelectAllRows() and GetSelectedRows() methods are implemented. For the GotoRow(), GotoFirstRow(), GotoLastRow(), GotoPreviousRow(), and GotoNextRow() methods, the Select parameter is implemented.
    • Ordering table data. For the TestedFormTable object, the SetOrder() method is implemented.
  • Expanding and collapsing managed form groups. For the TestedFormGroup object, the Collapse(), Expand(), and GetCurrentPage() methods are implemented.

The GetCurrentAreaText() method of the TestedFormField is declared obsolete. It is recommended that you use the GetAreaText() method of the TestedFormField object.

In the event of unexpected shutdown of a client application the user actions are automatically recorded to the user action log (provided that the user action log recording is enabled). A dump is also recorded to the dump directory.

The data processor that converts the log of user actions to a 1C:Enterprise script scenario is updated

URL2. +

Operations with performance indicators were not supported, as well as managed form table and managed form group operations.

Progress bar fields, track bar fields, and the Tumbler radio button field type were not supported.

In the event of an unexpected shutdown of a client application, the user actions were not recorded to the user action log and the accumulated action log was lost.

New automated testing features. Reduced number of manual operations during the testing.
Data display.
In sessions that do not have user interface (background and scheduled jobs, web services, and so on), the BriefErrorDescription() and DetailErrorDescription() method generate results that exactly match the results provided by these methods in managed application client sessions.

This change is not implemented in 8.3.5 compatibility mode.

In sessions that did not have user interface (background and scheduled jobs, web services, and so on), the BriefErrorDescription() and DetailErrorDescription() methods generated results that exactly matched the results provided by these methods in ordinary application client sessions.Eliminated unexpected system behavior.
Common objects.
When a configuration is saved, a check for style elements whose names match the values of the corresponding system value sets is performed:
  • For style elements of Color type: the StyleColors system value set
  • For style elements of Font type: the StyleFonts system value set
  • For style elements of Border type: the StyleBorders system value set

If such elements are found, an error is displayed and the configuration is not saved.

When a configuration was saved, a check for style elements whose names matched the values of the corresponding system value sets was not performed.Eliminated unexpected system behavior.

Eliminated situations where two values with the same name were present in a single system value set whose values were connected to style elements.

Internet-enabled functionality.
In the parsing of Internet mail messages, the message validity check is implemented. The check is available both for messages received from the server and during the generation of outgoing messages using the SetSourceData() method of the InternetMailMessage object. For the InternetMailMessage object, the ParseStatus property is implemented.

In the technological log, the <MAILPARSEERR> event is implemented.

This change is not implemented in 8.3.5 compatibility mode.

Detection of invalid mail messages resulted in an unexpected shutdown.Improved system reliability during email operations in scenarios where email messages being processed contain errors.
Internet-enabled functionality.
For the SetBodyFromString() method of the HTTPRequest and HTTPServiceResponse objects, the UseBOM parameter is implemented. It manages the availability of BOM in the specified text.

In version 8.3.5 compatibility mode, the BOM mark is added by default.

This feature was not provided.Simplified interaction with systems that do not expect BOM in HTTP queries.
Ordinary forms.
The Name property of ordinary form items is read-only.

This change is not implemented in 8.3.5 compatibility mode.

The DBMS request based on the VALUETYPE function was more complicated.Eliminated issues that occurred when a DBMS could not process a complex request.
OData operations.
The list of functions supported by OData standard interface is revised. The description of mod function is removed from the documentation.The documentation stated that the mod function was supported by standard Odata interface. +

The documentation describes the actual platform behavior.

File operations.
Client application.
Both in thin and thick clients, when a file is obtained interactively using the GetFile() method with the "open file" option, the search for associated application is performed (by the file extension). If an associated application is found, a system dialog box for selecting an application to open the file is displayed. If an associated application is not found, getting the file is canceled.

In the web client, the behavior is not changed, so it is now uniform with the behavior of thin and thick client applications.

In both thin and thick clients, when a file was obtained interactively using the GetFile() method with the "open file" option, the search for associated application was performed (by the file extension). If an associated application was found, the file was opened using this application. If an associated application was not found, getting the file was canceled.

The web client displayed a system dialog box for selecting an application to open the file.

Eliminated the difference in the web client, thin client, and thick client behavior.
File operations.
Web client.
The File object constructor with a file name parameter is available regardless of the Synchronous call usage mode for extensions and add-ins configuration property value. Configuration verification and refactoring no longer treat the File constructor with a file name parameter as a legacy synchronous call. Execution of this constructor no longer causes an exception in 1C:Enterprise mode.

In the web client execution of File constructor with a file name parameter no longer requires installing the file system extension.

The descriptions of File constructor without parameters and File.BeginInitialization() methods are removed from the documentation. The File.BeginInitialization() method is supported for compatibility purposes.

The File object constructor with a file name parameter was available when the Synchronous call usage mode for extensions and add-ins configuration property was set to Use or Use with warnings. Configuration verification and refactoring treated the File constructor with a file name parameter as a legacy synchronous call. If the Synchronous call usage mode for extensions and add-ins configuration property was set to Do not use, execution of this constructor caused an exception in 1C:Enterprise mode.

In the web client execution of File constructor with a file name parameter required installing the file system extension.

Operations with the File object that do not require access to the file system (such as getting a file extension) no longer require installing the file system extension.
Internet-enabled functionality.
IDs of email messages received using IMAP do not depend on whether you specify the mailbox by name or use the default one.

Once you disable the compatibility mode, the option to map messages to each other using the InternetMailMessage.MessageID property becomes available.

This change is not implemented in 8.3.5 compatibility mode.

+

IDs of email messages received using IMAP did not depend on whether you specified the mailbox by name or used the default one.You can unambiguously identify each email message, regardless of the selected mailbox. This simplifies the algorithm for distinguishing between received and new messages.

+

Web client.
System requirements.
The list of supported web browsers includes Google Chrome for x86-64 architecture. The platform uses 32-bit versions of add-ins and extensions with this browser.The list of supported web browsers did not include Google Chrome for x86-64 architecture. Extended list of supported web browsers.
Data composition system.
When columns of a data composition system report template are output to a value tree or a value table, invalid characters are removed from column names.

This change is not implemented in 8.3.5 repository compatibility mode.

+

When columns of a data composition system report template were output to a value tree or a value table, the column names matched the field names.Eliminated unexpected system behavior.
Add-ins.
In the add-in development technology, Mozilla Firefox and Google Chrome support (for all Windows, Linux, and MacOS X architectures) is now uniform. The xulrunner utility is no longer required for building add-ins and is removed from the distribution kit.

It is recommended that you build new installer packages (.msi and .sh) for Mozilla Firefox and create a new archive with version 40.* specified in the manifest. For support of earlier platform versions, also add legacy (.xpi) packages to the archive with version 31.0 specified in the manifest.

The add-in development technology documentation and examples are updated accordingly.

Add-ins created for Mozilla Firefox and Google Chrome were different. The xulrunner utility was used to build Mozilla Firefox add-ins.Support of add-ins for browsers that no longer support legacy add-in creation functions is implemented.
Predefined data.
The configuration check that is always performed before database configuration update includes a check for uniqueness of predefined item names. No duplicate predefined item names are allowed for any configuration object. If duplicate predefined items are found, this is reported to the message window but does not prevent the configuration update.The configuration check that is always performed before database configuration update did not include a check for uniqueness of predefined item names.Improved reliability of configuration updates for configurations that include predefined data.

Table of contents

Renamed objects

ObjectThe old nameThe new name
The name of the URLProcessing event handler parameter is changed for form decoration, form field extension for a label, and managed form objects.
  • URL
  • FormattedStringURL
Parameter of the AutoCompleteText and TextEditEnd event handlers of the form text box extension.
  • Parameters.
  • DataGetParameters.
The method that obtains the most accurate location provider is renamed. The former name is supported for compatibility purposes.
  • GetMostAcurateProvider().
  • GetMostAccurateProvider().

+

+
English name of CryptoCertificate.BeginUnloading() method.

The former name is supported for compatibility purposes.

  • BeginUnload().
  • BeginUnloading().
English name of BeginCheckingExistence() method.

+

The former name is supported for compatibility purposes

  • BeginCheckingExist().
  • BeginCheckingExistence().

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Client application.
Faster startup of mobile applications.Insufficient startup speed of mobile applications.Improved usability of mobile applications.
Development tools.
Data display.
The set of data stored in picture archives that include variants is modified. The manifest file manifest.xml, which is included in the archive, stores descriptions of picture variants. Custom names for pictures designed for specific display resolutions are allowed. Template pictures (pictures that have transparent background, which is displayed using the current text color) are supported. It is recommended that you store template pictures in PNG format.Picture variants were described by their file names. A manifest file was not included.

Template pictures were not supported.

You can use more of mobile application system appearance design features.
Full-text search.
In the mobile platform, you can use full-text search. The full-text search index is updated automatically upon data modification.

The search is not morphological. Additional dictionaries and text extraction are not supported. The index is updated when the mobile platform is not performing any server calls or background jobs.

The mobile platform did not support full-text search.You can use full-text search in the mobile platform.
System requirements.
The Google Play store now considers mobile applications optimized not only for phones but also for tablet PCs.

The change takes effect when you rebuild the mobile application using the new mobile platform and then republish the application to Google Play.

The Google Play store considered mobile applications optimized for phones only.Tablet PC users can see mobile applications in the default Google Play list. Searching by title is not necessary.
Calendars.
During the creation of data composition fields, if they include calendar or contact data, you can specify just a field name, without specifying its data type.

Creation of data composition fields with data types specified is supported forn compatibility purposes.

During the creation of data composition fields, if they included calendar or contact data, specifying the full field name with its data type was required.The system behaves as described in the documentation.

Simplified interaction with calendars and contacts in some scenarios.

Window management.
The option to handle the change of mobile device display parameters is now available.

The OnChangeDisplaySettings event handler is implemented. The event occurs when the client application display parameters are changed.

The Width and Height properties of the ClientDisplayInformation object store the actual values (which depend on the screen orientation).

This feature was not provided.

The platform could not detect the changes of display parameters.

The Width and Height properties of the ClientDisplayInformation object stored constant (canonical) values.

You can handle the display size changes caused by mobile device orientation changes or by connecting the mobile device to external displays. You can create applications with better usability.
Multimedia support.
Photo shoot and video recording quality control implemented (for Android only).

Camera control for photo shoots and video recording is implemented.

In the MultimediaTools object, for the PhotoSupported() and VideoRecordingSupported() methods, the CameraType parameter is implemented.

In the MultimediaTools object, for the MakePhoto() method, the CameraType, Resolutions, Quality, and Monochrome parameters are implemented. For the MakeVideoRecording() method of the MultimediaTools object, the CameraType and Quality parameters are implemented. For the MultimediaTools object, the GetSupportedCameraResolutions() method is implemented.

These features were not provided.Extended capabilities for mobile device cameras.
Printing.
On the mobile platform, you can print spreadsheet documents. Printers that use PCL3 and ZPL protocols are supported. WiFi and Bluetooth are used for connecting to printers (only for Android).This feature was not provided.You can print spreadsheet documents from mobile applications.
Configuration properties.
 +

The documentation now contains the description of the mobile platform compatibility mode:

  • It cannot be managed from Designer.
  • It is not changed when an infobase is migrated to a new platform version.
  • It is set during the infobase creation as its mobile platform version.
  • It is changed to the new mobile platform version when an infobase is migrated to a new mobile platform version.

The documentation also describes the correspondence of PC platform versions and mobile platform versions.

 +

The mobile platform compatibility mode was not described in the documentation.

The documentation is updated with the latest information.
Managed forms.
Development tools.
Asynchronous dialog box operations are available to mobile platform developers.

Selecting Mobile device in the Use purposes configuration property does not change the Modality usage mode configuration property.

Only synchronous dialog box operations were available to mobile platform developers.

When the Mobile device value was selected in the Use purposes configuration property, a request to confirm the change of the Modality usage mode configuration property value was displayed (only if the change was required).

Applied solution development for the mobile platform is simplified. Developers no longer need to support two sets of dialog box operations, one for the mobile platform and the other one for the PC platform.
1C:Enterprise script.
In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties is defined by the value of the Script variant configuration property.In the mobile platform, the language of generated names of form items, form attributes, form commands, form parameters, and structure properties was English only if the default configuration language was English. Otherwise it was Russian.The mobile platform behavior is uniform with the PC-based platform behavior.
Development tools.
Push notification and local notification support is implemented. This feature relies on Apple push notification service and Google Cloud Messaging. The option to display the number of notifications that are not yet processed is implemented: mobile application icon badges (for iOS) or status bar notifications (for Android). Devices running Android 4.1 or later display the notifications diferently from devices with earlier Android version. A dedicated service provided by 1C Company is implemented to simplify the development of notifications for applied solutions that run on the PC platform. Notification senders can choose between using this service, Apple push notification service, and Google Cloud Messaging.

For the mobile platform, the DeliverableNotifications global context property, the DeliverableNotificationManager object, and the DeliverableNotification object are implemented.

For the PC platform, the DeliverableNotificationSend global context property, the

DeliverableNotificationSendManager object, and the DeliverableNotification object are implemented.

For mobile applications, the Push notifications and Local notifications permissions are implemented.

The mobile application builder supports building mobile applications that use notifications.

This feature was not provided.You can use standard user notifications in mobile applications. Notifications can be generated either by a mobile application on the mobile device (local notifications) or by an applied solution running on a PC (push notifications).
Dynamic lists.
Improved performance of dynamic list opening. The process of loading list data now has a visual presentation.The process of loading dynamic list data had no visual presentation and took more time.Optimized dynamic list operations.
Internet-enabled functionality.
The following mobile platform features support secure connection (HTTPS):
  • HTTP operations
  • POP3 and SMTP email operations

Support of IMAP email operations (including secure connection) is implemented.

Support of client certificates and certification authority center certificates stored in files is implemented.

In the mobile platform the FileClientCertificate, FileCertificationAuthorityCertificates, and OpenSSLSecureConnection objects are implemented, together with the corresponding properties of the HTTPConnection, InternetMailProfile, and InternetMail objects.

The mobile platform did not support the following features:
  • Secure connection for HTTP, POP3, and SMTP operations
  • IMAP email operations

Client certificate operations and authority center certificate operations.

 +

The mobile platform supports secure operations with email and with other resources.

Error handling.
In the mobile platform for developers, you can obtain error details (the Details button in the error dialog box) and information for technical support (in the About 1C:Enterprise window).Error details and information for technical support were not available in the mobile platform.Improved issue diagnostics in the mobile platform for developers.
Interface.
New interface for the mobile platform client application, with a large number of improvements. The most significant changes are:
  • The interface style is derived from the Taxi interface, but optimized for mobile devices to maximum extent.
  • The interface appearance is revamped. This change affects the form design, primary colors, and the look of form items. The interface now matches the modern mobile interface standards.
  • The main application menu is revised.
  • The main section command interface is revised.
  • Navigation options are revised.
  • A form and main section command interface can be both present on the start page.
  • Form command bar placement and generation rules are modified.
  • The option to display a form navigation panel is implemented.
  • The text input field is optimized for touch screen devices.
  • The form title is no longer duplicated in the form body.
  • Users have the option to create a list item when selecting a value from a drop-down list.
  • Form item context menus are supported.
  • Fields that require filling are not highlighted.
  • New display options for page groups are implemented.
  • Search in dynamic lists is implemented. It is based on full-text search.
  • A dynamic list can be sorted by tapping a column header.
  • Table operations are significantly revised, including scrolling, table item selection, and row rearrangement.
  • In managed form tables the multiple selection option is implemented.
  • The option to update a list by pulling the list down or up when the first or last row is on the screen ("pull to refresh") is implemented.
  • The approach to handling the current row of a managed form table is changed.
  • A managed form table is automatically scaled to fit displayed data by height, unless it displays dynamic list data.
  • Spreadsheet documents can be scaled using gestures.
  • User message appearance is revised.
  • Subsystems are supported (and available in the interface).
  • The radio button field and the track bar field are implemented.
  • For a managed form table the RefreshRequestProcessing event is implemented. For the FormPagesRepresentation system enumeration the Swipe value is implemented. For a managed form table the RefreshRequest property is implemented.
  • The Move up/Move down standard table commands are removed.
  • For a managed form command the Use current row and Associated table properties are implemented (not available from 1C:Enterprise script). For a managed form button the Representation in context menu property is implemented (not available from 1C:Enterprise script).
  • Many other features are implemented. The full list of changes is quite long, therefore it is recommended that you read the chapter about mobile application development in 1C:Enterprise Developer Guide.
The mobile application interface was similar to managed application interface version 8.2. The mobile application interface meets the modern requirements to mobile interfaces. Improved mobile application usability. New interface uses the same color scheme and style as the Taxi interface, at the same time it is optimized for mobile devices.
Managed forms.
For devices that run Android operation system, predictive text input in multiline text boxes is implemented (with optional automatic correction of the entered text). This feature is available when it is enabled in the virtual keyboard settings.This feature was not provided.Improved usability for text input.
Mobile application builder.
In mobile application builder, you can publish an application to Apple App Store and Google Play directly from the builder.

The mobile application builder help describes how to connect to Google Play Market.

This feature was not provided.

Mobile applications required manual publishing.

Publishing mobile applications to Apple App Store and Google Play is simplified.
Dynamic lists.
The option to specify dynamic list settings using 1C:Enterprise script is implemented.

The DynamicList.SettingsComposer property is now available on the mobile platform.

The following objects are implemented: DataCompositionSettingsComposer, DataCompositionUserSettings, and DataCompositionSettings, as well as their constructors and methods. Their methods are not available on the mobile platform.

The DataCompositionUserSettingsItemCollection object is implemented.

This feature was not provided.Работа с настройками динамического списка на мобильной платформе приближена к возможностям платформы для персонального компьютера.
Dynamic lists.
Interface.
When the selection mode is on, dynamic list rows that represent parent groups have left arrows displayed.When the selection mode was on, dynamic list rows that represented parent groups did not have left arrows displayed.Improved navigation of hierarhical dynamic lists in the selection mode.

Table of contents

Library updates

Table of contents

Transition from the previous version to the version 8.3.6

Table of contents

Version 8.3.5

Version 8.3.5 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.4 is added to the list of available values of the Compatibility mode property. +Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, and 8.3.3. +In version 8.3.5 you can run configurations created in version 8.3.4 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.5 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.4 for working with the infobase even after the transition to version 8.3.5. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on). +
Development tools.
In Designer, new icons for external data source tables and cubes are implemented.Pictures for external data source tables and cubes were different.Icons for external data source tables and cubes are uniform with other platform pictures.
Development tools.
In Designer, you can filter objects by parts of names, synonyms, comments, or presentations. The filter is available in the following windows:
  • Configuration window
  • Configuration object selection dialog box
  • Type editing dialog box
  • Object properties window

For the Subsystem configuration object, a quick filter is implemented in the configuration window. The filter is available from the Subsystem objects context menu command of the object.

In the configuration window, you can set a quick filter for configuration repository objects locked by the current user.

This feature was not provided.

Only filtering by objects included in subsystems was available.

Improved usability for developers.
Interface.
1C:Enterprise script provides tools for managing start page (desktop) form contents and positions.

The StartPageForms object is implemented. For the StartPageSettings object, the GetForms() and SetForms() methods and the default constructor are implemented.

The global context method RefreshInterface() rebuilds the start page (desktop) based on the settings from the system settings storage.

The StartPageSettings object stored the differences between the start page (desktop) settings of the client application and the settings specified in Designer.

1C:Enterprise script did not provide tools for managing form contents and positions.

You can manage contents and positions of the client application start page (desktop) forms using 1C:Enterprise script.
Administration tools.
For the Purpose column of value table returned by the GetDBStorageStructureInfo() method, new purposes are specified. The full list of database table purposes is available in the description of the GetDBStorageStructureInfo() method in the Syntax Assistant.The list of table purposes did not fully describe the current database schema.The purposes of database scheme tables are described more clearly.
Data exchange.
For exchange plans, the ThisNode standard attribute is implemented. It specifies whether the exchange plane node describes the current infobase.

For the ExchangePlanObject object, the DataExchange property is implemented. Only the Load property can be used in this property. The DataExchange property is used for disabling the uniqueness check of the ThisNode item when exchange plan items are edited or deleted.

This change is not implemented in 8.3.4 compatibility mode.

The ThisNode standard attribute was not available in exchange plans. Replacing the exchange plan node that described the current infobase was impossible.

The ExchangePlanObject object did not have the DataExchange property.

You can define ThisNode items in a distributed infobase in a session that does not use separators.

You can replace the data item that describes the current infobase in the exchange plan.

Managed forms.
For managed form text boxes, the EditTextChange event is implemented. This event occurs when one of the following actions modifies the text box content:
  • Typing in the text box
  • Copying text from the clipboard
  • Running Undo or Redo command
  • Canceling input by pressing ESC

The event occurs before the AutoComplete event.

There was no event that occurred when text box content was modified. Actions triggered by this modification could be performed in the AutoComplete event handler (with limitations).In managed forms, complete implementation of the following scenario is available: text being typed in a text box is used as a filter parameter in the linked dynamic list.
Development tools.
New features in the module editor:
  • Find all usage instances of an export variable, procedure, or function in the entire configuration.
  • Convert a selected code fragment to a separate procedure or function.
  • Rename a local variable, procedure, or function.
  • Insert a comment block that describes the function or procedure purpose, parameters, and return value before the function or procedure declaration.
  • Convert modal calls to nonmodal calls (in a limited set of cases).
  • Convert procedures or functions to types that can be used in sequences of asynchronous calls.
  • Convert a selected code fragment to a separate procedure or function suitable for using in sequences of asynchronous calls.
  • Find all usage instances of modal methods in the specified module.
  • Convert all modal methods that are found to their asynchronous analogs.
  • Create notification processing events for methods that lock the interface.

Commands that perform these functions are located in the Refactor submenu of the module text editor context menu and in the Configuration section of the Designer main menu.

These features were not provided.Improved efficiency of routine operations performed by developers.
Managed forms.
In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers are implemented.

This change is not implemented in 8.3.4 compatibility mode.

In text boxes that display values of StandardBeginningDate type, in the date input mode, the AutoComplete (on value input) and TextEditEnd (on generating a value based on the input string) event handlers were not implemented.The behavior of text boxes linked to values of StandardBeginningDate type in the date input mode is identical to behavior of text boxes linked to values of Date type.
Client application.
The option to follow a navigation link during client application startup is implemented, with the navigation link passed as a parameter. This feature is implemented for the 1C:Enterprise launcher, thin and thick clients, the GotoURL() method, the standard full-text search form, and the new Go to link command in the startup window. Only external navigation links (which contain infobase connection settings) are supported. When following a link, the platform attempts to use running client application instances connected to the infobase specified in the navigation link. In 8.3.4 version compatibility mode, the GotoURL() method is not modified.

The /url startup option is implemented for the launcher, thin client, and thick client.

This feature was not provided.

Users could only follow external links when they accessed the infobase using the web client.

Simplified access to infobase data if a link to this data is provided by third-party tools, such as email.
Internet-enabled functionality.
For the InternetMailMessage object, the GetSourceData(), SetSourceData(), and GetSourceText() methods are implemented. These methods are intended for getting original email messages without changing the encoding and processing source texts of messages whose encoding was changed.This feature was not provided.You can save email messages to files and load them from files, provided that they comply with RFC 822 URL9, and you can also perform custom processing of email message source texts.
Data display.
Charts.
Animated charts are implemented. The Animation property is implemented for the Chart object. The ChartsViewSettings object is implemented. The chart display settings are stored in the system settings storage.

This change is not implemented in 8.3.4 compatibility mode.

This feature was not provided.More chart display options are available.
Web services and HTTP services.
Data exchange.
Database operations.
Web client and web service publishing tools.
1C:Enterprise infobase data can be retrieved and modified using the OData protocol (read more) v3 (read more). The following data presentation is supported: atom-xml.

Enabling this feature does not require modification of applied solution, it is performed using a web server publication.

The enableStandardOData attribute is implemented for <point> tag in the default.vrd file.

In 8.3.4 version compatibility mode, all configuration objects that support OData protocol are available through this interface. If the compatibility mode is disabled, the access to objects is managed using the SetStandardODataInterfaceContent() method.

Universal access to 1C:Enterprise infobase data was only available on Windows operating systems and was based on COM/OLE features. It was not available on Linux. The option to access data using web services implemented in applied solutions was also available.Extended integration features for 1C:Enterprise data, including data access from external Linux systems, which does not require modification of applied solutions .
Configuration repositories.
Optimized selective comparison of forms, access rights, and command interface fragments in scenarios where the configuration repository is located on a network drive or on a repository server.

Local data cache is implemented for configuration repositories. You can manage the size and location of local and global repository caches using the configuration repository administration settings dialog box or cfgrepo.conf configuration files. These files are located in the cfgrepo subdirectory of the infobase service files directory (for the local cache) or in the configuration repository directory (for the global cache).

The following features are implemented for batch Designer startup mode:

  • Clearing the global configuration repository cache (the /ConfigurationRepositoryClearGlobalCache command-line option)
  • Clearing the local configuration repository cache (the /ConfigurationRepositoryClearLocalCache command-line option)
The selective comparison of forms, access rights, and command interface fragments lacked efficiency if the configuration repository was located on a network drive or on a repository server.

Editing the size and location of the global configuration repository cache was not available. The local cache for configuration repository data was not available.

Selective comparison and some other configuration repository features are optimized.

You can manage the size and location of configuration repository data cache.

Dynamic lists.
Extended search capabilities in tables that display dynamic lists. A standalone search string box that provides full-text search is implemented. Search by current cell value is available. The search history is implemented. The current search state is clearly visible. The search result includes items that have search words located both in a single column and in different columns. In each column, search by a single value is available (the Find in search results option is not supported).

For automatically created forms that contain tables linked to dynamic lists, the set of items related to search in dynamic lists is modified (together with their appearance). The search dialog box layout is modified.

The new FormItemAddition managed form item stores additional properties of form items.

Extensions of form items intended for displaying a search string, a view status, and a search control are implemented.

For the FormTable managed form item, the predefined items SearchString, ViewStatus, and SearchControl, and also properties SearchStringLocation, ViewStatusLocation, and SearchControlLocation are implemented.

The search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>.

The SearchControl picture is added to the picture library.

Search in tables was performed using the search dialog box. The option to search a column by multiple values (the Find in search results check box) was available. The search dialog box had a different layout. There was no simple way to determine whether the search is applied to a table (except for checking the availability of the Cancel search button if it was present on the command bar).The search in managed form tables is improved, it is clearly visible whether the search is applied to a table.
Web services and HTTP services.
Developers can create HTTP services in applied solutions. Developers can access HTTP request body, headers, and line.

Publishing HTTP services is similar to publishing web services.

To access HTTP services, use URLs of the following format: http://<host name>/<base name>/hs/<resourсe identifier>. You can create HTTP services in the Common/HTTP services branch of the configuration tree.

The following objects are implemented: HTTPServices, HTTPService, HTTPServiceRequest, and HTTPServiceResponse.

This feature was not provided.

Only access to web services implemented in the applied solution was available.

You can create services that have the following advantages over web services:
  • Simpler implementation.
  • Less amounts of data transferred.
  • Less computing power is required to parse a response.

A different usage model (RESTful services).

Client application.
Database operations.
The Hibernated session state is implemented, which is intended for preserving sessions after unexpected connection losses. Sessions that require licenses release the occupied licenses once they are hibernated. If a connection is assigned to a hibernated session, the session loses its Hibernated state. During the recovery from hibernation, sessions that require licenses attempt to obtain licenses. If a license cannot be obtained, the session is terminated. The option to set a timeout for automatic shutdown of hibernated sessions is implemented. If a connection to the client is closed by the 1C:Enterprise server, the session is hibernated(instead of being terminated).

For the ISessionInfo object, the following properties are implemented: Hibernate, PassiveSessionHibernateTime, and HibernateSessionTerminateTime. New global context methods are implemented: SetPassiveSessionHibernateTime(), GetPassiveSessionHibernateTime(), SetHibernateSessionTerminateTime(), and GetHibernateSessionTerminateTime().

The hibernation timeout and the timeout for closing hibernated sessions can be set in Designer, in the infobase parameters dialog box.

This feature was not provided.

If a client application was inactive for 20 minutes, the session was closed.

In the client/server mode, in some scenarios the client application continues functioning even when the client computer stays in hibernation mode for a long time.
Data composition system.
In the data composition system, new options are implemented for comparison of string data: BeginsWith, NotBeginsWith, Like, and NotLike.This feature was not provided.Extended features for filtering by string expressions in reports created using the data composition system and in dynamic lists.
Applied objects.
For catalog, chart of characteristic types, chart of accounts, chart of calculation types configuration objects, the GetPredefinedNames() method is implemented.This feature was not provided.You can get the flag indicating that a configuration object has predefined items, as well as the full list of predefined item names. Using this list, you can check whether data items are set for all predefined items.
External data sources.
You can write data to external data source tables.

This feature is intended for integration with other applications, external sources should not be used as applied solution data storages.

This feature was not provided.

External data source table data was read-only.

New options for integration with information systems and databases.
Queries.
A query wizard for managed mode is implemented. For the QueryWizard object, the Show() method is implemented.

The following pictures are added to the picture library:

Rename, Attribute, Dimension, Resource, NestedTable, QueryWizardShowChangesTables, QueryWizardCreateNestedQuery, QueryWizardCreateTempTableDescription, QueryWizardReplaceTable, QueryWizardTableParameters, QueryWizardCreateTempTableDropQuery

QueryWizardTempTableDescription, QueryWizardGroupTempTables, QueryWizardTempTable, QueryWizardNestedQuery, and CustomExpression.

This feature was not provided.New features for using queries in managed applications.
Queries.
An object model intended for modification of query texts is implemented. The QuerySchema object is implemented.This feature was not provided. +

You can modify queries from 1C:Enterprise script without analyzing the query text.

Spreadsheet documents.
You can insert pictures in spreadsheet document cells. You can specify text position relative to the picture in a cell (or an area of cells) of a spreadsheet document. A picture is linked to a cell where it is inserted.

For the SpreadsheetDocumentRange object, the following properties are implemented: Picture, PictureSize, PictureHorizontalAlign, PictureVerticalAlign, TextPositionRelativeToPicture, and PictureParameter.

Pictures could only be inserted in spreadsheet documents as images that were not linked to any specific cell (or an area of cells).Improved usability of pictures in spreadsheet documents.
System requirements.
Alt Linux SPT 6.0 distribution kit is supported.This distribution kit was not supported.New Linux distribution kit is supported.
Data composition system.
For the DataCompositionFilter object, the default constructor is implemented.This feature was not provided.In a mobile application, you can set a filter for a list of contacts.
Event log.
The _$Data$_.TotalsMaxPeriodUpdate event with presentation Data.Modify maximum calculated totals period is implemented. The event is registered when the SetMaxTotalsPeriod() or SetMinAndMaxTotalsPeriods() method is called.

The _$Data$_.TotalsPeriodUpdate event is used for compatibility purposes.

The _$Data$_.TotalsPeriodUpdate event was registered when the maximum totals period was set.The event log displays actions that set the totals period more consistently.
Linux.
Client application.
1C:Enterprise searches for the ImageMagick library by name libMagickWand-6.Q16.1C:Enterprise did not search the ImageMagick library by name libMagickWand-6.Q16.During the startup, 1C:Enterprise is not shut down if the ImageMagick library was renamed and then reinstalled.
DBMS operations.
Microsoft SQL Server 2014 DBMS is now supported.Microsoft SQL Server 2014 DBMS was not supported.New Microsoft SQL Server version is now supported.
Developer tools.
For the Technological log configuration file editor (read more) and User action log conversion (read more), data processors, which are distributed via 1c-dn.com, the English interface is implemented. Both data processors are rewritten using the English variant of 1C:Enterprise script.The Technological log configuration file editor and User action log convertor data processors had Russian interface only.

Both data processors were written using the Russian variant of 1C:Enterprise script.

Simplified usage and modification of the Technological log configuration file editor and User action log convertor data processors for non-Russian-speaking developers.
Development tools.
In the "dump configuration to files" feature, the approach to dumping standard attribute data is modified. Only attributes whose properties differ from the default values (for the given attribute) are dumped. Changing properties of a single standard attribute results in dumping all of the standard attributes of the configuration object. The same behavior is implemented for loading: if an XML file contains a description of a standard attribute, it is loaded to the configuration even if the description of the standard attribute contains only default values.

An external data processor intended for deleting descriptions of standard attributes with default values from XML dump files is implemented.

The data processor can be used only with files dumped by 1C:Enterprise version 8.3.5. You have to use it once before loading the dumped files back to the configuration.

+

While dumping configuration files, standard attribute data was always dumped, even if all of the standard attribute properties had default values.Reduced configuration file size. Reduced number of "different" objects found when comparing configurations after dumping and subsequent loading.
Predefined data.
Applied objects.
Common attributes / Data separation.
You can edit the flag that shows whether predefined data is initialized in a data area or in the entire infobase. The GetPredefinedDataInitialization() and SetPredefinedDataInitialization() methods are added for catalog managers, charts of characteristic types, charts of accounts, and charts of calculation types.

This change is not implemented in 8.3.4 compatibility mode.

Editing the flag that shows whether predefined data is initialized in a data area or in the entire infobase was not available.Extended capabilities for processing predefined data. You can inform the system at any time that predefined data in a data area or in the entire infobase is initialized (or not initialized). In a distributed infobase, when you remove infobase subordination to the master node, you can specify that all of the predefined data items are created in the infobase whose subordination is being removed.
System requirements.
Microsoft Windows Server 2012 R2 (x86-64) is now supported.Microsoft Windows Server 2012 R2 (x86-64) was not supported.New version of the Microsoft operating system is now supported.
Server clusters.
Administration tools.
You can use an external utility for generating dumps when the platform stops responding.

In the logcfg.xml file, the externaldump attribute of the dump element is implemented.

The dumper.exe utility, which is now included in the platform delivery kit, is implemented.

Dumps were generated by the process that stopped responding.Eliminated the issue where the system stopped responding while generating a dump for a process that stopped responding.
Data exchange.
The instructions for unbinding an infobase from the root node and restoring a configuration in a distributed infobase node, which take into account the specifics of predefined data usage, are available in the platform documentation.This information was not available in the documentation.The documentation contains recommendations for using distributed infobases that include predefined data.
Client application.
Managed forms.
In thin and thick client applications, the system behavior based on the Modality usage mode configuration property value is modified. For thin and thick client applications, the EnableCheckModal startup parameter is implemented.

If EnableCheckModal is not used, modal methods are executed without any warnings or exceptions.

If EnableCheckModal is used, executing a modal method generates a warning or an exception (depending on the Modality usage mode configuration property value).

When an applied solution is started from Designer, the EnableCheckModal parameter is automatically added to the applied solution command line (this behavior cannot be disabled).

The web client behavior is not modified: the command-line parameter is not used. The web client always generates a warning or an exception (depending on the Modality usage mode configuration property value) when modal methods are executed.

The modal method behavior was based on the Modality usage mode configuration property value only. Depending on this property value, modal methods were executed with warnings or exceptions. This behavior could not be changed using command-line parameters.You can use external data processors that include modal methods in applied solutions where modality is disabled.
System requirements.
Support of Microsoft Windows 8.x operating system is implemented.Microsoft Windows 8.x operating system was not supported.Extended list of supported operating systems.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Client application installation.
While the client application is being updated via the Internet, a dialog box displaying the progress of downloading the distribution kit from the server is being displayed. You have the option to cancel the download.

While the client application was being updated, the progress of downloading the distribution kit was not displayed.

Improved process of updating the client application using Internet services: the progress is displayed and the download can be canceled.
Client application.
The Help window is opened like any other form:
  • In the Forms in separate windows mode, it is opened in a separate window.
  • In the Forms in tabs mode, it is opened in a tab.
  • In the Taxi mode, it is opened in the main window working area.
  • If help is opened from a form that locks the entire interface, it is opened on top of all windows and locks the entire interface.
  • If help is opened from a modal form, it is opened in a modal form.

The help command bar is modified.

The search is started either when the focus leaves the search text box or when the user clicks Find.

Help was always opened in a new window, regardless of the main application window interface settings.

The help command bar had different content.

The search started while the search expression was still being typed (during a pause in the typing).

The behavior of the Help window is unified with other forms.
Configuration installation.
New splash screen in the configuration installation wizard.The configuration installation wizard used a different splash screen.The configuration installation wizard and the platform installation wizard have uniform looks.
Client application.
If OpenID authentication is available in an infobase, once you run the thin client and select the infobase, the authentication dialog box will display the name of the last authenticated user.The user name box in the OpenID authentication dialog box was always empty.The user name box behavior is uniform for all authentication methods.

+

+

Predefined data.
When a catalog, chart of characteristic types, or chart of accounts folder is marked for deletion, unmarked for deletion, or deleted, the platform checks whether the user has enough rights to access subordinate predefined objects.When a catalog, chart of characteristic types, or chart of accounts folder was marked for deletion, unmarked for deletion, or deleted, the platform did not check whether the user had enough rights to access subordinate predefined objects.The platform does not allow deletion of a catalog, chart of characteristic types, or chart of accounts folder if the folder contains a predefined item and the user does not have the right to delete that item interactively.
Web client.
When the web client is started in Google Chrome web browser on MacOS X operating system, the message that the web browser is not supported is not displayed.When the web client was started in Google Chrome web browser on MacOS X operating system, the message that the web browser was not supported was displayed.Improved usability of applied solution startup in the web client that is started in Google Chrome web browser on MacOS X operating system (the message is removed). Support of this web browser is subject to further discussion.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Common attributes / Data separation.
File mode.
In separated infobases that run in the file mode, query execution is optimized. +

In separated infobases that ran in the file mode, query execution lacked efficiency.

Improved performance of separated infobases that run in the file mode.
Managed forms.
In some scenarios, forms are opened faster.Opening forms was not optimized.Improved system performance in some scenarios.
Database operations.
Improved performance of establishing a connection to an infobase that is running in the file mode and located on a network resource.The performance of establishing a connection to an infobase that was running in the file mode and located on a network resource was insufficient.For the second and following users, improved performance of establishing a connection to an infobase running in the file mode and located on a network resource.
1C:Enterprise script.
Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.The performance of the following operations was insufficient: execution of 1C:Enterprise script methods and getting configuration object properties.Improved performance of the following operations: execution of 1C:Enterprise script methods and getting configuration object properties.
Accounting registers.
Improved performance of writing to accounting registers for record sets that contains no more than 10 records.When a record set with no more than 10 records was written to an accounting register, the writing performance was insufficient.Optimized accounting register operations.
DBMS operations.
Accounting registers.
Common attributes / Data separation.
In the client/server mode with IBM DB2 or Oracle Database DBMS, improved performance of writing to accounting registers that are included in the contents of common attributes used as separators.In the client/server mode with IBM DB2 or Oracle Database DBMS, the performance of writing to accounting registers included in the contents of common attributes that were used as separators was insufficient.Optimized accounting register operations in the client/server mode with IBM DB2 or Oracle Database DBMS.

Table of contents

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 forms.
Dynamic lists.
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 storages.
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.
XML and XDTO support.
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.
XML and XDTO support.
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 forms.
 +

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.
XML and XDTO support.
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 documents.
XML and XDTO support.
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 repositories.
 +

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 forms.
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.
XML and XDTO support.
Development tools.
In the "dump configuration to files" feature, XML file format is changed for the following configuration parts: managed forms, dynamic list settings, 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.

Dynamic list settings are dumped to a single element, which has the data composition schema settings format.

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, dynamic list settings, 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.
Charts 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.
The event log format is modified. The log is now stored in an SQLite database. The log file has .lgd extension.

The log location is not changed. The SQLite log format is the default format for new infobases. The performance of accessing event log data 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 standard event log viewer supports new log file format (.lgd).

In the standard event log viewer form the command for viewing a log stored in a file is renamed to More - View from file.

The event log had text format.

In the standard event log viewer form the command for viewing a log stored in a file had the following name: More - Load from file.

Improved performance when accessing event log data. Improved event log reliability.

Better name for the command for viewing a log stored in a file.

Event log.
Deletion of a large number of event log records (more than 10 million) takes much less time.

You can terminate the reducing of event log size by pressing Ctrl+Break in Designer or by closing the session using administrative tools (as a result, a part of records is deleted, and the rest are not deleted).

The performance of event log record deletion was insufficient.

Reducing the event log size could not be terminated.

Reducing the size of a large event log takes reasonable time.

This operation can be terminated if needed.

Spreadsheet documents.
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.
Database operations.
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.

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 detailed messages about 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 documents.
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 documents.
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 forms.
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 forms.
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.
Database operations.
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.
Data display.
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.
XML and XDTO support.
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.
Managed forms.
Getting a choice form in a slow connection scenario is implemented identically to getting forms in other scenarios.Getting a choice form in a slow connection scenario was implemented differently from getting forms in other scenarios, it included caching the form.Increased relaibility for getting choice forms in a slow connection scenario.
Applied objects.
During the restructuring of hierarchical predefined data, if an item parent is not found during the update, the item is moved to the top level.

During the creation or restructuring of predefined data, if references to subordinate items are missing from predefined tabular sections, rows with missing references are deleted. Upon deletion, the platform generates a diagnostics message or an event log record, and the tabular section row numbering is updated accordingly.

This change is not implemented in 8.3.4 compatibility mode.

Invalid references to parent items or subordinate items in predefined data might cause errors during infobase retructuring.Increased system stability in the scenario where predefined data items contain invalid references to parent or subordinate items.
Command interface.
In the Taxi interface the scaling of pictures in the sections panel of the web client is now identical to that of the thin client. The picture height is calculated as follows:
  • If any of the pictures have height more than 48 pixels, they are scaled to the height of 48 pixels.
  • If all of the pictures have height less that 48 pixels, the section panel height is calculated based on the maximum picture height, while smaller pictures are centered at their respective positions.
In the Taxi interface of the web client 48x48 pixel squares were reserved for section panel pictures. The size of larger pictures was reduced proportionally and smaller pictures were centered within those squares. The section panel height was never reduced.The Taxi interface behavior in the web client is unified with that of the thin client.
Spreadsheet documents.
XML and XDTO support.
When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file is not important.When a spreadsheet document is XDTO-deserialized, the order of items in the source XML file was important.Spreadsheet documents serialized to XDTO using 1C:Enterprise version 8.3.4 and earlier can be read without errors.
Third-party software.
The OpenSSL library is updated to version 1.0.0r.OpenSSL version 1.0.0m was used.Eliminated OpenSSL security issues.
Web client.
The web client is optimized for Google Chrome 37 web browser. The managed form issues where text did not fit the desired area are eliminated.The web client had issues related to displaying text in Google Chrome 37 web browser. +

Improved Google Chrome 37 web browser support.

DBMS operations.
Improved reliability of PostgreSQL DBMS operations in certain scenarios.Insufficient reliability of PostgreSQL DBMS operations in certain scenarios.Improved reliability of PostgreSQL DBMS operations.
Regional settings.
For Russia, a single one-hour time zone shift is applied in line with Federal Law #248-FZ. This change affects all 1C:Enterprise system components, except for the web client. The web client uses time zone data provided by operating systems and web browsers.

+

The platform did not reflect the changes introduced by Federal Law #248-FZ.The time offset changes introduced by the new law are implemented.
Add-ins.
A section describing add-in limitations is added to the Add-in development technology document (read more).The Add-in development technology document did not describe add-in limitations.Improved add-in technology description.
Client application.
Development tools.
When the thick client (1cv8) is started in ordinary application mode, the performance indicator window is not displayed.When the thick client (1cv8) was started in ordinary application mode, the performance indicator window was not displayed.The display of performance indicators in ordinary applications is disabled because they are rarely used in this mode.

Table of contents

Changes that require modification of configuration and administrative settings

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

This change is not implemented in 8.3.4 compatibility mode.

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode

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

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

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

 +

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

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

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

This feature was not provided.

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

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

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

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

For the TestedClientApplicationWindow object, the StartPage property is implemented.

This change is not implemented in 8.3.4 compatibility mode.

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

 +

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

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

This change is not implemented in 8.3.4 compatibility mode.

 +

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

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

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

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

A different dialog box was used in the following scenarios:

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

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

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

This change is not implemented in 8.3.4 compatibility mode.

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

The feature is implemented for thin and web clients.

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

This change is not implemented in 8.3.4 compatibility mode.

 +

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

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

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

+

For configuration objects that were included in separator content and had tabular sections, data access restriction checks were not performed (after writing) if the access restriction conditions included attributes from the object tabular sections.Eliminated unexpected system behavior. +
Predefined data.
Charts of accounts.
Charts of calculation types.
The following rules now apply during infobase restructuring:
  • A row of a predefined tabular section of a chart of accounts or a chart of calculation types, which is added in 1C:Enterprise mode and refers to a predefined item, is marked predefined if a predefined row that refers to the same item is added in Designer mode.
  • When a predefined row is deleted from a predefined tabular section of a chart of accounts or a chart of calculation types, the actual row is not deleted. Instead, it loses the "predefined" flag.

In addition to that, the order of tabular section rows might be changed to ensure that all of the predefined items are at the top.

This change is not implemented in 8.3.4 compatibility mode.

In a chart of accounts, adding a predefined extra dimension type in Designer mode was impossible if the extra dimension type was added in 1C:Enterprise mode earlier. When an attempt to delete a predefined row from a predefined tabular section of a chart of accounts was made, the actual row was deleted.

Charts of calculation types had the following behavior:

  • In 1C:Enterprise version 8.2.12 or earlier, the behavior was the same as in 1C:Enterprise version 8.3.5.
  • In 1C:Enterprise versions 8.2.13–8.3.4, if a base, leading, or displacing calculation type that was added earlier in 1C:Enterprise mode was then added in Designer mode, a duplicate calculation type entry was generated. When a predefined row was deleted from a predefined tabular section of a chart of calculation types, the actual row was deleted.
Editing predefined tabular sections no longer might cause data losses.

Editing the list of extra dimension types of a predefined account in Designer might result in a message that the account's maximum number of extra dimension types is exceeded.

Accounting registers.
Accumulation registers.
Information registers.
Calculation registers.
In a value table obtained by the Unload() method of an accounting register, accumulation register, calculationregister, or information register record set, the value of the LineNumber column is equal to the line number in the record set.

This change is not implemented in 8.3.4 compatibility mode.

In the value table obtained by the Unload() method of an accounting register, accumulation register, calculation register, or information register record set, the value of the LineNumber column was equal to the index of the record set index.Eliminated unexpected system behavior.
Client application.
Internet-enabled functionality.
The TLS protocol is recommended for secure connections as it is more secure. The SSL protocol version 3.0 is disabled by default.

If the web server used for thin client connections can use SSL version 3.0 for connecting to a web server, you can use the thin client command-line option /HttpsAllowSSLv3.

SSL version 3.0 is not used (by default) with the HTTPConnection, FTPConnection, InternetMail, WSProxy, WSReference, and WSDefinition objects, when connecting to the configuration repository, and in Debugger. If you need to use SSL version 3.0 in these scenarios, use the AllowSSLv3 option in the conf.cfg file. For the conf.cfg configuration file, the AllowSSLv3 option is implemented.

For the InternetMail object in version 8.3.5 and earlier compatibility mode and in earlier 1C:Enterprise versions:

  • On Windows, you can enable the SSL protocol version 3.0 by editing the system register.
  • On Linux, the availability of SSL protocol version 3.0 is defined by the OpenSSL library version.
The SSL protocol version 3.0 was used for secure connections.Improved security of connections established by client applications that work over the Internet.
Web client.
Add-ins.
The file system extension and the cryptography extension are modified (for all supported Windows web browsers). The reason is that the NPAPI technology is no longer supported in Google Chrome browser.

New extension versions perform all file and cryptography operations asynchronously (using notifications).

To be able to use 1C:Enterprise extensions and browser extensions, you are required to install a dedicated web browser extension. The web client prompts you to install that extension once you attempt to enable a browser extension.

On the client side, add-ins, the file system extension, and the cryptography extension run asynchronously. Synchronous add-in, file system extension, and cryptography extension operations are supported on the client side for compatibility purposes. Refactoring applied solutions, including those that have add-ins, is required to support synchronous operations:

  • change method calls to calls of BeginCalling<MethodName>() asynchronous methods,
  • change reading property values to calls of BeginGetting<PropertyName>() asynchronous method,
  • change setting property values to calls of BeginSetting<PropertyName>() asynchronous method.

Refactoring add-ins is not required. The platform automatically adds prefixes and asynchronous behavior support to add-in methods. +The SynchronousExtensionAndAddInCallUseMode configuration property is implemented. If the property is set to Do not use, NPAPI-based extensions are not loaded in the web client and, as a result, synchronous methods cannot be executed. In other cases, an attempt to load an NPAPI-based extension is performed. If an extension is successfully loaded, both synchronous and asynchronous methods can be executed. For more information, see the documentation.

Previous extension versions can be uninstalled in a regular way.

Improved add-in development technology (read more).

The following global context methods are implemented: BeginAttachingCryptoExtension(), BeginAttachingFileSystemExtension(), BeginAttachingAddIn(), BeginCopyingFile(), BeginMovingFile(), BeginDeletingFiles(), BeginFindingFiles(), BeginCreatingDirectory(), BeginGettingTempFilesDir(), BeginGettingDocumentsDir(), BeginGettingUserDataWorkDir(), BeginGettingFiles(), BeginPuttingFiles(), BeginRequestingUserPermission(), and BeginRunningApplication().

For the CryptoManager object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginEncrypting(), BeginSigning(), BeginGettingCryptoModuleInformation(), BeginGettingCertificatesFromSignature(), BeginGettingCertificateStore(), BeginVerifyingSignature(), BeginCheckingCertificate(), and BeginDecrypting().

For the CryptoCertificate object, a constructor without parameters is implemented, and also the following methods: BeginInitialization() and BeginUnload.

For the CryptoTools object, the BeginGettingCryptoModuleInformation() method is implemented.

For the CryptoCertificateStore object, the BeginAdding(), BeginFindingByThumbprint(), BeginFindingBySerialNumber(), BeginFindingBySubject(), BeginGettingAll(), and BeginDeleting() methods are implemented.

For the FileDialog object, the Show() method is implemented.

For the File object, a constructor without parameters is implemented, and also the following methods: BeginInitialization(), BeginGettingModificationTime(), BeginGettingHidden(), BeginGettingReadOnly(), BeginGettingSize(), BeginGettingModificationUniversalTime(), BeginCheckingExist(), BeginSettingModificationTime(), BeginSettingHidden(), BeginSettingReadOnly(), BeginSettingModificationUniversalTime(), BeginCheckingIsDirectory(), and BeginCheckingIsFile().

You can use the refactoring feature to convert synchronous extension and add-in methods to their asynchronous counterparts. New refactoring settings are available.

The file system extension and the cryptography extension were implemented using the NPAPI technology. The extension methods were executed synchronously. In Google Chrome web browser synchronous execution of methods from add-in APIs was possible. +

The platform supports asynchronous add-in, cryptography extension, and file system extension operations in the web client, which ensures Google Chrome support.

Important! Support of synchronous operations in Google Chrome is disabled by default since version 42 (April 2015) and discontinued since version 45 (September 2015). Therefore, synchronous 1C:Enterprise script methods will stop working in Google Chrome even if you use a platform version that supports them.

Web client.
Add-ins.
The add-in technology (read more) no longer supports add-in development for Safari web browser for Windows.The add-in technology supported add-in development for Safari web browser for Windows.The outdated web browser is no longer supported. The Apple company stopped updating Safari web browser for Windows.
Add-ins.
The add-in development technology supports Mozilla Firefox web browser versions 31.0 and later. It is recommended that you build a new installer package for Mozilla Firefox using the new adapter. It is also recommended that you remove installer packages for Mozilla Firefox versions 30.0 and earlier from the add-in archive.

The add-in development technology does not support Mozilla Firefox web browser versions 30.0 or earlier.

Adapters for Mozilla Firefox versions 30.0 or earlier are removed.

The add-in development technology did not support Mozilla Firefox web browser versions 31.0 or later.

The add-in development technology supported Mozilla Firefox web browser versions 30.0 and earlier.

The add-in development technology supports the latest versions of Mozilla Firefox web browser (31.0 or later).

The add-in development technology does not support older versions of Mozilla Firefox web browser (30.0 or later).

Table of contents

Renamed objects

ObjectThe old nameThe new name
The names of AddressData object properties are changed. For compatibility purposes, the previous names are supported.
  • Street
  • House
  • PrimaryAddressString
  • AdditionalAddressString
In the event log, presentations of the following events are modified: _$Data$_.TotalsMinPeriodUpdate and _$Data$_.TotalsPeriodUpdate.
  • _$Data$_.TotalsMinPeriodUpdate
  • Data. Modify totals period
  • Data. Modify minimum calculated totals period
  • Data. Modify maximum calculated totals period

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
Dynamic lists.
Queries.
Custom queries, including queries that generate dynamic lists, are now available in the mobile platform.This feature was not provided in the mobile platform.In mobile applications, you can use dynamic lists generated based on custom queries, and use queries to the infobase for implementing various features, such as checking balance while posting documents
Managed forms.
Faster form opening and faster execution of context server calls.Insufficient performance of form opening and execution of context server calls.Improved user experience by improving the performance of form operations.
Applied objects.
Predefined items are created at the first call of the corresponding table. Calling the SetPredefinedDataUpdate() method before the first call modifies the flag that shows whether predefined data is created.Predefined items were only created when mobile application configuration was updated. After calling the SetPredefinedDataUpdate() method, predefined data was only modified during the next mobile application configuration update.Mobile platform behavior is uniform with that of PC platform version 8.3.3.
Background and scheduled jobs.
Background jobs are now available in the mobile platform.This feature was not provided in the mobile platform.Background jobs are available in mobile applications.
Access rights.
Functional options.
In the mobile platform, the following features are available:
  • Functional options and functional option parameters.
  • Roles (limited support). Role management of item visibility and availability for forms and for the command interface.
  • A role setting for form visibility on the start page. After functional options and roles are applied, the first form from the list of available forms is displayed.
  • Infobase users (limited support).

Limitations of the implemented features are described in the documentation.

These features were not provided in the mobile platform.Extended features for applied solution interface management.
Database operations.
The EraseInfoBaseData() global context method is implemented.This feature was not provided on the mobile platform.On the mobile platform, you can delete all infobase data.
Development tools.
In Designer, support of Android Debug Bridge (adb) is added. Now you can start a mobile application from Designer on a mobile device emulator or on a physical device connected to a computer.This feature was not provided.Easier development and debugging of mobile applications for Android OS.
Internet-enabled functionality.
Telephony.
New features:
  • Send and receive emails using the built-in mail client of a mobile device. The MailTools object is implemented.
  • Send and receive SMS and MMS messages. The SMSMessage object is implemented.
  • Dial phone numbers. The TelephonyTools object is implemented.
  • Access the call history filterred by call type(incoming, outgoing, or missed).The CallLog object is implemented.

The limitations of the telephony tools on supported operating systems are listed in documentation.

Sending SMS messages and making calls was available with some limitations using parameters of the RunApp() and GotoURL() methods.

Access to the call history and sent email messages from the built-in email client was not available.

Easy access to mobile device functionality: SMS and MMS, call history, and making calls.
System requirements.
The configuration property RequiredMobileApplicationPermissions, specifies permissions that mobile application will require on Android:
  • Multimedia
  • Geolocation
  • Reading and writing contacts
  • Reading and writing calendar events
  • Access to telephony

The Mobile application builder uses the specified permissions.

This feature was not provided.You can specify permissions required for your mobile applications more clearly.
Multimedia tools.
Scanning barcodes using the mobile device camera is supported.

For the MultimediaTools object, the following methods are implemented: BarcodeScannerScanning(), ShowBarcodeScanning(), and CloseBarcodeScanning().

This feature was not provided.New mobile platform feature.
Development tools.
In Designer, you can edit pictures with variants. You can convert images to images with variants and back.You could only load pictures with variants without editing them.Creating images for mobile applications became easier.
Access to mobile device features.
Access to mobile device contact lists, both local and linked to specific accounts, is implemented. The following objects are implemented: ContactManager, ContactData, AccountContactData, LocalContactKey, ContactAccount, ContactDataItem, and ContactDataItemInstantMessaging.This feature was not provided.You can access mobile device contacts.
Access to mobile device features.
Access to mobile device calendars linked to specific accounts is implemented. The following objects are implemented: CalendarManager, CalendarAccount, LocalCalendarKey, LocalCalendarEventKey, CalendarEventData, AccountCalendarEventData, CalendarData, and AccountCalendarData.This feature was not provided.You can access mobile device calendars.
Location tools.
For the AddressData object, the AddressString property is implemented. It stores an address fragment starting from the street.This feature was not provided.The AddressData object functionality is extended. It can be used not only for geolocation purposes, but also for storing various types of contact information.
Development tools.
The mobile platform distribution kit mobile.zip now includes the version.txt file. The file contains the version number of the mobile platform delivered in the archive.This feature was not provided.Simplified identification of the mobile platform version, including scenarios that use Mobile application builder.
Mobile application builder.
The mobile application builder, which is included in the mobile platform, is improved:
  • The temporary user directory is no longer used for building. An explicitly defined directory is used instead, the path to this directory must contain ASCII characters only.
  • The build date of each mobile application is recorded (and displayed).
  • You can save graphic assets and mobile configurations to the hard disk.
  • When the mobile platform version 8.3.5 is loaded, the version number is obtained automatically from the version.txt file, which is included in the mobile platform distribution kit (mobile.zip).
  • Android SDK version 17 or later is required for building mobile applications for Android.
  • For files that contain graphic assets, the check whether the file contains a full set is implemented (the check is also performed when the file is loaded).
  • Files that contain graphic assets support icons for devices with high density screens (size 144 x 144 pixels, file name Android\icon-144x144.png).
  • Other improvements are implemented.
The mobile application builder had the following features:
  • The temporary user directory was used for building mobile applications. The mobile application could not be built for Android if the name of the user on whose behalf the build was performed contained non-ASCII characters.
  • Mobile application build dates were not recorded.
  • Saving graphic assets and mobile configurations to the hard disk was not available.
  • Android SDK version 17 was required for building mobile applications for Android, other versions were not supported.
  • The mobile platform did not support icons for Android devices with high density screens.
The usability of the mobile application builder is improved.
Client application.
The text displayed on the mobile platform splash screen is translated to all localization languages.The text displayed on the mobile platform splash screen was always displayed in Russian.Eliminated unexpected system behavior.
Common objects.
The option to run external applications on mobile devices and get the results of their execution is implemented. This feature is only available on operating systems of Android family.

The MobileDeviceApplicationLaunch and MobileDeviceApplicationLaunchExtrasData objects are implemented. +

This feature was not provided.Simplified applied solution integration with mobile applications, including the option to get mobile application execution result.

This feature is only available on operating systems of Android family.

Development tools.
During the building of an Xcode project, the "executable" attribute is set for the 1cem file included in the project.During the building of an Xcode project, the attributes of the 1cem file included in the project were not changed.Eliminated the problem that occurred when a project file was rebuilt on an operating system of Windows family: the "executable" attribute of the 1cem file was cleared.
Data display.
Mobile application builder.
In the mobile platform, graphical assets for iPhone 6 and iPhone 6 Plus devices are implemented:
  • splash screens: 750x1334, 2208x1242, and 1242x2208
  • icons: 87x87 and 180x180

In the mobile application builder, support of graphical assets for iPhone 6 and iPhone 6 Plus devices is implemented.

The mobile platform and mobile application builder did not support graphical assets required for iPhone 6 and iPhone 6 Plus devices.New Apple mobile devices are supported.

Table of contents

Transition from the previous version to the version 8.3.5

Table of contents

Version 8.3.4

Version 8.3.4 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.3 is added to the list of available values of the Compatibility mode property. +Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, and 8.3.2. +In version 8.3.4 you can run configurations created in version 8.3.3 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.4 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.3 for working with the infobase even after the transition to version 8.3.4. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on). +
Common objects.
In the RepresentableDocumentBatchItems object, the optional parameter DocumentAddress is implemented for the Add() and Insert() methods. This parameter stores the address of the temporary storage for the document being saved.This feature was not provided.Improved usability of generating document batches for saving and printing.
Spreadsheet documents.
You can save spreadsheet documents in HTML 5 format. Сharts and grafic primitives are saved in SVG format; free text rotation is supported.This feature was not provided.You can save spreadsheet documents in HTML 5 format.
Background and scheduled jobs.
When specifying a value for the Parameters property of the BackgroundJobs object or for the Parameters property of the Execute() method of the ScheduledJob object, you can omit any number of last parameters, provided that their default values are defined in the method that implements the background or scheduled job.During the start of a background or scheduled job, if any number of last parameters with default values specified were not specified explicitly, an exception was raised.You can modify methods implementing background or scheduled jobs by adding new parameters to the end of the parameter list, provided that their default values are defined. In this case modification of previously created code fragments that describe creation of background or scheduled jobs is not required.
Development tools.
In Designer, the following module editor features are available:
  • Selecting all entries of the identifier marked by cursor location
  • Selecting all entries of an identifier marked by a double-click
  • Selecting pairs of opening and closing 1C:Enterprise script clauses (including brackets): Procedure ... EndProcedure, If ... EndIf, and so on

Selecting identifiers is disabled by default. To use this feature, enable it in Designer options dialog box. Selecting the search expression is available in Designer, thick client, and thin client.

This features were not provided.The 1C:Enterprise script editor is improved.
External data sources.
External data sources support all features of the MySQL query language.

In the ExternalDataSourceConnectionParameters object, the MySQL value is implemented for the DBMS property.

In the technological log, the DBMySQL property is implemented for the DBMS property of the EDS event..

External data sources did not support all features of the MySQL query language.Dynamic lists, temporary tables, and other platform features are now supported for MySQL external data sources.
Interface.
Management of client application interface content from 1C:Enterprise script is implemented.

The objects ClientApplicationInterfaceContentSettings, ClientApplicationInterfaceContentSettingsGroup, and ClientApplicationInterfaceContentSettingsItem are implemented. Calling the RefreshInterface() global context method rebuilds interface panels according to the settings from the system storage.

For the ClientApplicationInterfaceSettings object, a constructor and methods GetContent() and SetContent() are implemented.

The ClientApplicationInterfaceContentSettings object stored the differences between the client application settings and the settings specified in Designer.

Interface management from 1C:Enterprise script was not supported.

1C:Enterprise script-based management of application interface panel visibility and positions.
Automated testing.
For the TestedFormField object, the WaitForDropListGeneration() method is implemented.This feature was not provided.The option to wait while a dynamic list is being generated is now available. You can use it when the generation takes significant time.
Interface.
A new display option intended for improving the view of item-heavy forms without introducing any significant form changes is available in the Taxi interface. The Scale property is implemented for managed forms. The property is only available if the Interface compatibility mode configuration property is set to Version 8.2. For the ClientSettings object, the ClientApplicationFormScaleVariant property is implemented.

This property modifes the scale of all forms in the applied solution for a specific user.

This feature was not provided. There was no simple way to make a form compact.For applications designed for Version 8.2 interface and not yet migrated to Taxi, a new option that regulates the scale of managed form items is implemented.

You can modify both a scale of a single form (which is not yet redesigned for Taxi interface mode) and the scale of the entire application (you might need this if the applied solution runs on a computer with a low-resolution or small-sized display).

The scale of a single form is specified in Designer, while the scale for the entire application is specified in the settings for a specific user.

Managed forms.
Passing additional parameters to an object creation form that is opened from a managed form text box is implemented (in addition to passing filters and standard parameters). Choice forms are used for storing additional parameters and passing them to item creation forms. Additional parameters are specified in choice parameters and choice parameter links using parameter naming forms (the parameter names must have the Additional. prefix). When item creation is initiated from a text box, these parameters are passed directly to the item creation form. When item creation is initiated from a drop-down list in a text box, they are first passed to the list form and then, when item creation is actually initiated, they are passed to the item creation form.

The standard parameter AdditionalParameters of Structure type is implemented for managed form extensions of objects, catalogs, documents, charts of characteristic types, business processes, tasks, and dynamic lists.

For dynamic list table extensions, the AdditionalCreateParameters property of FixedStructure type is implemented.

Filter values could be passed from text fields to item creation forms as filling values. Additional parameters could not be passed.You can pass additional parameters (that are not filter options) to an item creation form that is opened from a text box.
Managed forms.
You can enable or disable history for text fields linked to data of the following types: catalog, document, business process, task, chart of characteristic types, chart of calculation types, chart of accounts, or exchange plan.

The ChoiceHistoryOnInput property of configuration objects, configuration object attributes, and form items defines whether the history is enabled.

This feature was not provided.For text fields whose business logic does not require keeping the history of values, you can disable the history.
Managed forms.
You can use the DropListWidth property to specify minimum width of drop-down lists for managed form text fields. The actual list width is the minimum value of the following: the property value and the stabdard width (40 characters).Drop-down lists in text fields had fixed width (40 characters).You can increase the width of drop-down lists that contain long items.
Configuration repositories.
In Designer batch mode, the following features are available:
  • Creating a configuration repository (/ConfigurationRepositoryCreate command-line option)
  • Creating a configuration repository user(/ConfigurationRepositoryAddUser command-line option)
  • Copying users from another configuration repository (/ConfigurationRepositoryCopyUsers command-line option)
This feature was not provided. Configuration repository administrators only could create new configuration repositories and users interactively.You can automate administrative operations on configuration repositories, including automatic creation of repositories for project parts that are being developed independently.
Dynamic lists.
Document journals.
In document journals, you can use "Create" commands parametrized by the type of document being created. In a dynamic list that has a document journal table specified as its main table, a document creation button that opens a submenu with the list of documents available for the current user can be generated automatically.

For dynamic list form table extensions, a standard CreateByParameter command is implemented.

For the Button form item, the Parameter property is implemented. It is available only if the button is linked to the CreateByParameter command.

For the BeforeAddRow event handler of form tables, the Parameter parameter is implemented. It is used for passing document type values during document creation.

This change is not implemented in 8.3.2 compatibility mode.

In a dynamic list that has a document journal specified as a main table, a single Create command that did not open submenus was available. Running this command opened a dialog box for selecting document type. The type of document being created was not passed to the BeforeAddRow event handler of the form table linked to the dynamic list.In document journals that contain a small number of document types, you can simplify the type selection during document creation. Easy and fast generation of individual buttons for creating documents of specific types on the form command bar.
Server clusters.
Licenses with a limited number of simultaneous sessions are implemented for the 1C:Enterprise server. The limitations apply to the following sessions:
  • Designer (except for sessions intended for infobase creation)
  • Thin client
  • Web client
  • Thick client
  • External connection

Licenses can be activated for both 32-bit and 64-bit server versions. The server cluster that uses this license type can only contain a single working server.

This feature was not provided.

1C:Enterprise server did not have limitations for the number of simultaneously connected users.

Extended list of supported licenses for 1C:Enterprise server. New delivery option focused on using the server in small businesses or subsidiaries.
Internet-enabled functionality.
The thin client supports the TLS protocol since 1C:Enterprise version 8.3.4.428.

For the thin client, the /HttpsForceSSLv3 command-line option is implemented. It forces the system not to use the TLS protocol (if the connection is established using a web server), even if the web server supports this protocol.

1C:Enterprise versions 8.3.4.408 (and earlier) and 8.2.19 did not support the TLS protocol.You can use the TLS protocol when needed.
National settings.
The following Mongolian locales are supported:
  • mn - Mongolian
  • mn_Cyrl - Mongolian (Cyrillic)
  • mn_MN - Mongolian (Mongolian)
  • mn_Mong - Mongolian (Traditional Mongolian)
  • mn_Mong_CN - Mongolian (Traditional Mongolian, PRC)
Mongolian locales were not supported.When 1C:Enterprise is started on a computer with Mongolian national settings, it is not shut down unexpectedly.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Web client.
In Mozilla Firefox web browser, wordings in the web browser extension installation dialog box are clarified. The user is explicitly offered to install the extension.The web browser extension installation dialog box offered the user to enable the extension.For the web browser extension, the installation process is clearly differentiated from enabling the installed extension.
Advanced error handling.

Improved dump generation algorithm in the event of unexpected shutdown. The dump is generated even if a new exception occurs while the first exception is being processed.

If a new exception occurred while an exception was being processed, the dump was not generated.The frequency of cases where the cause of an unexpected shutdown cannot be found by analyzing dumps is reduced.
Client application.
In the web client, the following managed system forms are revised:
  • Select font dialog box
  • Search and replace dialog box in spreadsheet documents
  • Performance indicator dialog box

In all managed system forms, the Help button is located in the command bar, instead of the More (All actions) menu.

Managed system forms had different layouts.Managed system forms are improved.
Internet-enabled functionality.
Client application.
Microsoft Internet Explorer 11 web browser is now supported.Microsoft Internet Explorer 11 web browser was not supported.The new version of Microsoft web browser is now supported.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Configuration properties.
Configuration change checks are optimized.

The execution time is reduced for the following configuration check operations:

  • Executing the ConfigurationChanged() method
  • Starting a 1C:Enterprise client

Reading changes using the ReadChanges() method of an exchange plan manager.

The performance of configuration change checks lacked efficiency.Improved performance of configuration change checks.
Web client.
Improved web client performance with the Taxi interface when a large number of forms are open.The web client performance with the Taxi interface when a large number of forms were open lacked efficiency.Improved web client performance in the Taxi interface mode.
Server clusters.
Applied objects.
In the client/server mode, the impact of the numbering service on transaction start and end times is reduced, even when the numbering service is not used within the transaction.

In the client/server mode, the performance of the numbering service with a large number of prefixes is improved.

In the client/server mode, the numbering service had negative impact on transaction start and end times, even when the numbering service was not used within the transaction.

In the client/server mode, the performance of the numbering service with a large number of prefixes lacked efficiency.

Improved performance in the client/server mode when the numbering service is actively used with a large number of prefixes, e.g. in infobases with a large number of areas.
Managed forms.
Editing a large number of text lines in text boxes with the MultiLine property set to Yes was sped up for both thick and thin clientsThe performance of text boxes that contained a large number of text lines was insufficient.Reduced response time while editing large multiline texts in text boxes.
Configuration repositories.
For configuration repositories that do not use the compatibility mode, performance is improved for the following action types:
  • Open a configuration bound to the repository
  • Connect to the repository
  • Store objects to the repository
  • Update a configuration from the repository, retrieve objects, and cancel object locks
  • Store objects to the repository while multiple users are working simultaneously
The specified operations lacked efficiency.Improved performance of configuration repository operations.
Web client.
In Microsoft Internet Explorer 8 web browser, rounded borders of controls are not displayed in order to increase performance.In Microsoft Internet Explorer 8 browser, rounded borders of controls were displayed.Improved performance in Microsoft Internet Explorer 8 web browser.
Linux.
Performance of Linux clients is impoved for some scenarios.In some scenarious, Linux clients lacked efficiency.Improved performance of Linux clients.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Applied objects.
Before restructuring an infobase, the platform checks whether user-created object attributes or tabular sections with reserved names are present in exchange plans. The list of reserved names in English includes: Ref, Code, Description, DeletionMark, ThisObject, DataVersion, AdditionalProperties, SentNo, and ReceivedNo. The list or reserved names in Russian includes: Ссылка, Код, Наименование, ПометкаУдаления, ЭтотОбъект, ВерсияДанных, ДополнительныеСвойства, НомерОтправленного, and НомерПринятого. If any exchange plan contains attributes or tabular sections with names listed above, the infobase cannot be restructured.

This change is not implemented in 8.3.3 compatibility mode.

Before restructuring an infobase, the platform did not check whether object attributes and tabular sections with reserved names were present in the exchange plans.The system behaves as expected during infobase restructuring.
Applied objects.
In the FillCheckProcessing() handler, if the Cancel parameter is set to True, event subscription execution is interrupted for the following objects: catalogs, documents, register record sets (including recalculations), document sequences, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks.

This change is not implemented in 8.3.3 compatibility mode.

In the FillCheckProcessing() handler, if the Cancel parameter was set to True, event subscription execution was never interrupted.The system behaves as expected.
Common attributes / Data separation.
Managed locks.

In sessions that do not use separators, when data is being written or deleted, managed locks are set not only by reference and explicitly specified fields, but also by common attributes that serve as separators and include the object being written or deleted.

The common attributes that are not separators can be used in the DataLockFields configuration object property.

The DataLockFields list of attributes cannot contain common attributes that serve as separators in the Independently and simultaneously mode. You can specify such attributes as names for lock spaces of DataLock objects. If the separator value used in the DataLock object differs from the separator value used in the session, an exception is raised.

These changes are implemented for the following object types:

  • Catalogs
  • Documents
  • Charts of characteristic types
  • Charts of accounts
  • Charts of calculation types
  • Exchange plans
  • Business processes
  • Tasks
  • Constants
In sessions that did not use separators, when data was being written or deleted, managed locks were set only by reference and explicitly specified fields.

The common attributes that were not separators could not be used in the DataLockFields configuration object property. Such common attributes could not be used as names for lock spaces of DataLock objects.

The number of lock collisions is reduced. In sessions that do not use separators, you can modify data in any data areas within a lock space provided that the data does not belong to the area where the lock has been set. For example, a lock is set to the Products catalog in the O1 area. You can modify data in any areas where the separator value is not equal to O1.
Spreadsheet documents.
When a spreadsheet document is saved to a PDF file, charts (Chart, GanttChart, and Dendrogram objects) are saved in the vector format.When a spreadsheet document was saved to a PDF file, charts were saved as bitmap images.The resulting PDF file size is reduced. Charts are resized when the file display area is changed in the PDF file viewer program.
Configuration repositories.
The history of comments entered by users when they store objects to the configuration repository is implemented. The history stores last 20 comments. Users can enter comments (which are saved to the history) when they lock repository objects. Users can select comments from the history when they store objects to the repository.Comments that users entered when they stored objects to configuration repositories were not saved to a history. +

In the configuration repository, improved usability of repeated object storing operations related to a single task, such as step-by-step implementation of a single feature.

Access rights.
You can specify multiple roles to be used for defining access rights when the user list is empty.

The DefaultRoles configuration property is implemented. The DefaultRole property is supported for compatibility purposes. If the compatibility mode is disabled, accessing the DefaultRole property raises an exception.

In 8.3.3 version compatibility mode, you can only specify a single role in the DefaultRoles property.

Only a single role could be specified as the default one.

Simplified development of applied solutions that can be run with or without user list.

Applied objects.
For configuration objects that can contain predefined data, you can set the PredefinedDataName property to a value of a custom type, which consists of the # character and the text presentation of a unique identifier.The value of the PredefinedDataName property could be set only in the load mode (when the DataExchange.Load property was set to True).You can load predefined data from files that have custom format.
Automated testing.
For user action log entries that are generated as a result of user interaction with managed form fields, buttons, groups, tables, and decorations, the name attribute is implemented. It stores the name of the form item accessed by user.

The user action log conversion data processor includes the option that defines how the search for form items is performed: by presentation or by name. +

Form item presentations were recorded to the user action log.

The user action log conversion data processor only supported search for form items by item presentation.

The automated testing is more reliable. Search for form items by name is available, which eliminates the dependence of automated tests on localization language, item presentation typos, item presentation uniqueness, and so on.
Spreadsheet documents.
Spreadsheet documents are printed with the scale specified in their print options.

This change is not implemented in 8.3.3 compatibility mode.

On some printers, spreadsheet documents were printed at 200% scale.If a spreadsheet document is printed using a scale different from 100%, the system behaves as expected.
Dynamic lists.
In dynamic list filters, you can specify tabular section fields of objects that are used in the query that generates the dynamic list.

This change is not implemented in 8.3.3 compatibility mode.

Tabular section fields of objects could not be used in dynamic list filters.The list of dynamic list features is extended.
Dynamic lists.
During the retrieval of dynamic list data, dynamic list settings that are disabled by functional options are deleted.

This change is not implemented in 8.3.3 compatibility mode.

Settings disabled by functional options were not removed from dynamic list settings.Unexpected system behavior is eliminated.
Interface.
The colors of the sections panel and current section command panel in the Taxi interface are changed.

When the current section command panel orientation is vertical, its title is not displayed. The presentation of current section command panel is changed to current section function panel.

The colors of the sections panel and current section command panel in the Taxi interface were different.

If the current section command panel orientation was vertical, its title was displayed.

Better usability inTaxi interface mode.
Development tools.
Configuration repositories.
You can quickly view the selective change history of configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window.

Selective history is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, objects included in exchange plans, styles, main section working areas, flowcharts, forms, help pages, predefined items, command interface fragments, and role rights. +To view the selective history, right-click anywhere in any of the repository dialog boxes or in the configuration comparison window, and then click View selective history.

In the Filter repository versions dialog box, filter by properties of selected configuration objects is added. +Viewing selective history is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.

This feature was not provided. +Only the full object change history was available.Improved usability of configuration repository. Viewing the history of items that are parts of configuration objects is simplified.
Web client and web service publishing tools.
In Designer, in the dialog box for publishing the web client and web services:
  • You can manage execution of background jobs in file mode (the allowexecutescheduledjobs attribute of the ws tag).
  • You can specify whether web services are published by default (the pointEnableCommon attribute of the ws tag).
Managing execution of background jobs in file mode and specifying whether web services are published by default were only available when publishing was performed using the webinst utility (based on a template). The publishing dialog did not provide access to managing these features.You can specify all of the options available in the default.vrd file during interactive publishing.
Spreadsheet documents.
You can use the ViewScalingMode property of spreadsheet document form extension to specify how the spreadsheet document will be displayed: as in platform version 8.2 or enlarged.This feature was not provided. Reports with large fonts looked too large in the Taxi interface mode.You can scale displayed spreadsheet documents that have custom (large) fonts.
Dynamic lists.
In dynamic lists, presentation fields cannot be used in filters, groupings, or ordering. Searching by presentation fields is not available.In dynamic lists, presentation fields could be used in filters, groupings, or ordering. Search by presentation fields was available.Unexpected system behavior is eliminated.
External data sources.
Data composition system.
Queries.
In external data sources, you can use functions specified in them. A function can return a value, or a table, or nothing. +You can specify types of external data source tables: table or expression (this is required to describe functions that return tables). +To call an external data source function, use one of the following query language expressions:
  • ExternalDataSource.< Source name>.Table.<Table function name>(<Parameter 1>,...,< Parameter N>)
  • ExternalDataSource.<Source name>.<Function name>< Parameter 1>,...,< Parameter N>

You can call functions using the object model. This can be performed with either external data source managers or external data source table managers.

In the picture library, the ExternalDataSourceFunction is implemented.

External data sources did not support functions. +

The external data source functionality is extended.

Data composition system.
If an aggregate function is used in the RecordsFilter parameter of the EvalExpressionWithGroupArray() or EvalExpressionWithGroupValueTable() functions, an error is generated.

This change is not implemented in 8.3.3 compatibility mode.

Using aggregate functions in the RecordsFilter parameter of the EvalExpressionWithGroupArray() and EvalExpressionWithGroupValueTable() functions did not generate an error.Unexpected system behavior is eliminated.
Web client.
In Microsoft Internet Explorer 10 web browser, in managed form text boxes, the Clear input system button is removed.In Microsoft Internet Explorer 10 web browser, in the managed form text box, the Clear input system button had the same functionality as the Clear button, which was added by the platform.Eliminated web client appearance differences between Microsoft Internet Explorer 10 and other web browsers.
Configuration repositories.
The Update configuration from repository command is executed without displaying a dialog box if new objects are found in the repository.

New objects are automatically created in the target configuration.

The Update configuration from repository command opened a dialog box if new objects were found in the repository. If a configuration was updated using Designer batch mode and new objects were found in the repository, the update was not performed.Applied solution configurations can be updated automatically (for example, using the a batch file). You can include the update in various scheculed tasks, such as automated testing. The configuration update no longer requires interactive actions, which can pause the batch file execution.
Interface.
The splash screens for Designer and all types of client applications are modified: borders are used instead of shadows.The splash screens had shadows.Eliminated splash screen drawing issues in a number of scenarios.
Common objects.
Checks that determine whether defined type contents are valid are performed for each defined type call in the following scenarios:
  • during configuration verification
  • before saving a configuration.

The check is only performed when the Compatibility mode configuration property is set to Version 8.3.3 or None. If the compatibility mode is set to version earlier than version 8.3.3, defined type contents are only checked for the presence of external data source functions.

The checks whether defined type contents were valid were only performed when the dialog box for specifying configuration object attribute type was generated. When a configuration was saved, the checks whether defined type contents were still valid were not performed for each defined type call.Eliminated several potential issues that could occur during the development of applied solutions with defined types.
Managed forms.
In 8.2.16 version compatibility mode, if a text box does not have the selection list mode enabled, its drop-down lists do not contain the selection list specified in the text box properties.In version 8.3.3, drop-down lists in text boxes always contained the choice lists specified for these text boxes.Redesign is not required for applied solutions that run in version 8.2.16 compatibility mode.
Standard functions.
Common attributes / Data separation.

The standard Delete marked objects data processor attempts to set the exclusive mode for object deletion if the configuration compatibility mode is set to Version 8.3.3 or later (including the None value of the Compatibility mode property).

If the configuration has Version 8.3.2 or earlier compatibility mode, the exclusive mode is only set for sessions that do not use separators or in configurations that are not separated.

The standard Delete marked objects data processor attempted to set the exclusive mode for object deletion only if deletion was performed either in a session that did not use separators or in a configuration that was not separated. The compatibility mode did not affect the criteria for setting exclusive mode.

You can delete marked objects in sessions that use separators.
Applied objects.
An automatically assigned object number is reused if the transaction where the object was written is cancelled, regardless of the value of the Objects Autonumbering Mode configuration property.If the Objects Autonumbering Mode configuration property was set to Do not Release Automatically, an object number was not reused when the transaction where the object was written was canceled.Eliminated unexpected system behavior.
XML and XDTO support.
When data is deserialized from XML- or XDTO-serialized files, the Predefined items are ignored for tabular sections of charts of accounts and charts of calculation types. If such items are found, no errors occur and data is deserialized successfully.During the attempt to deserialize items of a chart of accounts or a chart of calculation types, having the Predefined item in a tabular section resulted in an exception and the deserialization could not be performed.You can load data serialized in later versions of 1C:Enterprise (version 8.3.5 and later).
Third-party software.
The OpenSSL library is updated to version 1.0.0m.OpenSSL version 1.0.0l was used.Eliminated OpenSSL security issues.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Information registers.

For information registers with Enable totals for retieving slice first or Enable totals for retrieving slice last property enabled, the Active and LineNumber fields are removed from the list of fields of information register slice first/last virtual tables.

If Enable totals for retieving slice first or Enable totals for retrieving slice last property is disabled, the Active and LineNumber fields are included in the slice first/last virtual tables.

The Active and LineNumber fields were included in the list of fields of information register slice first/last virtual tables.The system behaves as expected. In managed forms, the form items linked to the Active and LineNumber fields are removed automatically.
Managed locks.
Managed transaction locks (the DataLockFields property) cannot be set by attributes of objects of the following types: string of unlimited length, value storage, characteristic value type, and complex types that include these types.

The check is performed during the configuration check, and an error message is displayed if any field does not comply with the limitations.

It was recommended that you did not use attributes of the following types in managed locks: string of unlimited length, value storage, characteristic value type, and composite types that included these types.

During the configuration check, the check for managed locks by attributes of these types was not performed.

The configuration performance is optimized.

Improved quality control during configuration development.

Access rights.
The IsInRole() function raises an exception in the following cases:
  • A value that is not a string and not a Role configuration object is passed as a parameter.
  • A name of a role that does not exist is passed.

This change is not implemented in 8.3.3 compatibility mode.

The IsInRole() function did not check the parameter value and returned True even when the passed role was missing from the configuration.The system behaves as expected.
Data composition system.

When data composition is performed from 1C:Enterprise script, the platform checks whether the privileged mode is enabled while getting the list of available fields.

This change is not implemented in 8.3.3 compatibility mode.

When data composition was performed from 1C:Enterprise script, the platform did not check whether privileged mode was enabled.If privileged mode is enabled, data composition can include fields that users cannot access.
Web services.
The values of the WSParameterDirection system enumeration are corrected:
  • The InOut item represents the InOut value.
  • The Out item represents the Out value.

This change is not implemented in 8.3.3 compatibility mode.

The values of the WSParameterDirection system enumeration represented the following:
  • The InOut item represented the Out value.
  • The Out item represented the InOut value.

+

Unexpected system behavior is eliminated.
Data exchange.
 +

A flag that specifies whether predefined data should be updated for the entire infobase is now available. It can be set both in 1C:Enterprise script and in the command line. In the 1C:Enterprise mode, the predefined data update procedure checks the flag that is set for the entire infobase (in addition to checking the flags set for individual configuration objects, checking the flags set for infobase data, and checking the infobase type: master/not distributed infobase or subordinate infobase).

The global context methods SetInfoBasePredefinedDataUpdate() and GetInfoBasePredefinedDataUpdate() are implemented.

The command-line option /SetPredefinedDataUpdate is implemented for Designer batch mode.

This change is not implemented in 8.3.3 compatibility mode.

The check whether predefined data should be updated was based on infobase data and metadata flags and on the infobase type.You have the option to set predefined data update flags easily for infobases that are disconnected from distributed systems for maintenance. Also, the following scenario is now supported: exchange in a nondistributed infobase between two similar applications where predefined data is set in one of the applications and should be replicated to the other one during the exchange.
Applied objects.
In the thick and thin clients, the WriteParameters parameter is implemented for the AfterWrite handler of managed form extension handlers for constants, information register records, and register record sets.

In version 8.3.3 or earlier compatibility mode, the parameter always has the Undefined value.

The description of the WriteParameters parameter is added to the AfterWrite Syntax Assistant entry.

The AfterWrite handler of managed form extension handlers for constants, information register records, and register record sets lacked the WriteParameters parameter.

The description of the WriteParameters parameter was missing from the AfterWrite Syntax Assistant entry.

Unexpected system behavior is corrected.
Dynamic lists.
Functional options.
The main managed form attribute of Object(CatalogObject, DocumentObject, and so on) type is disabled if a functional option disables the corresponding configuration object. The main managed form attribute of DynamicList type is disabled if a functional option disables a configuration object that is used a main table for the dynamic list.

In both cases, only functional options without parameters are taken into account.

In 1C:Enterprise version 8.2, the main form attribute of Object type was not disabled even if any functional option disabled the corresponding configuration object.

In 1C:Enterprise version 8.3, the main form attribute of Object type was disabled if a functional option disabled the corresponding configuration object. All functional options were taken into account.

In the previous 1C:Enterpise versions, the main form attribute of DynamicList type was disabled if a functional option disabled the configuration object that was used as a main table of the dynamic list. All functional options were taken into account.

The system behaves as expected. In particular, the following issue is eliminated:
  • Editing a form changes a functional option parameter (directly or indirectly).
  • The new parameter value causes the functional option to disable the configuration object that is the main form attribute.
  • The disabled configuration object clears the entire object form.
Managed forms.
If the interface compatibility mode is set to Version 8.2, text boxes have the following specifics:
  • When a text box is activated, a drop-down list is not opened.
  • For the DropListButton property of the managed form field extension for a text box, the Auto value is interpreted as False.
  • For the ChoiceButtonRepresentation property of the managed form field extension for a text box, the Auto value is interpreted as ShowInInputField.
  • For the ChoiceButton property of the managed form field extension for a text box, the Auto value is interpreted as in 1C:Enterprise version 8.3.2.
  • Clicking the Down Arrow button opens a choice form, not a drop-down list.
In Version 8.2 interface compatibily mode,the text box behavior was identical to the text box behavior in Taxi interface compatibility mode.For users who migrated to 1C:Enterprise version 8.3 while keeping Version 8.2 interface compatibility mode, the system behavior is similar to previous versions.
System requirements.
Microsoft Windows 2000 operating system is no longer supported.Microsoft Windows 2000 operating system was supported.An outdated operating system is no longer supported.
Client application.
Client computers that run operating systems of Windows family require Microsoft Internet Explorer web browser version 7.0. On computers with Microsoft Internet Explorer version 6.0 or earlier, users of thick and thin clients of version 8.3.4 or later might experience various issues.Client computers that run operating systems of Windows family required Microsoft Internet Explorer web browser version 6.0 or later.The out-of-date web browser is no longer supported. The platform features that use Microsoft Internet Explorer now require Microsoft Internet Explorer version specified in the platform system requirements.

Table of contents

Renamed objects

ObjectThe old nameThe new name
A property of managed form extension for text fields. The former name is supported for compatibility purposes.
  • ListSelWidth
  • DropListWidth
The English name for the Choose() method of the QueryResult and QueryResultSelection objects is changed. The former name is supported for compatibility purposes.
  • Choose()
  • Select()
The button linked to the Cancel command in the managed report form extension, report settings form, and report variant form.

The former name is used in version 8.3.3 compatibility mode.

  • FormCancel
  • FormCancelEdit

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
System requirements.
Mobile platform now supports x86 Intel CPU-based devices that run Android OS. The mobile platform for x86 architecture is provided in a separate file.

The mobile platform distribution kit contains the following files:

  • 1cem-arm.apk, the developer's mobile platform for ARM architecture
  • cem-x86.apk, the developer's mobile platform for x86 architecture
  • prjandroid-arm.zip, the mobile platform for building mobile applications (for ARM architecture)
  • prjandroid-x86.zip, the mobile platform for building mobile applications (for x86 architecture)
The mobile platform did not support x86 Intel CPU-based architecture.More devices are now supported.
Development tools.
Mobile application builder is a new applied solution intended for building mobile applications. It has the following features:
  • Storing mobile configurations
  • Storing mobile platforms (starting from version 8.3.4)
  • Storing graphic assets
  • Building mobile applications
  • Storing the built mobile applications

Mobile application builder can build mobile applications for Android x86 operating systems.

It can also perform full building of mobile applications for iOS using a Mac computer with Xcode installed.

The configuration is delivered together with the mobile platform distribution kit. The data processor used for building mobile applications is removed from the mobile platform distribution kit.

Building can be performed using any Android SDK version.

A data processor was used for building mobile applications. It was included into the mobile platform distribution kit.Simplified building of mobile applications. Building mobile applications for iOS no longer requires additional steps.
System requirements.
Android version 2.2 is no longer supported.Android version 2.2 was supported.Support of the obsolete operating system version has ended.

Table of contents

Transition from the previous version to the version 8.3.4

Table of contents

Version 8.3.3

Version 8.3.3 includes known bug fixes and functionality modifications. +

New functionality and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.2 is added to the list of available values of the Compatibility mode property. +Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, and 8.3.1. +In version 8.3.3 you can run configurations created in version 8.3.2 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.3 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.2 for working with the infobase even after the transition to version 8.3.3. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on). +
Managed forms.
You can specify settings for vertical scaling of form elements, namely the minimum element height, at the development stage in Designer using the new VerticalScroll property.

If a form has a vertical scroll bar and the command bar is located above or below all form elements and occupies the entire form width, the area being scrolled does not include the command bar.

Managed form elements could be reduced to the default minimum height by reducing the form height. If a managed form had a vertical scroll bar, the area being scrolled included all form elements.Elements of managed forms with vertical scroll bars cannot be compressed below the minimum height guaranteeing comfortable work. The command bar with important form commands, such as Write and close, is always available because it is not included in the area being scrolled.
Managed forms.
Web client.
In the web client, if the VerticalScroll property of the managed form is set to UseIfNecessary, reducing the vertical form size never leads to reducing the vertical size of the form elements to the point where they can no longer be used.In the web client, reducing the vertical form size could lead to reducing the vertical size of the form elements to the point where they could no longer be used.Eliminated situations when reducing the vertical form size led to reducing the vertical size of the form elements to the point where they could no longer be used.
Development tools.
In the built-in script editor, you can group an arbitrary number of lines in the same way as they are grouped in some syntax units (conditions or cycles).

#Region and #EndRegion preprocessor instructions are implemented. These instructions are ignored during script execution. +A template for creating a script fragment with line grouping is added to the set of standard templates.

This feature was not provided. Only a few script syntax units allowed line grouping.Improved usability for working with source text. You can group parts of source text in a logical way and hide text that is not used at the moment.
External data sources.
Support of the following OLAP sources is added to the external data sources mechanism:
  • Microsoft SQL Server Analysis Services
  • IBM InfoSphere Warehouse
  • Oracle Essbase

Requests to OLAP sources and errors that occur during the request execution are recorded to the EDS event of the technological log.

The following pictures are added to the picture library: ExternalDataSourceCube, ExternalDataSourceCubeDimensionTableObject.

External data sources provided access to relational tables only.Both relational data and OLAP sources can be used when creating reports based on data from external systems (external data sources).
Interface.
You can get the resolution and DPI of monitors connected to a computer in the client application (thin client, thick client, web client) and at the server. For the external connection, the GetClientDisplayInformations() method returns UNDEFINED.

The information on characteristic of client computer monitors is passed through at the session start and when the RefreshInterface() method is called.

You could get the information on monitors connected to a computer only on the mobile platform.You can determine the number of monitors connected to the computer where the application is being executed, as well as their characteristics.
Data composition system.
For conditional appearance elements, you can specify areas where the given conditional appearance element will be used.

This feature is not used in dynamic lists.

This change is not implemented in 8.3.2 compatibility mode.

The conditional appearance was applied both to data area and area header, without further customizationExtended formatting capabilities for complex reports.
Web client and web service publishing tools.
Infobases, web services, and mobile applications can be published from Designer that is running on Linux. +Publishing can only be performed to Apache web servers and only if Designer is running under root account.Publishing of infobases and web services on Linux was possible only using the webinst utility. Publishing mobile applications was not available on Linux.Eliminated some Designer limitations on Linux.
Linux.
You can create distribution kits in the Linux version of Designer. The platform distribution files now include an installation program that installs templates and updates for applied solutions that run on Linux. The installation program supports both 32-bit and 64-bit Linux versions. The installation program shares the list of Linux operating systems with the client application.Creation of distribution kits was not available on Linux.You can install templates and update applied solutions on Linux operating systems.
Autorun.
The Autorun application is capable of running on Linux. The application supports both 32-bit and 64-bit Linux versions. The application shares the list of Linux operating systems with the client applications. +The following properties are added to the Element section of the autorun.lst configuration file: CommandWindows, CommandLinux, and RunAsRoot. The properties specify how a given item is executed in various operating systems.The Autorun application was not available for Linux systems. +The autorun.lst configuration file did not include CommandWindows, CommandLinux, and RunAsRoot properties.You can create applied solution distribution kits that include the Autorun application and are delivered on removable media that can be used to install the solution on both Windows and Linux operating systems.
Applied objects.
Managed forms.
Objects of reference types can be created while data is being entered in a form. A new property of configuration objects and form elements is implemented for this feature. The form element property manages the visibility of the command that creates a choice list element. The feature is implemented for catalogs, documents, charts of characteristic types, charts of accounts, charts of calculation types, business processes, tasks, and exchange plans. +The command for creating a choice list element is not available in version 8.3.2 compatibility mode.This feature was not provided. +Users had the option to open the choice form and create an object there, and then select the created object.Improved usability in cases when object creation is required while data is being entered.
Managed forms.
Development tools.
In the managed form editor, the list of elements available for adding to the form now includes a usual group without a title.In the managed form editor, in order to create a usual group without a title, a developer had to add a usual group and then change the properties that define whether the title is displayed.Improved usability of editing managed forms when groups are used for defining element positions on the form.
Managed forms.
Development tools.
During the generation of event handlers for client form elements and commands, you can specify which procedures will be generated:
  • A client handler only
  • A client handler and a server procedure (to be executed outside of a context) that is called from the handler
  • A client handler and a context server procedure that is called from the handler

A context server procedure cannot be generated for those client handlers where calling context server procedures is not recommended.

When a client handler was generated, this only included the generation of the handler itself. The associated procedures were not generated.Simplified development of forms where actions that are called at client are executed at server. Developers no longer have to create the server method manually and then add the method call to the client handler body.
Configuration repositories.
The data storage format of the configuration repository is modified. Repository objects are stored in the file system. The 1cv8ddb.1CD file stores information on changed objects. +The compatibility mode is implemented for the configuration repository. The new storage format is available only if the compatibility mode is disabled. +Optimization of configuration repository data is introduced. The optimization procedure is available both from the repository administration window and by using the ConfigurationRepositoryOptimizeData command-line option when Designer is started in batch mode. +The format of configuration repository files is not intended for reading or writing by any tools other than 1C:Enterprise.All configuration repository data was stored in the 1cv8ddb.1CD file. Optimization of the configuration repository was not available.Significantly increased number of changes (versions) that can be stored in the configuration repository.
Development tools.
Client application.
The infobase selection dialog box and the two authentication dialog boxes (for access to infobases and configuration repositories) that are displayed during the start of a client application or Designer can be disabled.

To disable them, use the DisableStartupDialogs command-line option for the 1cv8.exe/1cv8 file.

If the command-line that starts a client application or Designer contains errors that led to displaying these dialog boxes in earlier platform versions, the dialog boxes are not displayed; diagnostic messages are generated instead. These messages are recorded to the file that stores service messages (the Out command-line option).

During the start of client application or Designer in the batch mode, provided that infobase parameters or authentication parameters contained any errors, modal dialog boxes that prompted users to enter the correct parameters were displayed. This paused the execution of the entire batch.When Designer is started in batch mode - especially if Designer is started from another application or service - it is now possible to avoid the hard-to-detect situations when Designer attempts to create a selection dialog box for parameters that cannot be specified interactively, and therefore stops responding.
Localization.
The NumberInWords() and PeriodPresentation() global context methods support French language. The language code is as follows: fr, fr_CA. Values of the NumerationItemOptions parameter of the NumberInWords() method are specified similar to English, Finnish, and Kazakh languages.The NumberInWords() and PeriodPresentation() global context methods did not support French language.Improved presentation of information for French-speaking users.
Managed forms.
Full-text search.
For the FullTextSearchList object, you can disable the search by presentations of configuration objects. Use the MetadataUse property of this object to enable or disable this feature.The search by presentations of configuration objects could not be disabled.You can search by data only, without seaching by presentations of configuration objects at the same time.
1C:Enterprise script.
For the Array, Structure, and Map collections implemented constructors that create these objects based on the corresponding fixed collections (FixedArray, FixedStructure, and FixedMap). Recursive conversion is performed for arrays—a fixed array item that is a fixed array itself is recorded to a regular array.Fixed collections could be converted to their regular analogs only by using program loops.Simplified editing of values stored in fixed collections.
Common attributes / Data separation.
Exclusive access can be set for a data area. Exclusive access is not compatible with any data locks set by other sessions in this area. Exclusive access to a data area must be explicitly set or removed using the SetExclusiveMode() method. When a background job is started from a session that set exclusive access to a data area, the background job obtains exclusive access and the parent session loses exclusive access until the parent session is completed. At this time, changing data from the parent session is not available. Exclusive access is returned to the parent session after the background job completion. When a session switches to a different area, this does not affect the list of areas where the session has exclusive access.

Exclusive access to an area prohibits the following actions:

  • Creation of new sessions with the same set of separators.
  • Access to the area-contained data from enveloping areas.
  • Setting exclusive access in enveloping areas.

Setting shared managed locks for an area is ignored if exclusive access is set for this area.

Exclusive access to a data area could not be set. Instead, you only could set an exclusive managed transaction lock to all area-contained data.You can perform consistent changes of the data area even if they cannot be included into a transaction.
Common objects.
The DataHashing object can calculate the SHA1 and SHA256 hash functions.The DataHashing objects could calculate only the MD5 and CRC32 hash functions.The list of supported hash functions is extended.
Applied objects.
You can create defined types. A defined type consists of one or several allowed types, and it has a unique name. Defined data types can be used as types of configuration object attributes. Defined types cannot be included in complex types and cannot be used as data types for charts of characteristic types. +If you want to run the applied solution on a previous platform version, you have to remove all defined types from the configuration.This feature was not provided.You can create a type that can be used for defining types of specific attributes. For example, in a universal multipurpose configuration fragment, you can describe attributes that refer to data that will be defined when the fragment is included into a specific configuration.
Mobile application.
You can choose a ZIP archive containing multiple pictures of different sizes, instead of a single picture, for the application. This option is targeted for mobile applications that can be used in devices with different screen resolutions. The following mobile device screen types are supported:
  • devices with screen resolution below 140 DPI
  • devices with screen resolution from 140 to 180 DPI and Apple devices with standard screens
  • devices with screen resolution from 180 to 270 DPI
  • devices with screen resolution over 270 DPI and Apple devices with Retina screens

Each picture corresponds to specific screen settings of the target device. It is recommended that you use the PNG format for the archived pictures and you create the archive without compression. +For the Picture object, the ChoiceSet property is implemented.

This feature was not provided. On the mobile platform, the developer had to specify multiple picture versions for various screen resolutions using 1C:Enterprise script.Simplified process of creating applications intended for running on both PC and mobile devices. The developer only has to provide pictures for different display resolutions, and they do not have to write the script for resizing the pictures before displaying them in the 1C:Enterprise mode.
Accumulation registers.
Accounting registers.
In accumulation and accounting registers, the interval for storing totals by periods can be limited. You can specify both the lower and the upper boundary of the interval. Totals within this interval can be recalculated automatically when totals outside of the interval are changed. Totals by periods are not stored outside of the interval. They are calculated by register record tables when needed. +For accumulation register managers and accounting register managers, the following methods are implemented: SetMinTotalsPeriod(), GetMinTotalsPeriod(), and SetMinAndMaxTotalsPeriods(). +The totals storage limits are taken into account when the chart of accounts is changed, when register records are generated, when totals are recalculated, and when balance is obtained by balance accumulation and accounting registers. +When totals are enabled, periods are only recalculated if they contain actual changes. +This change is not implemented in 8.3.2 compatibility mode.Totals were stored by all periods later than the period of calculated totals for the register. When register records were changed for a prior period, all totals were recalculated for periods later than the modified date. +When using totals was turned on, all register totals were also recalculated.This change reduces database size and optimizes performance of administrative operations. +This decreases the system load for databases that store data for long periods (several years), and where changes in prior periods are performed on regular basis but regular data retrieval (using totals) is performed within a limited time interval from the current date.
Add-ins.
The add-in creation functionality includes the option to display interactive messages to users and the option to store values between sessions in a local web browser cache.

The add-in development technology documentation (http://1c-dn.com/library/add_in_creation_technology/) is updated by enhancing examples and adding new versions of web browser adapters.

The add-in creation functionality did not include the option to display interactive messages to users or the option to store values between sessions in a local web browser cache.When a web browser add-in attempts to access local resources, warnings can be displayed. They are similar to warnings available in the built-in platform features.
Web client.
Spreadsheet documents.
Printing documents.
Documents intended for printing can be combined into batches. To print the entire batch, you only have to start printing once. +You can specify printing options for batches. Batches can be nested. A batch can be written to a single PDF file, which simplifies printing in the web client. +The RepresentableDocumentBatch object is implemented.Batch printing was not available in the web client. To print a set of documents, the user had to click the Print button for each single document.Improved usability of printing muptiple documents (with different printing options) in the web client. To print a batch of documents, the user has to start printing once (regardless of the number or documents in the batch), and the printing options (including page orientation and the number of copies) will be set for each individual document.
Server clusters.
In the client/server mode, security profiles are implemented for the purpose of managing applied solution access to the following external resources on 1C:Enterprise server: file system, COM objects, add-ins, operating system applications, Internet resources, privileged mode, external reports and data processors, and global context methods Execute() and Eval(). A security profile can be assigned to each infobase; a security profile can also be assigned to the source code that is executed in the safe mode.

For the purposes of software cluster administration:

  • ISecurityProfile object is implemented.
  • ISecurityProfileVirtualDirectory object is implemented.
  • ISecurityProfileCOMClass object is implemented.
  • ISecurityProfileAddIn object is implemented.
  • ISecurityProfileExternalModule object is implemented.
  • ISecurityProfileApplication object is implemented.
  • ISecurityProfileInternetResource object is implemented.
  • For the IServerAgentConnection object, the following methods are implemented: GetSecurityProfiles(), RegSecurityProfile(), UregSecurityProfile(), CreateSecurityProfile(), GetSecurityProfileVirtualDirectories(), RegSecurityProfileVirtualDirectory(), UnregSecurityProfileVirtualDirectory(), CreateSecurityProfileVirtualDirectory(), GetSecurityProfileCOMClasses(), RegSecurityProfileCOMClass(), UnregSecurityProfileCOMClass(), CreateSecurityProfileCOMClass(), GetSecurityProfileAddIns(), RegSecurityProfileAddIn(), UnregSecurityProfileAddIn(),CreateSecurityProfileAddIn(), GetSecurityProfileUnSafeExternalModules(), RegSecurityProfileUnSafeExternalModule(), UnregSecurityProfileUnSafeExternalModule(), CreateSecurityProfileUnSafeExternalModule(), GetSecurityProfileApplications(), RegSecurityProfileApplication(), UnregSecurityProfileApplication(), CreateSecurityProfileApplication(), GetSecurityProfileInternetResources(), RegSecurityProfileInternetResource(), UnregSecurityProfileInternetResource(), and CreateSecurityProfileInternetResource().
  • For the IInfoBase object, the following properties are implemented: SecurityProfileName and SafeModeSecurityProfileName.
  • The type of the SafeMode parameter (used in the Create() and Connect() methods of external report and data processor managers and in the SetSafeMode() global context method) was changed from BOOLEAN to STRING. The type of value returned by the SafeMode() global context method was changed from BOOLEAN to STRING. When this parameter (or returned value) has STRING type, it stores the security profile name.

Similar changes are implemented in:

  • Cluster administration utility (rac) – the profile mode is implemented, and the update command of the infobase mode is modified.
  • Java API for server administration.
This feature was not provided.You can limit access of applied solutions to the resources of the system in which they run by using administrative tools (without modification of the applied solution source code). The functionality of the source code that is executed in the safe mode (for example, code developed by user) can be extended while preserving the required security level.

For example, you can use security profiles to organize individual temporary storage directories for each data area, or describe the list of Internet resources available for use in a specific infobase.

Automated testing.
The following objects are implemented:

TestedCommandInterfaceButton, TestedCommandInterfaceGroup, and +TestedWindowCommandInterface. +For tested objects, the GetObject() method is implemented. Its set of parameters is similar to that of the FindObject() and FindObjects() methods. If the object is not found, the GetObject() method raises an exception. +Methods for testing user messages are implemented. The list of properties and methods for managing tested objects is extended. You can get the form name, the current window, the command interface, and so on. You can get the information on the last error that occurred in the tested client application. +For the TestedApplication object, the methods GetActiveWindow() and GetCurrentErrorInfo() are implemented. For the TestedClientApplicationWindow object, the methods GetCommandInterface(), GetUserMessageTexts(), and ChooseUserMessage() are implemented. For the TestedForm object, the FormName property and the methods FindDefaultButton(), CurrentModified(), and GetCommandBar() are implemented, while the Close() method is moved to the TestedClientApplicationWindow object. For the TestedFormField object, the methods CurrentModeIsEdit() and GetEditText() are implemented, and the methods BeginEditCurrentArea() and EndEditCurrentArea() are modified. For the TestedFormTable object, the method CurrentModeIsEdit() is implemented, and the methods ChangeRow(), EndEditRow(), GotoPreviousRow(), GotoNextRow(), Expand(), and Collapse() are modified. For objects that describe tested form elements, the methods GetToolTipText(), CurrentVisible(), CurrentEnable(), CurrentReadOnly(), GetContextMenu(), and GetCommandBar() are implemented.

The application window command interface could not be tested automatically. Operations on user messages were not available during the automated testing.You can test the application window command interface automatically. +In test scenarios, simplified the processing of errors that occur when attempts to get non-existent objects are made.
Dynamic lists.
Dynamic list settings can be saved automatically. For managing this feature, the Auto save user settings property is implemented for dynamic lists. For storing settings, the dynamic list settings storage is implemented. For managed form tables linked to dynamic lists, the following functionality is implemented: commands for saving and restoring settings, and events for implementing custom responces to saving, restoring, or editing dynamic list settings. The view mode of the dynamic list (list, tree, or hierarchical list) is stored together with form element settings.

You can edit user settings of a dynamic list in a separate group of the form that displays the dynamic list. For that purpose, the User settings group property is implemented. Dynamic list settings can be edited in a separate common form, which is specified using the Default dynamic list settings form configuration property.

For the DynamicList object, the SettingsComposer property is implemented, which is similar to the corresponding property of report objects.

This change is not implemented in 8.3.2 compatibility mode.

For dynamic lists, only the following settings were saved automatically: filters (that were restored with disabled usage flag) and conditional appearance. To save and restore other settings, developers had to create custom algorithms in 1C:Enterprise script.Improved usability of dynamic lists for end users. Simplified development of dynamic lists with quick access to filters for developers. Development of custom algorigthms for saving or restoring dynamic list settings is not required.
Managed forms.
A new permission allowing end users to expand or collapse a managed form group (only vertically) was added. If the permission is granted, a user can collapse the group (hide all of the items that are included in the group). For managed form groups, the following properties are implemented: Behavior, ControlRepresentation, ShowLeftMargin, and CollapsedRepresentationTitle.

Only usual groups with displayed titles can be collapsed.

This feature was not provided. The only available method to hide unused items was to change their visibility. +

Hiding form items that are rarely used is available. This decreases the amount of data that is displayed to an end user. To view the hidden data, an end user can expand the group.

Development tools.
On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed is displayed in the message window.On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed was displayed in a modal window. +

Developers no longer have to close modal dialog boxes many times when they attempt to perform mass modification of objects that cannot be modified (for example, objects stored in a configuration repository that are not locked).

Interface.
A new client application interface type "Taxi" is implemented.

The Taxi interface includes a large number of changes, with the following highlights:

  • A whole new view: enlarged fonts, increased spacing between elements in forms, modified color scheme and form element layout, enlarged form elements.
  • Improved application navigation: focus on a single-window functionality, single purpose panels (such as history or favorites), switching back and forward between previously opened windows, and so on.
  • Extended main application window settings: developers can define the content and location of panels for the applied solution, at the same time users can arrange these panels as they like.
  • A system form for the full-text search.
  • The form navigation panel is located in the upper part of the form.
  • The message window is located in the lower part of the form and is only visible when there are messages to display.
  • The performance meter is displayed in a separate application window panel, not in a separate window.
  • In the History panel, records are grouped by days with their opening time displayed. You can search for history items and add them to Favorites.
  • In the Favorites panel, you can search for items, rename them, and "pin" important ones at the top of the list.

Use the iTaxi command-line option of the client application for the forced start of this interface mode (provided that using Taxi is allowed in the applied solution). You can also switch between interface modes using the client application settings window. +The following configuration properties are implemented:

  • InterfaceCompatibilityMode - specifies which interface modes are available in the applied solution.
  • ClientApplicationInterface - stores the list of panels used by default in the client application, as well as their positions.
  • DefaultSearchForm - specifies the search form that is used for the full-text search in application data. If the form is not specified, the system full-text search form is used.

A brand new look for the calendar. For the managed form calendar field, the following properties related to the new features are implemented: HeightInMonths, WidthInMonths, and ShowMonthsPanel. These properties are only used in the Taxi interface. +For the ClientApplicationInterfaceVariant object, the ClientApplicationInterfaceVariant property is implemented (it is used for getting the interface mode), and the global context method ClientApplicationInterfaceCurrentVariant(). The ClientApplicationBaseFontCurrentVariant() global context method is implemented. It gets the size of the base font in the client application. +For the UserWorkFavoritesItem object, the Important and Presentation properties are implemented. +In the Taxi interface, the Desktop is renamed to Start page (the related commands are renamed accordingly). The Dashboard section of the section pane is used for accessing the command interface. +In the Taxi interface:

  • The All actions menu is renamed to More.
  • The default presentations of standard commands in forms are changed, as well as command presentations in the command panel and in the More menu.
  • The presentations of form item groups are changed.

The link to the start page (desktop) of the applied solution has the following format: e1cib/navigationpoint/startpage. Start page (desktop) settings are stored with the settings key StartPage/WindowSettings (for Taxi interface, StartPage/Taxi/WindowSettings). +In the managed form editor, switching between interface 8.2 and Taxi modes in the preview window is implemented.

The interface implemented in platform version 8.2 was used in managed applications.Improved applied solution navigation, improved usability, development according to modern interface design trends.
Interface.
The NormalTextFont style font used as a basis for size calculation for other style fonts except the TextFont is implemented. The actual choice of font depends on the interface mode of the applied solution (Taxi or interface 8.2).This feature was not provided.Using the new font (and the fonts based on it) allows storing fort size proportions for managed form elements in both interface modes.
Interface.
The MainSectionPicture configuration property is implemented. In this property, you can specify a picture that will be used for the main section (desktop) in the section panel.The desktop had a fixed picture that could not be changed.You can create a uniform graphic design for your applied solution, and you can create a desktop look that will be friendly to the primary audience of the solution.
Development tools.
A context tooltip can be displayed for the

parameters of the function or procedure that is being edited in the module text editor. If the method has several syntax variants, you can select the required variant. +Automatic parsing of procedure and function comments for displaying them in context tooltips is implemented. Procedure and function comments can be sorted for displaying in the context tooltip. The comment format is described in the documentation and complies with the applied solution development standards. Procedure and function templates that comply with this format are included into the distribution kit. +The option that shows or hides the context tooltips is implemented in Designer. In the source code editor, you can open the context tooltip by pressing Ctrl+Shift+Spacebar.

In Designer, context tooltip for procedure and function parameters was not available. The context tooltip was only available for names of applied solution procedures and functions. Comments to procedures and functions were not used for getting information on their parameters.Improved usability of writing source codes. The Syntax Assistant is not required for a quick reference on the order and types of procedure or function parameters.
Administration tools.
The documentation describes DBMS setup and maintenance features that can be used for 1C:Enterprise administration.The documentation did not describe the administration tools that could be used without violating the license agreements.You can use DBMS features that do not affect the structure of data used by 1C:Enterprise (the changes that are made do not affect the restructuring and are saved after the restructuring).
Managed forms.
For fields of check box and radio button types, the tumbler look is implemented (several adjacent buttons where the active value has a different color). For managed form fields of these types, the properties CheckBoxType and RadioButtonsType are implemented.This feature was not provided.New presentation features. Improved usability for touch interfaces.
Database configuration updates.
Server clusters.
Infobase restructuring is required when a chart of characteristic types is modified or when a chart of accounts where a chart of characteristic types is used as an extra dimension,is modified.

The following changes are implemented in the background restructuring procedure:

  • You cannot create, edit, or delete exchange plan items if the exchange plan requires the restructuring. The restructuring is performed during the processing phase.
  • You cannot create, edit, or delete chart of characteristic types items if the chart is specified as an extra dimension for a chart of accounts and this chart of accounts requires restructuring. In this case the restructuring of the chart of characteristic types is performed during the processing phase.
  • The SetPredefinedDataUpdate() method cannot be called during the background restructuring.
Charts of characteristic types were restructured when they were modified.

All charts of characteristic types and exchange plans were restructured when the changes were applied (during the background restructuring).

In the background database configuration update, the specifics of changing some data structures are taken into account. This prevents mismatching of object data.
System requirements.
Microsoft Windows Server 2012 (x86-64) is now supported.Microsoft Windows Server 2012 (x86-64) was not supported.New version of the Microsoft operating system is now supported.
Data display.
If the Interface compatibility mode configuration property is set to Taxi or Taxi.Version 8.2 enabled, the Help picture from the picture library corresponds to the Taxi interface.The appearance of the Help picture in the picture library did not depend on the configuration property values.The appearance of the Help button depends on the interface mode.

Table of contents

New functionality and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Printing documents.
Changed behavior of print status forms in managed applications in thin and thick clients:
  • In the Forms in tabs form opening mode, print status forms are opened in separate windows.
  • The form is opened in a modal window so that users cannot interact with the interface during printing.
  • The form cannot be closed by clicking the "X" button.

The form cannot be resized.

The print status form had different behavior.Improved usability of printing documents.
Linux.
The Primary Selection clipboard is now supported (data is copied to this clipboard when a text fragment is selected, without the need to press any keys). Copying to the Primary Selection clipboard is supported for the following form elements:
  • Text box
  • Text document field
  • Formatted document field
  • Spreadsheet document field

Insertion from the Primary Selection clipboard (available by pressing the middle mouse button) is supported in text boxes.

This feature was not provided.Improved usability of client application for users with Linux experience.
Managed forms.
Functional options.
If a text box is linked to an attribute of complex type where all types except one are disabled by access rights or functional options, when user attempts to select a value in the text box, the choice value form is opened.

This change is not implemented in 8.3.2 compatibility mode.

If a text box was linked to an attribute of complex type, when a user attempted to select a value in the text box, the type selection dialog box, was displayed even if the list of types contained a single value. +

Users do not have to select from a single value in the type selection dialog box.

Automated testing.
On closing an application, if the log of user actions is being recorded at the moment, a request for saving the log is sent.On closing the application, unsaved data from the log of user actions was lost.Reduced chance of losing unsaved data from the log of user actions when the application window that initiated recording to the log of user actions is closed.
Web client.
During the startup of the web client, the check for a pop-up window blocker is only performed if the separate window interface is used and modal windows are enabled. +The check for a pop-up window blocker is performed after the user authentication.

+

+

The check for a pop-up window blocker was always performed during the web client startup.Users are not prompted to specify the pop-up blocker settings when it is not required.
Interface.
On interface mode change, the user is prompted to restart the client application.Changing interface mode did not prompt to restart the client application.The procedure of changing the interface mode became more user-friendly: the system now informs the user what they have to do to have the changes take effect.
Standard functions.
The following changes are implemented in the standard functions:
  • Event log:
    • The set of commands in the form command bar is changed, as well as the command presentations.
    • The procedures for enabling and disabling the filter are revised.
    • You can view log entry data by clicking the link in the corresponding log column.
    • You can filter records by date and time.
  • Find references to object:
    • You can search for references to a reference that is found (from the context menu).
  • Manage full-text search:
    • The form is revised.
    • Enabling or disabling full-text search is performed without opening additional forms.
  • Post documents:
    • The form is revised.
  • Active users:
    • You can open the event log filtered by user by clicking a hyperlink in the User column.
Standard function dialog boxes were less user-friendly.

Improved usability of standard functions.

Web client.
The documentation includes recommendations for choosing a web browser for low-performance computers.The documentation did not include recommendations for choosing a web browser.Recommendations for choosing a web browser are available.
Web client.
In Microsoft Internet Explorer web browser, notification windows do not fade out of view when they are closed automatically.In Microsoft Internet Explorer web browser, notification windows faded out of view when they were closed automatically.Improved performance of notification windows in Microsoft Internet Explorer web browser.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
DBMS operations.
Accumulation registers.
Queries.
Optimized performance of accumulation register virtual tables when obtaining totals with a filter that does not include all dimensions.Insufficient performance of accumulation register virtual tables when obtaining totals with a filter that did not include all dimensions.Performance of accumulation register virtual tables is increased.
Server clusters.
Creation of new sessions is optimized.Creating of new sessions was performed inefficiently.Optimized performance when establishing connections to the 1C:Enterprise server in the following cases:
  • Simultaneous connections from a large number of client applications.
  • Connection of a new client application to a cluster that already runs a large number of sessions.
Information registers.
Improved performance of independent, non-periodic information registers that have more than 1 dimension. +This change is not implemented in 8.3.2 compatibility mode.Insufficient register performance.Increased speed of writing to a register, especially when a large number of users are working.
Applied objects.
Optimized selections from catalogs and charts of characteristic types for certain scenarios. +In certain scenarios performance of selections from catalogs and charts of characteristic types was inefficient.Increased performance of selections from catalogs and charts of characteristic types in certain scenarios.
Dynamic lists.
Improved dynamic list performance in client/server mode when a large number of users are working.In certain scenarios dynamic list performance was insufficient.Improved dynamic list performance in certain scenarios.
Server clusters.
Optimized processing of session data for some scenarios.In some scenarios processing of session data was inefficient. +

Improved performance and scalability of 1C:Enterprise servers.

Accumulation registers.
Optimized execution of queries to turnovers registers with a large number of dimensions that include aggregates (for some scenarios). This change is not implemented in 8.3.2 compatibility mode.In some cases execution of queries to turnovers registers with a large number of dimensions that included aggregates was inefficient.You can use aggregate functions in more scenarios than before.
DBMS operations.
In order to optimize some queries to IBM DB2 DMBS, the recommendation to run the db2set DB2_OVERRIDE_BPF=5000 command and then restart the DBMS is included into the documentation. Methods of detecting situations when the optimization is required are also described in the documentation.Some queries to IBM DB2 DBMS were performed inefficiently.Optimized performance during the execution of some types of IBM DB2 DBMS queries.
Information registers.
For periodic information registers that are subordinate to recorders, the Active field is listed in the following indexes:
  • By period
  • By dimensions
  • By dimension

The Active field is the last one in these indexes. +After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes. +This change is not implemented in 8.3.2 compatibility mode.

The Active field was not included in the list of indexes of periodic information registers subordinate to recorders.Improved performance when retrieving the first and the last slices.
Server clusters.
1C:Enterprise server is optimized to reduce memory usage and fragmentation.In some scenarios, 1C:Enterprise server used memory inefficiently. This led to memory fragmentation and increased memory consumption.Reduced memory consumption of 1C:Enterprise server, and lower memory fragmentation. This allows to reduce the number of planned 1C:Enterprise server restarts and improves the system stability.
DBMS operations.
Indexes of attributes with additional ordering include deletion marks and all fields that are indexed with additional ordering. This data is added to the end of the index.Indexes of attributes with additional ordering did not include deletion marks and all fields that were indexed with additional ordering. +

Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark).

Managed forms.
Optimized performance of displaying managed forms after server calls (both explicit and implicit ones) that change the form appearance.Forms were not displayed fast enough when their appearance was changed from 1C:Enterprise script.Optimized performance of displaying forms, for example, when the displayed title of a form element is modified.
Common attributes / Data separation.
Once the version 8.3.2 compatibility mode is disabled, optimization is performed on the structure that stores data on the table separators connected to objects included in the separator contents. When the version 8.3.2 compatibility mode is enabled, the reverse restructuring of the database tables is performed.The structure that stored separator data was not optimal.Improved performance due to the changes in the structure that stores separator data.
Server clusters.
In server cluster, the algorithm for balancing the working process load is optimized. The following parameters are used in addition to parameters used in the previous versions to define the available server performance: size of CPU queue, current processor load, and number of CPU cores. +Values used for defining the available server performance are recorded to the TXT property of the CLSTR event in the technological log. +To obtain performance parameters, the user on whose behalf the 1C:Enterprise server is running must be included in the Performance Log Users group.In the server cluster, the algorithm for balancing the working process load took less number of parameters into account.Improved reactivity of the load balancing algorithm. The algorithm defines overloaded CPUs and stops sending new tasks to them.
Managed forms.
Optimized performance of opening managed forms with multiline text boxes that contain a large number of line breaks.Performance of opening forms with multiline text boxes containing a large number of line breaks was not high enough.Forms with multiline text boxes that contain a large number of line breaks are opened faster.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Software licensing.
Licenses for basic configurations are available on Linux.Basic version licenses for Linux were unavailable.You can run basic 1C:Enterprise configuration versions on Linux.
Applied objects.
Infobase object autonumbering logic is revised. The check for number or code uniqueness (including automatically generated codes and numbers) is always performed while the object is being written.

The message informing the user that a number or code is not unique now specifies the value of the non-unique number or code.

Numbers or codes that are no longer used are never re-assigned automatically, even when the desired prefix is not specified explicitly. In the event when the desired prefix is not specified explicitly, the platform forms a number or code as follows: it selects the greatest of the prefixes that match the specified pattern and then adds the next subsequent number (prefixes are compared according to their alphabetical order, for example, B is greater than A).

The uniqueness check was not performed for automatically generated numbers or codes while the object was being written.

The message informing the user that a number or code was not unique did not include the value of the non-unique number or code.

Numbers or codes that were no longer used might be re-assigned automatically in the event when the desired prefix was not specified explicitly–the platform might assign a code that was used before when its prefix matched the specified pattern and the prefix was not the greatest one among those matching the pattern (prefixes are compared according to their alphabetical order, for example, B is greater than A).

Increased stability and reliability of infobase object autonumbering. +Messages informing the user that a number or code is not unique now contain more information. +The autonumbering is more logical: numbers or codes are always issued in the ascending order.
Applied objects.
If a text value presentation cannot be calculated during debugging, the string Error getting value presentation is returned as a text presentation.If a text value presentation could not be calculated, Designer might stop responding.Improved system stability during debugging.
Managed forms.
Visibility of the command for switching to the calculation register (in a recorder form) is set to True by default.

This change is not implemented in 8.3.2 compatibility mode.

Visibility of the command for switching to the calculation register (in a recorder form) was set to False by default.Default visibility of commands for switching to registers is the same for all registers.
Managed forms.
When attributes of Number type that have minimum or maximum values set are cleared interactively, the attribute values after clearing cannot exceed the specified limits. +This change is not implemented in 8.3.2 compatibility mode.When attributes of Number type were cleared interactively, their minimum and maximum values were ignored.Users cannot enter data that does not meet the conditions specified by the developer.
Applied objects.
When a spreadsheet document is saved to a .docx file, image border styles are preserved. +This change is not implemented in 8.3.2 compatibility mode.When a spreadsheet document was saved to a .docx file, images always had borders.More accurate export of spreadsheet document styles to .docx format.
Applied objects.
When a spreadsheet document is saved to a .docx file the following spreadsheet document print options are preserved:
  • paper size
  • page orientation
  • scale
  • pagination
  • margins
  • headers and footers
  • repeating rows
  • displaying headers and footers on the first page

This change is not implemented in 8.3.2 compatibility mode.

Print options were not preserved when a spreadsheet document was saved to a .docx file.Improved usability of spreadsheet documents saved in .docx format.
Data composition system.
When a user field is added to data composition system settings and the source of available settings is not specified, the file name is generated using the language of the current script variant.

This change is not implemented in 8.2.16 compatibility mode. +

When a user field was added to data composition system settings and the source of available settings was not specified, the file name was generated in English.The data composition system behavior is uniform with behavior of similar platform features.
File operations.
The look and behavior of the file selection dialog box (including the FileDialog object) in Windows Vista and later Windows versions complies with the standards of these operating systems. In Windows XP and earlier and in the web client the look of the dialog box is not changed.In Windows Vista and later, an outdated file selection dialog box was used.The look of the file selection dialog box corresponds to the operating system being used.
File operations.
If both Directory and FullFileName are specified for a FileDialog object, the dialog box is opened in the specified directory and with the specified file name.If both Directory and FullFileName were specified for a FileDialog object, the dialog box ignored the specified directory and used the directory that was obtained from the full file name.Improved usability of the file choice dialog.
Automated testing.
Wildcard support implemented for the InputText() method of the TestedFormField object.The automated testing mechanism did not support wildcards in text input fields.Extended functionality of the automated testing system.
Dumping/loading configurations to files.
When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName.

Configurations dumped using earlier platform versions cannot be loaded.

When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.
When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName.

Configurations dumped using earlier platform versions cannot be loaded.

When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.
When dumping a configuration to XML files, names of standard commands of managed forms follow this convention: Form.StandardCommand.CommandName. +Configurations dumped using earlier platform versions cannot be loaded.When dumping a configuration to XML files, names of standard commands followed this convention: +FormStdCommand.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.
When dumping a configuration to XML files, names of managed form commands follow this convention: Form.Command.FormCommandName. +Configurations dumped earlier will not be loaded.When dumping a configuration to XML files, names of managed form commands followed this convention: FormCommand.FormCommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.
When dumping a configuration to XML files, names of standard commands of managed form elements follow this convention: Form.Item.ElementName.StandardCommand.StandardCommandName. Configurations dumped earlier will not be loaded.When dumping a configuration to XML files, the standard commands of managed form elements followed this convention: Form<ElementType>.ElementName.StandardCommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configurations to files.
When a configuration is dumped to files:
  • References to missing configuration objects are dumped as text presentations of identifiers of missing configuration objects.
  • Properties of the ManagedForm element of a managed form that make sense only in the 1C:Enterprise mode are not dumped.
  • For attributes and elements of managed forms, the internal identifiers required for saving their settings are dumped.

For elements of business process flowcharts, element identifiers are dumped.

 +

When a configuration was dumped to files:

  • References to missing configuration objects were ignored.
  • Properties of the ManagedForm element of a managed form that made sense only in the 1C:Enterprise mode were dumped.
  • For attributes and elements of managed forms, the internal identifiers required for saving their settings were not dumped.
  • For elements of business process flowcharts, element identifiers were not dumped.
In dumping/loading of configurations, the following improvements are implemented:
  • User settings are preserved when a configuration is dumped and then loaded.
  • The accuracy of configuration comparison (after a configuration is dumped and then loaded) is increased.
Managed forms.
When Esc is pressed in a text box (except multiline text boxes), the following actions are performed:
  • If the initial text box content was modified in any way, the text box reverts to the initial content.
  • If the initial content was not modified, the text box does not process pressing the Esc key and passes the processing to the form.
Pressing Esc was always processed by the form. The text box did not perform any actions if Esc was pressed while the text was being edited.You can cancel editing a value in a text box.
Managed locks.
The maximum number of managed locks is 100 000 (exceeding this limit locks the entire lock space).The maximum number of managed locks was 20 000 (exceeding this limit locked the entire lock space).Improved user experience when using transactions with a large number of locks (more than 20 000) in a single lock space.
Information registers.
Data exchange.
When a set of information register records is passed to the SelectChanges() method as a filter value, the system behavior depends on the compatibility mode:
  • In version 8.2.16 or earlier compatibility mode, the selection includes data that does not match the filter criteria defined by the record set;
  • In version 8.3.1 or later compatibility mode (or if the compatibility mode is not used), the selection only contains data that exactly matches the filter criteria.
When a set of information register records was passed to the SelectChanges() method as a filter value, the system behavior did not depend on the compatibility mode.
  • In version 8.2.16 or earlier, the selection included data that did not match the filter criteria defined by the record set
  • In version 8.3.1 or later, the selection only contained data that exactly matched the filter criteria.
Improved compatibility with previous platform versions.
Dynamic lists.
In the data composition system and query wizard, syntax units enclosed in braces {} do not lead to errors in dynamic lists.In the data composition system and query wizard, syntax units enclosed in braces led to errors in dynamic lists in some cases.Better stability of dynamic list. +
Cryptography.
The value of the CryptoModuleName parameter in the CryptoManager object wizard is case insensitive.The value of the CryptoModuleName parameter in the CryptoManager object wizard was case sensitive.The system behavior complies with common standards.
Managed forms.
Ordinary forms.
In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromMenu() method is a managed form table, a managed form, a table box, or an ordinary form, the menu that is opened using this method is displayed in the following location:
  • For a table box or a managed form table, the menu is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table if the current cell cannot be determined.
  • For a form, the menu is displayed in the upper left corner.

This change is not implemented in 8.3.2 compatibility mode.

 +

If the second parameter (FormElement) of the ChooseFromMenu() method was a managed form table, a managed form, a table box, or an ordinary form, the menu was displayed in the following location:

  • For a table box or a managed form table, the menu was displayed in the lower left corner of the element passed as the parameter value.
  • For a form, the menu was displayed in the lower left corner of the current form element. If the current form element could not be determined, the menu was displayed in the lower left corner of the form. In the web client, the menu was displayed in the center of the screen.
Uniform behavior when the system opens similar menus (e.g. context menu in a managed form table) or the applied solution opens such menus (using the ChooseFromMenu() method).
Managed forms.
Ordinary forms.
In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromList() method is a managed form table, a managed form, a table box, or an ordinary form, the list that is opened using this method is displayed in the following location:
  • For a table box or a managed form table, the list is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table, if the current cell cannot be determined.
  • For a form, the list is displayed in the upper left corner.

This change is not implemented in 8.3.2 compatibility mode.

If the second parameter (FormElement) of the ChooseFromList() method was a managed form table, a managed form, a table box, or an ordinary form, the list was opened in the following way:
  • For a table box or a managed form table, the list was displayed in the lower left corner of the element passed as the parameter value.
  • For a form, the list was displayed in the lower left corner of the current form element. If the current form element could not be determined, the list was displayed in the lower left corner of the form.
  • In the web client, the list was displayed according to form settings because a system form was used to display it.
Uniform behavior when executing similar actions (the ChooseFromMenu() and ChooseFromList() methods). +
Development tools.
You can search and replace in the ChoiceParameters property of configuration objects. The search and replace algorithm is modified for the ChoiceList and ChoiceParameterLinks configuration objects. +The search and replace are performed:
  • For the ChoiceParameters property: in the Name and the Value columns (including fixed array elements). The search is performed on values of String type.
  • For the ChoiceList property: in the Presentation column and in the Value column if the value has the String type.
  • For the ChoiceParameterLinks property: in the Name column.
  • Every time the search string is found, the search/replace procedure is paused and a message prompting to resume the procedure is displayed.

Search in the LinkByType property of configuration objects is no longer supported.

Search and replace in the ChoiceParameterLinks property of configuration objects was performed only in the Name column. +Search and replace in the ChoiceList property of configuration objects was performed only in the Presentation column. +Search and replace was not performed in the ChoiceParameters property of configuration objects. +Search could be performed in the LinkByType property of configuration objects.The search and replace operations in configuration object properties are now uniform to similar operations in texts.
Development tools.
The presentation of the ChoiceParameters property of configuration objects in the object properties editing window is changed. If a value of any property element is a fixed array, presentations of array values are used. +The presentation of the ChoiceList property of configuration objects in the object properties window is changed. A presentation now consists of both list item values and their presentations (if the presentations are specified).If an element of a ChoiceParameters property was a fixed array, its presentation was a FixedArray string. +For the ChoiceList property of configuration objects, the presentation in the object properties window was generated from the list item values only.Improved usability of ChoiceParameters and ChoiceList properties in Designer.
Managed forms.
Improved look and behavior of drop-down lists in text box fields that can be edited and contain data of reference type, enumerations, or system enumerations:
  • If a field contains data of reference type or an enumeration, the field includes the choice button, and the characters typed in the field do not match any choice list values, the Click show all to select item message is displayed in the list.
  • If the drop-down list is displayed and a value is selected in it, pressing Tab, Shift+Tab, or Enter selects the current value from the list. Clicking another form element does not select the current value; the list is closed instead (same effect as pressing Esc). The selection is not moved to the form element that was clicked.
  • If the drop-down list is not displayed and the characters typed in the field uniquely identify a choice list value, pressing Tab, Shift+Tab, or Enter selects this value. Clicking another form element also selects this value.

If the drop-down list is not displayed and the characters typed in the field match multiple choice list values, pressing Tab, Shift+Tab, or Enter opens the drop-down list. Clicking another form element also opens the drop-down list.

The drop-down list had a different look and behavior. Improved usability of text box fields that contain data of reference type, enumerations, or system enumerations.
Accumulation registers.
You can enable the aggregates mode for any turnovers accumulation register, regardless of the actual presence of aggregates in metadata. +In the client/server mode you can create new optimal aggregates (and remove outdated ones) when aggregates are being rebuilt in 1C:Enterprise mode. +This change is not implemented in 8.3.2 compatibility mode.Developers had to add aggregates in Designer to keep the list of optimal aggregates up to date.Simplified support of optimal aggregate list: you only have to rebuild aggregates on regular basis.
Managed forms.
In text boxes containing data of reference type, only the color of the text presentation of the value is changed on element activation.In text boxes containing data of reference type, the color of the entire field changed on element activation.Better text box usability. A tooltip can be displayed in a text box linked to data of reference type if the text box is first in the tab order of the form.
Development tools.
Configuration repositories.
You can perform quick comparison of selected configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective comparison is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, exchange plan content objects, styles, desktop workspaces, maps, forms, online help pages, predefined items, command interface fragments, and role rights. +To run the selective comparison command, right-click anywhere in any of the repository dialog boxes or in the compare configurations window, and then click Perform selective comparison with the configuration object. +Selective comparison of configuration objects is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.This feature was not provided. +When comparison was initiated for a specific object, full comparison of two configurations was performed. The focus in the comparison window was set to that object.Improved usability of configuration repository. Optimized comparison procedure when it is performed for a single configuration object.
DBMS operations.
Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later is now available.

All of the required settings are specified automatically by the installation program of the patched PostgreSQL version unless a cluster created by the standard PostgreSQL version is found on the computer.

Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later was not available.1C:Enterprise supports clusters created by the following versions of PostgreSQL DBMS:
  • PostgreSQL 8.1.5-X.1C - 9.1.2-1.1C
  • PostgreSQL 9.2.1-2.1C
  • Standard version of PostgreSQL provided that the cluster locale is identical to the infobase locale.

You can upgrade or downgrade 1C:Enteprise without upgrading or downgrading the associated PostgreSQL instance; this does not require any manual configuration.

Note that once you migrate to a new PostgreSQL version, you cannot use 1C:Enterprise version 8.3.2 or earlier. This only applies to new infobases that were created using PostgreSQL 9.2.1-2.1C. Do not create infobases using PostgreSQL 9.2.1-2.1C if you are planning to access them from earlier platform versions.

Managed forms.
If the ChoiceDataGetProcessing event handler of the enumeration manager returns an empty list and the formal parameter StandardProcessing returned by this handler is set to False, the returned list is used for filling the choice list. +This change is not implemented in 8.3.2 compatibility mode.If the ChoiceDataGetProcessing event handler of the enumeration manager returned an empty list and the formal parameter StandardProcessing returned by this handler was set to False, the client application filled the choice list by all enumeration values.The system behaves as expected when a developer decides to disable selection of enumeration values.
Standard functions.
In the default event log form, filter presentation is localized.In the default event log form, filter presentation was always displayed with Russian names of event log columns.The filter presentation is uniform with other platform features.
Configuration repositories.
Optimized the reference integrity check algorithm for configuration repository operations (storing and retrieving) on objects that are deleted from the repository and objects that reference to deleted ones. +In some cases, it is not necessary to lock objects that contain references to objects being deleted during the deletion. The reference integrity check algorithm used when deleting objects from the repository is uniform with the reference integrity check algorithm used when deleting objects from a configuration that is not bound to a repository. +This change is not implemented in 8.3.2 compatibility mode.The reference integrity check algorithm for configuration repository operations was not optimized. +The reference integrity check algorithm used when deleting objects from a repository was different from the reference integrity check algorithm used when deleting objects from a configuration that was not bound to a repository.Eliminated problems that occurred when deleting objects from configurations because of the reference integrity check differences. Storing deleted objects to the configuration repository is optimized.
Managed forms.
In the managed mode of the thick client, if the In list editing mode is selected for a configuration object, calling the OpenValue() method or clicking the Open button in the text input area opens the regular list form, provided that the following conditions are met:
  • The In list editing mode is selected.
  • A regular list form exists and it is selected as a default or additional one.
  • Using regular forms in the managed application is allowed in this applied solution.
  • The list or object managed form that is used as a default or additional one is missing.

In all other cases, this opens the object form.

This change is not implemented in 8.2.16 compatibility mode.

In the managed mode of the thick client, if the In list editing mode was selected, calling the OpenValue() method or clicking the Open button in the text input area opened the managed list form.To display configuration objects that have the In list editing mode set, or for editing their elements, the system opens the regular list form. This behavior is more consistent than before.
Development tools.
The following changes are implemented in the configuration comparison feature:
  • The parent node of predefined data elements is excluded from the comparison.
  • Missing help data is considered identical to empty help data.
  • Additional properties of the ManagedForm managed form element that make sense only in the 1C:Enterprise mode are excluded from the comparison.
When configurations were compared:
  • The node to which predefined data items were subordinate was included into the comparison.
  • Missing help data was considered different from empty help data.
  • Additional properties of the ManagedForm managed form element that make sense only in the 1C:Enterprise mode were included into the comparison.
The configuration comparison is perfomed as expected.
Managed forms.
When a choice list is generated for form fields linked to data of EnumRef type, it is based on the choice parameters and choice parameter links of the form element.

This change is not implemented in 8.3.2 compatibility mode.

When a choice list was generated for form fields linked to data of EnumRef type, the choice parameters and choice parameter links were not taken into account.The choice list generation for enumerations is uniform with other similar system features.
Internet-enabled functionality.
For the InternetMailProfile object, the SMTPAuthentication property (which is obsolete) is set to SMTPAuthenticationMode.Default.

This change is not implemented in version 8.2.16 compatibility mode.

For the InternetMailProfile object, the obsolete property SMTPAuthentication was set to SMTPAuthenticationMode.None.The default settings of the authentication method is the safest among those supported by the mail server.
Internet-enabled functionality.
If the SMTPSecureAuthenticationOnly property of the InternetMailProfile object is set to TRUE, authentication attempts are performed independently of other settings.

User authentication on the SMTP server is not performed in the following scenarios:

  • The SMTPUser property of the InternetMailProfile object is an empty string.
  • The SMTPAuthentication property of the InternetMailProfile object is set to SMTPAuthenticationMode.None.
  • The POP3BeforeSMTP property of the InternetMailProfile object is set to TRUE.

+

User authentication on the SMTP server was not performed if the name of the SMTP server user was not specified (the SMTPUser property of the InternetMailProfile object).User authentication on the SMTP server can be performed using a POP3 server if the SMTPSecureAuthenticationOnly property is not set. The value of the SMTPUser property of InternetMailProfile object does not affect this behavior. At the same time, the authentication is not performed if the mail server does not support the secure authentication methods.

When connecting to a mail server, you can exclude insecure authentication methods from the list of available ones.

Software licensing.
If a license acquisition dialog box appears at the start of the client application, the first page of the dialog box specifies which kind of license (server or client) the application requires. +A hyperlink to 1C:Licensing center contact information is displayed on the license registration pages and on the page that appears when license activation is not successful. A dialog box that displays 1C:Licensing center contact information is added. +When a user types a PIN code or a response from a licensing center operator in the license aсquisition dialog box, once they have completed a text field, the cursor moves to the next field automatically.

If a license acquisition dialog box appeared at the start of the client application, the first page of the dialog box did not specify which kind of license (server or client) was not found. +The license registration pages and the page that appeared when license activation was not successful only contained information how to find 1C:Licensing center contacts in the printed documentation. +When a user typed a PIN code or a response from a licensing center operator in the license aсquisition dialog box, the cursor did not move to the next field automatically.Improved usability of license acquisition dialog box.
Spreadsheet documents.
Web client.
The web client now supports text orientation in spreadsheet document cells.The web client did not support text orientation in spreadsheet document cells.Extended formatting capabilities for spreadsheet documents in the web client.
Server clusters.
When a cluster service is reassigned from one cluster manager to another, the service status is replicated to the new cluster manager and the service is shut down on the former cluster manager, which releases the resources used by the service. +The status is replicated for the following services: object locks, numbering, and background restructuring. +In the technological log, the <SRVC> event is implemented. It describes the following operations with cluster services: starting, stopping, and various alerts. Descriptions of operations being executed are generated in the Descr property. +Each cluster manager stores its session data in a dedicated directory. You can choose how a working process is selected when a new connection is created: by available performance or by available memory. If the selection is performed by available memory, either the working process that currently maintains connections to the infobase is used, or the working process that is running on the server and has the maximum amount of available memory. +In the cluster properties, the Load balancing mode property is implemented. For the IClusterInfo object, the LoadBalancingMode property is implemented. +For starting a background job, the working process that maintains the session that initiated the background job is selected with the highest priority (this rule is ignored if the selection is performed by available memory). +You can specify a priority for each assignment rule. If several identical assignment rules are found during assignment rule selection and all other conditions are equal, the rule with the highest priority is used. Assignment rules now have the Priority property. For the IAssignmentRule object, the Priority property is implemented. In the cluster mode of the server cluster administration utility (rac), the load-balancing-mode parameter is implemented for the create and update commands. Similar changes are implemented in the Java server administration API. +When determining available working process performance, the CPU load of the working server and the number of threads in the execution queue are taken into account, in addition to other factors.In some cases, used resources were not released after the reassignment of services. +The status was not replicated for the following services: object locks, numbering, and background restructuring. In the technological log, there were no events that described operations with cluster services. +Data belonging to all sessions was stored in a single directory, which could lead to access collisions. +When a background job was created, the working process for handling the job was always selected by available performance. +If several identical assignment rules were found during assignment rule selection, the rule that was applied could not always be determined unambiguously. +When available working process performance was determined, the CPU load and the number of threads in the execution queue were not taken into account.Increased fault tolerance of clusters. Improved quality and manageability of load balancing between cluster servers. A new setting ensures efficient memory usage when a cluster maintains a large number of infobases with a small number of sessions from each infobase.
Managed forms.
For unavailable groups, colors of the title and border (line) are changed.For unavailable groups, the title and border (line) had different colors.The look of unavailable groups is uniform with the look of other unavailable elements.
Applied objects.
Common attributes / Data separation.
Access rights.
Data exchange.
Mobile application.
Predefined data is available for configuration objects included in separator contents in the Independent and Shared mode. Predefined items can be linked to any data elements of matching type. The linking is optional. If data elements are not linked, the predefined data is considered empty. For configuration objects that can contain predefined data, the PredefinedDataName property is implemented. Support of predefined data items that refer to deleted predefined items is implemented. Identical references to predefined items are never generated, even for objects included in separator contents in the Independent mode, and even for items that belong to different areas. The GetPredefinedItemName() method is declared deprecated is only supported for compatibility purposes. Predefined data is registered in exchange plans like any other data. You can manage creation and update of predefined data in the infobase using the new configuration object property PredefinedDataUpdate and the new methods GetUpdatingPredefinedData() and SetPredefinedDataUpdate(). The global context method InitializePredefinedData() is implemented. Using this method, you can create data objects for predefined items that are not linked to any data (in the current data area). +Access rights and restrictions are specified simultaneously for the Predefined and PredefinedDataName fields. +These features are also implemented for the mobile platform. The new access rights InteractiveDeletePredefinedData, InteractiveSetDeletionMarkPredefinedData, InteractiveClearDeletionMarkPredefinedData, and InteractiveDeleteMarkedPredefinedData are implemented. They specify whether editing of predefined data is allowed.

Restrictions for editing predefined data in charts of accounts and charts of calculation types are eliminated. Predefined data can be marked for deletion, and it can be completely deleted. A chart of accounts must be included into the contents of all separators that contain all extra dimensions used in the chart. The infobase restructuring process is modified. This change is not implemented in 8.3.2 compatibility mode.

Predefined data was not available for configuration objects included in separator contents in the Independent and Shared mode. Predefined data could not be linked to any existing data object. Each predefined item had identical references in all data areas. During data exchange in a distributed infobase, predefined data was replicated only together with applied solution configuration changes. Creation and update of predefined data were not available.You can use predefined data in all separation modes. Predefined data management is more flexible than before.
Interface.
In the help topics, links to external resources are opened in the default web browser of the operating system.In the help topics, links to external resources were opened in the built-in web browser of 1C:Enterprise.Improved usability of viewing the resources that are opened by clicking links in the help topics.
Interface.
For new users, the interface mode is set to Forms in tabs, provided that the platform version compatibility mode is not used and the interface compatibility mode is set to Version82 or Version82TaxiAllowed.For new users, the interface mode was set to Forms in separate windows.The Forms in tabs interface is the default option for new users. This interface mode provides better usability.
Interface.
For a text box in a managed form table, the drop-down list is always opened at the start of editing.For a text box in a managed form table, the drop-down list was opened at the start of editing only if the editing was started using the mouse.Quick access to the drop-down list is implemented for text boxes located in managed form tables.
Common attributes / Data separation.
1C:Enterprise script.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state matches the state that the data area had when it was accessed for the first time. In particular:
  • Tables of enumerations are not modified.
  • If the version 8.3.2 or later compatibility mode is set, predefined data values revert to the values specified in Designer or to the default values. If the compatibility mode is disabled, predefined data items will be created on the first attempt to access them.
  • In the exchange plans, the values of ThisNode element attributes revert to the default values.
  • Values of nonseparated constants revert to the default values, while values of separated constants are deleted.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state did not match the state that the data area had when it was first accessed:
  • Tables of enumerations were removed.
  • For nonseparated objects, the predefined data values were saved.
  • In the exchange plans, the values of ThisNode element attributes were saved.
  • Constant values were preserved.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the state of the data area now reflects its initial state much better than it did in the previous platform versions.
Application appearance.
New splash screens are implemented for Designer, client application, Autorun program, and the installation program. +The splash screen size (and the size of the applied solution splash screen template) is 600 x 255 pixels.Splash screens that were used for various parts of the system had different looks. The size of the applied solution splash screen template was 305 x 110 pixels.The new splash screens better fit the new user unterface.
Managed forms.
When a value is entered or selected in a text box, it is converted to the text box value type, and then the value presentation is displayed in the text box. +This change is not implemented in 8.3.2 compatibility mode.When a value was entered or selected in a text box, the resulting text displayed in the box might not match the entered or selected value.The system behaves as expected. Eliminated incorrect system behavior.
Client application.
The message that is displayed before updating a client application using an insecure connection is clarified. The message was not clear enough.The message describes the situation more clearly.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Dumping/loading configurations to files.
Only access rights that have nondefault values are included in dump files. The default values are defined by the Set rights for new objects and Set rights for attributes and tabular sections by default properties. Values of these properties are default values for access rights to metadata objects and access rights to attributes and tabular sections respectively.All access rights were included in dump files, including those having default values.Improved performance of dumping configurations to files. Reduced size of dump files.
Dumping/loading configurations to files.
Applied objects.
When dumping a configuration to XML files, English descriptions of document journal selection types follow this convention: DocumentJournalSelection.DocumentJournalName.When dumping a configuration to XML files, English descriptions of document journal selection types followed this convention: DocumentJournalsManager.DocumentJournalName.Type names are uniform.
File operations.
When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right is checked for the attributes that store the file data. If the GetFiles() method is used and access to at least one the requested files is denied, the entire operation is canceled. +This change is not implemented in 8.3.2 compatibility mode. +

When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right was not checked for the attributes that stored the file data.

The behavior of the GetFile() and GetFiles() methods is uniform with other system features.
Development tools.
Before database configuration update, the check whether the Ref attribute is present is performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. If this attribute exists, restructuring cannot be performed. +This change is not implemented in 8.3.2 compatibility mode.Before database configuration update, the check whether the Ref attribute is present was not performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks.Eliminated this type of errors in applied solutions.
Server clusters.
In the server cluster administration utility (rac), the name and cluster-port options of the server update command are removed. In the Java-based administration server interface, the setName() and setClusterMainPort() methods are removed from the IWorkingServerInfo interface. +In the server cluster administration utility (rac), the security-level option of the infobase update command is removed. In the Java-based administration server interface, the setSecurityLevel() method is removed from the IInfoBaseInfo interface.In the server cluster administration utility (rac), the name and cluster-port options were available for the server update command. The values specified in these options were never used and no error messages were displayed when the command was run with these options.

In the Java-based administration server interface, the IWorkingServerInfo interface included the setName() and setClusterMainPort() methods. These methods did not perform any actions and there were no error messages when these methods were called.

In the server cluster administration utility (rac), the security-level option was available for the infobase update command. The value specified in this option was never used and no error messages were displayed when the command was run with this option.

In the Java-based administration server interface, the IInfoBaseInfo interface included the setSecurityLevel() method. This method did not perform any actions and there were no error messages when this method was called.

Options of the administration utility (rac) and the set of Java-based administration server interface methods match the set of actions that the system can actually perform. Working server parameters can be specified during the registration of the working server in the cluster. +The infobase security level can be specified while adding the infobase to the cluster.
Administration tools.
Server clusters.
The server cluster administration utility (rac) from the previous platform versions (8.3.1 and 8.3.2) cannot be connected to the administration server (ras) of the current platform version. +The server cluster administration utility (rac) from the current platform version cannot be connected to the administration server (ras) of the previous platform versions (8.3.1 and 8.3.2).The server cluster administration utility (rac) could be connected to the administration server (ras) of any platform version.The server cluster administration utility (rac) and the administration server (ras) that have incompatible versions cannot interact with each other.
File operations.
Linux.
You can get a file mask that describes all files for the operating system where 1C:Enterprise runs. The following methods are implemented: GetAllFilesMask(), GetClientAllFilesMask(), and GetServerAllFilesMask().This feature was not provided.You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs.
File operations.
Linux.
You can get a file path separator for the operating system where 1C:Enterprise runs. The following methods are implemented: GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator().This feature was not provided.You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs.
ZIP archive operations.
The behavior of the ZipFileWriter object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in a source directory:
  • If a file name does not contain wildcard characters (? or *), the file is added to the archive.
  • If a file name contains the wildcard characters (? or *), an exception is generated.

The behavior of the ZipFileReader object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in the directory containing the archive file, the archive is opened in the read-only mode. +This change is not implemented in 8.3.2 compatibility mode.

During the creation of an archive using the ZipFileWriter object, if the user under whose account the system was running did not have rights for viewing the list of files in the source directory, the files were not added to the archive and the resulting archive did not contain expected data. +The archive could not be opened using the ZipFileReader object if the user under whose account the system was running did not have rights for viewing the contents of the directory containing the archive file.The behavior of ZipFileWriter and ZipFileReader objects became more logical. Decreased chance of creating archive files with incorrect data.
Configuration repositories.
The compatibility mode with 1C:Enterprise versions 8.3.2 and earlier is implemented for the configuration repository. If the compatibility mode is disabled:
  • New configuration repository database structure is used.
  • The optimized method for interaction with configuration repository server is used.

If the compatibility mode is disabled, only 1C:Enterprise version 8.3.3 or later can be used to access the repository. +The command line option ConfigurationRepositoryClearCache is implemented in Designer. It is intended for clearing the local configuration cache. +The option to stop the execution of repository operations by pressing Ctrl+Break is implemented (this does not depend on repository compatibility mode).

A different configuration repository database structure was used. Some repository operations were performed inefficiently. +The Designer command line option ConfigurationRepositoryClearCache was not available. Pressing Ctrl+Break did not stop the execution of repository operations.Improved performance when accessing a configuration repository server.
Applied objects.
The Filter property of the parameter structure that is passed to the formal parameter of the GetChoiceData() method or the ChoiceDataGetProcessing handler can contain elements with values of ValueList and Array types. The system applies the In list comparison type to such values (it is the same comparison type that is used with FixedArray values).The Filter property of the parameter structure that is passed to the formal parameter of the GetChoiceData() method or the ChoiceDataGetProcessing handler could not contain elements with values of ValueList and Array types.Extended filtering options when retrieving selection data. Removed unnecessary data conversions.
Background and scheduled jobs.
Background and scheduled jobs can now run in the file mode without using the ProcessJobs() global context method. The ProcessJobs() method does not perform any actions. Background and scheduled jobs are executed in one of the client applications connected to the infobase. The behavior of background and scheduled jobs has some specifics (see the full list in the documentation):
  • All scheduled jobs are executed in a dedicated client application (by default, it is the first session started).
  • A background job started by a session is executed by the client application that started it.
  • Within a client application, a single background job is performed at a time (this includes scheduled jobs).

For specifying the client application that will execute scheduled jobs, the AllowExecuteScheduledJobs command-line option is implemented for the client application. The Background jobs check box, which is located in the Autoattach dialog box in Designer, affects the attachment to background jobs both at server and at client.

This change is not implemented in 8.3.2 compatibility mode.

The only way to run background and scheduled jobs in the file mode involved using the ProcessJobs() global context method.

The Background jobs check box, which is located in the Autoattach dialog box in Designer, only affected attachment to background jobs at server.

Reduced developer efforts during implementation of background and scheduled job execution in the file mode.
Applied objects.
Common attributes / Data separation.
In order to successfully read or write separated constants using the Constants method of the global context, values of all shared separators that split the constant must be specified. Otherwise an exception is generated. +This change is not implemented in 8.3.2 compatibility mode.Reading or writing separated constants using the Constants method of the global context was performed successfully even when values of all combined separators that split the constant were not specified.The feature is uniform with other similar platform features.
Linux.
The config_system configuration utility for Linux is removed from the distribution kit. +The search for MS Core Fonts required by the platform is performed automatically in the following directories:
  • /usr/share/fonts/truetype/msttfcorefonts
  • /usr/share/fonts/msttfcorefonts
  • $HOME/.fonts

The system automatically searches for required dynamic libraries when functions from these libraries are used. +If the required font or dynamic library is not found, an error message is displayed. +The operating system setup instructions for Linux are provided in the documentation.

The config_system configuration utility for Linux was included in the distribution kit. If required fonts or dynamic libraries were missing, this was not detected directly and could lead to various errors or unexpected behavior. The operating system setup instructions for running 1C:Enterprise on Linux were not provided in the documentation.Simplified operating system for running 1C:Enterprise on Linux. Improved issue diagnostics.
Access rights.
Queries.
Accumulation registers.
Accounting registers.
Access rights for autogenerated period fields (YearPeriod, HalfYearPeriod, QuarterPeriod, MonthPeriod, TenDaysPeriod, DayPeriod, HourPeriod, and SecondPeriod) in virtual tables of accumulation and accounting registers are obtained from the corresponding access rights of the standard Period attribute.

This change is not implemented in 8.3.2 compatibility mode.

Access rights for autogenerated period fields in virtual tables of accumulation and accounting registers depended on the state of the Set rights for attributes and tabular sections by default check box. If the property was set to True, the user was granted the right.Access right management is more consistent.
Development methodology.
The documentation includes a section with recommendations for developing cross-platform applied solutions.The documentation did not include recommendations for developing cross-platform applied solutions.Recommendations for creating the cross-platform applied solutions at minimal costs are available.
Managed locks.
Managed transaction locks can be set by object attributes. For specifying attributes whose values are taken into account when setting transaction locks, the DataLockFields property is implemented for the following configuration objects:
  • Catalogs
  • Documents
  • Charts of characteristic types
  • Charts of calculation types
  • Business processes
  • Tasks
  • Charts of accounts
  • Exchange plans

While objects are being written or deleted, they will be temporarily locked by all attributes specified in the DataLockFields property and the Ref field. For objects being written, attribute values available at the beginning of the writing process are used. For objects being deleted, current attribute values are used.

This change is not implemented in 8.3.2 compatibility mode.

Managed locks for the following objects could be set only by the standard attribute Ref: catalog, document, chart of characteristic types, charts of calculation types, business process, task, chart of accounts, and exchange plan.Extended managed lock functionality. When you need to perform a coordinated action on a set of objects filtered by a specific attribute and at the same time prohibit the creation of new objects that match the filter, you have the option to set a lock by the attribute, rather than lock the entire set of objects of the given type.
Managed locks.
Using the DataLock object outside of a transaction or in the automatic data lock control mode raises an exception.

This change is not implemented in 8.3.2 compatibility mode.

Using the DataLock object outside of a transaction or in the automatic data lock control mode did not raise an exception and did not lead to any locks.Situations when the system seemed to work properly but actually did not perform any actions are eliminated.
Client application installation.
Administration tools.
You can specify whether the latest 1C:Enterprise updates are installed automatically. This is configured using the following new parameters:
  • The AppAutoInstallLastVersion command-line option of the non-interactive startup utility.
  • The AppAutoInstallLastVersion parameter in the 1CEStart.cfg and 1CESCmng.cfg configuration files.

When the client application version does not match the 1C:Enterprise server version, or when a specific 1C:Enterprise version is required to access an infobase, the new version is always installed unless the required version is already present at the client computer. The Install new application versions automatically check box is added to the infobase startup settings dialog box.

The non-interactive startup utility installed the latest 1C:Enterprise version, except the following scenarios:
  • In the startup utility configuration dialog box, a specific 1C:Enterprise version is selected for all infobases.
  • A specific version of the client application or interactive startup utility is started.
In the non-interactive startup utility, you have the option to disable the search and installation of the latest 1C:Enterprise version in the event when the required version is already installed at the client computer, but later versions are available and not yet installed. You still have the option to install any 1C:Enterprise version that you need.
Development tools.
During the database configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library is performed. If matches are found, the message informing that the names are not unique is displayed and the database configuration is not updated. +This change is not implemented in 8.3.2 compatibility mode.During the configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library was not performed.The following scenario is no longer possible: when a common picture name matches a picture name from the picture library, in 1C:Enterprise mode the picture from the library is displayed instead of the common picture.
Managed forms.
The Close() method called on an additional form closes this form. If this form is active, the default form is made active, otherwise no additional actions are performed. +The IsOpen() method called on an additional form that is open returns True. If the user switched to another additional or default form after opening the additional form, the IsOpen() method still returns True.If the Close() method was called on an additional form, an error was generated and the form was not closed. +The IsOpen() method called on an additional form that was open returned False.The system behaves as expected.
XML and XDTO support.
During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the Can be empty property (the nillable attribute of the XSD schema) is set to True, otherwise the property value is not set.

If you specify the Any ref type for an attribute (such as a resource or dimension) in Designer, the type is converted into one of the following in the configuration data model:

  • The {http://v8.1c.ru/8.1/data/enterprise}AnyRef type if the configuration includes multiple metadata objects that form the Any ref type.
  • The type that corresponds to reference data type if the configuration includes a single metadata object that forms the Any ref type.

This change is not implemented in 8.3.2 compatibility mode.

During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the value of the Can be empty property (the nillable attribute of the XSD schema) was never set.

If you specified the Any ref type for an attribute (such as a resource or dimension) in Designer, it was always converted to the {http://v8.1c.ru/8.1/data/enterprise}AnyRef type in the configuration data model.

The XML data model generation for the Any ref type is uniform with other types.
Full-text search.
Full-text search indexes include the number of 1C:Enterprise version that was used to create them. If the full-text search index is created in version 8.3.3 or later while the compatibility mode is disabled, and then the infobase is accessed using version 8.3.2 or earlier, the search by presentations of configuration objects is not performed.Full-text search indexes did not include the number of 1C:Enterprise version that was used to create them.Reverse compatibility of full-text search indexes is implemented. The full-text search indexes are now compatible with earlier 1C:Enterprise versions that have different index format.
Web services.
Web links.
You can specify proxy server parameters in constructors of the WSProxy and WSDefinitions objects and in the CreateWSProxy() method.

The former constructor and method syntax is supported for compatibility purposes.

Proxy server parameters could not be specified when WSProxy or WSDefinitions objects were created or when the CreateWSProxy() method was called. The proxy server settings could be specified only by editing the inetcfg.xml configuration file.Extended web service support functionality: the proxy server settings can be specified in the configuration settings rather than by editing the configuration file.
Functional options.
If the privileged get mode is set for a functional option, getting the functional option value in the safe mode does not require checking the access rights. +This change is not implemented in 8.3.2 compatibility mode.If the privileged get mode was set for a functional option, getting the functional option value in the safe mode included checking the access rights. Eliminated the issues related to accessing functional options in the safe mode. The data provided by a functional option that has privileged get mode set is considered safe enough and can be retrieved in the safe mode.
Automated testing.
If an object being tested cannot perform the required action, an exception is raised (except methods that search for objects, which never raise this kind of exception).It was impossible to detect situations when objects being tested could not perform the required actions. Better error detection during automated testing.
Automated testing.
Methods that perform actions on objects being tested do not wait for action completion. Methods that previously returned the execution results now raise exceptions when the actions cannot be performed.Methods that performed actions on objects being tested waited for action completion. In some cases such methods returned result codes.Better error detection during automated testing.
Managed forms.
For managed form fields, the DropListButton property is implemented. It describes whether the button that opens the drop-down list is present. Depending on the type of the attribute linked to the text box, the list can contain the following data:
  • Choice list - from the choice list property of the text box.
  • Quick choice list - for the quick choice property of the configuration object.
  • Choice values – values matching the text entered by the user.
  • Choice history - for reference fields and enumeration fields. Note that the history is not available for fields that contain configuration objects with the quick choice option enabled.

During the text input in a text box, the platform displays unique items from all these lists (if they are available for the text box). +For managed form fields, the ChoiceButtonRepresentation property is implemented. It describes whether the button that opens the choice form is present in the field. +The DropListButton property of managed form fields is no longer available; it is left for compatibility purposes. The StartListChoice event of text box objects is never called. +This change is not implemented in 8.3.2 compatibility mode.

The DropListButton property was available for managed form fields. When a user started selecting an item from the list, the the StartListChoice event was generated. Developers could not control whether the choice form could be opened from the choice list.The choice list is designed to allow users to select values quickly, without opening the choice form, whenever possible. For that, the choice list contains data that helps users to select a value for a text box:
  • History of choices in the fields of the given type (with the given parameters)
  • Choice values
  • Quick choice list, and so on
Web client.
In the web client for iPad, only the Forms in tabs mode without modal windows and the Taxi interface are supported. The webclientmode command-line parameter is no longer supported. Standard gestures for zooming in and out are now supported. +Form items with content that can be scrolled have scroll bars.In the web client for iPad, modal windows were supported with some limitations, and the Forms in tabs mode was not supported. The webclientmode command-line parameter was supported. Standard gestures for zooming in and out were not supported. Form items never had scroll bars.Configuration tuning is no longer required to run applications on iPad (provided that you switch to the mode that does not use modal windows). In earlier versions of the platform, the developer had to remove a part of functionality to make an application compatible with iPad because modal calls were supported with limitations.
Managed forms.
Command interface.
Enhanced window blocking technology introduces innovative approach to window modality. Blocking windows are used instead of modal windows, while modal windows are supported for compatibility purposes. +It is recommended that you replace all modal windows with blocking windows in your applied solutions, and use new platform methods that do not create modal windows. +A call of a modal form is broken down into one or more separate calls: the first call opens a blocking form instead of a modal one and the the other one contains a callback procedure that is called by the platform when a form operation is complete (it includes getting the return value). +Applied solutions designed for iPad must support the blocking windows technology. +The ModalityUseMode configuration property is implemented, it defines the modal window usage mode. In the extended configuration check, the search for methods related to modal windows is implemented. You can also perform this check from the command line by using the CheckUseModality option of the ExtendedModulesCheck command-line parameter. +The NotifyDescription object is implemented, it passes the callback procedure description to platform methods that open blocking windows. The global context method ExecuteNotifyProcessing() is implemented. +For the FormWindowOpeningMode system enumeration, the LockWholeInterface value is implemented. +For managed forms, command interface commands, and common modules, the ThisObject property is implemented. This property is not supported in version 8.3.2 compatibility mode. +The global context method OpenForm() is modified. +The following global context methods are implemented: ShowQueryBox(), ShowValue(), ShowMessageBox(), ShowInputDate(), ShowInputValue(), ShowInputString(), ShowInputNumber(), BeginInstallAddIn(), BeginInstallFileSystemExtension(), BeginInstallCryptoExtension(), and BeginPutFile(). +For objects StandardPeriodEditDialog, FormatStringWizard, FontChooseDialog, ColorChooseDialog, and ScheduledJobDialog the Show() method is implemented. For the DataCompositionDetailsProcess object, the ShowChooseAction() method is implemented. +For the ValueList object, the methods ShowCheckItems() and ShowChooseItem() are implemented. +For the ManagedForm object, the Open() method is modified, and the methods ShowChooseFromMenu() and ShowChooseFromList() are implemented. +For the ManagedForm object, the OnCloseNotifyDescription property is implemented. +The ThisForm property of the ManagedForm object is removed but supported for compatibility purposes. +The system enumeration value PostingModeUse.Ask is supported for managed forms only in version 8.3.2 compatibility mode.In the web client on iPad, the modal window support was limited, while modal windows were widely used in applied solutions and in the system part of the interfaces.The web client meets the modern web technology standards. Removed limitations on modal window usage in the web client on iPad. +Configuration modification is required for applied solutions intended to run in the web client on iPad.
Technological log.
The resolution of the event time output to the technological log is increased to 1 microsecond. The count of microseconds in technological log event time has six digits. +The DurationUs property is implemented. It contains the event duration measured in microseconds. For compatibility purposes, filtering by Duration properties is supported.The resolution of the event time output to the technological log was equal to 100 microseconds. The count of microseconds in the technological log had four digits. +Only the Duration property was available in the technological log. It contained the event duration measured in hundreds of microseconds.Decreased chance of the time counter overflow that occurred when the count of technological log events exceeded 10 000 events per second. One second can now contain up to 1 000 000 events of the technological log. +It is recommended that you use the DurationUs property instead of the Duration property.
Web client.
System requirements.
The following browsers are no longer supported:
  • Microsoft Internet Explorer version 7.0;
  • Safari for Windows;
  • Mozilla Firefox version 16 and earlier for Windows and Linux.
The following browsers were supported:
  • Microsoft Internet Explorer version 7.0;
  • Safari for Windows;
  • Mozilla Firefox version 16 and earlier for Windows and Linux.
Improved web client stability because rarely used browsers with errors and non-standard behavior are no longer supported.
Linux.
The platform supports XBase objects on 64-bit Linux operating systemsThe platform did not support XBase objects on 64-bit Linux operating systemsOperations with .dbf files are now available on all supported architectures, except the mobile platform.
Dynamic lists.
The DataVersion field is removed from the list of available fields of dynamic list settings.The DataVersion field was included in the list of available fields of dynamic list settings.The field that was erroneously added to the list of available fields of dynamic list settings is now removed from the list.
Access rights.
Managed forms only display data retrieved using "." (dot) if the user has access rights for all parts of the full path to the data. +If they do not have the rights, the item linked to this data is not displayed on the form.If a user did not have access rights for all parts of the full path to data retrieved using "." (dot), the item linked to the data was displayed in the form, but it did not contain any data.When accessing data using "." (dot), the form item linked to the data is not displayed on the form if the user does not have access rights for all parts of the full path to the data.
Administration tools.
In the Java API for server administration, the value of the RuleType property of the AssignmentRuleInfo object matches the value of the RuleType property of the IAssignmentRule object in the server cluster administration tools that use COM connection.The values of the RuleType properties differed in the Java API for server administration and in the server administration tools that used COM connection.The server cluster administration tools are unified.
Internet-enabled functionality.
The OpenID pass-through authentication protocol implementation is revised. The implementation complies with the Direct Identity version 2.0 mode of the OpenID protocol. +The format of the OpenID provider address in the default.vrd file is modified (the url attribute of the rely item): httрs://<address of the OpenID provider infobase>/e1cib/oid2op. The default authentication lifetime is 24 hours. The maximum authentication lifetime is 168 hours. +The protocol for interaction between the relying party and the OpenID provider is modified. +In the authentication dialog box, you can disable storing authentication data. +For the web client, a dialog box for entering the user name and password at the OpenID provider side is implemented.The protocol implementation did not fully comply with the Direct Identity version 2.0 mode of the OpenID authentication protocol. The OpenID provider address in the default.vrd file was as follows: httрs://<address of the OpenID provider infobase>/e1cib/oida. The default authentication lifetime was 1 week. The maximum authentication lifetime was not limited. In the web client, there was no dialog box for entering the user name and password at the OpenID provider side. The OpenID pass-through authentication protocol complies with the specification.
Add-ins.
Web client.
The add-in technology now supports Mozilla Firefox browser version 22.0 and later. You can use add-in adapters for Mozilla Firefox 22.0 in the later versions of the web browser without recompiling the adapters.

For add-ins intended for use with all supported Mozilla Firefox versions, you have to add several add-in versions to the archive:

  • For Mozilla Firefox version 18.0 or earlier
  • For Mozilla Firefox versions 19.0 to 21.0
  • For Mozilla Firefox version 22.0 or later

It is recommended that you specify only the minimum version of the web browser in the add-in manifest file.

Documentation on creating add-ins is updated (read more). Examples are added, new versions of adapters for web browsers.

Adapters for Mozilla Firefox versions that are no longer supported by the developer (versions 3.6, 4.0, and 5.0) are removed.

The add-in technology did not support Mozilla Firefox browser version 22.0 or later.The add-in technology now supports new versions of Mozilla Firefox browser (version 22.0 or later).
Managed forms.
Full-text search.
When a choice list is generated for the "input by string" feature (for reference configuration objects), the following options are available:
  • Full-text search
  • Search by substring or by the beginning of the string
  • Instant or background search

You can specify each of these options in Designer, in the configuration object properties. +The full-text search is performed only among the configuration object attributes that are selected in the "input by string" options of the configuration object. If a filter is applied during the input by string, the filter is converted (whenever possible) to a full-text search query in order to increase the search performance.

For external data source tables, you can only select the search modes (by substring or by beginning of the string, and instant or background). +In the file mode, the background search can be performed only when any other background or scheduled job is not being executed. +For the AutoComplete and TextEditEnd event handlers, the formal option Parameters is implemented. It contains settings for getting choice data and allows you to manage this process by changing the properties of the structure that is passed in this parameter.

The following options were not available in the "input by string" feature:
  • Full-text search
  • Search by substring or by the beginning of the string
  • Instant or background search

The full-text search and search by substring were available in ChoiceDataGetProcessing handlers.

New standard options for the "input by string" feature in text boxes:
  • Full-text search
  • Search by substring (as an alternative to the search by the beginning of the string)
  • Background search (the search is running while the user is typing the search string)

Table of contents

Renamed objects

ObjectThe old nameThe new name
The name of calculating register recalculation manager type is changed. +This change is not implemented in version 8.3.2 compatibility mode.CalculationRegisterRecalcs.<Calculation register name> +RecalculationManager.<Calculation register name> +
English names of the following script objects are changed:
  • External data source table record (ExternalDataSourceTableRecord);
  • External data source record set (ExternalDataSourceTableRecordSet).

This change is not implemented in 8.3.2 compatibility mode.

  • ExternalDataSourceRecord;
  • ExternalDataSourceRecordSet.

  • ExternalDataSourceTableRecord;
  • ExternalDataSourceTableRecordSet.

For turnovers accumulation register managers and for accounting register managers, the methods for setting and getting the totals period are renamed. For compatibility purposes, the previous names are supported.
  • GetTotalsPeriod()
  • SetTotalsPeriod()
  • GetMaxTotalsPeriod()
  • SetMaxTotalsPeriod()
For objects that describe form elements being tested, the name of the property that contains the element title is changed.

+

  • Title
  • TitleText

The names of the UsualGroupRepresentation system enumeration items are changed. For compatibility purposes, the previous names are supported.

  • Line
  • Margin
  • GroupBox
  • WeakSeparation
  • NormalSeparation
  • StrongSeparation
The names of the methods for getting and setting the client application window caption are changed. For compatibility purposes, the previous names are supported.

+

  • GetApplicationCaption
  • SetApplicationCaption
  • GetClientApplicationCaption
  • SetClientApplicationCaption
The name of the configuration property that describes the desktop command interface is changed.

+

  • DesktopCommandInterface
  • MainSectionCommandInterface
The name of configuration property that describes the desktop workspace (the starting page) is changed.
  • DesktopWorkingArea
  • StartPageWorkingArea
The names of settings that store start page (desktop) parameters. +In version 8.3.2 compatibility mode, use the old names. When the compatibility mode is changed, the saved settings keys are changed as well.
  • Common/DesktopSettings
  • Desktop/NavigationPanel/CommandInterfaceSettings
  • Desktop/ActionsPanel/CommandInterfaceSettings +
  • Common/StartPageSettings
  • MainSection/NavigationPanel/CommandInterfaceSettings
  • MainSection/ActionsPanel/CommandInterfaceSettings.
The name of the type that describes the object containing start page (desktop) settings is changed. For compatibility purposes, the previous name is supported.
  • DesktopSettings
  • StartPageSettings
The Russian name of the TestedFormField object method, which ends the editing of the current area, is changed.
  • ЗавершитьРедактированиеТекущейОбласти()
  • ЗакончитьРедактированиеТекущейОбласти()

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
System requirements.
For iOs-based devices, the iOS version 4.x is not supported. The minimum iOS version is 5.1.

For Android-based devices, the minimum RAM size is 256 MB.

iOS version 4.x was supported.

Android-based devices required 100 MB of RAM to run 1C:Enterprise.

System requirements for the mobile platform are revised.
Managed forms.
In the mobile application, the extended tooltop can be used, except the Balloon option.Extended tooltips were not available in mobile applications.On the mobile platform, you can create tooltips for form elements using a variety of tooltip design options.
Common objects.
Geolocation functions and multimedia tools (photos, audio- and videorecording) provided by mobile devices are available in mobile applications.

The following geolocation functions are implemented: GeographicCoordinates, LocationData, LocationProviderInformation, LocationTools, AddressData. The LocationTools global context property is implemented. Global context methods GetAddressByLocation(), GetLocationByAddress(), and ShowOnMap() are implemented. The GeographicalSchemaCoordinates type is renamed to GeographicCoordinatesp; it is used in geolocation functions. The GeographicalSchemaCoordinates type name is supported for compatibility purposes.

The MultimediaData and MultimediaTools objects are implemented to support processing multimedia features. The MultimediaTools global context property is implemented.

These features were not provided.Geolocation and multimedia functions of mobile device perating systems are now available in the mobile platform. You can add features for defining the current location, making photos of incoming items, and so on.
Development tools.
The configuration check verifies whether the conifiguration language code meets the ISO standard. It is recommended that you use ISO-compliant language codes.The language codes were not checked for compliance with ISO standard.Reduced chance of incorrect mobile platform language selection based on the mobile device language.
1C:Enterprise script.
Common modules that reuse returned values are now supportedThis feature was not provided.On the mobile platform, you can optimize getting the same data multiple times during a single session or a single server call.
Predefined data.
While a mobile application is being updated, metadata objects are compared by their internal identifiers. +When a mobile application is updated to version 8.3.3, the corresponding restructuring is performed. While a mobile application was being updated, metadata objects were compared by their names.You can rename metadata objects while preserving the object data.
Data display.
The mobile platform picture format is replaced by the format that supports several screen resolutions of mobile devices.All mobile platform pictures had the same resolution.The sizes of system pictures displayed on mobile device screens depend on the screen resolutions.
Backups.
When an infobase is created on iOS-based devices, the directory containing the application data is marked as excluded from the backup. When the infobase data is modified (object form extension data and register data is recorded), the directory with application data is marked for backup and the backup is initiated using the system tools.On iOS-based devices, the infobase directory was marked for backup since it was created.The application behavior meets the requirements of the Apple company to user data backup.
Spreadsheet documents.
On the mobile platform, resolved issues with displaying spreadsheet documents that have a large number of rows and columns.In some cases displaying a spreadsheet document with a large number of rows and columns on the mobile platform led to an unexpected shutdown.Improved mobile platform stability when processing large spreadsheet documents.
Internet-enabled functionality.
For the mobile platform, the HTML-document field is implemented. The HTML-document field has the following specifics:
  • The Document and Output properties are not supported.
  • The OnClick event is fired only during the attempt to switch to a new page. At this time, all properties of the EventData parameter except Href contain the UNDEFINED value. The Href property contains the address of the new page.
The HTML-document field was not supported on the mobile platform.In mobile applications, displaying HTML pages in forms is implemented. For example, you can create a manual for your configuration.
Interface.
On mobile devices with Android OS, you can change the order of items in the list of applications.On mobile devices with Android OS, changing the order of items in the list of applications was not available.Improved usability of the list of applications. User can arrange applications in any order.
Data composition system.
Processing data composition system details on the mobile platform is implemented (this includes opening values and remote processing of the details). For mobile platform, the DataCompositionDetailsID object is implemented.On the mobile platform, reports that contained data composition system details could not be opened.On the mobile platform, reports can be generated using the data composition system. Report that contains details can be opened on the mobile platform.
Mobile application development.
In the Mobile application creation wizard data processor, you can specify a key for Google Maps. +You can also specify a logo for screen resolution 950×1136 (iPhone 5 screen) in this data processor.These features were not provided.You can use the Mobile application creation wizard data processor for creating mobile applications that utilize new mobile platform features (geocoding support). Support of iOS-based devices was improved as well.
Internet-enabled functionality.
For the objects HTTPConnection, WSProxy, WSDefinitions, and InternetMailProfile, and for the CreateWSProxy() method, the option to set a timeout for interaction with a network resource is implemented. +User names and passwords that are passed to WSProxy, WSDefinitions, and HTTPConnection +objects can contain special characters, except ":". +You can encode (the EncodeString() method) and decode (the DecodeString() method) custom text strings for using them in URLs. Encoding is performed in compliance with the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt). +You can process HTTP request headers and return codes, as well as get and set request bodies as strings or binary data. The HTTPRequest and HTTPResponse objects are implemented.

This functionality is similar to the PC-based platform functionality. +

This feature was not provided on the mobile platform.On the mobile plaform, the following features are available:
  • Setting timeouts for interaction with network resources
  • Using characters that do not belong to the ASCII character set in user names and passwords
  • Generating URLs and getting values from them according to the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt) when custom text is added to a URL
  • Generating HTTP requests, processing responses, and interacting with REST services from 1C:Enterprise script
1C:Enterprise script.
The CurrentUniversalDateInMilliseconds() function is implemented. It gets the number of milliseconds that passed since January 1, year 0001, 0:00:00 UTC.

The attempt to assign a value to a fixed structure item raises an exception. +In value tables, serialization of index descriptions is implemented. The index contents are not serialized but restored during deserialization. +The hash function value can be calculated based on MD5 and CRC32 algorithms using the DataHashing object. +This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform, you can do the following:
  • Measure time intervals more precisely. For example, this can be handy for getting the duration of a specific action.
  • Use fixed structures in a similar way to other fixed collections.
  • Restore the value table state in more detail during its deserialization.
  • Quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.
Managed forms.
When specifying values of managed form fields or tables, you can specify data stored in a specific row of a form attribute that is a table (but not a dynamic list). +Data belonging to dynamic lists that are currently not displayed on a managed form is not read during the operations that involve the managed form. +For attributes of String type that have fixed length and are located in managed form tables, table boxes, or spreadsheet documents, the appearance of the mark that indicates that the field must be filled is modified. +The following style fonts are implemented: SmallTextFont, LargeTextFont, and ExtraLargeTextFont. For the Font type, the Scale property is implemented. It defines increase or decrease of the font relative to the initial size. +For groups of "usual group" or "page" type, you can set the background color of form group extensions using the BackColor property. +The URLProcessing handler is implemented for the Label form field, Decoration form field of Label type, and managed form. The handler is called when a user clicks a formatted string with a hyperlink in a field. +Extended appearance customization options for form fields of label type and decorations of label type. +In usual groups with limited width, the size of managed form buttons can vary depending on the width, which is similar to the behavior of other form items in a group with limited width. +This functionality is similar to the PC-based platform functionality.This feature was not provided on the mobile platform.On the mobile platform, you can do the following:
  • Edit data stored in specific rows of form table data in separate fields.
  • Get fast access to managed forms with dynamic lists located on different pages.
  • Ensure that the behavior of the mark that indicates that the field must be filled is the same for all attribute types.
  • Specify font size in a form relative to the form base font, without using absolute font size values.
  • Improve form usability by highlighting group colors.
  • Create a handler for each hyperlink represented as a formatted string.
  • Use more appearance customization options in managed forms.

When the size of a usual group is limited, the algorithm used for resizing group items is the same for all item types.

Applied objects.
User presentations are implemented for database objects of the following types: Catalog, Document, and ExchangePlan. +In document journals, the attribute containing the document number has fixed length if all documents included in the journal have the number field of String type with fixed length. Otherwise, the journal attribute has variable length. +A value obtained from an unfilled table attribute, value tree, or tabular section is equal to the default value of the column attribute type, with the type qualifier taken into account. +This functionality is similar to the PC-based platform functionality.This feature was not provided on the mobile platform.On the mobile platform, you can do the following:
  • Get nonstandard data presentations in various scenarios.
  • Get document numbers in a uniform way, regardless of the method used to obtain the document numbers: either from the document itself or from the document journal.
  • Generate default values in the same way as they are generated on the PC-based platform.
Command interface.
In the information register record form, if the OnlyInActions property of the Copy command has the Auto value, the system behavior is changed. This value now means that the command is located in the More (or All actions) menu only.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform, you can specify the same default location for the Copy command in information register records set forms and in the item forms.
Charts.
New types of charts are implemented:
  • Funnel
  • 3D funnel
  • Normalized funnel
  • 3D normalized funnel

The antialiasing mode is implemented for charts.

You can connect series of charts to each other.

The semitransparency mode is implemented for charts.

The Indicator property is implemented for the tape graph chart.

This functionality is similar to the PC-based platform functionality. +

This feature was not provided on the mobile platform.Extended chart features on the mobile platform.
Information registers.
For periodic information registers, the totals for getting first and last slices are implemented.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform, you can get first and last slices, which represent data as of the last (current) moment in time, much faster.
Spreadsheet documents.
If a fixed area is larger than the displayed area, the spreadsheet document does not use the fixation.

The algorithm for horisontal cell placement in different rows is modified.

This functionality is similar to the PC-based platform functionality. +

This feature was not provided on the mobile platform.On the mobile platform you can:
  • Improve usability of reports that contain areas with left or top fixation.
  • Improve usability of spreadsheet documents.
XML and XDTO support.
If a message to a user contains characters incompatible with XML format (in the thick or thin client), the error XML text contains invalid characters in X position is generated.

This functionality is similar to the PC-based platform functionality. +

This feature was not provided on the mobile platform.The processing of characters that are incompatible with XML format on the mobile platform is uniform with processing them on the PC-based platform.
Data display.
Formatted strings are available (the FormattedString type).

You can use a formatted string as:

  • Data for the "label field" form items
  • Title for form items of decoration type
  • MessageText parameter of the DoMessageBox() method
  • QueryText parameter of the DoQueryBox() method

+

This feature was not provided on the mobile platform.On the mobile platform, the text presentation capabilities are improved.
XML and XDTO support.
During the import of XSD schema, if the target namespace definition is missing in the schema, a diagnostic message is displayed.During the import of XSD schema, when any problems occurred while loading the XSD schema, a diagnostic message was not displayed.Improved diagnostics during XSD schema import.
Managed forms.
Command interface.
Common objects.
You can specify the Arbitrary type for a subordinate attribute of a managed form attribute (for example, a value table column or a value tree column). +For managed forms, the URL and AutoURL properties are implemented. You can use the URL property to get a link to the main form of the object. +For the GetForm(), OpenForm(), and OpenFormModal() methods, the URL parameter is implemented. Its value is assigned to the URL property of a form when the form is obtained or opened. +Navigation links to lists are implemented. For a form whose main attribute is a dynamic list with a main table specified, the navigation link points to the list of the object specified as the main table. Following the link opens the main form of the list. +You can use navigation links to global command interface commands. +The format of navigation links to navigation points generated by standard commands is modified. +Changes made to a table of totals storage settings for accumulation registers are applied within a transaction. +Values of the ReadOnly and Protection properties are preserved when a spreadsheet document is passed between the client and the server. +For the NumberInWords() global context method, the AU formatting option is implemented.

The TextReader and TextWriter objects are implemented. +This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.Some mobile platform features are now uniform with PC-based platform.
Mobile application.
The mobile platform supports all of the interface languages that are supported in the PC-based platform. The mobile platform delivery that supports only English and Russian interface languages is also available.

The content of the mobile platform distribution kit is modified.

The mobile platform supported English and Russian interface languages only.The system part of the mobile platform interface supports more languages than before.
Development tools.
If the Use purposes configuration property is set to Mobile device only, other configuration settings are changed automatically:
  • The Modality usage mode property is set to Use.
  • The Interface compatibility mode is set to Version 8.2.
If the Use purposes configuration property was set to Mobile device only, other configuration properties were not changed automatically.For configurations being developed for mobile platform only, eliminated the chance to save configuration property values that are incompatible with mobile platform limitations.

Table of contents

Transition from the version 8.2 to the version 8.3.3

Table of contents

Transition from the previous version to version 8.3.3

Table of contents

Version 8.3.2

Version 8.3.2 includes known bug fixes and functionality modifications.

New functions and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.3.1 is added to the list of available values of the Compatibility mode property.Compatibility modes were available for the following platform versions: 8.1, 8.2.13, and 8.2.16.In version 8.3.2 you can run configurations created in version 8.3.1 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.2 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.1 for working with the infobase even after the transition to version 8.3.2. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Development tools.
Automated configuration testing is implemented for managed applications. The testing is written in 1C:Enterprise script (using the appropriate script objects); it emulates a sequence of interactive actions and checks the results of their execution.

Automated testing is supported for thin, thick, and web clients, both in file and client/server modes.

The test does not require making any changes in the configuration being tested.

Implemented the option of recording interactive user actions in a managed application for later use in a 1C:Enterprise script-based scenario, which reproduces the actions (http://its.1c.ru/db/metod81#content:5014:1).

This feature was not provided.Better development quality can be achieved due to automated testing of the applied solution interface.
Development tools.
Applied objects.
Implemented XDTO serialization for pivot charts. Templates of spreadsheet documents that contain pivot charts can be dumpled to XML files. +This feature was not provided.All configuration objects can be dumped to files. +
Mobile application.
Mobile application development is supported, with target operating systems iOS and Android. Applications can run on mobile devices in the offline mode; permanent Internet connection is not required. Application data exchange through the Internet can be implemented using standard 1C:Enterprise tools. The development is performed in Designer; the managed application development model is used. The subset of functionality used for PC application development is supported.

The resulting applications can run both on PC and mobile devices.

This feature was not provided.

Mobile application development was only supported in the mobile extension for handheld devices (and only for Microsoft Windows Mobile and Microsoft Windows CE operating systems).

You can develop applications for devices with iOS and Android operating systems using 1C:Enterprise platform tools. Data exchange between mobile applications and PC applications is available.

Table of contents

New functions and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Client application.
If an error that leads to system shutdown occurs, the error text is displayed in the technical support information window.In some cases the error that led to system shutdown was not displayed in the technical support information window.Improved usability of information for technical support. +

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Applied objects.
Reduced verification and repair time for document journals.For large journals the "Verify and Repair" operation might take significant time.Reduced time of the "Verify and Repair" operation for document journals. +
Development tools.
Optimised memory usage when comparing configurations and updating modified configurations.Comparison and merging of large configurations might cause issues related to high memory usage.Comparison and merging of large configurations no longer requires customized OS settings.

Table of contents

Changes altering the system behavior

FunctionalityAfterBeforeResult of changes
Command interface.
In the information register record form the system behavior has been changed in the case when the OnlyInAllActions property of the Copy command is set to Auto. This value now means that the command is only present in the All actions menu. This change is not implemented in 8.3.1 compatibility mode.The Auto value of the OnlyInAllActions property of the Copy command meant that the command was present both in the command bar and in the All actions menu.The behavior of the Copy command in the information register record form is unified with its behavior in forms of other objects.
Window management.
Relative positions of the user notification window and the window showing server calls are changed.

The default position of the user notification window is the bottom right corner of the workspace area.

The default position of the window showing server calls is the bottom left corner of the workspace area.

On Windows operating system, default window positions depended on the taskbar position. On Linux operating system, default window positions were not defined.Unified default positions for the user notification window and the window showing server calls in different operating systems. Eliminated indeterminate behavior on Linux operating system.
Web client.
When a pop-up window is blocked by the pop-up blocker in Google Chrome web browser, the browser displays a related setup instruction in a new tab.The browser setup instruction was displayed in a new browser window (not in a new tab)Better usability of web browser setup.
Applied objects.
A value obtained from an empty table of values attribute, a value tree, or a tabular section matches the default value of the column attribute type (the type qualifier is taken into account).

This change is not implemented in version 8.2.16 compatibility mode.

A value obtained from an empty table of values attribute, a value tree, or a tabular section matched the default value of the column attribute type, but the type qualifier was not taken into account.The default value generation is uniform throughout the system.
Client application.
DBMS operations.
System requirements.
Configuration repositories.
The mechanism of shared work with infobase files and configuration repository files is revamped. Shared work with infobases and configuration repositories is supported for both Windows and Linux users. For the files 1Cv8.1CD, 1Cv8tmp.1CD, 1Cv8.1CL, 1Cv8tmp.1CL, and for some other files the system creates auxiliary files that have the same names with .cfl extension added (for example, 1Cv8.1CD.cfl). These files have zero size and are never deleted on closing client applications.

Shared work with a file infobase is only possible if all client applications have the same version number.

The number of simultaneous connections to a file infobase is limited to 1024.

The mechanism of shared work with the file infobase and the configuration repository did not take into account some pecularities of Linux file system.Shared work with the file infobase and the configuration repository is available to both Windows and Linux users. Issues related to multiuser work with file infobases and configuration repositories on Linux operating system are eliminated.
Data display.
When you create a formatted string in Designer (in the dialog for editing a formatted string), you can use style elements (font face and color). The formatted string stores references to style elements that were used during its creation. Converting style elements to actual fonts and colors (dereferencing) is performed when the string is displayed.The dialog for editing a formatted string did not have options for specifying style elements.

Formatted strings that were created using 1C:Enterprise script and included style elements actually contained explicit font and color values (not the references).

Improved usability of formatted string creation. You can simultaneously change the formatting of all text fragments that have the same style element applied to them.
Internet-enabled functionality.
If you use the InternetMail object with a mail server where secured StartTLS connection is set up to use the same ports as unsecured connection, the StartTLS connection is established.

This change is not implemented in version 8.2.16 compatibility mode.

If you used the InternetMail object with a mail server where secured StartTLS connection was set up to use the same ports as unsecured connection, the StartTLS connection was not established.You can establish a secured StartTLS connection to a mail server.
Spreadsheet documents.
When the Join() method of a spreadsheet document is called, the properties StayWithNext, PageTop, and PageBottom of a spreadsheet document cells area are only copied when joining is performed for the area located beyond the right border of the resulting document.

This change is not implemented in version 8.2.16 compatibility mode.

When the Join() method of a spreadsheet document was called, properies of a spreadsheet document cells area were always copied.The Join() method handles page breaks during the output to a spreadsheet document.
Server clusters.
Removing a server cluster or a working server from the cluster console requires a confirmation.Removing a server cluster or a working server from the cluster console did not require a confirmation.The chance of accidentally removing a server cluster or a working server from the cluster console is decreased.
Administration tools.
The URL parameter is added to the CheckInfoBases method of the WebCommonInfoBases internet service. It allows "redirection" of infobase list requests to another internet service (provided that the other service has the same method descriptions). The other internet service can have different authentication settings.Internet service "redirection" was not available. All web service calls used the same authentication.When retrieving the list of infobases through internet services, you have the option to use multiple services with different authentication requirements. This allows implementing scenarios of the following type: the check for infobase list changes does not require authentication, but retrieving the list requires authentication.
Applied objects.
Information registers.
Attributes, common attributes (that are not separators), and resources are not read implicitly when record sets are written to information registers.

Rights to read attributes, common attributes (that are not separators), and resources are not required when writing a recordset to an information register.

Rights to read attributes, common attributes (that are not separators), and resources were required when writing a recordset to an information register.Access right restrictions for read operations are not checked when writing a record set to an information register.

Table of contents

Changes that require changes to the configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Data display.
If a message to a user contains characters incompatible with XML format (in thick or thin client), the error XML text contains invalid characters in X position is generated.

This change is not implemented in version 8.3.1 compatibility mode.

If a message to a user contained characters incompatible with XML format, the thick and thin clients did not display any error message.Uniform system behavior for handling characters incompatible with XML format.
Applied objects.
If you explicitly specify the Encoding property of the InternetMailAttachment object, the outgoing email message is generated with explicitly specified attachment encoding.

+

This change is not implemented in version 8.2.16 compatibility mode.

The Encoding property of the InternetMailAttachment object was ignored during the generation of outgoing email message.Explicitly specified attachment encoding ensures that the emal client displays the attachment name and content correctly whenever email message encoding is different from the attachment encoding.
Spreadsheet documents.
The algorithm for calculating horizontal cell positions is changed. If total width of several adjacent cells is identical for different rows, such blocks of adjacent cells have equal width in all rows and therefore have common vertical borders.

This change is not implemented in version 8.2.16 compatibility mode.

If total width of several adjacent cells was identical for different rows, the cells might have different width in different rows, and therefore might not have common vertical borders.Improved usability of spreadsheet documents.

Table of contents

Transition from the previous version to the version 8.3.2

Table of contents

Version 8.3.1

Version 8.3.1 does not include changes introduced in version 8.2.17.

Version 8.3.1 includes known bug fixes and functionality modifications.

+

Improved the list of new and updated features:

New functions and changes

FunctionalityAfterBeforeResult of changes
Configuration properties.
Version 8.2.16 is added to the list of available values of the Compatibility mode property.Compatibility modes were available for the following platform versions: 8.1 and 8.2.13.1C:Enterprise provides compatibility of configurations developed using version 8.3.1 or later with previous platform versions.
Designer.
Cross-platform architecture.
The client application for Linux operating system is available. It includes thin client, thick client, and Designer. It supports file and client/server operation modes. Thin client can connect to infobases using a web browser. Limitations of the client application for Linux are listed in the documentation.

Installation of multiple 1C:Enterprise versions is not supported.

Shortcuts for noninteractive startup application, thin client, and thick client are added to the application menu of Linux desktop environment. They are located in the Finance subsection of the Office section.

Only the 1C:Enterprise server and the web client were available for Linux operating system.You can develop applied solutions and run client applications on Linux operating system.
Thin client access over the Internet.
The thin client is now HTTPS-enabled, thanks to client certificate support. The following client certificate storage options are supported: file, Windows certificate store, and NSS certificate store.

The following command line options for specifying certificate parameters are implemented: HttpsCert, HttpsCA and HttpsNSS.

Client applications for Linux operating system do not support Windows certificate store, and HttpsCert, and HttpsCA command line options.

The thin client was not HTTP-enabled, and client certificates were not supported.The thin client is HTTP-enabled, and client certificates are supported.
Web links.
Web services can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).Web services could not operate using HTTPS with client certificates.Web services are operational in cases when the server side requires a client certificate to use HTTPS.
Internet-enabled functionality.
HTTP and FTP connections can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).HTTP and FTP connections could not operate using HTTPS with client certificates.HTTP and FTP connections are operational in cases when the server side requires a client certificate to use HTTPS.
1C:Enterprise script.
You can calculate the value of hash function by MD5 and CRC32 algorithms using the DataHashing object.Calculating the hash function required the use of third-party (add-ins, etc.) tools. You can quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.
External data sources.
Common attributes / Data separation.
A common attribute can include an external data source. Connection parameters for such external data sources are stored by separator values. If a separator is not used in a session, the separator is treated as an independent value for storing connection parameters. Data located in tables of external data sources is not separated by separator values.Common attributes could not include external data sources.You can specify connection parameters for each data area in the infobase. This provides you with the option to access either different infobases with the same structure, or a single infobase with different connection parameters.
Managed forms.
You can specify data located in a specific row of a form attribute that has table structure (except dynamic lists) as a value of a managed form field or table.This feature was not provided.You can implement such interface features as displaying report settings in separate form fields.
External data sources.
Operating system authentication is available when working with external data sources. The SessionOSAuthenticationChange access right is implemented. It allows or denies changing the operating system authentication setting both in user settings and in current session parameters.This feature was not provided.You can establish connection to external data sources if the only authentication method available is operating system authentication.
Applied objects.
Data display.
User presentations for data base objects of the following types: Catalog, Document, ChartOfAccounts, ChartOfCalculationTypes, ChartOfCharacteristicTypes, BusinessProcess, Task, ExchangePlan, Table. Implemented the PresentationFieldsGetProcessing and PresentationGetProcessing event handlers for object manager modules of these types.

This change is not implemented in version 8.2.16 compatibility mode.

Modification of database objects using script tools was not allowed.Custom presentations for database objects. The option to obtain presentations for external data source tables when the field that provides the presentation is not specified. The option to obtain presentations of objects that include localized data.
External data sources.
1C:Enterprise script.
You can search for references to objects of external data source tables using the FindByRef() global context method or Find references to object standard function. The search is performed both in infobase tables and in external data source tables.Searching for references to objects of external data sources tables using the FindByRef() global context method or Find references to object standard function was not available.You can search for references to objects of external data source tables.
External data sources.
The AllRefsType() method is implemented for the ExternalDataSourceTablesManager object.This feature was not provided.Implementation of missing features for working with external data sources.
External data sources.
The OpenValue() global context method allows opening the following value types: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.The OpenValue() global context method did not allow opening the following value type: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.Implementation of missing features for working with information registers and external data sources.
Database configuration updates.
Server clusters.
Background database configuration update is implemented. The update is supported in client/server mode only. It is available when the data structure is modified. The update does not require long-lasting exclusive access to the infobase. The exclusive access is required at the final stage of the background update for a short period of time.

The database configuration update service is implemented for a server cluster. A system background job that performs the background database configuration update is implemented.

The GetDataBaseConfigurationUpdate() global context method and the DataBaseConfigurationUpdate object are implemented.

For the /UpdateDBCfg Designer batch mode command line option, the following parameters are implemented: -Dynamic, -BackgroundStart, -BackgroundCancel, -BackgroundFinish, -BackgroundSuspend,and -BackgroundResume.

The following events are implemented in the event log: _$InfoBase$_.DBConfigBackgroundUpdateStart, _$InfoBase$_.DBConfigBackgroundUpdateFinish, _$InfoBase$_.DBConfigBackgroundUpdateCancel, _$InfoBase$_.DBConfigBackgroundUpdateSuspend, and _$InfoBase$_.DBConfigBackgroundUpdateResume.

An update of database configuration with modified data structure was possible only in the exclusive mode.The update of database configuration with significant changes in its data structure does not cause long application downtime for end users.

You have the option to perform dynamic infobase configuration update in Designer batch mode. The option is available for both background and regular updates.

1C:Enterprise script.
File operations.
Web client.
The TempFilesDir() method is implemented for the web client. The method is available when the file system extension is installed.

The UserDataWorkDir() method is implemented. It provides access to the user directory created by the system. The method is available for thin, thick, and web clients. In the web client the method is available when the file system extension is installed.

The DocumentsDir() method is implemented. It provides access to the default document directory of the operating system. The method is available for thin, thick and web clients. In the web client the method is available when the file system extension is installed.

Standard catalogs (user data directory and document directory) were inaccessible for standard tools. In the thick and thin clients the access could be implemented using third-party tools, which reduced 1C:Enterprise portability between operating systems and client applications types.Access to certain standard directories on the client computer, which allows storing user file data in designed locations without using third-party tools.
Data display.
Formatted strings are available (FormattedString type). You can use formatted strings as:
  • data for the form elements of Label type;
  • title for the Decoration form element;
  • MessageText parameter of the DoMessageBox() method
  • QueryText parameter of the DoQueryBox() method.
Displaying text that included various formatting styles was only available for HTML documents and formatted documents.Improved text presentation capabilities and usability.
1C:Enterprise script.
Managed forms.
The URLProcessing handler is implemented for the form field Label, form field Decoration of Label type, and managed form.

The handler is called if the following conditions are met: there is a formatted string in any of the specified form fields, it contains a hyperlink, and the Hyperlink property of the form element is set to False.

Implementing presentation of an entire form element as a hyperlink was allowed, but including multiple hyperlinks in a single field was not allowed.The option to handle each hyperlink contained in a formatted string separately.
Command interface.
You can use navigation links to commands of the global command interface. Using a link executes the command.

Support of navigation links to commands is implemented for the GotoURLGotoURL() global context method.

This feature was not provided.Using a link can execute a command, and this feature can be used in the script.
Managed forms.
The URL property is implemented for managed forms. It is used for obtaining a link to the default object form.

The AutoURL property is implemented for the managed form. The GetURL() method of the ClientApplicationWindow objects returns a value of the URL property (if the AutoURL property is set to False) or the standard link to the default form.

This feature was not provided.You can specify the value of the navigation link obtained from the client application window.
1C:Enterprise script.
Common attributes / Data separation.
Applied objects.
Document journals can be included in contents of common attributes, which are not used as separators. For compatibility purposes, in infobases created in 1C:Enterprise version 8.2, the value of the Use property of the the common attribute content element is set to Do not use for document journals. Common attributes could not be displayed in document journals.Common attributes can be displayed in document journals.
Data display.
Managed forms.
Implemented the following style fonts: SmallTextFont, LargeTextFont, ExtraLargeTextFont.

For the Font type the Scale property is implemented. It specifies increase or decrease of the font size relatively to the original size.

The only method of specifying font size in a managed form was setting absolute font size.You can specify the size of the form font relatively to the base font of the form, without using absolute font size values.
Server clusters.
1C:Enterprise script.
The SafeCallMemoryLimit property is implemented for the IWorkingProcessInfo object. It specifies the amount of memory (in bytes) that the application can use during a single server call. The SafeWorkingProcessesMemoryLimit property for the IWorkingServerInfo object is implemented. It specifies maximum amount of memory (in bytes) available for all running processes on a given working server.No tools for limiting memory usage were available. It might cause problems in some situations - for example, when users customized reports that selected large amounts of data.Server stability improved. If a specific session consumes a large amount of memory, it does not cause emergency shutdown of the entire server cluster. Instead, the client application that causes the memory consumption is shut down.
Server clusters.
1C:Enterprise script.
While a working process is executing a script in the client/server infobase mode, the stack is monitored to prevent it from overflowing.Infinite recursion might lead to emergency shutdown of the working process of the server cluster.Stability of server cluster operation improved.
Server clusters.
1C:Enterprise script.
For the ISessionInfo and IInfoBaseConnectionInfo objects the following properties are implemented:
  • MemoryCurrent - size of memory (in bytes), used from the beginning of the current call;
  • MemoryLast5Min - size of memory (in bytes), used by calls during the last 5 minutes;
  • MemoryAll - size of memory (in bytes), used by calls since the beginning of the session;
  • InBytesCurrent - number of bytes read from the disk since the start of the current call;
  • InBytesLast5Min - number of bytes read by the session from the disk during the last 5 minutes;
  • InBytesAll - number of bytes read from the disk by the session since the beginning of the session;
  • OutBytesCurrent - number of bytes written to the disk by the session since the beginning of the current call;
  • OutBytesLast5Min - number of bytes written to the disk by the session for the last 5 minutes;
  • OutBytesAll - number of bytes written to the disk by the session since the beginning of the session.

Similar properties are implemented in the cluster console for the list of sessions, list of connections, and connection properties dialog.

This feature was not provided.Monitoring tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.
Technological log.
Server clusters.
Extended the list of properties for the <call> event of the technological log when the event is generated for the rphost process (the process property is set to rphost), and also when the rphost process performs a call to virtual system resources. The following properties are added:
  • Report - metadata object name of the report being executed;
  • Method - name of the called method;
  • SessionID - session number;
  • Memory - size of memory (in bytes) that was occupied and not released during the call;
  • MemoryPeak - size of memory (in bytes) that was occupied and not released during the call. The peak value;
  • InBytes - number of bytes read from the disk during the call;
  • OutBytes - number of bytes written to the disk during the call;
  • Context - event context.
The listed properties were absent from the <call> event.Technological log tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.
Common attributes / Data separation.
1C:Enterprise script.
You can delete data from a specific data area or from the entire infobase. The following data can be deleted:
  • Applied object data
  • Settings storage data
  • History
  • List of users
  • Time zone settings

The Administration right is required for deletion. The deletion can be performed:

  • using the /EraseData command line option of the Designer batch mode
  • using the EraseInfoBaseData() global context method

The _$InfoBase$_.EraseData event is implemented in the event log.

It was impossible to delete a specific data area.You can delete a data area that is no longer needed (for example, data belonging to a subscriber that stopped using the system).
Server clusters.
Software licensing.
The licensing service is implemented for the server cluster. The license search algorithm is modified.The licensing service was not present.You have the option to bind a software license to a specific computer, which is intended for running the licensing service only and will not be subject to hardware changes.
Development tools.
Dumping configurations to files and loading configurations from files is implemented.

Most objects are dumped to .xml files. Modules are dumped to the text files. Pictures are dumped to files in their original format, help information is dumped to .html files. Vendor configurations are dumped to configuration files (.cf). Ordinary forms and interfaces are dumped to binary files.

Dump configuration to files and Load configuration from files commands are added to the Configuration menu. Dump configuration files and Load configuration files commands are removed from the Configuration menu, but you can restore them using the main menu settings dialog.

The DumpConfigToFiles and LoadConfigFromFiles command line options are implemented.

Limited set of data was dumped and loaded: modules, help information, templates, rights, and pictures. Other configuration data was not dumped.

Dump configuration files and Load configuration files commands from the Configuration menu were used for dumping and loading data.

You can analyze and modify configurations using third-party tools.
Data display.
Managed forms.
You can specify the background color for form group extensions of regular groups and pages using the BackColor property. If the background color of a group is different from Auto and the group is displayed as a Group box, the group box (including the title) is filled with the specified background color.The option to specify background color for form groups was not provided.The color highlighting of groups improves visibility of form elements and the overall usability of forms.
Common attributes / Data separation.
New global context methods for managing the safe mode of data separation are available in 1C:Enterprise script: SetDataSeparationSafeMode and DataSeparationSafeMode. They duplicate the functionality of the safe attribute in the zone tag of the default.vrd file.Switching to the safe mode of data separation was only available by editing the file default.vrd and only if the web server connection to the infobase (the HTTP protocol) was used.The new methods enable safe execution of code fragments called from sessions that do not use separator values (but are intended to run in specific data areas, without any way to change the area accidentally).
Event log.
OpenID authentication.
In case of successful or unsuccessful OpenID authentication the Session.Authentication or Session. Authentication error events are generated in the event log.OpenID authentication events were not written to the event log.You can obtain information about OpenID authentication events from the event log.
Event log.
OpenID authentication.
For infobases that are OpenID providers the OpenIDProvider.PositiveAssertion event is implemented. It is generated in case of a positive response to the authentication request. If the response to the authentication request is negative, the OpenIDProvider.NegativeAssertion event is generated in the event log of the infobase.This feature was not provided.Improved tools for administration of OpenID providers.
Development tools.
You can view the values of the form element properties Font, TitleFont, FooterFont and ChoiceList in a separate window when editing of these properties is disabled.These properties could not be viewed if the object was not locked in the repository or was supported.If an item is not locked in the configuration repository or is supported, you can view its font style and choice list without disabling support and without locking the object in the repository.
Server clusters.
When logon to or logout from an infobase that requires a client license is performed, the platform can notify an external application using web service methods. In response to logon notification, the external application can allow or deny the start of the session. This option is only available in client/server infobase mode. For specifying web service parameters, the following properties are implemented:
  • External session manager property of the infobase in the cluster console
  • ExternalSessionManagerConnectionString property of the IInfoBaseInfo object.

If a web service for external session management is unavailable, the system behavior is determined using the following properties:

  • Required usage of external session manager property of the infobase in the cluster;
  • ExternalSessionManagerRequired property of the IInfoBaseInfo object.

The external session manager service is implemented on the server.

Parameters of invoked web services are listed in the documentation.

The only option to limit the number of simultaneous sessions was appropriate modification of the applied solution. A platform mechanism for performing this task was not available.A platform mechanism for monitoring the number of simultaneously used licenses for various applied solutions, which does not require modification of these applied solutions.
Web client.
Add-ins.
You can use add-ins in Google Chrome and Safari web browsers (for operating systems of Windows family and Mac OS X). The Mac OS value is implemented for the PlatformType system enumeration. A file system extension is available for these browsers on operating systems of Windows family and Mac OS X. A cryptographic extension is available for these browsers on operating systems of Windows family only.Add-ins, file system extension, and cryptographic extension were not supported for Google Chrome and Safari web browsers.A file system extension and cryptographic extension (for operating systems of Windows family only) are available for Google Chrome and Safari web browsers. Add-ins can be created for all supported web browsers.
Pictures.
Processing pictures from the script with help of the new PictureProcessor object. The following options are available:
  • Selecting a significant picture part
  • Rotating a picture
This feature was not provided.A way to process pictures before placing them in a spreadsheet document. Usage examples:
  • Select a seal from a photo
  • Rotate a picture by a specified angle to align a signature
Charts.
The managed form editor allows interactive setup for the following attribute types: Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema. You can open the interactive setup dialog box from the property panel of the attribute.Only the following ways to set up the Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema objects were available: through 1C:Enterprise script, or by putting a set up object to a template and then putting the object from the template to a form element at form creation.This feature facilitates development.
Data display.
New parameter AU for the global context method NumberInWords(). It is only used in the English locale (en, en_XX). It defines the number notation, classic or compact.

In the classic notation "and" is always used between the word "hundred" (or "thousand" or "million") and the word representing the last two decimal digits. For example, 150 is "one hundred and fifty", while 100 is "one hundred" and 50 is "fifty". In the compact notation "and" is omitted.

The compact notation was always used for converting numbers to English words.Correct number-to-word conversion according to the common practice rule in European countries.
Charts of characteristic types.
You can use the ALLOWED keyword when retrieving a list of characteristics, provided that the list was defined using one of the following: the CHARACTERISTICS keyword of the query language or the dialog box for specifying object characteristics. If you retrieve the list of characteristics using a query, you have the option to use the ALLOWED keyword there.The ALLOWED keyword was not used when retrieving lists of characteristics.Data access restrictions are implemented for tables that store property lists (for example, charts of characteristic types).
Data composition system.
Fields from data sets that are not connected can be displayed in details. For DataCompositionTemplateRecordsDataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects, the DataSets properties are implemented. The property value is an array containing names of data sets whose details are displayed.

The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects is deprecated. It is recommended that you do not use this property, although it is supported for compatibility purposes. Calling the DataSet property throws an exception if the DataSets property contains an array with more than one item.

It was impossible to display fields from data sets that were not connected.

The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords contained the name of the dataset whose details were displayed.

You can create complex analytic reports.
External data sources.
The FormGetProcessing event is implemented in the manager module of external data source table.This feature was not provided.The default form of the external data source can be redefined when the external data source is opened or obtained.
External data sources.
Hierarchical lists can be organized for object data of external data sources. The ParentField and UnfilledParentValue attributes are implemented for the Table metadata object. Hierarchical object tables can be used in the data composition system, queries, and dynamic lists.This feature was not provided.You can work with hierarchical data in external data sources.
External data sources.
Queries.
Data composition system.
You can use temporary tables when working with external data sources. Temporary tables are created directly in the database of the external data source. The following syntax is used for calling temporary tables:ExternalDataSource.<External data source name>.TempTable.<Temp table name>.This feature was not provided.You can create complex reports based on external data source tables.
Charts of characteristic types.
Data composition system.
When creating object characteristics using the Additional characteristics of metadata object dialog, if the list of characteristics is not obtained from the chart of characteristic types, the characteristic value type is defined by the attribute type specified in the Value field attribute of this dialog. If this attribute is not specified, the characteristic value type is Boolean.

When object characteristics are specified using the CHARACTERISTICS query language extension of the data composition system, if the TYPE property is not specified, the characteristic type is defined by the value type obtained in the CHARACTERISTICVALUES property. If the CHARACTERISTICVALUES property is not specified, the characteristic value type is Boolean.

When object characteristics were specified using the Additional characteristics of metadata object dialog or the CHARACTERISTICS query language extension, if the list of characteristics was not obtained from the chart of characteristic types, the characteristic value type was Boolean.

+

You can store characteristic types in catalogs, and you can modify characteristic types using a complex type of the attribute that stores the characteristic value (e.g., type of information register resource).
1C:Enterprise script.
Serialization of value table index descriptions is implemented. The index content is not serialized, but restored during deserialization.Value table indexes were lost during serialization/deserialization.More complete restoration of value table state during deserialization.
Charts.
New types of charts are implemented:
  • Funnel
  • 3D funnel
  • Normalized funnel
  • 3D normalized funnel

The following properties are implemented for the Chart object: FunnelNeckHeight, FunnelNeckWidth, and FunnelSpace. These properties are applicable for the new charts types only.

This feature was not provided.New chart functionality.
Charts.
Antialiasing mode is implemented for charts. SplineMode and SplineStrain properties are implemented for the Chart object. These properties are applicable to the following chart types: line, stacked line, area, stacked area, normalized area, ceil graph, tape graph, waterfall, funnel, and 3D funnel, and also for the following chart types, which have the Indicator flag set for the series: column, 3D column, bar, 3D bar, stacked column, 3D stacked column, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.This feature was not provided.New chart functionality.
Charts.
You can connect series of charts with each other. For the Chart object the following properties are implemented: ValuesBySeriesConnection, ValuesBySeriesConnectionLines, and ValuesBySeriesConnectionColor. These properties are applicable to the following chart types: stacked column, 3D stacked column, stacked bar, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.This feature was not provided.New chart functionality.
Charts.
The semitransparency mode is implemented for charts. SemitransparencyMode and SemitransparencyPercent properties are implemented for the Chart object. These properties are applicable to the following chart types: area, bar graph, pyramid graph, ceil graph, tape graph, waterfall, funnel, 3D funnel, and 3D normalized funnel.This feature was not provided.New chart functionality.
Charts.
Data composition system.
For the objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance the following properties are implemented: ChartType.ValuesBySeriesConnection, ChartType.ValuesBySeriesConnectionLines, ChartType.ValuesBySeriesConnectionColor, ChartType.SplineMode, ChartType.SplineStrain, and ChartType.SemitransparencyMode. These properties are used for setting data composition template parameters.This feature was not provided.New chart management options in the data composition system.
Data composition system.
In the data composition system expression language the following aggregate functions are implemented: Every(), Any(), Stddev_Pop(), Stddev_Samp(), Var_Samp(), Var_Pop(), Covar_Pop(), Covar_Samp(), Corr(), Regr_Slope(), Regr_Intercept(), Regr_Count(), Regr_R2(), Regr_AvgX(), Regr_AvgY(), Regr_SXX(), Regr_SYY(), and Regr_SXY().These aggregate functions were not provided in the data composition system expression language.The new functions facilitate creation of complex analytic reports.
Data composition system.
In the data composition system expression language the following functions are implemented: ACos(), ASin(), ATan(), Sin(), Cos(), Tan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), ValueType(), and Type().These functions were not provided in the data composition system expression language.The new functions facilitate creation of complex analytic reports.
Data composition system.
New aggregate function Rank() in the data composition system expression language. The function returns a sequence number of the current record in the current grouping, provided that all records of the current grouping are sorted in the specified order.This aggregate function was not provided in the data composition system expression language.The new functions facilitate creation of complex analytic reports.
Data composition system.
New aggregate function ClassificationABC() in the data composition system expression language. The function returns the class number: 1 – class "А", 2 – class "B", 3 – class "C".This aggregate function was not provided in the data composition system expression language.The new function facilitates creation of complex analytic reports.
Spreadsheet documents.
The Merge command is added to the shortcut menu of a spreadsheet document. It is also accessible through a keyboard shortcut Ctrl+M.

+

+

Merging cells of a spreadsheet document was only available by using the menu command Table - Merge or clicking the corresponding toolbar button.Improved usability of spreadsheet documents containing a large number of merged cells.
Charts.
The Indicator property is supported for the tape graph chart: when antialiasing is disabled, the series with the Indicator property set are displayed semitransparently on the entire chart area, overlapping other series.This feature was not provided.New chart functionality.
Managed forms.
You can specify the Arbitrary type for a subordinated attribute of a managed form attribute (e.g., column of a value table, column of a value tree, etc.).It was impossible to store some data types (such as a references to external data source tables) in subordinated attributes of managed form attributes.You can store references to external data source tables in subordinated attributes of managed form attributes.
Data display.
You can manage duplex printing of spreadsheet documents, graphical schemas (using script and interactively), and text documents (interactively only). System enumerations DuplexPrintingType and PagePlacementAlternation are implemented.This functionality was only available from a printer driver.You can explicitly specify the duplex printing option in some use cases.
Development tools.
Web client and web service publishing tools.
In the dialog for publishing to the web server you can edit all tags present in the default.vrd file. You can edit custom default.vrd files in this dialog. The descriptor parameter of the webinst utility allows you to perform publishing by template. The generated default.vrd file is used as a template.A limited set of tags present in the default.vrd file was available for editing in the dialog for publishing to the web server. The option to publish by template was unavailable in the webinst utility, which limited the capabilities of automatic publication. E.g., publishing of web services using the utility was impossible. You can edit all tags of the default.vrd file interactively, and you can create templates for the future automatic publication. Using templates allows publishing web services using the command line utility.
Client application installation.
You can set up the update of thin client distribution kit and downloading the list of common infobases using an HTTP connection or a web service.

If versions of client and server applications do not match, the thin client is downloaded and installed automatically.

The following parameters of the 1cestart.cfg file are implemented :

  • InternetService - address of the web service for updating of the thin client distribution kit and the list of common infobases,
  • WebCommonInfoBases - address of the web service for downloading the list of common infobases,
  • WebDistributiveLocation - address of the web service for updating the thin client distribution kit.

You can specify a link to the thin client distribution kit in the following configuration files:

  • In the default.vrd file using the pubdst attribute;
  • In the conf.cfg file using the PublishDistributiveLocation parameter.
Automatic update of the thin client and downloading of list of common infobases were only available in a local network.You can update the thin client distribution kit and download the list of common infobases without creating common directories. This allows you to obtain an up-to-date version of the distribution kit and the current list of infobases from a remote network.
DBMS operations.
DBA rights are not required for creating infobases in Oracle Database. The following actions cannot be performed without DBA rights:
  • creating a database (data schema)
  • deleting a data base (data schema) using the cluster management console
DBA rights were required for creating infobases in Oracle Database.Increased security of DBMS operations. New scenario of creating an infobase without DBA rights, provided the database (data schema) already exists.
Internet-enabled functionality.
1C:Enterprise script.
Encoding of text strings is implemented (the global context method EncodeString()). It simplifies the following operations:
  • Converting a text string to a format that allows using it as a part of a URL
  • Converting a URL string to a RFC 1738-compliant format

Decoding of text strings is implemented (method DecodeString()).

+

This feature was not available.Easier generation of URLs containing non-English characters.
Administration tools.
You can create a self-extracting archive (SFX archive) of a client application and upload it to a web site. You can include the client application distribution kit and the 1CEStart.cfg configuration file, which is used for installing the client application, into the archive. The created executable file is only intended to run on Windows operating systems.

The self-extracting archive is generated using the 1CEClientSetupMake.exe utility, which is distributed via ITS (http://its.1c.ru/db/metod81#content:4914:1).

This feature was not provided.Simplified installation of client applications on the client computer for infobase access over the Internet (instead of using the web client).

Table of contents

New functions and changes in the 1C:Enterprise mode

FunctionalityAfterBeforeResult of change
Standard functions.
The search for references to external data source tables is available for the standard function Find references to object, which operates in the managed mode.It was impossible to find references to objects of external data sources tables using the standard function Find references to object.You can search for references to external data source objects using a standard function.
Spreadsheet documents.
In a spreadsheet document that is in the read-only mode, you can expand and collapse groups not only using a mouse, but also using keyboard shortcuts and the shortcut menu of the spreadsheet document.In a spreadsheet document that was in the read-only mode, expanding and collapsing groups could only be performed using a mouse.Improved usability of spreadsheet documents.
Navigation links.
In the In tabs form opening mode when a form is opened by clicking a navigation panel command and the navigation link is requested, if the managed form property AutoUrl is set to True, the form returns a link to the object displayed by the form. Otherwise, it returns the value of the Url property of the managed form.In the In tabs form opening mode forms opened by clicking navigation panel commands returned links to navigation points.You can open a list form in a separate window using the shortcut menu of the tab title.
Managed forms.
If the EditMode property of a managed form table cell is set to Directly, pressing the Enter key in this cell moves the cursor to the next editable cell in this row. If the cell is last in a row, the cursor is moved to the first editable cell of the next row. If there is no next row and the managed form table has the Autoinput new row property set to True, a new row is added.In the row editing mode pressing the Enter key finished editing the table cell and did not move the cursor to the next cell.Pressing the Enter key is handled in the same way in the new row input mode and in the row editing mode. This simplifies working with the platform and enhances editing table data using the keyboard.
Managed forms.
While editing a cell of a managed form table with EditMode property set to Directly:
  • Pressing the Ins key adds a new row;
  • Pressing PgUp or PgDn moves one table page up or down;
  • Pressing Ctrl+Home or Ctrl+End moves to the first or to the last table row.
These features were not provided.Improved usability of managed form tables.
Managed forms.
In managed forms, in automatic table row adding mode, you can delete rows by pressing Alt+Shift+Del. A row is deleted in the following cases:
  • The row does not contain any data, and you click in any area outside the new row.
  • The row does not contain any data, and you move to another row using the keyboard.

You can use this keyboard shortcut even while you are editing a table row.

This feature was not provided.Improved usability of managed form tables.
Managed forms.
If you press the Down Arrow key while the cursor is in the last row of a managed form table, a new row is added. If you press the Up Arrow key while the cursor is in a new row and the new row is still empty, this row is deleted. If you move the cursor from top to bottom by holding down the Down Arrow key, the cursor will stop at the last row of the managed form table. To add a new row, release the Down Arrow key and press it again.Pressing the Down Arrow key did not create a new row. Pressing the Up Arrow key did not undo the creation of a new row.Improved usability of managed form tables.
Managed forms.
For attributes of String type that have fixed length, the automatic marking of incomplete attributes is modified. The change affects attributes located in managed form tables, table boxes or spreadsheet documents. The check whether the attribute is performed using the ValueIsFilled() method, so the value of String type is considered incomplete if it does not contain any any characters except spaces.An attribute was considered incomplete only if it contained a blank string.Unified the behavior of marking of incomplete attributes.
Web client.
When the web client is started in a web browser that is not in the list of supported ones, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per week.The check for supported web browsers was not performed.The user receives a warning if they use an unsupported web browser or an unsupported version of a supported browser.
Web client.
When the web client is started in a web browser whose version is not supported, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.The check for supported browser versions was not performed.The user receives a warning when they use an unsupported web browser or an unsupported version of a supported browser. It is recommended that they change their browser version when they receive the warning.
Web client.
When the web client is started in Microsoft Internet Explorer version later than those available during the platform development, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.The check for supported Microsoft Internet Explorer versions was not performed.The user is notified if their Microsoft Internet Explorer version was not tested for compatibility with 1C:Enterprise.
Technological log.
You can write information about working with external data sources

to the technological log. For this purpose, the <EDS> event is added to the configuration file of the technological log.

Working with external data sources was not reflected in the system technological log.A tool for analyzing problems that might occur while working with external data sources.
Technological log.
You can have all operations that affect server cluster functioning (for example, operations performed during data replication between cluster services) written to the technological log. For this purpose, the <CLSTR> event is added to the technological log configuration file.Events that were generated during the execution of operations that affected server cluster functioning were not reflected in the technological log.A tool for analyzing server cluster issues.
Server clusters.
Administration tools.
Cross-platform administration server (RAS) is implemented for administering the server cluster. The application can run both as a standalone application and a service (daemon). The administration server is installed with 1C:Enterprise server.

The cross-platform command line utility (RAC) is implemented for the administrator server. The utility is installed with 1C:Enterprise server. Administration utility version and administration server version may differ. The utility provides the same administration functionality as program cluster administration tools (the V82.ComConnector COM object),

except operating system authentication of the administrator in infobases, clusters, or working servers. The utility does not support this feature.

An interface for working with the administration server using Java is also implemented. The interface is distributed via ITS (together with its description and usage example) (http://its.1c.ru/db/metod81#content:4985:1).

Tools for 1C:Enterprise server cluster administration were only available for Windows operating system as a cluster administration console and as V82.ComConnector COM object. Linux tools for server cluster administration were not provided.You can administer 1C:Enterprise server cluster using the command line in various operating systems (Windows and Linux), and also from Java programs.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
DBMS operations.
Optimized performance of Oracle DBMS queries that include complex conditions for data access restrictions.Insufficient performance of queries that include complex conditions for data access restrictions.Improved performance of operations with data access restrictions in Oracle Database.
Applied objects.
Working with memory is optimized for some mechanisms.Insufficient performance in certain scenarios.Improved overall system performance in some scenarios.
Queries.
When executing a query, for all IN HIERARCHY conditions with the same parameter value a single temporary table per batch query is generated.When executing a query, for IN HIERARCHY conditions with the same parameter value several temporary tables were generated.Improved the performance of queries containing the same parameter values in several IN HIERARCHY operations.
Queries.
When executing a query, for all IN conditions with the same list of values a single temporary table per batch query (for storing the list) is used.When executing a query, for IN conditions with the same list of values several temporary tables were generated, one for each condition.Improved the performance of queries containing the same list of values in several IN operations.
Queries.
Improved performance of queries that include the IN HIERARCHY expression. Improved performance of queries that include performing data composition system operations on external data sources by using the IN GROUP and IN GROUP FROM THE LIST expressions.Insufficient performance of query and report selections in some cases when hierarchy conditions were used.Improved performance of query and report selections in some cases when hierarchy conditions are used.
Server clusters.
Client application.
The amount of memory consumed by server working processes is significantly reduced. Reduced client application startup time. The effect is especially noticeable on configurations having large volumes of metadata.Inefficient use of memory on configurations having large volumes of metadata.Memory requirements for servers with configurations having large volumes of metadata are reduced.
DBMS operations.
For PostgreSQL and Oracle Database, optimized recording register records with update of account register totals. The optimization is achieved by introducing a new index. The performance increase takes effect after restructuring accounting registers and disabling the compatibility mode.The data structure did not allow using the existing indexes at their full potential, which led to insufficient system efficiency.Improved performance of operations with accounting registers in PostgreSQL and Oracle Database DBMS.
DBMS operations.
Improved performance of requests to main tables when Oracle Database is used.Response time for some DBMS requests was sub-optimal.Improved performance of database requests. This includes a significant increase in the speed of configuration updates that require infobase structure updates.
DBMS operations.
Optimized some accounting register-related DBMS requests. In particular, optimized requests that include filters by account.Inefficient usage of DBMS capabilities.Improved performance for "heavy" accounting register requests (such as, when creating accounting reports or performing month-end closing).
DBMS operations.
Optimized operations with temporary tables in Microsoft SQL Server, as well as operations with objects that use temporary tables: accumulation registers, accounting registers, sequences, and so on.Insufficient performance in case of heavy usage of temporary tables.Improved performance in case of heavy usage of temporary tables in Microsoft SQL Server.
Web client.
Faster start of the web client on slow connections.A large amount of service information was obtained during the start of the web client.Faster start of the web client on slow connections.
DBMS operations.
Improved performance of operations with Microsoft SQL Server DBMS in the following cases:
  • reading and writing data;
  • loading infobase from the *.dt file (if the recovery mode is set to Simple or Bulk-logged);
  • infobase restructuring (if the recovery mode is set to Simple or Bulk-logged).

+

Inefficient usage of DBMS capabilities.Improved performance of operations with infobases that use Microsoft SQL Server DBMS.
Accounting registers.
Improved performance of accounting register operations in the following cases:
  • writing record sets with up to ten records and with several hundred records;
  • obtaining totals for a given time;
  • generating reports that use the accounting register.

The performance increase takes effect after infobase restructuring.

Insufficient performance of accounting register operations in certain use cases.Improved performance of operations with accounting registers containing a large amount of data.
DBMS operations.
The performance of operations with PostgreSQL is improved by changing the index structure. The optimization applies both to new infobases and to existing ones (after restructuring their databases).Cluster indexes were not used in PostgreSQL operations; regular indexes were created instead.Faster execution of PostgreSQL operations.
DBMS operations.
You can use separate table spaces for indexes (the v81c_index space) and for data (the v81c_data space) in PostgreSQL.

Table spaces are not created automatically; a database administrator creates them. If no additional table spaces are created, the default table space (pg_default) is used.

Using a single table space might decrease the performance (due to storage medium overload or performance limitations).Balancing system performance by recording table spaces to multiple storage media in PostgreSQL.
Web client.
Faster opening of the following forms in the web client:
  • Forms located on the main window tabs
  • Forms that block windows of their owner forms
Delays when opening forms in the web client.Faster form opening, which improves user experience.
Queries.
Improved performance retrieving a selection by group (with a large number of records) from a result of a query containing a TOTALS clause.Insufficient performance when retrieving a selection by group from a result of a query that contains totals.Improved performance when processing results of queries that contain totals.
Server clusters.
Improved server performance and scalability when processing reference data types.Insufficient server performance when processing reference data types.Improved server performance when processing reference data types.
DBMS operations.
Temporary tables containing data of unrestricted length are temporary in IBM DB2 version 8.7 and later.For data of unrestricted length, permanent tables were created and then deleted after use.System tables cannot get locked. Improved user experience in case when a large number of users are working simultaneously.
DBMS operations.
Certain operations with IBM DB2 are optimized.Insufficient usage of IBM DB2 capabilities.Faster execution of IBM DB2 operations.
DBMS operations.
Accounting registers.
Faster processing of accounting register data during database configuration update in the client/server infobase mode.Insufficient performance when reconfiguring accounting registers.Faster processing of accounting register data during their reconfiguration.
Information registers.
Totals are implemented for periodic information registers. They are intended for retrieving first and last slices, provided that the following conditions are met:
  • using totals is allowed (in metadata);
  • using totals is enabled (in the 1C:Enterprise mode);
  • slice retrieval conditions do not include date;
  • slice retrieval conditions only include dimensions and separators;
  • data access restrictions for the register only include dimensions and separators.

Properties EnableTotalsSliceFirst and EnableTotalsSliceLast are implemented for information registers.

Methods RecalcTotals(), SetTotalsUsing(), and GetTotalsUsing() are implemented for information register managers.

Access right TotalsControl is implemented for information registers. The Verify and Repair action in Designer includes recalculation of first and last slices if the Recalculating totals option is enabled in the Verifications and modes list and using totals is enabled for the register.

Each slice retrieval resulted in execution of a query to the main register table, with calculation of resource values.Faster retrieval of first and last slices for the first and the last (current) moments of time.
Development tools.
Optimized memory usage in the following cases:
  • operations with configurations that are on support
  • loading and dumping the 1cv8.dt file

This change is not implemented in 8.2.16 compatibility mode.

In some cases working with configurations that are supported by vendor configurations of large size was impossible.Reduced RAM usage when working with vendor configurations of large size.

Table of contents

Changes altering the system behavior

FunctionalityAfterBeforeResult of change
DBMS operations.
If a database query contains more than 400 levels of expression nesting, an exception occurs but the system is not shut down. This change is not implemented in 8.2.16 compatibility mode.If a database query contained more than 400 levels of expression nesting, the system performed emergency shutdown.The system stability increased, preventing shutdowns when executing complex queries.
Attribute fill checks.
Functional options.
Attributes disabled by a functional option are not included in the list of checked attributes of the FillCheckProcessingAtServer() handler.

This change is not implemented in 8.2.16 compatibility mode.

When generating the list of checked attributes, functional options were not considered.Application developers do not need to programmatically exclude attributes disabled by functional options from the check.
Queries.
If there is a list of totals with a grand total in the query result, unloading the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object results in a tree with a single node with the grand total, while nodes for groupings located in the query after the grand total become the tree elements.

This change is not implemented in 8.2.16 compatibility mode.

If there was a list of totals with a grand total in the query result, unloading of the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object created a tree with several nodes of the same level: the grand total and groupings located in the query after the grand total.The query behavior provides more comfortable work with totals when unloading the result to a tree.
Data composition system.
When a data composition result is exported to a collection of values, columns containing calculated fields will have value types specified in the calculated fields. If the calculated field value type is not specified, the value type for the corresponding column is determined automatically based on the calculated field expression.

This change is not implemented in 8.2.16 compatibility mode.

When a data composition result was exported to a collection of values, the value types for columns that contained calculated fields were always determined automatically based on the calculated field expressions. You can specify the calculated field type explicitly in cases when automatic type definition is difficult or impossible.
Client/server interaction.
When the server version is changed, sessions running at the time when the server manager is started are not deleted automatically. When a client application that uses a web server is shut down due to the client/server version difference exception, an attempt to delete the session at the server is made.When the server version was changed, the message Session is missing or deleted was generated. Furthermore, users did not receive messages that clearly described the problemWhen the platform version is changed at the server, users receive messages stating that the client application version and the server version differ (instead of the messages stating that the session is missing or deleted).
Configuration repositories.
Working with configuration repository is only possible if the repository version matches the Designer version.The check whether the repository version matches Designer version was not performed.Prevention of compatibility problems when the configuration repository server and Designer have different versions.
Configuration repositories.
When Designer operates in batch mode, if the location of the infobase that is bound to the repository is changed, the infobase is rebound to the repository and no warnings are displayed. When the location check is performed for the infobase bound to the repository, the name of computer from which the connection to the infobase in established is ignored for client/server infobases and for file infobases located on network drives.In batch mode, a warning about the infobase location change was displayed and user response was expected. When the location check was performed for the infobase bound to the repository, the name of computer from which the connection to the infobase was established was taken into account for client/server infobases and file infobases located on network drives.In batch mode, an attempt to access a copy of an infobase bound to the repository from the repository user account that is used for accessing the original infobase will lead to disconnecting the original infobase from the repository. A warning about the infobase location change is not displayed for client/server infobases and for file infobases located on network drives if the connections differ only by the name of computer from which the connection is established.
DBMS operations.
The following clustered indexes are created when using IBM DB2 DBMS:
  • for object tables - primary key (reference);
  • for tables of totals between accounts - by period;
  • for information registers - Dimensions, Dimensions+Period, Recorder+Number, Dimensions+Period+Recorder+Number, and Dimensions+Period (depending on register type).
When using IBM DB2 DBMS the following indexes were created:
  • for object tables - index by the primary key was not clustered;
  • for tables of totals between accounts - no clustered index;
  • for information registers - clustered indexes were used only in the following cases: Recorder, Dimensions, Dimensions+Period (depending on register type).
Unified approach to the implementation of object indexes in various DBMS.
Export to Microsoft Excel.
When a spreadsheet document is exported to Microsoft Excel 97 or Microsoft Excel 2007 format, cells of the spreadsheet document that are left-aligned are exported together with their general formatting. This change is not implemented in 8.2.16 compatibility mode.When a spreadsheet document was exported to Microsoft Excel 97 or Microsoft Excel 2007, cell values were converted to numbers in the following cases:
  • a number is recognized in the string content, and there is no text data after the number;
  • a number is recognized in the string content, and text data is following it, but the cell is right- or center-aligned.
If a cell of a spreadsheet document contains a numeric value, which is intended to be used as text, and the value is left-aligned (e.g., the cell contains a product code or article), when the spreadsheet document is exported to Microsoft Excel format, the cell value is not converted to a number. This simplifies the use of the converted document (including editing and comparison).
1C:Enterprise script.
Managed forms.
For methods GetForm(), OpenForm(), and OpenFormModal() the URL parameter is implemented. Its value is assigned to the URL property of received or opened forms, unless the parameter value is Undefined. Furthermore, the AutoURL property of received or opened forms is set to False. For the CommandExecuteParameters object the URL property is implemented. The property usage example is added to the command module example.This feature was not provided.You can specify a navigation link for a form that is being opened. The navigation link can be used later in the interactive mode (e.g., stored in the history).
Infobase users.
When you press Shift+Del in the list of infobase users, a warning is displayed.Pressing Shift+Del in the list of infobase users deleted a user without a warning.Prevention of accidental deletion of infobase users.
Software licensing.
If an application license is not found during the start of the application, the differences between the current hardware settings and hardware settings at the moment when the license was obtained are written to the license search log. This information is only written for software licenses.Information on differences in hardware settings was not listed in the license search log.Simplified diagnostics of software license problems when the license is not issued due to hardware settings differences.
DBMS operations.
Managed locks.
In version 8.2.16 compatibility mode, if you use Microsoft SQL Server version 2005 or later and the configuration uses managed lock mode, row versioning is enabled. The transaction isolation level is READ_COMMITED_SNAPSHOT. Consistent read is used for reading data outside of transactions.Microsoft SQL Server 2005 or later had a lock mode enabled. The transaction isolation level was READ_COMMITED. "Dirty" read was used for reading data outside of transactions.The following improvements are available:
  • Reduced number of locks and deadlocks while executing transaction queries.
  • Eliminated errors in the execution of out-of-transaction queries involving frequently modified applied objects.
  • Consistent results for reports generated outside of transactions.
Managed forms.
Data composition system.
You can implement quick choice user settings as a set of form fields in a separate group. You can manage location and other parameters of this group. The User settings group property is implemented for managed form extension for reports. You can create user settings items using the CreateUserSettingsFormElements() method of managed form extension for reports. Before settings elements are created, all existing elements are deleted from the group. Forms that are created automatically (report and user settings forms) include dedicated groups with elements used for editing settings. The OnUpdateUserSettingSetAtServer event is implemented for managed report form extension. The event is called in the following cases:
  • when the report form is created;
  • after the report variant is loaded;
  • after the report variant is changed;
  • after user modification of settings.

Presentation of automatically generated report forms is changed: report variant presentation moved to report title; the variant selection button moved to report command bar, etc. This change is not implemented in 8.2.16 compatibility mode.

Quick choice user settings were edited in a special table located in the form. The form for editing user settings contained a table for editing all user settings.

There was a field with current report presentation and a button for selecting report variant in the report form.

Improved report settings usability - they are displayed similarly to other form elements because standard form elements (text box, check box, etc.) are used instead of tables for editing settings.
Event log.
When event log is being read, events are not filtered by current separator value if the separator is conditionally disabled in the current session.When event log was being read, records were filtered by value of a conditionally disabled separator.Eliminated the differences between event log functioning in infobases without separators and infobases with conditionally disabled separators.
DBMS operations.
Internal implementation of several query executions for PostgreSQL, IBM DB2, and Oracle Database is modified. This change is not implemented in 8.2.16 compatibility mode.The implementation took advantage of DBMS specifics to a lesser extent.Improved the internal implementation of query executions for specific DBMS.
Command interface.
Navigation links to lists are implemented. A navigation link request to a form whose main attribute is a dynamic list with the main table specified returns a navigation link to the list of the object specified as the main table. This link opens the default list form. Support of navigation links to lists is implemented for the GotoURLGotoURL() global context method. This change is not implemented in 8.2.16 compatibility mode.Navigation links to lists were not provided.Users can store links to lists in history and favorites.
Configuration comparison reports.
The configuration comparison report no longer includes added and removed objects whose access rights exactly match their default access rights.

+

Added and removed objects whose access rights exactly matched their default access rights were included in the report.The report no longer displays redundant information that does not help in merging data.
Third-party software.
Migrated from OpenSSL 1.0.1 to OpenSSL 1.0.0g.OpenSSL version 1.0.1 was used.An HTTP server query error is no longer displayed when the thin client is started.
Applied objects.
Value length for Description length and Order length properties of Chart of accounts objects is limited by 628 characters. The current value length is only checked when an attempt to change it is made.Value length for Description length and Order length properties of Chart of accounts objects was not limited.

Increased platform stability. Prevention of infobase corruption (in the file mode). Prevention of performance losses.
Queries.
If a script generated by the query wizard includes result processing, the name of the variable where the result is stored is QueryResult.

This change is not implemented in 8.2.16 compatibility mode.

In certain cases (for example, when a query was created with the option to display the processed result in a report), a naming conflict occurred between variable names created by the wizard and attribute names of the report form whose module contained this code. As a result, the generated code did not work properly.Eliminated naming conflicts between variable names created by the query wizard and report form attribute names (for queries that include result processing).
Data composition system.
A query field used in a union operation becomes unavailable to filters if it has the NULL value in all parts of the union. This change is not implemented in 8.2.16 compatibility mode.If a query field used in a union operation had the NULL value in all parts of the union, filters were applied at the data set level of data composition template, not inside the query.When the UNION or UNION ALL expression is used in a query that retrieves a data set of the data composition system (with automatic filling of available settings), if a filter is applied to a field attribute, the filter is only applied to the parts of the union where the given attribute exists. When a filter is applied to a field, it is only applied to the parts where the field expression is not equal to NULL.
Event log.
The *.elf extension is removed from the Files of type list in the open file dialog box in the thick client and Designer. Opening event logs in the *.elf format is still supported. To open an .elf file, select the Event log (*.lgf) file type and then enter the file name, including the elf extension.The list of file extensions in the open file dialog box in the thick client and Designer included both *.lgf and *.elf extensions.Removed obsolete user interface options.
Event log.
Data display.
Events related to canceled transactions are displayed in gray in the ordinary form of the event log (in the same way as they are displayed in the managed form of the event log). This change is not implemented in 8.1 compatibility mode.Events related to canceled transactions were displayed in black in the ordinary form of the event log.Unification of display of ordinary and managed forms of the event log.
Standard functions.
Data display.
Object presentation in standard functions Find references to object and Delete marked objects is modified. Names of metadata objects types are removed from object presentations.In standard functions Find references to object and Delete marked objects object presentation contained the name of metadata object type.System-standard object presentation is introduced.
Accumulation registers.
Accounting registers.
Common attributes / Data separation.
Server clusters.
Changes in the table of storage settings for accumulation and accounting register totals are performed within a transaction. While tables are being modified, managed data locks are applied to the corresponding lock namespace.

A cache for storing totals storage settings for working processes is implemented.

Changes in the tables of storage settings for accumulation and accounting register totals were performed outside a transaction. Each retrieval of totals storage settings was performed using a database query.Elimination of conflicts that might occur during the modification of totals storage settings tables from multiple simultaneous sessions that have identical data separator values.

Reducing the number of database queries and improving parallel processing for sessions that use separators.

Common attributes / Data separation.
Accounting registers.
Accumulation registers.
If separators are deleted or separator types are modified, during the next update of database configuration records in the tables of totals storage settings for accounting and accumulation registers are merged according to the new sets of separators.If separators were deleted or separator types were modified, the following situations might occur:
  • Inserting records with identical values in a table of totals storage settings.
  • Database update errors due to attempts to insert records with identical values.
Improved reliability of operations during database configuration updates caused by deleting separators or modifying separator types.
Text operations.
Implemented recording a byte order mark (BOM) to the beginning of files generated by the TextWriter object if the following conditions are met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8.

This change is not implemented in the compatibility with 8.2.16 mode.

A byte order mark (BOM) was not added to the beginning of files generated by the TextWriter object if the following conditions were met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8.A byte order mark (BOM) ensures unique identification of text encoding used in a file.
XML and XDTO support.
During the import of XSD schema, if definition is missing from the target namespace schema, a diagnostic message is displayed.During the import of XSD schema, if any loading problems occurred, a diagnostic message was not displayed.Improved diagnostics during XSD schema import.
DBMS operations.
The documentation describes the specifics of working with the following DBMS: Oracle Database and PostgreSQL.The documentation did not contain enough details about the specifics of working with the following DBMS: Oracle Database and PostgreSQL.Documentation is expanded to clarify DBMS usage specifics during configuration development.
Spreadsheet documents.
While you are changing the selection area in a spreadsheet document, if the selection area contains rows with different formatting, the platform switches to the row selection mode. Then, if the platform previously was in cell selection mode and after another selection change all selected rows have the same formatting, the platform switches back to the cell selection mode.The only ways to select rows with different formatting were using headers of spreadsheet document rows or the Alt+Shift+Arrows key combination. Simplified copying of data from spreadsheet documents with different row formatting.
Web client.
Spreadsheet documents.
Users can edit spreadsheet documents in the web client. The Table main menu is modified in the web client. Clipboard is implemented for spreadsheet documents in Google Chrome web browser. The clipboard is available within a single browser instance working with a single infobase.This feature was not provided (except editing cells with values, changing the display mode of groupings, freezing rows and columns, and changing column width).Users can edit spreadsheet documents after they are generated in the web client.
Client application.
Web client.
Designer.
Spreadsheet documents.
In the Table menu of thin client, web client, thick client, and Designer, the Cells submenu is implemented. It includes some of the commands that were previously located in the Table menu, and some new commands.The Cells submenu was not available in the Table menu of thin client, web client, thick client, and Designer.Improved usability of spreadsheet documents. Menu items intended for working with spreadsheet document cells are grouped into a single submenu.
Dynamic update.
Improved reliability of dynamic update in various situations.In certain situations dynamic update worked improperly.Improved reliability of dynamic update operations.
Managed forms.
If a width limit is set for a regular group in a managed form, the size of buttons within the group is adjusted (similar to adjusting the size of other elements included in the group).A width limit set for a regular group might not affect the size of buttons within the group.Unified the algorithm of adjusting element sizes when a width limit is set for a regular group.
Data display.
Managed forms.
Tooltips of managed form items can have one of the following types: displayed directly in the text box, displayed near the form item, and opened clicking a button (in a pop-up window). If a tooltip is not specified for a form item, the command bar button linked to this item also does not have a tooltip.

You can use the InputHint property, which contains tooltip text, to display a tooltip directly in the text box. This type of tooltip is unavailable for text boxes that display data of Number and Date types.

To manage the display of tooltips and their appearance, the ExtendedTooltip and TooltipDisplay properties are implemented for the following form controls: field, table, group, button, and decoration of Text type.

Tooltips were only available in pop-up windows of form items. If a tooltip was not specified for a form item, its title was used as a tooltip for the command bar button linked to this item.You can manage tooltip formatting and tooltip positions.

Table of contents

Changes that require changes to the configuration and administrative settings

FunctionalityAfterBeforeResult of change
1C:Enterprise software system.
1C:Enterprise version is changed to 8.3.

Installation directories are changed:

  • For Windows: C:\Program Files\1cv8;
  • For Linux: /opt/1С/v8.3.

Names of installation files are changed:

  • For Windows: 1CEnterprise 8*.msi;
  • For Linux: 1С_Enterprise83*.

Names of COM objects are changed: V83.Application, V83.ComConnector.

The server service name is :

  • For Windows: 1C:Enterprise 8.3 Server Agent;
  • For Linux: srv1cv83.

The default name of the user on whose behalf the server service starts is usr1cv8.

Default template directory is changed: %APPDATA%\1C\1Cv8\tmplts.

Add-in installation directory is changed: %APPDATA%\1C\1Cv8\ExCompT.

1C:Enterprise version was 8.2.

Installation directories had the following names:

  • For Windows: C:\Program Files\1cv82;
  • For Linux: /opt/1С/v8.2.

Installation files had the following names:

  • For Windows: 1CEnterprise 8.2*.msi;
  • For Linux: 1С_Enterprise82*.

COM objects had the following names: : V82.Application, V82.ComConnector.

The server service had the following name:

  • For Windows: 1C:Enterprise 8.2 Server Agent;
  • For Linux: srv1cv82.

The default name of the user on whose behalf the server service started was usr1cv82.

Default template directory was %APPDATA%\1C\1Cv82\tmplts.

Add-ins installation directory was %APPDATA%\1C\1Cv82\ExCompT.

Due to the version number change, names and identifiers that include the version number are changed.
Applied objects.
In a document journal the attribute containing the document number is generated with fixed length if all documents included in the journal have a number field of String type of fixed length. Otherwise, the journal field will have variable length. This change is not implemented in 8.2.16 compatibility mode.In a document journal the attribute containing the number of documents was always generated with fixed length.The document number is retrieved in a uniform way, which does not depend on the retrieval method (from the document itself or from the document journal).
Spreadsheet documents.
When any of the spreadsheet document methods Show(), Print(), Hide(), and Write() is called at server or in an external connection with the SpreadsheetDocumentFileType parameter set to XLS95, an exception occurs. This change is not implemented in 8.2.16 compatibility mode.When the method was called at server or in an external connection, this did not lead to an error, but the method did not perform any actions either.Simplified detection of configuration errors related to specifying incorrect file type when working with a spreadsheet document at server or in an external connection.
Queries.
Specifying type qualifiers in the Type() function of the query language is not allowed. This change is not implemented in 8.2.16 compatibility mode.Specifying type qualifiers for the Type() function was allowed, but it did not affect the returned values.Implemented a check that eliminates the chance to misuse the query language syntax.
Spreadsheet documents.
Print scaling of a spreadsheet document does not affect its margin size. This change is not implemented in 8.2.16 compatibility mode.Print scaling of a spreadsheet document affected its margin size.Independent management of margin size and print scaling.
Data composition system.
When data composition result is put into a collection of values, fields belonging to different groups and referencing to the same data composition field are put in the same collection column. This change is not implemented in 8.2.16 compatibility mode.When data composition result was put into a collection of values, fields belonging to different groups and referencing to the same data composition field were put in different collection columns.Output of the result to a collection is performed in the same way as output of the result to a spreadsheet document.
Command interface.
1C:Enterprise script.
Format of navigation links to navigation points generated by standard command is modified to the following: e1cib/navigationpoint/Purchases/Catalog.Products.OpenList (example link). The former navigation link format is also supported.

This change is not implemented in 8.2.16 compatibility mode.

Navigation links to navigation points generated by standard commands had the following format: e1cib/navigationpoint/Purchases/Catalog.Products.Command.OpenList (example link).Unified usage of metadata names.
DBMS operations.
External data sources.
If the Name in the data source property of an external data source field contains a value enclosed in single straight quotation marks, when a DBMS query is generated, this value is not enclosed in double straight quotation marks. Otherwise, if the field value contains special characters, it is enclosed in double straight quotation marks. This change is not implemented in 8.2.16 compatibility mode.If the Name in the data source property of an external data source field contained special characters (including single straight quotation marks), the value was enclosed in double straight quotation marks.Compatibility with DMBS that use different field description syntaxes in their query and database fields (for example, MySQL).
Software licensing.
The search for available licenses covers all folders where they might be located.The search for available licenses only covered *.lic files stored in the first folder of the list and skipped any other folders where the license files might be located, regardless of whether the license was found in the first folder.Increased flexibility of the licensing mechanism. Elimination of problems that occured when the license files were located in multiple folders (for example, the first folder that was searched contained a server license, while another folder contained a multiuser license).
Managed forms.
In managed forms, the platform does not read data from hidden dynamic lists. When a form is opened, the value of the CurrentRow attribute of the managed form table connected to the dynamic list is Undefined. The CurrentRow attribute value is changed at the moment when the table is displayed to the user. This change is not implemented in 8.2.16 compatibility mode.In managed forms, the platform read data from all dynamic lists, whether they were displayed on the form or not.Reduced time for opening forms that contain multiple pages with dynamic lists.
Functional options.
Managed forms.
Behavior of the following form elements related to functional options is modified:
  • Form attributes of reference type are disabled if configuration objects that determine their type are disabled by functional options. Form attributes of complex type are disabled if functional options disable all types that form the complex type.
  • Form attributes of <Type>Object type (e.g., the main attribute of the form) are disabled if configuration objects that determine their type are disabled by functional options.
  • Form tables are disabled if they display data belonging to attributes disabled by functional options.
  • Types are not included in type selection dialogs (e.g., in text boxes connected with attributes of complex types) if configuration objects that determine these types are disabled by a functional option. Information on types disabled by functional options is cached at the client and is cleared in 20 minutes or when the RefreshInterface() method is called.

This change is not implemented in 8.2.16 compatibility mode.

Attributes and form elements had the following behavior:
  • Form attributes of reference type were not disabled when configuration objects that determined their type were disabled by functional options.
  • Form attributes of <Type>Object type were not disabled if configuration objects that determined their type were disabled by functional options.
  • Form tables were not disabled if they displayed data belonging to attributes disabled by functional options.
  • Type selection dialogs contained all types, including those disabled by functional options.
Increased effect of default functional option values on the data composition system. Unification of functional option effect on various application elements.

+

Functional options.
Data composition system.
Functional option effect on the data composition system is modified:
  • A data composition system field becomes unavailable if it is connected to attributes whose types are disabled by functional options.
  • A query table and attributes of this table become unavailable if a functional option disables the configuration object forming this table.

This change is not implemented in 8.2.16 compatibility mode.

The data composition system did not disable fields or query tables connected to data whose type was disabled by functional options.Increased automatic effect of functional options on the data composition system. Unification of functional option effect on various application elements.
Functional options.
Command interface.
Commands of the command interface become unavailable in the following cases:
  • An attribute, which is a command parameter, is disabled by a functional option.
  • A command parameter type is disabled by a functional option. If the command parameter has complex type, the command becomes unavailable if all of the parameter types are disabled.

This change is not implemented in 8.2.16 compatibility mode.

The command availability was not changed if the availability of the attribute, which was used as a parameter for the command, was changed, or when the command parameter type was disabled by a functional option.Increased effect of functional options on the data composition system. Unification of functional option effect on various application elements.
Data composition system.
Spreadsheet documents.
You can fix rows and columns of a spreadsheet document using the FixedLeft and FixedTop output parameters. If the fixed area exceeds the displayed area, the fixing is automatically turned off.The data composition system always used fixing of rows and columns in reports. In spreadsheet documents the fixed area might be larger than the displayed area.Improved usability of row and column fixing in reports. Users can disable fixing in reports when they find it inconvenient. Fixing is disabled automatically when it does not allow scrolling of the spreadsheet document.
Managed forms.
It is recommended that you use methods SetObjectAndFormConformity() and GetObjectAndFormConformity().

Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() are declared deprecated, they are only supported for compatibility purposes.

Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() were not declared deprecated.New methods with enhanced functionality are implemented, while the old ones that provide similar functionality are declared deprecated.
Lock manager.
When using the Range object constructor, an exception is thrown if the left range boundary is greater than the right one. This change is not implemented in 8.2.16 compatibility mode.Using the Range object constructor was allowed when the left boundary of the range was greater than the right one.Elimination of unpredictable behavior of the managed locks manager. Elimination of developer errors.
Managed locks.
When a managed lock is set in the file mode of the infobase, types are validated for the values located in the DataSource attribute of the DataLockItem object. This change is not implemented in 8.2.16 compatibility mode.Validation of the value types was not performed in the file mode.Unified behavior in the file and client/server modes. Easier detections of errors in the applied solution.
1C:Enterprise script.
An attempt to assign a value to an item of a fixed structure causes an exception. This change is not implemented in 8.2.16 compatibility mode.An attempt to assign a value to an item of a fixed structure did not cause an exception, and the value was not assigned.Behavior of fixed structures is similar to behavior of other fixed collections.
Web client.
System requirements.
Mozilla Firefox versions 3.0 and 3.5 are no longer supported.Mozilla Firefox versions 3.0 and 3.5 were supported.Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.
Web client.
System requirements.
Microsoft Internet Explorer version 6.0 is no longer supported. The warning that was displayed when the web client was started in Microsoft Internet Explorer 6.0 is changed to the warning about unsupported web browser.Microsoft Internet Explorer version 6.0 was supported.Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.
Spreadsheet documents.
Whenever a spreadsheet document is transferred between the client and the server, the values of its ReadOnly and Protection properties are preserved.

This change is not implemented in 8.2.16 compatibility mode.

Whenever a spreadsheet document was transferred between the client and the server, the values of its ReadOnly and Protection properties were set to False.Whenever a spreadsheet document is transferred between the client and the server, its properties are preserved in a uniform way.
Formatted documents.
Formatted document object model is extended. The document text consists of paragraphs of various types, which are included in the paragraph collection. A paragraph consists of items included in the formatted document item collection. Functionalities for paragraph and item management are implemented.

Methods GetItems() and GenerateItems() return the array of formatted document items located between the specified bookmarks. Method FindText() returns the formatted document area (FormattedDocumentRange object) that contains the specified text.

The ItemType parameter type in methods Add() and Insert() of the FormattedDocument object was changed.

Methods Add() and Insert() of the FormattedDocument object return the added/inserted item.

You can add a picture by specifying its URL (in text format).

It is recommended that you do not add or insert pictures using binary data, this options is present for compatibility purposes only. It is recommended that you use the Picture object for inserting pictures.

+

+

Formatted document text was not represented as an object model.You can implement various text processing algorithms that are based on standard formatting elements (paragraphs, lists, and so on). Automated text generation is now simpler.
Data access restrictions.
If the Update right of an object includes data access restrictions with conditions that apply to tabular section attributes, writing the object after it was modified is only allowed if tabular section data before and after the modification match the data access restrictions.

Requests from data access restrictions to tabular sections increase the processing time.

This change is not implemented in 8.2.16 compatibility mode.

If the Update right of an object included data access restrictions with conditions that applied to tabular section attributes, then whenever tabular section attributes were modified, their compliance with the data access restrictions was not be verified.Data access restrictions apply to object data and object tabular section data in a uniform way.
DBMS operations.
For complex Oracle Database queries of certain type, DBMS request generation rules are modified. Cases that led to DBMS errors are eliminated. A slowdown in DBMS request execution can occur if there are many join operations. It is recommended that you do not use queries with a large number of join operations. This change is not implemented in 8.2.16 compatibility mode.When executing complex Oracle Database queries of certain type, DBMS errors might occur in some cases.Improved stability when using Oracle Database.
Internet-enabled functionality.
You can use secure versions of SMTP and POP3.

The following properties are implemented for the InternetMailProfile object: SMTPUseSSL, POP3UseSSL, IMAPSecureAuthenticationOnly, SMTPSecureAuthenticationOnly, and POP3SecureAuthenticationOnly.

POP3 supports the GetMessageCount() method of the InternetMail object.

It is recommended that you do not use SMTPAuthentication and POP3Authentication properties of theInternetMailProfile object, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations. SMTPAuthentication and POP3Authentication properties, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations are supported for compatibility. It is recommended that you use SMTPSecureAuthenticationOnly and POP3SecureAuthenticationOnly properties of the InternetMailProfile object.

The InternetMail object did not supportsecure versions of SMTP and POP3.You can use secure versions of SMTP and POP3.
Internet-enabled functionality.
Default values are changed for InternetMailProfile object properties that store port numbers:
  • The default SMTPPort value is 0, which means port 25 for nonsecure connections and port 465 for secure connections.
  • The default POP3Port value is 0, which means port 110 for nonsecure connections and port 995 for secure connections.
  • The default IMAPPort value is 0, which means port 143 for nonsecure connections and port 993 for secure connections.

This change is not implemented in 8.2.16 compatibility mode.

The InternetMailProfile object properties that store port numbers had the following default values:
  • SMTPPort - 25.
  • POP3Port - 110.
  • IMAPPort - 143.
Simplified port setup for the InternetMailProfile object. In most cases the default port values suffice.
Managed forms.
Changed the behavior of the drop-down list in form fields that contain reference data types, enumerations, or system enumerations. Changed the look and behavior of the drop-down list. The system storage settings now store the history of previously selected values (the ChoiceHistory setting).

If user-generated lists, using a value of the FormattedString type as a value presentation is allowed.

This change is not implemented in 8.2.16 compatibility mode.

The drop-down list had a different look and behavior. The choice list did not appear in the drop-down list.Better usability of fields, which display data of reference types, enumerations, or system enumerations.
Linux.
The configuration utility for Linux is named config_system.The configuration utility for Linux was named config_server.The new utility name provides a better description of its purpose because it performs the environment check not only at the server side, but also at the client application side.
Administration.
The location.cfg configuration file stores the list of directories where 1C:Enterprise searches for system data.

During the installation of version 8.3, the search for data (user profiles, configuration files, software license files, etc.) belonging to version 8.2 is performed in directories available to the current user. If directories with data belonging to version 8.2 are found, then location.cfg files are generated in the directories intended for storing data in version 8.3. These files contain links to directories with data from version 8.2. Therefore, installing the new version does not require transferring all data and settings from version 8.2 directories to version 8.3 directories.

This feature was not provided.After installing version 8.3, you can use a single list of settings for version 8.2.16 and version 8.3.
Software licensing.
If the software license is activated "for all users" or using 1C:Enterprise server, the following directory is used for storing software licenses:
  • on Windows: %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses - for Windows Vista and later);
  • on Linux: /var/1C/licenses.

The directory is created during 1C:Enterprise installation.

Rights for accessing the created directory are granted depending on the operating system being used:

  • On Windows, read and write rights are granted to the user under whose account the server service runs. If the service is not installed, the rights for accessing the directory are not changed.
  • On Linux, the user group grp1cv8 is created. All users under whose names the server daemon runs must be included into this group. The following rights are set for the created directory: owner - root, rights - read and write; owner group - grp1cv8, rights - read and write; other users are granted the read only right.

Only users with administrative rights can obtain a client license "for all users".

The following directory was used for storing the software license files:
  • on Windows: %ALLUSERSPROFILE%\Application Data\1C\1Cv82\Conf (%ALLUSERSPROFILE%\1C\1Cv82\Conf for Windows Vista and later);
  • on Linux: ~/.1cv82/conf.

On Windows, the directory was used when the software license was activated "for all users", and on Linux - when the software license was activated using 1C:Enterprise server.

Administration of software license files is made easier. 1C:Enteprise versions 8.2.16 and 8.3 can use the same set of licenses when their software licenses are activated "for all users" or using 1C:Enterprise server.
Server clusters.
Administration tools.
The server cluster administration scheme is modified. The management of cluster processes and function distribution between these processes are performed automatically, and therefore the option to manage them manually is removed. You can affect the automatic distribution process by creating service cluster assignment rules or working server connection rules. The server cluster is functional until at least one working server marked as central server is running. The server cluster availability is defined by the Fault tolerance level parameter (the maximum number of working servers that can become unavailable without service interruption).

In the cluster console, the server cluster is displayed by its name (the Cluster name property), not by its port.

The software tools for administering server cluster version 8.3 are not compatible with the software tools for administering server cluster version 8.2.

The SessionFaultToleranceLevel property is implemented for the IClusterInfo object.

For the IWorkingServerInfo object the following properties are implemented: MainServer, ClusterMainPort, DedicatedManagers, InfoBasesPerWorkingProcessLimit, ConnectionsPerWorkingProcessLimit, and WorkingProcessMemoryLimit.

The IAssignmentRule object is implemented, it allows to manage the functionality of working servers.

The list of required functionality assignments is available via the IServerAgentConnection object and the cluster console.

For the IServerAgentConnection object the following methods are implemented: RegAssignmentRule(), UnregAssignmentRule(), GetAssignmentRules(), CreateAssignmentRule(), and ApplyAssignmentRules().

The properties of IWorkingProcessInfo, IClusterManagerInfo, and IClusterServiceInfo objects are read-only.

For the IServerAgentConnection object the following methods are removed: CreateWorkingProcessInfo(), RegWorkingProcess(), UnregWorkingProcess(), StartWorkingProcess(), StopWorkingProcess(), SetWorkingProcessUsage(), SetClusterMultiProcess(), SetWorkingProcessCapacity(), SetClusterDescription(), CreateClusterManagerInfo(), RegClusterManager(), UnregClusterManager(), RegClusterService(), UnregClusterService(), CreateStandbyClusterItem(), RegStandbyCluster(), UnregStandbyCluster(), and GetStandbyClusterList().

The IStandbyClusterItem object is deleted.

The SyncPort property is deleted for the following objects: IWorkingProcessInfo, IClusterManagerInfo, IWorkingServerInfo, and IClusterInfo.

Management of cluster processes and function distribution between these processes could only be performed manually. The server cluster was displayed in the cluster console as a port number. The fault tolerance level could not be set.Working processes are managed automatically, so that the load distribution in the server cluster is improved. At the same time, an administrator can specify working servers where certain cluster services or connections will be executed (using rules). For example, they can move the license management service to a separate working server with minimal configuration changes, or execute certain background jobs at the working server that is running Windows operating system.
Server clusters.
On Linux operating system, a server is not automatically started after it is installed. On Linux operating system, servers were automatically started after they were installed.A server is not started in the environment that is not fully configured. To configure the environment, you have to run the config_system utility first, and then you can start the server.

Table of contents

Renamed objects

ObjectThe old nameThe new name
Column groups in the user settings table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup1.

  • <Table name>ColumnGroupSettings;
  • <Table name>ColumnGroupValues.

Column groups in the data parameters table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup1;
  • <Table name>ColumnGroup2;
  • <Table name>ColumnGroup3.
  • <Table name>ColumnGroupParameterAndPeriodValue;
  • <Table name>ColumnGroupParameter;
  • <Table name>ColumnGroupPeriodValue;
  • <Table name>ColumnGroupParameterValue.
A column group in the available fields table of the data composition system is renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup.
  • <Table name>ColumnGroupAvailableField.
Column groups in the group fields table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup1;
  • <Table name>ColumnGroup2;
  • <Table name>ColumnGroup3;
  • <Table name>ColumnGroup4;
  • <Table name>ColumnGroup5.
  • <Table name>ColumnGroupGroupField;
  • <Table name>ColumnGroupFieldAndType;
  • <Table name>ColumnGroupPeriod;
  • <Table name>ColumnGroupField;
  • <Table name>ColumnGroupBeginOfPeriod;
  • <Table name>ColumnGroupEndOfPeriod.
Column groups in the selected fields table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup1;
  • <Table name>ColumnGroup3;
  • <Table name>ColumnGroup2.
  • <Table name>ColumnGroupSelectedField;
  • <Table name>ColumnGroupHeaderAndPlacement;
  • <Table name>ColumnGroupHeader;
  • <Table name>ColumnGroupField.
Column groups in the filter table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup2;
  • <Table name>ColumnGroup3;
  • <Table name>ColumnGroup4;
  • <Table name>ColumnGroup1.
  • <Table name>ColumnGroupFilter;
  • <Table name>ColumnGroupMainFilterItems;
  • <Table name>ColumnGroupLeftValue;
  • <Table name>ColumnGroupRightValue;
  • <Table name>ColumnGroupApplication.
A column group in the order table of the data composition system is renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup.
  • <Table name>ColumnGroupField.
Column groups in the output parameters table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup1;
  • <Table name>ColumnGroup2;
  • <Table name>ColumnGroup3.
  • <Table name>ColumnGroupParameterAndPeriodValue;
  • <Table name>ColumnGroupParameter;
  • <Table name>ColumnGroupParameterValue;
  • <Table name>ColumnGroupParameter.
A column group in the user field case variants table of the data composition system is renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup.
  • <Table name>ColumnGroupValue.
A column group in the appearance fields table of the data composition system is renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup.
  • <Table name>ColumnGroupField.
A column group in the gauge chart quality bands table of the data composition system is renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup.
  • <Table name>ColumnGroupBackColor.
Column groups in the filter conditions table of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • <Table name>ColumnGroup;
  • <Table name>ColumnGroup1.
  • <Table name>ColumnGroupValueAndPeriod;
  • <Table name>ColumnGroupPeriod.
Column groups in the report variant form elements of the data composition system are renamed.

This change is not implemented in version 8.2.16 compatibility mode.

  • GoToReportSelectedFields1;
  • GoToReportFilter1;
  • GoToReportOrder1;
  • GoToReportConditionalAppearance1;
  • GoToReportOutputParameters1.
  • GoToReportSelectedFieldsFromInaccessibleSelectedFields;
  • GoToReportFilterFromInaccessibleFilter;
  • GoToReportOrderFromInaccessibleOrder;
  • GoToReportConditionalAppearanceFromInaccessibleConditionalAppearance;
  • GoToReportOutputParametersFromInaccessibleOutputParameters.
Russian presentation for the ReportSettings command of the report form is changed.
  • Настройка ....
  • Настройки ....
English and Russian presentations for the LoadReportSettings command of the report form are changed.
  • Select setting ....
  • Выбрать настройку ...
  • Select settings ....
  • Выбрать настройки ...
English and Russian presentations for the SaveReportSettings command of the report form are changed.
  • Save setting ...
  • Сохранить настройку ...
  • Save settings ...
  • Сохранить настройки ...
Presentation of the StandardSettings command in the report variant form is modified.
  • Standard setting.
  • Standard settings.
Field containing name of saved settings in the Save settings dialog is changed.
  • Name of saved setting.
  • Name of saved settings.

Table of contents

Upgrade from the previous version to version 8.3.1

Table of contents

\ No newline at end of file diff --git a/distr/docs/ru/V8Update.htm b/distr/docs/ru/V8Update.htm new file mode 100644 index 0000000..32947b8 --- /dev/null +++ b/distr/docs/ru/V8Update.htm @@ -0,0 +1,673 @@ +V8Update

1С:Предприятие 8

Версия 8.3.27

Версия 8.3.26

Версия 8.3.25

Версия 8.3.24

Версия 8.3.23

Версия 8.3.22

Версия 8.3.21

Версия 8.3.20

Версия 8.3.19

Версия 8.3.18

Версия 8.3.17

Версия 8.3.16

Версия 8.3.15

Версия 8.3.14

Версия 8.3.13

Версия 8.3.12

Версия 8.3.11

Версия 8.3.10

Версия 8.3.9

Версия 8.3.8

Версия 8.3.7

Версия 8.3.6

Версия 8.3.5

Версия 8.3.4

Версия 8.3.3

Версия 8.3.2

Версия 8.3.1

Список функциональностей.

Все функциональности, Режим совместимости, Web-сервисы, Web-сервисы и HTTP-сервисы, Web-ссылки, Автоматизированное тестирование, Автономный сервер, Администрирование, Аналитика - дашборды, Аналитика - диаграммы, Аналитика - другое, Аналитика - источники, Аналитика - рабочий стол, Аналитика - язык выражений, Аутентификация OpenID, Безопасность работы системы, Ввод по строке, Веб-клиент, Внешние источники данных, Внешние компоненты, Внешние отчеты и обработки, Внешний вид приложения, Временное хранилище, Встроенный язык, Выгрузка/загрузка конфигурации в файлы, Географическая схема, Геопозиционирование, Глобальный поиск, Дата акселератор, Двоичные данные, Диаграммы, Динамический список, Динамическое обновление, Документация, Доступ к возможностям мобильного устройства, Журнал документов, Журнал регистрации, Инструменты разработчика, Интерфейс, Интерфейс OData, Используемые компоненты, История данных, Картинки, Кластер серверов, Клиент-серверное взаимодействие, Клиентское приложение, Командный интерфейс, Конфигуратор, Копии базы данных, Криптография, Кроссплатформенность, Локализация, Менеджер блокировок, Методики разработки, Механизм анализа данных, Мобильная платформа, Мобильное приложение, Мобильный клиент, Навигационные ссылки, Национальные установки, Обмен данными, Обновление конфигурации базы данных, Обработка ошибок, Общие объекты, Общие реквизиты / Разделение данных, Объекты конфигурации, Объекты метаданных, Обычная форма, Ограничение доступа к данным, Оконная система, Определяемые типы, Отображение информации, Отчет о сравнении объектов, Печать документов, План видов расчета, План видов характеристик, План счетов, Полнотекстовый поиск, Пользователи информационной базы, Права доступа, Предопределенные данные, Прикладные объекты, Приложение Autorun, Проверка заполнения реквизитов, Программное лицензирование, Работа в macOS, Работа в ОС Linux, Работа с HTML, Работа с JSON, Работа с OData, Работа с PDF-документами, Работа с WebSocket, Работа с xBase, Работа с XML, XDTO, Работа с ZIP-архивами, Работа с базой данных, Работа с буфером обмена, Работа с запросами, Работа с Интернет, Работа с информационными базами, Работа с календарями, Работа с криптографией, Работа с мультимедиа, Работа с ОС, Работа с СУБД, Работа с текстом, Работа с телефонией, Работа с файлами, Работа системы, Работа тонкого клиента через Интернет, Распознавание речи, Распределенные информационные базы, Расширение конфигурации, Региональные установки, Регистры бухгалтерии, Регистры накопления, Регистры расчета, Регистры сведений, Резервное копирование, Сборщик мобильных приложений, Свойства конфигурации, Сервис интеграции, Синтез речи, Система аналитики, Система взаимодействия, Система компоновки данных, Система лицензирования, Система программ "1С:Предприятие", Системные перечисления, Системные требования, Создание мобильного приложения, Специальные возможности, Специальные возможности мобильного устройства, Список пользователей информационной базы, Справочники, Сравнение/объединение конфигураций, Средства администрирования, Средства мультимедиа, Средства печати, Средства публикации веб-клиента и Web-сервисов, Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов, Средства разработки, Стандартные функции, Табличный документ, Тестирование и исправление информационной базы, Технологический журнал, Толстый клиент, Управляемая форма, Управляемые блокировки, Управляемые формы, Установка клиентского приложения, Установка прикладного решения, Файловый вариант, Фоновые и регламентные задания, Форма клиентского приложения, Форматированный документ, Функциональные опции, Хранение настроек, Хранилище двоичных данных, Хранилище конфигурации, Экспорт в Microsoft Excel.

Версия 8.3.27

Версия 8.3.27 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8327doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.26.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.25. +Возможность запуска конфигураций, разработанных в версии 8.3.26 и более младших, в версии 8.3.27, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.27 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.27, при необходимости, использовать для работы с информационной базой и версию 8.3.26. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Работа с WebSocket.
В системе «1С:Предприятие» реализована возможность выступать в роли WebSocket-клиента. В этой роли может выступать тонкий, толстый, веб-клиенты и сервер системы «1С:Предприятие».

Создание WebSocket-клиентов возможно в ветке Общие - WebSocket-клиенты дерева объектов конфигурации.

Реализованы свойства глобального контекста WebSocketКлиентСоединения и WebSocketКлиенты.

Данная возможность не предоставлялась.Система программ «1С:Предприятие» может выступать в роли WebSocket-клиента.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Для глобального поиска реализована возможность поиска по сообщениям контекстных обсуждений. Максимальное количество найденных сообщений (как по неконтекстным, так и по контекстным обсуждениям) равно 20.Глобальный поиск искал только в сообщениях неконтекстных обсуждений. Максимальное количество найденных сообщений было равно 15.Расширены возможности глобального поиска,
В документации данное изменение описано здесь.
Дата акселератор.
Кластер серверов.
Для Дата акселератора реализована возможность управления местом хранения базы данных: только в оперативной памяти или в оперативной памяти и на дисковом накопителе.

Каталог хранения определяется через стандартный механизм изменения каталога хранения данных для сервисов кластера (сервис DataAcceleratorService). Данная возможность поддерживается всеми инструментами администрирования кластера серверов.

Для метода МенеджерКопийБазыДанных.Добавить() реализован параметр ВариантХраненияДанныхДатаАкселератора, позволяющий указать место размещения базы Дата акселератора. Реализовано свойство МенеджерКопииБазыДанных.ВариантХраненияДанныхДатаАкселератора.

В стандартной функции Управление копиями базы данных реализована поддержка данной возможности (в диалоге создания новой копии и в списке копий базы данных).

Дата акселератор хранил базу данных только в оперативной памяти. Это приводило к тому, что после аварийного завершения работы Дата акселератора или кластера серверов, база данных должны была заново заполниться из основной базы данных, что приводило к замедлению или невозможности получения требуемых отчетов.Дата акселератор теперь можно настроить таким образом, что его перезапуск не будет требовать повторного заполнения базы данных. В результате не будет страдать оперативность получения требуемых данных.
В документации данное изменение описано здесь, здесь и здесь.
Копии базы данных.
Реализована возможность получения развернутой информации о состоянии копии базы данных. С помощью данной информации можно оценивать текущее состояние копии базы данных, состояние обновления копии и т.д. Реализована возможность запускать обновление копии базы данных в фоновом режиме (используется системное фоновое задание).

Реализован метод МенеджерКопийБазыДанных.ОбновитьВФоновомРежиме(). Реализован метод МенеджерКопииБазыДанных.ПолучитьИнформациюОКопии().

В стандартной функций управления копиями базы данных реализованы возможности просмотра состояния экземпляров выбранной копии. Запуск обновления копии теперь выполняется в фоновом режиме.

Данная возможность не предоставлялась.

Можно было получить только дату последней репликации данных.

Расширены возможности диагностики проблемных ситуаций при работе с копиями базы данных.
В документации данное изменение описано здесь и здесь.
Работа с криптографией.
Реализована возможность проверки сертификата на какой-либо момент времени в прошлом. Реализован параметр УниверсальнаяДатаПроверки для методов ПроверитьСертификат() и ПроверитьСертификатАсинх() менеджера криптографии.

Для сертификата криптографии реализована:

  • Возможность получения интервала действия закрытого ключа. Для объекта СертификатКриптографии реализованы свойства УниверсальнаяДатаНачалаЗакрытогоКлюча и УниверсальнаяДатаОкончанияЗакрытогоКлюча.
  • Возможность получения списка дополнений сертификата. Для объекта СертификатКриптографии реализовано свойство ДополненияСертификата.
  • Возможность получения дополнения сертификата в исходном виде. Для объекта СертификатКриптографии реализовано свойство ДополненияСертификатаКакИсходныеДанные.
  • Возможность определения алгоритмов, которые использовались для формирования открытого ключа и подписи, а также получения самой электронной подписи. Для объекта СертификатКриптографии реализованы свойства АлгоритмОткрытогоКлюча, АлгоритмПодписи, ЗначениеПодписи.

Свойство СертификатКриптографии.РасширенныеСвойства признано устаревшим и не рекомендуется для использования. Рекомендуется использовать свойство СертификатКриптографии.ДополненияСертификата.

Данные возможности не предоставлялись.Расширены возможности работы с сертификатами криптографии. В частности стало возможно проверять, что закрытый ключ может быть использован (не истек его срок действия).
В документации данное изменение описано здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
В тонком клиенте, работающем под управлением ОС Linux, реализована поддержка видеозвонков.В ОС Linux видеозвонки могли использоваться только в веб-клиенте.Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь.
Распознавание речи.
Средства администрирования.
Переработан механизм управления локальным распознаванием речи:
  • Для диалога создания клиент-серверной информационной базы реализован флажок Запретить локальное распознавание речи.
  • Для файла conf.cfg, расположенного в каталоге информационной базы (для файлового варианта информационной базы) реализован параметр DisableLocalSpeechToText.
  • В диалоге добавления файловой информационной базы удален флажок Запретить локальное распознавание речи.
  • Удалена команда командной строки запуска клиентского приложения /DisableLocalSpeechToText.
Управление локальным распознаванием речи выполнялось с помощью других инструментов:
  • В диалоге добавления информационной базы был доступен флажок Запретить локальное распознавание речи.
  • Могла использоваться команда командной строки запуска клиентского приложения /DisableLocalSpeechToText.

+

+

Управление локальным распознаванием речи унифицировано с другими аналогичными механизмами системы «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Кластер серверов.
При формировании дампа аварийного завершения механизмом мониторинга кластера, для завершения процесса и формирования дампа используется сигнал SIGABRT.При формировании дампа аварийного завершения механизмом мониторинга кластера, для завершения процесса и формирования дампа использовался сигнал SIGSEGV.При анализе службой поддержки фирмы «1С» дампов аварийного завершения станет проще различать дампы, сформированные механизмом мониторинга кластера (SIGABRT) и дампы, сформированные в результате критических ошибок приложения (SIGSEGV).
В документации данное изменение описано здесь.
Внешние компоненты.
Кластер серверов.
При изолированном подключении внешних компонент стало возможно принудительно завершать сеанс, даже если сеанс в момент прерывания ожидает возврата из метода внешней компоненты.При изолированном подключении внешних компонент было невозможно принудительно завершить сеанс, если сеанс в момент прерывания ожидает возврата из метода внешней компоненты.Повышено удобство администрирования кластера серверов. Снижено количество ситуаций, в которых администратор не может завершить сеанс, который блокирует нормальную работу системы.
Система взаимодействия.
Во время видеозвонка реализована возможность проинформировать участников звонка о желании высказаться или задать вопрос (поднять руку). Одновременно поднять руку могут несколько человек.

Информация о поднятой руке выводится в кадре пользователя, поднявшего руку. Также в окне видеозвонка отображается количество участников, поднявших руку. Пользователи, поднявшие руку, отображаются в порядке поднятия (чем раньше поднял - тем выше в списке).

Если пользователь, поднявший руку, покинет видеозвонок, система потеряет статус поднятия и после возвращения ему надо будет повторно поднять руку (если это все еще необходимо).

Данная возможность не предоставлялась.В обсуждениях групповых видеозвонков станет проще «просить слово», при этом не снизится количество попыток участников перебивать друг-друга.
Стандартные функции.
Хранилище двоичных данных.
Переработан интерфейс стандартной функции Управление хранилищами двоичных данных с целью сделать использование функции более понятным и удобным.Интерфейс стандартной функции Управление хранилищами двоичных данных был менее удобным и понятным для пользователей.Интерфейс стандартной функции Управление хранилищами двоичных данных стал более понятным и удобным.
Клиентское приложение.
При запуске клиентского приложения с базовой конфигурацией, будет отображаться форма с индикатором выполнения для операций анализа конфигурации и оборудования текущего компьютера.При запуске клиентского приложения с базовой конфигурацией, во время операций анализа конфигурации и оборудования текущего компьютера пользователь никак не информировался о том, чем занято клиентское приложение. В результате создавалось ощущение, что система «повисла».Ожидается снижение количества жалоб пользователей о зависании системы при запуске базовых конфигураций прикладных решений (особенно с большим количеством метаданных).
Средства администрирования.
Для команды завершения фонового обновления агента конфигуратора (config update‑db-cfg --background-finish) реализован необязательный параметр --session-terminate, который позволяет управлять принудительным завершением активных сеансов при необходимости установки исключительной блокировки базы данных.

Для команды завершения фонового обновления (config update‑db-cfg --background-finish) и команды интерактивного обновления конфигурации (config update-db-cfg) агента конфигуратора реализованы необязательный параметр --session-terminate-message, который позволяет указать причину завершения сеанса на стороне клиентского приложения.

Данная возможность не предоставлялась.Унифицировано интерактивное поведение конфигуратора и поведение в режиме агента.
В документации данное изменение описано здесь.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Хранилище двоичных данных.
Оптимизирована запись во встроенное хранилище двоичных данных.Запись во встроенное хранилище двоичных данных занимала больше времени.Ускорена запись данных во встроенное хранилище двоичных данных.
Работа с криптографией.
Работа в ОС Linux.
При работе под управлением ОС Linux ускорено построение цепочки сертификатов менеджером криптографии. При работе под управлением ОС Linux построение цепочки сертификатов менеджером криптографии занимало существенно больше времени. При работе под управлением ОС Linux ускорено построение цепочки сертификатов менеджером криптографии.
Регистры сведений.
Если запись регистра сведений была предварительно считана из информационной базы, то при вызове метода Записать() менеджера записи регистра сведений в режиме замещения, выполняется проверка равенства текущих значений ключевых полей значениям считанной записи. В случае совпадения ключевых полей выполняется обновление текущей записи.Если запись регистра сведений была предварительно считана из информационной базы, то при вызове метода Записать() менеджера записи регистра сведений в режиме замещения, запись всегда выполняется в два этапа: удаление существующей записи и записи новой.Ускорена запись единичных записей регистра сведений в том случае, если при записи неизменными остаются все ключевые поля записи.
В документации данное изменение описано здесь.
Технологический журнал.
Операция удаления устаревших файлов технологического журнала не блокирует работу пользователей и выполняется в фоновом режиме.Операция удаления устаревших файлов технологического журнала могла блокировать работу пользователей (при большом объеме удаляемых файлов) и выполняется кластером серверов в синхронном режиме.Снижено влияние технологических операций кластера серверов на работу пользователей.
Работа в macOS.
Оптимизирована работа клиентского приложения при работе под управлением ОС macOS, ускорена отрисовка окон клиентского приложения и прокрутка больших табличных документов.При работе клиентского приложения под управлением ОС macOS наблюдалась невысокая скорость работы, долго выполнялась отображение и прокрутка содержимого окон клиентского приложения.Оптимизирована работа клиентского приложения при работе под управлением ОС macOS.
Работа с СУБД.
Кластер серверов.
Ускорено удаление временных таблиц (и их индексов) при работе под управлением СУБД PostgreSQL, Postgres Pro, Tantor SE 1C и Pangolin.При работе под управлением СУБД PostgreSQL, Postgres Pro, Tantor SE 1C и Pangolin удаление временных таблиц (и их индексов) занимало больше времени.Ускорено удаление временных таблиц (и их индексов) при работе под управлением СУБД PostgreSQL, Postgres Pro, Tantor SE 1C и Pangolin.
Средства разработки.
Реализовано построение индекса метаданных в Конфигураторе в фоновом режиме.

Для отключения этой возможности реализована команда /DisableBackgroundIndexBuild строки запуска Конфигуратора.

Построение индекса метаданных в Конфигураторе начиналось в момент первого использования этого индекса пользователем и блокировало выполнение запрошенной операции до окончания формирования индекса..Возможно ускорение первого использования следующих операций после изменения метаданных: поиск ссылок на объект конфигурации, удаление объекта конфигурации, переименование объекта конфигурации. Ускорение произойдет в том случае, когда индекс метаданных успел перестроится в фоновом режиме.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Клиентское приложение.
Уменьшено время первого запуска тонкого клиента в файловом варианте информационной базы после выполнения следующих операций:
  • Создание новой информационной базы.
  • Загрузка информационной базы из dt-файла.
  • Загрузка конфигурации из сf-файла.
  • Обновление конфигурации информационной базы.
Первый запуск тонкого клиента в файловом варианте информационной базы занимал больше времени.В некоторых случаях уменьшено время первого запуска тонкого клиента в файловом варианте информационной базы .
Средства разработки.
В Конфигураторе оптимизирован поиск ссылок на объекты конфигурации, а также операции, которые используют этот поиск: переименование объекта конфигурации и удаление объекта конфигурации.Поиск ссылок на объекты конфигурации (в Конфигураторе) занимал больше времени.В Конфигураторе ускорена операция поиска ссылок на объекты конфигурации и связанные операции: переименование и удаление объекта конфигурации.
Работа с СУБД.
Кластер серверов.
Оптимизирована работа кластера серверов под нагрузкой при использовании СУБД PostgreSQL, Postgres Pro, Tantor SE 1C и Pangolin.Работа кластера серверов под нагрузкой при использовании СУБД PostgreSQL, Postgres Pro, Tantor SE 1C и Pangolin была неоптимальной.Оптимизирована работа кластера серверов под нагрузкой при использовании СУБД PostgreSQL, Postgres Pro, Tantor SE 1C и Pangolin.
Полнотекстовый поиск.
Оптимизирован алгоритм формирования индекса полнотекстового поиска, что приведет к сокращению объема индекса. Оптимизация будет заметна на индексах полнотекстового поиска большого размера (от 10 Гбайт).Предыдущий алгоритм построения индекса полнотекстового поиска формировал индексы большего объема.В результате оптимизации алгоритма формирования индекса снижается объем индекса полнотекстового поиска для больших индексов (более 10 Гбайт).
Работа с СУБД.
Ускорена очистка временных таблиц при работе с СУБД Microsoft SQL Server и PostgreSQL (и наследуемых СУБД) в условиях большой нагрузки для баз с большим количеством таблиц.Очистка временных таблиц при работе с СУБД Microsoft SQL Server и PostgreSQL (и наследуемых СУБД) в условиях большой нагрузки для баз с большим количеством таблиц занимала больше времени.Ускорена очистка временных таблиц при работе с СУБД Microsoft SQL Server и PostgreSQL (и наследуемых СУБД) в условиях большой нагрузки для баз с большим количеством таблиц.
Дата акселератор.
Оптимизировано выполнение некоторых типов запросов, включая запросы по колонкам с переменной длиной.

Повышена стабильность работы в условиях нехватки оперативной памяти во время выполнения запросов.

Выполнение некоторых типов запросов, включая запросы по колонкам с переменной длиной, требовало больше ресурсов компьютера.

Работа Дата акселератора была нестабильной при выполнении запросов в условиях нехватки оперативной памяти.

Оптимизирована работа Дата акселератора.
Полнотекстовый поиск.
При формировании и слиянии индексов полнотекстового поиска стало использоваться меньше оперативной памяти компьютера, на котором выполняются эти операции.Операции формировании и слиянии индексов полнотекстового поиска использовало больше оперативной памяти для выполнения этих операций.Снижено потребление оперативной памяти при выполнении операций формирования и слияния индексов полнотекстового поиска.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Прикладные объекты.
Для объекта метаданных, описывающего табличную часть, реализовано свойство ДлинаНомераСтроки. С помощью данного свойства реализована возможность управлять количеством строк, которые можно сохранить в табличной части прикладного объекта. Значение свойства может меняться от 5 до 9 (включая эти значения). В расширении свойство не может быть изменено.

В режиме совместимости с версией 8.3.26 поведение не изменилось.

В табличной части прикладного объекта не могло быть более 99 999 строк (длина номера строки равна 5 десятичным разрядам).Реализована возможность управлять количеством строк, которые можно сохранить в табличной части прикладного объекта. При необходимости, в табличной части объекта можно сохранять 999 999 999 строк.
В документации данное изменение описано здесь и здесь.
Пользователи информационной базы.
Средства администрирования.
Клиентское приложение.
Реализована возможность аутентификации по электронной почте. Аутентификация по электронной почте недоступна при использовании пакетного режима запуска.

Реализовано свойство ПользовательИнформационнойБазы.АутентификацияЧерезЭлектроннуюПочту. Для объекта МенеджерДополнительныхНастроекАутентификации реализованы методы УстановитьНастройкиАутентификацииЧерезЭлектроннуюПочту(), ПолучитьНастройкиАутентификацииЧерезЭлектроннуюПочту(). Реализован объект НастройкиАутентификацииЧерезЭлектроннуюПочту.

Реализовано свойство НастройкиВосстановленияПароля.СрокДействияКодаПодтверждения. Реализовано значение системного перечисления РежимАутентификации.АутентификацияЧерезЭлектроннуюПочту.

Реализована команда /EmailAuth командной строки запуска клиентского приложения.

Для атрибута type элемента method файла default.vrd (point.authentication.logonView) реализовано значение email.

Расширен состав информации для событий журнала регистрации:

  • _$User$_.New,
  • _$User$_.NewError,
  • _$User$_.Update,
  • _$User$_.UpdateError,
  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdate,
  • _$InfoBase$_.

О запуске стандартного сервиса отправки писем с кодом подтверждения для входа через электронную почту будет сообщено дополнительно, в информационном письме.

Данная возможность не предоставлялась.Расширен список вариантов аутентификации в информационной базе.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Средства администрирования.
Для утилит установки прикладных решений (autorun и SetupV8, (см. здесь)) реализована возможность определять формат дистрибутива прикладного решения: в распакованном виде или в виде zip-архива. При обнаружении архива, утилиты автоматически распакуют этот архив, затем выполнят установку и удалят временные файлы.Утилиты установки прикладных решений умели работать только с распакованными дистрибутивами прикладных решений. Пользователю было необходимо самостоятельно распаковать дистрибутив, после чего запускать программу установки.Упрощена установка прикладных решений.
Хранилище двоичных данных.
Реализована возможность создавать внешнее хранилище двоичных данных внутри контейнера S3 (например, если ограничено количество контейнеров, которые может создать пользователь). Реализована возможность указания пути к хранилищу двоичных данных внутри контейнера S3.

Реализовано свойство ПараметрыПодключенияВнешнегоХранилищаДвоичныхДанных.Каталог.

Реализована возможность загрузки файла в хранилище частями, если установлено ограничение на размер передаваемых данных. Размер части выбирается автоматически.

Получении файла из хранилища выполняется частями. Размер одной части равен 100 Мбайт и не настраивается.

Реализована обработка ограничения количества запросов, настроенная на стороне контейнера S3. Если обнаруживается такое ограничение - выполняется несколько повторных попыток выполнить запрос чтения/записи с задержкой. Выполняется не более 4 попыток, таймаут между попытками не превышает 20 секунд.

Данные возможности не предоставлялись.Механизмы внешнего хранилища двоичных данных позволяют учесть некоторые ограничения, которые существуют в контейнерах S3.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Хранилище двоичных данных.
Средства администрирования.
Для инструментов администрирования кластера серверов системы «1С:Предприятие» реализованы средства работы с хранилищем двоичных данных:
  • Реализован объект встроенного языка АдминистрированиеХранилищеДвоичных данных. Реализован метод АдминистрированиеИнформационнаяБаза.ПолучитьХранилищаДвоичныхДанных.
  • Для COM-коннектора реализован интерфейс IBinaryDataStorageInfo. Для интерфейса IWorkingProcessConnection реализованы методы GetInfoBaseBinaryDataStorages(), ClearBinaryDataStorageUnusedSpace(), CreateBinaryDataStorageFullBackup(), CreateBinaryDataStorageDifferentialBackup(), LoadBinaryDataStorageFullBackup(), LoadBinaryDataStorageDifferentialBackup().
  • В интерфейсе работы с сервером администрирования из языка Java реализован объект IBinaryDataStorageInfo. Для объекта IAgentAdminConnection реализованы методы getBinaryDataStorages(), сlearBinaryDataStorageUnusedSpace(), createBinaryDataStorageFullBackup(), createBinaryDataStorageDifferentialBackup(), loadBinaryDataStorageFullBackup(), loadBinaryDataStorageDifferentialBackup().
  • Для утилиты rac реализован режим binary-data-storage. Уточнено назначение параметров для режима infobase (доступно во встроенной справке утилиты).
  • Для утилиты ibcmd реализован режим binary-data-storage.
  • Для консоли администрирования кластера и стандартной функции Управление серверами реализована возможность просмотра хранилищ двоичных данных, подключенных к информационной базе. Для элемента с описанием информационной базы реализован подчиненный элемент Хранилища двоичных данных.
Данные возможности не предоставлялись. Администрирование хранилищ двоичных данных было доступно только через программный интерфейс работы с самим хранилищем.Администрирование хранилищ двоичных данных стало можно выполнять аналогично администрированию других механизмов кластера серверов.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Для интеграции системы взаимодействия с WhatsApp реализована возможность отправки шаблонного сообщения пользователю, который еще не писал пользователю интеграции (новый пользователь).

Реализовано свойство ВнешнийИдентификатор у объектов ОбсуждениеСистемыВзаимодействия и ОтборОбсужденийСистемыВзаимодействия.

Для интеграции с WhatsApp свойство ВнешнийИдентификатор заполняется номером телефона пользователя интеграции.

Для обсуждения WebHook в обсуждение автоматически добавляются пользователи, указанные в качестве пользователей интеграции по умолчанию, если при получении первого сообщения, у обсуждения нет пользователей кроме внешнего пользователя интеграции.

Данная возможность не предоставлялась.Прикладное решение может самостоятельно начинать обсуждение с пользователем, если используется интеграция с WhatsApp.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
В системе компоновки данных реализована возможность использования форматированных строк (макеты, условное оформление, использование функций встроенного языка, возвращающих форматированную строку и т.д.) при выводе в табличный документ. При выводе в диаграмму форматированные строки игнорируются.

Интерактивные инструменты работы с системой компоновки данных доработаны для поддержки возможности использования форматированных строк.

Для объекта ОформлениеПоляОбластиКомпоновкиДанных.ДоступныеПараметры реализована возможность использования элементов оформления ЦветФона, ЦветТекста, Шрифт, ВыделятьОтрицательные, Картинка, ПоложениеТекстаОтносительноКартинка.

Для элемента оформления Текст объекта ОформлениеКомпоновкиДанных.ДоступныеПараметры реализована поддержка типа ФорматированнаяСтрока.

Функция Представление() языка выражений системы компоновки данных возвращает значение типа ФорматированнаяСтрока, если тип значения параметра тоже ФорматированнаяСтрока.

В режиме совместимости с версией 8.3.26 поведение не изменилось.

В системе компоновки данных не поддерживалась возможность использования форматированной строки.

Для ячеек, в которые выводится несколько полей, оформление применялось к ячейке в целом.

Функция Представление() языка выражений системы компоновки данных для значения типа ФорматированнаяСтрока возвращало простую строку.

При выводе отчета на основе системы компоновки данных в табличный документ расширены возможности оформления.
Табличный документ.
При установке параметру ячейки табличного документа значения типа ФорматированнаяСтрока происходит сохранение форматирования параметра в результирующем документе, для чего результирующая ячейка становится ячейкой с форматированным текстом.

Базовым форматом для вставляемого значения параметра является:

  • Для ячейки с параметром – формат ячейки .
  • Для простой ячейки с шаблоном – формат ячейки.
  • Для форматированной ячейки с шаблоном – формат первого символа «[» в имени параметра.

В режиме совместимости с версией 8.3.26 поведение не изменилось.

Данная возможность не предоставлялась:

устанавливаемое значение приводилось к простому тексту, тип текста результирующей ячейки оставался таким же, как и тип текста ячейки с параметром в макете.

Расширены возможности оформления табличного документа.
В документации данное изменение описано здесь.
Копии базы данных.
Изменено поведение системы при выполнении обновления данных в копии базы данных, которая работает на Microsoft SQL Server с использованием репликации Версия 2. Если во время репликации данных новую таблицу информационной базы не получается подключить к механизму записи изменений (CDC), то продолжается обновление всех таблиц, которые ранее были подключены к механизму записи изменений. После окончания обновления, генерируется исключение категории ОшибкаКопииБазыДанных с текстом, описывающим проблему и содержащим список таблиц, которые не подключены к механизму. Для порционного обновления исключение после окончании обновления генерируется только в том случае, если все добавленные в механизм записи изменений (CDC) таблицы готовы к выполнению запросов.

Для того, чтобы повторить попытку подключения новых таблиц к механизму записи изменений, необходимо повторно выполнить обновление данных копии при снижении нагрузки на исходную информационную базу.

Наблюдалось другое поведение системы при выполнении обновления данных в копии базы данных, которая работает на Microsoft SQL Server с использованием репликации Версия 2. Если во время репликации данных новую таблицу информационной базы не получалось подключить к механизму записи изменений (CDC), то обновление прекращалось и пользователю отображался исходный текст ошибки SQL Server, который был сложно понимаем.Улучшена диагностика и поведение системы при возникновении проблем при обновлении данных в копии базы данных, работающей под управлением Microsoft SQL Server.
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.20.Версия формата выгрузки конфигурации в XML-файлы была равна 2.19.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
Копии базы данных.
Дата акселератор.
Если при выполнении запроса к копии базы данных, размещенной в Дата акселераторе, происходит ошибка нехватки памяти для выполнения SQL-запроса, то:
  • Копия не отключается.
  • Если настройка исполнения запроса в копии базы данных позволяет исполнить запрос на другой копии (или основной базе данных), то запрос исполняется и пользователь не получает информации об ошибке.
  • Если настройка исполнения запроса в копии базы данных не позволяет выполнить запрос в другой копии (или основной базе данных), то выполнение запроса завершается с ошибкой и пользователь видит ошибку, зависящую от механизма платформы, в котором выполняется запрос. При этом ошибка Дата акселератора будет являться причиной отображаемой ошибки.
Если при выполнении запроса к копии базы данных, размещенной в Дата акселераторе, происходит ошибка нехватки памяти для выполнения SQL-запроса, то выполнение запроса завершается с ошибкой и копия отмечается отключенной. Последующее подключение копии приведет к полному обновлению данных в копии базы данных.Снижено количество аварийных завершений выполнения запроса к копии базы данных, размещенной в Дата акселераторе. Также снижено количество неожиданных полных обновлений данных в копии базы данных, размещенной в Дата акселераторе.
Дата акселератор.
Ошибки, связанные с аутентификацией в Дата акселераторе или подключением к Дата акселератору, имеют категорию КатегорияОшибки.ОшибкаКопииБазыДанных.Ошибки, связанные с аутентификацией в Дата акселераторе или подключением к Дата акселератору, имели категорию КатегорияОшибки.ОшибкаХранимыхДанных.Категория (и описание) ошибок, связанные с аутентификацией в Дата акселераторе или подключением к Дата акселератору, стали лучше соответствовать реальной ситуации и стали более понятны.
Система компоновки данных.
В том случае, если свойство Значение объекта ЯчейкаМакетаКоллекцииЗначенийОбластиКомпоновкиДанных установлено в значение Неопределено, XDTO-сериализация такого объекта не приводит к ошибке.В том случае, если свойство Значение объекта ЯчейкаМакетаКоллекцииЗначенийОбластиКомпоновкиДанных установлено в значение Неопределено, XDTO-сериализация такого объекта приводило к ошибке.Устранено некорректное поведение системы.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Системные требования.
Прекращена поддержка операционных систем Microsoft Windows XP, Windows Vista, Server 2003 и Server 2008.

При работе веб-клиента под управлением веб-браузере Mozilla Firefox, веб-браузер должен быть не ниже версии 68 (включая эту версию).

Система «1С:Предприятие» поддерживала работу под управлением операционных систем Microsoft Windows XP, Windows Vista, Server 2003 и Server 2008.

При работе веб-клиента под управлением веб-браузере Mozilla Firefox, веб-браузер должен был быть не ниже версии 52 (включая эту версию).

Прекращена поддержка устаревших операционных систем и веб-браузеров.
В документации данное изменение описано здесь.
Кластер серверов.
Пользователи информационной базы.
Средства администрирования.
Реализована возможность распределения сеансов пользователей по рабочим серверам. Распределение выполняется с помощью требований назначения функциональности. Группировка пользователей выполняется или по имени пользователя или по ключу требования назначения.

Реализовано свойство ПользовательИнформационнойБазы.КлючТребованияНазначения. Данное свойство доступно для редактирования через стандартные инструменты работы со списком пользователей (в Конфигураторе и режиме «1С:Предприятие»).

Для требований назначения функциональностей реализованы дополнительные параметры UserName и UserAssignmentRuleKey.

Данная возможность не предоставлялась.

Сеансы новых пользователей распределялись по рабочим серверам последовательно, в соответствии с механизмами балансировки нагрузки.

+

Стало возможно выносить работу отдельных пользователей (или групп пользователей) на выделенные рабочие сервера.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Кластер серверов.
Средства администрирования.
Реализована возможность настроить расписание перезапуска рабочих процессов кластера серверов. Расписание может задаваться для кластера целиком и индивидуально для каждого рабочего сервера (имеет приоритет перед расписанием, указанным для кластера серверов целиком). Перезапуск рабочих процессов кластера (если рабочих процессов несколько) выполняется последовательно. Формат расписания аналогичен формату расписания утилиты cron (из ОС Linux). Параметр свойств кластера серверов Интервал перезапуска объявлен устаревшим и не используется для работы.

Реализована возможность выключения конкретного рабочего процесса.

Для объектов встроенного языка:

  • Реализовано свойство объекта АдминистрированиеКластер.РасписаниеПерезапуска.
  • Реализовано свойство объекта АдминистрированиеРабочийСервер.РасписаниеПерезапуска.
  • Реализован метод объекта АдминистрированиеРабочийПроцесс.Выключить().

Для объектов COM-интерфейса администрирования кластера серверов:

  • Реализовано свойство объекта IClusterInfo.RestartShcedule.
  • Реализовано свойство объекта IWorkingServerInfo.RestartSchedule.
  • Реализовано свойство объекта IWorkingProcessInfo.TurnedOn.
  • Реализован метод объекта IServerAgentConnection.TurnOffWorkingProcess().
  • Свойство IClusterInfo.LifeTimeLimit объявлено устаревшим и не рекомендуется к использованию.
  • Метод IWorkingProcessInfo.IsEnable() объявлен устаревшим и не рекомендуется к использованию.

Для объектов интерфейс администрирования из языка Java:

  • Реализованы методы объекта IClusterInfo getRestartShcedule() и setRestartShcedule().
  • Реализованы методы объекта IWorkingServerInfo getRestartShcedule() и setRestartShcedule().
  • Реализовано метод объекта IWorkingProcessInfo.TurnedOn().
  • Реализован метод объекта IAgentAdminConnection.turnOffWorkingProcess().
  • Метод IWorkingProcessInfo.isEnable() объявлен устаревшим и не рекомендуется к использованию.

Для утилиты rac реализованы следующие команды строки запуска:

  • Для режимов cluster и server реализована команда --restart-schedule.
  • Для режима process реализована команда --turn-off.
Данная возможность не предоставлялась.

Было возможно указать интервал перезапуска рабочего процесса, который отсчитывался только от момента запуска перезапускаемого рабочего процесса.

Реализована возможность более гибкой настройки перезапуска рабочих процессов кластера серверов по времени.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства разработки.
После выполнения агентом конфигуратора команды infobase-tools restore-ib:
  • выдается предупреждение о необходимости повторного подключения к агенту конфигуратора (в текстовом режиме - интерактивное, при выводе результатов в json-файл - информативное);
  • сеанс работы с информационной базой завершается. SSH-соединение разрывается;
  • агент конфигуратора не перезапускается;
  • для продолжения работы требуется заново подключиться к информационной базе (процесс агента конфигуратор остается прежним).
После выполнения агентом конфигуратора команды infobase-tools restore-ib:
  • выдавалось всегда интерактивное предупреждение о перезапуске агента конфигуратора;
  • агент конфигуратора перезапускался;
  • для продолжения работы требовалось заново подключиться к информационной базе, но процесс агента конфигуратора был другим.
Поведение агента конфигуратора синхронизировано с поведением автономного сервера при выполнении аналогичной операции.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Английское написание свойства объекта АдминистрированиеРабочийПроцесс.Включен. Старое наименование поддерживается для совместимости.
  • Enable.
  • TurnedOn.
Название стандартной функции управления хранилищами двоичных данных.
  • Управление хранилищем двоичных данных.
  • Управление хранилищами двоичных данных.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
В мобильной версии системы «1С:Предприятие» реализована поддержка ОС Android 15. Таким образом, мобильная версия «1С:Предприятие» поддерживает ОС Android в интервале версий 5 - 15.Мобильная версия «1С:Предприятие» поддерживала ОС Android в интервале версий 5 - 14.Мобильная версия «1С:Предприятия» поддерживает актуальный состав версий операционной системы Android.
В документации данное изменение описано здесь.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Работа с WebSocket.
Реализован метод WebSocketКлиент.ПолучитьСостояниеСоединения() для получения состояния WebSocket-соединения.

Реализован идентификатор WebSocket, который используется для описания объекта системы, связанного с WebSocket, в журнале регистрации, отладчике и т.д.

Состояние WebSocket-соединения можно было узнать только после получения соответствующего объекта. Получить состояние соединения у WebSocket-клиента было невозможно.

Действия с WebSocket-ами, которые происходили в журнале регистрации, отладчике и т.д. не могли быть однозначно идентифицированы.

Упрощена проверка состояния соединения WebSocket-клиента.

Упрощена идентификация объектов, связанных с WebSocket-ами в журнале регистрации, отладчике и т.д.

В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства разработки.
При использовании EDT исключен неограниченный рост кеша метаданных, который используют Конфигуратор и толстый клиент.При использовании EDT иногда наблюдался неограниченный рост кеша метаданных, который используют Конфигуратор и толстый клиент. Это приводило к неожиданному исчерпанию свободного места на диске, где размещался кеш метаданных (профиль пользователя).Исключен неограниченный рост кеша метаданных. Существенно снижена вероятность исчерпания свободного места на диске, где размещался кеш метаданных, из-за увеличения размера файла кеша.
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.27 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.27 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Системные требования.
Прекращена поддержка следующих дистрибутивов операционной системы Linux:
  • Альт Линукс версия 8 СП.
Система «1С:Предприятие» поддерживала работу в следующих дистрибутивах операционной системы Linux::
  • Альт Линукс версия 8 СП.
Прекращена поддержка устаревших дистрибутивов операционной системы Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Документация.
В документации и СП уточнено, что в свойствах элементов формы клиентского приложения могут использоваться наборы картинок (в zip-архивах).В документации и СП не отображалось, что в свойствах элементов формы клиентского приложения могут использоваться наборы картинок (в zip-архивах).Уточнена документация к платформе.
Работа с PDF-документами.
Реализована поддержка формата JBig2 при отображении и печати PDF-документов.При отображении и печати PDF-документов не поддерживался формат JBig2Улучшена поддержка формата PDF.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1С: 13.20, 13.21, 14.17, 14.18, 15.12, 15.13.
  • Postgres Pro Standard: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.
  • Postgres Pro Enterprise: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.
  • Postgres Pro CERT Standard: 14.17.1, 14.18.1, 15.12.1, 15.13.1.
  • Postgres Pro CERT Enterprise: 13.20.1, 13.21.1, 14.17.1, 14.18.1, 15.12.1, 15.13.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данная версия СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1С: 16.8, 16.9, 17.4, 17.5.
  • Postgres Pro Standard: 16.8.1, 16.9.1, 17.4.1, 17.5.1.
  • Postgres Pro Enterprise: 16.8.1, 16.9.1, 17.5.1.
  • Postgres Pro CERT Standard: 16.8.1, 16.9.1, 17.4.1, 17.5.1.
  • Postgres Pro CERT Enterprise: 16.8.1, 16.9.1, 17.5.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данная версия СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Pangolin версий 6.4.2, 6.5.1.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД Pangolin не поддерживались системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Мобильная платформа.
Мобильный клиент.
В мобильной версии для ОС Android реализована поддержка новых требований Google к работе с картинками и видеофайлами. Изменен внешний вид диалога выбора файлов в части выбора фото и видео.

Для поддержки новых требований достаточно повторно собрать мобильное приложение с новой мобильной версией и опубликовать приложение.

Мобильная версия для ОС Android не поддерживала новые требования Google к работе с картинками и видеофайлами.В мобильной версии для ОС Android реализована поддержка новых требований Google к работе с картинками и видеофайлами.
Безопасность работы системы.
Документация.
В документации отражена информация, что во время выполнения некоторых обработчиков объектов конфигурации и подписок реализовано отключение защиты от опасных действий. После выполнения обработчика защита от опасных действий включается обратно (если была включена до вызова обработчика).

Если разработчику необходимо самостоятельно включить защиту от опасных действий в обработчиках событий, то сделать это можно с помощью реализованных методов глобального контекста УстановитьОтключениеЗащитыОтОпасныхДействий() и ПолучитьОтключениеЗащитыОтОпасныхДействий(). Методы недоступны в расширении.

В документации отсутствовала информация о том, что защита от опасных действий отключается в обработчиках событий модулей объектов.

Отсутствовала возможность вернуть защиту от опасных действий, если в обработчике события это необходимо.

Реализована возможность использования защиты от опасных действий в тех случаях, когда платформа отключает эту защиту.
В документации данное изменение описано здесь.
Безопасность работы системы.
При открытии URL с помощью поля HTML-документа задействован механизм защиты от опасных действий, если он включен. Режим включается через свойство пользователя или конфигурационный файл conf.cfg.

Положительный ответ на вопрос системы запоминается в разрезе пользователя и информационной базы, отрицательный ответ не запоминается и запрос подтверждения будет отображен при следующей попытке открыть URL.

При открытии URL с помощью поля HTML-документа не был задействован механизм защиты от опасных действий.Повышена безопасность системы при использовании поля HTML-документа.
В документации данное изменение описано здесь, здесь и здесь.
Общие объекты.
Если при решении (любым алгоритмом) системы уравнений (или ее части) с помощью объекта РасчетСистемЛинейныхУравнений точное решение не удается получить с заданной точностью (в свойстве ТребуемаяТочность) за указанное (в свойстве КоличествоИтераций) количество итераций, то возвращается то решение, которое удалось найти за заданное количество итераций, однако оно может не соответствовать заданному критерию точности.При решении системы уравнений (или ее части) с помощью объекта РасчетСистемЛинейныхУравнений, если точное решение не удавалось получить с заданной точностью (в свойстве ТребуемаяТочность) за указанное (в свойстве КоличествоИтераций) количество итераций, решение системы или её части обнулялось.Если точное решение системы линейных уравнений не удается получить с заданной точностью за настроенное количество итераций, возвращается решение, которое может не соответствовать заданному критерию точности.
В документации данное изменение описано здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Tantor:
  • SE 1C версий 14.17.0, 15.12.0, 15.14.2, 15.15.0, 16.8.0, 16.10.2, 16.11.0, 17.5.0, 17.6.0, 17.7.0.
  • Certified 1C версий 15.12, 15.14.1, 16.8, 16.10.0, 16.11.0.

Архитектуры процессоров, поддерживаемые СУБД: x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД Tantor не поддерживались системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь.
Табличный документ.
Преобразование табличного документа в компактный вид всегда будет завершаться за адекватное время.Преобразование табличного документа в компактный вид могло приводить к аварийному завершению работы системы.Устранено некорректное поведение системы.
Работа в ОС Linux.
Системные требования.
Реализована поддержка ОС Мос.ОС Серверная 15.5 для архитектуры Intel.Данная возможность не предоставлялась.Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 18 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
В документации данное изменение описано здесь.
Система взаимодействия.
Улучшена передача звука (в том числе улучшено шумоподавление и подавление эха) при совершении видеозвонка в системе взаимодействия. Улучшена стабильность работы видеозвонковВ системе взаимодействия наблюдались проблемы при работе со звуком в видеозвонках.Улучшена работа со звуком в системе взаимодействия.
Система взаимодействия.
Реализована возможность интеграции системы взаимодействия с системой мгновенного обмена сообщений MAX.Данная возможность не предоставлялась.Расширены возможности интеграции системы взаимодействия с системами мгновенного обмена сообщениями.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Пользователи информационной базы.
Средства администрирования.
Клиентское приложение.
Если для выполнения операций аутентификации по электронной почте или восстановления пароля по электронной почте используется стандартный сервис отправки фирмы «1С», то в клиентском приложении необходимо указать данные пользователя портала ИТС. Другими словами, анонимная отправка электронных писем более не поддерживается. Изменен протокол взаимодействия платформы и стандартного сервиса отправки. При настройке произвольного сервиса SMTP для выполнения аутентификации или восстановления пароля пользователя по электронной почте, реализована возможность настроить аутентификацию на почтовом сервере.

Для объектов НастройкиВосстановленияПароля и НастройкиАутентификацииЧерезЭлектроннуюПочту реализованы свойства ТолькоЗащищеннаяАутентификацияSMTP, АутентификацияПоТокену, ТокенДоступа, Отправитель.

Если для выполнения операций аутентификации по электронной почте или восстановления пароля по электронной почте используется стандартный сервис отправки фирмы «1С», то для отправки электронных писем использовался анонимный доступ к почтовому серверу.Повышена безопасность отправки электронных писем при использовании стандартного сервиса отправки электронной почты фирмы «1С».
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с Интернет.
В файлы cacert.pem и cacertnx.pem добавлен промежуточный сертификат Федерального Казначейства Российской Федерации.В файлах cacert.pem и cacertnx.pem отсутствовал промежуточный сертификат Федерального Казначейства Российской Федерации.Снижается количество ошибок соединения с Единой информационной системой в сфере закупок.

Оглавление

Переход с предыдущей версии на версию 8.3.27

Оглавление

Версия 8.3.26

Версия 8.3.26 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8326doc) документации к текущей версии.

Механизм Дата акселератора вышел из статуса бета-версии.

Для использования Дата акселератора требуется лицензия уровня КОРП.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.25.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.24. +Возможность запуска конфигураций, разработанных в версии 8.3.25 и более младших, в версии 8.3.26, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.26 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.26, при необходимости, использовать для работы с информационной базой и версию 8.3.25. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Средства разработки.
Реализована возможность оповещения клиентского приложения с сервера, без использования системы взаимодействия.

Реализовано свойство глобального контекста УведомленияКлиента.

Реализовано свойство ФоновоеЗадание.НомерРодительскогоСеанса.

Для менеджера кластера реализован сервис уведомления клиента.

Для автономного сервера реализован параметр --clnt-notif-data.

Данная возможность доступна для использования с лицензией ПРОФ.

Оповещение клиентского приложения с сервера было доступно или с помощью системы взаимодействия или путем постоянного опроса клиентским приложением сервера с целью получения необходимой информации.Реализована возможность оповещения клиентского приложения с сервера без необходимости использовать систему взаимодействия или постоянного опроса клиентом сервера (что снижает производительность системы).
В документации данное изменение описано здесь, здесь, здесь и здесь.
Расширение конфигурации.
Реализована возможность создавать собственные журналы документов в расширениях. В таком журнале могут находиться любые документы системы.Данная возможность не предоставлялась.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь.
Прикладные объекты.
Средства разработки.
Реализована возможность получать выборку из информационной базы с отбором по списку ссылок. Реализован метод ВыбратьПоСсылкам() для объектов СправочникМенеджер, ДокументМенеджер, ПланВидовХарактеристикМенеджер, ПланСчетовМенеджер, ПланВидовРасчетаМенеджер, ПланОбменаМенеджер, БизнесПроцессМенеджер,

ЗадачаМенеджер.

Данная возможность не предоставлялась.Стало проще выполнять пакетную обработку списка объектов, когда список известен заранее, но изменены могут быть не все объекты.
В документации данное изменение описано здесь.
Регистры сведений.
Для набора записей независимого регистра сведений реализована возможность обновления записей регистра сведений, совпадающих по ключевым полям с записями, присутствующими в наборе записей.

Реализовано значение системного перечисления РежимЗамещения.Обновление.

Данная возможность не предоставлялась.Упрощена и ускорена операция массового обновления записей в регистре сведений. В качестве примера можно привести необходимость заполнения нового ресурса (или реквизита) регистра фиксированным значением после выполнения добавления этого ресурса.
В документации данное изменение описано здесь и здесь.
Журнал регистрации.
Реализованы события журнала регистрации:
  • Пользователи. Изменение прав доступа (_$User$_.PermissionChange) - формируется при изменении прав доступа пользователей.
  • Информационная база. Изменение роли (_$InfoBase$_.RoleUpdate) - формируется при изменении роли прикладного решения. Для каждой роли формируется свое событие журнала регистрации.
  • Информационная база. Изменение блокировки начала сеансов (_$InfoBase$_.SessionLockChange) - формируется в случае установки блокировки начала сеансов с информационной базой.
  • Информационная база. Ошибка изменения блокировки начала сеансов (_$InfoBase$_.SessionLockChangeError) - формируется в случае ошибки установки блокировки начала сеансов с информационной базой.
  • Информационная база. Изменение региональных установок (_$InfoBase$_.RegionalSettingsChange) - формируется в случае изменения региональных установок информационной базы.
  • Информационная база. Ошибка изменения региональных установок (_$InfoBase$_.RegionalSettingsChangeError) - формируется в случае ошибки изменения региональных установок информационной базы.
  • Информацbонная база. Ошибка удаления данных информационной базы (_$InfoBase$_.EraseDataError) - формируется при ошибке удаления данных информационной базы (или области данных).
  • Информационная база. Ошибка изменения конфигурации (_$InfoBase$_.ConfigUpdateError) - формируется в том случае, если во сохранения конфигурации произошла ошибка.
  • Информационная база. Ошибка фонового обновления конфигурации базы данных (_$InfoBase$_.DBConfigBackgroundUpdateError) - формируется в том случае, если ошибка произошла во время фонового обновления конфигурации базы данных.
  • Информационная база. Добавление расширения конфигурации базы данных (_$InfoBase$_.DBConfigExtensionInsert) - формируется при добавлении расширения конфигурации информационной базы.
  • Информационная база. Ошибка добавления расширения конфигурации базы данных (_$InfoBase$_.DBConfigExtensionInsertError) - формируется при возникновении ошибки добавлении расширения конфигурации информационной базы.
  • Информационная база. Удаление расширения конфигурации базы данных (_$InfoBase$_.DBConfigExtensionDelete) - формируется при удалении расширения конфигурации информационной базы.
  • Информационная база. Ошибка удаления расширения конфигурации базы данных (_$InfoBase$_.DBConfigExtensionDeleteError) - формируется при возникновении ошибки удаления расширения конфигурации информационной базы.
  • Информационная база. Изменение режима монопольного доступа к текущей области (_$InfoBase$_.ExclusiveModeChange) - возникает при изменении режима монопольного доступа информационной базе (или области данных).
  • Информационная база. Ошибка изменения режима монопольного доступа к текущей области (_$InfoBase$_.ExclusiveModeChangeError) - возникает при ошибке изменения режима монопольного доступа информационной базе (или области данных).
  • Информационная база. Изменение административных параметров (_$InfoBase$_.AdministrationParametersChange) - формируется при изменении параметров информационной базы в кластере серверов.
  • Информационная база. Изменение профиля безопасности (_$InfoBase$_.SecurityProfileChange) - формируется для каждой информационной базы, в настройках которой указан изменяемый профиль безопасности.
  • Сеанс. Изменение текущей области (_$Session$_.DataZoneChange) - возникает при изменении текущей области данных.
  • Сеанс. Ошибка изменения текущей области (_$Session$_.DataZoneChangeError) - возникает при ошибке изменения текущей области данных.
  • Сеанс. Подключение внешней обработки (_$Session$_.ExternalDataProcessorConnect) - возникает при подключении к сеансу внешней обработки.
  • Сеанс. Ошибка подключения внешней обработки (_$Session$_.ExternalDataProcessorConnectError) - возникает при ошибке подключения к сеансу внешней обработки.
  • Сеанс. Подключение внешнего отчета (_$Session$_.ExternalReportConnect) - возникает при подключении к сеансу внешнего отчета.
  • Сеанс. Ошибка подключения внешнего отчета (_$Session$_.ExternalReportConnectError) - возникает при ошибке подключения к сеансу внешнего отчета.
  • Сеанс. Подключение внешней компоненты (_$Session$_.AddInAttach) - возникает при подключении к сеансу внешней компоненты.
  • Сеанс. Ошибка подключения внешней компоненты (_$Session$_.AddInAttachError) - возникает при ошибке подключения к сеансу внешней компоненты.

Расширен состав информации для событий журнала регистрации:

  • _$InfoBase$_.ConfigUpdate.
  • _$InfoBase$_.DBConfigUpdate.
  • _$InfoBase$_.DBConfigUpdateError.
  • _$InfoBase$_.DBConfigExtensionUpdate.
  • _$InfoBase$_.DBConfigExtensionUpdateError.
Данные возможности не предоставлялись.Расширен список журналируемых действий для облегчения администрирования системы.
Журнал регистрации.
Реализована возможность управлять записью в журнал регистрации событий аудита прав доступа. По умолчанию запись событий аудита отключена. К событиям аудита прав доступа относятся события:
  • _$InfoBase$_.RoleUpdate.
  • _$User$_.PermissionChange.
  • _$InfoBase$_.AdministrationParametersChange.
  • _$InfoBase$_.SecurityProfileChange.

Для конфигурационного файла conf.cfg реализован параметр EnableAccessRightAuditEventsWrite.

Для диалогов редактирования параметров кластера (в консоли управления кластером и в стандартной обработке Управления серверами) реализован флажок Разрешить запись событий аудита прав доступа.

Для команд rac cluster list и rac cluster info реализован вывод параметра allow-access-right-audit-events-recording. Для команд rac cluster insert и rac cluster update реализован параметр --allow-access-right-audit-events-recording.

Реализовано свойство АдминистрированиеКластер.РазрешитьЗаписьСобытийАудитаПравДоступа. Реализовано свойство IClusterInfo.AllowAccessRightAuditEventsRecording. Реализован метод IServerAgentConnection.SetAllowAccessRightAuditEventsRecording().

В интерфейсе работы с сервером администрирования из языка Java для объекта IClusterInfo реализованы методы isAllowAccessRightAuditEventsRecording(), setAllowAccessRightAuditEventsRecording().

Для командной строки запуска автономного сервера (ibsrv) реализован параметр --access-right-audit-events-recording. Для конфигурационного файла автономного сервера для секции server реализован параметр access-right-audit-events-recording.

Данная возможность (запись событий аудита прав доступа) требует лицензию КОРП.

Данные возможности не предоставлялись.Реализована возможность включения событий аудита прав доступа в тех случаях, когда такой аудит необходим.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Хранение настроек.
Реализованы настройки по умолчанию. Настройка по умолчанию действует для всех пользователей, у которых нет собственной настройки. Приоритет имеет собственная настройка. Для сохранения и удаления настроек по умолчанию необходимо, чтобы пользователь обладал правом «Администрирование данных». Выбирать и использовать настройку по умолчанию может любой пользователь информационной базы.

Для объекта СтандартноеХранилищеНастроекМенеджер реализованы методы ЗагрузитьНастройкуПоУмолчанию(), СохранитьНастройкуПоУмолчанию(), УдалитьНастройкуПоУмолчанию(), ВыбратьНастройкиПоУмолчанию().

Стандартный интерфейс системы «1С:Предприятие» не позволяет выполнять какие-либо действия с настройками по умолчанию. Для выполнения таких действий необходимо самостоятельно разработать соответствующий диалог.

Разработчикам прикладных решений рекомендуется использовать настройки по умолчанию, вместо того, чтобы выполнять массовое копирование настроек новым пользователям.

Данная возможность не предоставлялась.

При необходимости указать новому пользователю ранее сделанные настройки, их (настройки) было необходимо явно скопировать из настроек какого-либо образцового пользователя.

Существенно упрощена работа администратора по стартовой настройке прикладного решения для нужд пользователей (в том числе и тех, которые еще не заведены в информационной базе). Отпала необходимость выполнять копирование настроек всем (или только новым) пользователям информационной базы при необходимости изменить всем пользователям какие-либо настройки по умолчанию.
В документации данное изменение описано здесь и здесь.
Средства администрирования.
Реализована возможность проверки пароля пользователя на раскрытие (утечку) пароля. Поддерживается возможность проверки по стандартному списку платформы «1С:Предприятие», по собственному списку недопустимых паролей, а также возможность указания адреса Интернет-сервиса проверки паролей. Реализована возможность указывать необходимость проверки пароля в дополнительных настройках аутентификации, настройках информационной базы, политике паролей пользователей.

Для объекта ДополнительныеНастройкиАутентификации реализованы:

  • Свойство СписокПроверкиРаскрытияПаролей.
  • Методы УстановитьНастройкиПроверкиРаскрытияПароля(), ПолучитьНастройкиПроверкиРаскрытияПароля().

Для глобального контекста реализованы методы УстановитьПроверкуРаскрытияПаролейПользователей(), ПолучитьПроверкуРаскрытияПаролейПользователей(), УстановитьДействиеПриНесоответствииПаролейПользователейПриАутентификации(), ПолучитьДействиеПриНесоответствииПаролейПользователейПриАутентификации(), ПроверитьРаскрытиеПароля().

Для объекта ПолитикаПаролейПользователей реализованы свойства ПроверкаРаскрытияПаролей, ДействиеПриНесоответствииПаролейТребованиямПриАутентификации.

Реализовано свойство системного перечисления РезультатПроверкиСоответствияПароляПолитике.НеСоответствуетТребованиямПроверкиРаскрытия.

Реализовано свойство объекта ПользовательИнформационнойБазы.ПарольНеСоответствуетТребованиям.

Реализованы события журнала регистрации:

  • Сеанс. Несоответствие пароля требованиям при аутентификации (_$Session$_.PasswordRequirementsViolationOnAuthentication) - формируется при аутентификации, если пароль пользователя несоответствует требованиям.
  • Сеанс. Ошибка сервиса проверки раскрытия пароля при аутентификации (_$Session$_.PasswordCompromiseCheckServiceErrorOnAuthentication) - формируется при аутентификации, если возникла ошибка работы сервис проверки раскрытия паролей.
  • Информационная база. Ошибка сервиса проверки раскрытия пароля (_$InfoBase$_.PasswordCompromiseCheckServiceError) - формируется при ошибке обращения к сервису проверки раскрытия паролей.
  • Информационная база. Изменение списка проверки раскрытия пароля (_$InfoBase$_.PasswordCompromiseCheckListUpdate) - формируется при изменении списка проверки раскрытия паролей.
  • Информационная база. Ошибка изменения списка проверки раскрытия пароля (_$InfoBase$_.PasswordCompromiseCheckListUpdateError) - формируется при возникновении ошибки изменения списка проверки раскрытия паролей.

Расширен состав информации для событий журнала регистрации:

  • _$User$_.New.
  • _$User$_.NewError.
  • _$User$_.Update.
  • _$User$_.UpdateError.
  • _$InfoBase$_.ParametersUpdate.
  • _$InfoBase$_.ParametersUpdateError.
  • _$InfoBase$_.UserPasswordPolicyNew.
  • _$InfoBase$_.UserPasswordPolicyUpdate.
  • _$Session$_.PasswordChangeError.
  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdate.
  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdateError.
Данная возможность не предоставлялась.Реализована возможность блокировать возможность указания в числе паролей пользователей «общеизвестных» паролей и паролей, которые не могут быть назначены из-за корпоративных ограничений.
В документации данное изменение описано здесь, здесь и здесь.
Расширение конфигурации.
В расширении конфигурации реализована возможность модификации свойств Пакет и ПространствоИмен заимствованного пакета XDTO, а также свойства ПакетыXDTO заимствованного Web-сервиса.

Для пакета XDTO указанные свойства замещаются одноименными свойствами из расширения. Для Web-сервисов список пакетов в результирующей конфигурации дополняется значением из расширения.

Данная возможность не предоставлялась.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Копии базы данных.
При восстановлении информационной базы из dt-файла, блокируется синхронизация данных с копиями базы данных, которые настроены в исходной информационной базе (кроме копии Дата акселератора). Администратор может явным образом разрешить использование копий с помощью стандартной обработки Управление копиями базы данных в восстановленной информационной базе. Стандартная обработка также отображает владельца каждой копии, настроенной в информационной базе (кроме копии Дата акселератора).

Для менеджера копии базы данных реализованы методы УстановитьИспользованиеБазыДанныхКопииЭтойКопией().

Для менеджера копий базы данных реализован метод ПолучитьИнформациюОбИспользованииБазыДанныхКопии().

Метод Обновить() менеджера копий базы данных генерирует исключение, если обновляемая база данных используется другой информационной базой.

Рекомендуется провести анализ инструментов обновления копий базы данных в прикладных решениях и реализовать (при необходимости) информирование администратора о проблемах, которые возникают при обновлении копий базы данных.

Данная возможность не предоставлялась.

После восстановления информационной базы из dt-файла, и запуска прикладного решения, начинался процесс обновления всех настроенных копий (если СУБД, на которых располагались копии, были доступны восстановленной информационной базе), что могло привести к нарушению целостности информации в копиях (с точки зрения исходной информационной базы).

При создании копии информационной базы (например, для целей тестирования), данные из копии информационной базы не будут попадать в копии базы данных, с которыми работает исходная информационная база. Таким образом, данные в копиях будет защищены от обновления некорректной информацией.
В документации данное изменение описано здесь.
Работа с СУБД.
Реализована возможность создавать произвольные индексы для следующих объектов конфигурации: справочники, документы, журналы документов, регистры сведений, накоплений, бухгалтерии, расчета, бизнес-процессы, задачи, планы видов характеристик, планы счетов, планы обмена, последовательности. При создании индекса указываются поля и реквизиты конфигурации, а не физические поля базы данных. Платформа выполняет требуемую конвертацию автоматически, при сохранении конфигурации. Невозможно создание индекса, который будет содержать более 16 физических полей базы данных.

Встроенные индексы системы не подлежат редактированию и не показываются в инструментах конфигуратора. Фактическое добавление и удаление индексов происходит при реструктуризации информационной базы.

Для объектов конфигурации, поддерживающих возможность создания дополнительных индексов, реализовано свойство ДополнительныеИндексы.

Метод ПолучитьСтруктуруХраненияБазыДанных() возвращает информацию о дополнительных индексах, если они заданы в конфигурации (в колонке Индексы). В таблице значений, которая описывает поля индекса таблицы (Индексы.Поля), реализована колонка ТипПоля, которое описывает тип поля индекса.

Создание или изменение дополнительных индексов в расширении конфигурации не поддерживается.

При создании дополнительных индексов следует соблюдать осторожность и осмотрительность. Следует помнить, что дополнительные индексы могу приводить не только к позитивным последствиям (ускорение получения данных при работе прикладного решения), но и к негативным - замедление скорости записи в информационную базу, увеличение дискового пространства, занимаемого файлами базы данных, снижение скорости регламентных операций с базой данных.

Данная возможность требует лицензию КОРП.

Данная возможность не предоставлялась.

Создание дополнительных индексов было возможно только на уровне СУБД.

В случае необходимости, реализована возможность создания дополнительных индексов базы данных, которые могут ускорить выполнение специализированных запросов прикладного решения.
В документации данное изменение описано здесь, здесь и здесь.
Клиентское приложение.
Реализована возможность аутентификации пользователя с использованием QR-кода.

В параметрах пользователя реализован флажок Аутентификация QR кодом. Реализовано свойство ПользовательИнформационнойБазы.АутентификацияQRКодом.

Для файла default.vrd реализован элемент <mobileApps>.

Расширен состав информации для событий журнала регистрации:

  • _$User$_.New.
  • _$User$_.Update.
  • _$Session$_.Authentication.
  • _$Session$_.AuthenticationError.
  • _$Session$_.AuthenticationFirstFactor.
Данная возможность не предоставлялась.Если пользователь аутентифицирован в какой-либо информационной базе с помощью мобильного приложения, то стало возможно не вводить пароль при необходимости получения доступа к этой же базе с другого устройства - достаточно с мобильного устройства отсканировать QR-код, который отображается формой аутентификации.
В документации данное изменение описано здесь, здесь, здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
Во время демонстрации экрана в тонком клиенте, во время видеозвонка системы взаимодействия, реализована возможность выбирать окно (приложение), которое будет демонстрироваться абонентам во время разговора.

Реализована возможность настроить режим отображение оповещений системы взаимодействия во время демонстрации экрана: показывать все сообщение, показывать только отправителя и скрывать сообщения.

Во время демонстрации экрана в тонком клиенте, во время видеозвонка системы взаимодействия, было возможно выбирать только монитор (если их несколько), который будет демонстрироваться абонентам во время разговора. Не поддерживался выбор окна (приложения) для демонстрации.

Во время демонстрации экрана абоненты видеозвонка могли видеть все оповещения системы взаимодействия.

Стало возможно снизить нагрузку на канал связи при демонстрации экрана, за счет того, что для демонстрации можно выбрать не весь монитор, а только выбранного окно приложения, которое часто занимает не весь выбранный монитор/рабочий стол.

При видеозвонке стало возможно управлять отображением оповещений системы взаимодействия, что положительно скажется на конфиденциальности во время видеозвонка.

Система взаимодействия.
Улучшено качество видео и изображения демонстрируемого экрана при проблемах с сетью. При ухудшении пропускной способности канала должно пропорционально снижать качество изображения, но не должно происходить прерывания трансляции.При ухудшении качества канала связи могло происходить прерывание видеопотока (как обычного видео, так и демонстрации экрана) или существенные (по времени протекания) «замирания» картинки.Улучшено качество видеосвязи (в том числе демонстрации экрана) при проблемах с каналом связи.
Система взаимодействия.
При использовании видеозвонков системы взаимодействия в тонком клиенте реализована:
  • Возможность включения автоматической регулировки уровня усиления микрофона. В настройках системы взаимодействия реализован флажок Автоматическая регулировка уровня громкости микрофона. Настройка по умолчанию выключена. Настройка запоминается на клиентском компьютере в разрезе микрофонов.
  • Возможность выбрать режим работы шумоподавления: Тихий фоновый шум (значение по умолчанию), Громкая речь, шумы и Шумоподавление выкл. Настройка запоминается на клиентском компьютере в разрезе микрофонов.

+

При использовании видеозвонков в системе взаимодействия не было возможности управлять уровнем усиления микрофона и режимом работы шумоподавления.Стало возможно включить режим, когда система взаимодействия будет автоматически усиливать тихий и приглушать слишком громкий голос абонента. Также стало возможно управлять работой системы шумоподавления и эхоподавления.
Стандартные функции.
Для стандартной обработки История изменения данных переработана форма настройки:
  • Реализованы поля поиска по объектам конфигурации, табличным частям и полям.
  • Реализовано отображение признака того, что конкретная настройка выполнена в режиме «1С:Предприятие» или в Конфигураторе.
  • Реализована возможность установить для объекта (-ов) конфигурации стандартные настройки (из метаданных).
  • Реализована возможность очистки истории данных.
  • Реализовано возможность отображения отличия текущих настроек истории от настроек, сделанных в метаданных.
Данные возможности не предоставлялись.Расширены возможности настройки истории изменения данных.
Средства администрирования.
Клиентское приложение.
Доработан механизм обновления клиентского приложения: при отсутствии на клиентском компьютере нужной версии, сразу начинается загрузка нужного клиентского приложения. В форме, отображающей процесс скачивания, имеется возможность отказаться от скачивания или войти в информационную базу с помощью веб-клиента (если база доступа по протоколу HTTP(s)).Если при попытке входа в информационную базу на клиентском компьютере отсутствовала нужная версия клиентского приложения, то вначале предлагалось выбрать, что делать дальше: обновить клиентское приложение или войти в информационную базу с помощью веб-клиента. После выбора необходимости обновления - запускался процесс скачивания и установки клиентского приложения.Ускорен процесс обновления клиентского приложения.
Система взаимодействия.
При использовании видеозвонков в тонком и веб-клиентах снижено использование центрального процессора клиентского компьютера и нагрузка на сетевое соединение. Нагрузка на процессор и сеть перестает зависеть от количества участников звонка.

Для получения эффекта от изменения, администратор должен выполнить следующие действия:

  • Обновить сервера системы взаимодействия до версии 26 или последующей.
  • Обновить систему «1С:Предприятие» до версии 8.3.26 или последующей.
  • Обновить видеосервер Janus до версии 1.0.4 или последующей.
При использовании видеозвонков в тонком и веб-клиентах наблюдалась повышенное использование центрального процессора клиентского компьютера и повышенная нагрузка на сетевое соединение. Нагрузка на процессор и сеть была тем выше, чем большим было число участников видеозвонка.Снижена нагрузка на систему при использовании групповых видеозвонков. Стало возможно увеличить количество пользователей, которые одновременно могут участвовать в видеозвонке.
Система взаимодействия.
Интерфейс видеозвонка на сайте внешних пользователей и чате на сайте стал аналогичен такому же интерфейсу в клиентских приложениях системы «1С:Предприятие».Интерфейс видеозвонка на сайте внешних пользователей и чате на сайте отличался от такого же интерфейса в клиентских приложениях системы «1С:Предприятие».Расширены возможности сайта для внешних пользователей.
Система взаимодействия.
В интерфейс включения демонстрации экрана видеозвонка системы взаимодействия в тонком клиенте внесены следующие изменения:
  • Порядок следования мониторов изменен на системный (соответствует расположению мониторов по горизонтали).
  • При выборе экрана или приложения для демонстрации убраны кнопки Ок и Отмена. Демонстрация начинается сразу, после выбора соответствующего объекта.
  • Форма выбора экрана или окна уменьшена в размерах по вертикали, чтобы помещаться на экранах с низким разрешением.
В интерфейс включения демонстрации экрана видеозвонка системы взаимодействия в тонком клиенте наблюдалось следующее поведение:
  • Мониторы следовали в алфавитном порядке.
  • Для выбора экрана или окна для демонстрации было необходимо вначале выбрать демонстрируемый объект, а затем нажать кнопку Ок.
  • Форма выбора экрана или окна не помещалась на экранах с низким разрешением (по вертикали).
Улучшен интерфейс выбора демонстрируемого монитора или окна в тонком клиенте.
Технологический журнал.
Реализована возможность отслеживать использование оперативной памяти полнотекстовым поиском. Для файла logcfg.xml реализован элемент <systemmemoryprofile>. Информация об использовании оперативной памяти отображается в событиях <system>.

Настройка отслеживания и описание формируемых событий - не документируется. Данная возможность предназначена для использования специалистами фирмы «1С».

Возможность отслеживать использование оперативной памяти полнотекстовым поиском не предоставлялась.При возникновении проблем с использованием памяти полнотекстовым поиском, специалисты фирмы «1С» могут предоставить готовый файл logcfg.xml, а в ответ получить файлы технологического журнала для анализа ситуации и решения возникших проблем.
Веб-клиент.
Клиентское приложение.
При работе под управлением операционных систем, предшествующих Windows 7, будет выводится предупреждение о том, что поддержка этих операционных систем будет прекращена в версии 8.3.27 и рекомендацией обновить операционную систему.

Предупреждение выводится один раза в месяц для уникальной комбинации пользователя, информационной базы, вида клиента/веб-браузера (если используется веб-клиент).

Предупреждение об отказе от поддержки устаревших версий операционной системы Windows не выводилось.Пользователя предупреждают о том, что в используемой им операционной системе будет невозможен запуск следующей версии системы «1С:Предприятие».

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Кластер серверов.
Оптимизировано использование процессора, оперативной памяти и сеансовых данных кластером серверов системы «1С:Предприятие».Ресурсы компьютера, на котором запущен кластер серверов системы «1С:Предприятие», использовались недостаточно эффективно образом.Улучшена производительность и масштабируемость кластера серверов системы «1С:Предприятие».
Средства разработки.
Оптимизирована операция проверки наличия циклических ссылок при включении соответствующего режима.Операция проверки наличия циклических ссылок, при включении соответствующего режима, занимала больше времени.Снижены накладные расходы, которые вносит механизм проверки наличия циклических ссылок, что позволит сократить время анализа проблемной операции.
Средства разработки.
Оптимизирован первый запуск конфигуратора после загрузки конфигурации.После загрузки конфигурации, первый запуск конфигуратора занимал много времени.Ускорен первый запуск конфигуратора после загрузки конфигурации.
Средства разработки.
Уменьшено время повторного запуска клиентского приложения из Конфигуратора.Повторный запуск клиентского приложения из Конфигуратора занимал много времени.Уменьшено время повторного запуска клиентского приложения из Конфигуратора.
Система взаимодействия.
Для системы взаимодействия:
  • Оптимизирован поиск по списку обсуждений.
  • При изменении списка участников обсуждений (свойство ОбсуждениеСистемыВзаимодействия.Участники) записываются только изменения.
  • Обращение с сервера «1С:Предприятия» к серверу системы взаимодействия выполняется с таймаутом в 45 секунд. Если за это время действие не было выполнено - формируется исключение.
Для системы взаимодействия:
  • Поиск по списку обсуждений занимал больше времени.
  • При изменении списка участников обсуждения (свойство ОбсуждениеСистемыВзаимодействия.Участники) записывался весь список.
  • Обращение с сервера «1С:Предприятия» к серверу системы взаимодействия выполняется без таймаута, что могло приводить к зависаниям сервера «1С:Предприятие».
Оптимизирована работа с сервером системы взаимодействия.
Полнотекстовый поиск.
При использовании полнотекстового поиска на больших информационных базах снижено использование оперативной памяти.

Для получения эффекта от оптимизации, необходимо выполнить переиндексацию индекса полнотекстового поиска.

Платформа «1С:Предприятие» версии 8.3.25 и предыдущих версий выполнит очистку индекса, если он был построен версией 8.3.26.

Механизмы полнотекстового поиска на больших информационных базах требовали большого количества оперативной памяти.Полнотекстовый поиск стал требовать меньшее количество ресурсов для своей работы.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Хранение настроек.
Реализована возможность получить доступ к стандартным хранилищам настроек, даже если заданы пользовательские хранилища настроек.

Реализованы методы глобального контекста

ПолучитьСтандартноеХранилищеВариантовОтчетов(), ПолучитьСтандартноеХранилищеВнешнихДанныхНавигационныхСсылок(), ПолучитьСтандартноеХранилищеНастроекДанныхФорм(), ПолучитьСтандартноеХранилищеОбщихНастроек(), ПолучитьСтандартноеХранилищеПользовательскихНастроекДинамическихСписков(), ПолучитьСтандартноеХранилищеПользовательскихНастроекОтчетов(). Методы возвращают значения типа СтандартноеХранилищеНастроекМенеджер.

В том случае, если в прикладном решении были установлены пользовательские хранилища настроек, получить доступ к соответствующему стандартному хранилищу было невозможно.Стало возможно при обновлении конфигурации выполнить перенос настроек из стандартного хранилища в пользовательское, если новая версия прикладного решения содержала пользовательское хранилище настроек, которое заменяет стандартное хранилище.
Кластер серверов.
Средства администрирования.
Реализована возможность указывать альтернативные каталоги данных для некоторых сервисов кластера серверов. При указании альтернативного каталога перенос данных автоматически не выполняется, его (перенос) необходимо выполнять вручную. Структура каталогов с данными при переносе не изменяется.

Возможность настройки переноса каталогов реализована в консоли кластера и в стандартной обработке Управление серверами.

Для объекта АдминистрированиеРабочийСервер реализованы методы СоздатьНастройкуСервиса(), ПолучитьНастройкуСервиса(), ПолучитьНастройкиСервисов(), ПолучитьКаталогиДанныхСервисаДляПереноса().

Свойство АдминистрированиеРабочийСервер.КаталогМоделейРаспознаванияРечи объявляется устаревшим и не рекомендуется к использованию.

Для объекта COM-соединителя IServerAgentConnection реализованы методы CreateServiceSetting(), GetServiceSettings(), RegServiceSetting(), DeleteServiceSetting(), GetServiceDataDirsForTransfer(), GetServiceSettingByID(), GetServiceSettingByParams(), GetSettingActive(), ApplyServiceSettings().

Удалено свойство IWorkingServerInfo.SppechToTextModelDirectory.

Для объекта Java-интерфейса IAgentAdminConnection реализованы методы createServiceSetting(), getServiceSettings(), regServiceSetting(), deleteServiceSetting(), getServiceDataDirsForTransfer(), getServiceSettingByID(), getServiceSettingByParams(), getSettingActive(), applyServiceSettings().

Удалено свойство IAgentAdminConnection.SppechToTextModelDirectory.

Для утилиты rac реализован новый режим service-setting. Для команд insert и update режима server удаляется параметр --speech-to-text-model-directory.

Возможность указывать альтернативные каталоги данных для некоторых сервисов кластера серверов требует наличие лицензии КОРП.

Данная возможность не предоставлялась.

Перенос каталогов мог быть выполнен только средствами используемой операционной системы, что было не очевидно и непонятно для пользователя.

Стало возможно размещать данные кластера по разным дисковым накопителям для общего повышения производительности системы.
В документации данное изменение описано здесь, здесь и здесь.
Хранилище двоичных данных.
Реализована возможность указания объектов конфигурации, данные которых могут быть размещены в хранилище двоичных данных. Указание объектов может выполняться как в Конфигураторе, так и во время исполнения (из встроенного языка или с помощью стандартной функции).

Для менеджера хранилища двоичных данных реализованы методы УстановитьСоставХранимыхДанных(), ПолучитьСоставХранимыхДанных(), УстановитьИспользованиеКакХранилищаПоУмолчанию(), ПолучитьИспользованиеКакХранилищаПоУмолчанию(),

Для менеджера внешнего хранилища двоичных данных реализованы свойства СоставХранимыхДанных и ХранилищеПоУмолчанию.

Для реквизитов и ресурсов объектов конфигурации типа ХранилищеЗначения реализованы свойства ИспользованиеХраненияВХранилищеДвоичныхДанных и ПолеИспользованияХраненияВХранилищеДвоичныхДанных.

Доработана стандартная обработка Управление хранилищем двоичных данных.

Данная возможность не предоставлялась.

Существовало только ограничение на минимальный объем двоичных данных, которые попадали во внешнее хранилище. Было невозможно ограничить состав объектов конфигурации, данные которых могли попадать в хранилище двоичных данных.

Стало возможно управлять возможностью записи данных в хранилище двоичных данных не только по реквизитам объектов конфигурации, но и по конкретным данным, которые записываются в информационную базу.
В документации данное изменение описано здесь и здесь.
Работа с ZIP-архивами.
Реализована возможность распаковки архивов следующих форматов: GZIP, RAR, 7-ZIP, XZ, TAR. Возможность упаковки в эти форматы не поддерживается.

Реализованы объекты ЧтениеФайлаАрхива и ЗаписьФайлаАрхива. Реализовано свойство КатегорияОшибки.НеподдерживаемыйФормат.

Объекты ЧтениеZipФайла и ЗаписьZipФайла (и связанные объекты) объявляются устаревшими и не рекомендуются к использованию.

Данная возможность не предоставлялась.Стало возможно получать данные в архивах, которые упакованы не только в формате zip-файлов.
В документации данное изменение описано здесь.
Кластер серверов.
Реализована возможность изменять параметры системы отслеживания разрыва соединений без перезапуска процессов кластера. Данные возможности реализованы для всех средств администрирования: консоль кластера, COM-соединение, интерфейс администрирования из языка Java, сервер администрирования.

Для объекта АдминистрированиеКластер реализованы свойства ПериодПроверкиСоединения и ТаймаутПроверкиСоединения. Для объекта IClusterInfo реализованы свойства

PingPeriod и PingTimeout.

В консоли кластера (и стандартной функции Управление серверами) реализована возможность редактирования параметров Таймаут проверки и Период проверки в форме редактирования параметров кластера.

Для команды rac cluster update реализованы параметры --ping-period и --ping-timeout. В результат работы команды rac cluster info добавлена информация о текущих значениях параметров --ping-period и --ping-timeout.

В интерфейсе работы с сервером администрирования из языка Java для объекта IClusterInfo реализованы методы getPingPeriod(), setPingPeriod(), getPingTimeout(), setPingTimeout().

Изменять параметры системы отслеживания разрыва соединений можно было только путем перезапуска процессов кластера, т.к. эти параметры указывались в командной строке запуска агента сервера (ragent).Для администраторов кластера серверов реализована возможность настройки системы проверки соединений без перезапуска процессов кластера. Эта возможность может быть использована для настройки работы кластера в текущих условиях сети или выполнения длительных служебных операций (например, миграции данных).
В документации данное изменение описано здесь и здесь.
Регистры сведений.
Регистры накопления.
Для подчиненных регистров сведений и накопления реализована поддержка возможности обновления и удаления записей (дополнительно к добавлению и замещению). Использование режима записи РежимЗамещения.Слияние не поддерживается. Поведение аналогично таковому для независимых регистров сведений.

Возможность регулируется свойством РасширенныеРежимыЗамещения набора записей регистров, которое оказывает влияние только при работе с подчиненными регистрами сведений и накоплений. Если свойство установлено в значение Истина, то становится возможно использование удаления и замещения записей, изменение свойства НомерСтроки записи набора, а также указание поддерживаемых значений системного перечисления РежимЗамещения в качестве значения параметра Замещать метода Записать() подчиненных регистров сведений и накопления.

Для набора записей подчиненного регистра сведений и накопления поддерживалась возможность только добавления или полного замещения существующих записей в информационной базе.В некоторых сценариях становится возможно существенно ускорить работу с подчиненными регистрами сведений и накопления.
В документации данное изменение описано здесь, здесь и здесь.
Копии базы данных.
Ошибки, возникающие во время выполнения запроса к СУБД копии базы данных, делятся на восстановимые и не восстановимые. Восстановимые ошибки не приводят к отключению копии базы данных и допускают дальнейшее выполнение запросов из прикладного решения к такой копии. Не восстановимые ошибки приводят к отключению копии базы данных с невозможностью дальнейшего выполнения запросов из прикладного решения.

Перечень восстановимых и не восстановимых ошибок различается в режиме совместимости с версией 8.3.24 и с отключенным режимом совместимости.

Любая ошибка, возникающие во время выполнения запроса к СУБД копии базы данных, приводила к отключению такой копии от информационной базы и невозможности дальнейшего выполнения запросов в такой копии. При попытке выполнить на копии базы данных запрос, не учитывающий возможные особенности данных, будет сформировано исключение, но копия базы данных не отключится, другие запросы смогут выполнять запросы в этой копии.
Работа с PDF-документами.
Реализована возможность определения параметров страницы в документе PDF.

Реализовано свойство ДокументPDF.Страницы.

Для методов ДобавитьОтображаемыйОбъект(), ДобавитьОтображаемыйОбъектАсинх(), ДобавитьПодпись() и ДобавитьПодписьАсинх() объекта ДокументPDF реализован необязательный параметр УчитыватьОриентациюСтраницы.

Данная возможность не предоставлялась.Расширены возможности работы с pdf-документами.
В документации данное изменение описано здесь.
Клиентское приложение.
Журнал регистрации.
Средства администрирования.
Веб-клиент.
Переработана форма аутентификации клиентского приложения. Реализована возможность отображения на форме аутентификации всех доступных видов аутентификации, с возможностью быстрого выбора требуемого вида аутентификации. Реализована возможность запомнить параметры последней аутентификации пользователя для тонкого, толстого и веб-клиентов. Реализовано отображение 4 последних имен успешно аутентифицированных пользователей в списке выбора пользователя. Сплеш при аутентификации отображается до появления диалога аутентификации и после успешного входа в информационную базу.

Изменена полезная нагрузка, которая используется клиентским приложением в при аутентификации с помощью JWT.

Для запрета аутентификации тем или иным способом, необходимо или запретить аутентификацию этим способом или сменить пароль у скомпрометированного пользователя (пользователей). В случае смены пароля все сохраненные токены доступа становятся недействительными.

Реализована команда запуска клиентского приложения /ResetSavedAuth, которая сбрасывает параметры последней успешной аутентификации.

Реализованы параметры дополнительной аутентификации пользователей: Разрешить сохранение аутентификации, Сохранять аутентификацию по умолчанию, Время жизни сохраненной аутентификации.

Для менеджера дополнительных настроек аутентификации реализованы методы ПолучитьНастройкиАвтоматическогоСохраненияАутентификации(), УстановитьНастройкиАвтоматическогоСохраненияАутентификации().

Для элемента <point> файла default.vrd реализован элемент <authentication>, с помощью которого можно настроить вид аутентификации по умолчанию и доступные виды аутентификации для данной информационной базы.

Расширен состав информации для событий журнала регистрации:

  • _$InfoBase$_.AdditionalAuthenticationSettingsUpdate.
  • _$Session$_.Authentication.
  • _$Session$_.AuthenticationError.
  • _$Session$_.AuthenticationFirstFactor.
Данные возможности не предоставлялись.

Запомнить последнего аутентифицированного пользователя можно было только при OpenID Connect аутентификации.

Улучшен интерфейс диалога аутентификации пользователя. Реализована возможность настройки нужного типа аутентификации как вида аутентификации по умолчанию. Реализовано запоминание данных для повторного входа для всех видов аутентификации.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Система взаимодействия.
Для групповых обсуждений реализована возможность поиска в списке участников.

Для групповых обсуждений с большим количеством участников (более 100 участников) реализована асинхронная загрузка списка участников, которая выполняется по запросу. В групповом обсуждении не могут участвовать более 3000 участников.

Реализована возможность создавать обсуждение в режим «только просмотр». В таком обсуждении недоступно интерактивные действия, связанные с добавлением/изменением обсуждения. Изменение с помощью встроенного языка не ограничивается. Реализовано свойство ОбсуждениеСистемыВзаимодействия.ТолькоПросмотр.

Поиск среди участников групповых обсуждений не поддерживался.

Список участников группового обсуждения загружался всегда и сразу.

Отсутствовало ограничение на максимальное количество участников группового обсуждения.

Отсутствовала возможность создания обсуждения, которое недоступно для интерактивного использования.

Улучшена работа системы взаимодействия с групповыми обсуждениями, в которых принимает участие большое количество участников.
В документации данное изменение описано здесь и здесь.
Динамический список.
Реализована возможность управлять отображением на форме строки поиска динамического списка. Реализована возможность принудительно включать и выключать строку поиска, а также выключать строку поиска при невозможности эффективно использовать полнотекстовый поиск. Данная возможность доступа только из встроенного языка через хранилище системных настроек.

Реализован объект НастройкиОтображенияДинамическогоСписка.

Для системного хранилища настроек реализованы настройки НастройкиОтображенияДинамическогоСписка и НастройкиОтображенияДинамическихСписков.

Данная возможность не предоставлялась.

В ряде случаев полнотекстовый поиск (который используется строкой поиска) мог работать не эффективно или неверно.

Стало возможно указать необходимость использования строки поиска как конкретного динамического списка, так и всех динамических списков прикладного решения.
В документации данное изменение описано здесь и здесь.
Хранилище двоичных данных.
Реализована возможность блочного хранения двоичных данных в информационной базе системы «1С:Предприятие» (только в клиент-серверном варианте использования). В режиме совместимости Версия 8.3.25 и предшествующих, возможность управляется с помощью свойства конфигурации Режим использования блочного хранения двоичных данных. В остальных случаях возможность считается всегда включенной и не может быть отключена.

Для встроенного хранилища двоичных данных реализована возможность управления тем, где будут храниться двоичные данные, которые должны быть записаны в хранилище двоичных данных: только в хранилище двоичных данных или одновременно в информационной базе и хранилище. Если выбран режим одновременного хранения, то информационная база сохранит работоспособность в том случае, если встроенное хранилище двоичных данных будем разрушено или утеряно.

Для менеджера хранилища двоичных данных реализованы методы ПолучитьРежимРазмещенияКопийДанныхВХранилищеДвоичныхДанных() и УстановитьРежимРазмещенияКопийДанныхВХранилищеДвоичныхДанных().

Данная возможность не предоставлялась.

При подключении хранилища двоичных данных, данные могли храниться только в этом хранилище.

Стало возможно конвертировать информационную базу, в которой хранятся двоичные данные размером более 1 Гбайт, между Microsoft SQL Server и PostgreSQL.

Повышена надежность хранения двоичных данных при использовании внешнего хранилища двоичных данных. Если используется совместное хранение, то для операций резервного копирования достаточно копировать только информационную базу.

В документации данное изменение описано здесь.
Тестирование и исправление информационной базы.
Хранилище двоичных данных.
Если при выполнении проверки целостности хранения двоичных данных (во время выполнения операции тестирования и исправления информационной базы) были обнаружены объекты информационной базы с ошибкой двоичных данных (хранилище двоичных данных недоступно, двоичные данные удалены из хранилища или не существуют в хранилище), то система выводит информацию, которая позволит идентифицировать проблемный объект.При выполнении проверки целостности хранения двоичных данных (во время выполнения операции тестирования и исправления информационной базы), в случае возникновения проблем с двоичными данными, диагностическая информация система не позволяла понять, с какими объектами связана проблема.Упрощено определение объектов, в которых наблюдаются проблемы с двоичными данными, которые перенесены в хранилище двоичных данных.
Система взаимодействия.
Реализована поддержка вложений для интеграции типа вебхук.

Для запроса интерфейса взаимодействия createMessage реализованы необязательные параметры data и datаType. Для объекта СообщениеСистемыВзаимодействие реализовано свойство ФорматДанныхСтроки.

Данная возможность не предоставлялась.Для интеграции типа вебхук стало возможно передавать данные в систему «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Реализована возможность приглашать внешних пользователей в обсуждение и видеозвонок. Приглашение выполняется через навигационную ссылку специального вида. Воспользоваться ссылкой может как внешний, так и внутренний пользователь. Приглашение может позволить полноценно участвовать в обсуждении или участвовать только в видеозвонках (указывается при формировании приглашения).

Получить ссылку можно при создании нового обсуждения, в диалоге добавления участников обсуждения/видеозвонка или в меню формы внеконтекстного обсуждения.

Пользовательский интерфейс системы взаимодействия доработан с учетом новых возможностей.

Реализована возможность отзыва всех выданных приглашений для участия в обсуждении.

Для менеджера системы взаимодействия реализован метод ПолучитьНавигационнуюСсылкуПриглашенияВОбсуждение().

Подключить внешнего (или внутреннего) пользователя к видеозвонку по ссылке было невозможно. Вначале внешнего пользователя было необходимо пригласить на сайт внешних пользователей и только после этого начать видеозвонок.Пользователи смогут самостоятельно подключаться к видеозвонку, для этого не требуется, чтобы существующие участники обсуждения звонили новому участнику.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.19.Версия формата выгрузки конфигурации в XML-файлы была равна 2.18.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.
Работа с запросами.
Если в качестве операнда функций языка запросов СУММА() и СРЕДНЕЕ() выступает определяемый тип, то результатом работы функций будет число без ограничения размерности.

Ресурс регистра бухгалтерии, имеющий определяемый тип, будет иметь длину 38 разрядов и точность, описываемую определяемым типом.

Если в качестве операнда функций языка запросов СУММА() и СРЕДНЕЕ() выступает определяемый тип, то результатом работы функций было число с параметрами (длина и точность), которые указаны в определяемом типе.

Ресурс регистра бухгалтерии, имеющий определяемый тип, имел параметры (длину и точность) описываемую определяемым типом.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Сервис интеграции.
Автономный сервер.
В документации отражено, что автономный сервер не поддерживает сервисы интеграции. Изменение внесено в документацию, начиная с версии 8.3.21.В документации ошибочно отсутствовало указание на то, что автономный сервер не поддерживает сервисы интеграции.Исправлена ошибка документации.
Копии базы данных.
Установка текста запроса (свойство Запрос.Текст) или вызов методов объекта Запрос не приводят к изменению значений свойств ИспользованиеКопийБазыДанных и ИспользуемыеКопииБазыДанных объекта Запрос.

В режиме совместимости с версией 8.3.25 поведение не изменилось.

Установка текста запроса (свойство Запрос.Текст) или вызов методов объекта Запрос приводил к установке свойства Запрос.ИспользованиеКопийБазыДанных в значение ИспользованиеКопийБазыДанных.Авто и очистке свойства Запрос.ИспользуемыеКопииБазыДанных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Средства администрирования.
Реализована возможность выбора алгоритма хеширования паролей пользователей информационной базы системы «1С:Предприятие» из следующих алгоритмов: SHA-1, SHA-256, SHA-512, PBKDF2-HMAC-SHA256. Алгоритм хеширования настраивается в параметрах информационной базы. Если алгоритм хеширования отличается от SHA-1, то с информационной базой можно работать только с использованием системы «1С:Предприятие» версии 8.3.26 и последующих версий.

Для объекта ХешированиеДанных реализована возможность работы с алгоритмом хеширования PBKDF2-HMAC-SHA256.

Реализованы методы глобального контекста ПолучитьТипАлгоритмаХешированияПаролейПользователя(), УстановитьТипАлгоритмаХешированияПаролейПользователя(), ВычислитьСохраняемоеЗначениеПароляПользователя(), ПроверитьСоответствиеПароляПользователяСохраняемомуЗначению().

Реализовано свойство системного перечисления ХешФункция.PBKDF2SHA256.

Реализовано свойство ПользовательИнформационнойБазы.ТипАлгоритмаХешированияПароля.

В данные событий журнала регистрации _$InfoBase$_.ParametersUpdate, _$InfoBase$_.ParametersUpdateError, _$User$_.New, _$User$_.NewError, _$User$_.Update, _$User$_.UpdateError добавлена информация об используемом алгоритме хеширования.

Для хеширования паролей пользователей информационной базы системы «1С:Предприятие» всегда использовался алгоритм SHA-1.Стало возможно использовать более стойкие алгоритмы хеширования паролей паролей пользователей информационной базы.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Средства администрирования.
Реализована поддержка протокола ЕСИА версии 3.34.

Для секции clientconfig описания провайдера OpenID Connect в файле default.vrd реализован параметр client_certificate_hash, который необходим для работы по новой версии протокола.

Сохранена возможность использовать предыдущую версию протокола ЕСИА.

Данная возможность не предоставлялась.Реализована поддержка актуальной версии протокола ЕСИА.
В документации данное изменение описано здесь.
Средства администрирования.
Реализована возможность указывать время периода бездействия, после которого сеанс пользователя будет принудительно завершен. Данная возможность поддерживается в тонком, толстом, мобильном и веб-клиентах. В Конфигураторе данная возможность не поддерживается. Перед завершением сеанса пользователь получит предупреждение, отреагировав на которое можно отказаться от принудительного завершения сеанса.

В диалоге настройки параметров информационной базы реализованы параметры Время предупреждения о завершении сеанса при бездействии и Время завершения сеанса при бездействии. Реализованы методы глобального контекста УстановитьВремяПредупрежденияОЗавершенииСеансаПриБездействии(), ПолучитьВремяПредупрежденияОЗавершенииСеансаПриБездействии(), УстановитьВремяЗавершенияСеансаПриБездействии(), ПолучитьВремяЗавершенияСеансаПриБездействии().

Расширен состав информации для событий журнала регистрации:

  • _$InfoBase$_.ParametersUpdate.
  • _$InfoBase$_.ParametersUpdateError.

Использование механизма принудительного завершения сеансов по времени бездействия требует наличие лицензии КОРП.

Данная возможность не предоставлялась.Снижена вероятность несанкционированного доступа к данным информационной базы.

Снижен расход лицензий за счет отключения пользователей, которые ничего не делают в информационной базе длительный промежуток времени.

В документации данное изменение описано здесь и здесь.
Сервис интеграции.
Параметр МаксимальноеКоличество метода ВыбратьСообщения() менеджера канала сервиса интеграции используется в соответствии с названием: возвращаются сообщения канала сервиса интеграции в количестве, не превышающем значение указанное параметра.

В режиме совместимости с версией 8.3.25 поведение не изменилось.

При вызове метода ВыбратьСообщения() менеджера канала сервиса интеграции игнорировалось значение параметра МаксимальноеКоличество. Метод всегда возвращал все сообщения канала сервиса интеграции.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Сервис интеграции.
Если в структуре отбора метода ВыбратьСообщения() менеджера канала сервиса интеграции параметра отбора ИдентификаторСообщенияЗапроса установлен в значение нулевого уникального идентификатора (NIL UUID, значение из одних нулей), то возвращаются сообщения, у которых идентификатор сообщения запроса равен нулевому уникальному идентификатору.

В режиме совместимости с версией 8.3.25 поведение не изменилось.

Если в структуре отбора метода ВыбратьСообщения() менеджера канала сервиса интеграции параметра отбора ИдентификаторСообщенияЗапроса установлен в значение нулевого уникального идентификатора (NIL UUID, значение из одних нулей), то такое значение отбора игнорировалось и возвращались все сообщения канала.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Специальные возможности мобильного устройства.
В мобильной версии системы «1С:Предприятие» реализована поддержка мобильных сервисов магазина приложений RuStrore:
  • Встроенные покупки.
  • Push-уведомления.
  • Картография и работа с координатами.
  • Оценка приложений в магазине.

Если мобильное приложение собрано с поддержкой всех мобильных сервисов, то сервисы RuStore имеют приоритет на остальными мобильными сервисами. В сборщике мобильных приложений реализована возможность включения/отключения использования модулей работы с сервисами RuStrore (по аналогии с мобильными сервисами Google и Huawei), а также реализована возможность указания параметров, необходимых для успешной сборки приложений для RuStore.

Реализованы значения системных перечислении ТипПодписчикаДоставляемыхУведомлений.RMS и СервисВстроенныхПокупок.RuStoreInAppPurchase.

Метод ПолучитьМаркерДоступа() менеджера отправки доставляемых уведомлений учитывает возможности использования сервисов RuStrore.

В мобильной версии системы «1С:Предприятие» мобильных сервисов магазина приложений RuStrore не поддерживались. Из-за этого было невозможно разрабатывать мобильные приложения, которые не могли распространяться через магазины Google Play и Huawei AppGallery.Расширен перечень поддерживаемых мобильных сервисов.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Копии базы данных.
Расширение конфигурации.
Если к информационной базе подключено расширение, которое расширяет данные (или содержит собственные объекты с данными), то таблицы таких объектов не могут быть перенесены в копию информационной базы. Если в копии базы данных уже есть таблицы таких объектов, то при обновлении копии такие таблицы будут удалены из копии.Если к информационной базе подключено расширение, которое расширяет данные (или содержит собственные объекты с данными), то система «1С:Предприятие» работала некорректно. Устранено некорректное поведение системы.
Полнотекстовый поиск.
Ускорено слияние индексов полнотекстового поиска. Во время слияния повышено использование процессора компьютера. Полное слияние индексов возможно только в том случае, когда при вызове метода ОбновитьИндекс() менеджера полнотекстового поиска, параметр метода РазрешитьСлияние установлен в значение Истина. Слияние индексов полнотекстового поиска занимало больше времени. Полное слияние могло выполняться при добавлении в индекс поиска новой порции данных.Ускорено слияние индексов полнотекстового поиска. Устранено непрогнозируемое полное слияние индексов при добавлении новой порции данных.
Работа с СУБД.
Тестирование и исправление информационной базы.
Реализован параметр информационной базы Использовать дополнительные индексы. Реализованы методы УстановитьИспользованиеДополнительныхИндексов() и ПолучитьИспользованиеДополнительныхИндексов(). При включении параметра проверяется наличие лицензии КОРП.

Реализован режим тестирования и исправления информационной базы Проверка и включение функциональности КОРП.

Реализован параметр -CheckAndEnableCORPFunctionality команды /IBCheckAndRepair.

Данная возможность не предоставлялась.Реализовано управление возможностью физического создания дополнительных индексов в информационной базе.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Прекращена поддержка СУБД IBM Db2 всех версий, до версии 10.1 включительно.

Поддерживается СУБД IBM Db2 только версии 11.1.

Для СУБД IBM Db2 поддерживались версии 9.1, 9.5, 9.7, 10.1.Прекращена поддержка устаревших версий СУБД IBM Db2.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro Enterprise: 12.20.2, 13.16.2, 14.13.2, 15.8.2;
  • Postgres Pro CERT Enterprise: 13.16.2, 14.13.2, 15.8.2.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1С: 17.0;
  • Postgres Pro Standard: 17.0.1;
  • Postgres Pro Enterprise: 16.4.2;
  • Postgres Pro CERT Enterprise: 16.4.2.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа в ОС Linux.
Прекращена поддержка следующих дистрибутивов операционной системы Linux:
  • CentOS 7.
  • Oracle Linux 7.
  • Red Hat Enterprise Linux 7.
  • Астра Linux Common Edition 2.12.
Система «1С:Предприятие» поддерживала работу в следующих дистрибутивах операционной системы Linux::
  • CentOS 7.
  • Oracle Linux 7.
  • Red Hat Enterprise Linux 7.
  • Астра Linux Common Edition 2.12.
Прекращена поддержка устаревших дистрибутивов операционной системы Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1С: 12.22, 13.18, 14.15, 15.10;
  • Postgres Pro Standard: 12.22.1, 13.18.1, 14.15.1, 15.10.1;
  • Postgres Pro Enterprise: 12.22.1, 13.18.1, 14.15.1, 15.10.1;
  • Postgres Pro CERT Standard: 14.15.1, 15.10.1;
  • Postgres Pro CERT Enterprise: 13.18.1, 14.15.1, 15.10.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1С: 16.6, 17.2;
  • Postgres Pro Standard: 16.6.1, 17.2.1;
  • Postgres Pro Enterprise: 16.6.1;
  • Postgres Pro CERT Standard: 16.6.1, 17.2.1;
  • Postgres Pro CERT Enterprise: 16.6.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Работа с Интернет.
Средства администрирования.
Аутентификация с помощью OpenID считается приоритетным способом аутентификации, если этот способ настроен для информационной базы. Общая форма аутентификации отображается только в том случае, если пользователь явно выполнил операцию logout в провайдере OpenID аутентификации или предъявленные логин и пароль вызывают ошибку аутентификации провайдера. В остальных случаях система пытается использовать настроенную аутентификацию до того, как отображать пользователю какие-либо формы ввода.

Если для информационной базы настроена аутентификация OpenID Connect, то при запуске веб-клиента выполняется попытка выполнить аутентификацию у провайдера по параметрам последней успешной аутентификации. Общая форма аутентификации будет отображаться в том случае, если веб-клиент не смог осуществить аутентификацию OpenID Connect.

Если для информационной базы была настроена аутентификация OpenID, то диалог для подтверждения входа (и содержащий список доступных видов аутентификации) отображался при каждой попытке входа в приложение.Аутентификация в приложении стала более однозначной и ожидаемой.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro Enterprise: 17.2.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.26 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.26 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Tantor SE 1C версий 14.15.0, 15.10.0 и 16.6.0.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данная версия СУБД Tantor SE не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Клиентское приложение.
Средства администрирования.
В протокол работы OpenID-провайдера, реализованного в платформе «1С:Предприятие», внесены изменения, направленные на обеспечение обратной совместимости. Рекомендуется обновить клиентские приложения.

Для тонкого клиента версии 8.3.26 реализовано сохранение признака аутентификации по умолчанию при использовании OpenID-провайдера, работающего на платформе «1С:Предприятие» версии 8.3.25 и предыдущих версий.

Для OpenID-провайдера, работающего на платформе «1С:Предприятие» версии 8.3.26, реализована возможность обслуживать клиентские приложения версии 8.3.25 и предыдущие версии.

Для тонкого клиента версии 8.3.26 признак аутентификации по умолчанию не отображался и не запоминался при использовании OpenID-провайдера, работающего на платформе «1С:Предприятие» версии 8.3.25 и предыдущих версий.

Клиентские приложения версии 8.3.25 (и предшествующие версии) получали неожиданные ответы от OpenID-провайдера, работающего на платформе «1С:Предприятие» версии 8.3.26, в результате корректная работа такой связки была невозможна.

Восстановлена обратная совместимость OpenID-провайдера версии 8.3.26 и клиентских приложений предыдущих версий. Клиентские приложения версии 8.3.26 могут работать с OpenID-провайдером версии 8.3.25 и предыдущих версий.
В документации данное изменение описано здесь.
Двоичные данные.
При одновременных попытках удаления и чтения записи базы данных, содержащей двоичные данные, не возникает ситуаций, которая закачивается ошибкой чтения двоичных данных.При одновременных попытках удаления и чтения записи базы данных, содержащей двоичные данные, могла возникнуть ситуация, которая заканчивалась ошибкой чтения двоичных данных.Устранен конфликт, который может возникать при одновременных попытках удаления и чтения записи, содержащей двоичные данные.

Оглавление

Переход с предыдущей версии на версию 8.3.26

Оглавление

Версия 8.3.25

Версия 8.3.25 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8325doc) документации к текущей версии.

Механизм хранилища двоичных данных вышел из статуса бета-версии.

Для использования механизма требуется лицензия уровня КОРП.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.24.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.23. +Возможность запуска конфигураций, разработанных в версии 8.3.24 и более младших, в версии 8.3.25, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.25 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.25, при необходимости, использовать для работы с информационной базой и версию 8.3.24. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Синтез речи.
Реализована возможность синтеза речи.

Для менеджера работы с речью реализованы методы: НачатьСинтез(), ОстановитьСинтез(), Синтезировать(), ПолучитьДоступныеГолосаСинтеза().

Реализованы объекты: ОписаниеГолосаСинтезаРечи, ОписаниеПараметраГолосаСинтезаРечи, ОписаниеЗначенияПараметраГолосаСинтезаРечи.

Синтез речи не поддерживается при работе под управлением операционных систем Windows XP и Windows Server 2003.

Платформа «1С:Предприятие» не содержала встроенных механизмов синтеза речи.Реализована возможность синтеза речи. С помощью средств платформы стала возможна реализация голосовых интерфейсов с пользователем.
В документации данное изменение описано здесь и здесь.
Общие объекты.
Реализован метод глобального контекста ВызватьПаузу(). Метод доступен только на сервере. Метод недоступен в серверных вызовах, которые инициированы клиентским приложением.Данная возможность не предоставлялась.В серверном коде (фоновые и регламентные задания, Интернет-сервисы и т.д.) реализована возможность приостанавливать выполнение кода на встроенном языке.
Хранилище двоичных данных.
Средства администрирования.
Для Конфигуратора реализован инструмент (Главное меню - Администрирование - Управление хранилищем двоичных данных), по своим возможностям аналогичный стандартной функции Управление хранилищем двоичных данных.В Конфигураторе было недоступно управление хранилищем двоичных данных.В Конфигураторе стало возможно выполнять тот же набор операций, который был доступен с помощью стандартной функции, которая могла быть вызвана только в случае успешного запуска клиентского приложения с данной информационной базой.
В документации данное изменение описано здесь.
Хранилище двоичных данных.
Для механизма хранилища двоичных данных реализована возможность дедупликации фрагментов двоичных данных формата Microsoft Compound Binary File (CBF, файлы Microsoft Office 2003 и предшествующих версий). Данный процесс не управляется и не контролируется пользователем. Дедупликации подвержены файлы, к которым не было обращений более 2 месяцев.Данная возможность не предоставлялась. Дедуплицировались только файлы целиком.При хранении большого количества файлов Microsoft Office 2003 и предшествующих версий, может быть уменьшено дисковое пространство для хранения этих данных за счет исключения повторяющихся фрагментов таких файлов,
В документации данное изменение описано здесь.
Работа с запросами.
В языке запросов реализованы возможности:
  • Добавлять данные в ранее созданную временную таблицу (реализовано предложение ДОБАВИТЬ).
  • Индексировать временную таблицу по наборам полей (реализовано предложение ИНДЕКСИРОВАТЬ ПО НАБОРАМ).
  • Создавать уникальные индексы во временных таблицах (реализована опция УНИКАЛЬНО для предложений ИНДЕКСИРОВАТЬ ПО и ИНДЕКСИРОВАТЬ ПО НАБОРАМ).

Для объекта ЗапросВыбораСхемыЗапроса:

  • Реализовано свойство Индексы.
  • Реализовано свойство ТаблицаДляДобавления.
  • Свойство Индекс объявлено устаревшим и не рекомендуется для использования.

Рекомендуется рассмотреть возможность использования новых возможностей в следующих случаях:

  • Выполняется выборка данных из одной временной таблицы, объединение с другими данными и помещение в новую временную таблицу.
  • Выполняются многократные запросы к одной и той же временной таблице с отбором либо соединением по разным полям (наборам полей).
Данные возможности не предоставлялись.Расширены возможности работы с временными таблицами в языке запросов.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Расширение конфигурации.
Реализована возможность заимствовать бизнес-процессы и задачи. Для заимствованных объектов, в числе прочих, допускается изменение карты маршрута бизнес-процесса, которая полностью заменяет карту маршрута расширяемой конфигурации при загрузке расширения.

Реализована возможность создавать в расширениях собственные бизнес-процессы и задачи. +

Данные возможности не предоставлялись.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Средства администрирования.
При добавлении нового рабочего сервера реализована возможность отключить назначение на этот сервер любой функциональности. Для этого создается запрещающее требование назначения функциональности, которое автоматически применяется.

Реализовано:

  • В диалоге создания нового рабочего сервера флажок Установить запрещающее требование назначения функциональности.
  • Для метода COM-соединения IServerAgentConnection.RegWorkingServer() реализован параметр УстановитьЗапрещающееТребованиеНазначенияФункциональности.
  • Для метода Java-интерфейса IAgentAdminConnection.regWorkingServer() реализован параметр AddProhibitingAssignmentRule.
  • Для режима server утилиты rac реализован параметр add-prohibiting-assignment-rule.
  • Для метода АдминистрированиеРабочийСервер.Записать() реализован параметр УстановитьЗапрещающееТребованиеНазначенияФункциональности.
Данная возможность не предоставлялась.

На новый рабочий сервер сразу начинали назначаться новые функциональности, что могло приводить к различным ошибкам из-за того, что новый рабочий сервер не был настроен до конца.

Упрощена настройка нового рабочего сервера администратором после добавления его (рабочего сервера) в кластер серверов.
В документации данное изменение описано здесь.
Кластер серверов.
Средства администрирования.
Для полей Профиль безопасности и Профиль безопасности безопасного режима свойств информационной базы реализована возможность выбора профиля безопасности из списка существующих профилей безопасности. Для поля Счетчик потребления ресурсов свойств ограничения потребления ресурсов реализована возможность выбора имени счетчика из списка существующих счетчиков потребления ресурсов.

Сохранена возможность ввода имени профиля безопасности и счетчика потребления ресурсов вручную.

Данные возможности реализованы в консоли кластера и стандартной обработке управления кластером серверов.

Данные возможности не предоставлялись. Ввод имен профилей безопасности и счетчиков безопасности выполнялся только вручную.Снижена вероятность ошибочного ввода:
  • имени профиля безопасности во время редактирования свойств информационной базы.
  • имени счетчика потребления ресурсов во время редактирования ограничений потребления ресурсов.
В документации данное изменение описано здесь и здесь.
Средства администрирования.
При работе с файловым вариантом информационной базы расширен список мест, в которых система «1С:Предприятие» выполняет поиск параметров ExternalSessionManagementRequired и ExternalSessionManagementConnectionString в файлах conf.cfg.При работе с файловым вариантом информационной базы система «1С:Предприятие» выполняла поиск параметров ExternalSessionManagementRequired и ExternalSessionManagementConnectionString в файле conf.cfg, который располагается в каталоге информационной базы или по пути, который указан в параметре ConfLocation конфигурационного файла, расположенного в каталоге информационной базы.Стало возможно более гибко управлять размещением настроек сервиса внешнего управления сеансами при работе с файловым вариантом информационной базы.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Средства администрирования.
Реализована возможность управления нагрузкой на кластер серверов для информационных баз с низкой активностью пользователей:
  • Минимальный период запуска регламентных заданий без активных пользователей.
  • Максимальный сдвиг запуска регламентных заданий без активных пользователей.
  • Задержка выгрузки конфигурации рабочим процессом без активных пользователей.

Реализованы:

  • Параметры информационной базы (в консоли кластера и стандартной обработке): Задержка выгрузки конфигурации рабочим процессом, Минимальный период запуска регламентных заданий, Максимальный сдвиг запуска регламентных заданий.
  • Свойства объекта IInfoBaseInfo COM-соединения: ConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers, MinimumScheduledJobsRunningPeriodWithoutActiveUsers, MaximumScheduledJobsStartShiftWithoutActiveUsers.
  • Методы объекта IInfoBaseInfo Java-интерфейса: getConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers(), setConfigurationUnloadDelayByWorkingProcessWithoutActiveUsers(), getMinimumScheduledJobsStartPeriodWithoutActiveUsers(), setMinimumScheduledJobsStartPeriodWithoutActiveUsers(), getMaximumScheduledJobsStartShiftWithoutActiveUsers(), setMaximumScheduledJobsStartShiftWithoutActiveUsers().
  • Параметры режима infobase утилиты rac: configuration-unload-delay-by-working-process-without-active-users, minimum-scheduled-jobs-start-period-without-active-users, maximum-scheduled-jobs-start-shift-without-active-users.
  • Свойства объекта АдминистрированиеИнформационнаяБаза: ЗадержкаВыгрузкиКонфигурацииРабочимПроцессомБезАктивныхПользователей, МинимальныйПериодЗапускаРегламентныхЗаданийБезАктивныхПользователей, МаксимальныйСдвигЗапускаРегламентныхЗаданийБезАктивныхПользователей.
Данная возможность не предоставлялась.Стало возможно управлять поведением регламентных заданий для информационных баз с низкой активностью пользователей.
В документации данное изменение описано здесь и здесь.
Средства администрирования.
Технологический журнал.
Реализована возможность:
  • Управления размещением файлов технологического журнала: в структуре каталогов или в плоском списке файлов. Реализован атрибут placement элемента log файла настройки технологического журнала logcfg.xml.
  • Настройки ротации файлов журнала: по времени или по размеру файла журнала. Реализована возможность указания критериев ротации: размер файла, период ротации. Реализованы атрибуты rotation, rotationsize, rotationperiod элемента log файла настройки технологического журнала logcfg.xml.
  • Настройки сжатия устаревших файлов технологического журнала. Сжатие выполняется в фоне, во время ротации файлов журнала. Реализован атрибут compress элемента log файла настройки технологического журнала logcfg.xml.
  • Записи файлов технологического журнала в формате JSON. Реализован атрибут format элемента log файла настройки технологического журнала logcfg.xml.

Реализована возможность отключения автоматического удаления файлов технологического журнала с помощью указания значения 0 в атрибуте history элемента log файла настройки технологического журнала logcfg.xml. Очистка каталога технологического журнала в этом случае ложится на внешние инструменты (по отношению к системе «1С:Предприятие»). Изменен алгоритм удаления файлов технологического журнала. Отменена проверка каталога размещения файлов технологического журнала на предмет размещения неизвестных файлов.

Для всех событий технологического журнала реализовано свойство level, которое описывает уровень важности события.

Данные возможности не предоставлялись.Расширены возможности формирования технологического журнала работы системы «1С:Предприятие», например, для использования во внешних инструментах анализа журналов.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Кластер серверов.
Средства администрирования.
Для сервера администрирования кластера (ras) и автономного сервера (ibsrv) реализована возможность предоставления показателей производительности кластера серверов (метрик производительности) в формате OpenMetrics. Реализован набор параметров HTTP-запроса, которые позволят ограничить набор получаемых метрик.

Для командной строки сервера администрирования кластера реализованы команды monitor-address, monitor-port, monitor-base. Для доступа к метрикам используется аутентификация системы «1С:Предприятие».

Для командной строки автономного сервера реализованы параметры monitor-address, monitor-port, monitor-base. Для файла конфигурации автономного сервера реализована секция monitor секции gates. В состав секции входят параметры address, port, base. Для доступа к метрикам не требуется аутентификация.

Использование метрик в формате OpenMetrics требует наличия лицензии КОРП.

Данная возможность не предоставлялась.Расширены возможности формирования технологического журнала работы системы «1С:Предприятие», например, для использования во внешних инструментах анализа журналов.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Кластер серверов.
Средства администрирования.
Для утилиты управления автономным сервером (ibcmd) реализован режим работы с журналом регистрации (без участия информационной базы). Допускается выгрузка журнала регистрации в форматах XML и JSON, а также выгрузка модели событий журнала регистрации в виде xsd-схемы. Реализована команда eventlog.Данная возможность не предоставлялась.Упрощено получение журнала регистрации для анализа внешними инструментами.
В документации данное изменение описано здесь.
Копии базы данных.
Реализована поддержка нового механизма обновления копии базы данных (версия 2) для СУБД PostgreSQL. Для включения этого механизма необходимо выполнение (одновременно) следующих условий:
  • PostrgeSQL версии 10 и последующие.
  • СУБД должна быть установлена или обновлена из дистрибутива, распространяемого фирмой «1С».
  • В файле конфигурации СУБД должен быть установлен параметр wal_level=logical.
  • В стандартной обработке управления копиями базы данных для выбранной информационной базы должна быть включена версия 2 стандартной репликации.
Поддержка нового механизма обновления копии базы данных (версия 2) поддерживалась только при работе с СУБД Microsoft SQL Server.При использовании нового механизма обновления копии базы данных повышается скорость обновления копии базы данных.

+

В документации данное изменение описано здесь.
Работа с криптографией.
Реализована поддержка формата ACH.1 в кодировке base64 в метода криптографии.Данная возможность не предоставлялась.Стало возможно обрабатывать данные формата ACH.1 (сертификаты, списки отзыва и данные в формате PKCS#7) непосредственно в кодировке base64, без предварительной конвертации в двоичные данные
Регистры сведений.
Для набора записей независимого регистра сведений реализованы дополнительные режимы записи:
  • Слияние - в этом случае в информационной базе происходит обновление записей, совпадающих по ключевым полям с записываемым набором записей, а остальные записи набора просто добавляются в регистр.
  • Удаление - в этом случае происходит удаление из информационной базы записей, совпадающих по ключевым полям с записями, присутствующими в наборе записей.

Реализовано системное перечисление РежимЗамещения, описывающий возможные варианты записи набора записей регистра сведений. Для метода РегистрСведенийНаборЗаписей.Записать() реализована возможность указывать значение типа системного перечисления РежимЗамещения в качестве значения параметра Замещать (наряду со значением типа Булево).

Обработчики событий ПередЗаписью() и ПриЗаписи(), а также обработчики соответствующих подписок получают значение параметра Замещение в том виде, в каком он был передан методу Записать() набора записей регистра сведений.

Для набора записей независимого регистра сведений поддерживались возможность только добавления или полного замещения существующих записей в информационной базе.В некоторых сценариях становится возможно существенно ускорить работу с независимыми регистрами сведений.
В документации данное изменение описано здесь.
Автоматизированное тестирование.
Расширены возможности автоматизированного тестирования конфигураций:
  • Реализован метод ТестируемаяТаблицаФормы.СкопироватьСтроку().
  • Для объектов ТестируемоеОкноКлиентскогоПриложения, ТестируемаяГруппаКомандногоИнтерфейса, ТестируемаяКнопкаКомандногоИнтерфейса, ТестируемаяФорма, ТестируемоеПолеФормы, ТестируемаяГруппаФормы, ТестируемаяКнопкаФормы, ТестируемаяТаблицаФормы, ТестируемаяДекорацияФормы реализован метод ПолучитьРодителя().
  • Для объекта ТестируемоеПолеФормы реализован метод ЗаголовокОтображается().
  • Для расширения поля формы для тестируемого форматированного документа реализован метод НажатьНаГиперссылкуВФорматированномДокументе().
  • Для метода ТестируемоеПолеФормы.ЗаписатьСодержимоеВФайл() реализована возможность сохранять содержимое в файл с другим именем, если документ в поле уже сохранялся. Реализован параметр метода СохранитьКак.
  • Для тестируемого поля формы реализовано расширение HTML-документа, которое позволяет выполнить действия, аналогичные полю форматированного документа.
  • Для расширения поля формы для тестируемого табличного документа реализованы методы ТекстВПределахГраницыОбласти() и ВходитВОбъединеннуюОбласть().
  • Для объекта ТестируемаяДекорацияФормы и ТестируемоеПолеФормы, отображающее форматированный документ, реализован метод ПолучитьПредставленияГиперссылокФорматированнойСтроки().
  • Реализован метод ТестируемоеПолеФормы.ВыполнитьВыборИзМенюРасшифровки() для случая, когда поле формы отображает табличный документ.
  • Реализован метод ТестируемоеПриложение.ОчиститьРезультатДиалогаВыбораФайла().
  • Для объекта ТестируемаяФорма реализованы методы ПолучитьПредставлениеСпискаВыбора(), ТекущаяДоступность(), ТекущееТолькоПросмотр().
  • Реализовано свойство ТестируемоеОкноКлиентскогоПриложения.НавигационнаяСсылка.
  • Реализован метод глобального контекста ТекущийСеансТестируется().
Данные возможности не предоставлялись.Расширены возможности автоматизированного тестирования прикладных решений.
В документации данное изменение описано здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Стандартные функции.
Средства администрирования.
Кластер серверов.
Для стандартной обработки Управление серверами реализованы возможности сохранения и восстановления параметров администрируемых серверов (кнопка Параметры кластеров). Сохранение параметров выполняется в xml-файл. Структура файла не документируется.

Создание нового подключения к кластеру серверов, а также команды сохранения и восстановления списка кластеров сгруппированы в кнопке Подключения.

Стандартная обработка Управление серверами не поддерживала возможность сохранения (восстановления) параметров администрируемых кластеров серверов в файл (из файла).Упрощен перенос настроек параметров кластера серверов между компьютерами, например, при развертывании идентичных кластеров.
Управляемые блокировки.
При работе с регистром бухгалтерии поглощение управляемых блокировок срабатывает раньше эскалации управляемой блокировки. В результате повышается параллельность работы с регистром бухгалтерии. +При работе с регистром бухгалтерии эскалация управляемой блокировки срабатывала раньше, чем поглощение блокировок. В результате параллельная работа с регистром бухгалтерии могла стать невозможной.Повышена параллельность работы с регистром бухгалтерии.
Система взаимодействия.
Работа в macOS.
Веб-клиент.
Реализована возможность использовать видеозвонки при использовании веб-браузера Safari версии 13 и последующих версий под управлением ОС macOS.Не поддерживались видеозвонки при использовании веб-браузера Safari.Стали доступны видеозвонки при работе в веб-браузере Safari под управлением ОС macOS.
В документации данное изменение описано здесь.
Средства администрирования.
Если при загрузке дистрибутива клиентского приложения по протоколу HTTP возникает ошибка, то текст сообщения об ошибке включает не только код ошибки, но и текстовое описание (если таковое доступно).Если при загрузке дистрибутива клиентского приложения по протоколу HTTP возникает ошибка, то текст сообщения об ошибке включал только код ошибки.Упрощено расследование проблемных ситуаций, возникающих при загрузке дистрибутива клиентского приложения по протоколу HTTP.
Обработка ошибок.
Кластер серверов.
Средства администрирования.
При завершении сеанса и прерывании серверного вызова из конфигуратора, встроенного языка, из механизма управления потреблением ресурсов или через средства администрирования, если файл сеансовых данных не удалялся, то пользователю будет показано сообщение с причиной завершения сеанса. Сообщение будет показано при следующем серверном вызове, даже если сеанс был удалён не в момент серверного вызова.

Реализовано свойство системного перечисления КатегорияОшибки.ПринудительноеЗавершениеРаботы. В эту категорию попадают все исключения, связанные с прерыванием серверного вызова с помощью средств администрирования и все исключения, связанные с завершением сеанса с помощью средств платформы (через конфигуратор, из встроенного языка, через средства администрирования).

Пользователю не отображался текст, который мог быть указан администратором в случае принудительного завершения сеанса пользователя.Устранено некорректное поведение системы.
Обработка ошибок.
Автономный сервер.
Средства администрирования.
В диалоге завершения сеансов пользователя из конфигуратора (при обновлении конфигурации базы данных) реализована возможность указать сообщение, которое будет отображено пользователю в качестве причины прерывания сеанса.

Для команд утилиты управления автономным сервером (ibcmd) infobase restore и config apply реализован параметр session-terminate-message, позволяющий указать текст, который будет показан пользователю в качестве причины прерывания сеанса.

Если параметр командной строки session-terminate утилиты ibcmd предписывает прерывать пользовательские сеансы, а параметр session-terminate-message не указан, то утилита будет ожидать ввода сообщения в консоли и продолжит свою работу только после ввода сообщения.

При завершении сеансов пользователя из конфигуратора не предоставлялась возможность указать текст, описывающий причину завершения сеанса пользователя.

Утилита управления автономным сервером (ibcmd) не предоставляла возможности указать текст, который отображается пользователю в качестве причины завершения сеанса.

Стало возможно указать текст, описывающий причины прерывания сеанса, в тех случаях, когда сеансы прерываются во время обновления конфигурации информационной базы из конфигуратора или с помощью утилиты управления автономным сервером.
В документации данное изменение описано здесь и здесь.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Глобальный поиск.
Ускорено выполнение операций глобального поиска.Медленное выполнение операций глобального поиска.Ускорено выполнение операций глобального поиска.
Кластер серверов.
Оптимизирована загрузка метаданных при загрузке конфигурации в клиент-серверном варианте запуска.

Уменьшено время подключения первого клиента к информационной базе. Уменьшено время запуска первого сеанса информационной базы на рабочем процессе, который еще не обслуживал сеансы этой информационной базы. +

При работе в клиент-серверном варианте медленно выполнялась загрузка метаданных конфигурации. Долго выполнялся запуск первого сеанса информационной базы на рабочем процессе, который еще не обслуживал сеансы этой информационной базы.Уменьшено время запуска первого сеанса информационной базы на рабочем процессе, который еще не обслуживал сеансы этой информационной базы.
Автономный сервер.
Уменьшено время запуска автономного сервера в файловом и клиент-серверном вариантах работы.Запуск автономного сервера занимал много времени.Уменьшено время запуска автономного сервера в файловом и клиент-серверном вариантах работы.
Средства разработки.
В Конфигураторе оптимизирована операция глобальной замены в конфигурации.Операция глобальной замены в конфигурации занимала много времени.В Конфигураторе оптимизирована операция глобальной замены в конфигурации.
Средства разработки.
В Конфигураторе оптимизирована операция поиска ссылок на объект конфигурации.Поиск ссылок на объект конфигурации занимал много времени.В Конфигураторе оптимизирована операция поиска ссылок на объект конфигурации.
Кластер серверов.
Оптимизировано использование центрального процессора и оперативной памяти в кластере серверов (с уровнем отказоустойчивости 2 и выше), повышена надежность и скорость работы механизмов репликации состояния серверов при высоких нагрузках, а также повышена общая стабильность работы кластера при высоких нагрузках.При работе высоконагруженного кластера серверов с уровнем отказоустойчивости 2 и выше, кластер использовал больше ресурсов компьютера и работал менее стабильно.Оптимизировано использование ресурсов компьютера кластера серверов, повышена надежность и стабильность работы кластера серверов
Полнотекстовый поиск.
Оптимизировано использование оперативной памяти механизмом полнотекстового поиска.

Для получения эффекта от оптимизации, необходимо выполнить переиндексацию индекса полнотекстового поиска.

Механизм полнотекстового поиска не оптимально использовал оперативную память компьютера.Снижено потребление оперативной памяти механизмом полнотекстового поиска и повышена стабильность работы системы.
Копии базы данных.
Выбор копии, на которой будет выполняться запрос, стал выполняться быстрее.Выбор копии, на которой будет выполняться запрос, требовал больше времени.Повышена производительность системы в том случае, когда перед выполнением запроса необходимо выбрать копию базы данных, на которой будет выполняться запрос.
Система взаимодействия.
При выполнении видеозвонков в тонком клиенте снижается нагрузка на центральный процессор и сетевой канал клиентского компьютера.При выполнении видеозвонков в тонком клиенте нагрузка на центральный процессор и сетевой канал клиентского компьютера была выше.Снижается нагрузка на процессор и сетевой канал клиентского компьютера во время видеозвонков в тонком клиенте.
Система взаимодействия.
Снижается нагрузка на центральный процессор и сетевой канал сервера системы взаимодействия при выполнении групповых видеозвонков с помощью тонкого клиента.

Для получения эффекта необходимо:

  • Обновить платформу до версии 8.3.25.
  • Обновить сервер системы взаимодействия до версии 25.
  • Обновить видеосервер Janus (на сервере системы взаимодействия) до версии 1.0.4.
При выполнении групповых видеозвонков с помощью тонкого клиента наблюдалась повышенная нагрузка на центральный процессор и сетевой канал сервера системы взаимодействия.При использовании тонких клиентов при совершении групповых видеозвонков стало возможно повысить качество видеозвонка и повысить количество пользователей, которые одновременно могут находиться в одном видеозвонке.
Работа с СУБД.
Оптимизировано создание табличных частей объектов, а также записей наборов записей регистров сведений и накоплений.Создание табличных частей объектов, а также запись наборов записей регистров накопления и сведений занимала больше времени.Оптимизирована создание табличных частей объектов, запись набора записей регистра сведений и регистра накоплений.
Копии базы данных.
Ускорено начальное заполнение копии базы данных.Начальное заполнение копии базы данных занимало больше времени.Ускорено начальное заполнение копии базы данных.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
Реализована возможность изменения администратора абонента системы взаимодействия. Реализована возможность ведения списка администраторов абонента системы взаимодействия. Реализована возможность смены адреса электронной почты для пользователя системы взаимодействия.

Для менеджера системы взаимодействия реализованы методы: ПолучитьНовыйКлючАдминистрирования(), ОтправитьВременныйКод(), ДобавитьВАдминистраторыАбонента(), ИсключитьИзАдминистраторовАбонента(), УстановитьАдресЭлектроннойПочтыАбонента(). Реализовано свойство ПользовательСистемыВзаимодействия.АдминистраторАбонента. Реализовано свойство ОтборПользователейСистемыВзаимодействия.АдминистраторАбонента.

Стандартная функция Управление системой взаимодействия доработана с учетом реализованных возможностей.

Данная возможность не предоставлялась. Администратор абонента не мог быть изменен.Стало возможно восстановить доступ к абоненту системы взаимодействия в том случае, когда потерян доступ к электронной почте, на которую регистрировался абонент.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства администрирования.
При записи (любым способом) пользователя информационной базы для которого указано имя пользователя операционной системы, длина которого превышает 128 символов, формируется ошибка.При записи пользователя информационной базы для которого указано имя пользователя операционной системы, длина которого превышает 128 символов:
  • Если запись выполнялась в Конфигураторе - происходило аварийное завершение работы системы.
  • Если запись выполнялась с помощью встроенного языка - значение игнорировалось, ошибка не формировалась.

+

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Кластер серверов.
Средства администрирования.
Для свойства Data события CLSTR (когда свойство Event равно значению performance update) документированы отображаемые данные, которые описывают текущие показатели производительности процессов кластера.Данные, которые отображаются в свойстве Data события CLSTR (когда свойство Event равно значению performance update) не были документированы.Уточнена документация к системе.
В документации данное изменение описано здесь.
Расширение конфигурации.
Реализована возможность включения реквизитов, добавляемых расширением конфигурации в расширяемые объекты, в состав собственных и заимствованных критериев отбора.

Реализована возможность в расширении изменять свойство Тип параметра команды для общих команд и команд объектов конфигурации.

Реализована возможность в расширении изменять свойство Форма выбора для констант, реквизитов, ресурсов, измерений и полей внешних источников данных.

Реализована возможность в расширениях добавлять собственные подчиненные подсистемы к заимствованным подсистемам. Для свойства Состав заимствованных подсистем реализована возможность отключения модификации при подключении расширения. Редактирование заимствованных подсистем выполняется в панели свойств, аналогично остальным заимствованным объектам конфигурации.

Данные возможности не предоставлялись.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь, здесь и здесь.
Регистры сведений.
Справочники.
Для измерений независимого регистра сведений и стандартного реквизита справочников Владелец реализована возможность указывать, какие действия при реструктуризации информационной базы будут предприняты в том случае, когда сокращается набор типов, описывающих тип соответствующего объекта. Предоставляется возможность:
  • Запретить изменение состава типов.
  • Преобразовать значения к новому набору типов.
  • Удалить записи, которые соответствуют удаленным типам.

Реализовано свойство Режим сокращения типа для измерения независимого регистра сведений и стандартного реквизита справочника Владелец. Для объектов метаданных ОписаниеСтандартногоРеквизита и Измерение реализованы свойства РежимСокращенияТипа. +

Данная возможность не предоставлялась.

Для измерения регистра сведений всегда выполнялась попытка преобразования значения, а для стандартного реквизита справочника Владелец всегда блокировалось сокращение состава типов.

Упрощена разработка объектов конфигурации (регистры сведений и подчиненные справочники), которые обрабатываются только с помощью встроенного языка, но в состав типов входит большое количество прочих объектов конфигурации.
В документации данное изменение описано здесь, здесь и здесь.
Дата акселератор.
В том случае, если используется масштабируемый Дата акселератор (Дата акселератор запущен более чем на одном рабочем сервере кластера серверов) и копия базы данных расположена более чем на одном экземпляре Дата акселератора, реализовано параллельное обновление всех используемых экземпляров Дата акселератора.

Ошибка обновления на одном экземпляре Дата акселератора не приведет к прекращению обновления всего Дата акселератора (будут обновлены все экземпляры, кроме того, на котором произошла ошибка).

Обновление экземпляров Дата акселератора выполнялось последовательно, от экземпляра к экземпляру. При ошибке во время обновления одного экземпляра, процесс прекращался, в результате чего все экземпляры Дата акселератора, которые следовали за аварийным, оказывались с неактуальными данными.Сокращено время обновления данных в том случае, если Дата акселератор состоит из нескольких экземпляров.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.18.Версия формата выгрузки конфигурации в XML-файлы была равна 2.17.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа с XML, XDTO.
При XDTO-сериализации плана счетов свойства, соответствующие общим реквизитам, размещаются после свойств, соответствующих признакам учета.

В режиме совместимости с версией 8.3.24 поведение не изменилось.

При XDTO-сериализации плана счетов свойства, соответствующие общим реквизитам, размещались до свойств, соответствующих признакам учета.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Кластер серверов.
Средства администрирования.
При запуске кластера серверов сразу считывает все необходимые данные из файлов списка кластеров и реестра кластера. В случае ошибок чтения этих данных, кластер серверов не стартует, а в технологический журнал фиксируются обнаруженные ошибки.При запуске кластера серверов данные из файлов списка кластеров и реестра кластера считывались по мере необходимости. В результате ошибки, которые могли возникать при чтении этих файлов, приводили к труднодиагностируемым ошибкам в процессе работы кластера.Упрощено администрирование в случае ошибок, которые могу возникать при чтении списка кластеров и реестра кластера во время запуска кластера серверов.
Система взаимодействия.
Реализована возможность размещения панели кнопок в сообщениях системы взаимодействия (включая интеграции с различными внешними системами).

Действия сообщений системы взаимодействия объявляются устаревшими и не рекомендуются к использованию. Рекомендуется заменить действия системы взаимодействия на панели кнопок.

Для объекта СообщениеСистемыВзаимодействия реализованы свойство ИсходноеСообщение. ПанельКнопок.

Для объекта ИнтеграцияСистемыВзаимодействия реализован метод ПоддерживаетсяДействиеКнопкиПанелиКнопокСообщения().

Для модуля бота системы взаимодействия реализован обработчик события

ОбработкаНажатияКнопкиПанелиКнопокСообщенияСистемыВзаимодействия().

Для модуля приложения реализован обработчик события

ПриНажатииКнопкиПанелиКнопокСообщенияСистемыВзаимодействия().

Объявляются устаревшими (и не рекомендуются для использования) следующим свойства и методы:

  • Свойство СообщениеСистемыВзаимодействия.Действия.
  • Методы ПодключитьОбработчикДействияСообщения() и ОтключитьОбработчикДействияСообщения() для менеджера системы взаимодействия.
  • Обработчик события модуля приложения ПриВыбореДействияСообщенияСистемыВзаимодейстивя().
  • Объекты КоллекцияДействийСообщенияСистемыВзаимодействия, ДействиеСообщенияСистемыВзаимодействия.
Существовала возможность задавать действия для сообщений системы взаимодействия, которая была не доступна в сообщениях интеграции.Стало возможно реализовать единый, наглядный, интерфейс взаимодействия пользователя системы взаимодействия и информационной системы (интерфейс бота), который единообразно выглядит во всех сообщениях системы взаимодействия.
В документации данное изменение описано здесь.
Средства администрирования.
Возможность указания одного адреса электронной почты (в разных регистрах) для разных пользователей информационной базы больше не поддерживается. При попытке записи второго пользователя с уже существующим адресом электронной почты будет сформировано исключение.Имелась возможность указать один и тот же адрес электронной почты (в разных регистрах) для разных пользователей информационной базы.Устранена возможная неоднозначность определения пользователя по адресу электронной почты.
В документации данное изменение описано здесь.
Средства администрирования.
Ускорена проверка уникальности адреса электронной почты при записи пользователя.

Для получения необходимого эффекта рекомендуется выполнить операцию тестирования и исправления информационной базы (в режиме исправления). В результате этого будет создан необходимый индекс для таблицы пользователей, что и приведет к ускорению проверки уникальности адреса электронной почты.

Длина адреса электронной почты не может превышать 128 символов.

При записи пользователя информационной базы проверка уникальности адреса электронной почты выполнялась очень долго.

Длина адреса электронной почты могла превышать 128 символов.

Ускорена проверка уникальности адреса электронной почты при записи пользователя.
В документации данное изменение описано здесь.
Средства администрирования.
Кластер серверов.
Для объекта АдминистрированиеСеанс реализованы свойства:
  • ДлительностьТекущегоВызоваСУБД.
  • ВремяПоследнегоВызоваСУБД.
Данная возможность не предоставлялась.

Данные свойства были доступны в других административных интерфейсах системы, но отсутствовали в объекте АдминистрированиеСеанс.

Устранено незапланированное поведение системы.
Кластер серверов.
Средства администрирования.
Счетчик потребления ресурсов с длительностью сбора «серверный вызов», учитывает каждый сеанс одного пользователя как отдельный объект. Объединение разных сеансов одного пользователя сохраняется для счетчиков, длительность сбора данных которых отлична от «серверный вызов».Счетчик потребления ресурсов с длительностью сбора «серверный вызов», суммировал показатели всех сеансов одного пользователя.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Кластер серверов.
Средства администрирования.
Реализована корректная обработка прерывания серверного вызова, выполняющего вызов к СУБД, с помощью счетчика потребления ресурсов:
  • При завершении сеанса отображается ошибка, указанная администратором и сеанс завершается.
  • При прерывании вызова отображается ошибка, указанная администратором и прерванный серверный вызов не повторяется.
Обработка прерывания серверного вызова, выполняющего вызов к СУБД, с помощью счетчика потребления ресурсов, выполнялась некорректно:
  • Вначале завершается вызов СУБД, потом срабатывает ограничение счетчика..
  • При прерывании серверного вызова, выполнение вызова к СУБД повторяется заново. При удалении сеанса отображается ошибка плохого соединения после чего сеанс удаляется.
Устранено некорректное поведение системы.
Кластер серверов.
Средства администрирования.
Реализовано корректное отображение значений использованного процессорного времени для счетчиков потребления ресурсов.Отображение значений использованного процессорного времени для счетчиков потребления ресурсов могло выполняться некорректно.Устранено некорректное поведение системы.
Работа с XML, XDTO.
Работа с JSON.
Реализована возможность явного указания типа значения при выполнении XDTO-сериализации (в XML или JSON) значений, которые отсутствуют в модели данных (для открытой модели содержания). Для метода ОбъектXDTO.Добавить() реализован параметр НазначениеТипа.

При чтении данных с помощью объекта ФабрикаXDTO реализована возможность указать. каким образом должен определяться тип считываемого значения, если значение отсутствует в модели содержания. Для методов ПрочитатьXML() и ПрочитатьJSON() объекта ФабрикаXDTO реализован параметр НазначениеТипа.

При выполнении XDTO-сериализации значения, отсутствующего в модели данных, тип такого значения не записывался в результирующий файл.Устранено некорректное поведение системы.
Средства администрирования.
Информация о завершенных сеансах информационной базы сохраняется:
  • В клиент-серверном варианте и при работе с использованием автономного сервера - в файле snccntx.dat.
  • В файловом варианте - в файле 1Cv8snc.1CD в каталоге информационной базы. Файл не удаляется при завершении последнего сеанса информационной базы.

Информация о завершенных сеансах хранится неделю. Старая информаци очищается 1 раз в час.

Данная возможность не предоставлялась.Реализовано хранение информации о завершенных сеансах информационной базы.
Система взаимодействия.
Для коллекций КоллекцияВложенийСистемыВзаимодействия, РядКнопокПанелиКнопокСообщенияСистемыВзаимодействия и РядыКнопокПанелиКнопокСообщенияСистемыВзаимодействия унифицирован набор методов, доступность и поведение в разных клиентских приложениях.У коллекций КоллекцияВложенийСистемыВзаимодействия, РядКнопокПанелиКнопокСообщенияСистемыВзаимодействия и РядыКнопокПанелиКнопокСообщенияСистемыВзаимодействия был разный набор методов, доступность и поведение в разных клиентских приложениях.Унифицировано описание и поведение однотипных (по сути) коллекций объектов при работе с системой взаимодействия. Устранено незапланированное поведение системы.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Стандартная обработка работы с речью.
  • Управление распознаванием речи.
  • Управление работой с речью.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
В мобильной версии «1С:Предприятие» реализована возможность использовать механизм распознавания речи:
  • Мобильная платформа - позволяет использовать только облачный сервис распознавания речи.
  • Мобильный клиент - позволяет использовать как облачный так и локальный вариант механизма.

На мобильной версии системы «1С:Предприятие» реализована доступность соответствующих объектов, свойств и методов встроенного языка.

Данная возможность не предоставлялась.Реализована возможность использовать распознавание речи на мобильных устройствах.
В документации данное изменение описано здесь.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
Система взаимодействия.
В мобильной версии реализована возможность делиться файлами из мобильного приложения через стандартные интерфейсы мобильной операционной системы.

Для системы взаимодействия реализованы возможности поделиться: сообщением целиком, выделенным текстом сообщения или поля ввода сообщения, вложением сообщения.

Реализовано свойство глобального контекста СредстваПередачиДанныхНаУстройстве. Для объекта ДанныеМультимедиа реализован конструктор объекта из файла.

Для системного перечисления СтандартнаяКомандаСистемыВзаимодействия реализованы значения ПоделитьсяСообщением и ПоделитьсяВложением. Данные команды могут использовать только в мобильном клиенте.

Данная возможность не предоставлялась.Упрощено использование сторонних приложений для обработки данных, которые сформированы в мобильном приложении, собранном на мобильной версии «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Системные требования.
Прекращена поддержка ОС iOS версий 9 и 10.

Реализована поддержка ОС iOS версий 13 - 16 (включительно).

Мобильная версия системы «1С:Предприятие» поддерживала использование ОС iOS версий 9 и 10.Актуализирован список поддерживаемых версий ОС iOS. Мобильная версия системы «1С:Предприятие» поддерживает ОС iOS версий с 11 по 16 (включительно).
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
Для сборки мобильных приложений следует использовать Java версий 17 и последующие.

Для сборки мобильных приложений с использованием мобильной версии 8.3.25 следует использовать:

  • Сборщик мобильных приложений версии 8.3.25.
  • Java версий 17 и последующие (рекомендуется Java версии 19 и последующих версий).

Для сборки мобильных приложений с использованием предыдущих версий платформы следует использовать:

  • Сборщик мобильных приложений версии 8.3.25.
  • Java версий 17 и последующие.

При использование Java версии 8 - 16 сохранена возможность собирать мобильные приложения с использованием мобильной версии 8.3.24 и предшествующих версий.

Для сборки мобильных приложений использовались версии Java c 8 по 13. Инструменты сборки не позволяли использовать Java версий 14 и последующие.Выполнен переход на новые инструменты сборки мобильных приложений для работы под управлением ОС Android.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Для системного перечисления ТипШтрихКода реализованы значения: QRCode, DataMatrix, PDF417, Aztec, MaxiCode, UPCA, UPCE, EAN13, EAN8, Codabar, Code93, Code128, RSS14, RSSExpanded, Code39, ITF.

Для метода ПоказатьСканированиеШтрихКодов() параметр ТипШтрихКода может принимать массив значений, описывающих, какие типы штрих-кодов ожидаются в данном сканировании. Мобильное приложение поддерживает единый список сканируемых типов штрих-кодов на всех поддерживаемых мобильных платформах.

Улучшено качество распознавания штрих-кодов.

При работе под управлением ОС Android увеличен размер окна сканирования.

В методе ПоказатьСканированиеШтрихКодов() не поддерживалось точное указание перечня ожидаемых штрих-кодов. Было хуже качество распознавания штрих-кодов. Список поддерживаемых типов сканируемых штрих-кодов зависел от платформы, для которой собиралось мобильное приложение.Улучшено качество сканирования штрих-кодов. За счет возможности точного указания ожидаемых штрих-кодов может быть снижена нагрузка на процессор во время сканирования, что приведет к снижению энергопотребления при сканировании штрих-кодов.
В документации данное изменение описано здесь.
Специальные возможности мобильного устройства.
Для мобильной версии реализована возможность из встроенного языка предлагать пользователю оценить приложение и оставить отзыв в магазине приложений соответствующей мобильной операционной системы.

Реализован метод глобального контекста ПоказатьВводОценкиПриложения().

Данная возможность не предоставлялась.Позволяет предлагать пользователям отправлять оценки и обзоры в магазин приложений, не выходя из приложения. Наличие оценок и отзывов влияет на общий рейтинг приложения в поисковой выдаче. Пользователям в магазине приложений чаще предлагаются приложения, у которых больше оценок и отзывов.

+

В документации данное изменение описано здесь.
Сборщик мобильных приложений.
В процессе сборки мобильных приложений для работы под управлением ОС Android, реализована проверка того, что добавляемый элемент манифеста собираемого приложения уже имеется в манифесте. Если добавляемый элемент уже есть в манифесте - повторно он (элемент) не добавляется.В процессе сборки мобильных приложений для работы под управлением ОС Android, отсутствовала проверка того, что добавляемый элемент манифеста собираемого приложения уже имеется в манифесте.Снижено количество сложно диагностируемых ошибок сборки мобильного приложения для работы под управлением ОС Android, которые возникают из-за того, что, например, внешние компоненты требуют разрешение, которое уже затребовано при сборке (другой внешней компонентой или самим приложением). В результате изменения, дублирующие записи не будут попадать в результирующий манифест собираемого приложения, что позволит собрать приложение, сборка которого ранее завершалась с ошибками.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Реализована поддержка сервиса Firebase Cloud Messaging на протоколе HTTP v1 для отправки push-уведомлений. Поддержка реализована в версии 8.3.25.43 и последующих мобильных версиях. Для работы с push-уведомлениями необходимо модифицировать прикладное решение в части получения и использования маркера доступа при работе с сервисом Firebase Cloud Messaging на протоколе HTTP v1.

Метод ПолучитьМаркерДоступа() менеджера отправки доставляемых уведомлений используется для получения маркера доступа (внесены изменения в тип и содержание параметров метода).

В методе Отправить() менеджера отправки доставляемых уведомлений используется ранее полученный маркер доступа. +

Сервис Firebase Cloud Messaging на протоколе HTTP v1 не поддерживался мобильной версией системы «1С:Предприятие». Поддерживалась предыдущая версия сервиса, которая отключается компанией Google.Актуализирована поддержка сервиса отправки push-уведомлений на платформе Android.
В документации данное изменение описано здесь, здесь и здесь.

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Дата акселератор.
Системные требования.
Реализована работа Дата акселератора под управлением операционных систем Astra Linux, Альт Линукс и РЕД ОС.

Точные номера версий приведены в документации.

Дата Акселератор не поддерживал работу в операционных системах Astra Linux, Альт Линукс и РЕД ОСРасширен список операционных систем, под управлением которых может работать Дата акселератором.
В документации данное изменение описано здесь.
Общие объекты.
Исправлена ошибка формирования UUID версий 3 и 5 при использовании объекта УникальныйИдентификатор. В режиме совместимости с версией 8.3.24 поведение не изменилось.

Реализован устаревший метод ПолучитьУникальныйИдентификаторСПоддержкойСовместимости(), который позволит получить UUID с ошибкой (как было в предыдущих версиях платформы) с отключенным режимом совместимости. Использовать данный метод для каких-либо других целей настоятельно не рекомендуется.

При формировании UUID версий 3 и 5 с помощью объекта УникальныйИдентификатор, UUID формировался с ошибкой. Результат не полностью удовлетворял стандарту RFC 4122.Устранено некорректное поведение системы.
Работа с XML, XDTO.
Размер значения элемента XML не может превышать 100 000 000 символов.Размер значения элемента XML не мог превышать 10 000 000 символов. Это значение не было документировано.Снижено количество ошибок, которые возникали из-за того, что фактический размер значения элемента XML-документа превышал максимальное значение размера.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
В мобильной версии системы «1С:Предприятие» реализована возможность использовать механизм синтеза речи. Реализована функциональность Синтез речи.Синтез речи не поддерживался в мобильной версии системы «1С:Предприятие».Расширены возможности мобильной версии системы «1С:Предприятие». Стало возможно реализовать в мобильных приложениях, на базе мобильной версии системы, голосовые подсказки при выполнении тех или иных процессов в приложении.
В документации данное изменение описано здесь и здесь.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C: 16.2;
  • Postgres Pro Standard: 16.2.1;
  • Postgres Pro Enterprise: 16.2.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C: 12.18, 13.14, 14.11, 15.6;
  • Postgres Pro Standard: 12.18.2, 13.14.2, 14.11.2, 15.6.2;
  • Postgres Pro Enterprise: 12.18.2, 13.14.2, 14.11.2, 15.6.2.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.25 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.25 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C: 12.19, 13.15, 14.12, 15.7, 16.3;
  • Postgres Pro Standard: 12.19.2, 13.15.2, 14.12.2, 15.7.2, 16.3.1;
  • Postgres Pro Enterprise: 12.19.2, 13.15.2, 14.12.2, 15.7.2, 16.3.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C: 16.3;
  • Postgres Pro Standard: 16.3.1;
  • Postgres Pro Enterprise: 16.3.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro Standard: 13.15.2, 14.12.2, 15.7.2;
  • Postgres Pro Enterprise: 13.15.2, 14.12.2, 15.7.2.

Разрядность версий СУБД: E2k.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro Standard: 16.3.1;
  • Postgres Pro Enterprise: 16.3.1.

Разрядность версий СУБД: E2k.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Тестирование и исправление информационной базы.
Пользователи информационной базы.
Оптимизирован один из этапов операции тестирования и исправления информационной базы (категория Проверка логической целостности информационной базы - Прочее). Этот этап необходимо выполнить при переходе на версию 8.3.25 для повышения скорости работы с пользователями информационной базы.Один из этапов операции тестирования и исправления информационной базы (категория Проверка логической целостности информационной базы - Прочее) занимал очень много времени.Уменьшено время, которое требуется для реструктуризации списка пользователей информационной базы.
Мобильная платформа.
Мобильный клиент.
Системные требования.
В мобильной версии системы «1С:Предприятие» реализована поддержка ОС Android 14. Таким образом, мобильная версия «1С:Предприятие» поддерживает ОС Android в интервале версий 5.0 - 14.

При работе мобильного приложения под управлением ОС Android 14 и последующих версий, если мобильное приложение использует функциональность Библиотеки картинок и видео, то пользователь может не только полностью разрешить или запретить доступ к библиотеке, но указать отдельные картинки или видеоролики, к которым будет предоставлен доступ.

Мобильная версия «1С:Предприятие» поддерживала ОС Android в интервале версий 5.0 - 13.Мобильная версия «1С:Предприятия» поддерживает актуальный состав версий операционной системы Android.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C: 12.20, 13.16, 14.13, 15.8;
  • Postgres Pro Standard: 12.20.1, 13.16.1, 14.13.1, 15.8.1;
  • Postgres Pro Enterprise: 12.20.1, 13.16.1, 14.13.1, 15.8.1;
  • Postgres Pro CERT Standart: 14.13.1, 15.8.1;
  • Postgres Pro CERT Enterprise: 13.16.1, 14.13.1, 15.8.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C: 16.4;
  • Postgres Pro Standard: 16.4.1;
  • Postgres Pro Enterprise: 16.4.1;
  • Postgres Pro CERT Standart: 16.4.1;
  • Postgres Pro CERT Enterprise: 16.4.1.

Разрядность версий СУБД: x86-64, E2k, ARM64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.22.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данные версии СУБД Postgres Pro не поддерживались.Расширен список поддерживаемых СУБД.
Клиентское приложение.
Общие реквизиты / Разделение данных.
Реализована поддержка аутентификации OpenID Connect (в том числе и аутентификации с помощью ЕСИА) в разделенных информационных базах.

При использовании клиентским приложением аутентификации с помощью OpenID Connect реализована поддержка команды /Z строки запуска клиентского приложения.

В файле default.vrd реализована возможность передать значения разделителей в URL, который указывается в параметре redirect_uri секции описания провайдера OpenID.

Аутентификация OpenID Connect в разделенных информационных базах не поддерживалась платформой «1С:Предприятие».Упрощено использование аутентификации OpenID Connect в разделенных информационных базах.
В документации данное изменение описано здесь и здесь.
Форма клиентского приложения.
Значения реквизитов формы с типом Произвольный корректно восстанавливаются из настроек формы.

Разработчикам прикладных решений рекомендуется проанализировать случаи использования сохраняемых реквизитов такого типа.

Значения реквизитов формы с типом Произвольный не восстанавливались из настроек формы.Устранено некорректное поведение системы.
Работа в ОС Linux.
Системные требования.
Реализована поддержка дистрибутива МОС 12 семейства Linux. Дистрибутив работает на процессорах архитектуры x86-64.Данный дистрибутив не поддерживался.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Tantor SE 1C версий 14.13.0, 15.8.0 и 16.4.1.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данная версия СУБД Tantor SE не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь.
Общие объекты.
Изменена последовательность, в которой заполняются значения свойств при работе метода ЗаполнитьЗначенияСвойств() при работе под управлением ОС Linux. Последовательность свойств может изменяться в зависимости от версии платформы «1С:Предприятие» и используемой операционной системы.

Не рекомендуется использовать метод ЗаполнитьЗначенияСвойств() для установки значения свойств, установка которых изменяет значение других свойств. Например, не рекомендуется применять метод к свойству КлючПараметровПечати, т.к. установка этого свойства может приводить к замене значений других свойств.

Последовательность, в которой заполняются значения свойств при работе метода ЗаполнитьЗначенияСвойств() при работе под управлением ОС Linux, была другой.Изменена последовательность, в которой заполняются значения свойств при работе метода ЗаполнитьЗначенияСвойств() при работе под управлением ОС Linux. +
Работа с СУБД.
Расширение конфигурации.
Общие реквизиты / Разделение данных.
Повышена надежность работы платформы в том случае, когда в кластере имеются несколько рабочих процессов или рабочих серверов, на которые могут быть назначены соединения одной разделенной информационной базы, в которой используются расширения.В том случае, когда в кластере имеются несколько рабочих процессов или рабочих серверов, на которые могут быть назначены соединения одной разделенной информационной базы, в которой используются расширения, работа платформы была нестабильной и могла приводить к неожиданным ошибкам.Повышена надежность работы платформы с распределенной информационной базой, в которой используются расширения.
Средства администрирования.
При создании информационной базы в диалоге создания будут отображаться все установленные шаблоны конфигураций. Свойство AppVersion манифеста шаблона конфигурации игнорируется при заполнении списка шаблонов.При создании информационной базы в диалоге создания отображались только те шаблоны, которые содержат значения 8.2 и 8.3 в свойстве AppVersion файла-манифеста шаблона конфигурации.Стало возможно создавать конфигурации из шаблонов, созданных системой «1С:Предприятие» версии 8.5.1 и последующих версий.
Безопасность работы системы.
Табличный документ.
При открытии из файла табличного документа задействован механизм защиты от опасных действий, если он включен. Предупреждение выдается в том случае, если табличный документ содержит OLE-объекты и открытие документа выполняется в клиентском приложении, работающем под управлением ОС Windows. Механизм защиты от опасных действий включается через свойство пользователя или конфигурационный файл conf.cfg.

Положительный ответ на вопрос системы запоминается в разрезе пользователя и информационной базы, отрицательный ответ не запоминается и запрос подтверждения будет отображен при следующей попытке открыть табличный документ с OLE-объектами.

При открытии из файла табличного документа с OLE-объектами, не был задействован механизм защиты от опасных действий.Повышена безопасность системы при открытии из файла табличных документов, содержащих OLE-объекты.
В документации данное изменение описано здесь и здесь.

Оглавление

Переход с предыдущей версии на версию 8.3.25

Оглавление

Версия 8.3.24

Версия 8.3.24 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8324doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.23.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.22. +Возможность запуска конфигураций, разработанных в версии 8.3.23 и более младших, в версии 8.3.24, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.24 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.24, при необходимости, использовать для работы с информационной базой и версию 8.3.23. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Реализована возможность использовать КриптоПро для организации защищенного соединения по HTTP. Реализована возможность управлять режимом проверки отзыва сертификатов сервера из встроенного языка.

Реализован объект ЗащищенноеСоединениеКриптоПро. Реализовано системное перечисление РежимПроверкиОтзываTLSСертификатаСервера. Реализовано свойство ЗащищенноеСоединениеOpenSSL.РежимПроверкиОтзываTLSСертификатаСервера. Для конструктора объекта ЗащищенноеСоединениеOpenSSL реализован параметр РежимПроверкиОтзываTLSСертификатаСервера.

Для конструктора объекта HTTPСоединение реализована возможность получения объекта ЗащищенноеСоединениеКриптоПро в качестве значения параметра ЗащищенноеСоединение.

Возможность использовать КриптоПро для организации защищенного соединения по HTTP не предоставлялась. Не поддерживалась возможность управлять режимом проверки отзыва сертификатов сервера из встроенного языка.Расширены возможности организации защищенного соединения по протоколу HTTP.
В документации данное изменение описано здесь.
Распознавание речи.
Реализована возможность запрещать локальное распознавание речи для системы «1С:Предприятие»:
  • Команда /DisableLocalSpeechToText командной строки запуска клиентского приложения.
  • Параметр disstt строки соединения с информационной базой.
  • Свойство объекта администрирования кластера серверов АдминистрированиеИнформационнаяБаза.ЗапретитьЛокальноеРаспознаваниеРечи.
  • Свойство COM-объекта администрирования кластера серверов IInfoBaseInfo.DisableLocalSpeechToText.
  • Методы объекта Java-интерфейса администрирования кластера серверов InfoBaseInfo: setDisableLocalSpeechToText() и getDisableLocalSpeechToText().
  • Для утилиты администрирования кластера серверов (rac) реализовано свойство информационной базы disable-local-speech-to-text.
  • Параметр запуска автономного сервера (в том числе и в конфигурационном файле) disable-local-speech-to-text.
  • Реализовано управление данной возможностью в стандартной обработке управления серверами.
Данная возможность не предоставлялась.

Запретить локальное распознавание речи было невозможно.

Стало возможно принудительно запрещать локальное распознавание речи. При это удаленное распознавание речи все равно можно использовать.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Хранилище двоичных данных.
Реализована возможность использовать в качестве хранилища двоичных данных любое внешнее хранилище данных, к которому можно получить доступ по протоколу Amazon S3. Реализовано свойство глобального контекста ВнешниеХранилищаДвоичныхДанных. Для доступа к настройкам хранилища двоичных данных и внешнего хранилища двоичных данных требуется право Администрирование. Доработана стандартная функция управления хранилищем двоичных данных.

Возможность использования хранилища S3 в качестве внешнего хранилища двоичных данных требует лицензию КОРП.

Данная возможность включена в статусе бета-версии. Для использования хранилища S3 в качестве внешнего хранилища двоичных данных во время бета-тестирования требуется лицензия на тестирование выделенной функциональности. При отсутствии лицензии на тестирование выделенной функциональности использование данного механизма будет невозможно.

Данная возможность не предоставлялась.

Двоичные данных могли храниться только на компьютере, где развернут кластер серверов «1С:Предприятия».

Расширены возможности хранилища двоичных данных.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Хранилище двоичных данных.
Реализована возможность исключения дублирующихся копий повторяющихся данных (дедупликация). Дедупликация выполняется как при записи данных, так и в фоновом режиме.

Для объекта ИнформацияХранилищаДвоичныхДанных реализованы свойства ОбъемХранимыхДанныхНаДиске и КоличествоДедуплицированныхЭлементов.

Данная возможность не предоставлялась.Хранилище двоичных данных может занимать меньше места на дисковом накопителе в том случае, если в хранилище помещают одинаковые данные.
В документации данное изменение описано здесь и здесь.
Хранилище двоичных данных.
При работе с хранилищем двоичных данных реализованы следующие возможности:
  • Получить статистическую информацию о хранилище двоичных данных.
  • Выполнить очистку хранилища от неиспользуемых данных.
  • Выполнить очистку совместно с выполнением резервного копирования хранилища двоичных данных.

Реализованы методы менеджера хранилища двоичных данных ПолучитьИнформацию(), ОчиститьНеиспользуемоеМестоПоУниверсальнойДате(), ПолучитьУниверсальнуюДатуСозданияРезервнойКопии(). Реализован метод глобального контекста ПолучитьРазмерДанныхБазыДанныхИХранилищаДвоичныхДанных().

Для методов менеджера хранилища двоичных данных СоздатьПолнуюРезервнуюКопию() и СоздатьДифференциальнуюРезервнуюКопию() реализован параметр УниверсальнаяДатаДоКоторойВыполнитьОчистку.

Для стандартной функции Управление хранилищем двоичных данных реализовано отображение информации о хранилище двоичных данных и инструменты по выполнению очистки хранилища от удаленных данных.

Данные возможности не предоставлялись.Расширены возможности администрирования хранилища двоичных данных.
В документации данное изменение описано здесь и здесь.
Автономный сервер.
Хранилище двоичных данных.
В автономном сервере реализована поддержка хранилища двоичных данных.

Для командной строки запуска автономного сервера реализована команда --binary-storage-data.

Данная возможность не предоставлялась.Автономный сервер стал поддерживать хранилище двоичных данных.
В документации данное изменение описано здесь и здесь.
Работа с буфером обмена.
Реализована возможность работы с буфером обмена операционной системы. Реализовано свойство глобального контекста СредстваБуфераОбмена.

Реализованы обработчики события ПриВставкеИзБуфераОбмена для модуля приложения и модуля формы клиентского приложения.

Для объекта СсылкаНаФайл реализованы методы ПолучитьКакСтрокуАсинх() и ПолучитьКакДвоичныеДанныеАсинх().

Работа с буфером обмена недоступна на мобильных устройствах.

Данная возможность не предоставлялась.Реализована возможность программной работы с буфером обмена используемой операционной системы. +
В документации данное изменение описано здесь.
Средства администрирования.
Расширение конфигурации.
Реализована возможность выполнять реструктуризацию таблиц расширений конфигурации информационной базы во время операции тестирования и исправления информационной базы:
  • В диалоге Тестирование и исправление информационной базы реализован пункт Реструктуризация таблиц расширения конфигурации.
  • Для команды /IBCheckAndRepair пакетного режима запуска конфигуратора реализован параметр -RebuildConfigurationExtensions.

Если в процессе тестирования будет выявлено отсутствие таблицы расширения, то такая таблица будет создана, если выбран режим тестирования и исправления. +

Данная возможность не предоставлялась.Механизм тестирования и исправления информационной базы стал лучше соответствовать текущим возможностям платформы «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Средства администрирования.
Расширение конфигурации.
Реализована возможность выполнять операцию тестирования и исправления информационной базы в конкретной области (или областях) разделенной информационной базы:
  • В диалоге Тестирование и исправление информационной базы реализована возможность указать области данных, в которых будет выполняться операция тестирования и исправления.
  • Для команды /IBCheckAndRepair пакетного режима запуска конфигуратора реализован параметр -Z, позволяющий указать области данных, в которых будет выполняться операция тестирования и исправления.

Если разделители не заданы, то операция тестирования и исправления будет выполняться для всей информационной базы. +

Данная возможность не предоставлялась.Механизм тестирования и исправления информационной базы стал лучше соответствовать текущим возможностям платформы «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Средства администрирования.
Расширение конфигурации.
Если при настройке операции тестирования и исправления информационной базы выбраны только параметры Проверка логической целостности расширений конфигурации или Реструктуризация таблиц расширений конфигурации, то монопольный режим для всей информационной базы не требуется и не устанавливается.

Для каждой обрабатываемой области устанавливаются следующие блокировки:

  • Разделяемая, если выбрана только операция тестирования.
  • Исключительная, если выбрана операция тестирования и исправления, а также выявлена необходимость исправления информационной базы.

Ошибка блокировки области не приводит к прерыванию всего процесса тестирования и исправления, но приводит к переходу к следующей области данных. +

Данная возможность не предоставлялась.Механизм тестирования и исправления информационной базы стал лучше соответствовать текущим возможностям платформы «1С:Предприятие».
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность обмена файлами при интеграции системы взаимодействия с WhatsApp.Данная возможность не предоставлялась.Расширены возможности интеграции с системами мгновенного обмена сообщениями.
Расширение конфигурации.
Внешние источники данных.
Реализована возможность создавать собственные внешние источники данных:
  • Таблицы, поля для таблиц внешних источников данных.
  • Функции внешних источников данных.
  • Таблицы измерений, поля таблиц измерений, измерения и ресурсы кубов внешних источников данных.

Реализована возможность заимствовать внешние источники данных. При изменении свойств заимствованных объектов несколькими расширениями конфигурации, значения свойств объектов будут получаться из последнего расширения в списке.

Данная возможность не предоставлялась.Расширены возможности работы с расширением конфигурации.
В документации данное изменение описано здесь.
Средства разработки.
Расширены возможности точки останова с условием при отладке прикладных решений:
  • Включение/выключение точки останова реализовано флажком в диалоге настройки условия точки останова.
  • Для вызова диалога реализовано сочетание клавиш Ctrl+F9.
  • Расширено поле редактирования условия срабатывания точки останова.
  • Реализована возможность указывать, что точка прерывания должна сработать при вызове из такого-то метода конфигурации. Имя метода может быть указано с помощью регулярных выражений. Диалект регулярных выражений аналогичен диалекту регулярных выражений, доступных во встроенном языке.
  • Реализована возможность задавать условие срабатывания точки останова на основании количества попаданий в строку текста на встроенном языке.
  • Реализована возможность указывать действия, которые будут выполнены при попадании в точку останова:
    • Вывести какое-либо сообщение в окно сообщений.
    • Вывести результат вычисления выражения.
    • Вывести стек вызовов встроенного языка.
    • Вывести количество попаданий в точку останова.
    • Для всех перечисленных действий реализована возможность не останавливаться после выполнения действия, а продолжить выполнение встроенного языка.

При нажатии клавиши F9 на отключенной точке останова происходит включение точки останова.

Реализована возможность переносить точку останова (в пределах модуля) с помощью мыши и клавиатуры.

Реализованы возможности запоминать и вставлять точку останова через буфер обмена.

Диалог редактирования условной точки останова содержал только простую строку редактирования условия останова.

При нажатии клавиши F9 на отключенной точке останова происходило удаление точки останова (и потере всех настроек).

Не поддерживались возможности переноса точек останова с помощью клавиатуры, мыши и буфера обмена.

Упрощена отладка прикладных решений. Расширены возможности работы с точками останова. Расширены возможности задания условий условных точек останова. +
В документации данное изменение описано здесь.
Диаграммы.
Система компоновки данных.
Изменено отображение круговой и кольцевой диаграмм (включая объемные варианты этих диаграмм). Реализована возможность управления отображением круговой и кольцевой диаграммы. При отрисовке круговых и кольцевых диаграмм учитывается значение свойства ПоложениеПодписей.

Для объекта Диаграмма реализованы свойства НачальныйУгол, КонечныйУгол, ГлубинаОбъемнойДиаграммы.

Для свойства Диаграмма.ПоложениеПодписей значением по умолчанию будет значение Авто.

Для объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы свойства ТипДиаграммы.НачальныйУгол, ТипДиаграммы.КонечныйУгол и ТипДиаграммы.ГлубинаОбъемнойДиаграммы.

В режиме совместимости с версией 8.3.23 поведение не изменилось.

Данные возможности не предоставлялись.

Для свойства Диаграмма.ПоложениеПодписей значением по умолчанию было значение Край.

Расширены возможности отображения круговых диаграмм.
В документации данное изменение описано здесь, здесь и здесь.
Отображение информации.
В библиотеку картинок добавлены следующие картинки:
  • ФорматированнаяСтрока.
В библиотеке картинок отсутствовали добавленные картинки. Расширен состав библиотеки картинок.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Стандартные функции.
Для стандартной функции История изменения данных реализована возможность управления настройкой использования истории.Данная возможность не предоставлялась.Управлять историей изменения данных можно непосредственно из стандартной функции, без необходимости использования сторонних инструментов.
Система взаимодействия.
В обсуждениях системы взаимодействия реализована отметка прочтения сообщений. Отметка отображается в тонком клиенте, толстом клиенте и веб-клиенте. В мобильном клиенте отметка прочтения не отображается, однако информация о прочтении в мобильном клиенте отображается другими клиентскими приложениями.

Статус прочтения отображается в контекстных обсуждения, в которых количество авторов сообщений и получателей сообщений меньше 100, а также в неконтекстных обсуждениях, в которых:

  • Нет участника «все пользователи».
  • Есть другие участники, кроме текущего пользователя.
  • Общее количество участников в обсуждении меньше 100.
Данная возможность не предоставлялась.Пользоваться обсуждениями системы взаимодействия стало более удобно и наглядно.
Система взаимодействия.
При отправке сообщения в неконтекстное обсуждение системы взаимодействия, данное обсуждение становится первым во всех сеансах данного пользователя в данной информационной базе. Данное поведение реализовано в тонком клиенте, толстом клиенте и веб-клиенте.Порядок неконтекстных обсуждений в разных сеансах одного пользователя информационной базы мог быть разным.Пользоваться обсуждениями системы взаимодействия стало более удобно.
Копии базы данных.
Для стандартной функции управления копиями базы данных реализована возможность указания, какое количество фоновых заданий должно выполнять первоначальное заполнение таблиц копии. В форме Параметры копий базы данных реализован параметр Количество заданий заполнения.Данная возможность не предоставлялась.

Первоначальное заполнение таблиц копии данными всегда выполнялось с использованием 4 фоновых заданий. Это количество нельзя было изменить интерактивно, только с помощью встроенного языка.

Администратор получил возможность управлять интенсивностью первоначального заполнения таблиц копии базы данных.
Технологический журнал.
При работе тонкого и толстого клиентских приложений реализовано формирование технологического журнала процессом видеомодуля системы взаимодействия. Также реализовано формирование дампов аварийного завершения процессов видеомодуля. Настройка выполняется с помощью стандартного файла настройки технологического журнала logcfg.xml.

При использовании 32-разрядной системы «1С:Предприятие» под управлением 64-разрядной операционной системы, не поддерживается использование внешней программы создания дампов аварийного завершения. Дамп аварийного завершения процесса видеомодуля выполняется из самого процесса.

Реализованы события технологического журнала <VIDEOCALL>, <VIDEOCONN>, <VIDEOSTATS>.

Данная возможность не предоставлялась.Упрощено предоставление информации в техническую поддержку в случае выявления каких-либо проблем при работе видеомодуля системы взаимодействия.
В документации данное изменение описано здесь, здесь и здесь.
Средства администрирования.
Реализована возможность автоматического удаления установленных версий платформы. Удаление будет выполняться отдельным процессом с пониженным приоритетом. Процесс удаления не взаимодействует с пользователем. Настройка параметров автоматического удаления реализована в диалоге настройки интерактивной программы запуска.

Реализована возможность явно указать одну или несколько версии системы, которые не должны удаляться автоматически.

Для конфигурационных файлов 1cestart.cfg и 1cescmn.cfg реализованы параметры AutoUninstall, AutoUninstallVersionsAfter, DontUninstallVersion.

Данная возможность не предоставлялась.

Удалять неиспользуемые версии было необходимо или вручную или с помощью самостоятельно написанных пакетных файлов.

Упрощено администрирование системы в части удаления более не используемых версий платформы «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Веб-клиент.
При выполнении некоторых операций (которые могут выполняться продолжительное время) в веб-клиенте курсор мыши меняет свои вид с указателя основного режима на указатель занятости.В веб-клиенте указатель мыши всегда находился в основном режиме.Поведение веб-клиента стало более удобно для пользователя.
Расширение конфигурации.
Табличный документ.
Уменьшено время первого получения макета, который расширен несколькими расширениями конфигурации. Расширенный макет кешируется для дальнейшего использования.

Кеш сохраняется до тех пор, пока не будут внесены изменения либо в расширяемый макет, либо в расширение, которое содержит расширение для этого макета.

Первое получение макета, который расширен несколькими расширениями конфигурации, занимало больше времени.Ускорена работа с макетами, которые расширяются несколькими расширениями конфигурации.
Система взаимодействия.
Переработан механизм определения (и отображения) говорящего пользователя в окне видеоконференции. Унифицировано отображение говорящего и поведение окна видеоконференции в различных клиентских приложениях.Определение говорящего пользователя и отображение окна видеоконференции было другим и различалось в разных клиентских приложениях.Улучшен интерфейс окна видеоконференции. Упростилось понимание того, какой пользователь говорит в данный момент (или у какого пользователя передается шум через микрофон).

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Копии базы данных.
 +

Ускорено первоначальное заполнения копии базы данных для объектов метаданных с табличными частями.

Первоначальное заполнения копии базы данных для объектов метаданных с табличными частями занимало больше времени.Ускорено первоначальное заполнения копии базы данных для объектов метаданных с табличными частями.
Кластер серверов.
Снижена общая нагрузка на компьютеры кластера серверов (сеть, оперативная память и процессоры) при большом количестве пользователей. Увеличена стабильность работы кластера серверов.При большом количестве пользователей кластера наблюдалось более высокое потребление оперативной памяти, процессора и сетевых соединений.Повышена стабильность работы кластера серверов при большом количестве пользователей.
Кластер серверов.
Средства администрирования.
При выполнении тестирования и исправления информационной базы оптимизировано выполнение операций проверки логической и ссылочной целостности в клиент-серверном варианте информационной базы.

Для команды /IBCheckAndRepair пакетного запуска Конфигуратора реализован параметр -JobsCount, который определяет количество системных фоновых заданий, которое используется для выполнения тестирования и исправления информационной базы.

Тестирование и исправление информационной базы выполнялось последовательно по таблицам информационной базы.Повышена скорость выполнения тестирования и исправления информационной базы.
В документации данное изменение описано здесь.
Система взаимодействия.
Улучшено качество звука в видеозвонках.Качество звука в видеозвонках было хуже.Улучшено качество звука в видеозвонках.
Полнотекстовый поиск.
Улучшена релевантность выдачи в результатах полнотекстового поиска в данных.

Для получения эффекта от данной оптимизации, необходимо очистить индекс полнотекстового поиска и заново его создать на платформе 8.3.24.

Платформа «1С:Предприятие» версии 8.3.23 и предыдущих версий выполнит очистку индекса, если он был построен версией 8.3.24.

Полнотекстовый поиск возвращал результаты, упорядоченные по набору критериев, который обеспечивал низкую релевантность выдачи.Результаты полнотекстового поиска стали более релевантны запросу пользователя.
Полнотекстовый поиск.
Ускорена индексация данных полнотекстовым поиском. Снижен объем промежуточных файлов, которые используются для индексации.Индексация данных для нужд полнотекстового поиска занимала больше времени и требовала больше места под временные файлы, используемые для индексации.Ускорена индексация данных для нужд полнотекстового поиска.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
Реализована возможность после аутентификации пользователя завершить «лишние» сеансы этого пользователя и продолжить работу. Эта возможность предоставляется в том случае, если после аутентификации обнаруживается, что в данной информационной базе уже есть сеансы этого пользователя и эти сеансы препятствуют началу нового сеанса.

Такое поведение реализовано после полного завершения аутентификации для следующих ситуаций:

  • Ошибка монопольного доступа к информационной базе или области данных.
  • Нехватка клиентских лицензий.
  • Запрет на начало сеанса, полученный от сервиса внешнего управления сеансами.
Данная возможность не предоставлялась.Упрощено решение проблем, которые возникают во время аутентификации пользователя при ограничении числа сеансов после зависания, аварийного завершения или при недоступности «лишнего» приложения.
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.17.Версия формата выгрузки конфигурации в XML-файлы была равна 2.16.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа в ОС Linux.
Программа установки «1С:Предприятия» для ОС Linux поставляется в zip-архиве. В состав архива включено приложение installAsRoot, которое позволяет выполнить установка от лица суперпользователя (root) максимально просто.

Во время работы программы установки происходит попытка установить все необходимые (для работы платформы) компоненты ОС. Если попытка не удалась, то в качестве сообщения об ошибке выводится сообщение пакетного менеджера ОС.

При установке создается только один ярлык - на интерактивную программу запуска. Остальные ярлыки можно создать с помощью пункта программы установки Установить ярлыки (или параметра desktop_icons пакетной установки системы).

При установке добавляет ярлык программы удаления платформы.

Имена ярлыков, которые создаются программой установки, стали короче и лучше отражают действия, выполняемые при использовании ярлыка. Имена ярлыков стали отображаться в несколько строк.

Процесс установки системы «1С:Предприятие» на ОС Linux был более сложен для обычного пользователя.

Программа установки не пыталась установить компоненты ОС, которые необходимы для работы системы.

Сообщения об ошибках, которые могли возникать в процессе установки, не позволяли адекватно понять причину ошибки.

Упрощена установка, запуск и деинсталляция системы «1С:Предприятие» с компьютера, работающего под управлением ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Автономный сервер.
В процессе обновления конфигурации базы данных автономный сервер выводит в стандартный поток вывода идентификатор нового поколения информационной базы.

В механизме выборочной загрузки объектов метаданных из xml-файлов реализован режим частичной загрузки внешних свойств, при котором не требуется загрузка самих объектов метаданных, которым принадлежат данные свойства. Также реализована поддержка независимой загрузки модулей форм без загрузки самих форм. Реализован параметр partial для следующих команд:

  • Для команды config load-config-from-files агента конфигуратора и SSH-шлюза автономного сервера.
  • Для команды /LoadConfigFromFiles пакетного режима запуска Конфигуратора.
  • Для команды infobase config import утилиты управления автономным сервером (ibcmd).
Данные возможности не предоставлялись.В ряде сценариев ускорено обновление конфигурации базы данных автономным сервером.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Навигационные ссылки.
Навигационная ссылка, сформированная методом ПолучитьНавигационнуюСсылкуИнформационнойБазы() и в диалоге получения навигационной ссылки, с установленным признаком Внешняя ссылка, содержит в своем составе разделители, используемые в текущем сеансе разделенной информационной базы. Если получение ссылки выполняется в веб-клиенте или тонком клиенте, подключенном через веб-сервер, в навигационной ссылке будут размещены только те разделители, которые не участвуют в формировании адреса информационной базы. Разделители указываются аналогично параметру Z командной строки запуска клиентского приложения.

При запуске клиентского приложения с параметром URL, выполняется поиск клиентского приложения с учетом значений разделителей, указанных в навигационной ссылке. Аналогичные действия выполняются при попытке перехода по внешней навигационной ссылке из диалога Перейти по ссылке, из строки глобального поиска и с помощью метода ПерейтиПоНавигационнойСсылке().

В режиме совместимости с версией 8.3.23 поведение не изменилось.

Навигационная ссылка, сформированная методом ПолучитьИнформационнуюСсылкуИнформационнойБазы() и в диалоге получения навигационной ссылки, с установленным признаком Внешняя ссылка, не содержала значений разделителей текущего сеанса для разделенной информационной базы.

При попытке перехода по внешней навигационной ссылке не учитывались значения разделителей при поиске запущенного приложения, что могло приводить к ошибкам при выполнении перехода по навигационной ссылке.

При переходе по внешней навигационной ссылке, которая сформирована в разделенной информационной базе, учитываются значения разделителей, которые использовались в сеансе, в котором получена навигационная ссылка. Таким образом, пользователь будет открывать объекты в той же области данных, что и область данных, в которой получали навигационную ссылку.
В документации данное изменение описано здесь и здесь.
Динамический список.
Из списка полей динамического списка, которые могут использоваться для упорядочивания списка, исключаются поля, которые являются полями составного типа и содержат более 100 типов.

В режиме совместимости с версией 8.3.23 поведение не изменилось.

Список полей, которые могут использоваться для упорядочивания динамического списка, не ограничивался по размеру составного типа поля динамического списка.При настройке динамического списка снижена вероятность создать сортировку, которая приведет к очень медленной работе динамического списка или его (списка) полной неработоспособности (например из-за ошибки СУБД, которая возникает при попытке отобразить список).
В документации данное изменение описано здесь и здесь.
Отображение информации.
Форма клиентского приложения.
Табличный документ.
Для табличного документа реализована возможность использования форматированной строки в ячейках и рисунках. Реализована возможность экспорта таких табличных документов в следующие форматы:
  • Microsoft Office OpenXML (Microsoft Word 2007 и последующих) и HTML - полностью.
  • Microsoft Office OpenXML SpreadsheetML (Microsoft Excel 2007 и последующих), OpenDocument Spreadsheet (*.ods) и PDF с некоторыми ограничениями:
    • Экспорт внедренных в форматированные строки картинок и гиперссылок не поддерживается.
    • Экспорт цвета фона не поддерживается.
    • Экспорт цвета шрифта в формат XLS (Microsoft Excel 95-2003) не поддерживается.

В редакторе табличного документа реализована возможность переключения между обычной и форматированной строкой. Реализована возможность редактирования форматированной строки.

Для поля табличного документа реализовано событие ОбработкаНавигационнойСсылки.

Свойство Текст объектов ОбластьЯчеекТабличногоДокумента и РисунокТабличногоДокумента может принимать тип Строка или ФорматированнаяСтрока.

В мобильной платформе поведение не изменяется - форматированная строка не поддерживается.

Данная возможность не предоставлялась.Стало возможно улучшить оформление табличного документа.
Хранилище конфигурации.
Реализована возможность настроить хранилище конфигурации таким образом, что будет невозможно создавать пользователей без указания пароля.

В помощнике создания хранилища реализована страница с указанием политики паролей: минимальная длина пароля и необходимость проверки сложности пароля. В диалоге администрирования хранилища реализована возможность редактировать эти же параметры. Если указать минимальную длину пароля равно 0, то можно будет создавать пользователей без указания пароля.

В списке пользователей хранилища реализована колонка, показывающая пароль у каждого пользователя.

Для команды /ConfigurationRepositoryCreate пакетного запуска Конфигуратора реализованы параметры -MinPasswordLength и -CheckPasswordComplexity.

Для глобального файла настроек хранилища конфигурации cfgrepo.conf реализованы параметры cfgrepo.users.minPasswordLength и cfgrepo.users.checkPasswordComplexity.

Рекомендуется администраторам хранилищ конфигураций проанализировать списки пользователей в администрируемых хранилищах и установить пароли для всех пользователей.

Хранилище конфигурации было невозможно настроить таким образом, чтобы при создании пользователя требовалось указывать пароль.Снижена вероятность несанкционированных изменений конфигурации, расположенной в хранилище, которые могут быть выполнены от имени любого пользователя хранилища без пароля.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
История данных.
Изменения, сделанные в обработчиках события ПриЗаписи(), не входят в записываемую версию данных.Версия данных, которая записывалась в историю, включала в себя изменения, сделанные в обработчиках события ПриЗаписи().Устранено некорректное поведение системы.
Работа с криптографией.
Упрощена инициализация менеджера криптографии. Реализован конструктор менеджера криптографии, в котором необходимо указать только вариант использования интерактивного режима. Параметры для каждой операции определяются по контексту этой операции.

Реализована возможность указания алгоритмов (шифрования, хеширования, подписи), которые будут использоваться для выполнения операции, с помощью OID алгоритма. Возможность указания алгоритмов путем наименования сохранена, но для четкой идентификации рекомендуется использовать OID.

Реализована возможность определять приоритеты использования алгоритмов хеширования и шифрования. Для менеджера криптографии реализованы свойства ОпределениеАлгоритмаХеширования и ОпределениеАлгоритмаШифрования.

Реализован унифицированный способ получения сертификата не только из зашифрованных или подписанных данных, но и из произвольного хранилища сертификатов. Для менеджера криптографии реализованы методы ПолучитьСертификаты() и ПолучитьСертификатыАсинх(). Методы менеджера криптографии ПолучитьСертификатыИзПодписи(), ПолучитьСертификатыИзПодписиАсинх() и НачатьПолучениеСертификатовИзПодписи() объявлены устаревшими и не рекомендуются к применению.

Реализована возможность поиска на локальном компьютере контейнера ключа для используемого сертификата. Для менеджера криптографии реализованы методы НайтиКлючевойКонтейнер() и НайтиКлючевойКонтейнерАсинх().

Реализована возможность указания конкретного сертификата и пароля доступа к закрытому ключу, с помощью которых будет выполняться расшифровка данных. Для методов Расшифровать(), РасшифроватьАсинх() и НачатьРасшифровку() реализованы параметры Сертификат и ПарольДоступаКЗакрытомуКлючу.

Реализовано свойство ИнформацияМодуляКриптографии.ТипМодуляКриптографии.

При инициализации менеджера криптографии было необходимо указать имя и тип модуля криптографии, а также путь к модулю криптографии.

Алгоритмы, которые используются для той или иной операции, могли быть указаны только по имени.

Отсутствовала возможность указания приоритетов использования алгоритмов хеширования и шифрования. Алгоритмы, указанные в методах менеджера криптографии, могли игнорироваться при выполнении операции.

Отсутствовала возможность получения списка сертификатов из зашифрованных данных. Имелась возможность получения списка сертификатов только из подписи данных (методы менеджера криптографии ПолучитьСертификатыИзПодписи(), ПолучитьСертификатыИзПодписиАсинх() и НачатьПолучениеСертификатовИзПодписи()).

Отсутствовала возможность проверить наличие на компьютере контейнера ключа для используемого сертификата.

При расшифровке данных можно указать только одного получателя расшифровываемых данных, других получателей указать было невозможно.

Упрощено использование менеджера криптографии в основных сценариях.
В документации данное изменение описано здесь и здесь.
Автономный сервер.
Из параметров автономного сервера исключены:
  • Параметр --debug-server-password утилиты ibsrv.
  • Параметр password секции debug - server конфигурационного файла автономного сервера.

Указание удаленных параметров не приводят к ошибке. Сами параметры игнорируются.

В параметрах автономного сервера ошибочно описывалась возможность указать пароль для доступа к серверу отладки в автономном сервере. Заданный пароль никогда не использовался.Устранена ошибка в параметрах автономного сервера.
В документации данное изменение описано здесь и здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Англоязычное написание имени параметра ОписаниеОповещения в методах встроенного языка.
  • NotifyDescription.
  • CallbackDescription.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Сборщик мобильных приложений.
Обработка режима совместимости в мобильной платформе приведена в соответствие с аналогичным поведением платформы для персонального компьютера.

Конфигуратор выгружает информацию о режиме совместимости конфигурации в файлы 1cema.xml и 1cemca.xml.

Сборщик мобильных приложений учитывает режим совместимости при сборке мобильных приложений. Если режим совместимости конфигурации не соответствует мобильной версии, которая используется для сборки мобильного приложения, сборка завершится с ошибкой.

Режим совместимости определялся версией мобильной платформы на которой выполнялось начальное создание информационной базы или выполнялось обновление конфигурации.

Сборщик мобильных приложений никак не проверял соответствие режима совместимости конфигурации и мобильной платформы, которая используется для сборки мобильного приложения.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Для мобильной платформы и мобильного клиента с автономным режимом реализована поддержка определяемых типов.Данная возможность не предоставлялась.Расширены возможности мобильной версии системы «1С:Предприятие».
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Реализована доступность на сервере мобильной платформы и платформы для персонального компьютера для объектов ДанныеМультимедиа, ПараметрыКачестваСканированияДокументов и СтраницаСканированияДокументов.Данная возможность не предоставлялась.Упрощена реализация работы с документами, которые сканируются не для отправки в сервис распознавания, а для сохранения в информационную базу.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Специальные возможности мобильного устройства.
В мобильной версии системы «1С:Предприятие» реализована поддержка Huawei Mobile Services (HMS). Поддерживаются следующие возможности этого набора сервисов: работа с картой (включая получения адреса по координатам и обратную операцию), зоны геолокации. работа с уведомлениями, реклама и встроенные покупки.

Реализовано значение системного перечисления ТипПодписчикаДоставляемыхУведомлений.HPK. Для метода ПолучитьМаркерДоступа() менеджера отправки доставляемых уведомлений реализован параметр ТипПодписчика (в методе стало 3 параметра). Метод ПолучитьМаркерДоступа() с двумя параметрами объявляется устаревшим и его использование не рекомендуется.

Реализовано значение системного перечисления СервисВстроенныхПокупок.HuaweiInAppPurchase.

В сборщике мобильных приложений реализована возможность указывать, работу с какими сервисами будет поддерживать собираемое мобильное приложение (включая возможность отключения обоих сервисов). Если на мобильном устройстве используются оба набора сервисов - приоритетным считается набор сервисов Google (приоритет не настраивается). Реализована возможность отключить оба набора сервисов, если собираемое приложение не использует возможности мобильных сервисов (уменьшится размер собираемого приложения). Публикация собранного приложения в магазин Huawei AppGallery из сборщика мобильных приложений не поддерживается.

Сервисы Huawei Mobile Services (HMS) не поддерживались мобильной версией «1С:Предприятие». Из-за этого было невозможно полноценное использование мобильной версии системы на устройствах Huawei.Расширен перечень поддерживаемых мобильных сервисов.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Мобильный клиент.
Распознавание речи.
В мобильном клиенте (в том числе с автономным режимом) реализована возможность использования механизма распознавания речи. Не поддерживается возможность механизма распознавания речи непосредственно на самом мобильном устройстве. Серверные методы работы с механизмом распознавания речи не поддерживаются в серверной части мобильного приложения и в мобильном автономном сервере.

Реализована функциональность РаспознаваниеРечи. Если в собираемом приложении отсутствует требование данной функциональности, то попытка обращения к механизмам распознавания речи (в собранном приложении) приведет к исключению времени исполнения.

Механизм распознавания речи не мог использоваться в мобильном клиенте.Расширены возможности мобильного клиента системы «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Системные требования.
В мобильной версии системы «1С:Предприятие» реализована поддержка ОС Android 13. В мобильной версии системы «1С:Предприятие» прекращена поддержка ОС Android 4.4. Таким образом, мобильная версия «1С:Предприятие» поддерживает ОС Android в интервале версий 5.0 - 13.

Для того, чтобы загрузить мобильное приложение в магазин Google Play, необходимо собрать мобильное приложение с использованием мобильной версии 8.3.24.40 или последующих.

При работе мобильного приложения под управлением ОС Android 13 и последующих версий:

  • Будет использоваться разрешение Размещение уведомлений, которое описывает, зачем пользователю необходимы оповещения в шторке мобильного устройства. Это разрешение используется при использовании геозон, уведомлений, видеозвонков и записи звука.
  • Для доступа к библиотеке ауидо и библиотеке картинок и видеофайлов требуется устанавливаться соответствующие функциональности (по аналогии с iOS). При использовании ОС Android предыдущих версий будет использоваться функциональность Воспроизведение аудио и вибрация.
Мобильная версия «1С:Предприятие» поддерживала ОС Android в интервале версий 4.4 - 12.

Мобильные приложения, которые собираются с использованием мобильных версий, предшествующих версии 8.3.24.40, будет невозможно загрузить в магазин Google Play после 1 ноября 2023 года.

Мобильная версия «1С:Предприятия» поддерживает актуальный состав версий операционной системы Android.
В документации данное изменение описано здесь.
Специальные возможности мобильного устройства.
Для мобильного приложения более не требуется получать разрешение пользователя для доступа к каталогу документов приложения.

Если отключена функциональность Доступ ко всем файлам, то при попытке доступа к файлам за пределами каталога данных приложения будет формироваться сообщение о том, что выключена требуемая функциональность.

Реализована функциональность Геозоны, которая управляет возможностью работы с геозонами.

При первом запуске приложения запрашивался доступ к каталогу документов приложения.

При попытке доступа к файлу за пределами каталога документов приложения формировалась ошибка доступа к файлу.

Работа с геозонами определялась функциональностью Геопозиционирование в фоновом режиме.

Устранено незапланированное поведение системы.

Поведение системы стало более логичным.

В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Для мобильной версии реализована возможность получать файлы, которыми пользователь поделился из других приложений на мобильном устройстве. Во время настройки механизма можно указать, что мобильное приложение будет обрабатывать какие-то конкретные расширения файлов или все расширения.

Реализовано свойство глобального контекста ДанныеЗапросаПоделитьсяЗапуска. Реализован обработчик события модуля приложения ОбработкаФормированияКомандВходящегоЗапросаПоделиться(). Для системного перечисления ФункциональностьМобильногоПриложения реализованы свойства ВходящиеЗапросыПоделиться и ОбработкаВсехТиповВходящихЗапросовПоделиться.

Данная возможность не предоставлялась.В мобильном приложении, созданном на базе системы «1С:Предприятие», стало возможно получать файлы, которыми поделились из других приложений с помощью стандартного механизма соответствующей мобильной операционной системы.
В документации данное изменение описано здесь и здесь.

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Встроенный язык.
Если метод табличной части Найти() не находит искомое значение и список колонок поиска состоит только из колонки НомерСтроки, то поиск по другим колонкам не выполняется.

Рекомендуется проанализировать использование данного метода и устранить возможное использование некорректного поведения.

В режиме совместимости с версией 8.3.23 поведение не изменилось.

Если метод табличной части Найти() не находит искомое значение и список колонок поиска состоит только из колонки НомерСтроки, то выполнялся поиск по всем колонкам табличной части.Устранено некорректное поведение системы.
Табличный документ.
При заполнении табличного документа реализована поддержка форматированных строк в ячейках с типом заполнения Шаблон.

При замене имени параметра на фактическое значение, форматирование результирующего текста определяется по первому символу имени параметра, картинки и ссылки внутри имени параметра удаляются. Остальные приемы работы с шаблонами не изменяются.

При заполнении табличного документа не поддерживались форматированные строки в ячейках с типом заполнения Шаблон.Расширена поддержка форматированных строк в табличном документе.
Установка клиентского приложения.
При работе под управлением ОС Windows, в настройках диалога запуска клиентского приложения и параметров информационной базы реализована возможность указания автоматического способа разрядности запускаемого клиентского приложения.

Если для работы с информационной базой запущено 32-разрядное приложение, то при автоматическом обновлении клиентского приложения будет скачиваться дистрибутив именно 32-разрядного приложения.

При автоматическом обновлении клиентского приложения, для скачивания выбиралось приложение, разрядность которого совпадала с разрядностью операционной системы, под управлением которой работало клиентское приложение. На разрядность запущенного клиентского приложения при обновлении внимания не обращалось.Упрощено автоматическое обновление клиентского приложения в тех случаях, когда на 64-разрядной ОС Windows используется 32-разрядное клиентское приложение (например, из-за того, что клиентское приложение использует внешние компоненты, которые существуют только в 32-разрядном варианте).
В документации данное изменение описано здесь, здесь и здесь.
Средства разработки.
Для копирования настроек точки останова в буфер обмена используется комбинация клавиш Ctrl+Alt+K.

Комбинация клавиш Ctrl+Alt+C была ранее (в предыдущих версиях платформы) указана для открытия окна стека вызовов.

Для копирования настроек точки останова в буфер обмена использовалась комбинация клавиш Ctrl+Alt+C.Устранено некорректное поведение системы. +
Сборщик мобильных приложений.
В сборщике мобильных приложений реализована возможность экспорта ключей, связанных с магазинами приложений Google Play и Huawei AppGallery. Возможность реализована в виде диалога, который можно вызвать из диалога редактирования параметров поставщика и из диалога редактирования группы мобильных приложений.

Выгружается следующая информация:

  • Закрытый ключ подписи приложения (для Google Play, необходимо указанием ключа шифрования из консоли разработчика магазина приложений).
  • Закрытый ключ и сертификат подписи приложения (для обоих магазинов).
  • Сертификат ключа загрузки приложения (для обоих магазинов).
Экспорт ключей поддерживался только для магазина Google Play, в формате, который перестал поддерживаться магазином.Восстановлена возможность работы с магазином Google Play из-за изменения магазином процедуры шифрования ключа подписи.

Стало возможно использовать загрузку aab-файлов в магазин приложения Huawei AppGallery.

В документации данное изменение описано здесь.
Стандартные функции.
В сервисе сборки мобильных приложения реализована поддержка мобильной версии 8.3.24 системы «1С:Предприятие». С помощью сервиса сборки стало возможно собирать мобильные приложения, работающие под управлением ОС Android, которые используют мобильные сервисы компании Huawei.Данные возможности не предоставлялись.Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Система взаимодействия.
Для сайта внешних пользователей и чата на сайте реализованы возможности:
  • Продолжить видеозвонок на другом устройстве.
  • Автоматическая переустановка соединения в видеозвонке при потере или ухудшении связи.

Улучшен интерфейс видеозвонков.

Данные возможности не предоставлялись.Возможности, которые предоставляет сайт внешних пользователей, приближены к возможностям клиентских приложений.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Postgres Pro версии 11.22.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.17.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Postgres Pro версии 12.17.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Postgres Pro версии 13.13.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Postgres Pro версии 14.10.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Postgres Pro версии 15.5.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Система компоновки данных.
Снижено время открытия схемы компоновки данных в том случае, когда план видов расчета содержит много предопределенных элементов.Открытие схемы компоновки данных занимало много времени, если план видов расчета содержит много предопределенных элементов.Устранено незапланированное поведение системы.
Работа в ОС Linux.
Для работы с объектами HTML в клиентских приложениях для ОС Linux используется библиотека WebKit2. Библиотека WebKit2 не поставляется в составе платформы, а используется библиотека, находящаяся в составе используемой операционной системы. Для обеспечения возможности предварительного просмотра содержимого поля HTML-документа используется библиотека evince. Если библиотеки не установлены, то они будут доустанавливаться во время установки системы «1С:Предприятие» из репозиториев используемой операционной системы.

Библиотека WebKit1 более не используется и не поставляется в составе системы «1С:Предприятие».

Для работы с объектами HTML в клиентских приложениях для ОС Linux использовалась библиотека WebKit1, которая входила в состав дистрибутива системы «1С:Предприятие».Для работы с объектами HTML используется более современная библиотека.
Система аналитики.
Аналитика - источники.
При построении отчета пользователю стало доступно управление местом выполнения отчета (аналогично объекту Запрос системы «1С:Предприятие»). Для настройки доступы следующие параметры: Использование копий БД, Актуальность данных, Время актуальности.Данная возможность не предоставлялась.Расширены возможности управления местом выполнения отчета в клиентском приложении «1С:Аналитики».
Расширение конфигурации.
В конфигураторе базовой версии системы «1С:Предприятие» реализована доступность формы работы с расширениями конфигурации (Главное меню - Конфигурация - Расширения конфигурации). В этой форме доступны функции интерактивного администрирования расширений (расширения, которые могут быть подключены к базовой конфигурации, должны быть подписаны тем же ключом, что и сама базовая конфигурация). Функции редактирования расширений остаются недоступными. Подключенное расширение доступно для просмотра.

+

Данная возможность не предоставлялась.

Подключать и отключать расширения можно было только с помощью пакетного режима запуска Конфигуратора.

Расширены возможности администрирования базовой версии системы «1С:Предприятие».
В документации данное изменение описано здесь.
Внешние компоненты.
Реализован метод глобального контекста СоздатьОбъектВнешнейКомпонентыАсинх() позволяющий выполнить асинхронное создание объекта внешней компоненты.Данная возможность не предоставлялась.

Объект внешней компоненты на стороне клиентского приложения можно было создать только с помощью синхронного конструктора, что в ряде случаев могло приводить к ошибкам при использовании внешней компоненты.

Снижена вероятность ошибки, если метод внешней компоненты вызывается сразу после создания объекта этой внешней компоненты. Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Обновление конфигурации базы данных.
При выполнении реструктуризации информационной базы устранено удаление завершающих пробельных символов (категория символов Mark, spacing combining стандарта Unicode), если при реструктуризации не выполнялась смена типа реквизита. При конвертации строки фиксированной длины в строку переменной длины, во время реструктуризации удаляются пробелы справа до первого символа, отличного от пробела.При выполнении реструктуризации информационной базы обрезались завершающие пробельные символы (категория символов Mark, spacing combining стандарта Unicode). При конвертации строки фиксированной длины в строку переменной длины, во время реструктуризации выполнялось удаление не только завершающих пробелов, но и завершающих пробельных символов.Устранено некорректное поведение системы.
Мобильная платформа.
Мобильный клиент.
Системные требования.
Реализована поддержка мобильных операционных систем:
  • для ОС Android: версия 14.
  • для ОС iOS: версии 15 - 17.
Поддерживались следующие версии мобильных операционных систем:
  • для ОС Android: версии 5 - 13.
  • для ОС iOS: версии 9 - 14.
Расширен список поддерживаемых мобильных операционных систем.
В документации данное изменение описано здесь.
Системные требования.
Работа в ОС Linux.
Реализована поддержка следующих дистрибутивов операционной системы Linux:
  • Альт СП 10,
  • Debian 12.
Данные дистрибутивы не поддерживались.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Системные требования.
Работа в ОС Linux.
Прекращена поддержка следующих дистрибутивов операционной системы Linux:
  • Mint 19,
  • Ubuntu 18.04 LTS,
  • Альт Образование 9,
  • Альт Рабочая станция 9,
  • Альт Рабочая станция К9,
  • Альт Сервер 9.
Система «1С:Предприятие» поддерживала работу в следующих дистрибутивах операционной системы Linux::
  • Mint 19,
  • Ubuntu 18.04 LTS,
  • Альт Образование 9,
  • Альт Рабочая станция 9,
  • Альт Рабочая станция К9,
  • Альт Сервер 9.
Прекращена поддержка устаревших дистрибутивов операционной системы Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Система лицензирования.
Для активации программной лицензии с помощью файла реализованы новые адреса сервисов. Механизмы платформы используют новые адреса сервисов. Прежние версии сервисов планируется отключить.

Адрес сервиса имеет вид: https://portal.1c.ru/support/license/license-from-file?lang=LL или https://portal.1c.eu/support/license/license-from-file?lang=LL (в зависимости от текущих настроек и версии системы), где LL - двухбуквенный код языка локализации запущенного экземпляра системы"1С:Предприятие» .

Для активации программной лицензии с помощью файла использовался сервис, расположенный по адресу https://users.v8.1c.ru/lc.Реализовано использование более современного сервиса для активации лицензии с помощью файла.
В документации данное изменение описано здесь.
Работа с Интернет.
Для объектов HTTPСоединение, FTPСоединение и WSПрокси реализована возможность указания таймаута с точностью до сотых долей секунды (2 знака после запятой).Для объектов HTTPСоединение, FTPСоединение и WSПрокси таймаут, указанный дробным числом, округлялся до ближайшего целого числа секунд.При работе с Интернет-сервисами стало возможно более точно указывать значения таймаутов операций.
Работа с криптографией.
Реализована возможность формирования присоединенной электронной цифровой подписи файл.

Реализована поддержка нескольких подписей документа, т.е. проверка выполняется не только для первой подписи, а для всех электронных подписей файл.

Реализована возможность добавления и удаления сертификатов в хранилище корневых сертификатов и сертификатов промежуточных удостоверяющих центров.

При добавлении архивной метки времени реализовано добавление не подписываемого атрибута ats-hash-index-v3.

Реализовано свойство ВключениеДанныхВПодпись для менеджера криптографии. Для менеджера криптографии реализованы методы ПроверитьНаличиеДанныхВПодписи(), ПроверитьНаличиеДанныхВПодписиАсинх(), ПолучитьДанныеИзПодписи(), ПолучитьДанныеИзПодписиАсинх(). В методах ПроверитьПодпись() и ПроверитьПодписьАсинх() реализована возможность работы с присоединенной электронной цифровой подписью. Реализовано свойство ПодписьКриптографии.Данные.

Поддерживалась работа только с отсоединенной цифровой подписью файла.

При проверке цифровой подписи выполнялась проверка только первой электронной цифровой подписи.

Не поддерживалось добавление и удаление сертификатов в хранилище корневых сертификатов и сертификатов промежуточных удостоверяющих центров.

При добавлении архивной метки времени добавлялся не подписываемый атрибут ats-hash-index.

Расширены возможности работы с механизмом криптографии.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Tantor SE 1C версии 15.6.1.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данная версия СУБД Tantor SE не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь.
Тестирование и исправление информационной базы.
Данное изменение отменено.

В режиме Проверка логической целостности операции тестирования и исправления информационной базы реализована возможность обнаружения (и удаления) пустых таблиц инициализированных предопределенных данных.

Данная возможность не предоставлялась.Снижена вероятность возникновения не информативных ошибок при работе с разделенной информационной базой.
Работа с СУБД.
Оптимизирована работа оператора запроса В() при работе с СУБД PostgreSQL (и наследуемых СУБД) в том случае, когда запрос формируется самой платформой «1С:Предприятие».При работе с СУБД PostgreSQL (и наследуемых СУБД) запросы с оператором В(), формируемые самой платформой «1С:Предприятие», выполнялись за большее время.При работе с СУБД PostgreSQL (и наследуемых СУБД) ускорена работа запросов, формируемых самой платформой «1С:Предприятие», если в них используется список значений для отбора в какой-либо таблице (оператор языка запросов В()).
Мобильный клиент.
Для версий мобильного клиента, которые не обеспечивают возможность смены пароля пользователя, при необходимости смены пароля пользователя, отображается корректное сообщение, описывающее сложившуюся ситуацию. В этом же сообщении приводятся действия, которые требуется выполнить пользователю.В версиях мобильного клиента, не обеспечивающих смену пароля пользователя, сообщение о необходимости смены пароля пользователя было непонятным и не описывало ситуацию..Поведение мобильного клиента стало более понятным.
Пользователи информационной базы.
Письмо, которое отправляется пользователю стандартным сервисом восстановления пароля, содержит явное указание на то, что восстанавливается пароль для входа в приложение «1С:Предприятия».Письмо, которое отправлялось пользователю стандартным сервисом восстановления пароля, не содержало явного указание на то, что восстанавливается пароль для входа в приложение «1С:Предприятия».При чтении письма пользователю понятно, куда ему предлагается восстановить пароль.
Работа в macOS.
Системные требования.
Реализована поддержка ОС macOS версии 15.Работа системы «1С:Предприятие» не поддерживалась под управлением ОС macOS версии 15.Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь и здесь.
Работа в ОС Linux.
Системные требования.
Реализована поддержка следующих дистрибутивов ОС Linux:
  • Для архитектуры x86 и x86-64:
    • Astra Linux Specail Edition 1.8 (только с ядром generic).
    • Mint 22.
    • Simply Linux 10.
    • Ubuntu 24.04 LTS.
    • РЕД ОС 8.
  • Для архитектуры ARM64:
    • Astra Linux Specail Edition 1.8 (только с ядром generic).
    • Simply Linux 10.
    • Ubuntu 24.04 LTS.
Данные дистрибутивы не поддерживались.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Дата акселератор.
Системные требования.
Изменен список дистрибутивов ОС Linux, при работе в которых поддерживается работа Дата акселератора. Поддерживаются следующие версии дистрибутивов:
  • Astra Linux Common Edition 2.12.
  • Astra Linux Special Edition 1.6 - 1.8(только ядро generic).
  • CentOS 7.
  • Debian 10 - 12.
  • Mint 20 - 22.
  • Oracle Linux 7 - 9.
  • Red Hat Enteprise Linux 7 - 9.
  • Simply Linux 10.
  • Ubuntu 20.04 LTS.
  • Ubuntu 22.04 LTS.
  • Ubuntu 24.04 LTS.
  • Альт 8 СП.
  • Альт Образование 10.
  • Альт Рабочая станция 10.
  • Альт Рабочая станция К 10.
  • Альт Сервер 10.
  • Альт 10 СП.
  • РЕД ОС 7.3 МУРОМ.
  • РЕД ОС 8.
Для работы Дата акселератора поддерживался следующий набор дистрибутивов ОС Linux:
  • CentOS 6 и выше.
  • Red Hat Enterprise Linux 7 и выше.
  • Fedora 20 и выше.
  • Debian GNU/Linux 8 и выше.
  • Ubuntu 14.04 и выше.
Список поддерживаемых дистрибутивов ОС Linux приведен в актуальный вид.

+

В документации данное изменение описано здесь.
Распределенные информационные базы.
В сообщении обмена данными распределенной информационной базы реализована запись информации об объектах конфигурации, которые изменяют структуру информационной базы без режима совместимости или изменения версии формата конфигурации. Данная информация позволит принимающей стороне определить, может сообщение обмена быть без проблем загружено в информационную базу или нет. Если такой возможности нет - сообщение будет отвергнуто и будет необходимо обновить платформу для загрузки сообщения.

Платформа «1С:Предприятие», которая не поддерживает данное изменение, не сможет загрузить такое сообщение обмена данными. Также сообщение не будет загружено, если платформа не поддерживает объекты конфигурации, информация о которых записана в сообщении обмена.

Данная возможность не предоставлялась. В результате любое сообщение обмена могло быть загружено с помощью любой платформы и при обновлении базы данных могли произойти изменения, приводящие к разрушению информационной базы в принимающем узле распределенной информационной базы.При работе в распределенной информационной базе повышена надежность работы за счет того, что платформа не позволяет загружать сообщения обмена, которые могут разрушить информационную базу.

Оглавление

Переход с предыдущей версии на версию 8.3.24

Оглавление

Версия 8.3.23

Версия 8.3.23 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8323doc) документации к текущей версии.

Автономный сервер вышел из статуса бета-версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.22.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.21. +Возможность запуска конфигураций, разработанных в версии 8.3.22 и более младших, в версии 8.3.23, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.23 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.23, при необходимости, использовать для работы с информационной базой и версию 8.3.22. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Средства разработки.
Для системы «1С:Предприятие» реализована лицензия для разработчиков (см. здесь):
  • Позволяет использовать клиентское приложение и кластер серверов.
  • Является исключительно программной лицензией.
  • Может быть привязана только к параметрам компьютера.
  • Не складывается.
  • Имеет ограничение по времени.
  • Не накладывает ограничение на количественные характеристики конфигурации и базы данных.
  • Для получения лицензии необходима регистрация на портале для разработчиков (см. здесь).

Особенности и ограничения лицензии для разработчиков приведены в документации.

Для объекта ЗапросНаПолучениеЛицензии реализованы свойства ИмяУчетнойЗаписи и ПарольУчетнойЗаписи. Для менеджера получения лицензий реализованы методы ПолучитьДоступностьИспользованияЛицензийРазработчика() и ПолучитьЛицензионноеСоглашениеРазработчика().

Данная возможность не предоставлялась.

Для обучения предлагалось использовать учебную версию.

Для разработки было необходимо приобрести комплект разработчика или любую основную поставку.

Реализована возможность бесплатно использовать полнофункциональную версию системы «1С:Предприятие» для обучения и разработки.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Средства администрирования.
Стандартные функции.
Реализована возможность управления табличными пространствами базы данных при работе в клиент-серверном варианте информационной базы. Реализована возможность управлять табличными пространствами для индексов и данных. Разделение таблиц по пространствам имен индивидуально для каждой информационной базы и не переносится с помощью выгрузки информационной базы. Управление табличными пространствами не поддерживается в файловой информационной базе и в Дата акселераторе.

Реализована стандартная функция Управление табличными пространствами базы данных, которая доступна в клиент-серверной информационной базе, начиная с режима совместимости Версия 8.3.7.

Реализовано свойство глобального контекст ТабличныеПространстваБазыДанных. Реализовано свойство системного перечисления КатегорияОшибки.ОшибкаТабличногоПространстваБазыДанных.

Для команды IBCheckAndRepair командной строки пакетного запуска конфигуратора реализован параметр RefreshTableLocation.

Для таблицы значений, возвращаемой методом ПолучитьСтруктуруХраненияБазыДанных() реализованы колонки ТабличноеПространствоХраненияДанных и ТабличноеПространствоХраненияИндексов.

Реализовано свойство конфигурации Режим использования табличных пространств.

Использование управления табличными пространствами базы данных требует наличие лицензии КОРП.

Данная возможность не предоставлялась.Расширены возможности по администрированию информационной базе в клиент-серверном варианте. Стало возможно распределять таблицы информационной базы по различным дисковым накопителям, в соответствии с профилями нагрузки на эти таблицы.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Встроенный язык.
Работа с JSON.
В глобальном контексте реализованы методы ЗаписатьЗначениеJSON() и ПрочитатьЗначениеJSON(). Методы доступны в любом контексте. Методы выполняют сериализацию и десериализацию определенного набора типов данных в строку JSON и обратно (из строки JSON в объекты встроенного языка).Данная возможность не предоставлялась.

Новые методы можно было реализовать с помощью существующих механизмов работы с JSON. Однако использование такой реализации (в общем случае) требовало-бы вызова сервера.

Упрощена работа с форматом JSON, особенно в веб-клиенте и на мобильных устройствах.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Реализована возможность обмена файлами при интеграции системы взаимодействия с Telegram и ВКонтакте. При обмене с системой ВКонтакте не поддерживается обмен видеофайлами.

Для хранения файлов, которые передаются между системами, на сервере взаимодействия можно настроить собственное хранилище.

Данная возможность не предоставлялась.Расширены возможности интеграции с системами мгновенного обмена сообщениями.
В документации данное изменение описано здесь.
Автономный сервер.
Средства администрирования.
Реализована возможность конвертации клиент-серверной информационной базы в информационную базу, обслуживаемую другой СУБД, минуя процесс выгрузки/загрузки информационной базы в dt-файл. Конвертация из файлового варианта информационной базы не поддерживается.

Для команды infobase утилиты ibcmd реализована команда replicate.

Данная возможность не предоставлялась.

Смена используемой СУБД выполнялась только с помощью выгрузки в dt-файл и последующей загрузки из этого файла в новой СУБД.

Упрощена миграция клиент-серверной информационной базы между различными СУБД.
В документации данное изменение описано здесь и здесь.
Встроенный язык.
Реализована возможность использования регулярных выражений во встроенном языке. Используются регулярные выражения стандарта ICU. Работа с регулярными выражениями доступна только на стороне сервера приложений «1С:Предприятия».

В глобальном контексте реализованы следующие методы: СтрНайтиПоРегулярномуВыражению(), СтрЗаменитьПоРегулярномуВыражению(), СтрПодобнаПоРегулярномуВыражению(),

СтрНайтиВсеПоРегулярномуВыражению().

Данная возможность не предоставлялась.Расширены возможности поиска в строках при использовании встроенного языка.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность интеграции системы взаимодействия с системой мгновенного обмена сообщений WhatsApp.

Реализовано свойство ИнтеграцияСистемыВзаимодействия.ДоступноРедактированиеСообщений.

Для менеджера системы взаимодействия реализованы методы ПолучитьВремяОкончанияДоступностиОтвета(), ПолучитьВремяОкончанияДоступностиОтветаАсинх(), ПолучитьШаблоныСообщения(), ПолучитьШаблоныСообщенияАсинх(). ПолучитьШаблонСообщения(), ПолучитьШаблонСообщенияАсинх(), УстановитьПредставленияШаблонаСообщения(), УстановитьПредставленияШаблонаСообщенияАсинх().

Для объекта СообщениеСистемыВзаимодействия реализованы свойства ШаблонСообщения и ЗначенияПодстановокШаблонаСообщения.

Реализовано событие модуля приложения ОбработкаВыбораШаблонаСообщенияСистемыВзаимодействия.

Данная возможность не предоставлялась.Расширены возможности интеграции системы взаимодействия с системами мгновенного обмена сообщениями.
В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
Стандартная обработка управления системой взаимодействия отображает информацию о параметрах системы взаимодействия, в которой зарегистрирована информационная база и адресе электронной почты абонента.

Для менеджера системы взаимодействия реализованы методы АдресСервера(), ВерсияСервера(), АдресЭлектроннойПочтыАбонента() и ТекущийПользовательЯвляетсяАдминистраторомАбонента().

Данная возможность не предоставлялась.Реализована возможность получить информацию о системе взаимодействия, к которой подключена текущая информационная база.
В документации данное изменение описано здесь.
Расширение конфигурации.
В расширении конфигурации реализована возможность создания собственных регламентных заданий.Данная возможность не предоставлялась.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Работа с СУБД.
При использовании СУБД Microsoft SQL Server в клиент-серверном варианте информационной базы реализована возможность использовать для работы с СУБД Microsoft OLE DB Driver for SQL Server.При использовании СУБД Microsoft SQL Server в клиент-серверном варианте информационной базы не поддерживалось использование Microsoft OLE DB Driver for SQL Server для работы с СУБД. Поддерживался только Microsoft SQL Server Native Client.Расширен список используемых инструментов доступа к СУБД Microsoft SQL Server.
В документации данное изменение описано здесь.
Автономный сервер.
Для автономного сервера реализованы возможности:
  • Прямого подключения к информационной базе (по протоколу TCP, только для управляемого приложения).
  • Использование Конфигуратора.
  • Использования автономного сервера в качестве менеджера тестирования.
  • Выполнять отладку прикладного решения, используя сервер отладки, встроенный в автономный сервер.
Данные возможности не предоставлялись.

Отладка прикладного решения поддерживалась только в том случае, когда сервер отладки был развернут отдельно от автономного сервера.

Расширены возможности автономного сервера.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Автономный сервер.
Реализована возможность включать и отключать функциональные возможности автономного сервера. Для этого в конфигурационном файле реализована секция features. Также могут использоваться команды командной строки утилиты ibsrv:
  • --enable-extended-designer-features, --disable-extended-designer-features - включает/отключает расширенные возможности конфигурирования в автономном сервере.
  • --enable-http-gate, --disable-http-gate - включает/отключает доступ к информационной базе по протоколу HTTP.
  • --enable-ssh-gate, --disable-ssh-gate - включает/выключает SSH-шлюз автономного сервера (работа в режиме агента).
  • --enable-direct-gate, --disable-direct-gate - включает/выключает доступ к информационной базе по протоколу TCP.
Данные возможности не предоставлялись.

Все возможности, предоставляемые автономным сервером. были доступны всегда,

Расширены возможности управления автономным сервером. Стало возможно отключить неиспользуемые возможности автономного сервера.
В документации данное изменение описано здесь и здесь.
Автономный сервер.
Для автономного сервера реализованы:
  • Режим mobile-app export - запись конфигурации мобильного приложения (доступна только после включения расширенных возможностей конфигурирования).
  • Режим mobile-client:
    • export - запись конфигурации мобильного клиента (доступна только после включения расширенных возможностей конфигурирования).
    • sign - выполнить цифровую подпись конфигурации.
  • Режим config - является сокращенной записью команды infobase config.
  • Режим extension - является сокращенной записью команды infobase config extension.
  • infobase config export - выгрузить в XML-файлы внешнюю обработку/отчет или расширение.
  • infobase config import - загрузить из XML-файлов внешнюю обработку/отчет или расширение.
Данные возможности не предоставлялись.Расширены возможности автономного сервера.
Автономный сервер.
Для SSH-шлюза автономного сервера реализованы следующие команды:
  • config mobile-app-write-file - запись конфигурации мобильного приложения.
  • config mobile-client-write-file - запись конфигурации мобильного клиента.
  • config sign-cfg - выполнить цифровую подпись конфигурации.
  • config mobile-client-digi-sign - выполнить цифровую подпись конфигурации мобильного клиента.
Данные возможности не предоставлялись.Расширены возможности автономного сервера.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность встраивать чат системы взаимодействия в сторонний сайт. Реализован программный интерфейс, который позволяет сайту управлять чатом.

Реализован новый вид интеграции - веб-чат системы взаимодействия.

Для модуля бота реализованы события ПриСозданииОбсужденияСистемыВзаимодействия, ПриДобавленииВОбсуждениеСистемыВзаимодействия, ПриУдаленииИзОбсужденияСистемыВзаимодействия.

Реализованы свойства ПараметрыФормированияКомандСистемыВзаимодействия.Пользователь, ПользовательСистемыВзаимодействия.Псевдоним, ИнтеграцияСистемыВзаимодействия.ДоступныВидеоконференции, СтандартнаяКомандаСистемыВзаимодействия.ПоказатьИнформациюОПользователе, ИсточникКомандСистемыВзаимодействия.Пользователь.

Реализован метод ПолучитьАбсолютный() для типов Цвет и Шрифт.

Реализован Collaboration System WebChat API, позволяющий сайту взаимодействовать с веб-чатом.

Данная возможность не предоставлялась.Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь, здесь и здесь.
Технологический журнал.
В технологическом журнале реализован вывод списка операций изменения данных сеанса с их контекстами в свойство Context событий CALL для методов seanceParametersCommit и finishSeance менеджера кластера (rmngr).

Данная возможность управляется элементом <sessiondatacontext> файла настройки технологического журнала logcfg.xml.

Включение данной возможности будет приводить к замедлению работы системы. Включение данной возможности необходимо выполнять только в случае расследования проблем с размером хранилища сеансовых данных кластера серверов.

Данная возможность не предоставлялась.Упрощено расследование проблем размера хранилища сеансовых данных кластера серверов.
В документации данное изменение описано здесь и здесь.
Распознавание речи.
Реализована возможность распознавания речи в платформе «1С:Предприятие». Распознавание речи может работать как в потоковом варианте, так и из файлов формата Ogg. Распознавание речи возможно как в локальном варианте (на компьютере пользователя, без соединения с Интернет), так и с использованием облачного сервиса фирмы «1С».

Реализовано свойство глобального контекста РаботаСРечью.

Реализована стандартная обработка Управление распознаванием речи.

Реализованы события технологического журнала <STTAdm> и <STT>.

Реализовано свойство системного перечисления КатегорияОшибки.ОшибкаРаботыСРечью.

Реализована команда командной строки запуска клиентского приложения /DisableLocalSpeechToText.

Реализован сервисы Сервис распознавания речи и Сервис управления моделями распознавания речи кластера серверов системы «1С:Предприятие».

Для рабочего сервера реализована возможность изменять расположение каталога с моделями распознавания речи с помощью свойства Каталог моделей распознавания речи рабочего сервера консоли кластера.

Для файла conf.cfg реализован параметр SpeechToTextModelLocation.

В интерфейсе клиентского приложения реализовано отображение состояния механизма распознавания речи.

Распознавание речи не поддерживается:

  • В веб-клиенте, который работает под управлением веб-браузеров Mozilla Firefox, Safari или Google Chrome (и веб-браузеры, основанные на движке Chromium) версии младше, чем 66.
  • В веб-клиенте, который доступен по протоколу HTTP и хост публикации не является localhost.
  • В автономном сервере.
  • В учебной версии.
  • При работе под управлением ОС Microsoft Windows XP или Microsoft Windows Server 2003.
  • В локальном варианте, если используется файловый вариант информационной базы:
    • работающей под управлением ОС macOS;
    • работающей на процессоре ARM.
  • В том случае, если информационная база создана в режиме совместимости с версией 8.1.
Данная возможность не предоставлялась.Реализована возможность использовать распознавание речи в прикладных решениях на базе системы «1С:Предприятие». В частности, становится возможным реализовать голосовое управление прикладным решением или ввод текста в поля ввода с использованием голосового набора.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Хранилище двоичных данных.
Реализовано хранилище двоичных данных. Предназначено для хранения двоичных данных на файловой системе компьютера кластера серверов «1С:Предприятия» вместо информационной базы. При этом использование хранилища прозрачно для операций чтения и записи данных: прикладное решение «считает», что выполняются операции чтения и записи данных из реквизитов прикладных объектов.

Хранилище поддерживается только в клиент-серверном варианте. Автономный сервер и файловый вариант информационный базы не поддерживают использование хранилища двоичных данных. Реализован программный интерфейс для администрирования хранилища с помощью встроенного языка.

Реализовано свойство глобального контекста ХранилищеДвоичныхДанных. Реализован сервис кластера серверов системы «1С:Предприятие» Сервис хранилища двоичных данных. Реализована стандартная обработка Управление хранилищем двоичных данных. Для технологического журнала реализовано событие <STORE>.

Реализована возможность выполнять проверку целостности хранения двоичных данных:

  • В диалоге Тестирование и исправление реализован пункт Проверка целостности хранения двоичных данных.
  • Для команды /IBCheckAndRepair командной строки пакетного запуска конфигуратора реализован параметр -BinaryDataStorageIntegrity.

Механизм хранилища двоичных данных требует лицензию КОРП.

Данная возможность включена в статусе бета-версии. Для использования хранилища двоичных данных во время бета-тестирования требуется лицензия на тестирование выделенной функциональности. При отсутствии лицензии на тестирование выделенной функциональности использование хранилища двоичных данных будет невозможно.

Данная возможность не предоставлялась.Реализована возможность для информационной базы, содержащей большое количество хранимых двоичных данных, управлять размером базы данных и производительностью работы с хранимыми с помощью механизма хранилища двоичных данных.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Для клиентского приложения реализовано автоматическое (каждые 20 минут) сохранение измененных пользовательских настроек:
  • положение и размера окна приложения,
  • настройки ширины колонок таблиц,
  • положение разделителей.
Пользовательские настройки сохранялись только во время штатного завершения работы клиентского приложения.Снижена вероятность потери настроек, которые выполнены пользователем за время работы в клиентском приложении.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность переключить текущий видеозвонок на другое устройство или другое запущенное приложение. Если в момент переключения пользователем выполнялась демонстрация экрана - она (демонстрация) будет отключена.Данная возможность не предоставлялась.Расширены возможности видеозвонков системы взаимодействия.
Система взаимодействия.
Мобильный клиент.
При возникновении сетевых проблем, система взаимодействия выполняет попытки восстановить соединение в процессе звонка. Система выполняет попытки восстановления соединения до тех пор, пока не закрыто клиентское приложение и не завершен видеозвонок, во время которого начались проблемы.При возникновении сетевых проблем система взаимодействия не предпринимала никаких попыток для восстановления ситуации.Улучшено качество видеозвонков в ситуации невысокого качества канала связи.
Система взаимодействия.
Реализована адаптация качества изображения видеозвонка к текущему качеству канала связи. Качество изображения может как ухудшаться (в случае ухудшения качества канала), так и улучшаться (в случае улучшения качества канала связи).В системе взаимодействия качество изображения видеозвонка могло только ухудшаться, если ухудшалось качества канала связи. Если качество канала связи улучшалось - качество изображения не восстанавливалось.Качество изображения видеозвонков стало адаптироваться к качеству канала связи (как в сторону ухудшения качества изображения, так и в сторону улучшения качества).

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Расширение конфигурации.
При запуске тонкого и веб-клиента после обновления расширения (или расширений) конфигурации, снижено количество запросов к серверу (и объем передаваемой информации).При запуске тонкого и веб-клиента после обновления расширения (или расширений) конфигурации, к серверу выполнялось большое количество запросов и передавался большой объем информации.Ускорен старт тонкого и веб-клиента, который выполняется после обновления одного или нескольких расширений конфигурации.
Копии базы данных.
Уменьшено время начального заполнения копии базы данных.Начальное заполнение копии базы данных занимало больше времени.Ускорено начальное заполнение копии базы данных.
Кластер серверов.
Снижено время недоступности (или устранено вовсе) клиентского приложения во время перезапуска рабочего процесса, обслуживающего это клиентское приложение.Во время перезапуска рабочего процесса, обслуживающего клиентское приложение, это клиентское приложение могло быть недоступно (зависать) на длительный промежуток времени.Снижено время недоступности (или устранено вовсе) клиентского приложения, которое наблюдается при перезапуске рабочего процесса, обслуживающего клиентское приложение.
Система взаимодействия.
Ускорено соединение между абонентами в том случае, когда соединение выполняется по протоколу «точка-точка».

Улучшено качество шумоподавления в том случае, когда говорят одновременно оба участника видеозвонка.

Повышено качество демонстрации экрана.

В том случае, когда соединение выполняется по протоколу «точка-точка», соединение могло устанавливаться (время от приема звонка до начала разговора) очень продолжительное время.

Качество шумоподавления было недостаточно хорошим, когда говорили одновременно оба участника видеозвонка.

Качество демонстрации экрана было недостаточно хорошим.

Улучшена работа с видеопотоком в системе взаимодействия в тонком и толстом клиентских приложениях.
Дата акселератор.
При выполнении некоторых пользовательских запросов устранен резкий рост потребления оперативной памяти Дата акселератором.При выполнении некоторых пользовательских запросов мог наблюдаться резкий рост потребления оперативной памяти Дата акселератором.В некоторых случаях снижен расход оперативной памяти Дата акселератором.
Дата акселератор.
Повышена скорость выполнения запросов с упорядочиванием к нескольким таблицам.Выполнение запросов с упорядочиванием к нескольким таблицам занимало больше времени.Ускорено выполнение запросов к нескольким таблицам в Дата акселераторе.
Дата акселератор.
В Дата акселераторе снижено использование памяти для хранения текстовых полей и ускорена их обработка.В Дата акселераторе для хранения текстовых полей требовалось больший объем памяти, а их обработка занимала больше времени.При использовании Дата акселератора ускорена работа с текстовыми полями.
Дата акселератор.
Оптимизирована работа Дата акселератора с индексами, настроенными в конфигурации.Дата акселератор не оптимально работал с индексами, настроенными в конфигурации.Уменьшено время выполнения запросов, которые используют таблицы, для которых в конфигурации настроены индексы.
Дата акселератор.
При запуске Дата акселератора под управлением ОС Linux проверяется, что параметра ядра операционной системы transparent hugepage настроен так, как необходимо для работы Дата акселератора. Данный параметр должен быть установлен в значения madvise или never.

Если параметр настроен не корректно, то Дата акселератор не запускается, а в технологический журнал записывается диагностическая информация.

Значение параметра ядра transparent hugepage операционной системы Linux не проверялось при запуске Дата акселератора под управлением этой операционной системы.При использовании Дата акселератора под управлением ОС Linux будет проверяться, что используются настройки операционной системы, необходимые для оптимальной работы продукта.
В документации данное изменение описано здесь.
Дата акселератор.
Оптимизировано выполнение некоторых запросов Дата акселератора.Выполнение некоторых запросов Дата акселератора занимало больше времени.Повышена производительность работы Дата акселератора.
Дата акселератор.
Повышена стабильность работы в условиях ограничений или нехватки оперативной памяти во время выполнения запросов, а также за счет изменения алгоритмов оптимизации запросов (что в ряде случаев может приводить к несущественному замедлению выполняемых запросов.Были возможны случаи нестабильной работы Дата акселератора в условиях ограничений или нехватки оперативной памяти во время выполнения запросов, а также в результате слишком агрессивной оптимизации запросов.Повышена стабильность работы в условиях ограничений или нехватки оперативной памяти во время выполнения запросов, а также за счет изменения алгоритмов оптимизации запросов (что в ряде случаев может приводить к несущественному замедлению выполняемых запросов.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Средства администрирования.
Механизм логирования действий пользователя объявлен устаревшим и не рекомендуется для использования.

Команда /LogUI интерфейса командной строки запуска клиентского приложения объявлена устаревшей и не рекомендуется к использованию.

Клиентское приложение поддерживало механизм логирования действий пользователя.Прекращена поддержка устаревшего механизма.
Средства администрирования.
Выполнение операции тестирования и исправления в клиент-серверном варианте всегда выполняется на стороне сервера.

Ускорено выполнение операции тестирования и исправления информационной базы.

Операция тестирования и исправления в клиент-серверном варианте информационной базы выполнялась на стороне клиента (в Конфигураторе).

Операция тестирования и исправления информационной базы занимала больше времени.

Ускорено выполнение операции тестирования и исправления информационной базы в клиент-серверном варианте.
Расширение конфигурации.
Для конструктора запросов, открытого в расширении конфигурации, реализована поддержка работы с объектами конфигурации, которые не захвачены в расширение. Если в запросе используются объекты, которые не добавлены в расширение, то после закрытия конструктора, предлагается добавить в расширение все недостающие объекты расширяемой конфигурации.

В диалоге конструктора запросов реализована возможность управлять отображением таблиц и полей расширяемой конфигурации.

Данная возможность не предоставлялась.

Конструктор запросов, открытый из расширения конфигурации, позволял использовать только таблицы и поля объектов расширения (собственных и заимствованных).

Расширены возможности работы с расширением конфигурации.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Реализована возможность управлять сохранением настроек окна клиентского приложения. Для этого реализовано свойство формы клиентского приложения Сохранять настройки окна, доступная в редакторе формы.

Реализована команда Восстановить размеры, для вызова которой предназначено сочетание клавиш Alt+Shift+R. Данная команда восстанавливает не только положение и размер окна, но и устанавливает в значения по умолчанию положения разделителей и размеры колонок всех таблиц формы.

Команда Восстановить положение окна более не доступна к использованию. Поведение команды Восстановить размеры зависит от того, как открыта форма.

Данная возможность не предоставлялась. Настройки формы сохранялись всегда, даже если это не требовалось разработчику формы.Реализована возможность управления необходимостью сохранения настроек формы.

Команда восстановления положения и размера окна также восстанавливает положение разделителей и размер колонок таблиц формы.

В документации данное изменение описано здесь.
Работа с криптографией.
При работе под управлением ОС Windows снято ограничено на размер расшифровываемого файла в 100 Мбайт.При работе под управлением ОС Windows размер расшифровываемого файла был ограничен размером 100 Мбайт.Снято ограничение на размер расшифровываемого файла при работе под управлением ОС Windows.
Клиентское приложение.
В клиентских приложениях и конфигураторе, работающих под управлением ОС macOS, при отображении сочетаний клавиш, вместо клавиш Alt и Ctrl упоминаются клавиши Option и Cmd.В клиентских приложениях и конфигураторе, работающих под управлением ОС macOS, при отображении сочетаний клавиш не учитывалась специфика клавиатуры компьютеров фирмы Apple.Отображение сочетаний клавиш приведено к стандарту, используемому в ОС macOS.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства разработки.
Клиентское приложение.
Для конфигуратора, работающего под управлением ОС macOS, реализованы следующие сочетания клавиш:
  • Cmd+M - вызов контекстной подсказки.
  • Cmd+Shift+M - контекстная подсказка по параметрам методов.
  • Option+F11 - шагнуть в метод в отладчике.
  • Shift+F12 - перейти к определению метода.
  • Cmd+Option+Shift+F5 - запуск прикладного решения без режима отладки.

Для любого клиентского приложения, работающего под управлением ОС macOS, реализованы следующие сочетания клавиш:

  • Cmd+J - выбор из списка шаблонов текста.
  • Cmd+Q - завершение работы приложения.

Все добавленные сочетания реализованы дополнительно к уже существующим сочетаниям клавиш для указанных функций.

Указанные сочетания клавиш были недоступны в клиентских приложениях и конфигураторе, работающих под управлением ОС macOS.Упорядочен использование сочетаний клавиш при работе под управлением ОС macOS.
Кластер серверов.
Система мониторинга кластера серверов считает успешное получение данных в процессе серверного вызова как доказательство работоспособности рабочего процесса.Система мониторинга кластера серверов использовала как доказательство работоспособности рабочего процесса только специальные вызовы самой системы мониторинга кластера, что в некоторых случаях большой нагрузки на кластер северов могло приводить к ошибочным перезапускам рабочих процессов..Снижена вероятность необоснованных перезапусков рабочих процессов системой мониторинга кластера серверов.
Клиентское приложение.
Если во время подключения клиентского приложения к кластеру серверов или во время серверного вызова на сервере произошла ошибка вызова сервиса кластера, то пользователю будет отображен диалог, который проинформирует об ошибке и позволит повторить (в том числе автоматически) подключение или серверный вызов.Если во время подключения клиентского приложения к кластеру серверов или во время серверного вызова на сервере произошла ошибка вызова сервиса кластера, то пользователю предлагалось завершить работу клиентского приложения или перезапустить его.Снижено количество ситуаций, когда выполняется перезапуск (или завершение работы) клиентского приложения.
Хранение настроек.
Для стандартного хранилища настроек устранены ограничения на длину имени пользователя и ключа настроек. Ограничения на длину ключа объекта не изменялись (строка с именем ключа объекта ограничена длиной в 256 символов).

Выборка, полученная с помощью метода Выбрать() менеджера стандартного хранилища настроек, будет упорядочена по:

  • Значению хеш-функции от имени пользователя (по возрастанию).
  • Ключу объекта (в алфавитно-цифровом порядке, по возрастанию).
  • Значению хеш-функции от ключа настроек (по возрастанию).
  • Полю Версия (по возрастанию).

В режиме совместимости с версией 8.3.22 поведение не изменилось.

Для стандартного хранилища настроек были установлены следующие ограничения на длину свойств:
  • Имя пользователя - не более 64 символов.
  • Ключ настроек - не более 128 символов.

Выборка, полученная с помощью метода Выбрать() менеджера стандартного хранилища настроек, была упорядочена по возрастанию по следующим полям:

  • Имя пользователя.
  • Ключ объекта.
  • Ключа настроек.
Расширены возможности работы со стандартным хранилищем настроек.
В документации данное изменение описано здесь, здесь и здесь.
Полнотекстовый поиск.
Если в строку глобального поиска вводится поисковый запрос длиной 3 или менее символов, то этот запрос отправляется в полнотекстовый поиск «как есть».

Удалено ограничение по количеству возвращаемых результатов полнотекстового поиска.

Если в строку глобального поиска вводится поисковый запрос длиной 3 или менее символов, то этот запрос отправлялся в полнотекстовый поиск с добавлением символа «*» после введенных символов.

Если полнотекстовый поиск возвращал более 1 млн. результатов - формировалась ошибка без отображения результатов поиска.

Стало возможно получить результат полнотекстового поиска в тех случаях, когда ранее это было невозможно (формировалась ошибка).
Расширение конфигурации.
Средства разработки.
В конфигураторе, при выполнении синтаксического контроля модуля расширения, в методах, которые аннотируются как ИзменениеИКонтроль, игнорируются ошибки Переменная не определена во всех областях метода, кроме области #Вставка ... #КонецВставки.В конфигураторе, при выполнении синтаксического контроля модуля расширения, в методах, которые аннотируются как ИзменениеИКонтроль, ошибки Переменная не определена возникали в том случае, когда в методе использовался реквизит, который не добавлен в расширение. Однако, фактического добавления реквизита не требовалось.В случае точечного изменения методов конфигурации (с помощью аннотации ИзменениИКонтроль) в расширение стало необходимо заимствовать меньшее количество объектов расширяемой конфигурации.
В документации данное изменение описано здесь.
Табличный документ.
Если для ячейки табличного документа вертикальное положение текста задано как Центр или Низ, а текст не полностью помещается в ячейку по вертикали, то текст будет выводиться таким образом, как если-бы в ячейке вертикальное положение текста было указано как Верх. В этом случае текст отображается начиная с верхней границы ячейки. Если текст не помещается в ячейку - будет обрезано окончание выводимого текста.

Если табличный документ экспортируется в какой-либо формат, отличный от формата MXL (HTML, Microsoft OpenXML, OpenOffice и т.д.), то выравнивание останется прежним и экспортированный документ может отличаться от оригинала.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

Если для ячейки табличного документа вертикальное положение текста задано как Центр или Низ, а текст не полностью помещается в ячейку по вертикали, то размещение по вертикали и обрезание текста (для того, чтобы текст поместился в ячейку) выполнялось следующим образом:
  • Для выравнивания Центр - текст центрировался по вертикали, а обрезание выполнялось и с начала и с конца текста.
  • Для выравнивания Низ - текст прижимается к нижнему краю ячейки, а обрезание выводимого текста выполнялось с начала текста.
Устранено некорректное поведение системы. Если текст не помещается в ячейку, то при любом вертикальном положении текста будет видно, в первую очередь, начало текста в ячейке.
В документации данное изменение описано здесь.
Мобильный клиент.
Веб-клиент.
Для полей формы клиентского приложения реализована возможность указывать содержимое полей, которое будет учитываться механизмом автозаполнения операционной системы. Возможность реализована в мобильном клиенте и веб-клиенте. В веб-клиенте для автозаполнения доступны только поля ввода текущей открытой формы. Содержимое полей других открытых форм остается неизменным.

Реализовано свойство ПодсказкаАвтозаполнения расширения поля формы для поля ввода.

Данная возможность не предоставлялась.Упрощено автозаполнение полей, которые имеют общепринятый смысл.
В документации данное изменение описано здесь.
Система компоновки данных.
Динамический список.
При восстановлении настроек метод КомпоновщикНастроекКомпоновкиДанных.Восстановить() будет очищать (или отключать) отборы, расположенные в пользовательских настройках и использующие поля (в левой части отбора), которых нет в доступных полях.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

При восстановлении настроек метод КомпоновщикНастроекКомпоновкиДанных.Восстановить() не проверял поля, используемые в левой части отбора, на нахождение в списке доступных полей.У отчетов и динамических списков будут отключены или удалены пользовательские отборы по полям, которые недоступны в отчете или динамическом списке. Изменение затронет, в том числе, отборы по полям, которые отключены с помощью функциональных опций.
В документации данное изменение описано здесь.
Система компоновки данных.
Оптимизировано отображение списка доступных полей системы компоновки данных в поле таблицы формы.Отображение списка доступных полей системы компоновки данных в поле таблицы формы было не оптимальным.Навигация по списку доступных полей системы компоновки данных должна выполняться без задержек (особенно в тех случаях, когда список доступных полей включает тысячи элементов).
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.16.Версия формата выгрузки конфигурации в XML-файлы была равна 2.15.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.
Система компоновки данных.
При применении отбора к полям, содержащим множественные характеристики, система компоновки данных выполняет фильтрацию поля, содержащего множественную характеристику, но не выполняет фильтрацию значений самой множественной характеристики.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

При применении отбора к полям, содержащим множественные характеристики, система компоновки данных выполняла фильтрацию поля, содержащего множественную характеристику, а также выполняла фильтрацию значений самой множественной характеристики.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Средства администрирования.
Реализована возможность настроить предварительную загрузку (и установку) дистрибутива клиентского приложения на компьютеры пользователя. Такая загрузка будет выполняться до фактического обновления приложения на сервере.

Реализован конфигурационный файл ClientUpdate.cfg.

Данная возможность не предоставлялась.

Запланировать обновление клиентского приложения было невозможно.

В результате предварительной загрузки и установки новой версии клиентского приложения, после обновления системы «1С:Предприятие» на сервере, пользователю перед началом работы не придется ожидать, пока будет выполнено скачивание и установка клиентского приложения.
В документации данное изменение описано здесь, здесь и здесь.
Форма клиентского приложения.
Для поля ввода, отображающего реквизит формы типа СписокЗначений или ДанныеФормыКоллекция, изменено отображение коллекции. Каждый элемент коллекции отображается своим элементом в поле ввода, который имеет свое представление, картинку, и кнопку удаления. Если поле ввода отображает коллекцию с единственным типом - реализована возможность добавлять значения в коллекцию непосредственно из поля ввода, включая множественный выбор. Кнопка выбора более не выполняет никаких действий. Кнопка просмотра активирует форму изменения коллекции.

Аналогичным образом изменено отображение списка значений в ячейке таблицы формы клиентского приложения.

Для поля ввода формы клиентского приложения реализованы свойства: ЦветФонаМножественныхЗначений, ЦветТекстаМножественныхЗначений, ШрифтМножественныхЗначений, ПутьКДаннымЗначенияМножественногоЗначения, ПутьКДаннымПредставленияМножественногоЗначения, ПутьКДаннымКартинкиМножественногоЗначения, КартинкаМножественныхЗначений, РазрешитьВводПустыхМножественныхЗначений, РазрешитьДублированиеМножественныхЗначений, ОтображатьФлажкиВВыпадающемСпискеПриВводеМножественныхЗначений, ГиперссылкаМножественныхЗначений, ФигураКартинкиМножественногоЗначения, РазмерКартинкиМножественногоЗначения.

Для расширения поля ввода для формы клиентского приложения реализованы методы: ПолучитьВыделенныеМножественныеЗначения(), УстановитьВыделенныеМножественныеЗначения().

Для поля ввода формы клиентского приложения реализованы события: ОбработкаФормированияКоманд, ДобавлениеМножественныхЗначений, УдалениеМножественныхЗначений, ОткрытиеМножественногоЗначения, ОбработкаНавигационнойСсылкиМножественногоЗначения.

Реализованы системные перечисления ФигураКартинкиМножественногоЗначенияПоляВвода, РазмерКартинкиМножественногоЗначенияПоляВвода.

Изменение отображение реализовано в интерфейсах Такси и Версия 8.2.

Поле ввода отображало реквизит формы типа СписокЗначений или ДанныеФормыКоллекция в виде списка представлений значений, разделенных символом «;». Для изменения списка было необходимо открывать отдельную форму.Улучшается отображение значений типа СписокЗначений и ДанныеФормыКоллекция. Это позволит создавать более компактные и удобные для пользователя интерфейсы.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Диаграммы.
Изменен внешний вид диаграммы Ганта в тонком и веб-клиентах. Для точек, значений и интервалов диаграммы реализована возможность вывода текста в несколько строк. Реализована возможность выводить текст на интервалах диаграммы.

Реализована возможность выделения значений диаграммы с помощью клавиатуры и мыши. Реализована возможность выделения интервалов диаграммы с помощью мыши. Реализовано отображение временных границ интервала во всплывающей подсказке. При перетаскивании интервала во всплывающей подсказе отображаются временные границы интервала.

Для объекта ДиаграммаГанта реализовано свойство ОтображениеТекстаИнтервала и метод НайтиИнтервалПоИдентификатору().

Для объекта ОбластьПостроенияДиаграммыГанта реализовано свойство РазмещениеТекста.

Для объекта ИнтервалДиаграммыГанта реализованы свойства ЦветТекста, Идентификатор.

Для расширения поля формы для диаграммы Ганта реализованы свойства ТекущееЗначение, ВыделенныеЗначения, РежимВыделенияЗначений, ТекущийИнтервал, ВыделенныеИнтервалы, РежимВыделенияИнтервалов, ВертикальныеЛинии, ГоризонтальныеЛинии.

Для расширения поля формы для диаграммы Ганта реализованы события ПриАктивизацииЗначения, ПриАктивизацииИнтервала, ПередРазворачиванием, ПередСворачиванием.

Диаграмма Ганта имела другой внешний вид. У диаграммы отсутствовали возможности выделения значений и интервалов.Диаграмма Ганта стала лучше соответствовать интерфейсу системы. Расширены возможности взаимодействия пользователя и диаграммы.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Для пространства имен XDTO http://v8.1c.ru/8.1/data/enterprise реализованы следующие типы:
  • AnyDBRef - базовый тип ссылок на объекты базы данных (любые ссылочные типы, кроме перечислений).
  • AnyMDEnum - базовый тип ссылок на перечисления конфигурации (любые значения перечислений, созданных в конфигурации).
  • AnyIBRef - тип, соответствующий типу ЛюбаяСсылка.

При формировании собственного пакета XDTO рекомендуется использовать один из реализованных типов (в зависимости от типа сохраняемого значения). При использовании глобальной фабрики XDTO новые типы будут использованы автоматически.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

В пространстве имен XDTO http://v8.1c.ru/8.1/data/enterprise существовал только тип AnyRef, который не позволял корректно отобразить значение типа ЛюбаяСсылка. При использовании глобальной фабрики XDTO для реквизита типа ЛюбаяСсылка применялся тип AnyRef.Устранено некорректное поведение системы.

С применением типа AnyIBRef стало возможно корректно сохранять и восстанавливать значение реквизита типа ЛюбаяСсылка.

Форма клиентского приложения.
На стороне сервера реализована поддержка следующих свойств элементов формы клиентского приложения:
  • Расширение поля формы для поля ввода: АвтоОтображениеКнопкиОчистки, АвтоОтображениеКнопкиОткрытия, АвтоИсправлениеПриВводеТекста, ПроверкаПравописанияПриВводеТекста, АвтоИзменениеРегистраПриВводеТекста, СпециальныйРежимВводаТекста, ТекстКнопкиВводаЭкраннойКлавиатуры, ВариантУправленияВысотой.
  • Расширение таблицы формы для поля ввода: ЗапросОбновления.

Обращение к свойству ИспользуемаяТаблица вызывает исключение для следующих элементов формы клиентского приложения: расширение группы формы для обычной группы, расширение группы формы для страниц, команда формы.

В режиме совместимости с версией 8.3.22 поведение не изменилось. +

При обращении на стороне сервера к следующим свойств элементов формы клиентского приложения не происходило никаких действий и не возникало ошибки:
  • Расширение поля формы для поля ввода: АвтоОтображениеКнопкиОчистки, АвтоОтображениеКнопкиОткрытия, АвтоИсправлениеПриВводеТекста, ПроверкаПравописанияПриВводеТекста, АвтоИзменениеРегистраПриВводеТекста, СпециальныйРежимВводаТекста, ТекстКнопкиВводаЭкраннойКлавиатуры, ВариантУправленияВысотой.
  • Расширение таблицы формы для поля ввода: ЗапросОбновления.
  • Расширение группы формы для обычной группы: ИспользуемаяТаблица.
  • Расширение группы формы для страниц: ИспользуемаяТаблица
  • Команда формы: ИспользуемаяТаблица.
Устранено некорректное поведение системы.
Система компоновки данных.
При программном или интерактивном редактировании структуры настроек системы компоновки данных реализовано ограничение в 30 уровней вложенности.

При интерактивной или программной загрузке отчета, варианта отчета, схемы компоновки данных из файла, будут загружены только те настройки, которые размещены не глубже 60 уровней вложенности. Остальные настройки будут проигнорированы.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

При работе (программной, интерактивной или загрузкой из файлов) со структурой настроек системы компоновки данных отсутствовали ограничения по вложенности элементов настроек, что в ряде случаев могло приводить к аварийному завершению клиентского приложения.Снижено количество случаев неконтролируемого увеличения размера настроек системы компоновки данных в результате редактирования этих настроек (например, в результате перетаскивания фрагмента настроек).

Разработчики и пользователи не смогут интерактивно и программно настроить вариант отчета, в котором будет превышено ограничение на глубину вложенности в 30 элементов для структуры настроек, элементов отбора или полей группировки.

При открытии отчетов, а также при загрузке вариантов отчетов и настроек компоновки данных, будут утеряны элементы настроек, которые расположены глубже, чем 60 уровней вложенности. При этом пользователю будет выдана соответствующая диагностика.

Форма клиентского приложения.
Если у формы клиентского приложения (в тонком, толстом или веб-клиенте) свойство Доступность установлено в значение Ложь, то на форме становятся недоступными кнопки, которые связаны с командами этой формы.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

Если у формы клиентского приложения (в тонком, толстом или веб-клиенте) свойство Доступность установлено в значение Ложь, то на кнопки формы, которые связаны с командами этой формы, оставались доступными.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

Устранено незапланированное поведение системы.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Имена свойств и объектов, связанных с полем планировщика. Старые наименования поддерживаются для совместимости.
  • ПараметрыФормированияКомандПланировщика.
  • ОписаниеКомандПланировщика.
  • ИсточникКомандПланировщика.
  • СтандартнаяКомандаПланировщика.
  • ПараметрыФормированияКомандПоляПланировщика.
  • ОписаниеКомандПоляПланировщика.
  • ИсточникКомандПоляПланировщика.
  • СтандартнаяКомандаПоляПланировщика.
Английское написание методов менеджера обработки ошибок. Старые наименования методов поддерживаются для совместимости.
  • GetCategoryForUser().
  • GetMessageForUser().
  • GetDescriptonForUser().
  • GetBriefDescription().
  • GetDetailDescription().

+

  • ErrorCategoryForUser().
  • ErrorMessageForUser().
  • ErrorDescriptionForUser().
  • BriefErrorDescription().
  • DetailErrorDescription().

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
При работе на мобильных устройствах, свойство СистемнаяИнформация.ТипПлатформы, содержит актуальное значение. Для системного перечисления ТипПлатформы реализованы значения, описывающие поддерживаемые мобильные операционные системы.

В режиме совместимости с версией 8.3.22 поведение не изменилось.

При работе на мобильных устройствах, свойство СистемнаяИнформация.ТипПлатформы содержало значение Неопределено.Упрощено определение типа (и разрядности) используемой мобильной версии системы «1С:Предприятие».
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Для мобильной версии системы «1С:Предприятие» реализована поддержка работы с NFC-метками. Данная возможность поддерживается при работе под управлением ОС Android версии 4.4 и последующих и iOS версии 13.0 и последующих. Поддерживается возможность чтения и записи данных в формате NDEF, перевод метки в состояние «только для чтения» и возможность запуска приложения при контакте мобильного устройства с NFC-меткой. Запуск приложения выполняется через механизм глубинного связывания.

Реализовано свойство глобального контекста СредстваNFC. Реализованы объекты ТекстоваяЗаписьNDEF, URIЗаписьNDEF, МедиаЗаписьNDEF, ЗаписьNDEFВнешнегоТипа, ПустаяЗаписьNDEF, НеизвестнаяЗаписьNDEF, СообщениеNDEF, МеткаNDEF. +

Данная возможность не предоставлялась.На мобильном устройстве стало возможно работать с NFC-метками (не включая возможности оплаты).
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Реализована возможность масштабирования картинки пользователем в окне предварительного просмотра, которое показывается при выполнении метода СредстваМультимедиа.СделатьФотоснимок().

Возможность реализована при работе под управлением ОС Android. Масштабирование выполняется стандартным способом.

Данная возможность не предоставлялась.Пользователь может посмотреть сделанную фотография более детально и повторить снимок, если это необходимо.
Мобильная платформа.
Мобильный клиент.
Для мобильной версии, работающей под управлением ОС Android, реализована возможность передавать данные запускаемому стороннему приложению и получать результат работы стороннего приложения. Реализована возможность настраивать поиск приложения, которое будет запущено с помощью объекта ЗапускПриложенияМобильногоУстройства.

Для объекта ЗапускПриложенияМобильногоУстройства реализованы следующие свойства: ПрикрепляемыеДанные, Категории.

Для объекта ЗапускПриложенияМобильногоУстройства реализованы следующие методы: ЗапуститьАсинх(), ЗапуститьБезОжидания(), УстановитьПараметрыВыбораПриложения().

Свойство ЗапускПриложенияМобильногоУстройства.Категория объявлено устаревшим и не рекомендуется для использования.

Метод ЗапускПриложенияМобильногоУстройства.Запустить() объявлено устаревшим и не рекомендуется для использования.

Для мобильной версии, работающей под управлением ОС Android, возможности по передаче данных запускаемому стороннему приложению были более ограниченные. Отсутствовала возможность получать результат работы стороннего приложения.Расширены возможности работы с внешними (по отношению к разрабатываемому мобильному приложению) мобильными приложениями при работе под управлением ОС Android.
В документации данное изменение описано здесь.
Мобильный клиент.
Для мобильного клиента с автономным режимом реализована возможность автоматического запуска обмена с основной информационной базой. Обмен запускается один раз в 15 минут (интервал не настраивается).

Для обработчика события ПослеОбменаДаннымиСОсновнымСервером реализован параметр ДатаОбмена.

Данная возможность не предоставлялась.Улучшена синхронизация данных между мобильным устройством и основной информационной базой.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
Система взаимодействия.
Реализована возможность переключать видеозвонок на мобильное устройство и с мобильного устройства.Данная возможность не предоставлялась.Стало возможно снова подключиться к видеозвонку в тех случаях, когда невозможно продолжать разговор на устройстве, с которого пользователь начал видеозвонок.
Мобильная платформа.
Мобильный клиент.
Переработана форма выбора даты и времени при работе на мобильном устройстве.Форма выбора даты и времени была другая.Выбирать дату и время на мобильном устройстве стало удобнее.
Мобильная платформа.
Мобильный клиент.
Мобильная версия системы «1С:Предприятие» перестала работать в ОС iOS 8.0.

Минимальная поддерживаемая версия iOS - версия 9.0.

Мобильная версия системы «1С:Предприятие» поддерживала использование ОС iOS 8.0.Прекращена поддержка устаревшей версии ОС iOS.
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
В мобильной версии системы «1С:Предприятие» реализована возможность сканирования документов (с нормализацией результата) с помощью встроенной камеры мобильного устройства. Реализована возможность автоматического и ручного сканирования, сканирования одной или нескольких страниц и изменения порядка следования страниц в сканируемом документе.

Для объекта СредстваМультимедиа реализованы методы:

  • ПоддерживаетсяСканированиеДокументов();
  • ПоказатьСканированиеДокументов();
  • СканироватьДокументыАсинх();
  • ЗакрытьСканированиеДокументов().

Реализована функциональность мобильного приложения СканированиеДокументов.

Возможность сканирования документов не поддерживается при работе под управлением ОС Windows.

Данная возможность не предоставлялась.

Документы можно было сканировать только как фотографии, без нормализации расположения и качества изображения.

Реализована возможность сканирования документов с помощью камеры мобильного устройства таким образом, что результат сканирования сопоставим с результатом сканирования стационарным сканером.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Расширены возможности отбора при работе с контактами и календарями.

Для отборов, которые используются в методах МенеджерКонтактов.НайтиКонтакты() и МенеджерКалендарей.НайтиКалендари() реализована возможность указания полей отбора УчетнаяЗапись, ИдентификаторУчетнойЗаписи и ИсточникУчетнойЗаписи.

При использовании методов МенеджерКонтактов.НайтиКонтакты(), МенеджерКалендарей.НайтиКалендари() и МенеджерКалендарей.НайтиСобытия() корневые значения переданного отбора складываются при выполнении поиска «по И».

Для повышения скорости работы с контактами и календарями всегда использовать отбор по используемой в приложении учетной записи.

При работе с контактами и календарями отсутствовала возможность отбора по учетной записи (или ее параметрам).Расширены возможности отбора при работе с контактами и календарями.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
В мобильной версии системы «1С:Предприятие», работающее под управлением ОС Android, начиная с версии 9 и ОС iOS, начиная с версии 11, реализована возможность загрузки картинок в формате HEIC. После загрузки картинки преобразуются в формат JPEG и хранятся именно в этом формате.Данная возможность не предоставлялась.Расширен список форматов картинок, которые могут быть загружены мобильными приложениями на платформе «1С:Предприятие».

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Форма клиентского приложения.
Для поля формы, отображающего реквизит формы типа СписокЗначений или ДанныеФормыКоллекция, реализовано свойство РасширенноеРедактированиеМножественныхЗначений. Если свойство установлено в значение Ложь, то поле ввода работает аналогично тому, как оно работало в предыдущих версиях, за исключением отображения содержимого коллекции.

Для поля ввода, отображающего множественные значения, реализована поддержка свойств ОграничениеТипа, ПараметрыВыбора, СвязиПараметровВыбора, СвязьПоТипу.

Для формы выбора реализован параметр ВыборДобавлением. Для метода ОповеститьОВыборе() реализован параметр ВыборДобавлением. Для обработчиков событий НачалоВыбора и ОбработкаВыбора расширения поля формы для поля ввода реализован параметр ВыборДобавлением. Эти параметры позволят однозначно определить, в каком режиме находится поле формы, из которого инициировано добавление значений.

Если для поля ввода, отображающего множественные значения, разрешен выбор с использованием флажков, а в данных поля расположено несколько значений, то открытие списка выбора приведет к тому, что в этом списке будут все выбранные значения с включенными флажками.

Данная возможность не предоставлялась.

Было невозможно изменить только представление множественных значений в поле ввода, не включая режим редактирования множественных значений.

В событиях и методах работы с подбором значений в поле ввода было невозможно определить, в каком режиме работы с множественными значениями работает поле.

При работе с множественными значениями в поле ввода стало возможно четко определять режим работы поля. Также стало возможно реализовать прежнее поведение там, где новое поведение не требуется.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Пользователю стало быстрее и проще добиться ситуации, когда документ в видоискателе мобильного устройства имеет оптимальное качество для сканирования (зеленая рамка вокруг документа).

Изменен алгоритм вычисления качества сканируемого документа для получения более равномерного распределения вычисляемого значения.

Пользователь будет получать предупреждение, если он пытается повторного сканировать уже отсканированную страницу.

Пользователю требовалось приложить больше усилий для того, чтобы система положительно оценила качество сканируемого документа.

Алгоритм вычисления качества сканируемого документа возвращал значения, которые были неравномерно распределены внутри допустимого диапазона значений.

Пользователь не получал предупреждения, если он пытался выполнить повторное сканирование уже отсканированной страницы.

Улучшен механизм сканирования документов в мобильной версии системы «1С:Предприятие».
Средства администрирования.
Метод ПолучитьСтруктуруХраненияБазыДанных() возвращает описание служебных таблиц, связанных с механизмом распознавания речи.Таблицы, связанные с механизмом распознавания речи, не возвращались методом ПолучитьСтруктуруХраненияБазыДанных().Устранено некорректное поведение системы.
Средства администрирования.
Метод ПолучитьСтруктуруХраненияБазыДанных() возвращает описание служебных таблиц, связанных с системой взаимодействия.Таблицы, связанные с системой взаимодействия, не возвращались методом ПолучитьСтруктуруХраненияБазыДанных().Устранено некорректное поведение системы.
Средства администрирования.
Метод ПолучитьСтруктуруХраненияБазыДанных() возвращает описание служебных таблиц, связанных с механизмом управления табличными пространствами базы данных.Таблицы, связанные с механизмом управления табличными пространствами базы данных, не возвращались методом ПолучитьСтруктуруХраненияБазыДанных().Устранено некорректное поведение системы.
Средства администрирования.
Метод ПолучитьСтруктуруХраненияБазыДанных() возвращает описание служебных таблиц, связанных с ботами системы взаимодействия.Таблицы, связанные с ботами системы взаимодействия, не возвращались методом ПолучитьСтруктуруХраненияБазыДанных().Устранено некорректное поведение системы.
Средства администрирования.
Метод ПолучитьСтруктуруХраненияБазыДанных() возвращает описание служебных таблиц, связанных с хранением различных настроек.Таблицы, связанные с хранением различных настроек, не возвращались методом ПолучитьСтруктуруХраненияБазыДанных().Устранено некорректное поведение системы.
Мобильный клиент.
При выполнении автоматической синхронизации данных мобильным клиентом с автономным режимом реализованы следующие возможности:
  • Блокируется переход устройства в спящий режим во время формирования и начальной загрузки данных автономного режима, а также во время первого обмена данными после запуска конфигурации.
  • Изменен способ индикации о процессе обмена (окно состояния в нижней части экрана с возможностью нажатия).
Мобильное устройство могло переходить в спящий режим во время начального заполнения информационной базы данными, что приводило к ситуациям, когда приложение работает, а данные в нем неполные или неконсистентные или отсутствуют.

Отображение информации о процессе обмена было менее наглядным.

Улучшен процесс автоматической синхронизации данных для мобильного клиента, работающего в автономном режиме.
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.23 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.23 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 11.19.1,
  • Postgres Pro Standard 11.19.1,
  • Postgres Pro Enterprise 11.19.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.17.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 11.19.1,
  • Postgres Pro Standard 11.19.1,
  • Postgres Pro Enterprise 11.19.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 12.14.1,
  • Postgres Pro Standard 12.14.1,
  • Postgres Pro Enterprise 12.14.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 12.14.1,
  • Postgres Pro Standard 12.14.1,
  • Postgres Pro Enterprise 12.14.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 13.10.1,
  • Postgres Pro Standard 13.10.1,
  • Postgres Pro Enterprise 13.10.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 13.10.1,
  • Postgres Pro Standard 13.10.1,
  • Postgres Pro Enterprise 13.10.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 14.7.1,
  • Postgres Pro Standard 14.7.1,
  • Postgres Pro Enterprise 14.7.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 14.7.1,
  • Postgres Pro Standard 14.7.1,
  • Postgres Pro Enterprise 14.7.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 15.2.1,
  • Postgres Pro Standard 15.2.1,
  • Postgres Pro Enterprise 15.2.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 15.2.1,
  • Postgres Pro Standard 15.2.1,
  • Postgres Pro Enterprise 15.2.1.
Расширен список поддерживаемых СУБД.
Система лицензирования.
Средства администрирования.
Проверка легальности использования прикладного решения на уровне «1С:Предприятия» реализована в клиент-серверном варианте информационной базы. Для прохождения проверки требуется выполнить настройку клиента лицензирования.

Описание настроек клиента лицензирования приведено в документации.

Для разделенной информационной базы настройки клиента лицензирования необходимо выполнить один раз. Не требуется выполнять данную настройку для каждой области данных.

Проверка легальности использования прикладного решения на уровне «1С:Предприятия» выполнялась только в файловом варианте и при использования сервера МИНИ.Проверка легальности использования прикладного решения стала выполняться во всех вариантах информационных баз.
В документации данное изменение описано здесь.
Средства администрирования.
При обновлении конфигурации информационной базы с помощью командной строки, реализована возможность завершать существующие сеансы работы с информационной базой, аналогично интерактивному поведению Конфигуратора. Перечень ситуаций, когда возможно завершение сеансов, не изменялся и описан в документации.

Реализованы следующие команды и параметры:

  • Для команды /UpdateDBCfg пакетного запуска Конфигуратора реализован параметр -SessionTerminate.
  • Для Конфигуратора, работающего в режиме Агента, а также для SSH-шлюза автономного сервера, реализован параметр --session-teminate команды config update-db-cfg.
  • Для команды infobase config apply утилиты администрирования автономного сервера (ibcmd) изменен список допустимых значений параметра --session-terminate, а также значение по умолчанию для данного параметра (значение disable).
  • В случае обновления конфигурации базы данных после обновления расширения допустимо использование параметра --session-terminate в команде infobase config apply.
Обновление конфигурации информационной базы с помощью командной строки (Конфигуратора, агента или SSH-шлюза автономного сервера) не позволяло завершать текущие сеансы с информационной базой, по аналогии с интерактивной работой в Конфигураторе.Унифицировано поведение различных вариантов обновления конфигурации информационной базы.
В документации данное изменение описано здесь, здесь и здесь.
Документация.
В справочной системе Конфигуратора и клиентского приложения отдельно описываются сочетания клавиш для компьютеров Mac в тех разделах, где приводится описание сочетаний клавиш.В справочной системе Конфигуратора и клиентского приложения отдельно не описывались сочетания клавиш для компьютеров Mac.Справочная система стала более информативной.
Средства администрирования.
Для утилиты административной консоли реализован режим, позволяющий выполнять тестирование и исправление только таблиц истории данных информационной базы. Для утилиты 1cv8a реализована команда командной строки запуска --data-history-integrity.Данная возможность не предоставлялась.Расширены возможности утилиты административной консоли.
В документации данное изменение описано здесь.
Средства разработки.
Уменьшено время запуска тонкого клиента из конфигуратора в клиент-серверном варианте информационной базы.Запуска тонкого клиента из конфигуратора в клиент-серверном варианте информационной базы занимал много времени.Ускорен запуск тонкого клиента из конфигуратора в клиент-серверном варианте информационной базы.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 11.20.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.17.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 12.15.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 13.11.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise (версия 13.11.2).
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 14.8.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 15.3.1 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Сборщик мобильных приложений.
В процесс сборки мобильного приложения, работающего под управлением ОС iOS, внесены изменения, которые позволяют выполнять публикацию собранного приложения в магазине AppStore.

Для публикации следует пересобрать мобильное приложение с использованием мобильной версии 8.3.23.80 (или последующие версии) на сборщике, который поставляется в комплекте с используемой мобильной версией.

Мобильное приложение, которое было собрано предыдущей версией сборщика мобильных приложений, не проходило проверку в магазине AppStore и не могло быть опубликовано.Устранено некорректное поведение системы.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 11.21.2 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.17.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 12.16.2 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 13.12.2 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 14.9.2 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.
  • Postgres Pro Enterprise certified.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro версии 15.4.2 следующих продуктов:
  • Postgres Pro 1C,
  • Postgres Pro Standard,
  • Postgres Pro Enterprise.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Данная версия СУБД Postgres Pro не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Дата акселератор.
Если во время исполнения запроса в Дата акселераторе формируется ошибка нехватки памяти, копия базы данных Дата акселератора отключается на 60 секунд. По завершению паузы в 60 секунд, запросы к Дата акселератору возобновляются. Если ошибки нехватки памяти не прекращаются последовательно 3 раза (с интервалом в 60 секунд), то копия базы данных Дата акселератора полностью отключается (до принудительного обновления).Копия базы данных Дата акселератора отключалась до принудительного обновления после первой же ошибки нехватки памяти.Выполняется попытка сохранить работоспособность копии базы данных Дата акселератора для выполнения более простых запросов, чем тот, который вызвал ошибку. Возможно, что при снижении нагрузки восстановится работа и со сложными запросами (ранее приводившим к ошибкам нехватки памяти).
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Tantor SE 1C.

Поддерживаются версии 14.8 и 15.4.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

СУБД Tantor SE не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Pangolin версии 5.3.2.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

СУБД Pangolin не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Jatoba версии 4.8.2-1117.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддерживаемые операционные системы: определяются производителем СУБД.

СУБД Jatoba не поддерживалась системой «1С:Предприятие».Расширен список поддерживаемых СУБД.
Работа в macOS.
Системные требования.
Реализована поддержка ОС macOS версий с 11 по 14 (включительно).Работа системы «1С:Предприятие» не поддерживалась под управлением ОС macOS версий 11.4 и последующих.Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь и здесь.
Документация.
В документации уточнено описание запроса OpenID-аутентификации, в том случае, если сервер OpenID использует проверку второго фактора аутентификации.В документации содержалось некорректное описание запроса OpenID-аутентификации, в том случае, если сервер OpenID использует проверку второго фактора аутентификации.Исправлена ошибка в документации.
В документации данное изменение описано здесь.
Средства администрирования.
В файлы cacert.pem и cacertnx.pem добавлены промежуточные сертификаты Федеральной налоговой службы Российской Федерации, сформированные с использованием алгоритмов ГОСТ Р 34.11-2012.Данная возможность не предоставлялась.Снижается количество ошибок проверки сертификатов при доступе к сайтам Федеральной налоговой службы Российской Федерации.
Средства разработки.
Реализована возможность активации лицензии для разработчиков в том случае, если пользователь зарегистрирован на портале «1C:Developer Network» (см. здесь).

Если язык локализации пользователя армянский, азербайджанский, грузинский, латышский, казахский, русский, туркменский - будет использоваться портал «1C для разработчиков» (см. здесь). Для всех остальных языков локализации будет предоставляться выбор между этими порталами. Выбор портала не зависит от параметра ExternalResourcesMode конфигурационного файла conf.cfg.

Для метода ПолучитьЛицензионноеСоглашениеРазработчика(), менеджера получения лицензий, реализован параметр ПорталРазработчиков. Реализовано свойство ЗапросНаПолучениеЛицензии.ПорталРазработчиков.

Возможность активации лицензии для разработчиков была доступна в том случае, когда пользователь был зарегистрирован только на портале «1C для разработчиков» (см. здесь).Получение лицензии для разработчиков стало доступно пользователям, которые не могут регистрироваться на портале «1C для разработчиков» (см. здесь).
В документации данное изменение описано здесь и здесь.

Оглавление

Переход с предыдущей версии на версию 8.3.23

Оглавление

Версия 8.3.22

Версия 8.3.22 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8322doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.21.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.20. +Возможность запуска конфигураций, разработанных в версии 8.3.21 и более младших, в версии 8.3.22, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.22 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.22, при необходимости, использовать для работы с информационной базой и версию 8.3.21. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Реализована новая версия (версия 2) механизма полнотекстового поиска в данных. Особенностью механизма является использование специальных алгоритмов выделения корневой основы и списка стоп-слов. Новая версия полнотекстового поиска поддерживает не все возможности поисковых запросов текущей версии полнотекстового поиска. Изменен дизайн выдачи результатов полнотекстового поиска.

Для новой версии полнотекстового поиска реализованы следующие изменения в поведении методов менеджера полнотекстового поиска:

  • Не используются методы ПолучитьРежимРазделенияСоставныхСлов()/УстановитьРежимРазделенияСоставныхСлов().
  • Метод ОбновитьИндекс() запускает процесс индексации и сразу возвращает управление. Для контроля завершения индексации следует использовать метод ИндексАктуален().
  • Метод ОбновлениеИндексаЗавершено() не учитывает необходимость слияния индексов полнотекстового поиска.

Для менеджера полнотекстового поиска реализованы методы ПолучитьВерсиюПолнотекстовогоПоиска()/УстановитьВерсиюПолнотекстовогоПоиска().

Реализованы сервисы кластера серверов:

  • Сервис полнотекстового поиска v2.
  • Сервис координации полнотекстового поиска v2.

Реализовано событие технологического журнала <FTS>.

Для утилиты ibsrv реализован параметр командной строки --ftext2-data.

Для работы новой версии полнотекстового поиска требуется наличие на компьютерах кластера серверов Java версии 8 и последующих.

Переработана стандартная обработка управления полнотекстовым поиском.

Новая версия полнотекстового поиска поддерживается в клиент-серверном варианте информационной базы, а при использовании автономного сервера - и с файловым вариантом информационной базы. В остальных вариантах использования новая версия полнотекстового поиска не поддерживается.

В платформе «1С:Предприятие» существовал только один вариант механизма полнотекстового поиска.В результате применения нового механизма полнотекстового поиска:
  • Повысится качество поисковой выдачи.
  • Повысится производительность полнотекстового поиска на больших информационных базах.
  • Повысится эффективность включения в индекс новой информации из информационной базы.
  • Будет исключено появление ошибки Превышено количество слов поиска.
  • Уменьшится дисковое пространство, которое занимает индекса полнотекстового поиска.
  • При большом количестве результатов поиска, сообщение об этом будет выступать предупреждением, а не ошибкой. Результаты поиска все равно будут отображаться.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Общие объекты.
Реализована возможность создания случайных паролей, структура которых упрощает запоминание пароля человеком (сохраняя сложность пароля). Реализован объект ГенераторСлучайныхПаролей.

В формах редактирования пользователя информационной базы и восстановления пароля реализована возможность сгенерировать случайный пароль.

В форме редактирования пользователя информационной базы, в полях ввода и подтверждения пароля, реализованы кнопки просмотра значения пароля. При нажатии гиперссылки Сгенерировать пароль - новый пароль отображается в поле Пароль в открытом виде.

Данная возможность не предоставлялась.Упрощено создание уникальных паролей для применения в различных подсистемах прикладного решения (в том числе для установки паролей входа пользователей информационной базы).
В документации данное изменение описано здесь, здесь и здесь.
Работа с криптографией.
Реализована полная поддержка использования криптографии в клиентском приложении под управлением ОС macOS. Поддерживаются криптографические механизмы «КриптоПро» (для ОС macOS).Поддержка механизма криптографии при работе под управлением ОС macOS была выполнена в ограниченном объеме.Реализована полная поддержка использования криптографии в клиентском приложении под управлением ОС macOS.
Расширение конфигурации.
Реализована возможность изменять свойства нумерации для документов, бизнес-процессов, задач и нумераторов.

Реализована возможность создания собственных нумераторов в расширениях. Реализована возможность установки собственных и заимствованных нумераторов для собственных и заимствованных документов расширения.

Реализована возможность изменять длину кода для справочников, задач, планов обмена, планов видов характеристик, планов счетов и планов расчета.

Реализована возможность изменять длину наименования для справочников, планов обмена, планов видов характеристик, планов счетов и планов расчета.

Данные возможности не предоставлялись.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь.
Общие объекты.
Реализовано свойство СистемнаяИнформация.ВариантПриложения. Свойство предназначено для идентификации специальных вариантов поставки платформы «1С:Предприятие». Обычная поставка идентифицируется пустой строкой в данном свойстве. Описание возможных значений свойства приводится в документации к специальным вариантам поставки платформы «1С:Предприятие».Данная возможность не предоставлялась.Реализована возможность определения специального варианта поставки платформы «1С:Предприятие» из встроенного языка.
Работа с PDF-документами.
Реализован метод ДокументPDF.Показать(). Данный метод позволяет открыть форму просмотра документа PDF из встроенного языка.Данная возможность не предоставлялась.

Форму просмотра документа PDF можно было открыть только интерактивно или создать полностью свою.

Объект ДокументPDF стал предоставлять возможности открыть форму просмотра, как и другие, аналогичные, объекты встроенного языка.
В документации данное изменение описано здесь.
Распределенные информационные базы.
Расширение конфигурации.
Реализована возможность получения информации о том, какие изменения находятся в обрабатываемом пакете обмена данными:
  • конфигурация,
  • расширения конфигурации,
  • расширения конфигурации, изменяющие данные.

Для менеджера плана обмена реализованы методы ПрочитатьОписаниеИзменений() и ПрочитатьИзмененияКонфигурацииИРасширенийКонфигурации().

Данная возможность не предоставлялась.

Было возможно только получить информацию о том, что в данный момент основная конфигурация отличается от конфигурации базы данных.

Улучшены возможности диагностики для реализации механизмов автоматического обмена данными в системах, использующих распределенную информационную базу.
В документации данное изменение описано здесь.
Клиентское приложение.
Средства администрирования.
Журнал регистрации.
Для аутентификации с помощью OpenID Connect или ЕСИА реализована возможность указания различных значений для идентификации пользователей информационной базы (ключи сопоставления). Эти значения указываются для каждого пользователя информационной базы и связаны с провайдером аутентификации, который используется в конкретном случае. Ключи сопоставления могут иметь произвольный идентификатор и значение.

Для объекта ПользовательИнформационнойБазы реализовано свойство КлючиСопоставленияПользователей. Доступ к данному свойству возможен только из встроенного языка.

Для указания, что пользователь при аутентификации определяется через ключи сопоставления, для поля authenticationUserPropertyName описания параметров провайдера в файле default.vrd, реализовано значение matchingKey.

Повышена информативность сообщений об ошибках при выполнении аутентификации с помощью OpenID Connect или ЕСИА.

При аутентификации пользователя с помощью OpenID Connect или ЕСИА можно было использовать ограниченный список полей для определения пользователя информационной базы.

Сообщения об ошибках, возникающих при аутентификации, были непонятными и не позволяли понять, в чем причина проблемы при выполнении аутентификации.

Улучшены возможности сопоставления пользователей при выполнении аутентификации с помощью OpenID Connect или ЕСИА. Улучшена диагностика проблемных ситуаций при выполнении аутентификации.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Система компоновки данных.
Реализована возможность указания макета оформления, который будет использоваться во всех отчетах прикладного решения по умолчанию. Реализована возможность указывать такой макет как для информационной базы в целом, так и для конкретного пользователя. Может быть указан как системный макет оформления данных, так и макет оформления данных, оформленный в виде общего макета конфигурации.

Для конфигурации реализовано свойство Основной макет оформления отчета. Реализовано свойство глобального контекста ОформлениеОтчетов.

Данная возможность не предоставлялась.

Указать макет оформления можно было только для каждого отчета, входящего в состав прикладного решения.

Улучшены возможности оформления отчетов. В частности, стало возможно оформить все отчеты конфигурации в едином стиле (включая отчеты, которые будут добавлены в конфигурацию позже и другими специалистами).
В документации данное изменение описано здесь.
Система взаимодействия.
Средства администрирования.
Реализована возможность создания выгрузки данных системы взаимодействия и восстановления данных из копии.

Реализована возможность переноса данных между различными экземплярами серверов системы взаимодействия.

Для менеджера системы взаимодействия реализованы методы: ПолучитьВыгрузкиДанныхАсинх(), ПолучитьВыгрузкиДанных(), ПолучитьВыгрузкуДанныхАсинх(), ПолучитьВыгрузкуДанных(), НачатьСозданиеВыгрузкиДанныхАсинх(), НачатьСозданиеВыгрузкиДанных(), ПолучитьАдресВыгрузкиДанныхАсинх(), ПолучитьАдресВыгрузкиДанных(), ЗагрузитьВыгрузкуДанныхАсинх(), ЗагрузитьВыгрузкуДанных(), ВыполнитьРегистрациюВыгрузкиДанныхАсинх(), ВыполнитьРегистрациюВыгрузкиДанных(), НачатьВосстановлениеИзВыгрузкиДанныхАсинх(), НачатьВосстановлениеИзВыгрузкиДанных(), УдалитьВыгрузкуДанныхАсинх(), УдалитьВыгрузкуДанных(), УстановитьОписаниеВыгрузкиДанныхАсинх(), УстановитьОписаниеВыгрузкиДанных().

Для стандартной обработки Управление системой взаимодействия реализована возможность выполнения работы с выгрузкой и загрузкой данных.

Формат файла выгрузки данных системы взаимодействия не документируется.

У сервера взаимодействия установлено ограничение на количество одновременно хранимых файлов выгрузки: не более 5 копий. Этот параметр можно изменить средствами конфигурирования сервера взаимодействия.

Данные возможности не предоставлялись.

Выполнять выгрузку данных системы взаимодействия и переносить данные между разными экземплярами серверов взаимодействия было невозможно.

Реализована возможность переноса данных с одного сервера взаимодействия (включая облачный сервер) в другой,

Стало возможно выполнять выгрузку всех данных сервера взаимодействия в виде одного файла.

В документации данное изменение описано здесь.
Работа с PDF-документами.
Реализована возможность выполнять преобразование документа PDF таким образом, чтоб цветовое оформление в документе преобразуется в оттенки серого.

В формах работы с документами PDF реализованы команды, позволяющие выполнить такое преобразование. Для объекта ДокументPDF реализованы методы ПреобразоватьВОттенкиСерогоАсинх(), ПреобразоватьВОттенкиСерого().

Данная возможность не предоставлялась.Расширены возможности работы с документами PDF.
В документации данное изменение описано здесь.
Работа с PDF-документами.
Для расширения поля формы для документа PDF реализовано свойство ИспользуемоеИмяФайла, с помощью которого можно указать имя файла, которое будет использовано в том случае, если пользователь решит сохранить документ, отображаемый полем формы.Данная возможность не предоставлялась.Расширены возможности работы с документами PDF.
В документации данное изменение описано здесь.
Встроенный язык.
Для колонок реквизитов формы клиентского приложения типа ТаблицаЗначений и ДеревоЗначений реализовано свойство Проверка заполнения (ПроверкаЗаполнения). Проверка выполняется формой клиентского приложения. Собственно проверка выполняется аналогично табличным частям справочников, документов и т.д.Проверка заполнения реквизитов формы клиентского приложения типа ТаблицаЗначений или ДеревоЗначений было возможно только на наличие хотя-бы одной строки. Проверка заполнения колонок реквизитов не поддерживалась.Улучшены возможности автоматической проверки заполнения реквизитов формы клиентского приложения типа ТаблицаЗначений или ДеревоЗначений.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Реализована возможность изменения в расширении локализуемых свойств объектов конфигурации (пояснение, форматы представления и редактирования, подсказки, представления объектов, записей и списков).

Реализована возможность модифицировать заимствованные общие макеты и макеты объектов конфигурации.

Отсутствовали возможности изменения локализуемых свойств объектов и макетов, кроме табличного документа.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Для метода РасширенияКонфигурации.Создать() реализован необязательный параметр Данные. С помощью этого варианта метода стало возможно создавать объект типа РасширениеКонфигурации из значения типа ДвоичныеДанные. Для объекта РасширениеКонфигурации, созданного таким способом, метод Записать() не будет требовать указания параметра Данные.

Реализован метод РасширенияКонфигурации.РасширенияКонфигурацииИзменены(), который позволяет узнать, что после запуска текущего сеанса был изменен состав расширений или было обновлено какое-то из существующих расширений.

Не поддерживалась возможность получить параметры расширения без записи расширения в базу данных.

Проанализировать, что после старта текущего сеанса состав расширений был изменен или было обновлено какое-либо расширение, можно было путем анализа состава и хеш-сумм расширений сеанса и информационной базы.

Расширены возможности администрирования расширений.
В документации данное изменение описано здесь.
Работа с запросами.
Система компоновки данных.
В запросах и системе компоновки данных реализована возможность получать уникальный идентификатор ссылки объекта информационной базы.

В языке запросов и языке выражений системы компоновки данных реализована функция УникальныйИдентификатор().

Данная возможность не предоставлялась.В запросах и системе компоновки данных реализована возможность получать уникальный идентификатор ссылки объекта информационной базы.
В документации данное изменение описано здесь и здесь.
Средства администрирования.
Кластер серверов.
Реализована возможность использовать сервис внешнего управления сеансами для файловых информационных баз. Использование сервиса внешнего управления сеансами для файлового варианта информационной базы доступно с использованием лицензии уровня ПРОФ.

Для конфигурационного файла conf.cfg реализованы параметры ExternalSessionManagementRequired и ExternalSessionManagementConnectionString.

Для метода synchronize() Web-сервиса внешнего управления сеансами реализованы параметры SessionNumber и ClientIPAddress. Для объекта Sessions реализованы свойства SessionNumber и ClientIPAddress. Новые возможности доступны только в том случае, если параметр wsver имеет значение 4.

Данная возможность не предоставлялась.

Возможность внешнего управления сеансами была доступна только для клиент-серверного варианта информационной базы.

Возможность централизованно управлять количеством одновременно используемых лицензий для различных прикладных решений, без модификации самих прикладных решений.
В документации данное изменение описано здесь, здесь и здесь.
Табличный документ.
Автоматический расчет ширины колонок при выводе результата отчета в табличный документ выполняется следующим образом:
  • Ширина колонок для первых 100 выводимых строки рассчитывается точно: при помощи графической библиотеки измеряется ширина, которую займет выводимый текст, без добавления «запаса» ширины.
  • Ширина колонок для строк, начиная со 101 строки, автоматически не рассчитывается.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

При двойном щелчке мышью по разделителю колонок, ширина колонки вычисляется с учетом свойства Размещение: если в ячейке табличного документа это свойство имеет значение Переносить, то ширина текста рассчитывается таким образом, чтобы не превышать 80 символов шрифта, установленного в ячейке (с учетом выполненных переносов).

Автоматический расчет ширины колонок при выводе результата отчета в табличный документ выполнялся следующим образом:
  • Для колонок первой выводимой строки размер рассчитывался «точно»: при помощи графической библиотеки измерялась ширина, которую займет выводимый текст и к этому значению добавлялось 10 пикселей.
  • Для последующих 99 выводимых строк размер рассчитывался «приблизительно»: количество символов выводимого текста, умножалось на среднюю ширину символа шрифта и к этому значению добавлялось значение, равное 2 средним ширинам символа.
  • Для строк, начиная со 101, ширина колонок автоматически не рассчитывалась.

+

Реализован более корректный расчет ширины колонок в отчетах.
В документации данное изменение описано здесь.
Табличный документ.
Для табличного документа реализована возможность устанавливать отступы содержимого от границ ячейки/области ячеек.

Для объектов ОбластьЯчеекТабличногоДокумента, РисунокТабличногоДокумента, ОформлениеКомпоновкиДанных, ОформлениеЯчейкиТаблицыОбластиКомпоновкиДанных реализованы свойства ОтступСлева, ОтступСправа, ОтступСверху, ОтступСнизу. Для настроек системы компоновки данных данные свойства доступны только для настроек отчетов.

Экспорт в форматы XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше, Microsoft Word 2007 и старше) или ODS (OpenDocument) учитывает наличие отступов.

Данная возможность не предоставлялась.Улучшены возможности оформления отчетов.
Табличный документ.
Реализована возможность получать формат строк области ячеек табличного документа.

Реализовано свойство ОбластьЯчеекТабличногоДокумента.ФорматСтрок.

Для методов Область() и ПолучитьОбласть() объекта ТабличныйДокумент реализован параметр ФорматСтрок.

Данная возможность не предоставлялась.С помощью встроенного языка стало возможно определить, какой формат строк установлен для выделенной области ячеек.
Работа с СУБД.
В данные (поле Назначение), возвращаемые методом глобального контекста ПолучитьСтруктуруХраненияБазыДанных(), внесена информация, описывающая таблицу обмена данными для мобильного клиента с автономным режимом.Данная возможность не предоставлялась.Устранено некорректное поведение системы.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 10.19, 11.14.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 10.20, 11.15.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 10.21, 11.16.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 12.9, 13.5, 14.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 12.10, 13.6, 14.2.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 12.11, 13.7, 14.3.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Средства печати.
В ОС macOS печать выполняется с использованием системных интерфейсов операционной системы.

В ОС macOS и Linux из всех форм печати скрывается кнопка Принтер.

В ОС macOS печать выполнялась средствами платформы.

В ОС macOS и Linux в формах печати была доступна кнопка Принтер, но нажатие этой кнопки не вызывало никаких действий, т.к. в этих ОС не предоставляется возможность открыть отдельный диалог настроек свойств принтера.

В ОС macOS при печати используются знакомые и привычные пользователю инструменты печати.
Система взаимодействия.
Реализован поиск неконтекстных обсуждений по заголовку обсуждения и по полным именам участников. Для поиска допускается вводить несколько слов, разделенных пробелом. Найдены должны быть все введенные слова.Поиск можно было выполнять только по заголовку обсуждений.Упрощен поиск неконтекстных обсуждений, когда известен только участник (или участники) обсуждения.
Система взаимодействия.
Упрощен выбор монитора при начале демонстрации экрана. Выбор предлагается в том случае, если к компьютеру подключены несколько мониторов. Изменение реализовано только для тонкого и толстого клиентских приложений.Выбор монитора при начале демонстрации экрана был менее понятным и требовал больше действий.Упрощен выбор монитора при начале демонстрации экрана.
Табличный документ.
Расширена область, за которую можно перетаскивать область табличного документа.Область, за которую можно перетаскивать область табличного документа, имела меньший размер.Стало более удобно перетаскивать область табличного документа.
Обработка ошибок.
Веб-клиент.
Если при формировании отчета об ошибке требуется снять скриншот с экрана, то в веб-браузере Mozilla Firefox для этого будет использоваться расширение веб-браузера для работы с 1С:Предприятием. В расширении реализовано разрешение для снятия скриншотов.

Если у пользователя не установлено расширение веб-браузера - формируется предупреждение о необходимости установки расширения и причинах такой рекомендации (снятие скриншота требует много времени).

Если при формировании отчета об ошибке требуется снять скриншот с экрана, то в веб-браузере Mozilla Firefox это могло занимать существенное время.Ускорено снятие скриншотов экрана с ошибкой в том случае, если при формировании отчета об ошибке в веб-клиенте требуется приложить скриншот экрана. Ускорение реализовано в том случае, если веб-клиент работает под управлением веб-браузера Mozilla Firefox.
Система взаимодействия.
Улучшен пользовательский интерфейс системы взаимодействия и окна с видеозвонком.

Для команды Пометить как прочитанное списка сообщений реализовано сочетание клавиш Ctrl + M.

Пользовательский интерфейс системы взаимодействия и окна видеозвонка был менее удобным.Улучшен пользовательский интерфейс системы взаимодействия и окна с видеозвонком.
Система взаимодействия.
Для сайта, обеспечивающего работу внешних пользователей системы взаимодействия, реализованы следующие возможности:
  • Команда цитирования при ответе на сообщения.
  • Команда пометки обсуждения прочитанным. Настройка отметки прочтения в настройках пользователя.
  • Просмотр изображения без необходимости скачивания файла картинки на локальный накопитель.
  • Диалог выбора оборудования для использования во время видеозвонков.
  • Редактирование аватара текущего пользователя.
  • Копирование вложений с помощью контекстного меню.
  • Более удобный вид окна для видеоконференции.
Данные возможности не предоставлялись.Улучшен сайт, обеспечивающий работу внешних пользователей системы взаимодействия.
Система взаимодействия.
В системе взаимодействия изменен внешний вид формы видеоконференции и кнопок в этой форме (распахнуть на весь экран и т.д.). Изменена анимация во время подключения нового пользователя, переподключения пользователя и запуске демонстрации экрана.В системе взаимодействия форма видеоконференции, изображение кнопок этой формы и анимация были другими.Улучшен внешний вид формы видеоконференции.
Мобильный клиент.
Система взаимодействия.
Повышено качество изображения видеозвонка в том случае, если на мобильном клиенте видеозвонки выполняются с помощью видео-сервера.

Качество изображения видеозвонка подстраивается под текущую загрузку процессора и размера видео на экране мобильного устройства.

При определении качества изображения видеозвонка не учитывалась нагрузка на процессор и размер видео на экране мобильного устройства.Улучшено качество изображения видеозвонка при работе мобильного клиента на мобильных устройствах.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
Оптимизировано получение результатов запроса, содержащего большое количество вложенных таблиц.Получение результатов запроса, содержащего большое количество вложенных таблиц, занимало много времени.Ускорено получение результатов запроса, содержащего большое количество вложенных таблиц.
Работа с СУБД.
Оптимизировано использование оператора языка запросов В(<список значений>) при работе с использованием СУБД PostgreSQL. В частности, ускорено исполнение запросов ограничения доступа к данным.

Рекомендуется проанализировать условия в запросах и, в случае использования СУБД PostgreSQL, выполнить замену выражений вида Пер1=Пер2 ИЛИ Пер1=Пер3 на выражение Пер1 В (Пер2, Пер3).

Запросы, которые использовали оператор языка запросов В(<список значений>) при работе с использованием СУБД PostgreSQL, требовали больше времени для исполнения.Повышена производительность оператора языка запросов В(<список значений>) при работе с использованием СУБД PostgreSQL.
Работа с файлами.
Существенно ускорены операции передачи файлов между клиентом и сервером.

Снимается ограничение на размер файла, который помещается во временное хранилище.

Операции передачи файлов между клиентом и сервером требовали больше времени.

Размер файла, который помещается во временное хранилище, не мог превышать 4 Гбайт (в сериализованном виде).

Улучшены характеристики механизма работы с файлами в системе «1С:Предприятие».
В документации данное изменение описано здесь.
Расширение конфигурации.
Кластер серверов.
При использовании расширений в разделенной информационной базе существенно снижено потребление оперативной памяти рабочими процессами кластера серверов.При использовании расширений в разделенной информационной базе рабочие процессы кластера серверов потребляли больше оперативной памяти.Снижено потребление оперативной памяти кластером серверов при использовании расширений в разделенной информационной базе.
Кластер серверов.
Оптимизирована работы с хранилищем сеансовых данных.Работа с хранилищем сеансовых данных выполнялась не оптимально.Отсутствует падение производительности кластера серверов в том случае, если кластер серверов хранит большие объемы данных в хранилище сеансовых данных.
Средства разработки.
Ускорена выгрузка конфигурации в cf-файл.Выгрузка конфигурации в cf-файл занимала больше времени.Ускорена выгрузка конфигурации в cf-файл.
Средства разработки.
Ускорена операция сравнения конфигураций.

Ускорено обновление конфигурации прикладного решение. В 32-разрядном варианте конфигуратора уменьшено использование оперативной памяти при выполнении обновления конфигурации. +

Операции сравнение конфигураций и обновления конфигурации занимали больше времени.

32-разрядный вариант конфигуратора использовал больше оперативной памяти при выполнении обновления конфигурации.

Ускорены операции сравнения конфигураций и обновления конфигурации.
Полнотекстовый поиск.
Уменьшено время выполнения запроса полнотекстового поиска, который использует оператор И. Для получения ускорения необходимо выполнить перестроение индекса полнотекстового поиска.Запрос полнотекстового поиска, который использует оператор И, требовал для выполнения больше времени.Ускорено выполнение запроса полнотекстового поиска, использующего оператор И.
Полнотекстовый поиск.
Повышена надежность работы полнотекстового поиска:
  • Предотвращено появление больших файлов индекса с высокой фрагментацией.
  • Повышена скорость слияния индексов на больших информационных базах.
Создание файлов индекса очень большого размера могло приводить к ошибкам файловой системы.Повышена надежность работы механизма полнотекстового поиска.
Средства разработки.
Оптимизировано использование оперативной памяти при открытии в конфигураторе формы Все роли.При открытии в конфигураторе формы Все роли использовалось большое количество оперативной памяти.Оптимизировано использование оперативной памяти при открытии в конфигураторе формы Все роли.
Средства администрирования.
Оптимизировано получение списка блокировок аутентификаций пользователей. Время, затрачиваемое на получения списка блокировок, не зависит от количества пользователей информационной базы.Время, затрачиваемое на получение списка блокировок аутентификаций пользователей, зависело от количества пользователей информационной базы.Ускорено выполнение команды конфигуратора Администрирование - Блокировки аутентификации и выполнение метода встроенного языка БлокировкаАутентификации.ПолучитьБлокировки().
Полнотекстовый поиск.
Если во время индексации данных полнотекстового поиска происходят какие-либо файловые ошибки (связанные с файлами индекса), то индекс полнотекстового поиска остается в корректном состоянии.Если во время индексации данных полнотекстового поиска происходят какие-либо файловые ошибки (связанные с файлами индекса), то индекс полнотекстового поиска становился непригодным для использования.Повышена стабильность работы полнотекстового поиска данных при индексации данных.
Расширение конфигурации.
Кластер серверов.
Снижено потребление оперативной памяти рабочим процессом кластера серверов, если рабочий процесс обслуживает разделенную информационную базу, к которой подключены разделенные расширения, влияющие на пользовательский интерфейс.Наблюдалось избыточное потребление оперативной памяти рабочим процессом кластера серверов, если рабочий процесс обслуживает разделенную информационную базу, к которой подключены разделенные расширения, влияющие на пользовательский интерфейс.Снижено потребление оперативной памяти кластером серверов, который обслуживает разделенные информационные базы с расширениями, влияющими на пользовательский интерфейс.
Картинки.
Ускорено обращение к свойствам объекта БиблиотекаКартинок (в том числе последовательные обращения к одному и тому же свойству) .Обращение к свойствам объекта БиблиотекаКартинок требовало больше времени.Ускорена работа с библиотекой картинок платформы «1С:Предприятие». В частности, ускорено открытие формы Функции для технического специалиста в конфигурациях с большим количество метаданных.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
Система «1С:Предприятие» устанавливает гранулярность блокировок на уровне строк, если используется Microsoft SQL Server версии 2008 и последующие версии. Исключается возможность эскалации блокировок. Возможно увеличение потребления оперативной память Microsoft SQL Server.Система «1С:Предприятие», использующая Microsoft SQl Server, устанавливала гранулярность блокировок на уровне страницы.Исключена вероятность блокировок в том случае, когда разные пользователи работали с разными объектами базы данных, попадавших в одну страницу индекса СУБД.
Журнал регистрации.
Исключена возможность конвертации журнала регистрации в формат SQLite.

Поддержка формата SQLite журнала регистрации будет прекращена в последующих версиях системы «1С:Предприятие».

Рекомендуется выполнить переход на последовательный формат хранения журнала регистрации.

Система «1С:Предприятие» поддерживала возможность конвертации журнала регистрации в формат SQLite.Выполнена подготовка системы «1С:Предприятие» к отказу от поддержки формата SQLite журнала регистрации.
В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Клиентское приложение.
Если при выполнении вызова Интернет-сервиса происходит потеря соединения - формируется перехватываемое исключение.

При работе клиентского приложения по протоколу HTTP, потеря связи во время работы приводит к возникновению стандартного диалогового окна ошибки с возможностью повторения незавершенного действия.

Если при выполнении вызова Интернет-сервиса происходила потеря соединения - происходило зависание приложения.

При работе клиентского приложения по протоколу HTTP, потеря связи во время работы приводило к зависанию клиентского приложения.

При нестабильном сетевом соединении повышена отзывчивость клиентского приложения при работе по протоколу HTTP и при использовании Интернет-сервисов.
Кластер серверов.
Переработан механизм мониторинга кластера серверов. Повышена стабильность работы кластера и подключенных пользователей. Показатели производительности измеряются в том числе и для рабочих процессов, которые работают на единственном рабочем сервере. Мониторинг продолжает свою работу и при зависании одного из рабочих процессов. При увеличении количества центральных серверов не происходит роста нагрузки на рабочие процессы.

Изменен состав свойств событий <ATTN> и <CLSTR>.

Показатели производительности не измерялись для рабочих процессов, которые работают на единственном рабочем сервере. Мониторинг кластера не работал при зависании одного из рабочих процессов. При увеличении количества центральных серверов росла нагрузка на рабочие процессы.Повышена стабильность работы кластера серверов и пользователей, которые обслуживаются этим кластером.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Общие объекты.
Для объекта ГенераторСлучайныхЧисел используется генератор случайных чисел в соответствие со стандартом NIST SP 800-90A (алгоритм Hash_DRBG). Последовательность чисел, которая получается при создании двух разных объектов генератора случайных чисел с использованием одного и того же начального числа, будет различной.Для объекта ГенераторСлучайныхЧисел использовался алгоритм Вихрь Мерсенна.Улучшен генератор случайных чисел.
Расширение конфигурации.
Для команды Конфигуратора Проверка применимости расширений реализованы дополнительные проверки:
  • Проверка существования метода, указанного в аннотации.
  • Проверка соответствия количества параметров методов и модификаторов передачи значений в методе основной конфигурации и расширения.

Данные проверки выполняются для методов, которые не являются обработчиками событий.

Данная возможность не предоставлялась.Упрощено исправление ситуаций, когда в основной конфигурации перестал существовать расширяемый метод или у расширяемого метода изменилось количество параметров или модификаторы передачи параметров.
Клиентское приложение.
В тонком клиенте, если серверный вызов не завершился в течение 400 мсек, курсор мыши меняет вид на «занят». В толстом клиенте поведение не изменилось.В тонком и толстом клиентском приложениях, курсор мыши менял вид на «занят» при начале серверного вызова.Изменение курсора мыши отображает длительный серверный вызов, но курсор не «моргает» при большом количестве коротких серверных вызовов.
Форма клиентского приложения.
Если шрифт создается на основании другого шрифта и при этом указан размер создаваемого шрифта, то размер и масштаб шрифта-основания не используются для определения характеристики создаваемого шрифта.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

Текст, для которого задан шрифт размера 0, всегда отображается шрифтом с размером 13 pt во всех клиентских приложениях и на сервере. +

Если шрифт создается на основании другого шрифта и при этом указан размер создаваемого шрифта, то размер и масштаб шрифта-основания использовались для определения характеристики создаваемого шрифта.

Текст, для которого задан шрифт размера 0, отображался по разному в разных клиентских приложениях.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если одно доступное поле отбора компоновки данных формируется из нескольких полей (посредством объединения полей в запросе или посредством получения нескольких полей через точку для разных ссылочных типов), то у этого доступного поля свойства СвязьПоТипу и ФормаВыбора заполняются, только если у всех полей, формирующих это поле, данные свойства содержат одинаковые значения. Кроме того, для доступного поля свойства ПараметрыВыбора и СвязиПараметовВыбора, заполняются таким образом, что в результирующие связи и параметры попадают только параметры и связи, которые есть во всех полях, входящих в доступное поле, и у которых совпадают значения всех свойств.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

Если одно доступное поле отбора компоновки данных формируется из нескольких полей (посредством объединения полей в запросе или посредством получения нескольких полей через точку для разных ссылочных типов), то у этого доступного поля свойства СвязьПоТипу, ФормаВыбора, ПараметрыВыбора, СвязиПараметовВыбора, заполнялись из первого поля, в котором соответствующее свойство имеет не пустое значение.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Внешние компоненты.
Веб-клиент.
Для внешних компонент, поддерживающих работу в среде веб-браузера под управлением ОС Linux, реализована поддержка работы с русским языком даже в том случае, когда в ОС отсутствует русская локализация.

Для того, чтобы внешние компоненты стали поддерживать эту возможность, внешние компоненты необходимо пересобрать с новыми библиотеками адаптеров.

Внешние компоненты, поддерживающие работу в среде веб-браузера под управлением ОС Linux, работали с ошибками в том случае, когда в ОС отсутствовала русская локализация.При работе веб-клиента под управлением ОС Linux, в которой не установлена русская локализация, стало возможно использовать внешние компоненты, расширения работы с файлами и криптографией.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.15.Версия формата выгрузки конфигурации в XML-файлы была равна 2.14.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
В XDTO-пакете, описывающем типы данных текущей конфигурации, для всех реквизитов, которые принадлежат только группе или только элементу иерархического плана видов характеристик, значение минимальной границы установлено в значение 0.

+

В XDTO-пакете, описывающем типы данных текущей конфигурации, для всех реквизитов, которые принадлежат только группе или только элементу иерархического плана видов характеристик, значение минимальной границы было установлено в значение 1.Устранено некорректное поведение системы.

При XDTO-сериализации объектов иерархического плана видов характеристик стали корректно передаваться реквизиты, которые присутствуют только в группе или только в элементе.

В документации данное изменение описано здесь.
Табличный документ.
Система компоновки данных.
При экспорте табличного документа в различные форматы реализована возможность управлять качеством картинок, которые размещены в экспортируемом табличном документе.

Для табличного документа реализовано свойство ПлотностьСохраняемыхКартинок. Для списка параметров вывода компоновки данных (тип ЗначенияПараметровВыводаКомпоновкиДанных) реализован параметр ПлотностьСохраняемыхКартинок. Реализован объект МакетДокументаОбластиКомпоновкиДанных. В макет компоновки данных для табличного документа первым макетом помещается объект ОписаниеМакетаОбластиМакетаКомпоновкиДанных. Этот макет помещается в тело макета компоновки данных.

При экспорте табличного документа в формате Office OpenXML (*.docx) рисунки сохраняются в формате DrawingML.

Если для системы компоновки данных не задан параметр ПлотностьСохраняемыхКартинок, то компоновщик макета компоновки данных использует для этого параметра значение Высокая (а в режиме совместимости с версей 8.3.21 - Исходная).

Если известно, что отчет или табличный документ содержат картинки, с которыми желательно работать в оригинальном качестве (например, они будут сохраняться в файлы и редактироваться), то рекомендуется устанавливать свойство ПлотностьСохраняемыхКартинок в значение Исходная.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

Данная возможность не предоставлялась. Картинки всегда сохранялись в исходном виде.

При экспорте табличного документа в формате Office OpenXML (*.docx) рисунки сохраняются в формате VML.

Стало возможно управлять размером файла, который получается в результате экспорта табличного документа в другой формат.
В документации данное изменение описано здесь.
Расширение конфигурации.
Снижено использование оперативной памяти в том случае, когда в расширении конфигурации находится много ролей и заимствованных объектов.

Ускорен запуск сеанса при наличии в расширении большого количества ролей и заимствованных объектов.

При подключении расширения уменьшено количество однотипных сообщений об ограничениях доступа при расширении ролей. +

Приложение использовало больше оперативной памяти в том случае, когда в расширении конфигурации находится много ролей и заимствованных объектов.

Запуск сеанса занимал больше времени при наличии в расширении большого количества ролей и заимствованных объектов.

При подключении расширения формировалось большое количество однотипных сообщений об ограничениях доступа при расширении ролей.

Повышена эффективность использования ресурсов компьютера при использовании расширений с большим количеством ролей и заимствованных объектов.
Табличный документ.
При экспорте табличного документа в форматы Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) реализовано следующее поведение для объектов типа Картинка:
  • Если значение свойство РазмерРисунка не равно значению Черепица, то в результирующий документ сохраняется оригинальная картинка. Если для ячейки задан узор, то дополнительно сохраняется картинка узора.
  • Если свойство РазмерРисунка установлено в значение Черепица, то картинка перерисовывается в результирующий документ, а для рисунка документа Microsoft Excel устанавливается цвет фона, равный цвету фона картинки сходного документа.

В результате сделанных изменений, при масштабировании документа Microsoft Excel, меньше искажаются картинки, размещенные в табличном документе.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

При экспорте табличного документа в форматы Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) наблюдалось следующее поведение для объектов типа Картинка:
  • Если значение свойство РазмерРисунка не равно значению Растягивать, то картинка перерисовывалась в результирующий документ.
  • Если свойство РазмерРисунка установлено в значение Растягивать, то картинка перерисовывалась в результирующий документ (если не задан цвет фона или узор) и сохранялась оригинальная картинка во всех остальных случаях.

+

Результат сохранения табличного документа в форматах Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) в большей степени соответствует ожиданиям пользователей.
Работа с PDF-документами.
Если PDF-документ содержит картинки в формате JPEG 2000, то они отображаются при просмотре этого документа средствами платформы «1С:Предприятие».Если PDF-документ содержит картинки в формате JPEG 2000, то при просмотре этого документа средствами платформы «1С:Предприятие», эти картинки не отображались.Устранено некорректное поведение системы.
Мобильная платформа.
Мобильный клиент.
Изменена работа с оповещением пользователя в мобильной версии системы «1С:Предприятие»:
  • Закрытие оповещения выполняется нажатием по нему.
  • Если оповещение позволяет выполнить действие, то в этом случае в правой части оповещения отображается картинка.
  • При отображении оповещения система старается расположить оповещение так, чтобы на закрывать (или минимально закрывать) элементы управления формы, которые могут быть использованы пользователем. В любом случае система старается отобразить оповещение в нижней трети экрана мобильного устройства.
Работа с оповещением пользователя в мобильной версии системы «1С:Предприятие» имела следующие особенности:
  • Закрытие оповещения выполнялось смахиванием оповещения.
  • Если оповещение позволяет выполнить действие, то это действие выполнялось при нажатии по оповещению. Если оповещение не содержало действия - нажатие на оповещение «пропускалось» в подлежащую форму.
  • Оповещение всегда располагалось в фиксированном месте экрана.
Поведение оповещения пользователя в платформе максимально приближено к поведению оповещения мобильной операционной системы. Использовать оповещения стало удобнее.
Система компоновки данных.
Если параметр отчета содержит значение типа СписокЗначений, то при формировании представления параметра используются настройки отображения значений, заданные пользователем:
  • Представление каждого значения списка формируется с учетом условного оформления и доступных значений.
  • Пустые значения отображаются строкой <Пустое значение>.
  • Представления значений разделяются символом «;».
При формировании представления параметра отчета, который содержит значение типа СписокЗначений, не использовались настройки отображения значений, заданные пользователем.Представление параметра отчета, содержащего список значений, формируется аналогично другим параметрам отчета.
Система взаимодействия.
Повышено качество изображения во время видеозвонков внешних пользователей системы взаимодействия.Качество изображения во время видеозвонков внешних пользователей системы взаимодействия было недостаточным.Повышено качество изображения во время видеозвонков. Снижена нагрузка на медленные клиентские компьютеры.
Система взаимодействия.
Реализована доступность на запись для свойства ПользовательСистемыВзаимодействия.ИдентификаторПользователяИнформационнойБазы.

Для изменения свойств ИдентификаторПользователяИнформационнойБазы и КлючСопоставления объекта ПользовательСистемыВзаимодействия,пользователь, от имени которого выполняется изменение, должен обладать правами АдминистрированиеДанных.

Свойство ПользовательСистемыВзаимодействия.ИдентификаторПользователяИнформационнойБазы было недоступно на запись.

Для изменения свойства ПользовательСистемыВзаимодействия.КлючСопоставления не требовались особые права

Стало возможно переносить данные между различными серверами системы взаимодействия без потери данных.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Внешние отчеты и обработки.
Для метода Подключить() менеджера внешних обработок реализован параметр КодЯзыка. Параметр позволяет указать язык, который будет использоваться в подключаемой внешней обработке в качестве текущего языка.Данная возможность не предоставлялась.

При подключении внешней обработки использовался текущий язык аутентифицированного пользователя. Код этого языка возвращается методом глобального контекста ТекущийЯзык().

Реализована возможность открывать внешние обработки на требуемом языке локализации.
В документации данное изменение описано здесь.
Дата акселератор.
Система лицензирования.
Кластер серверов.
Реализована возможность запуска в рамках одного кластера серверов нескольких экземпляров Дата акселератора. Реализована возможность управления созданием нескольких экземпляров Дата акселератора с помощью разрешительных и запретительных требований назначения функциональности.

Для лицензии уровня ПРОФ допускается использование не более одного экземпляра Дата акселератора в одном кластере серверов. Для лицензии уровня КОРП допускается использование неограниченного количества экземпляров Дата акселератора в одном кластере серверов.

В рамках одного кластера серверов «1С:Предприятия» можно было запустить только один экземпляр Дата акселератора.Стало возможно распределять нагрузку между несколькими экземплярами Дата акселератора. В результате повышена производительность выполнения запросов, использующих Дата акселератор.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Форма клиентского приложения.
Средства администрирования.
При сохранении настроек формы для другого (не текущего) пользователя, гарантируется, что новые настройки начнут действовать не более чем через 20 секунд с момента сохранения. Под «настройками формы» понимаются настройки, которые расположены в хранилище системных настроек и имеют суффикс ключа настроек /НастройкиФормы.Настройки формы, скопированные другому пользователю, применялись только после разрыва последнего соединения с информационной базой, если эта форма в сеансе пользователя (которому скопированы настройки) уже открывалась.Упрощено копирование настроек форм другим пользователям информационной базы.
Встроенный язык.
Если при создании объекта ОписанияОповещения() указывается метод обработки ошибок, то управление в этот метод попадает только в том случае, когда ошибка возникает в рамках того асинхронного вызова, в который передается созданный объект ОписаниеОповещения.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

Если при создании объекта ОписанияОповещения() указывается метод обработки ошибок, то управление в этот метод попадало не только в том случае, когда ошибка возникала в рамках выполнения асинхронного вызова, но и в том случае, когда ошибка возникала во время выполнения метода, который вызывается после завершения асинхронного вызова.Устранено некорректное поведение системы.
Система взаимодействия.
Для объекта ДанныеРегистрацииИнформационнойБазыСистемыВзаимодействия реализована доступность в тонком и веб-клиентах.Объекта ДанныеРегистрацииИнформационнойБазыСистемыВзаимодействия был доступен только в толстом клиенте и на сервере. При передаче значения данного типа с сервера в тонкий клиент, на стороне клиента значение было доступно как значение типа ДвоичныеДанные.Устранено незапланированное поведение системы.
Система компоновки данных.
Если параметр оформления Текст, заданный в оформлении поля набора данных схемы компоновки данных, используется в макетах отчетов системы компоновки данных, то в отчет будет выводиться значение этого параметра.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

Рекомендуется проанализировать использование параметра оформления Текст и если в настройках полей наборов данных есть заполненные параметры, но их вывод не предполагается - следует снять признак использования у такого параметра.

Параметр оформления Текст, заданный в оформлении поля набора данных схемы компоновки данных, не использовался при выводе отчета, если поле с таким параметром использовалось в макетах отчетов системы компоновки данных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Параметр оформления Выделять отрицательные, заданный в оформлении поля набора данных схемы компоновки данных, применяется в макетах отчетов системы компоновки данных и макетах динамических списков. Cпециальный цвет стиля ЦветОтрицательногоЧисла используется в ячейке макета отчета системы компоновки данных и динамическом списке, если в выводимом поле содержится отрицательное значение. В макете компоновки данных в оформлении ячейки для параметра оформления ЦветТекста создается выражение макета системы компоновки данных.

В режиме совместимости с версией 8.3.21 поведение не изменилось.

Параметр оформления Выделять отрицательные, заданный в оформлении поля набора данных схемы компоновки данных, используется в макетах отчетов системы компоновки данных и макетах динамических списков. Cпециальный цвет стиля ЦветОтрицательногоЧисла использовался в ячейке макета отчета системы компоновки данных и динамического списка, только если в ячейке содержится текст, первый значимый символ которого «-». В макете компоновки данных в оформлении поля макета создавался параметр ВыделятьОтрицательные.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Форма клиентского приложения.
Свойство диаграммы Обновление объявляется устаревшим для управляемого режима. При использовании в веб-клиенте использование свойства не оказывает влияния на поведение диаграммы.Использование свойства диаграммы Обновление в тонком клиенте не оказывало влияния на построение диаграммы. В веб-клиенте свойство работало.Устранено различие в поведении диаграммы в веб-клиенте (по сравнению с тонким клиентом).
Web-сервисы и HTTP-сервисы.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
Средства администрирования.
Повышена производительность исполнения вызова метода Интернет-сервиса за счет оптимизации выбора подходящего (для исполнения вызова) сеанса. Отсутствует ограничение на размер пула сеансов. Все вызовы Интернет-сервисов выполняются сразу.

В файле default.vrd для элементов, описывающих Web-сервисы, HTTP-сервисы и стандартный интерфейс OData удалены атрибуты poolSize и poolTimeout. +

При вызове Интернет-сервисов существовало ограничение на размер пула сеансов, которые выполняют вызовы.Повышена скорость вызова Интернет-сервисов.
В документации данное изменение описано здесь, здесь и здесь.
Средства администрирования.
Метод УстановитьМинимальнуюДлинуПаролейПользователей() не позволяет установить длину паролей пользователя менее 0 и более 99 символов. При нарушении ограничения вызывается исключение. В режиме совместимости с версией 8.3.21 поведение не изменилось.

Если в информационной базе действует проверка сложности паролей пользователя, то нижней границей длины пароля служит максимальное значение из 7 и установленной минимальной длины пароля.

Если установленное значение параметра информационной базы Минимальная длина паролей пользователей превышает значение 99 - будет использовано значение 99. В режиме совместимости с версией 8.3.21 поведение не изменилось.

В диалоге настройки параметров информационной базы, выключение флажка Проверка сложности паролей пользователей не приводит к изменению значения параметра Минимальная длина паролей пользователей.

Метод УстановитьМинимальнуюДлинуПаролейПользователей() не накладывал ограничений на устанавливаемую минимальную длину паролей пользователей.

При получении значения параметра информационной базы Минимальная длина паролей пользователей платформа не контролирует полученное значение.

В диалоге настройки параметров информационной базы, выключение флажка Проверка сложности паролей пользователей приводило к установке параметра Минимальная длина паролей пользователей в значение 0.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства администрирования.
Для параметра IgnoreServerCertificatesChainRevocationSoftFail файла conf.cfg значение по умолчанию принимается равным Истина.Для параметра IgnoreServerCertificatesChainRevocationSoftFail файла conf.cfg значение по умолчанию принималось равным Ложь.Стало возможно установить HTTPS-соединение (без дополнительных настроек системы) в том случае, если недоступен один или несколько серверов со списками отзыва сертификатов.
В документации данное изменение описано здесь.
Веб-клиент.
Системные требования.
Прекращена поддержка веб-браузеров:
  • Microsoft Edge версии 18 и предшествующих.
  • Microsoft Internet Explorer 10.
При работе в веб-клиенте поддерживались следующие веб-браузеры:
  • Microsoft Edge версии 18 и предшествующих.
  • Microsoft Internet Explorer 10.
Исключена поддержка устаревших веб-браузеров.
В документации данное изменение описано здесь и здесь.
Веб-клиент.
Системные требования.
Средства разработки.
Реализована поддержка веб-браузера Microsoft Edge версии 19 (и последующие версии), работающего под управлением ОС Linux, macOS и Windows.

Реализована поддержка видеозвонков при использовании веб-браузера Microsoft Edge версии 64 и последующих версий.

Реализована поддержка прогрессивных веб-приложений при использовании веб-браузеров Яндекс.Браузер и Microsoft Edge версии 73 и последующих версий.

Реализована возможность отладки веб-клиента, работающего под управлением веб-браузеров Яндекс.Браузер и Microsoft Edge.

Данные возможности не предоставлялись.Расширен список поддерживаемых веб-браузеров.

Расширены возможности системы, которые можно использовать в веб-клиенте.

В документации данное изменение описано здесь, здесь, здесь и здесь.
Полнотекстовый поиск.
Для конфигурационного файла conf.cfg реализован параметр FtsJavaOpts, с помощью которого можно задать параметры работы виртуальной машины Java, которая используется полнотекстовым поиском 2-й версии.Данная возможность не предоставлялась.Реализована возможность управления параметрами виртуальной машины Java, которая используется версией 2 полнотекстового поиска.
В документации данное изменение описано здесь.
Внешние отчеты и обработки.
Для метода Подключить() менеджера внешних отчетов реализован параметр КодЯзыка. Параметр позволяет указать язык, который будет использоваться в подключаемой внешнего отчета в качестве текущего языка.Данная возможность не предоставлялась.

При подключении внешнего отчета использовался текущий язык аутентифицированного пользователя. Код этого языка возвращается методом глобального контекста ТекущийЯзык().

Реализована возможность открывать внешние отчеты на требуемом языке локализации.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
При импорте XSD-схемы в пакет XDTO, для свойств, чьи элементы входят в модель содержания choice (в описании XSD-схемы), в качестве значения нижней границы устанавливаются значения, определенные для этих элементов непосредственно в XSD-схеме.При импорте XSD-схемы в пакет XDTO, для свойств, чьи элементы входят в модель содержания choice (в описании XSD-схемы), в качестве значений нижней границы всегда устанавливались значения 0.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Английский вариант наименования метода РасчетСистемЛинейныхУравнений.РассчитатьСистемыЛинейныхУравнений().
  • SolveSystemOfLinearEquations.
  • SolveSystemsOfLinearEquations.
Англоязычные имена следующих параметров оформления системы компоновки данных:
  • МаксимальнаяВысота,
  • МаксимальнаяШирина,
  • МинимальнаяВысота,
  • МинимальнаяШирина.

Для обеспечения совместимости, при поиске параметра из встроенного языка и при загрузке из XML, будут использоваться и старые и новые имена параметров.

В режиме совместимости 8.3.21 и предыдущих, при выгрузке в XML будут использоваться старые имена параметров для английского варианта встроенного языка.. +

  • MaximumHeight,
  • MaximumWidth,
  • MinimumHeight,
  • MinimumWidth.
  • MaxHeight,
  • MaxWidth,
  • MinHeight,
  • MinWidth.
Английское имя свойства формы клиентского приложения ОписаниеОповещения.
  • NotifyDescription.
  • CallbackDescription.
Английский вариант имени метода глобального контекста ВыполнитьОбработкуОповещения.
  • ExecuteNotifyProcessing.
  • RunCallback.
Английское имя свойства формы клиентского приложения ОписаниеОповещенияОЗакрытии.
  • OnCloseNotifyDescription.
  • CallbackDescriptionOnClose.
Параметр конфигурационного файла conf.cfg, позволяющий задать параметры виртуальной машины Java для работы оптимизированного механизма реструктуризации.
  • JavaOpts
  • RestructJavaOpts

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильный клиент.
Для мобильного клиента с автономным режимом реализована возможность автоматической синхронизации данных с основным сервером. При редактировании состава данных автономной конфигурации имеется возможность указать, что объект участвует в автоматическом обмене и будет-ли выполняться регистрация изменений объекта для целей автоматического обмена. Реализован диалог настройки автоматического обмена с автономной конфигурацией.

Для модуля объекта плана обмена реализованы обработчики событий ПриАвтоматическомСозданииНовогоУзла(), ПередСозданиемНачальногоОбраза(), ПередНачаломОтправкиДанныхПодчиненному(), ПередНачаломОтправкиДанныхГлавному().

Для плана обмена реализован стандартный реквизит ДатаОбмена.

Реализовано свойство глобального контекста ОбменДаннымиСОсновнымСервером.

Реализован обработчик события модуля приложения ПослеОбменаДаннымиСОсновнымСервером().

Данная возможность не предоставлялась. Синхронизацию всегда требовалось реализовать на встроенном языке.Упрощена реализация обмена между мобильным клиентом с автономным режимом и основным сервером.
В документации данное изменение описано здесь, здесь и здесь.
Мобильная платформа.
Табличный документ.
В мобильной платформе реализована возможность просмотра табличного документа с помощью метода ТабличныйДокумент.Показать() или интерактивного открытия.Данная возможность не предоставлялась.В приложениях на мобильной платформе стало возможно просматривать табличные документы, полученные извне.
Мобильный клиент.
Для мобильного клиента с автономным режимом реализована возможность переводить звонок системы взаимодействия в фоновый режим. При переводе звонка в фоновый режим прекращается передача видеопотока с мобильного устройства. При работе под управлением ОС iOS данная возможность доступна начиная с версии 10. При работе под управлением ОС Android данная возможность доступна на всех поддерживаемых версиях.

Для мобильного клиента реализована возможность демонстрации экрана собственного устройства и просмотр демонстрации «чужого» экрана устройства с помощью видеопотока системы взаимодействия. Демонстрация работает также и в том случае, когда приложение не активно. При работе под управлением ОС iOS данная возможность доступна начиная с версии 12. При работе под управлением ОС Android данная возможность доступна на всех поддерживаемых версиях.

Для списка используемых функциональностей мобильного устройства реализована функциональность Видеоконференция.

При сворачивании приложения мобильного клиента, переходе в другое приложение или блокировке устройства участие в видеозвонке приостанавливалось.

Демонстрация экрана использовала другой протокол работы.

Стало возможно продолжать звонок при переходе мобильного приложения в фоновый режим. Реализована возможность передачи не только экрана мобильного приложения, но и экрана устройства. Повышена производительность работы при демонстрации экрана устройства.
Мобильный клиент.
Если при потере соединения с основным сервером, в мобильном клиенте с автономным режимом работы используется форма отчета, то:
  • В форме отчета не блокируется поле табличного документа. Настройки и команды формы отчета становятся недоступными.
  • Становятся доступными команды сохранения и печати отчета.
  • Расшифровка отчета в таком режиме не поддерживается.
  • При открытии автономной формы отчета, текущая форма отчета не закрывается. При выборе команды Открыть онлайн, оффлайн форма отчета закрывается.
  • Если отчет формируется в фоновом режиме на сервере, то при восстановлении соединения форма отчета отображает получившийся результат. Если формирование не завершено - форма отчета продолжает ожидать окончание формирования.
Если при потере соединения с основным сервером, в мобильном клиенте с автономным режимом работы используется форма отчета, то:
  • Вся форма отчета становилась недоступной для редактирования.
  • При открытии офлайн формы отчета закрывалась онлайн форма отчета.
При переходе мобильного клиента в автономный режим пользователю стало более комфортно работать с отчетом.

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Восстановлена возможность обработки звонков и SMS в мобильном приложении, собранном для работы под управлением ОС Android. Для восстановления работы необходимо повторно собрать мобильное приложение с использованием мобильной версию 8.3.22 и конфигурации, которая выгружена конфигуратором версии 8.3.22.

При необходимости следует указать поясняющие тексты для требуемой функциональности мобильного приложения.

Не выполнялась обработка звонков и SMS в мобильном приложении, собранном для работы под управлением ОС Android, несмотря на корректно указанную используемую функциональность мобильного приложения.Устранено некорректное поведение системы.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 14.4.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Обновление конфигурации базы данных.
Ускорено выполнение команды MergeCfg пакетного режима запуска конфигуратора. Время выполнения команды должно соответствовать времени интерактивного выполнения операции.Выполнение команды MergeCfg пакетного режима запуска конфигуратора требовало больше времени.Устранено некорректное поведение системы.
Работа с XML, XDTO.
Для объектов ОбъектXDTO и ЗначениеXDTO реализован метод Фабрика(), который возвращает объект типа ФабрикаXDTO, который использовался для создания используемого объекта или значения.

При работе с объектами XDTO (и записи их в XML) следует использовать один и тот же экземпляр фабрики для всех используемых объектов.

Данная возможность не предоставлялась.В случае необходимости, стало возможно получить объект ФабрикаXDTO, который использовался для создания объекта или значения XDTO.
В документации данное изменение описано здесь.
Системные требования.
Для платформы «1С:Предприятие» реализована поддержка 64-разрядной архитектуры процессоров ARM (включая процессоры Байкал).

Система «1С:Предприятие» для процессоров ARM не поддерживает:

  • Работу под управлением ОС Windows для процессоров ARM.
  • Использование ключей защиты HASP (поддерживается только программное лицензирование).
  • Процессоры Apple M1 и последующие.
  • Процессоры Эльбрус.
  • Использование дистрибутива тонкого клиента, собранного для процессоров ARM, в механизмах автоматического обновление клиентских приложений.
  • Работу с СУБД:
    • Microsoft SQL Server.
    • IBM Db2.

Реализовано значение системного перечисления ТипПлатформы.Linux_ARM_64.

Внесены изменения в технологию создания внешних компонент (см. здесь).

Использование системы «1С:Предприятие» для процессоров ARM требует наличие лицензии КОРП.

Система «1С:Предприятие» не поддерживала запуск на системах, работающих на процессорах ARM.Расширен список оборудования, на котором может функционировать система «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Внешние компоненты.
Веб-клиент.
Реализована поддержка расширений для работы с файлами и криптографией при использовании веб-браузеров Яндекс.Браузер, Chromium-gost и Microsoft Edge.

Изменена документация по технологии создания внешних компонент (см. здесь).

Установка манифестов расширений и адаптеров внешних компонент выполняется в следующие каталоги (ключи реестра):

  • ОС Linux:
    • ~/.config/yandex-browser/NativeMessagingHosts;
    • ~/.config/chromium-gost/NativeMessagingHosts;
    • ~/.config/chromium/NativeMessagingHosts;
    • ~/.config/microsoft-edge/NativeMessagingHosts.
  • ОС macOS:
    • /Library/Application Support/Chromium/NativeMessagingHosts.
  • ОС Windows (записывается информация о месте размещения файлов):
    • HKEY_CURRENT_USER\SOFTWARE\Chromium\NativeMessagingHosts;
    • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\NativeMessagingHosts.
При работе веб-клиента под управлением веб-браузеров Яндекс.Браузер, Chromium-gost и Microsoft Edge не поддерживалось использование расширений для работы с файлами и криптографией.

Установка манифестов расширений и адаптеров внешних компонент выполнялась в следующие каталоги (ключи реестра):

  • ОС Linux:
    • ~/.config/google-chrome/NativeMessagingHosts;
    • ~/.mozilla/native-messaging-hosts.
  • ОС macOS:
    • /Library/Application Support/Mozilla/NativeMessagingHosts;
    • /Library/Google/Chrome/NativeMessagingHosts.
  • ОС Windows (записывается информация о месте размещения файлов):
    • HKEY_CURRENT_USER\SOFTWARE\Google/Chrome\NativeMessagingHosts;
    • HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts.
Расширены возможности веб-клиента при работе под управлением веб-браузеров Яндекс.Браузер, Chromium-gost и Microsoft Edge.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 10.21,
  • Postgres Pro Standard 10.21.1,
  • Postgres Pro Enterprise 10.21.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 10.21,
  • Postgres Pro Standard 10.21.1,
  • Postgres Pro Enterprise 10.21.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 11.16,
  • Postgres Pro Standard 11.16.2,
  • Postgres Pro Enterprise 11.16.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 11.16,
  • Postgres Pro Standard 11.16.2,
  • Postgres Pro Enterprise 11.16.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 12.11,
  • Postgres Pro Standard 12.11.2,
  • Postgres Pro Enterprise 12.11.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 12.11,
  • Postgres Pro Standard 12.11.2,
  • Postgres Pro Enterprise 12.11.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 13.7,
  • Postgres Pro Standard 13.7.2,
  • Postgres Pro Enterprise 13.7.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 13.7,
  • Postgres Pro Standard 13.7.2,
  • Postgres Pro Enterprise 13.7.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 14.4,
  • Postgres Pro Standard 14.4.1,
  • Postgres Pro Enterprise 14.4.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 14.4,
  • Postgres Pro Standard 14.4.1,
  • Postgres Pro Enterprise 14.4.1.
Расширен список поддерживаемых СУБД.
Система взаимодействия.
Изменена схема хранения значений разделителей для некоторых объектов системы взаимодействия в распределенной информационной базе.

После перехода на версию 8.3.22 боты системы взаимодействия начнут работать после наступления одного из событий:

  • Подключение к базе клиентского приложения.
  • Обращение к системе взаимодействия со стороны кластера серверов.
Схема хранения значений разделителей для некоторых объектов системы взаимодействия была другой.Устранено некорректное поведение системы.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
В интерфейсе мобильного приложения, который используется для сканирования штрих-кода (при вызове метода СредстваМультимедиа.ПоказатьСканированиеШтрихКодов()), реализована возможность интерактивного управления работой подсветки камеры. Кнопка управления подсветки зависит от наличия на устройстве подсветки и датчика освещения. Состояние использования подсветки запоминается между сеансами работы.Данная возможность не предоставлялась.

Подсветка камеры включалась только автоматически, что не позволяло использовать подсветку в случаях, когда на устройстве не было датчика освещенности.

Упрощено сканирование штрих-кодов встроенными средствами (в условиях недостаточной освещенности) на устройствах, которые не обладают датчиком освещенности, но имеют подсветку камеры. +
Кластер серверов.
Ускорено выполнение административных операций через сервер администрирования (ras).

Уменьшена частота и длительность периодов, когда соединения от сервера администрирования могут конфликтовать с монопольным доступом к информационной базе. +

Выполнение административных операций через сервер администрирования (ras) занимало больше времени.

Соединение с кластером серверов, которое установлено сервером администрирования (ras) могло чаще конфликтовать с монопольным доступом к информационной базе.

Ускорены операции по администрирования кластера серверов через сервер администрирования (ras).
Автономный сервер.
Для SSH-шлюза автономного сервера реализованы следующие команды:
  • config dump-external-data-processor-or-report-to-files - выгрузить в XML-файлы внешнюю обработку/отчет.
  • config load-external-data-processor-or-report-to-files - загрузить из XML-файлов внешнюю обработку/отчет.

Для команд infobase config export реализован параметр --file для указания размещения файла внешней обработки или конфигурации. +Для команд infobase config import реализован параметр --out для указания размещения файла внешней обработки или конфигурации.

Данные возможности не предоставлялись.Расширены возможности автономного сервера в части работы с внешними отбработками и отчетами.
В документации данное изменение описано здесь.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 10.22.1,
  • Postgres Pro Standard 10.22.1,
  • Postgres Pro Enterprise 10.22.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 10.22.1,
  • Postgres Pro Standard 10.22.1,
  • Postgres Pro Enterprise 10.22.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 11.17.1,
  • Postgres Pro Standard 11.17.1,
  • Postgres Pro Enterprise 11.17.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 11.17.1,
  • Postgres Pro Standard 11.17.1,
  • Postgres Pro Enterprise 11.17.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 12.12.1,
  • Postgres Pro Standard 12.12.1,
  • Postgres Pro Enterprise 12.12.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 12.12.1,
  • Postgres Pro Standard 12.12.1,
  • Postgres Pro Enterprise 12.12.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 13.8.1,
  • Postgres Pro Standard 13.8.1,
  • Postgres Pro Enterprise 13.8.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 13.8.1,
  • Postgres Pro Standard 13.8.1,
  • Postgres Pro Enterprise 13.8.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 14.5.1,
  • Postgres Pro Standard 14.5.1,
  • Postgres Pro Enterprise 14.5.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 14.5.1,
  • Postgres Pro Standard 14.5.1,
  • Postgres Pro Enterprise 14.5.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа в ОС Linux.
Реализована поддержка следующих дистрибутивов операционной системы Linux:
  • Debian 11,
  • Mint 21,
  • Oracle Linux 9,
  • RHEL 9,
  • Ubuntu 22.04 LTS.
Данные дистрибутивы не поддерживались.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Системные требования.
Работа в ОС Linux.
Прекращена поддержка следующих дистрибутивов операционной системы Linux:
  • Debian 9.
Система «1С:Предприятие» поддерживала работу в следующих дистрибутивах операционной системы Linux::
  • Debian 9.
Прекращена поддержка устаревших дистрибутивов операционной системы Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Мобильные приложения, собранные с использованием мобильной версии 8.3.22.40, будут удовлетворять требованиям магазина приложений Google в части загрузки новых приложений, использующих механизм встроенных покупок.

Для того, чтобы загрузить мобильное приложение в магазин Google Play, необходимо собрать мобильное приложение с использованием мобильной версии 8.3.22.40 или последующих.

Мобильные приложения, которые используют механизм встроенных покупок и собранные с использованием мобильных версий, предшествующих версии 8.3.22.40, будет невозможно загрузить в магазин Google Play после 1 ноября 2022 года.Мобильная версия системы «1С:Предприятие» удовлетворяет требованиям магазина приложений Google Play.
Мобильная платформа.
Мобильный клиент.
Расширен список поддерживаемых корневых сертификатов.Список поддерживаемых корневых сертификатов был меньшего размера.Расширен список поддерживаемых корневых сертификатов.
Автономный сервер.
Оптимизировано завершение работы автономного сервера.Завершение работы автономного сервера требовало больше времени.Ускорен перезапуск автономного сервера после выполнения операции обновления конфигурации информационной базы.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Обновлены версии библиотек статистики для мобильной платформы и мобильного клиента.Мобильная платформа и мобильный клиент содержали устаревшие версии библиотек статистики.Обновлены версии библиотек статистики для соответствия требованиям магазина Google Play.
Системные требования.
Для платформы «1С:Предприятие» реализована поддержка процессоров Эльбрус (процессоры Эльбрус-8С).

Система «1С:Предприятие» для процессоров Эльбрус не поддерживает:

  • Работу под управлением ОС Windows для процессоров Эльбрус.
  • Использование ключей защиты HASP (поддерживается только программное лицензирование).
  • Использование дистрибутива тонкого клиента, собранного для процессоров Эльбрус, в механизмах автоматического обновления клиентских приложений.
  • Работу с СУБД:
    • IBM Db2.
    • Microsoft SQL Server.
    • Oracle.
    • Дата акселератор.
  • Локальное распознавание речи.

Реализовано значение системного перечисления ТипПлатформы.Linux_E2K.

Внесены изменения в технологию создания внешних компонент (см. здесь).

Использование системы «1С:Предприятие» для процессоров Эльбрус требует наличие лицензии КОРП.

Система «1С:Предприятие» не поддерживала запуск на системах, работающих на процессорах Эльбрус.Расширен список оборудования, на котором может функционировать система «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована возможность работы с СУБД Microsoft SQL Server 2022.СУБД Microsoft SQL Server 2022 не поддерживалась.Реализована поддержка новой версии СУБД компании Microsoft.
В документации данное изменение описано здесь и здесь.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 10.23.1,
  • Postgres Pro Standard 10.23.1,
  • Postgres Pro Enterprise 10.23.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 10.23.1,
  • Postgres Pro Standard 10.23.1,
  • Postgres Pro Enterprise 10.23.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 11.18.1,
  • Postgres Pro Standard 11.18.1,
  • Postgres Pro Enterprise 11.18.2.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 11.18.1,
  • Postgres Pro Standard 11.18.1,
  • Postgres Pro Enterprise 11.18.2.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 12.13.1,
  • Postgres Pro Standard 12.13.1,
  • Postgres Pro Enterprise 12.13.2.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 12.13.1,
  • Postgres Pro Standard 12.13.1,
  • Postgres Pro Enterprise 12.13.2.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 13.9.1,
  • Postgres Pro Standard 13.9.1,
  • Postgres Pro Enterprise 13.9.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 13.9.1,
  • Postgres Pro Standard 13.9.1,
  • Postgres Pro Enterprise 13.9.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 14.6.1,
  • Postgres Pro Standard 14.6.1,
  • Postgres Pro Enterprise 14.6.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 14.6.1,
  • Postgres Pro Standard 14.6.1,
  • Postgres Pro Enterprise 14.6.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 15.1.1,
  • Postgres Pro Standard 15.1.1,
  • Postgres Pro Enterprise 15.1.1.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 15.1.1,
  • Postgres Pro Standard 15.1.1,
  • Postgres Pro Enterprise 15.1.1.
Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 10.22.

Поддерживаемые версией СУБД архитектуры процессоров: x86, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 11.17.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 12.12.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 13.8.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 14.5.

Поддерживаемые версией СУБД архитектуры процессоров: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 10.23.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 11.18.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 12.13.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 13.9.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 14.6.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 15.1.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 11.19.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.14.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 12.14.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 13.10.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 14.7.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL следующих версий: 15.2.

Поддерживаемые версией СУБД архитектуры процессоров: ARM64, E2k, x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.18.

Поддерживаемые операционные системы: определяются производителем СУБД.

Данные версии СУБД PostgreSQL не поддерживались.Расширен список поддерживаемых СУБД.
Работа с Интернет.
При использовании объектов HTTPСоединение, WSОпределения, WSПрокси и WSСсылки в операционных системах Linux и macOS реализована возможность использовать аутентификацию Kerberos. Данная возможность реализована в толстом клиенте и на стороне сервера.При использовании объектов HTTPСоединение, WSОпределения, WSПрокси и WSСсылки в операционных системах Linux и macOS не поддерживалась возможность использования аутентификации Kerberos. Данный вид аутентификации поддерживался только при работе под управлением ОС Windows.При использовании объектов HTTPСоединение, WSОпределения, WSПрокси и WSСсылки в операционных системах Linux и macOS реализована возможность использовать аутентификацию Kerberos.
Полнотекстовый поиск.
Оптимизировано выполнение полнотекстового поиска. Снижена нагрузка на процессор во время выполнения поиска.Полнотекстовый поиск требовал больше времени на нахождение результата и существенно нагружал процессор.Оптимизировано выполнение полнотекстового поиска.
Работа с файлами.
Исполнении методов НачатьПомещениеФайла(), НачатьПомещениеФайлов(), НачатьПомещениеФайлаНаСервер(), НачатьПомещениеФайловНаСервер(), ПоместитьФайлНаСерверАсинх (), ПоместитьФайлыНаСерверАсинх() в толстом клиенте выполняется в основном потоке, но остается асинхронным. В результате, при выполнении данных методов, блокируется обновление пользовательского интерфейса, но сохраняется программный интерфейс работы методов.Исполнении методов НачатьПомещениеФайла(), НачатьПомещениеФайлов(), НачатьПомещениеФайлаНаСервер(), НачатьПомещениеФайловНаСервер(), ПоместитьФайлНаСерверАсинх (), ПоместитьФайлыНаСерверАсинх() в толстом клиенте могло приводить к аварийному завершению работы приложения.Устранено некорректное поведение системы.
Средства администрирования.
Установка клиентского приложения.
Работа в ОС Linux.
Для ОС Linux реализована возможность установки системы «1С:Предприятие» с помощью rpm- и deb-пакетов. В пакетах поставляются все компоненты системы. Установка и удаление выполняется с помощью пакетного менеджера используемой операционной системы.

Для файл conf.cfg реализованы параметры PublishDistributiveLocationLinuxDeb64, PublishDistributiveLocationLinuxDeb32, PublishDistributiveLocationLinuxRpm64, PublishDistributiveLocationLinuxRpm32.

Для элемента point файла default.vrd реализованы атрибуты pubdstlindeb32, pubdstlindeb64, pubdstlinrpm32, pubdstlinrpm64.

Для параметра pubdst секции http конфигурационного файла автономного сервера реализованы параметры lindeb64, lindeb32, linrpm64, linrpm32.

Поддержка установки с помощью run-файлов (программа установки) не прекращается и будет существовать одновременно с файлами пакетов.

Приложения системы «1С:Предприятие» поставлялись в виде run-пакетов.Расширены возможности установки компонентов системы «1С:Предприятие» для ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Средства разработки.
Реализована возможность включать отладку по протоколу HTTP в том случае, если для кластера серверов системы «1С:Предприятие» настроен автоматический запуск при работе под управлением ОС Linux. Для включения протокола отладки необходимо использовать параметр SRV1CV8_DEBUG конфигурационного файла кластера серверов.Если в ОС Linux настроен автоматический запуск кластера серверов «1С:Предприятие» при старте операционной системы, то в этом случае не поддерживалось использование протокола отладки HTTP (поддерживался только протокол откладки TCP).Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Системные требования.
Работа с СУБД.
Web-сервисы и HTTP-сервисы.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 11.18.1,
  • Postgres Pro Standard 11.18.1,
  • Postgres Pro Enterprise 11.18.2.

Разрядность версий СУБД: x86-64.

Поддержка реализована, начиная с версии «1С:Предприятие»: 8.3.16.

Поддерживаемые операционные системы: определяются производителем СУБД.

+

Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 11.18.1,
  • Postgres Pro Standard 11.18.1,
  • Postgres Pro Enterprise 11.18.2.
Расширен список поддерживаемых СУБД.
Регистры бухгалтерии.
При работе с регистром бухгалтерии:
  • Оптимизирован запрос, выполняемый в случае использования отбора по субконто в параметре Отбор виртуальных таблиц регистра бухгалтерии, а также при незаданном параметре ВидыСубконто.
  • Оптимизирован запрос, выполняемый в случае использования в виртуальных таблицах отборов по диапазону дат, включая уточнение периода.
Некоторые запросы к регистру бухгалтерии работали не оптимально.Ускорено получение данных из регистра бухгалтерии.
Распределенные информационные базы.
При работе с механизмом распределенной информационной базы, объекты выгружаются в файл изменений в следующем порядке:
  • Константы;
  • Планы видов характеристик;
  • Планы счетов;
  • Планы видов расчета;
  • Справочники;
  • Прочие ссылочные объекты информационной базы (без определения порядка следования);
  • Наборы записей регистров (без определения порядка следования);
  • Записи регистров расчета;
  • Данные последовательностей.
При работе с механизмом распределенной информационной базы, порядок выгрузки объектов в файл изменений был не определен.Определение порядка обмена позволит снизить количество не консистентных состояний информационной базы во время обмена (до его завершения).
Тестирование и исправление информационной базы.
При выполнении тестирования и исправления информационной базы реализована возможность детализировать операции проверки логической и ссылочной целостности информационной базы по видам объектов (константы, справочники, документы и т.д.). Вне зависимости от выбранного набора видов объектов, некоторые проверки будут всегда выполняться для всех видов объектов (как и ранее).

Для параметров -LogIntegrity и -LogAndRefsIntegrity команды /IBCheckAndRepair реализованы следующие значения параметров:

  • Constants - констант;
  • Catalogs - справочников;
  • Documents - документов;
  • DocumentJournals - журналов документов;
  • ChartsOfCharacteristicTypes - планов видов характеристик;
  • ExchangePlans - планов обмена;
  • ChartsOfAccounts - планов счетов;
  • ChartsOfCalculationTypes - планов видов расчета;
  • InformationRegisters - регистров сведений;
  • AccumulationRegisters - регистров накопления;
  • AccountingRegisters - регистров бухгалтерии;
  • CalculationRegisters - регистров расчета;
  • BusinessProcesses - бизнес процессов;
  • Tasks - задач;
  • Other - других объектов.

+

Данная возможность не предоставлялась.Стало возможно выполнять проверки логической и ссылочной целостности информационной базы точечно, только по необходимым видам объектов.
В документации данное изменение описано здесь и здесь.
Внешние компоненты.
При подключении и установке внешней компоненты (с помощью методов ПодключитьВнешнююКомпоненту(), УстановитьВнешнююКомпоненту() или ПодключитьВнешнююКомпонентуАсинх()), файл компоненты будет кешироваться как и ранее, но для компонент, которые были подключены из данных в информационной базе, будет отслеживаться изменение данных. Проверка выполняется при подключении компоненты, но не чаще 1 раза в секунду. Если данные были изменены с момента последнего подключения компоненты, для этой компоненты будет очищаться кеш внешних компонент, и, при следующем подключении компоненты, компонента будет извлечена из данных заново. Для объектов метаданных, не имеющих версию записи, очистка кеша будет осуществляться при обращении за данными, но не чаще 1 раза в секунду.При подключении и установке внешней компоненты (с помощью методов ПодключитьВнешнююКомпоненту(), УстановитьВнешнююКомпоненту() или ПодключитьВнешнююКомпонентуАсинх()), файл компоненты кешировался во временном каталоге на сервере для повышения производительности при повторном использовании компоненты, однако, до перезапуска клиентского приложения было невозможно понять, что версия компоненты в кеше стала отличаться от версии компоненты в информационной базе (если компонента получалась из информационной базы).Улучшено управление внешними компонентами.
В документации данное изменение описано здесь.
Кластер серверов.
Системные требования.
Работа в ОС Linux.
Использование кластера серверов при работе под управлением ОС Linux всегда требует серверную лицензию, аналогично поведению под управлением ОС Windows.Кластер серверов под управлением ОС Linux позволял запускать до 12 клиентских сеансов без лицензии на сервер, если кластер серверов состоял из одного рабочего сервера с одним рабочим процессом.Устранена возможность нелицензионного использования кластера серверов под управлением ОС Linux. Устранено неожиданное прекращение работы системы из-за отсутствия лицензии на кластер серверов «1С:Предприятия».
Средства печати.
Работа с HTML.
В тонком и толстом клиентских приложениях реализовано сохранение настроек печати для поля HTML-документа в системном хранилище настроек. Настройки сохраняются при изменении настроек в диалоге параметров печати для поля HTML-документа, а читаются перед открытием диалога параметров печати и при печати/предварительном просмотре поля HTML-документа.Данная возможность не предоставлялась.

Печать всегда выполнялась с настройками по умолчанию.

Печатать данные из поля HTML-документа стало удобнее за счет того, что будут использовать ранее указанные настройки и не придется выполнять эти настройки каждый раз заново.
В документации данное изменение описано здесь.
Клиентское приложение.
Для команды командной строки запуска тонкого клиента /TComp реализованы параметры lz4 и zstd определяющие режимы сжатия трафика между клиентом и кластером серверов. Значением по умолчанию является параметр zstd.Параметром, определяющим сжатие трафика по умолчанию, являлся параметр -SDC.Реализована возможность более гибкого управления сжатием трафика между клиентским приложением и кластером серверов платформу «1С:Предприятие».

При использовании режима сжатия -zstd снижается объем трафика, который передается между клиентом и кластером серверов «1С:Предприятия».

В документации данное изменение описано здесь.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 16 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
В документации данное изменение описано здесь.
Средства администрирования.
В файлы cacert.pem и cacertnx.pem добавлены корневые сертификаты Министерства цифрового развития, связи и массовых коммуникаций Российской Федерации, сформированные с использованием алгоритмов ГОСТ Р 34.11-2012.Данная возможность не предоставлялась.Снижается количество ошибок проверки сертификатов при доступе к сайтам российского сегмента сети Интернет.
Локализация.
Реализована локализация интерфейса клиентского приложения для португальского (Бразилия) языка (код pt_BR).Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» пользователями, говорящими на бразильском диалекте португальского языке.
В документации данное изменение описано здесь и здесь.
Установка клиентского приложения.
При установке клиентского приложения, при обновлении по протоколу HTTP или из самораспаковывающегося архива прикладного решения (созданного утилитой 1CEClientSetupMake) под управлением ОС Windows 8.1 и предшествующих версий, реализовано предупреждение о невозможности проверить подпись программы установки и что установка выполняется под управлением устаревшей версии с возможностью отказаться от установки.

При установке клиентского приложения (при обновлении по протоколу HTTP) под управлением ОС Windows 8.1 и предшествующих версий, дополнительно реализована возможность отключить проверку подписи новой версии программы установки клиентского приложения. Флажок запоминается в параметре DisableInstallerVerification конфигурационного файла 1cestart.cfg.

При установке клиентского приложения, при обновлении по протоколу HTTP или из самораспаковывающегося архива прикладного решения (созданного утилитой 1CEClientSetupMake) под управлением ОС Windows 8.1 и предшествующих версий, установка клиентского приложения не могла быть выполнена из-за невозможности проверки цифровой подписи программы установки.Упрощено диагностика ситуации, которая возникает при попытке установить актуальные версии клиентского приложения под управлением устаревших операционных систем семейства Windows (версия 8.1 и предшествующие версии).
В документации данное изменение описано здесь.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 17 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.

Оглавление

Переход с предыдущей версии на версию 8.3.22

Оглавление

Версия 8.3.21

Версия 8.3.21 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8321doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.20.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.19. +Возможность запуска конфигураций, разработанных в версии 8.3.20 и более младших, в версии 8.3.21, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.21 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.21, при необходимости, использовать для работы с информационной базой и версию 8.3.20. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность получения навигационной ссылки на объект или запись текущей строки динамического списка без необходимости открывать форму объекта/записи.

Реализовано свойство расширения таблицы формы для динамического списка РазрешитьПолучатьНавигационнуюСсылкуТекущейСтроки. Для расширения таблицы формы для динамического списка реализованы обработчики событий ОбработкаПолученияСпискаНавигационныхСсылок и ОбработкаПолученияНавигационнойСсылки.

Диалог получения навигационной ссылки формы переработан с учетом данной возможности.

В диалоге получения навигационной ссылки на начальной странице отображаются все варианты ссылок, полученные у всех форм на начальной странице.

Возможность получения навигационной ссылки на объект или запись текущей строки динамического списка без необходимости открывать форму объекта/записи была недоступна.

На начальной странице было недоступно получение навигационной ссылки любой формы начальной страницы из одного диалога.

Улучшен и упрощен интерфейс получения навигационной ссылки в динамическом списке и на начальной странице.
В документации данное изменение описано здесь и здесь.
Выгрузка/загрузка конфигурации в файлы.
Автономный сервер.
Средства разработки.
Реализована возможность выгрузки конфигурации в zip-архив xml-файлов. При выгрузке на стороне кластера серверов реализована возможность многопоточной выгрузки конфигурации.

Команда Конфигуратора Выгрузить конфигурацию в файлы позволяет указать способ выгрузки (на сервере/на клиенте), количество одновременных потоков выгрузки и необходимость архивировать файл выгрузки.

Для выполнения данной задачи реализован специальный параметр для следующих инструментов загрузки:

  • Командная строка запуска конфигуратора. Для команды /DumpConfigToFiles реализован параметр -Server, -Archive, -JobsCount.
  • Конфигуратор в режиме агента. Для команды config dump-config-to-files реализованы параметры --archive, --server, --threads.
  • Утилита управления автономным сервером (ibcmd). Для команды infobase config export реализованы параметры --archive, --server, --threads.
Данная возможность не предоставлялась.Стало возможно существенно ускорить выгрузку конфигурации в xml-файлы. В том случае, если планируется передача выгрузки на другой компьютер, можно сразу упаковать файлы выгрузки в zip-архив.
В документации данное изменение описано здесь, здесь и здесь.
Отображение информации.
В библиотеку картинок добавлены следующие картинки:
  • ПовернутьПоЧасовойСтрелке;
  • ПовернутьПротивЧасовойСтрелки.
В библиотеке картинок отсутствовали добавленные картинки. Расширен состав библиотеки картинок.
Работа с PDF-документами.
Реализована возможность просмотра и печати документов PDF средствами платформы «1С:Предприятие». Поддерживается просмотр и проверка подлинности электронных подписей документа. Поддерживается работа с зашифрованными документами. Текущие ограничения описаны в документации.

Реализован объект ДокументPDF. Реализован вид поля формы клиентского приложения ПолеPDFДокумента.

Реализованы методы глобального контекста ДокументЗащищенПаролем(), ДокументЗащищенПаролемАсинх().

Для объекта КоллекцияВложенийPDF реализованы методы: Очистить(), Удалить().

Для системного перечисления ТипФайлаДокументаPDF реализованы свойства PDF, PDF_A_1, PDF_A_2, PDF_A_3.

Для системного перечисления КатегорияОшибки реализованы свойства НеправильныйПароль и ОшибкаПроверкиПодписи.

Данная возможность не предоставлялась.

Предоставлялась возможность только формировать документы PDF.

Расширены возможности работы с документами PDF.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с Интернет.
Для объекта HTTPСоединение реализована возможность использования клиентских сертификатов с поддержкой алгоритмов ГОСТ. Реализована поддержка КриптоПРО CSP при работе под управлением ОС Linux и macOS.

Для конфигурационного файла conf.cfg реализован параметр CryptoAPILibraryLocation.

Реализованы объекты СертификатКлиентаLinux, СпособВыбораСертификатаОС, СертификатКлиентаОС.

Конструктор объекта ЗащищенноеСоединениеOpenSSL может принимать объект СертификатКлиентаОС в качестве значения своего параметра СертификатКлиента.

Не поддерживалось использование клиентских сертификатов с поддержкой использования алгоритмов ГОСТ.Расширен список используемых видов сертификатов при работе с объектом HTTPСоединение.
В документации данное изменение описано здесь и здесь.
Форма клиентского приложения.
Реализована возможность отображения диаграммы Ганта совместно с таблицей, которая содержит дополнительные данные для значений диаграммы.

Реализовано расширение таблицы формы для диаграммы Ганта.

Для объекта ДиаграммаГанта реализовано свойство КолонкиДанных и метод НайтиЗначениеПоИдентификатору().

Для расширения поля формы для диаграммы Ганта реализовано свойство ПоложениеТаблицы.

Для объекта ЗначениеДиаграммыГанта реализованы свойства Идентификатор и Данные.

Для объекта ОбластьПостроенияДиаграммыГанта реализованы свойства ОтображатьТекстТочек и ОтображатьДанные. +Для объекта ПолеФормы реализовано свойство Таблица.

Данная возможность не предоставлялась. Диаграмма Ганта могла отображать только имена точек, которые созданы для серий диаграммы.Расширены возможности применения диаграммы Ганта.
В документации данное изменение описано здесь и здесь.
Копии базы данных.
Реализован новый механизм обновления копии базы данных при использовании стандартной репликации. Этот механизм использует специализированные средства СУБД основной базы данных. Новый механизм используется только для СУБД Microsoft SQL Server, в которой используется механизм записи изменений.

Для объекта МенеджерКопийБазыДанных реализованы методы ПолучитьВерсиюСтандартнойРепликации() и УстановитьВерсиюСтандартнойРепликации().

Данная возможность не предоставлялась.При использовании нового механизма обновления копии базы данных повышается скорость обновления копии базы данных.
В документации данное изменение описано здесь.
Работа с Интернет.
Реализована возможность использовать JWT-токен (стандарт RFC 7519) для авторизации в Интернет-сервисах платформы «1С:Предприятие». Также реализована возможность создания и проверки подписи JSON Web Signature (JWS).

Реализован объект ТокенДоступа.

Для объекта HTTPЗапрос реализован метод ДобавитьТокенДоступа(). Для объекта ПользовательИнформационнойБазы реализовано свойство АутентификацияТокеномДоступа.

Для файла defaul.vrd реализован элемент <accessTokenAuthentication>.

Для командной строки запуска тонкого клиента и веб-клиента реализованы команды /AccessToken.

Данная возможность не предоставлялась.Расширены возможности работы и повышена безопасность использования Интернет-сервисов.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Обработка ошибок.
В диалоге, который возникает при ошибках подключения к информационной базе, реализована возможность отображения информации, которая упростит (для пользователя) понимание причины ошибки и к кому следует обращаться в случае возникновения этой ошибки.

Реализован объект НастройкиОбработкиОшибокПриЗапуске. Для объекта МенеджерОбработкиОшибок реализованы методы УстановитьНастройкиОбработкиОшибокПриЗапуске() и ПолучитьНастройкиОбработкиОшибокПриЗапуке().

Для параметров подключения к информационной базы, которые описываются в файле *.v8i реализован параметр StartupErrorHelpURL и StartupErrorHelpText.

Данная возможность не предоставлялась.

Имелась возможность разместить ссылку на вспомогательную информацию только в диалоге ввода имени и пароля пользователя.

Упрощено восприятие ошибок подключения клиентского приложения к информационной базе.
В документации данное изменение описано здесь и здесь.
Командный интерфейс.
Реализована возможность при выборе подсистемы исполнять единственную команду этой подсистемы.

Для объекта метаданных Подсистема реализовано свойство ИспользоватьОднуКоманду.

Данная возможность не предоставлялась.Упрощено использование прикладного решения, когда в подсистеме присутствует только одна команда, доступная пользователю.
В документации данное изменение описано здесь.
Веб-клиент.
Работа с Интернет.
В веб-клиенте реализована возможность работы с HTTP-запросами. Предоставляемые возможности ограничены возможностями веб-браузеров.

В веб-клиенте реализована доступность объектов HTTPСоединение, HTTPЗапрос, HTTPОтвет и ЗащищенноеСоединениеOpenSSL. В веб-клиенте не поддерживаются синхронные методы объектов.

Данная возможность не предоставлялась.Расширены возможности веб-клиента в части работы с ресурсами сети Интернет.
Работа с Интернет.
В клиентских приложениях (тонкий, мобильный, толстый и веб-клиенты) реализована возможность асинхронного использования HTTP-запросов.

Для объекта HTTPСоединение реализованы методы ВызватьHTTPМетодАсинх(), ЗаписатьАсинх(), ИзменитьАсинх(), ОтправитьДляОбработкиАсинх(), ПолучитьАсинх(), ПолучитьЗаголовкиАсинх() и УдалитьАсинх().

Методы ВызватьHTTPМетод(), Записать(), Изменить(), ОтправитьДляОбработки(), Получить(), ПолучитьЗаголовки() и Удалить() объекта HTTPСоединение объявлены устаревшими при работе на стороне клиентских приложений и их работа поддерживается для совместимости. Указанные методы доступны только на стороне серверных приложений.

Асинхронное исполнение HTTP-запросов не поддерживалось системой «1С:Предприятие». Можно было только указывать только тайм-аут выполнения запросов.Реализована возможность выполнять асинхронный обмен с различными ресурсами, доступными в сети Интернет.
В документации данное изменение описано здесь.
Расширение конфигурации.
Общие реквизиты / Разделение данных.
Реализована возможность включать собственные объекты расширения в состав заимствованных общих реквизитов, которые являются разделителями.

Реализована возможность устанавливать расширения, расширяющие данные, одновременно как для всей информационной базы, так и для конкретной области данных.

Не поддерживалась возможность включения собственных объектов расширения в состав заимствованных общих реквизитов.

Расширение, расширяющее данные, могло быть установлено или в конкретной области данных или для информационной базы целиком. Одновременная установка таких расширений не поддерживалась.

Расширение конфигурации стало предоставлять больше возможностей.
В документации данное изменение описано здесь, здесь и здесь.
Прикладные объекты.
Динамический список.
Система компоновки данных.
При настройке характеристик объектов конфигурации реализована возможность указать, что характеристика может содержать более одного значения. Реализована поддержка этой возможности в системе компоновки данных и динамическом списке.

Для объекта ОписаниеХарактеристик реализованы свойства ПолеИспользованияМножественныхЗначений, ПолеКлючаМножественныхЗначений. ПолеПорядкаМножественныхЗначений.

Если в информационной базе указаны множественные характеристики, то при переходе на предыдущие версии платформы, данные в результате компоновки данных могут «задваиваться». В связи с этим не рекомендуется использовать предыдущие версии системы «1С:Предприятие» после указания множественных значений характеристик.

Характеристики объектов не поддерживали возможность задания более одного значения.Стало возможно указать множественные значения характеристик там, где они есть в реальном мире. Например, диапазоны частот WiFi, используемый материал товара и т.д.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
Для видеозвонков системы взаимодействия реализована возможность создания нового обсуждения во время видеозвонка. Состав участников обсуждения заполняется из состава участников текущего видеозвонка.

В окне видеозвонка, для кнопки Перейти к обсуждению, реализовано подменю из команд Перейти к обсуждению и Новое обсуждение для видеозвонка.

Перейти к обсуждению во время видеозвонка можно было только в том случае, если видеозвонок начинался из какого-либо обсуждения. Если видеозвонок начинался из меню системы взаимодействия, то для обмена текстовой информацией по теме обсуждения было необходимо вручную создать новое обсуждение и добавить в него всех участников звонка.Во время видеозвонка стало возможно быстро создать (и перейти при необходимости) в текстовый чат, связанный с текущим видеозвонком.
Обработка ошибок.
В диалоге формирования отчета об ошибке реализована возможность просмотра окна О программе.Данная возможность не предоставлялась.При формировании отчета об ошибке стало возможно уточнить информацию о том, в каком окружении произошла ошибка (версия прикладного решения и платформы, режим подключения, пользователь, имя информационно базы и т.д.).
Обработка ошибок.
Веб-клиент.
Если подключение к информационной базе выполняется веб-клиентом по протоколу HTTPS, в эту информационную базу с данного компьютера уже были успешные входы и используемый веб-браузер поддерживает технологию service-worker, то при ошибке подключения будет показана специальная страница (по аналогии со страницей выхода). Эта страница будет отображать информацию об ошибке подключения и различную вспомогательную информацию. Таким образом, страница будет функционально идентична форме ошибки подключения в тонком клиенте, но реализация будет соответствовать специфике веб-приложений.Данная возможность не предоставлялась.Ошибка подключения к информационной базе по протоколу HTTPS приведена в соответствие со спецификой отображения ошибок в веб-приложениях.
Система взаимодействия.
При работе через видео-сервер повышено качество изображения в видеозвонке, когда установлен режим отображения говорящего абонента.

При работе через видео-сервер снижена нагрузка на клиентский компьютер в том случае, когда в групповом видеозвонке все абоненты отображаются в виде галереи.

При работе через видео-сервер, когда во время видеозвонка установлен режим отображения говорящего абонента, качество изображения было недостаточно высоким.

При работе через видео-сервер наблюдалась высокая нагрузка на клиентский компьютер в том случае, когда в групповом видеозвонке все абоненты отображаются в виде галереи.

Повышено качество видеозвонков через видео-сервер.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Форма клиентского приложения.
Оптимизирована передача табличных частей с сервера на клиент в форме клиентского приложения. В случае, если на сервере выполняется изменение строк табличной части, на клиента передаются строки, которые состоят только из измененных колонок. Передаются изменения только тех строк, которые ранее переданы на сторону клиента. Передача осуществляется порциями по 35 строк (или менее). Если на сервере изменено более 105 строк (3 порции по 35 строк), то после передачи трех порций по 35 строк в каждой, выполняется передача на клиента всех строк табличной части. При открытии формы на клиента всегда передается не более 35 строк.При открытии формы на клиент передавалась только отображаемая часть табличной части. При любом изменении табличной части на сервере, на клиент передавалась вся табличная часть. При большом размере табличной части это могло приводить к большим временным затратам, а в некоторых случаях и к ошибкам времени исполнения.Повышается скорость реакции формы клиентского приложения в тех случаях, когда в большой табличной части на сервере (за один вызов) выполняется изменение небольшого количества строк.
Кластер серверов.
Оптимизировано использование кеша рабочего процесса: в кеше дольше хранятся часто используемые объекты и быстрее удаляются редко используемые объекты. Снижено потребление памяти рабочим процессом, повышена стабильность работы, снижена вероятность перезапуска рабочих процессов кластера по превышению порога допустимой памяти.Кеш рабочего процесса кластера серверов имел другую схему использования. Это, в частности, могло приводить к повышенному потреблению оперативной памяти рабочим процессом.Снижено потребление памяти рабочим процессом, повышена стабильность работы, снижена вероятность перезапуска рабочих процессов кластера по превышению порога допустимой памяти.
Общие объекты.
Оптимизирована установка значений в объекте типа ТаблицаЗначений в том случае, если колонка, в которую устанавливается значение, участвует в индексе, созданном для таблицы значений. К операциям, которые стали требовать меньше времени, можно отнести (не ограничиваясь этим списком):
  • Установка значения в колонку.
  • Копирование таблицы значений.
Установка значения в колонку объекта типа ТаблицаЗначений, которая участвовала в индексе, занимало очень много времени.Снижены временные затраты при изменении значений в колонках объекта типа ТаблицаЗначений, которые участвуют в индексах, построенных для таблицы значений.
Полнотекстовый поиск.
Оптимизирован полнотекстовый поиск по началу слова. Оптимизация проявляется при выполнении полнотекстового поиска из встроенного языка с указанием строки поиска вида «поис*» или в использовании поля глобального поиска.Полнотекстовый поиск по началу слова занимал больше времени.Повышена скорость полнотекстового поиска в данных.
Объекты метаданных.
Оптимизирована работа с прикладным решением, которое содержит большое количество объектов метаданных, в том числе оптимизировано:
  • Выражение языка запросов Значение(ИдентификаторПеречисления).
  • Работа пользователя с большим количеством ролей.
Скорость работы с прикладным решением, содержащим большое количество объектов метаданных, была недостаточно высокой.Ускорена работа прикладных решений с большим количеством объектов метаданных.
Табличный документ.
В тонком клиенте оптимизировано отображение табличного документа, который содержит большое количество объединенных ячеек и большое количество колонок.В тонком клиенте отображение табличного документа, который содержит большое количество объединенных ячеек и большое количество колонок, требовало много времени.Ускорено отображение табличных документов со сложной структурой.
Средства разработки.
При попытке просмотра большой коллекции в диалоге Выражение, коллекция получается в конфигуратор (для отображения) порциями. В результате для просмотра коллекции не приходится тратить существенное время.При попытке просмотра большой коллекции в диалоге Выражение, коллекция получалась в конфигуратор (для отображения) целиком. Это приводило к большим потерям времени и могло приводить к разрыву соединения с предметом отладки.Просматривать большие коллекции в диалоге Выражение стало более комфортно для разработчика.
Полнотекстовый поиск.
Уменьшено время подготовки пользователю результатов полнотекстового поиска.

В результатах полнотекстового поиска всегда выделяется первое точное вхождение искомого слова, если таковое имеется. Если точного вхождения нет - выделяется первая найденная форма искомого слова.

Подготовка пользователю результатов полнотекстового поиска занимала больше времени.

В результатах полнотекстового поиска всегда выделялась первая найденная форма искомого слова.

Уменьшено время, которое затрачивается на отображение пользователю результатов поиска.

Выделение искомого текста в результатах поиска стало более правильным.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Форма клиентского приложения.
В веб-клиенте размер отступа между картинкой и текстом заголовка страницы, а также размеры отступов до краев страницы зависят от размера шрифта всех элементов Страницы текущей формы.

+

В веб-клиенте размер отступа между картинкой и текстом заголовка страницы, а также размеры отступов до краев страницы зависели от размера шрифта конкретного элемента Страницы.

+

Поведение веб-клиента унифицировано с поведением тонкого клиента.
Работа с запросами.
При работе в толстом клиенте конструктор объекта КонструкторЗапроса может быть вызван с пустым текстом запроса. В этом случае считается, что вызван конструктор по умолчанию.При работе в толстом клиенте, конструктор объекта КонструкторЗапроса, формировал исключение, если значением параметра конструктора была пустая строка.Унифицировано поведение конструктора объекта КонструкторЗапроса в различных клиентских приложениях.
Обработка ошибок.
Расширены возможности по работе с ошибками для прикладного разработчика. Для собственных исключений реализована возможность определять коды исключений. Реализована возможность генерировать исключение на основе другого исключения. Изменено представление ошибок, которые генерируются из кода прикладного решения.

Для оператора ВызватьИсключение реализованы параметры Категория, Код, ДополнительнаяИнформация и Причина. При указании более одного параметра, оператор может записываться только в функциональном виде (с параметрами, заключенными в круглые скобки).

Реализовано свойство системного перечисления КатегорияОшибки.ОшибкаКонфигурации.

Для объекта ИнформацияОбОшибке реализованы свойства Код и ДополнительнаяИнформация.

Для запроса getInfo сервиса регистрации ошибок реализованы параметры errorCategories, clientID, reportID. Для отчета об ошибке реализованы свойства id (содержит значение reportID из запроса getInfo) и dump.reasonForNoDump (содержит причину, по которой отчет не содержит дампа аварийного завершения).

Для объекта НастройкиОбработкиОшибок реализованы свойства ОтправлятьОтчетНаСервере, ОтправлятьОтчетОбАварийномЗавершенииНаСервере, ОтправлятьОтчетОбАварийномЗавершенииНаСервереВСервисРегистрацииОшибокПлатформы, ВключатьИмяПользователяВОтчетНаСервере, ВключатьСведенияОбИнформационнойБазыВОтчетНаСервере, ВключатьПодробныйТекстОшибкиВОтчетНаСервере.

Данные возможности не предоставлялись.Расширены возможности работы с ошибками. Стало возможно вводить кодификацию ошибок прикладного решения. Расширены возможности программного интерфейса сервиса регистрации ошибок.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Встроенный язык.
Для объектов типа Соответствие и ФиксированноеСоответствие реализована возможность использовать значение Неопределено в качестве ключа. В веб-клиенте эта возможность была и ранее.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

Для объектов типа Соответствие и ФиксированноеСоответствие не поддерживалась возможность использовать значение Неопределено в качестве ключа, кроме веб-клиентаДля объектов типа Соответствие и ФиксированноеСоответствие реализована возможность использовать значение Неопределено в качестве ключа
Работа с XML, XDTO.
Для методов глобального контекста ЗаписатьXML() и СериализаторXDTO.ЗаписатьXML() реализована возможность передавать в качестве параметра Значение объект метаданных следующих типов: справочник, документ, план видов характеристик, план счетов, план видов расчета, регистры сведений, накопления и бухгалтерии, константа, бизнес-процесс и задача. Записаны будут все данные объекта метаданных, которые доступны пользователю, от имени которого выполняется запись данных.Данная возможность не предоставлялась. Выгрузить в XML все данные одного объекта конфигурации было невозможно. Необходимо было перебрать все данные и выгрузить каждый элемент данных отдельно.Ускорена выгрузка данных из прикладного решения.
В документации данное изменение описано здесь, здесь и здесь.
Навигационные ссылки.
Реализована возможность получать навигационную ссылку вместе с ее представлением. В диалоге получения навигационной ссылки реализован переключатель Копировать название. Диалог перехода по ссылке, глобальный поиск и система взаимодействия учитывают, что в буфере обмена может быть навигационная ссылка с представлением.Данная возможность не предоставлялась.Упрощено одновременное получение навигационной ссылки и представления объекта, на который ссылается навигационная ссылка.
В документации данное изменение описано здесь.
Общие объекты.
Реализована возможность формировать уникальные идентификаторы версий 1, 3, 4 и 5. Для конструктора объекта УникальныйИдентификатор реализованы параметры, необходимые для создания идентификаторов необходимой версии.

Реализовано системное перечисление ВерсияУникальногоИдентификатора.

Данная возможность не предоставлялась. Платформа «1С:Предприятие» позволяла формировать уникальные идентификаторы только одной, 4 версии.Прикладному разработчику предоставляется возможность формирования уникального идентификатора той версии, которая требуется для решения конкретной задачи.
Работа с Интернет.
Если в элементе формы ПолеHTMLДокумента в тонком и толстом клиентах отображается URL, для доступа к которой необходим SSL-сертификат, и у этого сертификата обнаружены какие-либо ошибки (например сертификат не является не валидным), то будет отображаться страница, содержащая описание ошибки и предлагающую возможность продолжить работу с URL либо отказаться от этого.Если в элементе формы ПолеHTMLДокумента в тонком и толстом клиентах отображается URL, для доступа к которой необходим SSL-сертификат, и у этого сертификата обнаружены какие-либо ошибки (например сертификат не является не валидным), то в поле будет отображено сообщение об ошибке и работа с требуемым URL будет невозможна.Улучшена диагностика проблем с URL, которые отображаются в клиентском приложении, а также обеспечивается работа с ресурсом в тех случаях, когда такая работа не рекомендуется, но пользователь уверен в своих действиях.
Копии базы данных.
Система компоновки данных.
Если во время выполнения запроса к данным копии произошла ошибка, связанная с используемой в запросе копией, то копия перестает использоваться во всех существующих или новых сеансах до обновления копии или перезапуска кластера серверов.

Если возникла ошибка от копии в процессе выполнения отчета, созданного на системе компоновки данных, в котором есть несколько наборов данных или иерархический набор данных, то пользователю выдается ошибка обращения к данным. В других случаях, а также если для отчета/запроса не требуется использование только копии базы данных, ошибка пользователю не выдается, а запрос автоматически повторно выполняется на основной базе данных или на одной из доступных копий базы данных (за исключением копии с ошибкой).

Данная возможность не предоставлялась.

Копию, в которой произошла ошибка, надо было отключать вручную. После перезапуска кластера или обновления копии было необходимо включить использовании копии обратно.

При работе с копиями базы данных, аварийная копия отключается автоматически, без участия пользователя. Если запрос может быть сформирован без участия аварийной копии базы данных - пользователь не заметит сбоя в копии. Пользователь получит сообщение об ошибке только в том случае, когда запрос к данным не может быть выполнен без данных копии базы данных, а все копии отмечены как аварийные и запросы к ним не выполняются.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Полнотекстовый поиск корректно обрабатывает ситуации, когда в информационной базе выполнялось большое количество итераций обновления индекса полнотекстового поиска (сотни тысяч итераций) и в базе находится большое количество индексируемых элементов.

Для включения этой возможности необходимо выполнить создание индекса с режимом совместимости, который установлен в значение Версия 8.3.14 или последующее (включая значение Не использовать).

Происходило нарушение корректности индекса полнотекстового поиска, когда в информационной базе выполнялось большое количество итераций обновления индекса полнотекстового поиска (сотни тысяч итераций) и в базе находится большое количество индексируемых элементов.Устранено некорректное поведение системы.
Табличный документ.
При преобразовании табличного документа в компактный вид, применяемый на мобильных устройствах, для выравнивания текста в ячейках используется свойство АвтоОтступ.При преобразовании табличного документа в компактный вид, применяемый на мобильных устройствах, для выравнивания текста в ячейках использовалось только свойство Отступ.Улучшено отображение табличного документа на мобильных устройствах.
Система взаимодействия.
Если в тонком или веб-клиенте во время видеозвонка включается режим отображения экрана, то окно видеозвонка меняет свой вид на компактное отображение. Реализована возможность свернуть компактное окно видеозвонка до размеров заголовка.Если в тонком или веб-клиенте во время видеозвонка включается режим отображения экрана, то окно видеозвонка пропадало с экрана. Пользователю, который демонстрирует экран, было непонятно, остались у него слушатели или уже нет.Пользоваться демонстрацией экрана во время видеозвонка стало удобнее.
Табличный документ.
При сохранении табличного документа в формат XLS (Microsoft Excel 97) или Microsoft Office OpenXML (Microsoft Excel 2007 и старше), в результирующем документе для листа Microsoft Excel устанавливается имя Лист_1. В режиме совместимости с версией 8.3.20 поведение не изменилось.

При сохранении табличного документа в формат XLS (Microsoft Excel 97) или Microsoft Office OpenXML (Microsoft Excel 2007 и старше) не скрывается панель листов документов.

При сохранении табличного документа в формат XLS (Microsoft Excel 97) или Microsoft Office OpenXML (Microsoft Excel 2007 и старше), в результирующем документе для листа Microsoft Excel устанавливалось имя TDSheet.

При сохранении табличного документа в формат XLS (Microsoft Excel 97) или Microsoft Office OpenXML (Microsoft Excel 2007 и старше) скрывалась панель листов документов.

Устранены проблемы производительности, которые возникали при попытке открыть в Microsoft Excel документ со скрытой панелью листов. Именование листов в результирующем документе Microsoft Excel стало более понятным и предсказуемым.
В документации данное изменение описано здесь.
Система взаимодействия.
Для системы взаимодействия реализована возможность включить поддержку специфических видов аудиоустройств (многоканальные микрофоны и аудиосистемы). Эта возможность включается отдельно - в диалоге настроек видео и звука настроек системы взаимодействия. Пользователь может использовать данную настройку в том случае, если имеются проблемы с захватом или воспроизведением звука на компьютере.На некоторых компьютерах могли наблюдаться проблемы со звуком при совершении видеозвонков.Реализована поддержка большего числа аудиоустройств в тонком клиенте.
Система компоновки данных.
При выводе списковых макетов системы компоновки данных в правой нижней ячейке макета не выполняется объединение по вертикали с пустой ячейкой, находящейся в строке ниже.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

При выводе списковых макетов системы компоновки данных в правой нижней ячейке макета выполнялось объединение по вертикали с пустой ячейкой, находящейся в строке ниже.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
Если динамический список содержит видимое поле, тип которого состоит из строки неограниченной длины и любого другого типа (кроме NULL и Неопределено), то:
  • В этом динамическом списке возможно использование строки поиска.
  • Такое поле отсутствует в списке доступных полей отбора.

В режиме совместимости с версией 8.3.20 поведение не изменилось. +

Если динамический список содержит видимое поле, тип которого состоит из строки неограниченной длины и любого другого типа (кроме NULL и Неопределено), то:
  • Использование строки поиска в этом динамическом списке было невозможно (формировалась ошибка).
  • Если такое поле присутствовало в списке доступных полей отбора, но попытка применить отбор по этому полю завершалась ошибкой.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Внешние компоненты.
Для программного нтерфейса внешних компонент реализован метод SetUserInterfaceLanguageCode(), который используется для передачи во внешнюю компоненту языка локализации интерфейса клиентского приложения. Метод SetLocale() считается устаревшим и не рекомендуется к применению. Внесены изменения в технологию создания внешних компонент (см. здесь).

Рекомендуется текущие внешние компоненты перевести на использование нового метода получения кода локализации интерфейса.

Для передачи во внешнюю компоненту языка локализации интерфейса клиентского приложения использовался метод SetLocale(). Данный метод работал по-разному в разных клиентских приложениях и с разными языками локализации интерфейса.Унифицирован способ передачи информации о языке локализации клиентского приложения во внешнюю компоненту.
Отображение информации.
Табличный документ.
Если в параметрах печати табличного документа установлен масштаб печати По ширине страницы и ширины страницы не хватает для размещения документа, то при экспорте табличного документа в формат Microsoft Word обеспечивается масштабирование документа аналогично масштабированию, которое система «1С:Предприятие» выполняет при печати табличного документа: изменяется ширина колонок, изменяется высота строк, изменяется размер шрифта.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

Если в параметрах печати табличного документа установлен масштаб печати По ширине страницы и ширины страницы не хватает для размещения документа, то при экспорте табличного документа в формат Microsoft Word документ изменялся не так, как это делает система «1С:Предприятие» при печати этого табличного документа.Если для табличного документа установлен масштаб печати По ширине страницы, то напечатанный документ и документ, экспортированный в формат Microsoft Word, будут иметь минимум отличий.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.14.Версия формата выгрузки конфигурации в XML-файлы была равна 2.13.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Форма клиентского приложения.
При попытке изменения реквизитов формы или состава настроек динамического списка из встроенного языка, добавление реквизита/колонки с дублирующимся именем приведет к формированию исключения.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

При попытке изменения реквизитов формы или состава настроек динамического списка из встроенного языка, добавление реквизита/колонки с дублирующимся именем было допустимо и не приводило к ошибкам добавления. Доступ к такому реквизиту из встроенного языка был невозможен.Устранено некорректное поведение системы.
Работа в ОС Linux.
Средства администрирования.
Кластер серверов.
При использовании кластера серверов «1С:Предприятие» под управлением ОС Linux, прекращено использование подсистемы инициализации и управления службами SystemV. Вместо нее используется аналогичная (по назначению) подсистема systemd.

В состав дистрибутива включен systemd-сценарий запуска кластера серверов и сервера администрирования (ras) и их конфигурационные файлы.

SystemV-сценарий запуска кластера серверов (и его конфигурационный файл) удален из дистрибутива системы «1С:Предприятие».

После смены версии необходимо заново сконфигурировать возможность автоматического запуска кластера серверов.

При использовании кластера серверов «1С:Предприятие» под управлением ОС Linux, использовалась подсистема инициализации и управления службами SystemV. Повысится удобство запуска и конфигурирования экземпляров сервиса «1С:Предприятия» для администраторов систем, работающих под управлением ОС на Linux, в том числе, и при необходимости множественного запуска разных экземпляров.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Внешние компоненты.
Реализована возможность загружать внешние компоненты в отдельном процессе, отделенном от процессов платформы «1С:Предприятие». В этом случае аварийное завершение внешней компоненты не приведет к аварийному завершению платформы, но потребует повторного подключения внешней компоненты.

В технологию создания внешних компонент внесены изменения, позволяющие внешней компоненте сообщать платформе, в каком режиме компонента умеет работать и в каком режиме работает в данный момент (см. здесь).

Для метода ПодключитьВнешнююКомпоненту() (и все асинхронные аналоги) реализован параметр ТипПодключенияВнешнейКомпоненты. Реализован метод ПроверитьПодключениеВнешнейКомпоненты().

Реализовано событие ОбработкаОтключенияВнешнейКомпоненты, которое вызывается при аварийном завершении процесса, в котором выполняется внешняя компонента.

Рекомендуется разрабатывать внешние компоненты с поддержкой изолированной работы. При использовании внешних компонент на стороне клиентского приложения рекомендуется предусмотреть код повторной загрузки при аварийном завершении внешней компоненты.

При разработке конфигураций в режиме совместимости с версией 8.3.20 или более ранних, внешние компоненты рекомендуется явно загружать изолировано, если компонента может работать в отдельном процессе.

Данная возможность не предоставлялась.

Внешние компоненты загружались только в адресное пространство процесса платформы «1С:Предприятие», которое использовало эту внешнюю компоненту. Аварийное завершение внешней компоненты приводило в аварийному завершению работы процесса «1С:Предприятие».

Повышена стабильность использования внешних компонент.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Средства администрирования.
Если перед установкой платформы автоматически выполнялась установка обновлений ОС или обновляемые файлы использовались другими программами, то после установки платформы выводится предупреждение о том, что может потребоваться перезагрузка компьютера.Если перед установкой платформы автоматически выполнялась установка обновлений ОС или обновляемые файлы использовались другими программами, то после установки платформы компьютер мог быть перезагружен без каких-либо предупреждений и вопросов, что могло приводить к потере данных пользователя, который выполнял установку системы «1С:Предприятие».Более корректное поведение программы установки в том случае, если для завершения установки требуется перезагрузка компьютера.
Клиентское приложение.
При подключении к информационной базе по протоколу HTTP с помощью тонкого или веб-клиента, в командной строке запуска реализована возможность указания команды /UC в том случае, если установлена блокировка начала сеансов с кодом разблокировки.При подключении к информационной базе по протоколу HTTP с помощью тонкого или веб-клиента, в командной строке запуска игнорировалось указание команды /UC.Для пользователя, который знает код разблокировки, реализована возможность подключаться к информационной базе по протоколу HTTP даже в том случае, когда установлена блокировка начала сеансов.
В документации данное изменение описано здесь, здесь и здесь.
Обработка ошибок.
Если в сеансе работы пользователя включен режим технического специалиста, то изменяется трактовка значения Авто свойства НастройкиОбработкиОшибок.ВариантОтображенияСообщения:
  • Включен режим технического специалиста - Авто трактуется как КраткоеПредставлениеОшибки.
  • Выключен режим технического специалиста - Авто трактуется как СообщениеОбОшибкеДляПользователя.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

Значение Авто свойства НастройкиОбработкиОшибок.ВариантОтображенияСообщения всегда трактовалось как СообщениеОбОшибкеДляПользователя.Для специалиста по разработке или внедрению ошибки будут выводиться в более техническом виде, что может упростить диагностику и решение проблемной ситуации.
В документации данное изменение описано здесь.
Расширение конфигурации.
Реализована возможность создания собственных предопределенных элементов заимствованных объектах следующего вида: справочники, планы видов характеристик, планы счетов, планы видов расчета. Предопределенные элементы могут быть заимствованными и собственными.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

Данная возможность не предоставлялась.Расширение конфигурации стало предоставлять больше возможностей.
В документации данное изменение описано здесь.
Работа с СУБД.
Для СУБД PostgreSQL, Oracle Database, IBM DB2 выражение языка запросов, содержащих множественный оператор В с подзапросом, транслируется в язык СУБД с использованием оператора EXISTS(). В результате изменения множественный оператор В с подзапросом всегда возвращает значение типа Булево. В режиме совместимости с версией 8.3.20 поведение не изменилось.

Рекомендуется проверить в прикладных решениях использование запросов, содержащих множественный оператор В с подзапросом.

Для СУБД PostgreSQL, Oracle Database, IBM DB2 выражение языка запросов, содержащих множественный оператор В с подзапросом, транслировались в язык СУБД с использованием оператора multivalue IN. В СУБД Microsoft SQL Server и файловом варианте информационной базы использовался оператор EXISTS(). Это приводило к тому, что выражение языка запросов могло возвращать разные значения на разных СУБД.Поведение множественного оператора В с подзапросом приведено к единому виду для всех поддерживаемых СУБД.
В документации данное изменение описано здесь.
Система компоновки данных.
Система компоновки данных не выводит в отчет записи из других периодов, если задана следующая группировка: поле-период - поле, не являющееся периодом - поле-период.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

Система компоновки данных выводила в отчет записи из других периодов, если задана следующая группировка: поле-период - поле, не являющееся периодом - поле-период.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При генерации макета компоновки данных, если какое-то необязательное соединение запроса набора данных признано используемым (в настройках компоновки данных используется поле из таблиц этого соединения), то используемыми считаются также и соединения с таблицами, поля которых использованы в этом соединении.

В режиме совместимости с версией 8.3.20 поведение не изменилось.

При генерации макета компоновки данных, если какое-то необязательное соединение запроса набора данных признано используемым (в настройках компоновки данных используется поле из таблиц этого соединения), то это не делало используемыми соединения с таблицами, поля которых были использованы в этом соединении.Поведение генератора макета компоновки данных стало более предсказуемым.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Если запрос полнотекстового поиска содержит символ *, обрамленный символами кавычек, например «стол*», то такое выражение интерпретируется как поиск символа *, а не как метасимвол.Если запрос полнотекстового поиска содержит символ *, то такое выражение всегда интерпретировалось как метасимвол, вне зависимости от того, как оформлялась строка поиска.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
В настройки системы компоновки данных, которые получаются в результате вызова метода расширения таблицы формы для динамического списка ПолучитьИсполняемыеНастройкиКомпоновкиДанных(), в конец списка полей порядка добавляются ключевые поля динамического списка, если эти поля заданы в свойстве Поля ключа динамического списка. В результате сортировка данных, которая выполняется по таким настройкам, всегда будет стабильной.

Рекомендуется выполнить анализ всех мест использования метода ПолучитьИсполняемыеНастройкиКомпоновкиДанных() для динамических списков с произвольным ключом и убедиться, что полученные настройки не загружаются в настройки динамического списка. Полученные настройки предназначены для использования только со схемой компоновки данных, которая получена в результате вызова метода ПолучитьИсполняемуюСхемуКомпоновкиДанных() расширения таблицы формы для того же динамического списка.

В настройки системы компоновки данных, которые получаются в результате вызова метода расширения таблицы формы для динамического списка ПолучитьИсполняемыеНастройкиКомпоновкиДанных(), в конец список полей порядка не добавлялись ключевые поля динамического списка. В результате сортировка данных, которая выполняется по таким настройкам, могла быть нестабильной.Сортировка данных, которые получаются с использованием исполняемой схемы компоновки данных и исполняемых настроек компоновки данных динамического списка, всегда будет стабильной.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Свойства объекта НастройкиОбработкиОшибок. Старые наименования поддерживаются для совместимости.
  • ВключатьИмяПользователяВОтчет;
  • ВключатьИнформациюОСистемеВОтчет;
  • ВключатьПодробныйТекстОшибкиВОтчет;
  • ВключатьСведенияОбИнформационнойБазеВОтчет;
  • ВключатьСнимокОконВОтчет;
  • ОтправлятьОтчетОбАварийномЗавершении;
  • ОтправлятьОтчетОбАварийномЗавершенииВСервисРегистрацииОшибокПлатформы;
  • ОтправлятьОтчет.
  • ВключатьИмяПользователяВОтчетНаКлиенте;
  • ВключатьИнформациюОСистемеВОтчетНаКлиенте;
  • ВключатьПодробныйТекстОшибкиВОтчетНаКлиенте;
  • ВключатьСведенияОбИнформационнойБазеВОтчетНаКлиенте;
  • ВключатьСнимокОконВОтчетНаКлиенте;
  • ОтправлятьОтчетОбАварийномЗавершенииНаКлиенте;
  • ОтправлятьОтчетОбАварийномЗавершенииНаКлиентеВСервисРегистрацииОшибокПлатформы;
  • ОтправлятьОтчетНаКлиенте.
В документации данное изменение описано здесь.
Свойство, предназначенное для указания адреса сервиса регистрации ошибок объекта НастройкиОбработкиОшибок.
  • АдресСервисаРегистрацииОшибок
  • АдресСервисаОбработкиОшибок
Русские имена картинок библиотеки картинок. Старые имена объявлены устаревшими и поддерживаются для совместимости.
  • ОформлениеЗнакВоcклицательныйЗнак,
  • ОформлениеВоcклицательныйЗнак.

Имена содержат латинскую букву «c». +

  • ОформлениеЗнакВосклицательныйЗнак,
  • ОформлениеВосклицательныйЗнак.

Имена содержат русскую букву «с». +

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
Работа с ZIP-архивами.
В мобильной версии «1С:Предприятия» реализована работа с zip-архивами.Данная возможность не предоставлялась.В мобильной версии системы «1С:Предприятие» стали доступны операции с zip-архивами.
Мобильная платформа.
Мобильный клиент.
Динамический список.
Система компоновки данных.
В мобильной версии «1С:Предприятия», сохранение пользовательских настроек отчета выполняется при формировании отчета. Свойство расширения формы отчета ПользовательскиеНастройкиМодифицированы устанавливается в значение Ложь при формировании результата отчета. В режиме совместимости с версией 8.3.20 поведение не изменилось.

В мобильной версии «1С:Предприятия», сохранение варианта отчета выполняется после закрытия формы редактирования варианта отчета с помощью кнопки Завершить редактирование. В режиме совместимости с версией 8.3.20 поведение не изменилось.

Пользовательские настройки динамического списка сохраняются после успешной загрузки записей динамического списка.

В мобильной версии «1С:Предприятия», сохранение пользовательских настроек отчета выполнялось при закрытии формы отчета. Свойство расширения формы отчета ПользовательскиеНастройкиМодифицированы устанавливается в значение Ложь при закрытии формы.

В мобильной версии «1С:Предприятия», сохранение варианта отчета выполнялось только при принудительном вызове команды Сохранить вариант.

Работа с настройками отчета и динамического списка стала более логичной и понятной.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Мобильный клиент.
Ускорен запуск мобильного клиента с подключенной системой взаимодействия.Запуск мобильного клиента с подключенной системой взаимодействия занимал больше времени.Ускорен запуск мобильного клиента с подключенной системой взаимодействия.
Средства разработки.
Реализована возможность запрещать выгрузку в XML-файлы ссылок на удаленные объекты конфигурации.

В диалоге выгрузки конфигурации в файлы реализован переключатель Не выгружать ссылки на несуществующие объекты.

Для команды /DumpConfigToFiles реализован параметр -ignoreUnresolvedReferences.

Для команды агента конфигуратора config dump-config-to-files реализован параметр --ignore-unresolved-refs.

Для команды утилиты управления автономным сервером (ibcmd) config export реализован параметр --ignore-unresolved-refs.

Данная возможность не предоставлялась.Стало возможно отказаться от выгрузки в XML-файлы конфигурации ссылки на объекты, которые ранее были удалены в конфигурации, но ссылки на которые остались в формах, командном интерфейсе и т.д.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Веб-клиент.
Если пользователь системы взаимодействия выполняет видеозвонок, находясь в веб-клиенте, который работает под управлением веб-браузера Mozilla Firefox, то качество видеопотока всегда будет высоким. Качество видеопотока не зависит от того, каким образом этот пользователь отображается у своего контрагента.Если пользователь системы взаимодействия выполняет видеозвонок, находясь в веб-клиенте, который работает под управлением веб-браузера Mozilla Firefox, то веб-клиент пытался управлять качеством видеопотока, но эти попытки не работали.Устранено некорректное поведение системы.
Динамический список.
Исключена возможность получения навигационной ссылки текущей строки для регистра сведений, подчиненного регистратору. В список навигационных ссылок, который передается в обработчик события ОбработкаПолученияСпискаНавигационныхСсылок для такого регистра сведений, не передается элемент с ключом ЗаписьТекущейСтрокиСписка.Предоставлялась возможность получения навигационной ссылки текущей строки для регистра сведений, подчиненного регистратору. Устранено некорректное поведение системы, т.к. для регистра сведений, подчиненного регистратору, отсутствует форма записи.
Система компоновки данных.
Мобильный клиент.
Реализовано сохранение пользовательских настроек отчета в следующих случаях:
  • При закрытии формы настроек (для тонкого, толстого мобильного и веб-клиентов).
  • При вызове стандартной команды формирования отчета.
  • Через 10 секунд после последнего редактирования пользовательских настроек.

В режиме совместимости с версией 8.3.20 поведение не изменилось. +

Пользовательские настройки отчета сохранялись только при вызове стандартной команды формирования отчета.Устранено некорректное поведение системы.

Снижена вероятность утери выполненных настроек за счет автоматического сохранения.

Распределенные информационные базы.
В каждом узле распределенной информационной базы необходимо вводить данные клиента лицензирования.Данные клиента лицензирования было необходимо вводить только в главном узле распределенной информационной базы.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Средства администрирования.
В состав мобильной версии системы «1С:Предприятие» включен файл cacertnx.pem, который содержит корневые сертификаты удостоверяющих центров.

При установке защищенного соединения, проверка отзыва сертификатов выполняется в следующем порядке: сертификаты из файла cacertnx.pem, сертификаты конфигурации, сертификаты приложения, сертификаты мобильной операционной системы.

Данная возможность не предоставлялась.Расширены возможности проверки отзыва сертификатов.

+

Работа с СУБД.
Регистры бухгалтерии.
Изменен состав индексов регистра бухгалтерии при работе под управлением СУБД PostgreSQL, Oracle Database и Дата акселератора.

Состав индексов изменяется при выполнении реструктуризации регистра бухгалтерии (в том числе при выполнении операции тестирования и восстановления).

Состав индексов регистра бухгалтерии при работе под управлением СУБД PostgreSQL, Oracle Database и Дата акселератора был другим.Ускорено получение данных из регистров бухгалтерии.
Мобильная платформа.
Мобильный клиент.
Системные требования.
Сборщик мобильных приложений.
Реализована поддержка ОС Android 12. Прекращена поддержка ОС Android 4.1 (минимальная поддерживаемая версия ОС Android - 4.4).

Изменена технология создания внешних компонент (см. здесь).

Мобильное приложение, которое будет опубликовано в магазине приложений Google Play и использует функциональность Установка приложений, должно соответствовать требованиям магазина приложений, которые вступают в силу 11 июля 2022 года. Для этого необходимо использовать мобильную версию 8.3.21.41 и последующие версии.

Поддерживалась ОС Android версии 4.1.Реализована поддержка актуальной версии ОС Android.

Мобильная версия «1С:Предприятие» перестала поддерживать устройства, для которых Google перестала выпускать обновления безопасности.

В документации данное изменение описано здесь.
Работа с информационными базами.
Средства администрирования.
При вызове метода УдалитьДанныеИнформационнойБазы() будет выполнена попытка установить монопольный режим, если монопольный режим еще не установлен. Если установить монопольный режим не получилось - метод завершит работу формированием исключения

При работе метода УдалитьДанныеИнформационнойБазы() расширения, установленные в информационной базе не удаляются. Данные в таблицах объектов расширений - удаляются.

В файловой информационной базе исполнение метода УдалитьДанныеИнформационнойБазы() без установки монопольного режима успешно работало.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с PDF-документами.
Для методов Записать() и ЗаписатьАсинх() объекта ДокументPDF реализованы параметры ТипФайла.

При интерактивном сохранении документа в формате PDF реализована возможность выбрать вариант PDF-документа.

Данная возможность не предоставлялась.Стало возможно записывать PDF-документ в нужном формате (включая форматы архивного хранения PDF/A)
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Если на устройстве под управлением ОС iOS установлен увеличенный масштаб, то мобильная версия «1С:Предприятие» также будет отображать свой интерфейс в увеличенном масштабе.Данная возможность не предоставлялась.Улучшено отображение пользовательского интерфейса на мобильных устройствах под управлением ОС iOS.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Если в результате XSL-преобразования, которое выполняется с помощью объекта ПреобразованиеXSL, результатом преобразования выступает HTML-файл, то для атрибутов различных элементов href, action, src и атрибута name элемента a, выполняется URL-кодирование значения атрибута. Из URL-кодирования исключаются следующие символы: @/:=?;#%&,+\.Если в результате XSL-преобразования, которое выполняется с помощью объекта ПреобразованиеXSL, результатом преобразования выступает HTML-файл, то URL-кодирование каких-либо значений не выполнялось.Устранено некорректное поведение системы.
Работа с XML, XDTO.
Для метода глобального контекст ПрочитатьXML() реализована возможность выполнить частичное чтение: прочитать только те данные, которые указаны в xml-файле, не изменяя данные, которые уже находятся в объекте информационной базы. Такое чтение включается в том случае, если xml-элемент, описывающий объект системы «1С:Предприятие» содержит необязательный атрибут dataPart, установленный в значение true.

Система «1С:Предприятие» не позволяет создать xml-файл, который позволит выполнить частичное чтение.

Частичное чтение реализовано для следующих объектов конфигурации: справочники, документы, задачи, бизнес-процессы, планы обмена, планы счетов, планы расчетов, планы видов характеристик, регистры сведений, накоплений, расчета и бухгалтерии.

Метод ПрочитатьXML() не позволял выполнить частичное чтение объекта конфигурации из xml-файла.Расширены возможности обмена со сторонними системами с помощью xml-файлов.
В документации данное изменение описано здесь.
Работа с Интернет.
Во время вызова метода ИнтернетПочта.Подключиться() используется защищенное соединение. Если в прикладном решении используются почтовые сервера, для которых не требуется выполняться проверку сертификата сервера, то эти сервера необходимо указать в конфигурационном файле conf.cfg. Для этого реализован параметр IgnoreInternetMailServerCertificateVerificationList этого конфигурационного файла.Во время вызова метода ИнтернетПочта.Подключиться() использовалось не защищенное соединение.Повышена безопасность использования объектов, связанных с удаленным доступом к различным внешним сервисам.
В документации данное изменение описано здесь.
Внешние компоненты.
Если у пользователя, от имени которого работает приложение, выполняющее попытку подключить внешнюю компоненту (метод ПодключитьВнешнююКомпоненту()) изолированно, недостаточно прав для создания отдельного процесса, то внешняя компонента будет подключена в не изолированном режиме.Если у пользователя, от имени которого работает приложение, выполняющее попытку подключить внешнюю компоненту (метод ПодключитьВнешнююКомпоненту()) изолированно, недостаточно прав для создания отдельного процесса, то внешняя компонента не подключалось и использовать внешнюю компоненту было невозможно.Стало возможно использование внешней компоненты вне зависимости от наличия прав на запуск отдельного процесса у пользователя, от имени которого работает приложение, выполняющее подключение внешней компоненты.
В документации данное изменение описано здесь.

Оглавление

Переход с предыдущей версии на версию 8.3.21

Оглавление

Версия 8.3.20

Версия 8.3.20 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8320doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.19.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.18. +Возможность запуска конфигураций, разработанных в версии 8.3.19 и более младших, в версии 8.3.20, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.20 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.20, при необходимости, использовать для работы с информационной базой и версию 8.3.19. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Расширение конфигурации.
Сервис интеграции.
Реализована возможность заимствования сервисов интеграции и создания собственных сервисов интеграции в расширении.Данная возможность не предоставлялась.Расширение конфигурации стало предоставлять больше возможностей.
В документации данное изменение описано здесь и здесь.
Система лицензирования.
Реализована возможность активации программной лицензии из встроенного языка. Реализовано свойство глобального контекста ПолучениеЛицензий.Данная возможность не предоставлялась.Стало возможно выполнять активацию программных лицензий в том случае, когда отсутствует возможность запуска конфигуратора.
В документации данное изменение описано здесь.
Журнал регистрации.
Реализована возможность управлять периодом разделения данных журнала регистрации и сокращать журнал регистрации из встроенного языка.

Реализованы методы ПолучитьПериодРазделенияХраненияДанныхЖурналаРегистрации(), УстановитьПериодРазделенияХраненияДанныхЖурналаРегистрации(), ПолучитьПериодЖурналаРегистрации(), СократитьЖурналРегистрации().

Тип Диапазон можно использовать не только для работы с блокировками, но и для работы с журналом регистрации.

Данная возможность не предоставлялась. Управление периодом разделения данных журнала регистрации и возможность сокращения журнала регистрации была доступна только в интерактивном режиме из Конфигуратора.Стало возможно реализовать все функции управления журналом регистрации с помощью встроенного языка.
В документации данное изменение описано здесь.
Региональные установки.
Реализована возможность работать с региональными настройками информационной базы из встроенного языка.

Реализованы методы глобального контекста ПолучитьРегиональныеНастройкиИнформационнойБазы(), УстановитьРегиональныеНастройкиИнформационнойБазы(), ПолучитьРегиональныеНастройкиСеанса().

Данная возможность не предоставлялась.

С помощью встроенного языка имелась возможность получения текущего кода локализации и код локализации информационной базы.

Стала возможна работа с региональными настройками информационной базы с помощью встроенного языка.
В документации данное изменение описано здесь.
Работа с запросами.
В языке запросов реализованы следующие функции: Строка(), ДлинаСтроки(), СокрЛ(), СокрП(), СокрЛП(), Лев(), Прав(), СтрНайти(), СтрЗаменить(), ВРег(), НРег(), Sin(), Cos(), Tan(), ASin(), ACos(), ATan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Окр(), Цел(), РазмерХранимыхДанных().

Если в запросе используются вышеописанные функции, то такой запрос не будет отправляться в Дата акселератор.

Данные возможности не предоставлялись.Расширены возможности языка запросов.
В документации данное изменение описано здесь.
Система компоновки данных.
В языке выражений системы компоновки данных реализованы следующие функции: СокрЛ(), СокрП(), СокрЛП(), Лев(), Прав(), СтрНайти(), СтрЗаменить(), ВРег(), НРег(), НСтр().

Если отбор системы компоновки данных применяется к вычисляемому полю, которое содержит следующие функции: Sin(), Cos(), Tan(), ASin(), ACos(), ATan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Окр(), Цел(), ДлинаСтроки(), то такое поле будет отрабатываться с помощью запроса (при возможности).

В режиме совместимости с версией 8.3.19 поведение не изменилось.

Данные возможности не предоставлялись.

Если отбор системы компоновки данных применяется к вычисляемому полю, которое содержит следующие функции: Sin(), Cos(), Tan(), ASin(), ACos(), ATan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Окр(), Цел(), ДлинаСтроки(), то такое поле вычислялось во время компоновки данных.

Расширены возможности системы компоновки данных.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность участия в обсуждениях системы взаимодействия внешних (по отношению к информационной системе) пользователей (обсуждения, видеозвонки). Внешние пользователи участвуют в обсуждении с помощью специального сайта https://dialog.online. Внешние пользователи могут общаться только с теми пользователями, которые участвуют в обсуждении, куда приглашен внешний пользователь. Для доступа к обсуждениям внешнему пользователю необходимо отправить приглашение.

Для объекта ПользовательСистемыВзаимодействия реализованы свойства Внешний, АдресЭлектроннойПочтыДляАутентификации.

Для менеджера системы взаимодействия реализованы методы ПоддерживаетсяВнешнийДоступ(), ПолучитьНавигационнуюСсылкуВнешнегоДоступа(), ОтправитьНавигационнуюСсылкуВнешнегоДоступа().

Реализован объект ОтборПользователейСистемыВзаимодействия. Для метода ПолучитьПользователей() менеджера системы взаимодействия реализован параметр Отбор.

Для модуля управляемого приложения реализован обработчик события ОбработкаПриглашенияВнешнегоПользователяСистемыВзаимодействия.

Внесены изменения в пользовательский интерфейс системы взаимодействия. +

Данная возможность не предоставлялась.Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 13 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
В документации данное изменение описано здесь.
Система взаимодействия.
В системе взаимодействия реализована возможность интеграции с произвольной системой. Реализована односторонняя интеграция - система взаимодействия может только получать сообщения определенного формата. Для взаимодействия используется REST-интерфейс.

Реализовано свойство ИнтеграцияСистемыВзаимодействия.НавигационнаяСсылкаТочкиПодключения.

Свойство ОбсуждениеСистемыВзаимодействия.Интеграция становится доступным для записи.

В текстах сообщений ограниченно поддерживается HTML-оформление.

Данная возможность не предоставлялась.

Для интеграции был доступен ограниченный список внешних систем.

Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь.
Расширение конфигурации.
Предопределенные данные.
Реализована возможность создавать предопределенные элементы в собственных справочниках расширений конфигурации. В режиме совместимости с версией 8.3.19 (для конфигурации и расширения конфигурации) поведение не изменилось.В собственных справочниках расширений конфигурации не поддерживалось создание предопределенных элементов конфигурации.Расширение конфигурации стало предоставлять больше возможностей.

+

В документации данное изменение описано здесь.
Интерфейс.
Реализована возможность управления отображением групп форм вида Страница:
  • Значение свойства ШрифтЗаголовка группы формы вида Страница задает шрифт заголовка страницы. Данное свойство для группы формы вида Страницы управляет шрифтом заголовка всех страниц группы (для которых явно не указан шрифт).
  • Значение свойства ЦветТекстаЗаголовка группы формы вида Страница задает цвет текста заголовка страницы. Данное свойство для группы формы вида Страницы управляет цветом текста заголовка всех страниц группы (для которых явно не указан цвет текста заголовка).

В режиме совместимости с версией 8.3.19 поведение не изменилось.

Данные возможности не предоставлялась.

Свойства ШрифтЗаголовка и ЦветТекстаЗаголовка не использовались для оформления групп формы вида Страница.

Расширены изобразительные возможности интерфейса клиентского приложения.
В документации данное изменение описано здесь.
Динамический список.
Для динамического списка реализована поддержка свойства Выражение представления для полей набора данных и вычисляемых полей. Это представление используется только в таблице динамического списка, и не используется для поля, которое отображается вне динамического списка.

Значение свойства может быть задано интерактивно или с помощью свойства ВыражениеПредставления объектов ПолеНабораДанныхСхемыКомпоновкиДанных и ВычисляемоеПолеСхемыКомпоновкиДанных.

Данная возможность не предоставлялась.Расширены оформительские возможности динамического списка.
Работа с XML, XDTO.
Реализовано свойство глобального контекста ОбработкаСтрокиXML. Для вызова метода НайтиНедопустимыеСимволыXML() необходимо использовать данное свойство. Одноименный метод глобального контекста является устаревшим и не рекомендуется к применению.

Для удаления недопустимых символов XML из строки реализован метод глобального контекста ОбработкаСтрокиXML.УдалитьНедопустимыеСимволыXML().

Предоставлялась только возможность найти вхождение недопустимого символа XML в строке с помощью метода глобального контекста НайтиНедопустимыеСимволыXML().Упрощена работа по очистке текста с XML-подобной разметкой от недопустимых символов.
Общие объекты.
Реализована возможность получения типа клиентского приложения, начавшего данный сеанс работы. Реализована возможность определить, что данное клиентское приложение может работать с автономным сервером мобильного клиента.

Для объекта КлиентскоеПриложение реализованы методы ТипКлиентскогоПриложения() и КлиентСИспользованиемАвтономногоСервера().

Данная возможность не предоставлялась.Упрощено определение используемого клиентского приложения.
Отображение информации.
В библиотеку картинок добавлены следующие картинки:
  • ИсторияСообщений;
  • ВнешнийПользователь;
  • ПоказатьПароль;
  • СкрытьПароль.
В библиотеке картинок отсутствовали добавленные картинки. Расширен состав библиотеки картинок.
Системные требования.
Реализована поддержка Astra Linux Special Edition 1.7 и СУБД PostgreSQL 11.10 из состава данной ОС.Astra Linux Special Edition 1.7 не поддерживалась платформой «1С:Предприятие».Расширен состав поддерживаемых ОС и СУБД.
В документации данное изменение описано здесь, здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
Видеозвонок автоматически завершается и окно видеозвонка закрывается, когда в списке участников остается только текущий пользователь.

В окне видеозвонка по умолчанию отображаются все участники видеоконференции без активации говорящего пользователя.

При демонстрации экрана в правом нижнем углу окна видеозвонка отображается видео с локальной камеры.

Окно видеозвонка оставалось открытым после завершения видеозвонка.

В окне видеозвонка по умолчанию активировался говорящий участник, а остальные отображались в колонку справа от говорящего.

При демонстрации экрана видео с локальной камеры нигде не отображалось.

Видеозвонки в системе взаимодействия стали более удобными для использования.
Система взаимодействия.
В системе взаимодействия реализованы следующие возможности установки признака прочитанности для сообщений:
  • При просмотре - сообщение помечается как прочитанное через несколько секунд после открытия сообщения пользователем.
  • Вручную - сообщение помечается прочитанным после нажатия гиперссылки Прочитано в списке сообщений.
  • При ответе или вручную - сообщение помечается как прочитанное при ответе на сообщение или при нажатии гиперссылки Прочитано.

В контекстном меню обсуждения (и меню Еще) реализована команда Пометить как прочитанное, доступная для обсуждений, в которых есть непрочитанные сообщения. +

Данные возможности не предоставлялись.

Сообщения всегда помечались как прочитанные через несколько секунд после просмотра. Управлять этим было нельзя.

Управлять признаком прочитанности сообщений стало удобнее. Пользователь может настроить для себя режим управления этим признаком.
Средства администрирования.
Реализованы стандартные обработки, позволяющие редактировать параметры информационной базы (Параметры информационной базы) и список пользователей (Пользователи).Платформа не позволяла выполнять данные операции в клиентском приложении. Данные инструменты могли быть реализованы в прикладном решении.Расширены возможности администрирования системы из клиентского приложения.
Система взаимодействия.
В меню системы взаимодействия реализована команда История сообщений. Данная команда открывает форму, которая позволяет просматривать сообщения за выбранную дату. В этой форме также отображаются все обсуждения, в которых участвовал пользователь в выбранный день.Данная возможность не предоставлялась.

Единый список всех сообщений за день был недоступен.

Улучшена работа с сообщениями системы взаимодействия.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
При работе на мобильных устройствах, изменен внешний вид и поведение следующих форм системы:
  • Форма сохранения настроек отчета.
  • Форма сохранения варианта отчета.
  • Форма выбора настроек динамического списка.
  • Форма сохранения настроек динамического списка.
  • Форма выбора настроек отчета.
  • Форма выбора варианта отчета.
  • Форма выбора параметров формы.
  • Форма сохранения параметров формы.
  • Форма отчета.
  • Форма настроек отчета.
  • Форма настроек динамического списка.
  • Форма редактирования состава настроек.
  • Форма редактирования варианта отчета.
  • Форма элемента условного оформления.

Рекомендуется проверить отображение указанных форм в используемых мобильных прикладных решениях на новой мобильной версии.

Указанные формы в мобильном приложении выглядели по-другому.Улучшен интерфейс некоторых форм при работе на мобильных устройствах.
Веб-клиент.
Работа с файлами.
При использовании расширения работы с файлами в веб-браузерах Google Chrome и Mozilla Firefox ускорено получение файлов по протоколу HTTPS.При использовании расширения работы с файлами в веб-браузерах Google Chrome и Mozilla Firefox получение файлов по протоколу HTTPS занимало больше времени.Ускорено получение файлов по протоколу HTTPS при использовании расширения работы с файлами в веб-браузерах Google Chrome и Mozilla Firefox.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Кластер серверов.
Повышена производительность кластера серверов при работе с высокой нагрузкой. Улучшено использование оперативной памяти при работе под управлением ОС Windows.При работе под управлением ОС Windows оперативная память использовалась менее эффективно.Незначительно повышена скорость работы системы и улучшено использование оперативной памяти при работе под управлением ОС Windows.
Кластер серверов.
Повышена стабильность работы кластера серверов. Снижено количество проблем, которые приводят к аварийному завершению работы кластера серверов.К аварийному завершению работы кластера серверов приводило большее количество проблем, возникающих во время работы кластера.Повышена стабильность кластера серверов в проблемных ситуациях.
Работа с запросами.
При работе в файловом варианте информационной базы оптимизирована работа оператора ПОДОБНО языка запросов.При работе в файловом варианте информационной базы оператор ПОДОБНО языка запросов требовал больше времени на свое исполнение.Повышена производительность оператора ПОДОБНО при работе в файловом варианте информационной базы.
Ограничение доступа к данным.
Оптимизирована работа запроса, одновременно использующего конструкции ВЫБРАТЬ ПЕРВЫЕ, РАЗРЕШЕННЫЕ и УПОРЯДОЧИТЬ ПО и ограничение доступа к данным. Для целей оптимизации, из запроса ограничения доступа к данным, по возможности, выделяется конструкция, не зависящая от данных в защищаемой таблице. Результат этого запроса размещается во временной таблице (но не более 6 временных таблиц), и эта временная таблица затем используется в оригинальном запросе. Конкретная реализация поведения зависит от используемой СУБД.Запрос, одновременно использующего конструкции ВЫБРАТЬ ПЕРВЫЕ, РАЗРЕШЕННЫЕ и УПОРЯДОЧИТЬ ПО и ограничение доступа к данным, мог исполняться неоптимальным способом из-за того, что СУБД не могла выбрать адекватный план запроса.Повышена производительность некоторых видов запросов, выполняющихся в системах с ограничением доступа к данным.
Кластер серверов.
Устранены выявленные утечки памяти в рабочем процессе в тех случаях, когда сеансы, обслуживаемые этим рабочим процессом, завершаются аварийно или мигрируют на другой рабочий процесс.Наблюдались утечки памяти в рабочем процессе в тех случаях, когда сеансы, обслуживаемые этим рабочим процессом, завершаются аварийно или мигрируют на другой рабочий процесс.Повышен контроль над использованием ресурсов рабочим процессом кластера.
Кластер серверов.
Общие реквизиты / Разделение данных.
Расширение конфигурации.
Снижено потребление оперативной памяти рабочим процессом в случае работы с разделенной информационной базой с большим количеством разделенных расширений конфигурации.Рабочий процесс при работе с разделенной информационной базой с большим количеством разделенных расширений конфигурации использовал больше оперативной памяти.Снижено потребление оперативной памяти кластером серверов при работе в разделенном режиме.
Расширение конфигурации.
Работа с информационными базами.
Оптимизирована реструктуризация информационной базы в том случае, если в ней присутствуют расширения конфигурации.Реструктуризация информационной базы в том случае, если в ней присутствуют расширения конфигурации, занимала больше времени.Реструктуризация информационной базы в том случае, если в ней присутствуют расширения конфигурации, выполняется быстрее.
Автономный сервер.
Выгрузка/загрузка конфигурации в файлы.
Существенно снижено время полной загрузки конфигурации из XML-файлов при использовании автономного сервера.Автономный сервер тратил существенно больше времени для выполнения полной загрузки конфигурации из XML-файлов.Ускорена загрузка конфигурации из XML-файлов при использовании автономного сервера.
Прикладные объекты.
Оптимизировано получение списка характеристик для составного типа, в том случае, когда настройки характеристик различных типов (из состава составного) отличаются только значением отбора вида характеристики.Получение списка характеристик для составного типа, в том случае, когда настройки характеристик различных типов (из состава составного) отличаются только значением отбора вида характеристики, занимало больше времени и могло приводить к замедлению в работе различных механизмов платформы.Оптимизирована работа со списком характеристик.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Расширение конфигурации.
Реализована возможность расширять типы следующих заимствованных объектов:
  • Тип общего реквизита, если общий реквизит не является разделителем.
  • Тип реквизита Тип плана видов характеристик.
  • Определяемый тип.

Реализована возможность создавать собственные определяемые типы (если режим совместимости расширения строго старше версии 8.3.19).

В собственных объектах расширения конфигурации реализована возможность использования типов вида ЛюбаяСсылка, СправочникСсылка и т.д. и определяемых типов.

Ссылки вида ЛюбаяСсылка, Справочник Ссылка и т.д. включают в себя ссылки на объекты, привнесенные расширениями конфигурации. Метод ТипВсеСсылки() включает типы из расширений в возвращаемое значение.

В режиме совместимости с версией 8.3.19 поведение не изменилось. +

Данные возможности не предоставлялись.Расширены возможности использования расширения конфигурации.
В документации данное изменение описано здесь, здесь и здесь.
Мобильный клиент.
Средства разработки.
Реализована возможность отлаживать автономный сервер для мобильного клиента с автономным режимом. Реализована возможность в одном сеансе отладки подключать три предмета отладки. Реализован предмет отладки Автономный сервер (мобильный клиент с автономным режимом). Реализована возможность пользоваться замером производительности для анализа времени исполнения всех трех компонентов мобильного клиента с автономным режимом.

Оптимизирована работа собственно отладчика.

Данная возможность не предоставлялась.

Один сеанс отладки одновременно мог подключать не более двух предметов отладки.

Упрощена отладка приложений, которые работают в мобильном клиенте с автономным режимом работы.
В документации данное изменение описано здесь и здесь.
Регистры сведений.
Ограничение доступа к данным.
Для регистров сведений реализована возможность использовать измерения и разделители, в состав которых входит регистр, в выражениях ограничения доступа к данным на чтение и изменение.

Указание различных ограничений доступа к отдельным полям действует только при получении данных из регистров сведений при помощи запросов и динамических списков. При использовании объектов встроенного языка считается, что доступ выполняется ко всем полям, и доступ разрешается только в том случае, если он разрешен ко всем полям (накладываются ограничения на все поля, объединенные «по И»). При записи набора записей применяются только ограничения на изменение.

В режиме совместимости с версией 8.3.19 поведение не изменилось.

Для регистров сведений, в выражениях ограничения доступа к данным, было недоступно указание измерений и разделителей, в состав которых входит регистр. При доступе на чтение к измерениям и полям-разделителям никакие ограничения доступа к данным не применялись.Расширены возможности ограничения доступа к данным регистров сведений.
В документации данное изменение описано здесь.
Расширение конфигурации.
При ошибках компиляции заимствованных модулей расширения реализовано следующее поведение:
  • Формируется оповещение в центр оповещений.
  • Формируется информация об ошибке компиляции (доступна с помощью диалога Информация для технической поддержки).
  • Действие (во время которого потребовалась компиляция заимствованного модуля) выполняется без расширения, в котором произошла ошибка.

Если прикладное решение запущено в режиме отладки, а также в режиме совместимости с версией 8.3.19 - поведение не изменилось.

При ошибках компиляции заимствованных модулей расширения наблюдалось следующее поведение:
  • Генерировалась ошибка компиляции модуля.
  • Действие (во время которого потребовалась компиляция заимствованного модуля) прерывалось.

+

Конфигурация максимально сохраняет работоспособность при проблемах с расширениями.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.13.Версия формата выгрузки конфигурации в XML-файлы была равна 2.12.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Средства администрирования.
В состав дистрибутива сервера «1С:Предприятие» для ОС Linux и Windows включена Java (Liberica JRE).

Изменены утилиты установки сервера «1С:Предприятие» для этих операционных систем.

Java не входила в состав дистрибутива сервера системы «1С:Предприятие». Для использования некоторых возможностей системы «1С:Предприятие» пользователь должен был самостоятельно скачать и установить Java.Упрощено использование тех компонент системы «1С:Предприятие», которые требуют для своей работы систему Java, например, механизм реструктуризации v2, утилита лицензирования и т.д.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Средства администрирования.
Из состава дистрибутива системы «1С:Предприятие» исключена утилита лицензирования. Утилита лицензирования доступна для скачивания через сервис 1С:Обновление программ портала ИТС (см. здесь).Утилита лицензирования входила в состав дистрибутива системы «1С:Предприятие».Упрощен доступ к утилите лицензирования.
В документации данное изменение описано здесь.
Расширение конфигурации.
Средства администрирования.
Для указания имени подписываемого файла следует использовать следующие параметры:
  • Команда /SignCfg - параметр -SignedFile.
  • Команды режима агента config sign-cfg - параметр --signed-file. Параметр --result-file более не используется.

Для указания типа конфигурации следует использовать следующие параметры:

  • Команда /SignCfg - параметр -ConfigurationType. Параметр -Type более не используется.
  • Команды режима агента config sign-cfg - параметр --configuration-type. Параметр --type более не используется.
Для указания имени подписываемого файла использовались следующие параметры:
  • Команда /SignCfg - первый позиционный параметр команды.
  • Команды режима агента config sign-cfg - параметр --result-file.

Для указания типа конфигурации следовало использовать следующие параметры:

  • Команда /SignCfg - параметр -Type.
  • Команды режима агента config sign-cfg - параметр --type.
Параметры команды /SignCfg пакетного режима и config sign-cfg агенте конфигуратора, отвечающие за указание имен файлов и типов конфигурации, унифицированы с аналогичными параметрами других команд.

+

В документации данное изменение описано здесь и здесь.
Средства администрирования.
Установка клиентского приложения.
Работа в ОС Linux.
Реализована программа установки компонентов системы «1С:Предприятие» для ОС Linux. Программа установки доступна в трех вариантах: полный, тонкий клиент и версия для обучения. Программа работает как в графическом режиме, так и пакетном режиме (без оконного интерфейса).

Файлы пакетов .deb и .rpm более не используются для поставки дистрибутивов системы для ОС Linux.

Реализована программа удаления установленного приложения.

Для файл conf.cfg реализованы параметры PublishDistributiveLocationLinux64 и PublishDistributiveLocationLinux32. Параметры этого файла PublishDistributiveLocationLinuxDeb64, PublishDistributiveLocationLinuxDeb32, PublishDistributiveLocationLinuxRpm64, PublishDistributiveLocationLinuxRpm32 более не поддерживаются.

Для элемента point файла default.vrd реализованы атрибуты pubdstlin64 и pubdstlin32. Атрибуты этого элемента pubdstlindeb32, pubdstlindeb64, pubdstlinrpm32, pubdstlinrpm64 более не поддерживаются.

Для параметра pubdst секции http конфигурационного файла автономного сервера реализованы параметры lin64 и lin32.

Приложения системы «1С:Предприятие» поставлялись в виде .deb и .rpm пакетов, которые можно было установить только из командной строки.Упрощена установка компонентов системы «1С:Предприятие» для ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Системные требования.
Работа в ОС Linux.
Прекращена поддержка следующих дистрибутивов ОС Linux:
  • Astra Linux Common Edition 1.11,
  • Astra Linux Special Edition 1.4 и 1.5,
  • Альт Линукс 7.0 СПТ.
Система «1С:Предприятие» поддерживала работу в следующих дистрибутивах ОС Linux:
  • Astra Linux Common Edition 1.11,
  • Astra Linux Special Edition 1.4 и 1.5,
  • Альт Линукс 7.0 СПТ.
Прекращена поддержка устаревших дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Системные требования.
Работа в ОС Linux.
В состав дистрибутива системы «1С:Предприятие» для ОС Linux включена библиотека WebKit1 версии 2.4.11.Библиотека WebKit1 не входила в состав дистрибутива системы «1С:Предприятие» для ОС Linux.Система «1С:Предприятие», развернутая под управлением ОС Linux, более не зависит от библиотеки webkitgtk-3.0.0.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность установить пользователя, от имени которого сеанс будет подключаться к системе взаимодействия. Данная возможность поддерживается только для сеансов, которые работают от имени «пользователя по-умолчанию» (фоновое задание, стартованное регламентным заданием).

Реализован метод МенеджерСистемыВзаимодействия.УстановитьТекущегоПользователя().

Данная возможность не предоставлялась.

Фоновое задание, которое стартовано регламентным заданием, не могло подключаться к системе взаимодействия без явного указания пользователя, от имени которого должно выполняться регламентное задание.

Упрощено подключение к системе взаимодействия из фоновых заданий, которые запускаются с помощью регламентных заданий.
В документации данное изменение описано здесь.
Хранение настроек.
При выполнении обхода списка настроек стандартного хранилища с помощью метода СтандартноеХранилищеНастроекВыборка.Следующий() не выполняется попытка десериализации хранимых настроек. Десериализация выполняется только тогда, когда выполняется попытка обратиться к объекту, хранящего настройки (СтандартноеХранилищеНастроекВыборка.Настройки). В этом случае возможно возникновение исключения.При выполнении обхода списка настроек стандартного хранилища с помощью метода СтандартноеХранилищеНастроекВыборка.Следующий() выполнялась попытка десериализации хранимых настроек. Если в хранилище размещался некорректный объект настроек - обход списка настроек завершался исключением.

После достижения конца выборки все свойства объекта содержат значения, соответствующие последнему элементу выборки. Если выборка является пустой или еще не было вызова метода СтандартноеХранилищеНастроекВыборка.Следующий(), то выборка содержит следующие значения:

  • Свойства КлючОбъекта. КлючНастроек, Пользователь, Представление - содержат пустую строку.
  • Свойства ДатаИзменения, Настройки - содержат значение Неопределено.
Обход списка стандартных настроек стал более логичным. Во время обхода списка исключено возникновение исключения, вызванного некорректными настройками.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Средства администрирования.
Для протокола OpenID Connect реализована поддержка аутентификация с поддержкой Authorization Code Flow.

Для секции описания OpenID-провайдера файла default.vrd (элемент <providers>) реализовано поле client_secret.

Рекомендуется перевести все производственные системы на использование Authorization Code Flow. Использование Implicit Code Flow (текущая реализация протокола) не рекомендуется по соображениям безопасности.

Для протокола OpenID Connect поддерживалась только аутентификация с поддержкой Implicit Code Flow.Реализована возможность использования более безопасного варианта протокола OpenID Connect.
В документации данное изменение описано здесь.
Обработка ошибок.
Реализована возможность определения ошибок, возникающих при преобразовании табличного документа во внешние форматы. Реализовано значение системного перечисления КатегорияОшибки.ОшибкаПреобразованияДокумента.

Прикладному разработчику при анализе категорий ошибок следует учитывать, что состав категорий может расширяться в новых версиях системы. Также следует быть готовым к тому, что ошибка может изменить принадлежность к той или иной категории.

Ошибки, возникающие при преобразовании табличного документа во внешние форматы, не были выделены в отдельную категорию.Расширен список категорий ошибок.
Система компоновки данных.
Если в схеме компоновки данных используется отбор с видами сравнения Содержит, Начинается с, Соответствует шаблону, Не содержит, Не начинается с, Не соответствует шаблону для поля запроса, содержащего объединение, в котором это поле в одной части объединения имеет строковой тип, а в другой части объединения – не строковой тип, то в той части объединения, где поле имеет не строковый тип, в запрос будет добавлено заведомо ложное условие.

Рекомендуется выполнить анализ отборов схем компоновки данных на предмет корректировки таких условий.

В режиме совместимости с версией 8.3.19 поведение не изменилось.

Если в схеме компоновки данных используется отбор с видами сравнения Содержит, Начинается с, Соответствует шаблону, Не содержит, Не начинается с, Не соответствует шаблону для поля запроса, содержащего объединение, в котором это поле в одной части объединения имеет строковой тип, а в другой части объединения – не строковой тип, то в той части объединения, где поле имеет не строковый тип, в запросе не было никаких условий.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Автономный сервер.
Все команды, использующие информационную базу (вне зависимости от способа выполнения), выполняются в рамках полноценного сеанса информационной базы с проверкой прав пользователя, от имени которого выполняется действие, и регистрацией действий в журнале регистрации.

Команды, относящиеся к серверу в целом (такие как получение списка сеансов или прерывание вызова), не требуют создания сеанса, однако также должны выполняться от имени пользователя информационной базы, имеющего административные права.

Для выполнения команд административного интерфейса не создавался сеанс, не выполнялась проверка прав пользователя, от имени которого выполняется административное действие и не выполнялась фиксация совершаемых действий в журнале регистрации информационной базы.Повышена безопасность управления автономным сервером.
В документации данное изменение описано здесь.
Автономный сервер.
Все команды административного интерфейса автономного сервера (за исключением команд инициализации конфигурации сервера, создания информационной базы и восстановления целостности информационной базы) доступны для управления запущенным экземпляром автономного сервера. Для идентификации управляемого сервера можно использовать идентификатор процесса автономного сервера (на локальном компьютере, обращение выполняется с использованием технологии IPC) или адрес удаленного компьютера (обращение выполняется с использованием протокола ssh). Для утилиты ibcmd реализованы параметры --pid, -p и --remote, -r для управления способом подключения к автономному серверу для исполнения команды.

Для утилиты ibcmd реализованы следующие команды утилиты ibsrv: --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, --openid-data.

Управление запущенным экземпляром автономного сервера не поддерживалось. Управление автономным сервером на удаленном компьютере не поддерживалось. Утилита ibcmd (в части настроек автономного сервера) могла только изменять содержимое конфигурационного файла.Для управления автономным сервером доступны два режима:
  • Без запущенного экземпляра сервера - в этом случае происходит формирование конфигурационного файла автономного сервера.
  • С запущенным экземпляром сервера - в этом случае необходимо явное указание экземпляра управляемого сервера (на текущем или удаленном компьютере) с помощью соответствующих параметров командной строки.
В документации данное изменение описано здесь.
Автономный сервер.
Реализована возможность описывать несколько HTTP-шлюзов, обслуживающих вызовы к информационной базе. В конфигурационном файле автономного сервера реализована секция gates. Доступ к информационной базе клиентского приложения и Интернет-сервисов выполняется с помощью секции gates|http.

Для автономного сервера реализован доступ к административному интерфейсу по протоколу SSH. Состав команд автономного сервера аналогичен составу команд конфигуратора в режиме агента и приведен в документации. В конфигурационном файле автономного сервера реализована секция gates|ssh.

Файл конфигурации автономного сервера поддерживал настройку только одного HTTP-шлюза, обеспечивающего доступ к информационной базе.

Доступ к автономному серверу по протоколу SSH не предоставлялся.

Расширены возможности администрирования автономного сервера.
В документации данное изменение описано здесь.
Автономный сервер.
Для автономного сервера реализованы следующие команды административного интерфейса:
  • session - работа со списком сеансов.
  • lock - работа с блокировками.
  • infobase config extension - работа с расширением.
  • infobase config data-separation list - получение списка имен общих реквизитов прикладного решения.
  • infobase config support disable - снимает конфигурацию с поддержки.
  • infobase config repair - выполняет тестирование и исправление информационной базы.

Для команды infobase config save:

  • Реализован параметр --db, обозначающий выполнение операции с конфигурацией базы данных.
  • Удален параметр --stage, обозначающий выполнение операции с основной конфигурацией.
  • По умолчанию команда выполняется с основной конфигурацией.

Для команды infobase config apply:

  • Реализован параметр --dynamic, позволяющий выполнять динамическое обновление конфигурации информационной базы.
  • Реализован параметр --session-terminate предназначенный для задания поведения при наличии сеансов, блокирующих установку монопольного режима доступа к информационной базе.

Для команды infobase config export реализован параметр --force, позволяющий принудительно выполнить полную выгрузку при использовании параметр --sync, если выясниться, что файлы конфигурации, расположенной на диске, имеют формат, отличающийся от формата выполнения текущей выгрузки.

Данные возможности не предоставлялись.Расширен административный интерфейс автономного сервера.
В документации данное изменение описано здесь.
Диаграммы.
Во встроенном языке стали недоступны следующе свойства объектов ДиаграммаГанта, Дендрограмма, СводнаяДиаграмма: РежимСглаживания, НатяжениеСглаживания. РежимПолупрозрачности, ПроцентПолупрозрачности, ВысотаГорлаВоронки, ШиринаГорлаВоронки, ПробелыВоронки, СоединениеЗначенийПоСериям, ЛинииСоединенияЗначенийПоСериям, ЦветСоединенияЗначенийПоСериям, ПорядокСерийВЛегенде, ОсьЗначений, ОсьТочек, ДополнительнаяОсьЗначений, ИсточникЗначенийОсиТочек, СерияНаОсиТочек, ИсточникЗначенияРазмераПузырька, ОбщаяСерияРазмераПузырька, ВлияниеРазмераНаПузырек, ОтображениеОтрицательныхЗначенийПузырьковойДиаграммы, РазмерПузырькаПоУмолчанию, МинимальныйРазмерПузырька, МаксимальныйРазмерПузырька, СоединениеТочек, ПорядокОтображенияТочекГоризонтальнойГистограммы, МаксимальноеКоличествоЦветовГрадиентнойПалитры, ЦветНачалаГрадиентнойПалитры, ЦветКонцаГрадиентнойПалитры, ИнформационныеЛинииЗначений, ИнформационныеИнтервалыЗначений, ИнформационныеЛинииТочек, ИнформационныеИнтервалыТочек, ОписаниеПалитрыЦветов, ОписаниеПалитрыЦветовИнформационныхИнтервалов, ИспользованиеНечисловыхЗначений, СоединениеТочекПриПропущенныхЗначениях, ВнутреннийРадиусКольцевойДиаграммы, ОтображениеПодсказкиЗначений, ЗаполнениеПодсказкиЗначений, РежимВыделенияОтображатьВсплывающуюИнформационнуюЛиниюТочек, ОтображатьВсплывающуюИнформационнуюЛиниюЗначений, РежимРедактированияЗначений.

Из встроенного языка стали недоступны следующе свойства объектов ОбластьПостроенияДиаграммыГанта, ОбластьПостроенияДендрограммы и ОбластьПостроенияСводнойДиаграммы: ШкалаТочек, ШкалаЗначений, ДополнительнаяШкалаЗначений, ШкалаСерий.

В режиме совместимости с версией 8.3.19 поведение не изменилось.

Указанные свойства были доступны из встроенного языка, но не оказывали никакого влияния.Исключен доступ к недокументированным свойствам объектов работы с диаграммами.
Средства администрирования.
Установка клиентского приложения.
Работа в ОС Linux.
Изменен формат установочных пакетов клиентских приложений для ОС Linux, которые используются при обновлении клиентских приложений через каталог distr. Имена файлов с дистрибутивами клиентских приложений имеют вид win-mac-clients-distr-ver.arch.run и all-clients-distr-ver.arch.run, где ver - это полный номер версии, а arch - архитектура процессора, для которого предназначен дистрибутив. Пакеты .deb и .rpm более не поддерживаются.

Реализована возможность устанавливать дистрибутивы клиентских приложений одновременно с установкой остальных компонентов системы «1С:Предприятие».

Установочные пакеты дистрибутивов клиентских приложений были доступны в формате .deb и .rpm пакетов. Не поддерживалась одновременная установка дистрибутива клиентского приложения одновременно с установкой других компонентов системы.Упрощена установка компонентов системы «1С:Предприятие» для ОС Linux. Установка дистрибутивов клиентских приложений максимально унифицирована с другими операционными системами.
В документации данное изменение описано здесь, здесь и здесь.
Табличный документ.
При экспорте табличного документа в формат Microsoft Excel, при вычислении высоты строк документа, содержащих многострочный текст (включая текст с автоматическим переносом строк), используется увеличенный межстрочный интервал.

Рекомендуется проверить корректность сохраняемых в формат Microsoft Excel табличных документов и, при необходимости, внести изменения в алгоритм формирования этих документов.

В режиме совместимости с версией 8.3.19 поведение не изменилось. +

При экспорте табличного документа в формат Microsoft Excel, при вычислении высоты строк документа, содержащих многострочный текст, использовался межстрочный интервал, равный таковому в табличном документе. Однако, межстрочные интервалы в табличном документе и Microsoft Excel различаются, что приводило к нарушению отображения документа.Документ Microsoft Excel, который получается в результате экспорта табличного документа, стал выглядеть более корректно.
В документации данное изменение описано здесь.
Оконная система.
При работе в интерфейсе Такси с помощью тонкого клиента или веб-клиента:
  • Если активная начальная страница, то метод АктивноеОкно() возвращает объект типа ФормаКлиентскогоПриложения, в котором:
    • Свойство НачальнаяСтраница установлено в значение Истина.
    • Свойство Содержимое содержит формы начальной страницы.
  • Для формы, размещенной на начальной странице, свойство Окно содержит объект типа ФормаКлиентскогоПриложения, в котором:
    • Свойство НачальнаяСтраница установлено в значение Истина.
    • Свойство Содержимое содержит формы начальной страницы.

Для активной начальной страницы, свойство формы начальной страницы Окно и метод АктивноеОкно() возвращают один и тот же объект.

В режиме совместимости с версией 8.3.19 поведение не изменилось.

При работе в интерфейсе Такси с помощью тонкого клиента или веб-клиента:
  • Если активная начальная страница, то метод АктивноеОкно() возвращало:
    • В тонком клиент - значение Неопределено.
    • В веб-клиенте - значение типа ОкноКлиентскогоПриложения, где свойство НачальнаяСтраница было установлено в значение Ложь.
  • Если активная начальная страница, то свойство Окно формы на начальной страницы возвращало:
    • В тонком клиент - значение Неопределено.
    • В веб-клиенте - значение Неопределено.
Устранено некорректное поведение системы.
Автономный сервер.
Системные требования.
Автономный сервер не поддерживает работу под управлением 32-разрядных ОС семейства Windows.Автономный сервер поддерживал работу под управлением 32-разрядных ОС семейства Windows.Прекращена поддержка 32-разрядных ОС семейства Windows автономным сервером.
В документации данное изменение описано здесь.
Автономный сервер.
Системные требования.
Автономный сервер не поддерживает работу под управлением 64-разрядных ОС Windows Server 2003 и Windows XP.Автономный сервер поддерживал работу под управлением 64-разрядных ОС Windows Server 2003 и Windows XP.Автономный сервер перестал поддерживать устаревшие ОС семейства Windows.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Метод проверки доступности видеоконференций системы взаимодействия. Старое наименование поддерживается для совместимости.
  • ВидеоконференцииДоступны().
  • ПоддерживаютсяВидеоконференции().
Англоязычное представление свойства СхемаКомпоновкиДанных.ВложенныеСхемыКомпоновкиДанных. Старое наименование поддерживается для совместимости.
  • NestedDataCompositionSchema.
  • NestedDataCompositionSchemas.
Свойство объекта НастройкиОбработкиОшибок, указывающее необходимость отправки отчета об ошибке. Старое наименование поддерживается для совместимости.
  • ОтправлятьОчет.
  • ОтправлятьОтчет.
Английское наименование свойства ПодписьМобильногоКлиента для объекта метаданных Конфигурация. Старое наименование поддерживается для совместимости.
  • MobileClientSign
  • MobileClientSignature

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
В мобильной платформе реализована возможность автоматизированного тестирования. Для работы автоматизированного тестирования в сети должна быть доступна информационная база менеджера тестирования, с которой и будет взаимодействовать мобильное приложение.

Для команды /TESTCLIENT командной строки запуска мобильного приложения реализован параметр -TURL, предназначенный для указания адреса публикации менеджера тестирования.

Автоматизированное тестирование было недоступно на мобильной платформе.Стало возможно использовать мобильную платформу для целей автоматизированного тестирования прикладных решений.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
При начале нового сеанса, кластер серверов автоматически завершает предыдущий сеанс работы, связанный с этим приложением мобильного клиента, если этот сеанс существует.

Если мобильный клиент подключается к кластеру серверов версии 8.3.19 и предыдущих версий или отображается список информационных баз, то приложение мобильного клиента явно отправляет запрос на завершение предыдущего сеанса, если этот сеанс не был завершен..

В модуле приложения реализованы обработчики событий ПриПробужденииКлиентскогоПриложения и ПриЗасыпанииКлиентскогоПриложения.

При сворачивании приложения или засыпании устройства, мобильный клиент не оповещал об этом кластер серверов. В результате сеанс не переходил в спящее состояние. Также было невозможно определить восстановление приложение после засыпания.Снижен расход лицензий для типовых схем использования приложения мобильного клиента, когда приложение не закрывается, а сворачивается.

Стало возможно определять засыпание и пробуждение мобильного приложения.

В документации данное изменение описано здесь.
Средства разработки.
Реализована стандартная обработка Сервис сборки мобильных приложений, которая предоставляет доступ к сервису сборки мобильных приложений, которые могут работать под управлением операционных систем Android и iOS. Сервис функционирует только при наличии доступа к сети Интернет. Для использования сервиса требуется регистрация на сайте для разработчиков (см. здесь).Данная возможность не предоставлялась.Сервис должен упростить и облегчить сборку мобильных приложений, которые работают под управлением операционных систем Android и iOS.
Мобильный клиент.
Мобильная платформа.
Для системных перечислений ПоведениеОбычнойГруппы и ОтображениеСтраницФормы реализовано значение Авто. При установке значения Авто особым образом обрабатывается отображение элементов формы на мобильном устройстве.Данная возможность не предоставлялась.

Было невозможно установить поведение системы таким образом, чтобы система автоматически изменяла поведение группы и страниц формы при работе на мобильном устройстве.

Упрощена разработка некоторых видов форм для работы на мобильных устройствах.
Мобильный клиент.
Для мобильного клиента реализована поддержка специализированного серверного приложения, развернутого на сервере взаимодействия. В том случае, когда на сервере взаимодействия развернуто такое приложение, повышается стабильность видеозвонков и расширяется количество одновременных участников видеоконференции. Мобильный клиент поддерживает все допустимые способы совершения видеозвонков.Мобильный клиент выполнял видеозвонки в режиме p2p, т.е. мобильный клиент обменивался видеопотоками с компьютерами всех участников видеозвонка.Повышена стабильность проведения видеозвонков из мобильного клиента, улучшено отображение участников видеозвонка.
Командный интерфейс.
Мобильный клиент.
В мобильном клиенте реализована поддержка свойства ПоложениеВКоманднойПанели кнопки формы. Поведение свойства аналогично платформе для персонального компьютера, со следующими исключениями:
  • Если в платформе для персонального компьютера значение Авто трактуется как ВКоманднойПанелиИВДополнительномПодменю, то в мобильном клиенте, в аналогичной ситуации, значение Авто будет трактоваться как ВКоманднойПанели.
  • Если у кнопки командной панели отображение установлено как ВКоманднойПанели, а кнопка не помещается в командную панель, будет установлен режим отображения ВДополнительномПодменю.
В мобильном клиенте поддержка свойства ПоложениеВКоманднойПанели кнопки формы была реализована ограничено: выполнялась только эмуляция свойства ТолькоВоВсехДействиях.Управление размещением кнопок в командной панели мобильного клиента унифицировано с клиентским приложением для персонального компьютера.

Оглавление

Система «1С:Аналитика»

ФункциональностьКак сталоКак былоРезультат изменения
Аналитика - дашборды.
Реализован специальный режим просмотра диаграмм и дашбордов. В этом режиме отключены функции редактирования, не требующиеся для анализа информации (раскладка элементов дашборда, добавление новых элементов). Режим включается автоматически для «чужих» диаграмм и дашбордов.Данная возможность не предоставлялась. Пользователь взаимодействовал со всеми объектами системы в режиме редактирования.Работать с данными дашборда стало удобнее.
Аналитика - диаграммы.
Изменен внешний вид панели выбора.У панели выбора был другой внешний вид.Улучшен внешний вид панели выбора диаграммы.
Аналитика - рабочий стол.
Реализована возможность передачи ссылок на свои папки другим пользователям.Данная возможность не предоставлялась..Пользователи могут делиться наборами диаграмм и дашбордов.
Аналитика - дашборды.
Реализована возможность настроить переход по ссылке при нажатии левой кнопкой мыши в любой точке элемента любого дашборда.Данная возможность не предоставлялась.Для дашбордов реализовано больше интерактивных возможностей.
Аналитика - дашборды.
Реализована возможность задавать стиль текста и указывать ссылки при редактировании текстовых элементов дашборда.Данная возможность не предоставлялась.Расширены возможности настройки текстовых элементов дашбордов.
Аналитика - диаграммы.
В диаграммах вида Сводная таблица реализована возможность закрепления строк и колонок.Данная возможность не предоставлялась.Реализована возможность более гибко настраивать отображение сводной таблицы.
Аналитика - дашборды.
Реализована возможность выполнять масштабирование диаграмм с помощью колеса мыши при одновременном нажатии клавиши Ctrl. Использование колеса мыши без клавиши Ctrl не приводит к масштабированию диаграммы.Масштабирование диаграмм выполнялось с помощью колеса мыши, без использования клавиатуры. Такое использование было неожиданным и мешало прокрутки дашборда.Масштабирование диаграмм стало более ожидаемым и не мешает прокрутке дашборда.
Аналитика - диаграммы.
Реализован новый тип диаграмм: линии с накоплением.Данная возможность не предоставлялась.Расширен перечень используемых типов диаграмм.
Аналитика - другое.
Объекты системы (диаграммы, дашборды, папки) автоматически удаляются из базы данных, если отсутствуют пользователи, которые используют эти объекты на своем рабочем столе.Данная возможность не предоставлялась.

Неиспользуемые объекты не удалялись из базы данных.

Оптимизировано использование базы данных системы «1С:Аналитика».
Аналитика - диаграммы.
Для диаграмм вида индикатор расширены возможности настройки и улучшен внешний вид.Внешний вид индикаторов определялся автоматически. Возможности настройки были ограничены.Улучшен внешний вид индикатора. Пользователь получил больше возможностей по настройке диаграммы данного типа.
Аналитика - диаграммы.
Для пузырьковой диаграммы реализована возможность вывода двух различных фактов на осях.Данная возможность не предоставлялась. Был доступен вывод только следующих комбинаций: факт-измерение и измерение-измерение.Расширены возможности визуализации для пузырьковой диаграммы.
Аналитика - другое.
Для системы «1С:Аналитика» реализован Центр оповещений, в котором сохраняются для просмотра последние сообщения системы.Данная возможность не предоставлялась.

После исчезновения оповещения с ошибкой его нигде нельзя было посмотреть.

Информирование о проблемах системы стало более простым.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Автономный сервер.
Выгрузка/загрузка конфигурации в файлы.
Оптимизировано использование некоторого количества операций с информационной базой, которые выполняются с помощью утилиты администрирования (ibcmd) путем подключения к работающему экземпляру автономного сервера. К перечню оптимизированных операций (но не ограничиваясь им) относятся: выгрузка конфигурации в XML-файлы, частичная загрузка конфигурации из XML-файлов. обновление конфигурации базы данных.Выполнение некоторого количества операций с информационной базой, которые выполняются с помощью утилиты администрирования (ibcmd) путем подключения к работающему экземпляру автономного сервера занимало больше времени.Ускорено выполнение некоторых операций с информационной базой, работающей под управлением автономного сервера.
Автономный сервер.
Средства разработки.
Для интерактивной программы запуска реализована возможность запуска 1C:Enterprise Development Tools. Если 1C:Enterprise Development Tools не установлены, то предлагается выполнить установку продукта. Видимость кнопки управляется с помощью флажка диалога настройки интерактивной программы запуска.

Для информационной базы, подключение к которой выполняется по протоколу HTTP(s), в настройках подключения реализована возможность указания адреса управления разработки. Эта возможность доступна после нажатия гиперссылки Дополнительно, если база расположена на веб-сервере.

Данная возможность не предоставлялась.

Интерактивная программа запуска не поддерживала работу с 1C:Enterprise Development Tools.

Расширены возможности интерактивной программы запуска. Улучшена интеграция 1C:Enterprise Development Tools и других компонентов системы программ «1С:Предприятие».
В документации данное изменение описано здесь и здесь.
Автономный сервер.
В административном интерфейсе автономного сервера по протоколу SSH реализована возможность получения информации об отладчике (infobase-tools debug-info). В набор параметров, который возвращается командой, добавлен необязательный параметр infobase-name, который содержит имя отлаживаемой информационной базы.Данная возможность не предоставлялась.Упрощено подключения отладчика 1C:Enterprise Development Tools к информационной базе, работающей под управлением автономного сервера.
Средства разработки.
Автономный сервер.
Выгрузка/загрузка конфигурации в файлы.
Для команд импорта конфигурации из XML-файлов реализована возможность отключать проверку целостности загружаемой конфигурации. Такая проверка может оказаться полезной в том случае, когда загружается ранее выгруженная конфигурация.

Для выполнения данной задачи реализован специальный параметр для следующих инструментов загрузки:

  • Командная строка запуска конфигуратора. Для команды /LoadConfigFromFiles реализован параметр -NoCheck.
  • Конфигуратор в режиме агента. Для команды config load-config-from-files реализован параметр --no-check.
  • Утилита управления автономным сервером (ibcmd). Для команды infobase config import реализован параметр --no-check.
Данная возможность не предоставлялась.Для некоторых сценариев работы, снижено время, которое будет затрачено для загрузки конфигурации из XML-файлов.
В документации данное изменение описано здесь и здесь.
Веб-клиент.
При запуске веб-клиента реализована возможность автоматического открытия формы стандартной функции. Открытие форм стандартных обработок из встроенного языка или пользовательского интерфейса клиентского приложения (переход по ссылке) не поддерживается.Данная возможность не предоставлялась.Стало возможно открывать стандартные функции при работе из 1C:Enterprise Development Tools.
В документации данное изменение описано здесь.
Клиентское приложение.
Реализована возможность запрещать открытие форм начальной страницы при открытии клиентского приложения. Для командной строки запуска тонкого клиента и веб-клиента реализована команда DisableHomePageForms.Данная возможность не предоставлялась.Реализована возможность открыть клиентское приложение с минимальными задержками.
В документации данное изменение описано здесь и здесь.
Средства разработки.
Автономный сервер.
Выгрузка/загрузка конфигурации в файлы.
При импорте конфигурации из XML-файлов реализована возможность импорта из ZIP-архива, содержащего XML-файлы конфигурации. Структура архива должна соответствовать структуре каталога загрузки.

Команда Конфигуратора Загрузить конфигурацию из файлов позволяет выбрать не только каталог, но и файл ZIP-архива.

Для выполнения данной задачи реализован специальный параметр для следующих инструментов загрузки:

  • Командная строка запуска конфигуратора. Для команды /LoadConfigFromFiles реализован параметр -Archive.
  • Конфигуратор в режиме агента. Для команды config load-config-from-files реализован параметр --archive.
  • Утилита управления автономным сервером (ibcmd). Для команды infobase config import files реализован параметр --archive. Для команд infobase config import и infobase config import all-extensions неименованый параметр может указывать как на каталог, так и на ZIP-архив. Для команды infobase create параметр --import может содержать как путь к каталогу, так и имя ZIP-архива.
Данная возможность не предоставлялась.Стало возможно сократить время загрузки файлов конфигурации, особенно, если перед загрузкой выполняется передача загружаемых файлов по каналам связи.
В документации данное изменение описано здесь, здесь и здесь.
Автономный сервер.
Автономный сервер формирует некоторые стандартные текстовые сообщения в стандартный поток вывода (stdout) после выполнения некоторых действий:
  • По факту готовности автономного сервера и после завершения обновления внутреннего состояния: 1C:Enterprise 8.3 (x86-64) (<номер версии>) Stand-alone Server ready.
  • После обновление конфигурации информационной базы (во время обновления внутреннего состояния): 1C:Enterprise 8.3 (x86-64) (<номер версии>) Stand-alone Server refreshing.
Данная возможность не предоставлялась.Упрощено получение статуса автономного сервера при выполнении некоторых команд управления.
Средства разработки.
Автономный сервер.
Реализована возможность получать идентификатор поколения метаданных конфигурации информационной базы. Данный идентификатор изменяется при выполнении любой операции изменения конфигурации.

Для выполнения данной задачи реализованы команды для следующих инструментов загрузки:

  • Командная строка запуска конфигуратора. Реализована команды /GetConfigGenerationID.
  • Конфигуратор в режиме агента. Реализована команда config generation-id.
  • Утилита управления автономным сервером (ibcmd). Реализована команда infobase config generation-id.
Данная возможность не предоставлялась.Реализована возможность определить, что конфигурация информационной базы не изменялась с момента последней проверки.
В документации данное изменение описано здесь и здесь.
Средства разработки.
Выгрузка/загрузка конфигурации в файлы.
При полной загрузке конфигурации из XML-файлов игнорируется тот факт, что в конфигурации настроены правила поддержки. Выполняется полная замена конфигурации, включая информацию о поддержке.Полная загрузка конфигурации из XML-файлов была невозможна, если в конфигурации были настроены правила поддержки. Для полной загрузки конфигурации из XML-файлов было необходимо снять конфигурацию с поддержки.Поведение при полной загрузке из XML-файлов приведено к поведению при загрузке конфигурации из CF-файла.
Средства разработки.
Модифицирован формат JSON-сообщений, которые используются при работе с конфигуратором в режиме агента. Для сообщения с типом questions реализована возможность указания более двух вариантов ответа на вопрос.В JSON-сообщениях (при работе с конфигуратором в режиме агента) с типом questions было возможно указывать только два варианта ответа на вопрос.Расширены возможности формата JSON-сообщений, которые используются при взаимодействии с конфигуратором в режиме агента.
Автономный сервер.
Выгрузка/загрузка конфигурации в файлы.
В автономном сервере прекращена поддержка линейного формата для загрузки конфигурации из XML-файлов. Для загрузки конфигурации из XML-файлов используется только иерархический формат.Автономный сервер поддкрживал возможность загрузки конфигурации из XML-файлы в линейном и иерархическом форматах.В автономном сервере прекращена поддержка устаревшего формата выгрузки.
В документации данное изменение описано здесь и здесь.
Хранение настроек.
Если выполняется обращение к свойствам объекта СтандартноеХранилищеНастроекВыборка в том случае, когда выборка закончена или она (выборка) пустая - формируется восстановимая ошибка встроенного языка.

Рекомендуется проанализировать места использования объекта СтандартноеХранилищеНастроекВыборка на предмет возможного появления ошибок, возникающих из-за окончания выборки (или пустой выборки).

В режиме совместимости с версией 8.3.19 поведение не изменилось.

При обращении к свойствам объекта СтандартноеХранилищеНастроекВыборка в разных случаях наблюдалось различное поведение:
  • Если выборка закончилась - в свойствах объекта оставались последние прочитанные значения.
  • Если выборка была пустой - в свойствах объекта находятся значения Неопределено.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
Снижено время исполнения запроса, который использует поля временных таблиц, которые получены из других временных таблиц с большой вложенностью.Исполнения запроса, который использует поля временных таблиц, которые получены из других временных таблиц с большой вложенностью, требовало больше времени.В некоторых случаях ускорено выполнение запросов.
Веб-клиент.
Работа с XML, XDTO.
Для свойства глобального контекста ОбработкаСтрокиXML реализована доступность в веб-клиенте.Свойство глобального контекста ОбработкаСтрокиXML было недоступно в веб-клиенте.В веб-клиенте стали доступны методы поиска и удаления недопустимых символов XML в произвольных строках.
Средства печати.
Если принтер, который используется для печати платформой «1С:Предприятие», является доступным - платформа кеширует эту информацию. Если в течение последующих 60 секунд для печати используется этот же принтер - состояние доступности получается из кеша.При множественных последовательных обращениях к одному и тому же принтеру, доступность принтера определялась по фактическому состоянию принтера при каждой попытке выполнения печати.Повышена скорость печати в том случае, когда последовательно печатаются несколько документов на один и тот же принтер.
Работа с СУБД.
При использовании СУБД PostgreSQL, результат работы функций МИНИМУМ() и МАКСИМУМ() языка запросов для поля типа Булево не зависит от того, в каком порядке в выборке представлены значения типа Булево и NULL.При использовании СУБД PostgreSQL, результат работы функций МИНИМУМ() и МАКСИМУМ() языка запросов для поля типа Булево зависел от того, в каком порядке в выборке представлены значения типа Булево и NULL.Устранено некорректное поведение системы. Функции языка запросов МИНИМУМ() и МАКСИМУМ() работают одинаково на всех поддерживаемых СУБД.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность повторной регистрации информационной базы в системе взаимодействия без явного указания адреса электронной почты после отключения базы от системы взаимодействия. Повторная регистрация будет выполнена на тот же адрес электронной почты, на который выполнялась первичная регистрация. После повторной регистрации будет восстановлен доступ ко всем ранее созданным объектам системы взаимодействия. Если информационная база ни разу не подключалась к системе взаимодействия, выполнить повторную регистрацию без указания адреса электронной почты будет невозможно.

Свойство ПараметрыРегистрацииИнформационнойБазыСистемыВзаимодействия.АдресЭлектроннойПочты не является обязательным.

Реализована возможность выполнить повторную регистрацию для стандартной обработки Управление системой взаимодействия.

Повторная регистрация информационной базы в системе взаимодействия могла быть выполнена только с указанием адреса электронной почты.Стало возможно восстановить регистрация информационной базы в системе взаимодействия в том случае, если базу отключили от системы взаимодействия, а адрес электронной почты, на который выполнялась регистрация, оказался забыт.
В документации данное изменение описано здесь.
Локализация.
Реализована возможность использовать туркменский язык (код tk) в следующих случаях:
  • Для указания в диалоге региональных настроек информационной базы.
  • Для указания в качестве кода локализации сеанса (параметр командной строки запуска /VL).
  • Просматривать календарь на туркменском языке.
Данные возможности не предоставлялись.В платформе реализована ограниченная поддержка туркменского языка.
Система компоновки данных.
Мобильная платформа.
Мобильный клиент.
В таблицах, отображающих настройки системы компоновки данных в мобильном клиенте и приложении для мобильной платформы, команды Свойства элемента пользовательских настроек, Установить представление, Использовать в качестве значения поле, Установить заголовок, Развернуть, Сгруппировать, Сгруппировать условия, Сгруппировать поля и Разгруппировать, доступны только в контекстном меню соответствующей строки таблицы. Изменения касаются форм настроек отчета, настроек динамического списка и редактирования варианта отчета.В таблицах, отображающих настройки системы компоновки данных в мобильном клиенте и приложении для мобильной платформы, команды Свойства элемента пользовательских настроек, Установить представление, Использовать в качестве значения поле, Установить заголовок, Развернуть, Сгруппировать, Сгруппировать условия, Сгруппировать поля и Разгруппировать, были доступны в контекстном меню соответствующей строки таблицы и в меню формы Еще. При этом команда из меню Еще не вызывала какого-либо действия.Устранено некорректное поведение системы.
Система взаимодействия.
Состояние настройки Помечать как прочитанное (диалог настройки системы взаимодействия) сохраняется на сервере взаимодействия. Если на сервере взаимодействия такой настройки нет - выполняется попытка чтения настройки из локального хранилища.Состояние настройки Помечать как прочитанное (диалог настройки системы взаимодействия) сохранялось в локальном хранилище на компьютере пользователя.Значение настройки Помечать как прочитанное (диалог настройки системы взаимодействия) стало одинаковым для любого устройства, на котором работает пользователь.
Работа с запросами.
Клиентское приложение.
В конструкторе запросов, который работает в тонком клиенте, реализованы команды поиска и отмены поиска во всех списках формы конструктора. Команды доступны в контекстном меню или меню Еще.

+

В конструкторе запросов, который работает в тонком клиенте, в списках формы конструктора были недоступны команды поиска и отмены поиска. Поиск и отмена поиска были доступны только с помощью горячих клавиш, что было непонятно пользователям.Использование поиска в конструкторе запроса тонкого клиента стало более понятным для пользователя.
Мобильная платформа.
Мобильный клиент.
Переработан диалог выбора файлов для мобильного приложения, которое работает под управлением ОС Android или iOS. Диалог стал более удобным и быстрым. Реализована возможность создания файла непосредственно из диалога выбора файлов. Для пользователя реализована возможность переключить диалог в режим множественного выбора (если этот режим доступен).

Диалог позволяет настраивать разделы, которые будут доступны при выборе файла. Реализовано свойство ДиалогВыбораФайлов.Разделы.

Реализована возможность фильтрации файлов по MIME-типу. Реализовано свойство ДиалогВыбораФайлов.ТипСодержимого.

Диалог выбора файлов для мобильного приложения, работающего под управлением ОС Android и iOS был менее удобным и более медленным.Улучшена работа диалога выбора файлов в мобильном приложении, работающем под управлением ОС Android и iOS.
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.19 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.19 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Работа в ОС Linux.
Системные требования.
Реализована поддержка следующих дистрибутивов операционной системы Linux:
  • Debian 10,
  • Mint 20,
  • Oracle Linux 7,
  • Oracle Linux 8,
  • RHEL 8,
  • Ubuntu 20.04 LTS,
  • Альт Образование 10,
  • Альт Рабочая станция 10,
  • Альт Рабочая станция К 10,
  • Альт Сервер 10 (только 64-х битный вариант),
  • РЕД ОС 7.3 (только 64-х битный вариант).
Данные дистрибутивы не поддерживались.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа в ОС Linux.
Системные требования.
Прекращена поддержка следующих дистрибутивов операционной системы Linux:
  • Centos 6,
  • Debian 8,
  • RHEL 6,
  • Ubuntu 14.04 LTS,
  • Ubuntu 16.04 LTS,
  • Альт Образование 8,
  • Альт Рабочая станция 8,
  • Альт Рабочая станция К 8,
  • Альт Сервер 8.
Система «1С:Предприятие» поддерживала работу в следующих дистрибутивах операционной системы Linux::
  • Centos 6,
  • Debian 8,
  • RHEL 6,
  • Ubuntu 14.04 LTS,
  • Ubuntu 16.04 LTS,
  • Альт Образование 8,
  • Альт Рабочая станция 8,
  • Альт Рабочая станция К 8,
  • Альт Сервер 8.
Прекращена поддержка устаревших дистрибутивов операционной системы Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Системные требования.
Реализована поддержка операционной системы Microsoft Windows 11.Операционная система Microsoft Windows 11 не поддерживалась.Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Сервис интеграции.
Для сервиса интеграции реализована возможность передачи сообщений с данными существенного размера (сотни мегабайт).

Метод СообщениеСервисаИнтеграции.ПолучитьТелоКакПоток() возвращает поток, для которого всегда недоступно изменение позиции, а возможность чтения и записи зависят от того, для какого сообщения вызывается метод.

Свойство СообщениеСервисаИнтеграции.ДатаУстаревания доступно только для чтения. Установку значения свойства можно выполнять только при создании сообщения. Для метода СервисИнтеграцииМенеджер.СоздатьСообщение() реализован параметр ДатаУстаревания.

Реализовано свойство СообщениеСервисаИнтеграции.РазмерТела.

Попытка передачи сообщений с данными существенного размера могло приводить к различным побочным эффектам и невозможности использования сервиса интеграции.

Поток, который возвращался методом СообщениеСервисаИнтеграции.ПолучитьТелоКакПоток() был всегда доступен на запись и чтение.

Свойство СообщениеСервисаИнтеграции.ДатаУстаревания было доступно на запись.

Повышена стабильность работы сервиса интеграции с сообщениями существенного размера.
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Результатом выполнения обещания, которое получено при использовании метода ПолучитьДанныеАсинх() менеджера безопасного хранилища, будет значение Неопределено, если пользователь не дал согласие на получение данных.Результат выполнения обещания, которое получено при использовании метода ПолучитьДанныеАсинх() менеджера безопасного хранилища, не позволял определить, что произошло во время выполнения метода: ошибка времени исполнения или пользователь не дал согласия на получение данных.При использовании метода ПолучитьДанныеАсинх() менеджера безопасного хранилища стало возможно различить ошибку времени исполнения и ситуацию, когда пользователь не дал согласие на получение данных.
В документации данное изменение описано здесь.
Системные требования.
Реализована поддержка операционной системы Microsoft Windows Server 2022.Операционная система Microsoft Windows Server 2022 не поддерживалась.Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Система аналитики.
В основном меню консоли администрирования системы 1С:Аналитика реализована возможность получения доступа к описанию программного интерфейса системы.

Реализована возможность изменять настройки сервера системы 1С:Аналитика с помощью объекта встроенного языка СоединениеССерверомАналитики.

Встроенный язык системы «1С:Предприятие» позволял читать и записывать параметры сервера системы 1С:Аналитика, но не позволял изменять эти параметры, т.к. они не были документированы.Реализована возможность изменять настройки сервера системы 1С:Аналитика с помощью объекта встроенного языка СоединениеССерверомАналитики.
Автономный сервер.
При использовании автономного сервера, серверная лицензия требуется в следующих случаях:
  • При работе утилиты ibcmd в клиент-серверном варианте.
  • При подключении к автономному серверу в клиент-серверном варианте по протоколу SSH.

При работе с файловой информационной базой, а также в том случае, если утилита ibcmd работает с информационной базой без подключения к автономному серверу, серверная лицензия не требуется.

При использовании автономного сервера, серверная лицензия требовалась при работе утилиты ibcmd и самого автономного сервера по протоколу SSH в любом случае, кроме использования файловой информационной базы с количество одновременных сеансов не более 3.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
В сервисе сборки мобильных приложений реализована возможность сборки платформы разработчика.Данная возможность не предоставлялась.Расширены возможности сервиса сборки мобильных приложений.
Работа с криптографией.
Веб-клиент.
Для менеджера криптографии реализована поддержка стандарта усовершенствованых подписей CAdES. CAdES определяет стандарт электронной подписи, которая сохраняет свою действительность в течение длительного промежутка времени.

Для объекта МенеджерКриптографии реализовано свойство АдресаСерверовМетокВремени. Для методов Подписать(), ПодписатьАсинх() и НачатьПодписывание() объекта МенеджерКриптографии реализован параметр ТипПодписиКриптографии. Для методов ПроверитьПодпись(), ПроверитьПодписьАсинх() и НачатьПроверкуПодписи() объекта МенеджерКриптографии реализован параметр ПроверятьДополнительныеАтрибуты.

Для объекта МенеджерКриптографии реализованы методы УсовершенствоватьПодпись(), УсовершенствоватьПодписьАсинх(), НачатьУсовершенствованиеПодписи(), ДобавитьАрхивнуюМеткуВремени(), ДобавитьАрхивнуюМеткуВремениАсинх(), НачатьДобавлениеАрхивнойМеткиВремени().

Для объекта ХранилищеСертификатовКриптографии реализованы методы ОбновитьСпискиОтзываСертификатов(), ОбновитьСпискиОтзываСертификатовАсинх(), НачатьОбновлениеСпискаОтзываСертификатов(), ПроверитьМеткуВремени(), ПроверитьМеткуВремениАсинх(), НачатьПроверкуМеткиВремени(), ПолучитьКонтейнерПодписейКриптографии(), ПолучитьКонтейнерПодписейКриптографииАсинх(), НачатьПолучениеКонтейнераПодписейКриптографии().

Усовершенствованная электронная подпись не поддерживается при использовании расширения криптографии в веб-браузере Safari. Усовершенствованная электронная подпись может не поддерживаться в последних версиях Internet Explorer, работающих под управлением операционной системы Windows 10. В этом случае рекомендуется использовать предыдущие версии этого веб-браузера или веб-браузеры Mozilla Firefox и Google Chrome.

Данная возможность не предоставлялась.Расширены возможности работы с криптографией в системе «1С:Предприятие».
В документации данное изменение описано здесь.
Веб-клиент.
Внешние компоненты.
При работе веб-клиента под управлением ОС Linux, расширения работы с файлами и криптографией, а также адаптеры внешних компонент стали использовать библиотеку GTK-3.При работе веб-клиента под управлением ОС Linux, расширения работы с файлами и криптографией, а также адаптеры внешних компонент требовали библиотеку GTK-3.Для работы в веб-клиенте под управлением ОС Linux внешних компонент, расширений работы с файлами и криптографией, необходимо, чтобы на компьютере была доступна библиотека GTK-3.
В документации данное изменение описано здесь.
Средства администрирования.
Реализован файл cacertnx.pem, который используется тонким клиентом, толстым клиентом и кластером серверов для проверки отзыва сертификатов. В файлы cacert.pem и cacertnx.pem добавляются корневые сертификаты доверенных удостоверяющих центров.

При установке тонкого клиента или полного дистрибутива (с помощью msi-файла) реализована возможность обновления файла cacertnx.pem. +Система «1С:Предприятие» выполняет проверку отзыва сертификатов следующим образом:

  • В режиме совместимости Версия 8.3.8 и последующих режимах совместимости: выполняется проверка с помощью файла cacertnx.pem, затем с помощью используемой операционной системы.
  • В режиме совместимости Версия 8.3.7 и предшествующих режимах совместимости: выполняется проверка только с помощью файла cacert.pem.
Данные возможности не предоставлялась.Расширены возможности проверки отзыва сертификатов.
В документации данное изменение описано здесь.
Средства администрирования.
При аутентификации с помощью ЕСИА реализована поддержка алгоритмов хеширования, реализованных в соответствии с ГОСТ.При аутентификации с помощью ЕСИА не поддерживались алгоритмы хеширования, реализованные в соответствии с ГОСТ.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.20 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.20 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Сборщик мобильных приложений.
В сервисе сборки мобильных приложений реализована поддержка мобильной версии 8.3.22 системы «1С:Предприятие».Сервис сборки мобильных приложений не поддерживал мобильную версию 8.3.22 системы «1С:Предприятие».Для сервиса сборки мобильных приложений расширен список поддерживаемых мобильных версии системы «1С:Предприятие».
Работа с XML, XDTO.
Если при работе с XML возникает ошибка, то сообщение об ошибке содержит причину ошибки, которая указывается в библиотеке, которую для работы с XML использует «1С:Предприятие».Если при работе с XML возникает ошибка, то сообщение об ошибке не содержало причину ошибки, которая указывалась в библиотеке, которую для работы с XML использует «1С:Предприятие».Устранено некорректное поведение системы.

Упрощена диагностика некоторых проблем при работе с XML.

Работа с СУБД.
Кластер серверов.
Реализована возможность защищенного соединения между кластером серверов и СУБД PostgreSQL с использованием протокола SSL.Данная возможность не предоставлялась.Устранено некорректное поведение системы.
Автономный сервер.
Выгрузка/загрузка конфигурации в файлы.
Оптимизировано использование оперативной памяти Конфигуратором и автономным сервером при загрузке конфигурации из xml-файлов.

Ускорена загрузка конфигурации из xml-файлов Конфигуратором и автономным сервером.

Конфигуратор и автономный сервер при загрузке конфигурации из xml-файлов использовали больше оперативной памяти.

Конфигуратор и автономный сервер тратили больше времени на загрузку конфигурации из xml-файлов.

Снижено использование оперативной памяти и ускорена загрузка конфигурации из xml-файлов Конфигуратором и автономным сервером.
Средства администрирования.
Расширен список поддерживаемых корневых сертификатов.Список поддерживаемых корневых сертификатов был меньшего размера.Расширен список поддерживаемых корневых сертификатов.
Кластер серверов.
При работе системы «1С:Предприятие» в клиент-серверном варианте восстановлены индексы для таблиц, связанных с пользователями информационной базы, если работа выполняется с использованием СУБД IBM Db2, Oracle Database и PostgreSQL.

После обновления платформы рекомендуется выполнить подключение к информационной базе одного пользователя (для восстановления индексов) перед тем, как будет выполняться штатное подключение остальных пользователей.

При работе системы «1С:Предприятие» в клиент-серверном варианте отсутствовали индексы для таблиц, связанных с пользователями информационной базы, если работа выполнялась с использованием СУБД IBM Db2, Oracle Database и PostgreSQL. В результате существенно замедлялся поиск пользователя по имени, и, как следствие, подключение новых пользователей к информационной базе (при большом количестве пользователей).Устранено незапланированное поведение системы.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
Снижено потребление оперативной памяти расширением веб-сервера при работе под управлением ОС Windows.Расширение веб-сервера при работе под управлением ОС Windows использовало больше оперативной памяти.Снижено потребление оперативной памяти расширением веб-сервера при работе под управлением ОС Windows.

Оглавление

Переход с предыдущей версии на версию 8.3.20

Оглавление

Версия 8.3.19

Версия 8.3.19 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8319doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.18.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.17. +Возможность запуска конфигураций, разработанных в версии 8.3.18 и более младших, в версии 8.3.19, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.19 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.19, при необходимости, использовать для работы с информационной базой и версию 8.3.18. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Документация.
Для синтакс-помощника реализована возможность отобрать объекты, которые доступны в мобильном автономном сервере.

Для синтакс-помощника реализован режим доступности Мобильный автономный сервер. Данный режим доступности описывает объекты и методы, которые доступны на стороне сервера «1С:Предприятия», работающего на мобильном устройстве в автономном режиме мобильного клиента. +

В синтакс-помощнике было невозможно отобрать объекты, которые доступны на мобильном устройстве, в серверной части мобильного клиента, работающего в автономном режиме.В синтакс-помощнике учтены новые возможности мобильной версии «1С:Предприятия».
В документации данное изменение описано здесь.
Навигационные ссылки.
Реализована возможность указывать дополнительные параметры в навигационных ссылках. Состав параметров зависит от вида ссылки. Реализована возможность выполнять следующие действия:
  • Передавать дополнительные параметры для открываемой формы.
  • Получать навигационную ссылку на вариант отчета.
  • Получать навигационную ссылку на полные настройки отчета.
  • Получать навигационную ссылку на динамический список с настройками.
  • Получать навигационную ссылку на текущую строку динамического списка с настройками.
  • Получать навигационную ссылку на команду и передавать в нее параметры.

Диалог получения навигационной ссылки (при необходимости) предоставляет выбор - какую навигационную ссылку необходимо получить в конкретном месте интерфейса клиентского приложения.

Для расширения формы клиентского приложения для отчета реализованы методы ПолучитьНавигационнуюСсылкуОтчета(), ПолучитьНавигационнуюСсылкуТекущегоВариантаОтчета(), ПолучитьНавигационнуюСсылкуТекущихНастроекОтчета().

Для расширения формы клиентского приложения для обработки реализован метод ПолучитьНавигационнуюСсылкуОбработки().

Для расширения формы клиентского приложения для динамического списка реализованы методы ПолучитьНавигационнуюСсылкуСписка(), ПолучитьНавигационнуюСсылкуТекущихНастроекСписка(). Реализован параметр формы клиентского приложения для динамического списка ОтображениеТаблицы.

Для расширения формы клиентского приложения для объекта, документа, справочника, бизнес-процесса, задачи, плана видов характеристик, объекта таблицы внешнего источника данных реализован метод ПолучитьНавигационнуюСсылкуОбъекта().

Для расширения формы клиентского приложения для записи регистра сведений и записи таблицы внешнего источника данных реализован метод ПолучитьНавигационнуюСсылкуЗаписи().

Для метода глобального контекста ПолучитьНавигационнуюСсылку() реализованы возможности получения всех перечисленных вариантов навигационных ссылок.

Для формы клиентского приложения реализованы обработчики ОбработкаПолученияСпискаНавигационныхСсылок и ОбработкаПолученияНавигационнойСсылки.

Реализовано свойство конфигурации ХранилищеВнешнихДанныхНавигационныхСсылок.

Изменен формат выгрузки конфигурации в формате XML.

Данные возможности не предоставлялись.Расширены возможности использования навигационных ссылок.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Форма клиентского приложения.
Для расширений поля формы для HTML-документа, форматированного документа, географической схемы, планировщика реализовано событие ПередПечатью, которое возникает перед интерактивной печатью объекта.

Для расширений поля формы для HTML-документа и форматированного документа реализовано событие ПередЗаписью, которое возникает перед интерактивной записью объекта.

Для расширений поля формы для HTML-документа и форматированного документа реализовано событие ПослеЗаписи, которое возникает после интерактивного сохранения объекта.

Команда формы клиентского приложения Сохранить, вызванная для табличного документа, выполняет следующие действия:

  • Если не задано имя файла или табличный документ не находится в режиме редактирования - формируется диалог указания имени сохраняемого файла.
  • Если имя файла указано и табличный документ находится в режиме редактирования, то выполняется сохранение без отображения диалога указания имени файла.

После сохранения табличного документа выводится оповещение о завершении операции.

Для всех видов элементов формы, поддерживающих возможность сохранения (кроме табличного документа), в параметр Копирование обработчика события ПередЗаписью передается значение, соответствующее выполняемому действию:

  • Истина - если выбрана команда Сохранить как.
  • Ложь - если выбрана команда Сохранить.

Для табличного документа или отчета поведение при выборе команды Сохранить не изменилось.

Для всех видов элементов формы, поддерживающих возможность сохранения, поведение системы при указании команд Сохранить и Сохранить как было одинаковым: формировался диалог выбора файла для сохранения.

Для всех видов элементов формы, поддерживающих возможность сохранения (кроме табличного документа), в параметр Копирование обработчика события ПередЗаписью всегда передавалось значение Истина. Для табличного документа при выборе команды Сохранить для табличного документа или отчета в обработчик ПередЗаписью в параметре Копирование передавалось значение Ложь.

Обработчики событий ПередПечатью, ПередЗаписью и ПослеЗаписи реализованы для всех элементов формы клиентского приложения, поддерживающих возможность сохранения и печати.
Клиентское приложение.
Изменены пиктограммы всех исполняемых файлов системы «1С:Предприятие», а также пиктограммы, ассоциированные с различными расширениями файлов, связанными с системой «1С:Предприятие».Пиктограммы исполняемых и формируемых файлов системы «1С:Предприятие» были другими.Пиктограммы нарисованы в едином стиле.
Картинки.
Реализована поддержка SMIL-анимации картинок в формате SVG. SMIL-анимация не поддерживается в веб-браузере Microsoft Internet Explorer и Microsoft Edge до версии 18 включительно. В веб-браузерах, которые не поддерживают SMIL-анимацию, будет выводиться статическая картинка.

В наборе вариантов картинок реализована возможность указать, для какого веб-браузера предназначен элемент варианта. При выводе картинки в веб-браузере вначале делается попытка определить вариант для используемого веб-браузера.

Рекомендуется использовать SVG-картинки со SMIL-анимацией для создания анимированных картинок в прикладном решении. Такие картинки занимают немного места и не требуют больших ресурсов для своего отображения.

Данная возможность не предоставлялась.Реализована возможность отображения анимированных SVG-картинок. Анимация отображается как в обычных клиентских приложениях, так и в веб-клиенте (кроме веб-браузеров Microsoft Internet Explorer и Microsoft Edge версии до 18 включительно).
В документации данное изменение описано здесь, здесь и здесь.
Динамический список.
Для динамического списка реализованы возможности, аналогичные возможностям которые имеются в системе компоновки данных:
  • Настройка полей запроса (заголовок, тип, оформление, ограничение использования и т.д.).
  • Работа с вычисляемыми полями.
  • Использование параметров в настройках пользователя.
  • Настройка свойств параметров (заголовок, тип и т.д.).
  • Для полей типа Дата реализована возможность работы с дочерними полями (начало дня, месяца и т.д.) в сортировке и группировке.

Изменен редактор настроек динамического списка.

Для динамического списка реализованы свойства Поля, ВычисляемыеПоля, ПараметрыДанных. Изменен формат выгрузки конфигурации в формате XML.

Методы динамического списка УстановитьОграниченияИспользованияВГруппировке(), УстановитьОграниченияИспользованияВОтборе(), УстановитьОграниченияИспользованияВПорядке(), ПолучитьОграниченияИспользованияВГруппировке(), ПолучитьОграниченияИспользованияВОтборе(), ПолучитьОграниченияИспользованияВПорядке() объявляются устаревшими и не рекомендуются к использованию. Рекомендуется использовать свойства динамического списка ОграничениеИспользования и ОграничениеИспользованияРеквизитов полей динамического списка.

В режиме совместимости с версией 8.3.18 поведение не изменилось. +

Данные возможности не предоставлялись.Упрощена настройка полей динамического списка. В частности стало возможно указывать локализованные представления полей запроса, которые отображаются в динамическом списке.
Система компоновки данных.
Динамический список.
При настройке характеристик объектов конфигурации реализована возможность указать, какое поле объекта конфигурации содержит имя характеристики. В результате изменение представления характеристики не будет приводить к «потере» полей настроек системы компоновки данных или динамического списка.

Реализовано свойство ОписаниеХарактеристик.ПолеПутиКДанным.

В качестве представления характеристики используется значение, которое возвращает виртуальное поле Представление. Для существующих характеристик новое поле не заполняется.

Рекомендуется при смене в описании характеристик поля, содержащего имя характеристики, предусмотреть механизм, конвертирующий настройки компоновки данных, заменяя старое имя характеристики на новое.

Изменен формат выгрузки конфигурации в формате XML.

В качестве имени характеристики использовалось представление этой характеристики. Изменение представления характеристики приводило к тому, что настройки системы компоновки данных и динамического списка «теряли» характеристики.Упрощено создание локализуемых представлений характеристик в прикладных решениях.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
Клиентское приложение, работающее под управлением ОС Windows, для видеозвонков использует модуль работа с видео, соответствующий разрядности операционной системы.Клиентское приложение, работающее под управлением ОС Windows, для видеозвонков использовало модуль работа с видео, соответствующий разрядности клиентского приложения.При использовании видеозвонка ресурсы компьютера используются более эффективно.
Клиентское приложение.
Веб-клиент.
Для интерфейса Такси реализована поддержка языков с написанием справа-налево (в тонком и толстом клиентских приложениях). Данный режим поддерживается во всем интерфейсе клиентского приложения автоматически.

Необходимость изменения интерфейса определяется по языку интерфейса или языку конфигурации. В клиентских приложениях реализована поддержка арабских форматов чисел и дат.

При расчете расстановки элементов формы и других элементов интерфейса по умолчанию используется шрифт Almarai.

Если в конфигураторе установлен в качестве текущего языка конфигурации язык с написанием справа-налево, то в редакторе формы предварительный просмотр формы также будет выполняться в соответствующем виде.

Поддержка языков с написанием справа-налево реализована начиная с режима совместимости с версией 8.3.7.

В веб-клиенте реализована поддержка языков с написанием справа-налево для планировщик и диаграмм. +

Поддержка языков с написанием справа-налево имелась только в веб-клиенте.Стало возможно использовать систему «1С:Предприятие» (с помощью тонкого и толстого клиентских приложений) в странах, где национальный язык использует написание справа-налево.
В документации данное изменение описано здесь, здесь и здесь.
Табличный документ.
Отображение информации.
Если в табличном документе, который сохраняется в формате Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML), обнаружено, что длина текста, размещенного в ячейке, превышает 32767 символов, то сохранение прерывается и пользователю выводится сообщение об ошибке.При сохранении табличного документа в формате Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) не выполнялась проверка длины текста в ячейке. Это могло приводить к получению документа, который не мог быть открыт Microsoft Excel.Сохранение в формате Microsoft Excel стало выполняться более корректно.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Работа с запросами.
Ускорено исполнение запросов, в том числе при использовании ограничения доступа к данным.

Ускорена работа функции выражения ограничения доступа к данным СтрСодержит().

Исполнение запросов (в том числе использующих ограничения доступа к данным) требовало больше времени.Оптимизирована работа запросов.
Кластер серверов.
Ускорена загрузка из .dt-файла в клиент-серверном варианте информационной базы за счет использования для загрузки нескольких фоновых заданий. Для получения существенного ускорения желательно, чтобы кластер серверов и СУБД располагались на одном компьютере или чтобы кластер серверов и СУБД были связаны каналом с высокой пропускной способностью (1 Гбайт/с и выше).

Для команды пакетного запуска конфигуратора /RestoreIB реализован параметр -JobsCount, позволяющий управлять количеством используемых фоновых заданий.

Загрузка из dt-файла в клиент-серверном варианте информационной базы выполнялась последовательно.Ускорено восстановление информации из .dt-файла в клиент-серверном варианте информационной базы.
В документации данное изменение описано здесь.
Общие объекты.
При решении систем линейных алгебраических уравнений уменьшено время, которое тратится на получение решения, а также снижено использование оперативной памяти.Решение систем линейных алгебраических уравнений занимало больше времени и требовало больше оперативной памяти.Оптимизирован механизм решения систем линейных алгебраических уравнений.
Кластер серверов.
Оптимизировано получение списка сеансов.

Реализован сервис Сервис получения списка сеансов кластера серверов.

Получение списка сеансов занимало больше времени и могло приводить к зависанию системы при массовом получении списка сеансов во время большой нагрузки на кластер серверов.Исключено зависание системы при массовом получении списка сеансов под высокой нагрузкой. Снижено время одиночной операции получения списка сеансов на кластере с несколькими серверами. Существенно снижены затраты времени при массовом одновременном получении списков сеансов.
В документации данное изменение описано здесь и здесь.
Работа с СУБД.
При многократном последовательном нажатии кнопки Записать в форме редактирования объекта (при неизменном объекте), не выполняется запись в СУБД табличных частей объекта при каждой записи объекта.При многократном последовательном нажатии кнопки Записать в форме редактирования объекта, выполнялась запись в СУБД табличных частей объекта при каждой записи объекта.Снижена нагрузка на СУБД в ряде случаев.
Работа с СУБД.
Работа с запросами.
В файловом варианте информационной базы ускорено исполнение запроса, который получает данные с упорядочиванием и фильтрацией по полю, для которого построен индекс, и в том случае, если для наложения условия используется оператор В, получающий большое количество данных.В файловом варианте информационной базы не оптимально исполнялся запрос, который получает данные с упорядочиванием и фильтрацией по полю, для которого построен индекс, и в том случае, если для наложения условия используется оператор В, получающий большое количество данных.Повышена скорость работы файлового варианта информационной базы.
Регистры бухгалтерии.
Оптимизирован запрос, который использует система «1С:Предприятие» при обращении к виртуальным таблицам остатков и оборотов регистра бухгалтерии.Запрос, который использует система «1С:Предприятие» при обращении к виртуальным таблицам остатков и оборотов регистра бухгалтерии, был не оптимальным.Повышена производительность запросов к виртуальной таблице остатков и оборотов регистра бухгалтерии.
Отображение информации.
Ускорена работа методов ПолучитьСклонениеСтроки() и ПолучитьСклонениеСтрокиПоЧислу() при последовательных вызовах (например, для получения сразу нескольких падежных форм одного и того же словосочетания).Несколько последовательных вызовов методов ПолучитьСклонениеСтроки() и ПолучитьСклонениеСтрокиПоЧислу() занимало больше времени.Ускорено получение сразу нескольких падежных форм одного и того же словосочетания с помощью методов ПолучитьСклонениеСтроки() и ПолучитьСклонениеСтрокиПоЧислу().
Автоматизированное тестирование.
Сокращено количество сетевых вызовов при работе методов НайтиОбъект(), НайтиОбъекты(), ПолучитьОбъект() механизма автоматизированного тестирования. За счет этого повышена общая производительность механизма автоматизированного тестирования.При работе методов НайтиОбъект(), НайтиОбъекты(), ПолучитьОбъект() механизма автоматизированного тестирования выполнялось большое количество сетевых вызовов, из-за чего механизм автоматизированного тестирования работал недостаточно быстро.Повышена производительность механизма автоматического тестирования, особенно при использовании веб-клиента.
Отображение информации.
Ускорено массированное получение представлений ссылочных объектов в том случае, если для формирования представления используется только те данные, которые передаются в обработчик. Ускорение достигается за счет кеширования самих представлений.

Если для получения представления используются данные, которые не передаются в обработчик формирования представления, то при смене представления в объекте, смена представления в обработчике произойдет только через 20 секунд.

Массированное формирование представлений ссылочных объектов занимало больше времени, т.к. кэшировались значения, используемые для получения представления, а само представление вычислялось каждый раз, когда требовалось это представление.Ускорены операции получения представлений ссылочных объектов и, как следствие, связанные операции. Например, ускорится упорядочивание таблицы значений по ссылочной колонке.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Копии базы данных.
Работа с запросами.
Система компоновки данных.
Реализована возможность управления тем, где будет выполняться конкретный запрос или компоновка данных: использовать для выполнения запроса только копии, только основную базу, преимущественно копии или выбирать автоматически. Таким образом стало возможно не нагружать основную базу данных запросом, который создавался для того, чтобы исполняться на копии.

Для объектов Запрос и ЗначенияПараметровВыводаКомпоновкиДанных реализованы свойства ИспользованиеКопийБазДанных и ИспользуемыеКопииБазыДанных.

Платформа автоматически выбирала, где будет выполняться запрос. При невозможности выполнить запрос на копии, для выполнения запроса использовалась основная база данных.Стало возможным не выполнять на основной базе данных запросы или отчеты, которые могут повлиять на производительность базы данных и которые предполагалось выполнять только на копии.
В документации данное изменение описано здесь.
Система компоновки данных.
После окончания формирования отчета, серверная часть системы компоновки данных оповещает клиентское приложение, инициировавшее формирование отчета, о завершении формирования отчета с помощью системы взаимодействия. Данный механизм работает совместно с существующим механизмом определения завершения формирования отчета (периодический опрос системного фонового задания).Для определения факта завершения формирования отчета использовался периодический опрос состояния системного фонового задания, которое формирует отчет. Каждая неудачная проверка завершения приводит к увеличению интервала времени, через который будет выполнена следующая проверка.При наличии системы взаимодействия, пользователь будет быстрее узнавать о завершении формирования длительного отчета.

Если система взаимодействия не подключена к информационной базе или временно не функционирует - будет использоваться существующий механизм.

В документации данное изменение описано здесь.
Динамический список.
Для заголовка колонки таблицы, отображающей динамический список, для которой есть элемент настройки порядка, недоступный для отключения пользователем:
  • В веб-клиенте: при клике по заголовку меняется порядок сортировки.
  • В тонком и толстом клиентских приложениях: в заголовке колонки всегда отображается направление сортировки.

В результате, поведение тонкого, толстого и веб-клиентов стало одинаковым в том случае, если пользователь нажимает левой кнопкой мыши по заголовку колонки динамического списка, в настройках упорядочивания которой есть элемент, недоступный для пользовательского управления.

Для заголовка колонки таблицы, отображающей динамический список, для которой есть элемент настройки порядка, недоступный для отключения пользователем:
  • В веб-клиенте: при клике по заголовку не менялся порядок сортировки.
  • В тонком и толстом клиентских приложениях: в заголовке колонки направление сортировки отображалось только в том случае, когда имелись пользовательские настройки упорядочивания для этой колонки.

Различалось поведение тонкого, толстого и веб-клиентов в том случае, если пользователь нажимал левой кнопкой мыши по заголовку колонки динамического списка, в настройках упорядочивания которой есть элемент, недоступный для пользовательского управления.

Унифицировано поведение тонкого, толстого и веб-клиентов в том случае, если пользователь нажимает левой кнопкой мыши по заголовку колонки динамического списка, в настройках упорядочивания которой есть элемент, недоступный для пользовательского управления.
Отображение информации.
Изменяется поведение метода ПолучитьСклоненияСтрокиПоЧислу() при формировании числа с окончанием:
  • Для порядкового числительного:
    • Если предпоследняя буква в окончании полученного числительного является согласной, то формируется двухбуквенный вариант.
    • Если предпоследняя буква в окончании полученного числительного является гласной, то формируется однобуквенный вариант.
  • Для количественного числительного: формируется ошибка неверного указания параметров.

В режиме совместимости с версией 8.3.18 поведение не изменилось.

При формировании числа с окончанием с использованием метода ПолучитьСклонениеСтрокиПоЧислу(), для порядковых и количественных числительных всегда возвращались двухбуквенные окончания.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Копии базы данных.
Реализована возможность включать в состав копии базы данных объекты, входящие в состав разделителей. При первоначальном заполнении переносится вся таблица, а при переносе изменений - только область, соответствующая разделителям текущий (переносимой) транзакции.

Для выполнения создания копии базы данных (использование метода МенеджерКопииБазыДанных.Записать()) и обновления данных копии (использование метода МенеджерКопииБазыДанных.Обновить()) необходимо право доступа АдминистрированиеДанных.

В состав копии можно было добавлять только те таблицы, которые не входили в состав разделителей или таблицы с условно выключенными разделителями.В состав копии базы данных стало можно включать разделенные объекты прикладного решения.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Клиентское приложение.
Реализована возможность управления аутентификацией OpenID Connect для каждого пользователя информационной базы. Реализовано свойство ПользовательИнформационнойБазы.АутентификацияOpenIDConnect.

Реализована возможность завершения сессии аутентификации в соответствии со стандартном OpenID Connect. В описании провайдера OpenID Connect, в файле default.vrd (элемент <providers>), реализовано свойство endSessionEndpoint.

Данная возможность не предоставлялась.Улучшена поддержка протокола OpenID Connect.
В документации данное изменение описано здесь, здесь и здесь.
Система лицензирования.
Расширен набор информации, выводимой утилитой лицензирования (команда ring license info):
  • В раздел с информацией о лицензии добавлена информация о типе лицензии и типе привязке лицензии.
  • Реализован новый раздел TechnicalInfo, содержащий машиночитаемую информацию. Данные в этом разделе всегда выводятся на английском языке.
Вывод команды ring license info не содержал информации о типе лицензии и типе привязке лицензии, а также не содержал раздела с машиночитаемой информацией о лицензии.Расширен набор информации, который можно получить об активированных лицензиях. Упрощено получение информации о лицензиях с помощью различных средств автоматизации.
В документации данное изменение описано здесь.
Диаграммы.
Система компоновки данных.
Диаграмма, размещенная в отчете системы компоновки данных, стала лучше адаптироваться под ширину экрана, на котором отображается отчет.

В режиме совместимости с версией 8.3.18 поведение не изменилось.

Диаграмма, размещенная в отчете системы компоновки данных, плохо адаптировалась к ширине экрана, на котором отображается отчет.Улучшен внешний вид диаграмм на экранах с невысоким разрешением.
Работа с запросами.
Если в запросе, формирующем временную таблицу на основании таблицы значений, используется получение поля «через точку» от другого выражения, то при исполнении такого запроса выдается ошибка языка запросов.

Рекомендуется проанализировать тексты запросов формирования временных таблиц для устранения изменяемого поведения.

В режиме совместимости с версией 8.3.18 поведение не изменилось.

Если в запросе, формирующем временную таблицу на основании таблицы значений, используется получение поля «через точку» от другого выражения, то при исполнении такого запроса в клиент-серверном варианте формировалась ошибка времени исполнения, а в файловом варианте - в значение временной таблицы помещалось неправильное значение.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
Данное изменение отменено.

При экспорте табличного документа в форматы Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) реализовано следующее поведение для объектов типа Картинка:

  • Если значение свойство РазмерРисунка не равно значению Черепица, то в результирующий документ сохраняется оригинальная картинка. Если для ячейки задан узор, то дополнительно сохраняется картинка узора.
  • Если свойство РазмерРисунка установлено в значение Черепица, то картинка перерисовывается в результирующий документ, а для рисунка документа Microsoft Excel устанавливается цвет фона, равный цвету фона картинки сходного документа.

В результате сделанных изменений, при масштабировании документа Microsoft Excel, меньше искажаются картинки, размещенные в табличном документе.

При экспорте табличного документа в форматы Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) наблюдалось следующее поведение для объектов типа Картинка:
  • Если значение свойство РазмерРисунка не равно значению Растягивать, то картинка перерисовывалась в результирующий документ.
  • Если свойство РазмерРисунка установлено в значение Растягивать, то картинка перерисовывалась в результирующий документ (если не задан цвет фона или узор) и сохранялась оригинальная картинка во всех остальных случаях.

+

Результат сохранения табличного документа в форматах Microsoft Excel (Microsoft Excel 97, Microsoft Office OpenXML) в большей степени соответствует ожиданиям пользователей.
Система компоновки данных.
Функциональные опции.
При вычислении доступности дочерних полей, используемых в выражениях компоновки данных, проверка того, что поле не отключено с помощью функциональной опции, выполняется и для самого поля и для всех родительских полей этого поля.

В режиме совместимости с версией 8.3.18 поведение не изменилось.

При вычислении доступности дочерних полей, используемых в выражениях компоновки данных, проверка того, что поле не отключено с помощью функциональной опции, выполнялось только для самого поля. Проверка для родительских полей не выполнялась.Проверка доступности полей, связанная с функциональными опциями, стала выполняться одинаково и в языке запросов и в системе компоновки данных.
В документации данное изменение описано здесь.
Обмен данными.
Для методов ЗарегистрироватьИзменения() и УдалитьРегистрациюИзменений() реализована возможность выполнять регистрацию и удаления регистрации изменений для произвольного набора объектов данных, которые передаются в качестве массива в параметре Данные этих методов.

Действие для всех объектов, находящихся в переданном массиве, будут выполнены в рамках одной транзакции с минимальным количеством используемых запросов.

Для методов ЗарегистрироватьИзменения() и УдалитьРегистрациюИзменений() не поддерживалась возможность указать массив объектов для выполнения действия.Повышена скорость выполнения методов ЗарегистрироватьИзменения() и УдалитьРегистрациюИзменений() в том случае, когда эти методы необходимо применить для большого количества объектов данных.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Установка клиентского приложения.
Средства администрирования.
Реализовано обновление клиентского приложения с помощью веб-сервера в том случае, когда в качестве веб-сервера используется Microsoft Internet Information Services, настроенные по умолчанию. Реализована поддержка MIME-типа application/x-zip-compressed, который используется веб-сервером для zip-файлов по умолчанию.Для обновления клиентского приложения с помощью веб-сервера в том случае, когда в качестве веб-сервера используется Microsoft Internet Information Services, требовалось вручную переопределить MIME-тип, который веб-сервер использует для передачи .zip-файлов.Упрощено администрирование веб-сервера Microsoft Internet Information Services в том случае, когда настраивается обновление клиентского приложения через веб-сервер.
В документации данное изменение описано здесь.
Средства администрирования.
При установке монопольного режима, реализована возможность указывать человекопонятное описание причины установки монопольного режима (чем занимается сеанс) и указывается возможность прервать сеанс, установивший монопольный доступ.

Для метода УстановитьМонопольныйРежим() реализован параметр Параметры. Реализован метод глобального контекста ПолучитьПараметрыМонопольногоРежима(). Реализовано право доступа ЗавершениеМонопольногоРежимаПриНачалеСеанса.

Текст сообщения о причине невозможности начала нового сеанса может быть форматированной строкой или HTML-строкой, созданной на основании форматированной строки.

+

При попытке входа в информационную базу, в которой установлен монопольный режим, было невозможно прервать работу такого сеанса (даже если прервать сеанс было возможно по логике выполняемых действий) и было непонятно, что выполняется в данный момент.При установке монопольного режима стало возможно указать понятный пользователю текст, который описывает причину установки монопольного режима. Пользователь может прервать работу сеанса, установившего монопольный доступ, если права пользователя и логика выполняемых действий позволяют такое прерывание.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Предопределенные данные.
При вызове метода ПредопределенноеЗначение(), когда в качестве значения параметра указано несуществующее значение перечисления, формируется исключение.

В режиме совместимости с версией 8.3.18 поведение не изменилось.

Вызов метод ПредопределенноеЗначение(), когда в качестве значения параметра указано несуществующее значение перечисления, возвращал пустое значение. Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства администрирования.
В именах программных продуктов, отображаемых в списке установленных приложений ОС Windows, название фирмы «1С» пишется с использованием русской буквы «С».

Название дистрибутива кластера серверов системы «1С:Предприятие» для архитектуры x86-64 выглядит следующим образом: 1C:Предприятие 8 (x86-64) Сервер.

В именах программных продуктов, отображаемых в списке установленных приложений ОС Windows, название фирмы «1С» записывалось с использованием латинской буквы «C».

Название дистрибутива кластера серверов системы «1С:Предприятие» для архитектуры x86-64 выглядело следующим образом: 1C:Предприятие 8 (x86-64).

Название программных продуктов приведено к единому виду для все дистрибутивов программных продуктов, поставляемых для работы под управлением ОС Windows.
Табличный документ.
Система компоновки данных.
Реализована возможность масштабировать картинку таким образом, чтобы высота картинки соответствовала высоте шрифта, используемого в элементе, который отображает картинку.

Реализовано свойство системного перечисления РазмерКартинки.ПоРазмеруШрифта.

Если картинка в ячейке отчета задается с помощью параметра условного оформления системы компоновки данных Картинка, то значение параметра РазмерКартинки считается равным значению ПоРазмеруШрифта (если параметр РазмерКартинки не задан в условном оформлении). В режиме совместимости с версией 8.3.18 поведение не изменилось.

Режим отображения картинки ПоРазмеруШрифта в табличном документе рекомендуется использовать в тех случаях, когда картинка в ячейке выполняет роль маркера. При использовании данного режима отображения картинки, высота картинки не оказывает влияния на автоматически рассчитываемую высоту строки табличного документа и не зависит от количества строк текста, выводимых в ячейке.

Если картинка в ячейке отчета задается с помощью параметра условного оформления системы компоновки данных Картинка, то для значения параметра РазмерКартинки значение по умолчанию не устанавливалось и этот параметр не использовался (кроме случаев явного указания этого параметра). Улучшено отображение картинок в табличном документе в тех случаях, когда необходимо использование картинки в тексте таким образом, чтобы размер картинки автоматически подгонялся под высоту используемого шрифта.
Кластер серверов.
Средства администрирования.
Реализована возможность использовать частичное делегирование Kerberos для выполнения аутентификации ОС в том случае, если кластер серверов работает под управлением ОС Windows, а веб-сервер и клиентское приложение расположены каждый на своем компьютере и этот компьютер отличается от компьютера, на котором работает кластер серверов.

Для средств администрирования кластера серверов реализована возможность указания имени участника-службы (SPN):

  • В консоли администрирования кластера, в свойствах рабочего сервера, реализовано свойство Имя службы (SPN) сервера 1С:Предприятия.
  • Свойство объекта АдминистрированиеРабочийСервер.ИмяСлужбыСервера.
  • Свойство объекта IWorkingServerInfo.ServicePrincipalName для средств администрирования с использованием COM-соединения.
  • Методы getServicePrincipalName(), setServicePrincipalName() интерфейса IWorkingServerInfo для средств администрирования из языка Java.
  • Параметр service-principal-name для команд rac server insert, rac server update.
Данная возможность не предоставлялась.

Аутентификация ОС могла выполняться только при полном делегировании Kerberos в том случае, если кластер серверов работает под управлением ОС Windows, а веб-сервер и клиентское приложение расположены каждый на своем компьютере и этот компьютер отличается от компьютера, на котором работает кластер серверов.

Стало возможно использовать аутентификацию ОС при доступе через веб-сервер без понижения общей безопасности системы.
В документации данное изменение описано здесь, здесь и здесь.
Отображение информации.
Реализована возможность автоматически преобразовывать отчет к компактному виду (при необходимости) вне зависимости от того, каким образом формируется отчет: с помощью платформы или из встроенного языка.

Реализовано свойство ПрименениеРежимаОтображенияПриУстановкеРезультата расширения формы клиентского приложения для отчета. Свойство работает совместно со свойством РежимОтображенияРезультата расширения формы клиентского приложения для отчета.

Изменен формат выгрузки конфигурации в формате XML.

Если отчет формировался из встроенного языка, то преобразование отчета в компактный вид (при необходимости) также было необходимо реализовывать самостоятельно.Для разработчика упрощен вывод отчета на форму в том случае, если отчет формируется из встроенного языка и необходимо учитывать, что отчет может отображаться на мобильных устройствах.
В документации данное изменение описано здесь.
Кластер серверов.
Значение свойства рабочего сервера кластера Временно допустимый объем памяти процессов используется и для перезапуска рабочих процессов по памяти и для управления прерыванием объемных вызовов. Данное свойство допускается использовать с лицензией уровня ПРОФ.При работе с лицензиями уровня ПРОФ, для перезапуска рабочих процессов кластера и для прерывания объемных вызовов сервера использовалось значение, равное 80% от оперативной памяти компьютера, на котором работает сервер. Изменять свойство рабочего сервера кластера Временно допустимый объем памяти процессов, обладая лицензиями уровня ПРОФ, не допускалось.Упрощено администрирование систем, работающих на лицензиях уровня ПРОФ.
В документации данное изменение описано здесь.
Табличный документ.
Для отчетов реализована возможность устанавливать режим отображения результата из встроенного языка.

Для расширения формы клиентского приложения для формы отчета реализованы методы ПолучитьРежимОтображенияРезультата(), ПолучитьТекущийРежимОтображенияРезультата(), УстановитьРежимОтображенияРезультата().

Изменен подход к сохранению информации о режиме отображения результата в системном хранилище настроек. Информация о режиме отображения результата сохраняется в системном хранилище отчета в тех случаях, когда устанавливаемое значение режима отображения отлично от заданного в конфигурации, при этом не учитывается интерпретация значения Авто для различных типов клиентов.

Свойство расширения формы клиентского приложения для формы отчета РежимОтображенияРезультата является устаревшим и не рекомендуется для использования.

Отсутствовала возможность изменять режим отображения результата отчета из встроенного языка.

В системном хранилище сохранялось значение, которое учитывало текущее клиентское приложение (учитывалась интерпретация значения Авто).

Стало возможно управлять отображением отчета из встроенного языка.
В документации данное изменение описано здесь.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильный клиент.
Автоматизированное тестирование.
Реализована возможность использовать мобильный клиент в качестве клиента тестирования. Мобильный клиент с автономным режимом может выступать в роли клиента тестирования только во время соединения с основным сервером.

Реализована возможность записывать действия пользователя на мобильном устройстве и воспроизводить тест, ранее написанный на встроенном языке.

Для командной строки запуска мобильного клиента реализованы команды /UILOGRECORDER и /TESTCLIENT.

Мобильный клиент разработчика всегда запускается с возможностью записи действия пользователя (с командой /UILOGRECORDER).

Если мобильный клиент запускается с использованием команды /UILOGRECORDER, то в меню Сервис и настройка мобильного клиент становится доступным пункт меню Запись действия пользователя. +

Данная возможность не предоставлялась.Стало возможно использовать мобильный клиент для целей автоматизированного тестирования прикладных решений.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Обработка ошибок.
Для системного перечисления КатегорияОшибки реализованы значения:
  • ОтсутствиеРазрешенияДляИспользованияФункциональности, которое описывает ошибки, связанные с тем, что в мобильном приложении отсутствуют разрешения, которые требуются для корректного использования тех или иных возможностей.
  • ОшибкаСредствМультимедиа, которое описывает ошибки, связанные с использованием камеры и микрофона мобильного устройства.
Данные категории ошибок отсутствовали в системном перечислении КатегорииОшибок.Уточнено отнесение ошибок мобильного приложения к категориям ошибок.
Специальные возможности мобильного устройства.
Реализована возможность управлять записью звука в фоновом режиме. При включении данной функциональности, запись звука будет продолжаться при сворачивании приложения и выключении экрана устройства.

Реализовано значение системного перечисления ФункциональностьМобильногоПриложения.ЗаписьАудиоВФоновомРежиме.

Запись аудио в фоновом режиме была недоступна. Аудиоинформация могла быть записана только в том случае, если приложение было активно.Улучшена работа с аудиоинформацией в мобильном приложении.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
Переработан интерфейс видеозвонков в мобильном клиенте.

В мобильном клиенте реализована возможность просмотра экрана другого устройства и выполнять трансляцию собственного экрана. Просматривающий экран не может управлять мобильным устройством, с которого выполняется демонстрация.

Интерфейс видеозвонков в мобильном клиенте был другим.

Мобильный клиент не поддерживал просмотр и демонстрацию экрана.

Улучшено использование видеозвонков системы взаимодействия в мобильном клиенте.

Оглавление

Система «1С:Аналитика»

ФункциональностьКак сталоКак былоРезультат изменения
Аналитика - диаграммы.
В графике, по умолчанию, измерение со временем будет располагаться на оси X.На ось X добавлялось первое добавленное измерение.Ожидаемый результат получается чаще без дополнительных действий.
Аналитика - дашборды.
В левой панели дашборда отображаются папки аналогично рабочему столу.В левой панели дашборда отображались все диаграммы, без учета папок.Стало удобнее ориентироваться в диаграммах на дашборде.
Аналитика - дашборды.
Уменьшены отступы между элементами дашборда.Отступы между элементами дашборда были больше.На дашборд стало помещаться больше информации.
Аналитика - диаграммы.
В режиме таблицы теперь можно настроить, как будут располагаться итоги: в начале или в конце значений измерения.В режиме таблицы итоги всегда отображались в начале измерения.Улучшены настройки внешнего вида итогов таблицы.
Аналитика - язык выражений.
Реализована функция ФОРМАТ() для форматирования значений в диаграмме.Значение выводились в формате по умолчанию.Стало возможно настроить требуемый вариант вывода значений.
Аналитика - диаграммы.
При переключении типа диаграммы, в диаграмме сохраняются близкие по смыслу роли полей.При переключении типа диаграммы, роли полей устанавливались в значения по умолчанию.При переключении типа диаграммы необходимо выполнять меньше действий для получения требуемого вида диаграммы.
Аналитика - источники.
При создании дополнительных источников на базе виртуальных таблиц, реализована возможность передачи в запрос параметров из настроек отчета.В дополнительных источниках нельзя было определить параметры виртуальных таблиц.Работа дополнительных источников, основанных на виртуальных таблицах, стала эффективнее.
Аналитика - язык выражений.
Реализованы функции ПРЕДДАТА() и ЗНАЧЕНИЕДЛЯ() для построения сравнительных графиков по различным срезам времени или других размерностей.

Использование данных функций позволит в таблице сравнивать одинаковые (по сути) показатели, полученные за различные периоды времени или по другим аналитическим размерностям.

Для вывода в таблицу было невозможно использовать одинаковые (по сути) показатели, полученные за разные периоды времени или по другим аналитическим размерностям.Стало возможно получать одинаковые показатели за различные периоды времени для построения более наглядных диаграмм.
Аналитика - язык выражений.
Реализована функция ПЕРВЫЕ(), которая позволяет ограничить число выводимых в отчете значений, а оставшиеся значения объединить в одно итоговое значение. Настройка доступна из контекстного меню измерения.Данная возможность не предоставлялась.Стало возможно строить более наглядные диаграммы.
Аналитика - диаграммы.
В редакторе диаграммы реализован поиск доступных полей во вложенных структурах источника (во вложенных ссылках на элементы справочников и документы).Поиск работал только для верхнего уровня иерархии.Стало проще выполнять поиск анализируемых полей.
Аналитика - диаграммы.
Реализовано раскрытие иерархии по дате, аналогично работе с иерархией справочников, при помощи меню иерархии поля в составе диаграммы.Уточнение периодов в диаграммах было необходимо выполнять вручную.Работа с датами в диаграммах стала более удобной.
Аналитика - диаграммы.
Реализована возможность настраивать местоположение легенды в диаграмме.Положение легенды было фиксированным.Настройки внешнего вида диаграмм стали более гибкими..
Аналитика - диаграммы.
Реализованы подсказки и пояснения в редакторе фильтра по дате для универсальных формул («Текущий год», «Прошлый год» и т.п.).Данная возможность не предоставлялась.В редакторе фильтра по дате стала доступна справочная информация.
Аналитика - диаграммы.
Фон диаграммы стал учитывать включенную в данный момент тему приложения.Фон диаграмм был светлым независимо от темы.Фон диаграмм стал соответствовать используемой теме.
Аналитика - диаграммы.
Реализован вывод подсказки для значения поля, если оно не умещается внутри одной ячейки в таблице.Данная возможность не предоставлялась.

Значения полей обрезались по границам ячейки.

Полностью увидеть значение в ячейке таблицы стало возможно для любой длины текстового представления значения.
Аналитика - диаграммы.
Реализована возможность показа полного значения даты в диаграмме с помощью контекстного меню.Полную дату можно было вывести только с помощью редактирования формулы.Работа с датами стала более комфортной.
Аналитика - диаграммы.
Реализована возможность плавной настройки размера панели с полями источника данных.Размер панели не настраивался.Стало возможно более эффективно использовать экранное пространство.
Аналитика - дашборды.
При переходе с дашборда на уровень диаграмм реализовано отображение общих фильтров дашборда и их быстрое включение/отключение.На дашборде не было общих фильтров.Пользователь может быстро оценить влияние фильтра на данные дашборда.
Аналитика - другое.
Реализована команда для открытия веб-клиента информационной базы «1С:Предприятие», с которой работает система «1С:Аналитика».Не предоставлялась возможность быстрого вызова веб-клиента для используемой информационной базы системы «1С:Предприятие».Работа с информационной системой стала более комфортной.
Аналитика - рабочий стол.
Реализована возможность группового копирования/перемещения объектов на рабочем столе.Объекты на рабочем стали можно было копировать и переносить только по одному.Организация рабочего стола стал более удобной.
Аналитика - рабочий стол.
Реализовано отображение пути до объектов при поиске на рабочем столе.При поиске было непонятно откуда объект.Поиск на рабочем столе стал информативнее.
Аналитика - диаграммы.
Данные диаграмм хранятся в кэше системы «1С:Аналитика» в течение 24 часов.Данные диаграмм хранились в кэше системы «1С:Аналитика» до перезагрузки вкладки веб-браузера.Получаемый результат стал более прогнозируемым.
Аналитика - дашборды.
Реализована возможность копирования виджетов на дашборде.Виджет на дашборде нельзя было скопировать. Было возможно только создать новый виджет, настраивать который требовалось вручную.Упростилась настройка дашборда.
Аналитика - диаграммы.
Реализована возможность устанавливать диапазон отображения значений на осях графика.Диапазон отображения значений на осях графика настраивался по отображаемым данным, автоматически.Расширены возможности настройки внешнего вида диаграммы.
Аналитика - источники.
При использовании виртуальных таблиц остатков и оборотов реализовано дополнение остатков по периодам, в которые не было оборотов по части значений измерений. Остаток в дополненных периодах равен остатку последнего фактического периода, предшествующего дополненному.При использовании виртуальных таблиц остатков и оборотов остатки по периодам не выводились (в данных могли быть пропуски), если по части значений измерений в эти периоды не было оборотов.Корректное отображение данных.
Аналитика - язык выражений.
Реализованы функции для работы с датами РАЗНОСТЬДАТ(), НАЧАЛОПЕРИОДА(), КОНЕЦПЕРИОДА().Данная возможность не предоставлялась.Расширен список функций для работы с датами.
Аналитика - дашборды.
Реализованы шаблоны фильтров для полей типа булево и дата на дашборде.Фильтры указанных типов можно было задавать только формулой.Упростилось создание фильтров.
Аналитика - источники.
Улучшен внешний вид диалога, который отображается во время обновления источников системы «1С:Аналитика». Диалог стал отображать более подробную информацию и не блокирует работу с системой.Диалог, который отображается во время обновления источников системы «1С:Аналитика», отображал меньше информации и блокировал работу с системой.Улучшен внешний вид и поведение системы «1С:Аналитика» во время обновления источников.
Аналитика - язык выражений.
Реализована функция ДОБАВИТЬ() для изменения значений даты и времени.Данная возможность не предоставлялась.Расширен список функций для работы с датами.
Аналитика - диаграммы.
Нажатие клавиши ESC приводит к закрытию окна редактированию поля только в том случае, если значения полей окна не были изменены.Нажатие клавиши ESC закрывало окно редактирования поля вне зависимости от того, были изменены данных в полях окна или нет, что могло приводить к потере данных.Работа с системой стала более предсказуемой и удобной.
Аналитика - язык выражений.
Улучшена контекстная подсказка при редактировании кода выражений.Контекстная подсказка при редактировании кода выражений работала плохо.Редактор выражений стал удобнее для использования.
Аналитика - диаграммы.
Улучшено отображение подписей на диаграммах.При большом количестве подписей, они закрывали друг друга и диаграмма выглядела плохо.Улучшен внешний вид диаграмм.
Аналитика - диаграммы.
Оптимизирована работа с группировками.Работа с группировками была выполнена неоптимально.Повышена производительность получения данных.

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.12.Версия формата выгрузки конфигурации в XML-файлы была равна 2.11.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
Отображение информации.
В библиотеку картинок добавлена картинка НачатьВидеоконференцию.В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.
Полнотекстовый поиск.
Ускорено выполнение полнотекстового поиска в том случае, когда поиск запущен из встроенного языка (включая механизмы глобального поиска) и задан отбор по метаданным (свойство СписокПолнотекстовогоПоиска.ОбластьДанных).

Ускорение будет заметно в том случае, если индекс полнотекстового поиска построен в режиме совместимости с версией 8.3.7 и последующих.

При установке отбора по метаданным, полнотекстовый поиск работал медленно.При установке отбора по метаданным, ускорена работа полнотекстового поиска.
Система компоновки данных.
При использовании условного оформления в системе компоновки данных, для оформления макетов ресурсов итога по горизонтали и вертикали таблицы используется элемент условного оформления с установленной областью использования В общем итоге .

В режиме совместимости с версией 8.3.18 поведение не изменилось. +

Элемент условного оформления с установленной областью использования В общем итоге не применялся для условного оформления макетов ресурсов итога по горизонтали и вертикали таблицы.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Картинки.
Мобильная платформа.
Мобильный клиент.
Реализована доступность объекта ОбрабатываемаяКартинка в мобильной версии системы «1С:Предприятие». Не реализованы следующие методы объекта: ВыделитьЗначимуюЧасть(), УстановитьГлубинуЦвета() и УстановитьПлотность(). Особенности работы остальных свойств и методов объекта в этом случае - отражены в синтакс-помощнике.

Для объекта Картинка реализована доступность методов Ширина(), Высота() и РазмерФайла() в мобильной версии. Методы ГлубинаЦвета(), ОттенкиСерого(), ПлотностьПоГоризонтали() и ПлотностьПоВертикали() в мобильной версии всегда возвращают значение Неопределено. +

В мобильной версии системы «1С:Предприятие» были недоступны объект ОбрабатываемаяКартинка и все методы объекта Картинка.Стало возможно реализовывать некоторые пользовательские сценарии на мобильных устройствах, например, отображение на форме уменьшенных картинок (для более эффективного использования ресурсов мобильного устройства).
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована техническая возможность при выполнении групповых видеозвонков обмениваться видеопотоком только с сервером. Для этого на сервере взаимодействия должно быть настроено специализированное серверное приложение.Групповые видеозвонки выполнялись в режиме p2p, т.е. клиентское приложение обменивалось видеопотоками с компьютерами всех участников видеозвонка.Реализована возможность снизить нагрузку на клиентский компьютер при групповом видеозвонке и большом количестве участников видеозвонка. Улучшена работа системы взаимодействия при наличии несимметричного канала связи у пользователя.
Сборщик мобильных приложений.
Мобильная платформа.
Мобильный клиент.
Дистрибутив мобильной версии системы «1С:Предприятие» содержит требования к версиям утилит, используемых для сборки мобильного приложения.Требования к утилитам, используемые для сборки мобильного приложения, не входили в состав дистрибутива мобильной версии. Пользователю было невозможно понять, какие версии утилит необходимо установить для успешной сборки мобильного приложения.Стало возможно понять, какие версии утилит, используемых для сборки мобильного приложения, необходимо установить на компьютер сборщика. При несоответствии версий формируется более понятная диагностика.
В документации данное изменение описано здесь, здесь и здесь.
Система лицензирования.
Система аналитики.
Реализована возможность запуска одного клиента системы 1С:Аналитика без наличия клиентской лицензии системы 1С:Аналитика в том случае, если к информационной базе подключено не более 5 сеансов клиентских приложений.Возможность запуска клиента системы 1С:Аналитика без собственной лицензии была недоступна.Разработчик прикладного решения может использовать систему 1С:Аналитика в целях разработки без необходимости приобретения клиентской лицензии 1С:Аналитика.
В документации данное изменение описано здесь.
Работа с файлами.
Обновлен дистрибутив программы работы с файлами (см. здесь). Дистрибутив поставляется с интерфейсом на всех языках, поддерживаемых системой «1С:Предприятие».Дистрибутив программы работы с файлами был представлен двумя вариантами: только на русском языке и на всех языках, поддерживаемых системой «1С:Предприятие».Упрощена работа с программой работы с файлами. Пользователю более нет необходимости выбирать, какой дистрибутив ему требуется.
Сервис интеграции.
Реализована возможность указать, что обработка получения сообщения сервиса интеграции будет выполняться вне транзакции.

Реализовано свойство ВТранзакции объекта конфигурации КаналСервисаИнтеграции.

Обработка получения сообщения сервиса интеграции всегда выполнялась в рамках транзакции.Стало возможно реализовать более гибкие алгоритмы работы с каналами сервисов интеграции.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Оптимизирован модуль демонстрации экрана при работе в тонком, толстом и веб-клиентах. Для работы нового модуля демонстрации экрана требуется сервер системы взаимодействия версии 10 и последующих. Для использования нового модуля демонстрации экрана в веб-клиенте - требуется Google Chrome версии 64 и последующих (дополнительно к версии сервера системы взаимодействия).

Оптимизированная версия модуля демонстрации экрана позволяет выбрать монитор для демонстрации (если мониторов несколько), работает более быстро, меньше загружает центральный процессор демонстрирующего компьютера.

Предыдущий модуль демонстрации экрана используется в том случае, если абонент в видеозвонке не может использовать новый вариант модуля.

Использовался предыдущий модуль демонстрации экрана, который не позволял выбрать монитор для демонстрации, отличался более низкой производительностью, более сильно нагружал центральный процессор демонстрирующего компьютера.Улучшена демонстрация экрана компьютера при использовании системы взаимодействия.
В документации данное изменение описано здесь.
Копии базы данных.
Оптимизировано выполнение запросов, которые выполняются в копии базы данных, в том случае, когда в основной базе данных выполняется большое количество транзакций, а переносы данных в копию выполняется не очень часто.

Для включения оптимизации необходимо выполнить реструктуризацию информационной базы (путем обновления конфигурации или при выполнении тестирования и исправления).

Запросы, которые выполняются в копии базы данных, были написаны не оптимально.Повышена производительность запросов, которые могут выполняться на копии базы данных.
Табличный документ.
Улучшено преобразование табличного документа в компактный вид, применяемый на мобильных устройствах.Преобразование табличного документа в компактный вид, работало недостаточно хорошо.Улучшено отображение табличного документа на мобильных устройствах.
Сборщик мобильных приложений.
Из сборщика мобильных приложений исключена поддержка следующих возможностей:
  • Сборка мобильных приложений с использованием Apache Ant.
  • Сборка мобильных приложений с помощью Android SDK версии 25 и предыдущих версий.
  • Сборка мобильных приложений, работающих под управлением ОС Windows 8.1.

Если требуется использование данных возможностей - следует использовать сборщик мобильных приложений версии 8.3.18 или предыдущие версии.

Сборщик мобильных приложений поддерживал:
  • Сборку мобильных приложений с использованием Apache Ant.
  • Сборку мобильных приложений с помощью Android SDK версии 25 и предыдущих версий.
  • Сборку мобильных приложений, работающих под управлением ОС Windows 8.1.
В сборщике мобильных приложений исключена поддержка устаревших технологий и мобильных операционных систем.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Начиная с мобильной версии 8.3.19.52 реализована возможность сборки мобильных приложений (для ОС Android) в формате пакета приложений (aab-файл).

Изменен состав файлов дистрибутива мобильной версии.

Сборщик мобильных приложений позволяет собирать приложения в любом формате (согласно мобильной версии, используемой для сборки мобильного приложения).

Сборщик мобильных приложений позволяет загружать в магазин приложений любой вариант собранного приложения (но не оба одновременно). Перед тем, как загрузить в сборщик мобильных приложений версию 8.3.19.52 или последующую версию - обязательно обновите сборщик на ту версию, которая идет в составе загружаемого дистрибутива!

Мобильная версия «1С:Предприятия» (включая сборщик мобильных приложений) не поддерживала возможность сборки пакетов приложений (aab-файлов).Реализована возможность собирать мобильные приложения, которые можно будет загрузить в магазин Google Play.
В документации данное изменение описано здесь.
Локализация.
Реализована локализация интерфейса клиентского приложения для туркменского языка (код tk).Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» пользователями, говорящими на туркменском языке.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Улучшено распознавание кодов DataMatrix с помощью камеры мобильного устройства:
  • Реализовано распознавание светлого кода на темном фоне.
  • Реализовано распознавание круглых пикселей в коде.
  • Улучшено распознавание сложных кодов: на мятой бумаге, с бликами и т.д.

При распознавании штрихкодов с помощью камеры мобильного устройства реализованы следующие изменения:

  • Автоматическая установка увеличения в 1,5 раза для упрощения сканирования мелких штрихкодов.
  • Уменьшена частота кадров при распознавании.
  • Уменьшен таймаут между последовательными сканирования до 1,3 секунды.
Распознавание кодов DataMatrix не отрабатывало некоторые часто встречающиеся ситуации.

При распознавании штрихкодов с помощью камеры мобильного устройства было неудобно сканировать мелкие штрихкоды. Пауза между последовательными сканирования была равна 2 секунды.

Улучшено использование камеры мобильного устройства для сканирования кодов DataMatrix и других штрихкодов.
Копии базы данных.
Повышена производительность первоначального заполнения копии базы данных.Первоначальное заполнение копии базы данных занимало больше времени.Повышена производительность первоначального заполнения копии базы данных.
Табличный документ.
Команда табличного документа Сохранить работает следующим образом:
  • Если не задано имя файла или табличный документ в режиме «только просмотр», то выдается диалог выбора файла для сохранения.
  • Если имя файла задано и табличный документ находится в режиме редактирования, то выполняется сохранение без отображения диалога выбора файла.

В режиме совместимости с версией 8.3.18 поведение не изменилось.

Команда табличного документа Сохранить работала аналогично команде Сохранить как.Устранено некорректное поведение системы.

Оглавление

Переход с предыдущей версии на версию 8.3.19

Оглавление

Версия 8.3.18

Версия 8.3.18 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8318doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.17.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.16. +Возможность запуска конфигураций, разработанных в версии 8.3.17 и более младших, в версии 8.3.18, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.18 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.18, при необходимости, использовать для работы с информационной базой и версию 8.3.17. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Веб-клиент.
Для веб-клиента реализована поддержка прогрессивного веб-приложения (Progressive Web Apps, PWA). Прогрессивное веб-приложение поддерживается для веб-браузера Google Chrome версии 73 и последующих, а также если веб-клиент опубликован по протоколу HTTPS.

В меню Сервис и настройки реализована команда Отображать как отдельное приложение.

Реализовано свойство глобального контекста ПрогрессивноеВебПриложение.

Реализован параметр запуска веб-клиента ProgressiveWebApplicationName.

Для файла default.vrd реализован элемент progressiveWebApplication.

Данная возможность не предоставлялась.Стало возможно выносить пиктограмму запуска приложения веб-клиента на рабочий стол. Веб-клиент (в режиме прогрессивного веб-приложения) запускается в отдельном окне, а не в окне веб-браузера.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Встроенный язык.
Переработана технология работы с асинхронными вызовами. Реализована возможность описывать метод как асинхронный, неблокирующий аналог обычного метода. Асинхронные методы всегда возвращают объект Обещание. Результат работы асинхронного метода возвращается через этот объект.

Реализован модификатор Асинх, используемый для описания метода. Реализованы объекты Обещание, РезультатАсинхВызоваВнешнейКомпоненты. Реализован оператор Ждать.

Для работы с внешними компонентами следут использовать методы <ИмяМетода>Асинх, Получить<ИмяСвойства>Асинх и Установить<ИмяСвойства>Асинх. Эти методы добавляются платформой автоматически, переделка внешней компоненты не требуется.

Для методов глобального контекста и объектов встроенного языка, начинающихся с Показать и Начать, реализованы аналоги с суффиксом имени Асинх.

Данная возможность не предоставлялась.

Для использования асинхронных методов было необходимо использовать специальные обработчики оповещений.

Работа с асинхронными методами стала более удобной.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с Интернет.
Веб-клиент.
В клиентских приложениях (тонкий, толстый и веб-клиент) реализована возможность получения информации о MAC-адресах сетевых адаптеров текущего компьютера.

Реализован объект ИнформацияОСетевомАдаптере. Реализованы методы глобального контекста ПолучитьИнформациюОСетевыхАдаптерах(), НачатьПолучениеИнформацииОСетевыхАдаптерах(), ПолучитьИнформациюОСетевыхАдаптерахАсинх().

Для работы в веб-клиенте требуется установка расширения получения информации о компьютере. Реализованы методы НачатьУстановкуРасширенияПолученияИнформацииОКомпьютере() и НачатьПодключениеРасширенияПолученияИнформацииОКомпьютере().

Данная возможность не предоставлялась.Стало возможно получить MAC-адрес клиентского компьютера в том случае, если это требуется для взаимодействия с внешними системами.
Локализация.
Для метода ЧислоПрописью() реализована поддержка китайского языка (zh, zh_CN).Данная возможность не предоставлялась.Упростилось представление информации для пользователей, говорящих на китайском языке.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 12 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 12.2.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Общие объекты.
Для объекта ХешированиеДанных реализована возможность вычисления хеш-функции SHA512.Данная возможность не предоставлялась.Расширение набора поддерживаемых хеш-функций.
Форма клиентского приложения.
Реализована возможность указания форматированной строки в качестве значения свойства Текст для следующих элементов планировщика: ЭлементПланировщика, ИзмерениеПланировщика, ЭлементИзмеренияПланировщика, МеткаИнтерфалаФонаПланировщика, МеткаЭлементаШкалыВремени. Для реквизита формы типа Планировщик реализовано свойство ТипТекстаНовыхЭлементов, позволяющее указать, какой текст можно вводить в новых элементах планировщика, создаваемых пользователем.

Реализована возможность установки действий для элемента планировщика. Реализовано свойство ЭлементПланировщика.Действия. Для каждого действия предоставляется возможность указания различных свойств оформления (доступность, картинка, представление, выравнивание и т.д.). Реализована возможность настраивать различные реакции системы на выбор действий или нажатие на гиперссылки, размещенные в элементах планировщика.

Для поля планировщика реализовано события: НажатиеНавигационнойСсылки, НажатиеНаДействиеПланировщика.

Реализована возможность создавать элементы планировщика, которые недоступны для редактирования пользователем. Реализовано свойство ЭлементПланировщика.РежимРазрешенияРедактирования.

Для интервала фона планировщика реализована возможность изменять цвет рамки. Реализовано свойство ИнтервалФонаПланировщика.ЦветРамки.

Реализована возможность задавать рамку для планировщика, интервала фона планировщика и элемента планировщика. Реализовано свойство Рамка для объектов Планировщик, ИнтервалФонаПланировщика, ЭлементПланировщика.

Параметр Текст события ПередСозданием расширения планировщика для поля формы может принимать значения типа Текст и ФорматированнаяСтрока.

Параметр Текст метода Добавить() объектов КоллекцияИзмеренийПланировщика, КоллекцияЭлементовИзмеренийПланировщика и КоллекцияМетокИнтерваловФонаПланировщика может принимать значения типа Текст и ФорматированнаяСтрока.

Параметр Текст метода Вставить() объектов КоллекцияИзмеренийПланировщика, КоллекцияЭлементовИзмеренийПланировщика и КоллекцияМетокИнтерваловФонаПланировщика может принимать значения типа Текст и ФорматированнаяСтрока.

Для системного перечисления

ИсточникКомандПланировщика реализованы новые значения: НавигационнаяСсылка и Действие.

Для системного перечисления ПараметрыФормированияКомандПланировщика реализованы значения НавигационнаяСсылка, Действие, Измерение.

Для системного перечисления СтандартнаяКомандаПланировщика реализованы значения ПерейтиПоНавигационнойСсылке, КопироватьНавигационнуюСсылку, ВыполнитьДействие.

Данные возможности не предоставлялись.Расширены возможности использования планировщика. Стало возможно реализовать более дружественный интерфейс пользователя с использованием планировщика.
В документации данное изменение описано здесь.
Глобальный поиск.
Реализована возможность задавать произвольные действия к результатам глобального поиска. Заданные действия отображаются рядом с результатом глобального поиска и доступны для выполнения непосредственно из списка результатов глобального поиска.

Реализовано свойство ЭлементРезультатаГлобальногоПоиска.Действия. Реализован обработчик события модуля приложения ПриВыбореДействияРезультатаГлобальногоПоиска.

Данные возможности не предоставлялись.Расширены возможности оформления результатов глобального поиска.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Средства администрирования.
Для команды /MergeCfg командной строки запуска конфигуратора реализована возможность работы с расширениями конфигурации. В качестве параметра команды может выступать файл .cfe. Для данной команды реализован параметр -Extension, позволяющий указывать имя расширения, для которого будет исполняться команда.Команда /MergeCfg не позволяла использовать расширения.Стало возможно использовать расширения в автоматизированных сценариях во время разработки, тестирования и обслуживания прикладных решений.
В документации данное изменение описано здесь.
Расширение конфигурации.
Реализована возможность расширять типы реквизитов заимствованных объектов, кроме:
  • типов общих реквизитов;
  • реквизитов с типами внешних источников данных;
  • реквизитов, имеющие определяемый тип;
  • реквизит Тип плана видов характеристик.

При сравнении и объединении расширений реализована возможность выбора действий для отдельных типов.

Данная возможность не предоставлялась.Расширены возможности использования расширения.
В документации данное изменение описано здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
В приложении «1С:Предприятие - оповещение и запуск» реализована возможность скрыть все важные оповещения одним нажатием. Данная возможность появляется в том случае, если появляются три (и более) оповещения.

В центре оповещений клиентского приложения кнопка очистки оповещений стала называться Очистить.

В приложении «1С:Предприятие - оповещение и запуск» не было возможности скрыть все важные оповещения одним нажатием.

В центре оповещений клиентского приложения кнопка очистки оповещений называлась Очистить оповещения.

Улучшена работа с оповещениями. Большое количество оповещений можно скрыть одним действием.
Система взаимодействия.
Реализована подсветка новых сообщений в открытом обсуждении.

Реализовано отображение заголовка приложения в заголовке входящего видеозвонка.

Реализована возможность вставки картинок с помощью комбинации клавиш Shift+Ins.

При прокрутке списка сообщений вверх с помощью колеса мыши, выполняется автоматическая подгрузка новых сообщений.

При отправке сообщения реализована установка признака прочитанности для данного обсуждения.

Реализовано кеширование файлов вложений при их получении или открытии (в тонком клиенте) или только получении (в веб-клиенте).

Реализована возможность цитирования сообщений. В контекстном меню выделенного текста реализована команда Цитировать. Признаком цитирования выступает символ «>» в первой позиции строки сообщения.

Реализована возможность копировать сообщение с вложениями.

Для клиентского приложения, работающего под управлением ОС Linux или Windows реализовано отображение количества непрочитанных сообщений в центре оповещений в виде числа на значке приложения в панели задач и на значке команды открытия списка оповещений.

Данные возможности не предоставлялись.Работа пользователя в системе взаимодействия стала более комфортной.
Веб-клиент.
Внешние компоненты.
Реализована поддержка 64-разрядных версий внешних компонент при работе в веб-клиенте, на операционных системах семейства Windows, в 64-разрядных веб-браузерах Google Chrome и Mozilla Firefox.В 64-разрядных веб-браузерах Google Chrome и Mozilla Firefox работающих на операционных системах семейства Windows, веб-клиент использовал 32-разрядные версии внешних компонент.Улучшена поддержка 64-разрядных веб-браузеров Google Chrome и Mozilla Firefox.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Автономный сервер.
Ускорена загрузка .DT-файла в информационную базу при использовании утилиты управления автономным сервером (ibcmd).Загрузка DT-файла в информационную базу автономного сервера (с помощью утилиты ibcmd) занимала больше времени.Ускорена загрузка DT-файла в информационную базу автономного сервера.
Стандартные функции.
Ускорено открытие основной формы стандартной функции просмотра журнала регистрации.Открытие основной формы стандартной функции просмотра журнала регистрации занимало больше времени.Просмотр журнала регистрации стал более комфортным.
Кластер серверов.
Существенно уменьшено время получения сеансом клиентской лицензии в следующих случаях:
  • Массовое начало работы пользователей.
  • Перезапуск менеджеров кластера после программного или аппаратного сбоев.
При массовом запуске (или перезапуске) клиентских сеансов, получении лицензий занимало много времени и существенно замедляло запуск сеансов.Устранено некорректное поведение системы.
Отображение информации.
Кластер серверов.
Повышена производительность методов ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() в том случае, если механизм склонения используется одновременно несколькими пользователями при работе в клиент-серверном варианте информационной базы.Если методы ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() используются одновременно несколькими пользователями в клиент-серверном варианте информационной базы, выполнение методов требовало больше времени.Устранено некорректное поведение системы.
Ограничение доступа к данным.
Повышена производительность функции СтрСодержит(), используемой в шаблонах ограничения доступа к данным.Производительность функции СтрСодержит(), используемой в шаблонах ограничения доступа к данным, была недостаточной.Повышена производительность функции СтрСодержит(), используемой в шаблонах ограничения доступа к данным.
Работа с СУБД.
При использовании запросов из платформы на СУБД Microsoft SQL Server, их планы кэшируются в том же разрезе свойств, что и при выполнении этих запросов из SQL Server Management Studio с настройками по умолчанию. В результате это не приводит к генерации другого плана запроса при повторном исполнении запроса в SQL Server Management Studio, что упрощает анализ работы запросов.При использовании в СУБД Microsoft SQL Server одного и того же запроса непосредственно из платформы и из SQL Server Management Studio, могли генерироваться различные планы запросов.Упрощен анализ планов запросов, которые используются в СУБД Microsoft SQL Server.
Копии базы данных.
Оптимизирован процесс переноса завершившихся транзакций в копию базы данных.Процесс переноса завершившихся транзакций в копию базы данных занимал больше времени.Ускорена операция переноса данных в копию базы данных.
Система компоновки данных.
Динамический список.
Ускорено открытие настроек отчетов и динамических списков, а также формирование макетов компоновки данных, если в настройках компоновки данных задействованы дочерние поля полей, для которых определено большое количество характеристик.Если в настройках компоновки данных задействованы дочерние поля полей, для которых определено большое количество характеристик, то открытие настроек отчетов и динамических списков, а также формирование макетов компоновки данных занимало много времени.Ускорено открытие форм настроек динамических списков и отчетов.
Ограничение доступа к данным.
В запросах ограничения доступа к данным реализована возможность заменять подзапросы, которые не зависят от защищаемой таблицы, на результат их работы. Поддерживается замена одного подзапроса для каждой защищаемой таблицы. Результат вычисления таких подзапросов кешируется в оперативной памяти рабочего процесса.Запросы ограничения доступа к данным не подвергались дополнительной обработке и всегда выполнялись в оригинальном виде.Повышена производительность запросов ограничения доступа к данным. В результате изменения СУБД может спланировать более эффективный запрос.
Табличный документ.
Работа с PDF-документами.
Оптимизирован экспорт табличного документа в формат PDF.Экспорт табличного документа в формат PDF требовал больше времени.Уменьшено время, требуемое для экспорта табличного документа в формат PDF. Возможно уменьшение размера получающегося документа PDF, если в исходном табличном документе имеются ячейки с измененной ориентацией текста.
Средства разработки.
Ускорено формирование автономной конфигурации.Формирование автономной конфигурации занимало больше времени.Ускорено формирование автономной конфигурации.
Табличный документ.
Оптимизирована работа с табличным документом, содержащем большое количество объединенных ячеек, расположенных в большом количестве строк.Работа с табличным документом, содержащем большое количество объединенных ячеек, расположенных в большом количестве строк, занимала больше времени.Ускорена работа с табличным документом.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Автономный сервер.
Для утилиты управления автономным сервером (ibcmd) реализованы возможности частичной выгрузки и загрузки конфигурации из файлов.

Для команды config export реализованы:

  • Параметр --sync - позволяет выполнить синхронизацию конфигурации и каталога выгрузки.
  • Команда objects - позволяет выгрузить только те объекты конфигурации, которые указаны в файле, являющимся параметром команды.
  • Команда info - позволяет получить информацию об информационной базе, с которой работает автономный сервер.
  • Команда status - позволяет получить различия между конфигурацией и каталогом выгрузки.
  • Команда base - позволяет выгрузить изменения в конфигурации информационной базы относительно каталога с ранее выгруженными файлами.
  • Команда all-extensions - позволяет выгрузить в файлы все расширения информационной базы.

Для команды config import реализованы команды:

  • Команда files - выполняет загрузку данных из файлов, перечислены в качестве параметра команды.
  • Команда all-extensions - позволяет загрузить из файлов все расширения, которые находятся в указанном каталоге.
Утилита управления автономным сервером (ibcmd) позволяла выполнять только операции полной загрузки и выгрузки конфигурации в в/из файлов.Расширены возможности работы с автономным сервером.
В документации данное изменение описано здесь.
Работа с Интернет.
Реализована возможность получать и устанавливать произвольный тип текста почтового сообщения при работе с механизмом ИнтернетПочта.

Для перечисления ТипТекстаПочтовогоСообщения реализовано значение ПроизвольныйТекст. Для объекта ИнтернетТекстПочтовогоСообщения реализовано свойство ПроизвольныйТипТекста, которое содержит реальный тип текста из свойства Content-Type почтового сообщения. В случае, если платформа не смогла определить тип почтового сообщения, то свойство ИнтернетТекстПочтовогоСообщения.ТипТекста устанавливается в значение ТипТекстаПочтовогоСообщения.ПроизвольныйТекст.

Параметр ТипТекста метода ИнтернетТекстыПочтовогоСообщения.Добавить() может принимать значения типа Строка.

При формировании текста письма, которое фактически будет отправлено на почтовый сервер, в заголовок Content-Type будет добавлен (или заменен) параметр charset с кодировкой, которая указана в свойстве ИнтернетТекстыПочтовогоСообщения.Кодировка.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

При работе с Интернет-почтой не предоставлялась возможность получения фактического типа почтового сообщения. Если платформа не могла определить тип текста почтового сообщения, то свойство ИнтернетТекстПочтовогоСообщения.ТипТекста устанавливалось в значение ТипТекстаПочтовогоСообщения.ПростойТекст.

При формировании текста письма, которое фактически будет отправлено на почтовый сервер, в заголовке Content-Type не формировался параметр charset.

При работе с Интернет-почтой упрощена работа с такими электронными письмами, как приглашения на встречи, которые отправляются из электронных календарей.
В документации данное изменение описано здесь.
Система взаимодействия.
Для системы взаимодействия реализована возможность реализации робота (бота), который работает на сервере «1С:Предприятия» (не требует запущенного экземпляра клиентского приложения).

Реализован объект БотСистемыВзаимодействия. Для менеджера системы взаимодействия реализован методы: ВыполнитьОбработкуБотов(), СоздатьБота(), ПолучитьБота(), ПолучитьБотов().

Реализованы системные фоновые задания для работы ботов.

В системной обработке управления системой взаимодействия реализованы возможности работы с ботами.

Для реализации робота (бота) было необходимо иметь постоянно запущенное клиентское приложение. Не было выделенной сущности, позволяющей описывать ботов.Упрощено создание роботов (ботов) в системе взаимодействия. Работающий робот не требует запущенного клиентского приложения.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Кластер серверов.
Реализована возможность параллельного пересчета итогов регистров при реструктуризации информационной базы и при выполнении тестирования и исправления информационной базы. Для пересчета используются системные фоновые задания (идентификатор такого фонового задания SystemBackgroundJob.RecalcTotals). Реализован параметр Количество заданий пересчета итогов для диалога Параметры информационной базы. По умолчанию количество фоновых заданий пересчета итогов равно 4.

Реализованы методы глобального контекста ПолучитьКоличествоЗаданийПересчетаИтогов() и УстановитьКоличествоЗаданийПересчетаИтогов().

Пересчет итогов регистров во время реструктуризации информационной базы и при выполнении тестирования и исправления информационной базы выполнялся последовательно, по всем необходимым регистрам информационной базы.Ускорена операция пересчета итогов при выполнении реструктуризации и тестирования и исправления информационной базы.
В документации данное изменение описано здесь и здесь.
Работа с HTML.
В синтакс-помощнике для свойства ОболочкаHTMLДокумента.КодЯзыкаМакета удалена доступность в толстом клиенте.В синтакс-помощнике для свойства ОболочкаHTMLДокумента.КодЯзыкаМакета была указана доступность в толстом клиенте.Исправлена ошибка в синтакс-помощнике.
Табличный документ.
Работа с PDF-документами.
При сохранении табличного документа в формате PDF, картинки сохраняются в сжатом формате (сохраняют свой формат), если в табличный документ эти картинки вставлены в формате JPEG.При сохранении табличного документа, содержащего картинки, в формат PDF, картинки сохранялись без использования алгоритмов сжатия JPEG.Уменьшен размер PDF-документов, если исходный табличный документ содержит картинки в формате JPEG.
Расширение конфигурации.
Реализована возможность продолжать полноценную работу с конфигурацией в том случае, если при запуске конфигурации, по какой-то причине, оказались не подключены расширения, выполняющие расширение данных.

В этом случае в расширенные реквизиты будут записываться значения по умолчанию для соответствующих типов.

Если при старте сеанса подключены не все расширения, расширяющие данные, прикладное решение могло без ошибок читать данные расширяемой конфигурации успешно подключенных расширений. При этом попытка записать объект, данные которого дополняются отключенным расширением, была невозможна.Прикладное решение, в котором используются расширение, выполняющие расширение данных, полностью сохраняет свою работоспособность (за исключением не подключенных расширений) в том случае, если подключены не все расширения, выполняющие расширение данных.
В документации данное изменение описано здесь.
Общие объекты.
Для методов ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() реализована поддержка буквы «ё».Методы ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() заменяли букву «ё» на «е» и в таком виде выполняли склонение получившейся строки.При использовании методов ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() буква «ё» перестала заменяться на букву «е».
Встроенный язык.
Функция Число() позволяет преобразовывать в числа экспоненциальные представления числа только в том случае, если абсолютное значение порядка такого числа не превышает 1 000. В веб-клиенте функция Число() не поддерживает преобразование из экспоненциального представления числа.Функция Число() позволяла преобразовывать в числа экспоненциальные представления числа без ограничения значения порядка. Это могло приводить к очень большому расходу памяти и очень большим затратам времени на арифметические операции с этими значениями.Устранено незапланированное поведение системы.
Внешние компоненты.
Имя временного файла, в который сохраняется внешняя компонента перед подключением, включается имя оригинального файла с внешней компонентой. Таким образом, полное имя файла с внешней компонентой состоит из префикса (назначается платформой по стандартному алгоритму формирования имени временного файла) и суффикса (который включает имя и расширение оригинального файла с внешней компонентой, полученного из манифеста внешней компоненты).Имя временного файла, в который сохраняется внешняя компонента перед подключением, состояло только из произвольного имени временного файла (с расширением .tmp) которое формировалось системой «1С:Предприятие».Упрощена диагностика аварийных ситуаций, вызванных проблемами в подключаемых внешних компонентах. В различных журналах будет явно видно имя внешней компоненты, в которой произошла ошибка.
Прикладные объекты.
Если основным реквизитом формы выступает КонстантыНабор и при открытии формы в наборе отсутствуют константы (из-за ограничений по правам доступа или отображаемым типам), то при открытии и закрытии формы для набора констант не вызываются методы чтения и записи данных в информационную базу.Если основным реквизитом формы выступает КонстантыНабор и при открытии формы в наборе отсутствуют константы (из-за ограничений по правам доступа или отображаемым типам), то при закрытии формы, недоступные константы в информационной базе заполнялись значениями по умолчанию для своих типов.Устранено некорректное поведение системы.
Форма клиентского приложения.
Изменено поведение некоторых кнопок в формах объектов и наборов записей:
  • Кнопки Удалить, Перечитать недоступны в формах нового объекта или записи регистра сведений и таблицы внешнего источника данных.
  • Кнопка Пометить на удаление недоступна в форме нового объекта.
  • Кнопка Активировать недоступна в форме новой задачи.
  • При нажатии кнопок Скопировать, Пометить на удаление система будет предлагать выполнить сохранение объекта и затем выполнение действия или отказ от действия в формах нового объекта, новой записи регистра сведений или записи таблицы внешнего источника данных.
В формах нового объекта, записей регистра сведений или записи внешнего источника данных команды Удалить, Перечитать, Пометить на удаление, Активировать и Скопировать были доступны всегда.Устранено некорректное поведение системы.
Общие объекты.
Если у объекта ЧтениеДанных свойство КонвертируемыйРазделительСтрок не установлено или установлено в значение Символы.ВК+Символы.ПС, а в читаемом текстовом файле имеются подряд идущие символы Символы.ВК между комбинациями Символы.ВК+Символы.ПС, то метод ПрочитатьСимволы() работает следующим образом:
  • Каждая пара Символы.ВК+Символы.ПС заменяется на Символы.ПС.
  • Все остальные символы возвращаются методом «как есть».

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Если у объекта ЧтениеДанных свойство КонвертируемыйРазделительСтрок не установлено или установлено в значение Символы.ВК+Символы.ПС, а в читаемом текстовом файле имеются подряд идущие символы Символы.ВК между комбинациями Символы.ВК+Символы.ПС, то метод ПрочитатьСимволы() мог нарушать порядок символов (включая перестановку символов, удаление и добавление Символы.ВК или Символы.ПС).Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Улучшено отображение диаграммы Ганта.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Диаграмма Ганта выглядела по-другому.На диаграмме Ганта исключены слияния линий связи, уменьшено количество линий связи сложной формы, улучшен внешний вид элементов диаграммы.
Обновление конфигурации базы данных.
При использовании оптимизированного механизма реструктуризации конфигурации информационной базы, фактическая реструктуризация будет выполняться в том случае если:
  • Выполнены следующие изменениях объектов конфигурации:
    • Удаление типа из состава составного типа.
    • Удаление регистратора у регистра сведений, регистра накопления или регистра бухгалтерии.
    • Удаление значения из перечисления.
  • Таблицы реструктурируемых объектов действительно содержат данные, которые должны быть изменены в процессе обновления. Если таких данных нет никаких действий не выполняется и реструктуризация считается выполненной.

+

Оптимизированный механизм реструктуризации информационной базы всегда выполнял реструктуризацию таблиц базы данных, если в объектах конфигурации были выполнены следующие изменения:
  • Удаление типа из состава составного типа.
  • Удаление регистратора у регистра сведений, регистра накопления или регистра бухгалтерии.
  • Удаление значения из перечисления.
В ряде случаев возможно существенное повышение скорости выполнения оптимизированного механизма реструктуризации информационной базы.
Отображение информации.
Если склоняемое словосочетание, которое выступает параметром методов ПолучитьСклонениеСтроки() и ПолучитьСклонениеСтрокиПоЧислу(), содержит нарушенный баланс скобок или кавычек, то платформа автоматически восстанавливает нарушенный баланс и выполняет склонение получившегося словосочетания. При этом количество скобок или кавычек в строке, полученной в результате работы методов, полностью соответствует количеству скобок или кавычек в строке, выступающей параметром методов.Если склоняемое словосочетание, которое выступает параметром методов ПолучитьСклонениеСтроки() и ПолучитьСклонениеСтрокиПоЧислу(), содержит нарушенный баланс скобок или кавычек, то платформа генерировала исключение.Поведение методов ПолучитьСклонениеСтроки() и ПолучитьСклонениеСтрокиПоЧислу() стало более логичным.
Полнотекстовый поиск.
Если при помощи полнотекстового поиска выполняется поиск по началу строки, то в представлении результатов поиска подсвечиваются все результаты, вне зависимости от количества результатов.Если при помощи полнотекстового поиска выполняется поиск по началу строки, и в результате поиска получается большое количество слов, удовлетворяющих поисковому запросу, то в результатах поиска могли не подсвечиваться найденные слова.Устранено некорректное поведение системы.
Работа с запросами.
Конструктор запросов формирует отсутствующие псевдонимы полей запроса по такой же схеме, как и механизм исполнения запросов.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Конструктор запросов мог формировать отсутствующие псевдонимы полей запроса по схеме, которая отличалась от такого же механизма при исполнении запросов.Автоматическое формирование псевдонимов полей в запросе (в различных инструментах и механизмах платформы) стало работать по единым правилам.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализованы стандартные команды системы взаимодействия, позволяющие выполнять копирование вложение и цитировать сообщение. Для системного перечисления СтандартнаяКомандаСистемыВзаимодействия реализованы значения КопироватьВложение и ЦитироватьСообщение.

Реализован конструктор по умолчанию для объекта КоллекцияИдентификаторовПользователейСистемыВзаимодействия.

Для объекта МенеджерСистемыВзаимодействия реализованы методы ВидеоконференцииДоступны(), ПолучитьМаксимальноеКоличествоУчастниковВидеоконференции() и НачатьВидеоконференцию().

Данные возможности не предоставлялись.Расширены возможности использования системы взаимодействия.
В документации данное изменение описано здесь.
Внешние компоненты.
Веб-клиент.
При попытке использовать несуществующее свойство или метод внешней компоненты в веб-клиенте, сообщается об ошибке, которую можно перехватить в рамках конструкции Попытка - Исключение. При этом вызов метода или обращение к свойству вообще не начинается.

Поведение в тонком и толстом клиентских приложениях соответствует описанному поведению веб-клиента (поведение не изменилось).

При попытке использовать несуществующее свойство или метод внешней компоненты в веб-клиенте, веб-клиент пытался выполнить вызов. Если метод или свойство отсутствовало, то ошибка попадала только в обработчик ошибки, который был указан в описании оповещения. Ошибка не могла быть перехвачена в рамках конструкции Попытка - Исключение.Поведение веб-клиента стало аналогичным поведению тонкого и толстого клиентских приложений.
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Реализована доступность объектов НастройкиНачальнойСтраницы и СоставФормНачальнойСтраницы на сервере мобильного приложения и на мобильном автономном сервере.Объекты НастройкиНачальнойСтраницы и СоставФормНачальнойСтраницы были недоступны на сервере мобильного приложения и на мобильном автономном сервере.На мобильном устройстве стала возможна настройка начальной страницы приложения.
Форма клиентского приложения.
В толстом клиенте и конфигураторе оптимизировано отображение табличного поля, в шапке или подвале которого содержится большое количество колонок, сгруппированных в многострочную составную колонку с использованием свойства Положение колонки табличного поля.В толстом клиенте и конфигураторе отображение табличного поля, в шапке или подвале которого содержится большое количество колонок, сгруппированных в многострочную составную колонку с использованием свойства Положение колонки табличного поля, выполнялось с задержками.Устранено некорректное поведение системы.
Система компоновки данных.
Генератор макетов системы компоновки данных вычисляет ширину (в ячейках) каждого макета ресурсов, выводимого в колонке таблицы системы компоновки данных, как максимальную ширину всех макетов, выводимых в данной колонке таблицы системы компоновки данных (как сгенерированных, так и предопределенных макетов). Таким образом, если для макетов группировок и ресурсов указаны предопределенные макеты, то для этих группировок не учитывается количество ресурсов, указанных для них в настройках компоновки данных.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Генератор макетов системы компоновки данных вычислял ширину (в ячейках) каждого макета ресурсов, выводимого в колонке таблицы системы компоновки данных, на основании всех выводимых в данный макет ресурсов (в настройках компоновки данных) и предопределенных макетов. Таким образом, если для какого-либо макета ресурсов, заданного для пересечения строки/колонки таблицы, предполагаемая ширина макета была больше, чем ширина предопределенного макета, то ширина создаваемого макета была равна предполагаемой ширине.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
В том случае, когда система компоновки данных выполняет группировку по вычисляемому полю, то в этой группировке (и в ее вложенных группировках), при выводе такого поля в результат компоновки данных, используется выражение представления этого поля (если указано).

В режиме совместимости с версией 8.3.17 поведение не изменилось.

В том случае, когда система компоновки данных выполняет группировку по вычисляемому полю, то представление вычисляемого поля выводилось только в детальных записях.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Для таблицы, отображающей дерево значений с одной колонкой, реализован следующий алгоритм вычисления ширины колонки, в зависимости от ширины текста, находящего в строках отображаемого дерева:
  • Для ячеек таблицы, у которых выключен автоматический расчет высоты ячейки, ширина ячейки таблицы рассчитывается на основании ширины отображаемого в ячейках текста.
  • Для ячеек таблицы, у которых включен автоматический расчет высоты ячейки, ширина ячейки таблицы рассчитывается на основании ширины, заданной в свойствах колонки при разработке конфигурации. Если в видимой области таблицы для отображения текста остается меньше половины от ширины таблицы, то ширина области текста становится равной ширине таблицы, при условии что эта ширина больше ширины выделенной области.
  • Фактическая ширина колонки таблицы вычисляется как максимальная ширина всех ячеек, отображаемых в видимой области таблицы.

Для таблицы, у которой при выборе строки выделяется ячейка (а не вся строка), при переходе по строкам таблицы, а также при активизации строки мышью, осуществляется горизонтальная прокрутка таким образом, чтобы текст полностью отображался в видимой области таблицы. Если текст полностью не умещается в видимой области, то осуществляется выравнивание области текста по левому краю таблицы.

Для таблицы, отображающей дерево значений с одной колонкой, ширина колонки и положение текста в колонке, никак не зависело от текста, отображаемого в дереве.Устранено некорректное поведение системы.
Расширение конфигурации.
При использовании в расширениях конфигурации аннотации ИзменениеИКонтроль, проверка применимости не учитывает изменения, в которых добавляются или удаляются пустые строки и строки, состоящие только из символов пробелов и табуляций.При использовании в расширениях конфигурации аннотации ИзменениеИКонтроль, проверка применимости учитывала изменения, в которых добавлялись или удалялись пустые строки и строки, состоящие только из символов пробелов и табуляций.Снижено количество ошибочных срабатываний механизма проверки применимости расширений.
В документации данное изменение описано здесь.
Табличный документ.
Мобильная платформа.
Мобильный клиент.
Улучшено преобразование табличного документа в компактное представление (на мобильном устройстве):
  • Стали возможны переносы ячеек табличного документа, которые размещены под горизонтальным объединением ячеек.
  • Для перенесенных ячеек реализовано автоматическое выделение цветом. Одним цветом выделяется одна колонка табличного документа. Выделение цветом не применяется в том случае, если для ячейки табличного документа явно указан цвет текста.
  • Цветовое выделение также не выполняется в том случае, если при преобразовании табличного документа в компактный вид не выполняется перенос ячеек.
  • Цвет разделительных линий табличного документа стал более светлым.
Алгоритм преобразования табличного документа в компактное представление был другим. Получавшийся табличный документ не вполне подходил для использования на мобильном устройстве.Улучшено отображение табличного документа на мобильном устройстве (компактное представление табличного документа).

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Расширение конфигурации.
Вызов методов расширяемой формы из расширения с помощью метода Выполнить() более не поддерживается. Вызывать можно только те методы, которые доступны через свойство ЭтотОбъект.

Рекомендуется выполнить анализ расширений и, при необходимости, провести их рефакторинг.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Поддерживался вызов методов расширяемой формы из расширения с помощью метода Выполнить(). Расширение формы может использовать только документированный интерфейс использования расширяемой формы. Под «документированным интерфейсом» понимаются методы, объявленные в модуле формы с использованием ключевого слова Экспорт.
В документации данное изменение описано здесь.
Средства администрирования.
Файл вывода служебных сообщений, который указывается в параметре /Out командной строки запуска клиентских приложений и конфигуратора, формируется в кодировке UFT-8.Файл вывода служебных сообщений, который указывается в параметре /Out командной строки запуска клиентских приложений и конфигуратора, формировался в системной кодировке операционной системы.Файл вывода служебных сообщений всегда формируется в одинаковой кодировке, независимо от кодировки операционной системы.
В документации данное изменение описано здесь.
Работа в ОС Linux.
Системные требования.
Автономный сервер.
При работе в операционной системе Linux реализована возможность одновременной установки нескольких версий системы «1С:Предприятие», в том числе различающихся только последней (четвертой) цифрой номера.

Реализован автоматически подбор версии запускаемого клиентского приложения.

Изменен запуск кластера серверов и расположение файлов srv1cv83 и srv1cv83.conf.

Реализована возможность автоматического обновления клиентского приложения по сети и через веб-сервер. В диалоге публикации веб-клиента (в Linux-версии конфигуратора) реализована возможность указания расположения дистрибутивов клиентского приложения.

Для файла conf.cfg реализованы параметры PublishDistributiveLocationLinuxDEB64, PublishDistributiveLocationLinuxDEB32, PublishDistributiveLocationLinuxRPM64, PublishDistributiveLocationLinuxRPM32. Для элемента <point> файла default.vrd реализованы атрибуты pubdstlindeb64, pubdstlindeb32, pubdstlinrpm64, pubdstlinrpm32.

Для параметра pubdst конфигурационного файла автономного сервера реализованы свойства lindeb64, lindeb32, linrpm64, linrpm32.

Данные возможности не предоставлялись.При работе под управлением ОС Linux стало возможно одновременное использование нескольких версий системы «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Отображение информации.
Параметр Параметры метода СтрокаСЧислом() переименован в ФорматнаяСтрокаЧисла. В этот параметр может передаваться форматная строка числа, аналогичная методу Формат().

Метод СтрокаСЧислом() формирует представление числа с учетом локализации текущего сеанса или переданной форматной строки.

Метод СтрокаСЧислом() всегда формировал представление числа с учетом кода локализации, переданного в качестве параметра метода и не учитывал локализацию текущего сеанса.Устранено некорректное поведение системы.

Результат работы метода СтрокаСЧислом() теперь соответствует локализации текущего сеанса.

Прикладные объекты.
Для журналов документов реализованы следующие изменения:
  • Строки таблицы журнала документов соответствующие документам, на которые отсутствует право Чтение, не могут быть получены с использованием языка запросов (динамический список, система компоновки данных).
  • Строки таблицы журнала документов соответствующие документам, на которые отсутствует право Просмотр, не могут быть получены с помощью системы компоновки данных при включенной проверке интерактивных прав, например, в динамическом списке и по умолчанию в отчётах.
  • Графа журнала документов доступна в том случае, если доступен хотя бы один реквизит, входящий в эту графу.
  • В системе компоновки данных интерактивные свойства графы журнала документов Режим пароля, Формат, Подсказка, Выделять отрицательные и Многострочный режим получаются из соответствующих свойств реквизитов документов, входящих в графу журнала.
  • В системе компоновки данных используется свойство Быстрый выбор для полей с типами ссылок на объектные таблицы внешних источников данных.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Для журналов документов наблюдалось следующее поведение:
  • Строки таблицы журнала документов соответствующие документам, на которые отсутствует право Чтение, можно было получить с использованием языка запросов, если имелось право Чтение на таблицу журнала.
  • Строки таблицы журнала документов соответствующие документам, на которые отсутствует право Просмотр, не могли быть получены с помощью системы компоновки данных при включенной проверке интерактивных прав, например, в динамическом списке и по умолчанию в отчётах.
  • Графа журнала документов была доступна в том случае, если были доступны все реквизиты, входящие в эту графу.
  • В системе компоновки данных интерактивные свойства графы журнала документов Режим пароля, Формат, Подсказка, Выделять отрицательные и Многострочный режим не получались из соответствующих свойств реквизитов документов, входящих в графу журнала.
  • В системе компоновки данных не использовалось свойство Быстрый выбор для полей с типами ссылок на объектные таблицы внешних источников данных.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система взаимодействия.
Переработан механизм работы с действиями в сообщениях системы взаимодействия.

Для создания списка действий реализован тип КоллекцияДействийСообщенияСистемыВзаимодействия. Для свойства СообщениеСистемыВзаимодействия.Действия типом значения становится КоллекцияДействийСообщенияСистемыВзаимодействия. В режиме совместимости с версией 8.3.17 поведение не изменилось.

Для модуля приложения реализован обработчик события ПриВыбореДействияСистемыВзаимодействия.

Методы менеджера системы взаимодействия ПодключитьОбработчикДействияСообщения() и ОтключитьОбработчикДействияСообщения() являются устаревшими и не рекомендуются для использования.

В прикладных решениях необходимо изменить алгоритмы работы с действиями в сообщениях системы взаимодействия.

Для указания списка действия системы взаимодействия использовался список значений. Для установки обработчиков действия сообщения системы взаимодействия было необходимо использовать методы менеджера системы взаимодействия ПодключитьОбработчикДействияСообщения() и ОтключитьОбработчикДействияСообщения().Схема работы с действиями унифицирована с другими механизмами платформы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если в запросе схемы компоновки данных используется объединение, и во всех частях объединения поле, к которому применяется отбор, доступно только для применения отбора (и недоступно для выбора), то отбор применяется только в тех частях объединения, где это поле доступно для отбора.

Рекомендуется проанализировать схемы компоновки данных, которые содержат запросы с объединениями.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

При применении отбора к запросу набора данных, содержащего объединение, отбор обязательно применялся ко всем частям объединения, если хотя бы в одной части объединения поле было доступно для отбора.Результат применения отбора в схеме компоновки данных стал более ожидаемым.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
При установке значения свойства СписокПолнотекстовогоПоиска.ОбластьПоиска генерируется исключение в том случае, если устанавливаемый массив содержит элемент, который не является объектом метаданных.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

При установке значения свойства СписокПолнотекстовогоПоиска.ОбластьПоиска не выполнялась проверка корректности устанавливаемого значения, однако при попытке получить результат поиска (метод СписокПолнотекстовогоПоиска.ПерваяЧасть()) генерировалось исключение с непонятным текстом.Проверка корректности параметров приведена в соответствие со стандартными практиками. Сообщение об ошибке стало соответствовать обнаруженной ошибке.
В документации данное изменение описано здесь.
Диаграммы.
Свойство диаграммы ИсточникДанных недоступно в тонком клиенте и веб-клиенте. При попытке установить значение данного свойства из встроенного языка - генерируется ошибка.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Попытка установить свойство диаграммы ИсточникДанных зависела от клиентского приложения:
  • В веб-клиенте генерировалась ошибка.
  • В тонком клиенте установка срабатывала и данные отображались диаграммой до первого серверного вызова. После первого серверного вызова связи диаграммы с данными терялась.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Не поддерживается интерактивное редактирование диаграммы с установленным источником данных.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Для диаграммы с установленным источником данных наблюдалось следующее поведение при попытке интерактивного редактирования:
  • Значения диаграммы редактировались.
  • Значения в источнике данных не изменялись.
  • При изменении значений в источнике данных - все изменения, сделанные вручную терялись и диаграмма начинала отображать данные из источника данных.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Настройки окна для тонкого клиента, веб-клиента, мобильного клиента и мобильной платформы хранятся с разными суффиксами ключей настроек. При изменении режима совместимости конфигурации выполняются следующие действия:
  • При установке режима совместимости Не использовать:
    • Для существующих настроек создаются 2 новых копии с новыми ключами настроек (для мобильного клиента и мобильной платформы).
    • Для существующих ключей настроек выполняется замена суффикса ключа настроек НастройкиОкна на значение НастройкиОкнаТонкогоКлиента.
  • При установке режима совместимости Версия 8.3.17:
    • Удаляются настройки для мобильной версии и мобильной платформы.
    • Для остающихся настроек в значениях ключей выполняется замена суффикса ключа настроек НастройкиОкнаТонкогоКлиента на значение НастройкиОкна.

Новые ключи настроек приведены в документации. +Если в конфигурации используется непосредственная работа с настройками окон, то рекомендуется проанализировать программный код, работающий с настройками и внести в него соответствующие изменения.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Данные возможности не предоставлялась.

Настройки хранились раздельно для веб-клиента (одна настройка) и всех остальных клиентских приложений (другая настройка).

Настройки окон клиентского приложения для разных видов клиентских приложений хранятся раздельно и не смешиваются друг с другом. Стало проще реализовать программную работу с настройками окон какого-то одного вида клиентского приложения.
В документации данное изменение описано здесь, здесь и здесь.
Система компоновки данных.
Если для отбора компоновки данных, заданного на уровне набора данных, указано условие Содержит, Не содержит, Подобно, Не подобно, Начинается с и Не начинается с, и строка с условием содержит символ ««» (одиночная двойная кавычка), то система компоновки данных автоматически экранирует такие символы при формировании макета компоновки данных.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Если для отбора компоновки данных, заданного на уровне набора данных, указано условие Содержит, Не содержит, Подобно, Не подобно, Начинается с и Не начинается с, и строка с условием содержит символ ««» (одиночная двойная кавычка), то система компоновки данных не экранировала такие символы при формировании макета компоновки данных. В результате исполнение такой компоновки данных могло привести к ошибке.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Регистры сведений.
В результат запроса к виртуальной таблице регистра сведений СрезПоследних попадают только те записи регистра, для которых свойство Активность установлено в значение Истина.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

В результат запроса к виртуальной таблице регистра сведений СрезПоследних попадали все записи регистра, вне зависимости от значения свойства Активность.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Ввод по строке.
Глобальный поиск.
Динамический список.
Полнотекстовый поиск.
Реализовано ограничение сложности поискового запроса. Общая длина поискового запроса не должна превышать 1 000 символов и 32 слов. Ограничения реализованы для следующих механизмов:
  • Ввод по строке.
  • Глобальный поиск.
  • Строка поиска динамического списка.
  • Полнотекстовый поиск.

В структуре параметров метода ПолучитьДанныеВыбора() ожидается наличие параметра ОграничиватьСтрокуПоиска, который позволяет выполнить поиск без анализа поискового запроса.

Реализовано свойство СписокПолнотекстовогоПоиска.ОграничиватьСтрокуПоиска. Если данное свойство установлено в значение Ложь, то механизм полнотекстового поиска не выполняет анализ поискового запроса.

В режиме совместимости с версией 8.3.17 поведение не изменилось. +

Отсутствовало ограничение на сложность поискового запроса, кроме поисковой строки динамического списка, где строка поиска не должна была превышать 1 000 символов и 20 слов.Ограничена сложность поискового запроса к встроенным инструментам поиска для предотвращения высокой нагрузки на сервер и возможного аварийного завершения работы из-за слишком сложного поискового запроса.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Внешние компоненты.
Примеры из технологии разработки внешних компонент переведены на сборку с помощью утилиты CMake.

Статические библиотеки для создания адаптеров веб-браузеров для ОС Windows собраны с помощью компилятора от Microsoft Visual Studio 2017 с поддержкой Windows XP.

Разработчики, которые разрабатывают тиражные внешние компоненты, должны поддерживать работу компоненты для все операционных систем из списка системных требований (см. здесь). Сборка адаптеров веб-клиента для ОС Windows должна выполняться компилятором от Microsoft Visual Studio 2017 с поддержкой Windows XP.

Разработчики, внешние компоненты которых разработаны для конкретного внедрения, могут использовать тот компилятор, какой они использовали для поддерживаемых версий операционных систем. Для сборки адаптеров веб-клиента для ОС Windows, тем не менее, следует использовать компилятор от Microsoft Visual Studio 2017 с поддержкой Windows XP.

Внесены изменения в технологию создания внешних компонент (см. здесь).

Примеры из технологии разработки внешних компонент собирались с помощью Microsoft Visual Studio 2013.Для сборки демонстрационных внешних компонент используется более современный инструментарий.
Форма клиентского приложения.
Перенос строки, не умещающейся по ширине в декорациях, полях надписи или заголовках полей, выполняется по разделителю слов, ближайшего к границе элемента формы.

При снятии режима совместимости рекомендуется проверить корректность отображения форм с текстами, которые не помещаются по ширине в декорациях, полях надписи или заголовках полей.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Перенос строки, не умещающейся по ширине в декорациях, полях надписи или заголовках полей, мог выполняться по разделителю слов, который не являлся ближайшим к границе элемента формы.Устранено некорректное поведение системы.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Системные имена событий журнала регистрации.
  • _$InfoBase$_.InfoBaseAdmParamsUpdate;
  • _$InfoBase$_.InfoBaseAdmParamsUpdateError;
  • _$InfoBase$_.TARInfo;
  • _$InfoBase$_.TARMess;
  • _$InfoBase$_.TARImportant;
  • _$InfoBase$_.SecondFactorAuthTemplateNew;
  • _$InfoBase$_.SecondFactorAuthTemplateUpdate;
  • _$InfoBase$_.SecondFactorAuthTemplateDelete.
  • _$InfoBase$_.ParametersUpdate;
  • _$InfoBase$_.ParametersUpdateError;
  • _$InfoBase$_.VerifyAndRepairInfo;
  • _$InfoBase$_.VerifyAndRepairMessage;
  • _$InfoBase$_.VerifyAndRepairImportant;
  • _$InfoBase$_.SecondAuthenticationFactorTemplateNew;
  • _$InfoBase$_.SecondAuthenticationFactorTemplateUpdate;
  • _$InfoBase$_.SecondAuthenticationFactorTemplateDelete.
Описание в конфигураторе имени свойства, содержащего роли, которые будет ограничивать возможности пользователя, работающего на мобильном устройстве. +
  • Роли ограничения автономной конфигурации.
  • Роли ограничения автономного мобильного приложения.
Флажок диалога проверки конфигурации, отвечающий за проверку конфигурации в автономном режиме.
  • Мобильный клиент (автономный режим).
  • Мобильный клиент (автономный режим) и мобильный автономный сервер.
Английские варианты имени метода Файл.Существует() и имени свойства ДиалогВыбораФайла.ПроверятьСуществованиеФайла.

Старые варианты имен поддерживаются для совместимости.

  • File.Exist().
  • FileDialog.CheckFileExist.
  • File.Exists().
  • FileDialog.CheckFileExistence.
Английский вариант наименования метода КопироватьФайл().
  • FileCopy().
  • CopyFile().
Наименование метода проверки того, что покупка была приобретена. Старое наименование поддерживается для совместимости.
  • Приобретена().
  • ПроверитьПриобретение().
Имена файлов с установочными пакетами ОС Linux, которые содержат дистрибутивы клиентских приложений.
  • win-mac-clients-distr-A.B.C-D.i386.rpm;
  • win-mac-clients-distr-A.B.C-D.x86_64.rpm;
  • win-mac-clients-distr_A.B.C-D_amd64.deb;
  • win-mac-clients-distr_A.B.C-D_i386.deb.

В данном списке A.B.C-D - это полный номер версии системы «1С:Предприятие».

  • win-mac-clients-A.B.C.D-distr-A.B.C-D.i386.rpm;
  • win-mac-clients-A.B.C.D-distr-A.B.C-D.x86_64.rpm;
  • win-mac-clients-A.B.C.D-distr_A.B.C-D_amd64.deb;
  • win-mac-clients-A.B.C.D-distr_A.B.C-D_i386.deb.

В данном списке A.B.C.D и A.B.C-D - это полный номер версии системы «1С:Предприятие».

В документации данное изменение описано здесь.
Свойство глобального контекста, которое позволяет получить доступ к данным ссылки, которая использовалась для запуск прикладного решения. Старое наименование свойства поддерживается для совместимости.

+

  • НавигационнаяСсылкаЗапуска.
  • ДанныеПереходаПоНавигационнойСсылкеЗапуска.
В документации данное изменение описано здесь.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
Реализована возможность управлять автоматическим поворотом снимка при использовании метода СредстваМультимедиа.СделатьФотоснимок(). Для этого в данном методе реализован параметр АвтоПоворот.При использовании метода СредстваМультимедиа.СделатьФотоснимок() мобильная версия всегда осуществляла поворот получившегося снимка, если ориентация телефона в момент фотосъемки не соответствовала ориентации получившейся фотографии.Стало возможно ускорить фотосъемку за счет отказа от поворота получившейся фотографии.
В документации данное изменение описано здесь.
Форма клиентского приложения.
В системной форме, которая формируется для редактирования строки таблицы формы (не связанной с динамическим списком), реализована группировка полей, если такая группировка реализована в настройках таблицы. В форме воссоздаются только первый уровень группировки. Более глубокие уровни группировки не воссоздаются на форме. Все поля более глубоких уровней группировки размещаются в родительской группе первого уровня.В системной форме, которая формируется для редактирования строки таблицы формы (не связанной с динамическим списком), все поля строки таблицы располагались плоским списком, без группировки.Улучшена автоматически формируемая форма редактирования строки таблицы формы.
В документации данное изменение описано здесь.
Средства разработки.
В диалоге Сервис - Параметры - Модули - Проверка реализована возможность настроить проверку модуля в автономном режиме мобильного клиента. Реализован флажок Мобильный клиент (автономный режим) и мобильный автономный сервер.Данная возможность не предоставлялась.Упрощена оперативная проверка модулей, которые должны работать в автономном режиме мобильного клиента.
В документации данное изменение описано здесь и здесь.
Средства печати.
Мобильная платформа.
Мобильный клиент.
Для мобильного приложения реализована возможность печати на принтерах, которые поддерживаются используемой мобильной операционной системой.

Переключение между возможностью печати через операционную системы и средствами платформы (принтера, поддерживающие языки PCL3 и ZPL) осуществляется в настройках информационной базы на мобильном устройстве (меню Сервис и настройки - Настройки) или в сборщике мобильных приложений (свойство настроек приложения Режим печати).

Мобильная версия системы «1С:Предприятие» поддерживала печать только на принтерах, поддерживающих языки PCL3 и ZPL.Расширен список принтеров, на которых может печатать мобильная версия системы «1С:Предприятие».
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Переработан механизм управления разрешениями мобильного приложения, собираемого с помощью сборщика мобильных приложений. Реализован механизм функциональностей, который объединяет собственно разрешение мобильного приложения, текст, который отображается пользователю при запросе того или иного разрешения и включение в состав мобильного приложения модуля мобильной версии, отвечающего за функциональность.

Таким образом, выключенная функциональность приведет к тому, что соответствующий модуль не будет включен в сборку, а при попытке использовать эту функциональность - может быть сформировано исключение времени исполнения (на мобильном устройстве).

Доступ к настройке функциональностей мобильного приложения выполняется с помощью свойства конфигурации Используемая функциональность мобильного приложения.

Перед сборкой конфигурации, которая выгружается с помощью версии 8.3.18, рекомендуется проверить, что для конфигурации корректно указана требуемая функциональность.

Механизм управления разрешениями мобильного приложения был другим. Он не влиял на итоговый размер собираемого приложения. Выключенное разрешение могло никак не влиять на работоспособность собранного приложения.Управление используемой функциональностью мобильного приложения стало более четким и формальным. Указывая ту или иную функциональность, разработчик должен также указать текст, который будет видеть пользователь при запросе того или иного разрешения, а также сделает возможным использование этой функциональности.
В документации данное изменение описано здесь и здесь.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Работа с запросами.
Общие реквизиты / Разделение данных.
При работе в файловом варианте информационной базы ускоряется выполнение запроса, в котором выполняется внутреннее соединение между данными объекта и его табличной части. Ускорение будет наблюдаться в том случае, если объект, используемый в запросе, входит в состав общего реквизита, являющегося разделителем.При работе в файловом варианте информационной базы выполнение запроса, в котором для объекта, входящего в состав разделителя, выполняется внутреннее соединение между данными объекта и его табличной части, занимало больше времени.Устранено некорректное поведение системы.
Средства разработки.
Реализована возможность использовать сочетание клавиш Ctrl+Alt+E для прерывания длительных операций при работе под управлением ОС Windows. Использование для этой цели сочетания клавиш Ctrl+Break сохраняется. Оба сочетания клавиш могут использовать одновременно.Для прерывания длительных операций можно было использовать сочетание клавиш Ctrl+Break при работе под управлением ОС Windows.Стало возможно прерывать выполнение длительных операций на устройствах, клавиатура которых не содержит клавиши Break.
Диаграммы.
Подсказка диаграммы больше не перекрывается полем форматированного документа и полем планировщика. Подсказка диаграммы отображается без полупрозрачности в том случае, если тонкое или толстое клиентское приложение работает под управлением ОС Linux и macOS.Подсказка диаграммы могла перекрываться полем форматированного документа и полем планировщика (часть информации в подсказке становилась недоступной для просмотра).Устранено некорректное поведение системы.
Расширение конфигурации.
Реализована возможность изменять данные объекта конфигурации, типы реквизитов которого изменены расширением, которое в данный момент отключено (неактивное расширение).

При чтении объектов с типами реквизитов, которые модифицированы отключенными расширениями конфигурации, значения, хранимые в базе данных. будут преобразовываться к типам конфигурации без учета неактивных расширений.

При записи будут обновляться только те реквизиты, которые реально изменены.

В отчет об ошибке добавляется информация об отключенных расширениях. Изменен формат файла report.json, в который помещается автоматически собираемая информация об ошибке.

Данный режим рекомендуется использовать только как авариный режим работы, когда необходимо выполнить обновление информационной базы прикладного решения при наличии расширений, которые несовместимы с новой версией конфигурации.

Было невозможно изменять данные объекта конфигурации, типы реквизитов которого изменены расширением, которое в данный момент отключено (неактивное расширение).Упрощено обновление конфигурации в том случае, когда расширение, модифицирующее типы реквизитов расширяемой конфигурации, становится неактивно после обновления расширяемой конфигурации.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Реализована возможность открывать мобильное приложение при переходе по навигационной ссылке. Схемы и ссылки, на которые реагирует мобильное приложение, могут быть настроены в конфигураторе и сборщике мобильных приложений. В конфигурации реализована возможность обрабатывать ситуацию перехода в приложение по навигационной ссылке.

Реализовано свойство конфигурации НавигационныеСсылкиМобильногоПриложения. В модуле приложения реализован обработчик ОбработкаПереходаПоНавигационнойСсылке(). Для глобального контекста реализован метод ПолучитьВнешнююНавигационнуюСсылку(). +

Данная возможность не предоставлялась. Мобильное приложение не могло быть вызвано из другого приложения, например, при размещении в электронном письме особой гиперссылки.Расширены возможности мобильной версии системы «1С:Предприятие». Стало возможно регистрировать навигационные ссылки особого вида, при нажатии на которых (в другом приложении) будет автоматически открываться мобильное приложение.
В документации данное изменение описано здесь, здесь и здесь.
Системные требования.
Реализована поддержка работы «1С:Предприятия» под управлением ОС Microsoft Windows Server 2019 (x86-64).Не поддерживалась работа «1С:Предприятия» под управлением ОС Microsoft Windows Server 2019 (x86-64).Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Форма клиентского приложения.
В форме клиентского приложения реализована возможность обрабатывать следующие события расширения поля формы для поля планировщика:
  • Выделение пустой области планировщика для создания элемента планировщика.
  • Выделение элементов планировщика.
  • Перетаскивание или изменение границ одного или нескольких элементов планировщика.
  • Копирование одного или нескольких элементов планировщика.

Реализован обработчик события расширения поля формы клиентского приложения для поля планировщика ПроверкаПеретаскиванияВнутри.

Для обработчика события расширения поля формы клиентского приложения для поля планировщика ПередСозданием следующие параметры становятся возвращаемыми: Начало, Конец, ЗначенияИзмерений, Текст.

Перетаскивание элементов внутри поля планировщика и изменение размера элементов поля планировщика были недоступны для обработки.Расширены возможности интерактивного редактирования поля планировщика.
В документации данное изменение описано здесь и здесь.
Обработка ошибок.
Реализована новая категория ошибок: ошибка копии базы данных. Ошибки, возникающие во время работы с копиями базы данных попадают в эту категорию.

Реализовано значение системного перечисления КатегорияОшибки.ОшибкаКопииБазыДанных.

В режиме совместимости с версией 8.3.17 поведение не изменилось.

Ошибки, возникающие при работе с копиями базы данных, попадали в категорию ошибок внешнего источника данных.Улучшена категоризация ошибок.
Табличный документ.
Веб-клиент.
Оптимизировано обновление табличного документа, отображаемого в веб-клиенте с масштабом больше 100%, при редактировании текста в ячейках. При окончании редактирования текста в ячейке не происходит обращения к серверу, если введенный текст умещается в ячейку по ширине и высоте.При окончании редактирования текста в ячейке табличного документа, отображаемого в веб-клиенте с масштабом более 100%, происходило обращение к серверу, если введенный текст умещался в ячейку по ширине и высоте.Устранено некорректное поведение системы.
Работа с Интернет.
Реализовано свойство ИнформацияОСетевомАдаптере.IPАдрес. Свойство содержит IP-адрес сетевого адаптера, который описывает объект ИнформацияОСетевомАдаптере.Данная возможность не предоставлялась.Расширена информация о сетевом адаптере, предоставляемая платформой «1С:Предприятие».
Полнотекстовый поиск.
Обработка ошибок.
Попытка выполнить поиск по слову, для которого найдено очень большое количество вхождений, приводит к ошибке. Снижен размер индекса полнотекстового поиска для очень больших информационных баз.

Реализовано значение системного перечисления КатегорияОшибок.ОшибкаПолнотекстовогоПоиска.

Рекомендуется очистить индекс полнотекстового поиска и заново его построить, если размер индекса полнотекстового поиска превышает 50 Гбайт.

При запуске предыдущей версии платформы с индексом полнотекстового поиска, построенным платформой версии 8.3.19 - индекс будет очищен и построен заново.

Попытка выполнить поиск по слову, для которого найдено очень большое количество вхождений, могло приводить к непредсказуемым результатам.Повышена стабильность и устойчивость работы полнотекстового поиска.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 12.4.1,
  • Postgres Pro Standard 12.4.1,
  • Postgres Pro Enterprise 12.4.1.
Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 12.4.1,
  • Postgres Pro Standard 12.4.1,
  • Postgres Pro Enterprise 12.4.1.
Расширен список поддерживаемых СУБД.
Сборщик мобильных приложений.
Версия сборщика мобильных приложений стала совпадать с номером мобильной версии «1С:Предприятия», с которой сборщик поставляется. Таким образом, сборщик мобильных приложений,который поставляется с мобильной версией 8.3.18 имеет номер версии 8.3.18.*. Четвертая цифра номера версии сборщика обозначает номер сборки сборщика и не имеет отношения с четвертой цифре номера мобильной версии системы «1С:Предприятие».

+

Сборщик мобильных приложений имел нумерацию, которая не совпадает с номером мобильной версии системы «1С:Предприятие».Нумерация сборщика мобильных приложений стала более понятной и стала связана со «своей» мобильной версией системы «1С:Предприятие».
Сборщик мобильных приложений.
Сборщик мобильных приложений не поддерживает использование мобильных версий системы «1С:Предприятие», чей номер (первые три цифры) больше, чем номер версии сборщика (первые три цифры). Сборщик мобильных приложений 8.3.18 не загрузит мобильную версию 8.3.19 и последующие версии.

При этом сборщик по прежнему позволяет загружать предшествующие мобильные версии системы «1С:Предприятие» (8.3.17 и предыдущие).

В сборщике мобильных приложений реализована блокировка загрузки конфигураций, формат которых не поддерживается текущей версией сборщика.

В сборщике мобильных приложений не стояло ограничений на загрузку мобильных конфигураций и мобильных версий системы «1С:Предприятие». Это могло приводить к труднодиагностируемым проблемам в тех случаях, когда в сборщик загружали конфигурации или мобильные версии, которые не поддерживались сборщиком.Сборщик мобильных приложений более не поддерживает загрузку объектов, работу с которыми он не поддерживает.
В документации данное изменение описано здесь и здесь.
Работа в ОС Linux.
Системные требования.
Реализована поддержка следующих дистрибутивов ОС Linux:
  • Альт Образование 9.
  • Альт Рабочая станция 9.
  • Альт Рабочая станция К 9.
  • Альт Сервер 9.

Прекращена поддержка следующих дистрибутивов ОС Linux:

  • Альт Линукс 6.0 СПТ.
  • Альт Рабочая станция 7.
  • Альт Сервер 7.
Поддерживались следующие дистрибутивы ОС Linux:
  • Альт Линукс 6.0 СПТ.
  • Альт Рабочая станция 7.
  • Альт Сервер 7.
Актуализирован список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь и здесь.
Глобальный поиск.
Изменен алгоритм выполнения стандартного вида глобального поиска Данные. В результате изменения поиск стал возвращать более релевантный результат за меньшее время.

Описание алгоритма приведено в документации.

При выполнении стандартного вида глобального поиска Данные результат мог плохо соответствовать поисковой строке.Повышена релевантность и скорость выполнения стандартного вида глобального поиска Данные.
В документации данное изменение описано здесь.
Система лицензирования.
Для дистрибутивов системы, предназначенных для ОС Windows XP, включен HASP Device Driver версии 7.63.

Из состава дистрибутива удалены устаревшие файлы haspds_windows.dll и hdinst_windows.dll.

Для дистрибутивов системы, предназначенных для ОС Windows XP, включен HASP Device Driver версии 7.92, который не запускался в этой операционной системе.Пользователи ОС Windows XP могу установить HASP Device Driver непосредственно из актуального дистрибутива системы «1С:Предприятие», без дополнительных поисков этого драйвера.
Встроенный язык.
Оптимизирована работа методов Вставить() и Получить() объекта Соответствие для случаев, когда в качестве ключа соответствия используется ссылка на объект информационной базы.Наблюдалась низкая производительность работы методов Вставить() и Получить() объекта Соответствие для случаев, когда в качестве ключа соответствия используется ссылка на объект информационной базы.Устранено некорректное поведение системы.
Специальные возможности мобильного устройства.
Переработан механизм встроенных покупок. Механизм покупок основан на библиотеке Google Play Billing 3.

Для метода ВстроенныеПокупки.ОбновитьИнформациюОПриобретении() реализованы параметры ТипПокупки и АвтоПодтверждение. Для методов ВстроенныеПокупки.НачатьПриобретение() и ВстроенныеПокупки.ПриобрестиАсинх() реализован параметр АвтоПодтверждение.

Для объекта МенеджерВстроенныхПокупок реализованы методы ПоддерживаетсяПодтверждениеПокупок(), ПроверитьПодтверждение(), ПодтвердитьПокупку().

Для сборки мобильного приложения, поддерживающего новый механизм встроенных покупок, необходимо использовать сборщик мобильных приложений версии 8.3.18 или последующие версии.

Рекомендуется выполнить рефакторинг прикладного решения с целью перехода на новый интерфейс работы со встроенными покупками.

Прежний механизм покупок поддерживается только в режиме совместимости с версией 8.3.17 и предыдущих.

Механизм встроенных покупок был основан на сервисе Google Play через Android Interface Definition Languages.Реализована поддержка механизма монетизации мобильных приложений, который будет обязателен при публикации в магазине Google Play, начиная с августа 2021 года.
В документации данное изменение описано здесь и здесь.
Сервис интеграции.
Реализована возможность получать состояние подключения к внешнему сервису интеграции. Реализована возможность получения и удаления сообщений, которые находятся в канале сервиса интеграции.

Для менеджера канала внешнего сервиса интеграции реализованы методы ПолучитьСостояние(), ВыбратьСообщения() и УдалитьСообщения().

Данные возможности не предоставлялась.

Сообщение при отправке могло только устареть. Если при отправке сообщения возникала ошибка, то такое сообщение блокировало работу канала.

Расширены возможности работы с сообщениями в канале внешнего сервиса интеграции.
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
Мобильная платформа.
Мобильный клиент.
В сборщике мобильных приложений реализована возможность выполнять сборку мобильных приложений для ОС iOS в том случае, если для сборки используется компьютер Mac, который базируется на процессоре Apple M1 и использует macOS Big Sur.Сборщик мобильных приложений не поддерживал запуск сборки мобильных приложений для ОС iOS в том случае, если для сборки используется компьютер Mac, который базируется на процессоре Apple M1 и использует macOS Big Sur.Сборщик мобильных приложений стал поддерживать современные компьютеры и операционные системы компании Apple.
Клиентское приложение.
Установка клиентского приложения.
Средства администрирования.
Для ОС Linux реализована возможность обновления дистрибутива без дополнительной настройки файла default.vrd (через каталог distr каталога конкретной версии).

Для ОС Linux и Windows реализованы файлы установочных пакетов, содержащие все клиентские приложения.

Возможность обновления дистрибутива без дополнительной настройки файла default.vrd (через каталог distr каталога конкретной версии) поддерживался только клиентскими приложениями для ОС macOS и Windows.Упрощена настройка распространения дистрибутивов клиентского приложения при обновлении версии системы «1С:Предприятие» на серверах, работающих под управлением ОС Linux.
В документации данное изменение описано здесь.
Веб-клиент.
В веб-клиенте реализованы возможности работы с навигационными ссылками:
  • Обработчик события глобального контекста ОбработкаПереходаПоНавигационнойСсылке.
  • Метод глобального контекста ПолучитьВнешнююНавигационнуюСсылку().
  • Свойство глобального контекста НавигационнаяСсылкаЗапуска. В данное свойство помещается навигационная ссылка, которая привела к запуску клиентского приложения.
Данные возможности были недоступны в веб-клиенте.Возможности веб-клиента по работе с навигационными ссылками приведены в соответствие с остальными клиентскими приложениями.
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
Упрощена процедура загрузки конфигураций в сборщик мобильных приложений. Сборщик автоматически определяет, в какую группу разместить загружаемую конфигурацию.

Реализована возможность просмотра свойств используемой конфигурации непосредственно из карточки собранного мобильного приложения.

Для конфигурации, загруженной в сборщик, реализована возможность получить список приложений, в состав которых входит данная конфигурация.

Для загрузки новой версии мобильной конфигурации было необходимо вручную определить, в какую группу необходимо загружать конфигурацию, что было не очень просто при большом списке используемых конфигураций.

Сборщик мобильных приложений не предоставлял простых способ для получения списка приложений, использующих какую-либо конфигурацию, а также не позволял быстро просмотреть свойства конфигурации в карточке собранного мобильного приложения.

Упрощена работа с мобильными конфигурациями в сборщике мобильных приложений.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
Проверка подписи мобильного клиента на сервере выполняется в соответствии со значением параметра в настройках информационной базы. Параметр в настройках информационной базы называется Проверка подписи мобильного клиента.

Для управления значением параметра реализованы методы глобального контекста ПолучитьСпособПроверкиПодписиМобильногоКлиента()/УстановитьСпособПроверкиПодписиМобильногоКлиента().

Проверка подписи мобильного клиента на сервере выполнялась всегда, вне зависимости от значения параметра в настройках информационной базы. Параметр в настройках информационной базы назывался Проверка подписи мобильного клиента при обновлении конфигурации базы данных.Реализована возможность отключения бесполезной диагностики в том случае, если прикладное решение не используется с мобильным клиентом и не требуется проверка подписи конфигурации для работы с мобильным клиентом.
В документации данное изменение описано здесь и здесь.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Мобильные приложения, собранные с использованием мобильной версии 8.3.18.71, будут удовлетворять требованиям магазина приложений Google в части загрузки новых приложений. Целевая версия SDK установлено в значение 30.

Для того, чтобы загрузить мобильное приложение в магазин Google Play, необходимо собрать мобильное приложение с использованием мобильной версии 8.3.18.71 или последующих.

Мобильные приложения, собранные с использованием мобильных версий, предшествующих версии 8.3.18.71, будет невозможно загрузить в магазин Google Play после 1 августа 2021 года.Мобильная версия системы «1С:Предприятие» удовлетворяет требованиям магазина приложений Google Play.
Мобильная платформа.
Мобильный клиент.
Реализована функциональность мобильной версии Доступ ко всем данным. Если у конфигурации включена данная функциональность, то мобильное приложение для ОС Android, включающее такую конфигурацию, получит разрешение на доступ к произвольному месту (в рамках глобальных ограничений операционной системы) файловой системы мобильного устройства.Доступ к произвольному месту файловой системы устройства под управлением ОС Android, не требовал указания каких-либо разрешений.Улучшено соответствие требований, которые выдвигает компания Google к мобильным приложениям, работающих под управлением ОС Android.
В документации данное изменение описано здесь.
Установка клиентского приложения.
Средства администрирования.
Работа в ОС Linux.
Если сервер системы «1С:Предприятие» обновлен до версии 8.3.20 и последующих, а обновление клиентского приложения настроено через сам сервер (любым способом), то тонкий клиент версии 8.3.18 и 8.3.19, работающий по управлением ОС Linux, сможет выполнить обновление до версии 8.3.20. При этом для обновления могут использоваться не только дистрибутивы в формате .deb и .rpm, но и фомате .run (реализован в версии 8.3.20).Клиентское приложение, работающее под управлением ОС Linux, могло обновляться только с использованием дистрибутивов в формате .deb и .rpm. После обновления на версию 8.3.20, клиентское приложение не могло самостоятельно обновиться до этой версии.Переход на версию 8.3.20 стал таким же простым, как и переход между предыдущими версиями, несмотря на смену формата файла с дистрибутивным комплектом.
Работа в macOS.
Системные требования.
Реализована поддержка ОС macOS Big Sur (версия 11).

Под управлением macOS Big Sur свойство СистемнаяИнформация.Процессор всегда содержит значение x86_64.

Система «1С:Предприятие» не работала под управлением операционной системой macOS Big Sur (версия 11).Расширен список поддерживаемых версий операционной системы macOS.
В документации данное изменение описано здесь и здесь.
Система аналитики.
Для выполнения запросов к данным, система аналитики использует пул сеансов, аналогичный пулу для обработки запросов к HTTP-сервисам.

Реализован новый тип сеанса: Запрос системы аналитики.

Настройка пула выполняется с помощью элемента analytics файла default.vrd. Интерфейс публикации информационной базы конфигуратора не поддерживает редактирование настроек пула.

Для выполнения запросов к данным система аналитики использовала фоновые задания.Ускорено выполнение запросов системы аналитики к данным информационной базы за счет сокращения времени на инициализацию сеанса.
Работа с PDF-документами.
Реализована возможность выполнять преобразование документа PDF в оттенки серого.

Для объекта ЗаписьPDF реализованы методы ПреобразоватьВОттенкиСерого() и ПреобразоватьВОттенкиСерогоАсинх().

Данная возможность не предоставлялась.Расширены возможности работы с документами PDF.
В документации данное изменение описано здесь.
Копии базы данных.
Повышена производительность запросов, выполняемых на копии базы данных.Запросы, выполняемые на копии базы данных, требовали больше времени.Повышена производительность запросов, выполняемых на копии базы данных.
Система компоновки данных.
Внешние источники данных.
Поля внешних источников данных не ссылочного типа, получаемые через точку от другого поля, становятся доступны в источнике доступных настроек компоновки данных, т.е. такие поля можно использовать в настройках компоновки данных.Поля внешних источников данных не ссылочного типа, получаемые через точку от другого поля, были не доступны в источнике доступных настроек компоновки данных, т.е. такие поля нельзя было использовать в настройках компоновки данных.Устранено некорректное поведение системы.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.18 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 11.13 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 12.8 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 13.4 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 14.0 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Система аналитики.
Стандартные функции.
Для стандартной обработки Управление системой аналитики реализованы:
  • Поддержка параметров виртуальных таблицы в запросах к дополнительным источникам.
  • Возможности по работе с дополнительными источниками данных: обновление списка с сервера, сохранение/загрузка списка дополнительных источников в файл/из файла.
Стандартная обработка Управление системой аналитики не поддерживала работу с параметрами виртуальных таблиц в запросах к дополнительным источникам, а для списка дополнительных источников поддерживалась только возможность регистрации дополнительного источника.Возможности стандартной обработки приведены в соответствие с возможностями системы 1С:Аналитика.
Системные требования.
Уточнены минимальные системные требования для компонентов платформы:
  • Устройство чтения компакт-дисков - исключено из списка системных требований.
  • Для установки требуется от 350 Мб до 1 Гб дискового пространства (в зависимости от устанавливаемого приложения).
  • Веб-браузер Chromium-gost - версия 64 и последующие.
  • Веб-браузер Google Chrome - версия 64 и последующие.

В документацию внесена рекомендация по выбору оборудования для выбора оптимальной конфигурации оборудования.

Минимальные системные требования компонентов платформы были следующими:
  • Требовалась поддержка устройства чтения компакт-дисков.
  • Для установки требовалось от 250 Мб до 800 Мб дискового пространства (в зависимости от устанавливаемого приложения).
  • Веб-браузер Chromium-gost - версия 49 и последующие.
  • Веб-браузер Google Chrome - версия 49 и последующие.
Уточнены некоторые системные требования.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 12.9.1,
  • Postgres Pro 1C 13.5.1,
  • Postgres Pro 1C 14.1.1,
  • Postgres Pro Standard 12.9.1,
  • Postgres Pro Standard 13.5.1,
  • Postgres Pro Standard 14.1.1,
  • Postgres Pro Enterprise 12.9.1,
  • Postgres Pro Enterprise 13.5.1,
  • Postgres Pro Enterprise 14.1.1.
Данные версии СУБД не поддерживались.Расширен список поддерживаемых СУБД.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 15.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Реализована поддержка протокола TLS 1.3. При использовании протокола TLS 1.3 не поддерживается использование клиентских сертификатов.

Для конфигурационного файла conf.cfg реализованы параметры ForceTLS1_1 и ForceTLS1_2, позволяющие указать максимальную версию используемого протокола TLS.

Для командной строки запуска клиентского приложения реализованы команды /HttpsForceTLS1_1 и /HttpsForceTLS1_2, позволяющие указать максимальную используемую версию протокла TLS при работе через веб-сервер по протоколу HTTPS.

+

Протокол TLS 1.3 не поддерживался.Повышена защищенность соединения, устанавливаемого клиентским приложением, при работе через Интернет.

Оглавление

Переход с предыдущей версии на версию 8.3.18

Оглавление

Версия 8.3.17

Версия 8.3.17 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8317doc) документации к текущей версии.

Толстый клиент и конфигуратор для работы под управлением ОС macOS вышли из статуса бета-версии.

Для использования Дата акселератора и механизма копии базы данных требуется лицензия уровня КОРП.

Лицензия для проведения тестирования выделенной функциональности более недоступна для Дата акселератора и механизма копии базы данных.

Реализована серверная лицензия для бета-тестирования системы «1С:Аналитика». Данная лицензия позволяет использовать систему «1С:Аналитика», а также механизмы Дата акселератора и копии базы данных.

Реализована лицензия для запуска клиента системы 1С:Аналитика. Количество одновременно запускаемых сеансов клиента 1С:Аналитика определяется номиналом лицензии. Лицензия для запуска клиента системы 1С:Аналитика может быть уровня ПРОФ и КОРП.

Лицензия для запуска клиента системы 1С:Аналитика устанавливается на компьютер с кластером серверов системы «1С:Предприятие» и позволяет:

В документации данное изменение описано здесь.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.16.Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.15. +Возможность запуска конфигураций, разработанных в версии 8.3.16 и более младших, в версии 8.3.17, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.17 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.17, при необходимости, использовать для работы с информационной базой и версию 8.3.16. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Отображение информации.
В библиотеку картинок добавлены картинки
  • ИзменитьМасштаб.
  • Параметры.
  • Информация.
  • КомандаМенюФункций.
  • Избранное.
  • Настройка.
  • Сообщение.
  • ГрупповоеОбсуждение.
  • ПользовательСистемыВзаимодействия.
  • ПоискДанных.
  • ПерейтиПоВнешнейНавигационнойСсылке.
  • Календарь. В режиме совместимости с версией 8.3.16 используется картинка КалендарьПоляВвода.
  • Калькулятор.В режиме совместимости с версией 8.3.16 используется картинка КалькуляторПоляВвода.
  • Справка.В режиме совместимости с версией 8.3.16 используется картинка СправкаФормы.
  • ПользовательИнтеграцииСистемыВзаимодействия,
  • ОткрытьСОсновногоСервера,
  • ОткрытьСАвтономногоСервера.

Перерисована картинка Обсуждения. +

В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.
Обработка ошибок.
Реализованы следующие возможности, связанные с обработкой ошибок, возникающих при работе прикладного решения:
  • Возможность обработки всех не перехваченных ошибок, возникающих при работе прикладного решения, перед отображением ошибок пользователю. Реализован обработчик модуля приложения ОбработкаОтображенияОшибки.
  • Реализована возможность декларативной настройки текстов сообщений об ошибке.
  • Реализована возможность формирования и отправки отчета об ошибке для службы технической поддержки (в том числе полностью автоматически). Реализован объект ОтчетОбОшибке.
  • Реализовано понятие «категория ошибки», что позволяет группировать ошибки. Реализован метод ИнформацияОбОшибке.ЯвляетсяОшибкойКатегории().
  • Изменено стандартное окно отображения ошибок пользователю.

Реализовано свойство глобального контекста ОбработкаОшибок.

Реализована стандартная функция Управление настройками обработки ошибок, позволяющая настроить тексты ошибок. +Методы глобального контекста КраткоеПредставлениеОшибки(), ПодробноеПредставлениеОшибки() и ПоказатьИнформациюОбОшибке() считаются устаревшими. Рекомендуется использовать одноименные методы объекта ОбработкаОшибок.

При работе под управлением ОС Linux для получения стека приложения в момент возникновения ошибки используется библиотека libunwind.

Данные возможности не предоставлялась.

Имелась возможность только локальной обработки восстановимых ошибок.

Стало возможно сделать тексты ошибок более понятными конечному пользователю.

Улучшена обработка ошибок во встроенном языке.

В документации данное изменение описано здесь, здесь и здесь.
Кластер серверов.
Клиентское приложение.
При работе в клиент-серверном варианте, реализована возможность автоматического удаления временных файлов, созданных с применением метода ПолучитьИмяВременногоФайла() на стороне компьютера (-ов), на котором (-ых) работает кластер серверов, в следующих случаях:
  • Через 20 минут после окончания сеанса, в котором создан временный файл.
  • Через 20 минут после окончания серверного вызова, в котором создан временный файл. Не поддерживается в режиме совместимости с версией 8.3.16 и предыдущих.

Удаление временных файлов при старте процессов системы «1С:Предприятие» (клиентские приложения, процессы кластера серверов) выполняется параллельно запуску процесса, без замедления запуска. +

Временные файлы удалялись только при запуске процессов системы «1С:Предприятие». Скорость запуска системы зависела от количества удаляемых временных файлов.Ускорен запуск процессов системы «1С:Предприятие» при наличии большого количества временных файлов, порожденных самой системой.

Снижена вероятность исчерпания места на дисках, на которых расположены каталоги временных файлов, при длительной работе системы без перезапуска и неаккуратном обращении прикладного решения с создаваемыми временными файлами.

Уменьшено количество одновременно существующих временных файлов с именами, которые получены с помощью метода ПолучитьИмяВременногоФайла().

Система взаимодействия.
Для системы взаимодействия реализована возможность интеграции с внешними (по отношению к системе взаимодействия) системами обмена мгновенными сообщениями. Реализовано взаимодействие со следующими системами: Telegram, ВКонтакте.

Реализован объект ИнтеграцияСистемыВзаимодействия. Для объекта МенеджерСистемыВзаимодействия реализованы методы СоздатьИнтеграцию(), ПолучитьИнтеграцию(), ПолучитьИнтеграции(), ПолучитьТипыВнешнихСистем(), ПолучитьОписаниеВнешнейСистемы().

Реализованы свойства ПользовательСистемыВзаимодействия.ТипВнешнейСистемы, ПользовательСистемыВзаимодействия.ИдентификаторПользователяВнешнейСистемы, ОбсуждениеСистемыВзаимодействия.Интеграция, ОтборОбсужденийСистемыВзаимодействия.Интеграция.

Данная возможность не предоставлялась.Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь, здесь и здесь.
Расширение конфигурации.
Реализована возможность заимствования подписок на события и создания собственных подписок в расширении.Данная возможность не предоставлялась.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Отображение информации.
Системные требования.
Реализована возможность сохранения табличного документа в формате Microisoft Excel 97 в клиентском приложении, работающем под управлением ОС macOS. При работе под управлением ОС Linux, для сохранения в формате Microsoft Excel 97 используется библиотека libgsf-v8, которая входит в состав дистрибутива платформы, и более не требуются библиотеки libgsf-1 и libglib-2.0.

Сохранение табличного документа в формат Microsoft Excel 95 при работе под управлением ОС Linux и macOS не поддерживается.

Сохранение табличного в формате Microsoft Excel 97 поддерживалось только под управлением ОС Linux.

Сохранение табличного документа в формат Microsoft Excel 95 при работе под управлением ОС Linux и macOS формально поддерживалось, но фактически не могло быть выполнено.

Пользователям клиентских приложений, работающих под управлением ОС macOS, стала доступна возможность сохранения табличных документов в формате Microsoft Excel 97.
В документации данное изменение описано здесь.
Средства разработки.
Для управляемого клиентского приложения реализован режим технического специалиста. В этом режиме для управляемых форм реализованы следующие возможности:
  • Возможность получения полного имени формы, отображающейся в данном окне с помощью команды Информация для технического специалиста контекстного меню заголовка формы и меню формы.
  • Возможность открыть в конфигураторе текущий объект конфигурации с помощью команды Открыть в Конфигураторе контекстного меню заголовка формы и меню формы. Данная возможность доступна только в том случае, если клиентское приложение открыто в режиме отладки.

+

Данная возможность не предоставлялась.

Было затруднительно определить, какая форма в данный момент используется в клиентском приложении.

Упрощена работа технического специалиста во время разработки или внедрения прикладного решения.
В документации данное изменение описано здесь.
Общие объекты.
Реализована возможность определения IP-адреса компьютера, который начал сеанс работы с информационной базой. IP-адрес может быть определен не всегда и не для всех режимов работы.

Реализовано свойство IPАдресКлиента для объектов АдминистрированиеСеанс и СеансИнформационнойБазы.

Реализована возможность отображения IP-адреса клиентского приложения в консоли управления кластером и стандартной обработке управления серверами.

В интерфейсе работы с сервером администрирования из языка Java реализовано свойство ISessionInfo.getClientIPAddress().

Для утилиты командной строки (rac) кластера серверов реализовано поле client-ip для результата работы команды session info.

Для метода onStartSession() Web-сервиса внешнего управления сеансами реализованы параметры SessionNumber и ClientIPAddress. Новые возможности доступны только в том случае, если параметр wsver имеет значение 3.

Данная возможность не предоставлялась.Реализована возможность определения IP-адреса компьютера, который начал сеанс работы с информационной базой.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Система аналитики.
Реализована интеграция системы программ «1С:Предприятие» с системой «1С:Аналитика» (система аналитики).

В настройках публикации на веб-сервере реализована возможность включить публикацию системы аналитики.

В меню Сервис и настройки реализована команда Система аналитики, позволяющая открыть в веб-браузере вкладку с системой аналитики для текущего пользователя.

Реализована стандартная функция Управление системой аналитики для интеграции системы аналитики и информационной базы.

Для глобального контекста реализовано свойство СистемаАналитики. Реализовано право доступа КлиентСистемыАналитики.

Система «1С:Аналитика» не входит в комплект поставки. Информация по данной функциональности публикуется отдельно.

Данная возможность не предоставлялась.Реализована интеграция системы программ «1С:Предприятие» с системой «1С:Аналитика» (система аналитики).
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Система компоновки данных.
Реализована возможность передачи в механизм системы компоновки данных менеджера временных таблиц. В механизмах компоновки данных разрешается использовать таблицы, которые не существуют в информационной базе, по аналогии с тем, как используются временные таблицы в языке запросов.

Для метода ПроцессорКомпоновкиДанных.Инициализировать() реализован параметр МенеджерВременныхТаблиц.

Данная возможность не предоставлялась. Временные таблицы в системе компоновки данных можно было использовать только в рамках пакетного запроса.Стало возможно использовать заранее подготовленные временные таблицы при выполнении запросов процессором компоновки данных.
Табличный документ.
Диаграммы.
Реализована возможность управлять отображением рамки выделения рисунков в табличном документе, который размещен в форме клиентского приложения.

Для расширения поля формы для поля табличного документа реализовано свойство РежимОтображенияВыделенияРисунков.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

Данная возможность не предоставлялась.

При выборе диаграммы в табличном документе, размещенном в форме клиентского приложения, диаграмма всегда выделялась.

Использовать диаграммы в табличном документе, расположенном в форме, стало более удобно.
Отображение информации.
Форма клиентского приложения.
В планировщике реализована возможность создания вложенных элементов измерений, а также возможность отображать текст в интервалах фона.

Для объекта ЭлементИзмеренияПланировщика реализованы свойства Элементы, Родитель, ОтображатьОбластьЭлементовТолькоДляПодчиненных.

Для метода КоллекцияЭлементовИзмеренияПланировщика.Найти() реализован параметр ВключатьПодчиненные.

Для расширения поля формы для поля планировщика реализованы:

  • Методы: СвернутьЭлементИзмерения(), РазвернутьЭлементИзмерения(), РазвернутЭлементИзмерения().
  • События: ПередРазворачиваниемЭлементаИзмерения, ПередСворачиваниемЭлементаИзмерения.

Для методов Добавить() и Вставить() объектов КоллекцияИзмеренийПланировщика и КоллекцияЭлементовИзмеренияПланировщика реализован параметр Текст. При использовании рекомендуется указывать значение данного параметра для исключения вызовов сервера с целью получения представлений.

Данные возможности не предоставлялись.Стало возможно реализовать группировку элементов измерений планировщика, аналогично группировке строк табличного документа или иерархического справочника.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Oracle Database следующих версии:
  • 12.2.
  • 18с.
  • 19с.
Данные версии СУБД Oracle Database не поддерживались.Расширен список поддерживаемых версий СУБД Oracle Database.
В документации данное изменение описано здесь, здесь и здесь.
Сервис интеграции.
Реализована возможность создания сервисов интеграции. Сервисы интеграции позволяют взаимодействовать с продуктом «Внешний сервис интеграции».

Реализовано свойство встроенного языка СервисыИнтеграции.

В стандартных функциях реализована возможность управления сервисами интеграции.

«Внешний сервис интеграции» не входит в комплект поставки. Информация по данной функциональности публикуется отдельно.

Для использования сервисов интеграции требуется лицензия на тестирование выделенной функциональности. При отсутствии лицензии на тестирование выделенной функицональности использование сервисов интеграции будет невозможно.

Данная возможность не предоставлялась.Реализована возможность взаимодействовать с продуктом «Внешний сервис интеграции».
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Веб-клиент.
Для веб-клиента реализована поддержка языков с написанием справа-налево. Данный режим поддерживается во всем интерфейсе клиентского приложения автоматически, за исключением следующих элементов формы: планировщик, диаграмма, диаграмма Ганта, дендрограмма, поле графической схемы и поле географической схемы. Необходимость изменения интерфейса определяется по языку интерфейса или языку конфигурации. В веб-клиенте реализована поддержка арабских форматов чисел и дат.

При расчете расстановки элементов формы и других элементов интерфейса по умолчанию используется шрифт Almarai.

Веб-клиент поддерживает использование специализированных арабских символов для записи арифметических выражений. В таких случаях вычисление выражений происходит корректно.

Веб-клиент не поддерживал использование языков с написанием справа-налево.Стало возможно использовать систему «1С:Предприятие» (с помощью веб-клиента) в странах, где национальный язык использует написание справа-налево.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Работа с файлами.
При открытии файла внешнего отчета или обработки в веб-клиенте (без установленного расширения работы с файлами), пользователю больше не предлагается повторно открыть выбранный файл после утвердительного ответа на предупреждение безопасности.

В диалоге открытия файлов веб-клиента стало возможно выбирать фильтр для отбора открываемых файлов (если он задан при открытии диалога).

При открытии файла внешнего отчета или обработки в веб-клиенте (без установленного расширения работы с файлами), пользователю предлагалось повторно открыть выбранный файл после утвердительного ответа на предупреждение безопасности.

В диалоге открытия файлов веб-клиента было невозможно указать фильтр для отбора файлов.

Открытие внешнего отчета или обработки на веб-клиенте (без установленного расширения работы с файлами) стало более простым и понятным.

Открытие прочих файлов в веб-клиенте стало более удобным.

Отображение информации.
Для части картинок платформы (включая часть библиотеки картинок) изменен внешний вид картинок (картинки перерисованы) и картинки реализованы в формате SVG.

Для интерфейса Такси несколько изменен внешний вид окон, которые формируются методами глобального контекста ПоказатьОповещениеПользователя() и Состояние().

Часть картинок платформы (включая часть библиотеки картинок) имела другой внешний вид, а картинки были реализованы в формате PNG.

Внешний вид окон, которые формируются в интерфейсе Такси, методами глобального контекста ПоказатьОповещениеПользователя() и Состояние(), был другим.

Улучшено визуальное восприятие интерфейса системы «1С:Предприятие».
Обработка ошибок.
При открытии диалога с информацией для специалиста технической поддержки, автоматически выделяется весь текст, расположенный в поле ввода.При открытии диалога с информацией для специалиста технической поддержки, текст, расположенный в поле ввода, не выделялся.Стало проще и быстрее скопировать информацию для технической поддержки, если это требуется.
Глобальный поиск.
Клиентское приложение.
Веб-клиент.
Реализованы команды глобального поиска:
  • справка - для открытия справки клиентского приложения по текущему контексту.
  • содержание справки - для открытия содержания справки клиентского приложения.

Команда контекстного меню Искать везде доступна в том случае, если курсор находится внутри какого-либо слова или есть выделенный фрагмент текста. Если нет выделения и курсор находится внутри слова, то поиск будет выполнен по этому слову или навигационной ссылке (если курсор находится внутри навигационной ссылки).

В представлении команды Искать везде в меню добавляется фрагмент текста, который будет искаться при вызове команды.

При работе в веб-клиенте с использованием веб-браузера Safari, нажатие правой кнопки мыши в поле ввода, форматированном и текстовом документах, приводит к выделению всего слова, в котором находится курсор (без анализа этого слова).

При работе в тонком клиенте, толстом клиенте и веб-клиенте (кроме веб-браузеров Mozilla Firefox и Safari) нажатие правой кнопки мыши в поле ввода приводит к установке курсора в позицию, где выполнено нажатие.

Команда контекстного меню Искать везде была доступна в том случае, если в текущем элементе формы был выделенный фрагмент текста. Поиск выполнялся по выделенному фрагменту.

В представлении команды Искать везде в меню не добавлялся искомый фрагмент текста.

Улучшено использование глобального поиска.
В документации данное изменение описано здесь.
Веб-клиент.
Табличный документ.
При работе в веб-клиенте, при условии медленного соединения, оптимизировано отображение табличного документа, содержащего узоры в ячейках. При сохранении табличного документа, содержащего узоры в ячейках, в формате HTML уменьшен размер получающегося HTML-документа.При работе в веб-клиенте, при условии медленного соединения, отображение табличного документа, содержащего узоры в ячейках, занимало больше времени.Устранено некорректное поведение системы.
Полнотекстовый поиск.
Стандартные функции.
Для стандартной функции управления полнотекстовым поиском реализована возможность выполнить проверку текущего индекса полнотекстового поиска на корректность.

Перед очисткой текущего индекса полнотекстового поиска выдается предупреждение с возможностью отказаться от очистки.

Для стандартной функции управления полнотекстовым поиском не предоставлялась возможность выполнить проверку текущего индекса полнотекстового поиска на корректность.

Очистка текущего индекса полнотекстового поиска выполнялась без предупреждений, безусловно.

Расширен набор возможностей стандартной функции управления полнотекстового поиска.

Стало сложнее случайно выполнить очистку индекса полнотекстового поиска.

В документации данное изменение описано здесь.
Веб-клиент.
Упрощен процесс установки расширения веб-браузера (для веб-браузеров Google Chrome и Mozilla Firefox), которое необходимо для работы расширений работы с файлами, криптографией и внешних компонент. После установки расширения для веб-браузера Google Chrome больше не требуется перезапускать веб-клиент.Процесс установки расширения веб-браузера (для веб-браузеров Google Chrome и Mozilla Firefox), которое необходимо для работы расширений работы с файлами, криптографией и внешних компонент, был более запутанным. После установки расширения для веб-браузера Google Chrome требовалось перезапустить веб-клиент.Процесс установки расширений веб-браузера стал проще и удобнее.
Система взаимодействия.
В интерфейс системы взаимодействия внесены следующие изменения:
  • Реализована возможность изменения размера поля ввода сообщения в контекстном обсуждении.
  • Реализовано отображение аватаров пользователей в диалоге создания обсуждения и добавления участников в не контекстные обсуждения.
  • Реализована возможность удаления любого участника не контекстного обсуждения любым участником.
  • Реализована возможность задать получателей сообщения для не контекстного обсуждения.
  • Список для подбора получателей в не контекстном обсуждении формируется аналогично контекстному обсуждению (включая вызов всех обработчиков). В список подбора пользователей не добавляется пункт Никого не оповещать.
  • В сообщениях, адресованных нескольким получателям, реализованы кнопки Ответить и Ответить всем (отображаются картинками).
  • Реализована возможность ответить на свое собственное сообщение. В этом случае в список оповещаемых попадут те же пользователи, что и в оригинальном сообщении.
  • Если в сообщении не контекстного сообщения текущий пользователь отсутствует в списке получателей, то пользователь не информируется о получении такого сообщения.
  • В создаваемых сообщениях реализована возможность просмотра вложений.
Интерфейс системы взаимодействия был другим.Пользоваться системой взаимодействия стало более удобно.
В документации данное изменение описано здесь.
Стандартные функции.
В диалоге настройки параметров полнотекстового поиска стандартной обработки управления полнотекстовым поиском, кнопка принятия изменений доступна всегда, а не только после изменения параметров. Сама кнопка называется ОК.В диалоге настройки параметров полнотекстового поиска стандартной обработки управления полнотекстовым поиском, кнопка принятия изменений была доступна только после изменения какого-либо параметра. Сама кнопка называлась Установить.Интерфейс диалога установки параметров приведен к стандартному виду, принятому в платформе.
В документации данное изменение описано здесь.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Форма клиентского приложения.
Оптимизировано удаление строк из таблицы, отображаемой на форме клиентского приложения.Удаление строк из таблицы, расположенной на форме клиентского приложение, занимало больше времени.Ускорена работа клиентского приложения при удалении строк из таблицы формы.
Журнал регистрации.
Реализовано индексирование файлов журнала регистрации. Индексация выполняется в фоновом режиме. Индексы хранятся в файлах с расширением .lgx в каталоге 1Cv8Log. Оптимизированы алгоритмы последовательного чтения файлов журнала регистрации.

Никаких дополнительных настроек для включения индексации не требуется. За счет индексации существенно ускорен отбор записей журнала регистрации по индексируемым полям.

При открытии в конфигураторе файла журнала регистрации другой информационной базы, индексирование данного файла выполняется в фоновом режиме и индексный файл стирается после завершения работы с просматриваемого журнала регистрации.

Для новой информационной базы значение параметра Разделять хранение журнала по периодам устанавливается в значение Неделя. Для существующих информационных баз рекомендуется установить разделение таким образом, чтобы размер одного файла журнала не превышал 100 Мбайт.

Прекращена поддержка журналов регистрации, сформированных в системе «1С:Предприятие» версий 8.0 и 8.1.

Данная возможность не предоставлялась.

Индексирование файлов журнала регистрации не велось. Отбор записей в журнале регистрации занимал очень продолжительное время в больших файлах журнала.

Ускорена работа с журналом регистрации.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Права доступа.
Кластер серверов.
При работе в клиент-серверном варианте ускорен запуск первого сеанса для доступа к информационной базе, конфигурация которой содержит большое количество ролей.При работе в клиент-серверном варианте запуск первого сеанса для доступа к информационной базе, конфигурация которой содержит большое количество ролей, занимал больше времени.Снизилось время недоступности кластера серверов для пользователей при перезапуске рабочих процессов, а также сократилось время старта первого сеанса для каждой информационной базы в каждом рабочем процессе.
Кластер серверов.
При работе в клиент-серверном варианте ускорен запуск первого сеанса для доступа к информационной базе. Ускорение особенно заметно для конфигураций, содержащих большой объем метаданных.При работе в клиент-серверном варианте запуск первого сеанса для доступа к информационной базе требовал больше времени.Снизилось время недоступности кластера серверов для пользователей при перезапуске рабочих процессов, а также сократилось время старта первого сеанса для каждой информационной базы в каждом рабочем процессе.
Общие объекты.
Реализована возможность ускорить решение некоторых систем линейных алгебраических уравнений.

Для метода РасчетСистемЛинейныхУравнений.РассчитатьСистемыЛинейныхУравнений() реализован параметр РазрешитьРедуцированиеГрафа, позволяющий управлять алгоритмом расчета. Реализован метод РасчетСистемЛинейныхУравнений.ПолучитьГлубинуГрафа(), позволяющий принять решение о значении параметра РазрешитьРедуцированиеГрафа.

Для некоторых систем линейных алгебраических уравнений система «1С:Предприятие» показывала недостаточную скорость поиска решений.Реализована более тонкая настройка поведения механизма решения системы линейных алгебраических уравнений.
Работа с запросами.
Оптимизировано сравнение составных типов с не составными, если не составной тип может принимать значение NULL и в запросе используются временные таблицы.

Оптимизированы следующие операции:

  • Сравнение вида A = B, где A – составной тип, а B – простой тип и может принимать значение NULL.
  • Сравнение вида ЕСТЬNULL(A, B) = C, где A – простой тип и может принимать значение NULL, а C – составной тип.
  • Сравнение вида Выражение1 В (ВЫБРАТЬ ….) и сравнение вида Выражение1 В (Список значений), где Выражение1 – поле ссылочного типа на несколько таблиц. При этом в списке выборки подзапроса или в списке значений должны находиться ссылки на разные таблицы и отсутствовать значение Неопределено.

Оптимизация применяется только в тех случаях, когда это не влияет на результат запроса. Оптимизация может привести к улучшению плана запроса и уменьшению времени компиляции запроса.

Сравнение составных типов с не составными, если не составной тип может принимать значение NULL и в запросе используются временные таблицы, приводило к формированию сложных запросов, которые могли приводить к ошибкам времени исполнения и неоптимальным планам запросов.В некоторых случаях ускорено выполнение запросов.
Работа с запросами.
Работа с СУБД.
Кластер серверов.
Если в запросе используется сравнение с пустой ссылкой, переданной в качестве параметра, то в СУБД передается запрос, в котором параметр заменен на константу. Оптимизация применяется в том случае, если кластер серверов использует СУБД IBM DB2, Microsoft SQL Server или Oracle Database.Если в запросе используется сравнение с пустой ссылкой, переданной в качестве параметра, то замены параметра на константу не выполнялось. СУБД может выбрать более оптимальный план выполнения запроса, если в запросе используется сравнение с пустыми ссылками, которые передаются в запрос в качестве параметров.
Работа с СУБД.
При работе в файловом варианте информационной базы оптимизирована (в большинстве случаев) работа запроса, который содержит несколько условий В, использующих индекс.

Тем не менее, в некоторых случаях возможно незначительное замедление выполнения таких запросов.

При работе в файловом варианте информационной базы работа запроса, который содержит несколько условий В, использующих индекс была неоптимальной.Ускорено выполнение некоторых запросов в файловом варианте информационной базы.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Система компоновки данных.
При чтении настроек отчетов, динамических списков и условного оформления форм, отсутствующие элементы стиля не вызывают ошибку, а заменяются значениями по умолчанию соответствующего типа.При чтении настроек отчетов, динамических списков и условного оформления форм, отсутствующие элементы стиля вызывали ошибку и делали невозможным применение таких настроек.Если в каких-либо настройках отчета, динамического списка, условного оформления формы в качестве значения параметра оформления используется элемент стиля, то в случае невозможности его прочитать, в результате удаления/переименования или применении настроек на предыдущей версии платформы, весь объект настроек не будет потерян и остальные настройки будут применены. Параметры оформления, содержащие некорректные значения также будут применены, но с использованием значений по умолчанию.
В документации данное изменение описано здесь.
Веб-клиент.
Повышена надежность работы веб-клиента.Надежность работы веб-клиента была более низкой.Повышена надежность работы веб-клиента.
Средства разработки.
Если во время отладки установлена возможность остановки по ошибке, то текст ошибки выводится не только в диалог, но и в окно сообщений. При этом предоставляется возможность перехода к месту исключения из окна сообщений.Данная возможность не предоставлялась.

Сообщение об ошибке выводилось только в диалог с описанием ошибки.

Упрощено использование отладчика при включенном останове при возникновении ошибки.
В документации данное изменение описано здесь.
Средства разработки.
При формировании отчета по версиям хранилища конфигурации реализована возможность управлять:
  • Интервалом дат, за который получается отчет.
  • Включением или исключением из отчета версий с установленными метками.
  • Включить вывод в отчет комментарии, начинающиеся с символов комментария (//).
  • Указывать, для какой версии конфигурации выводить изменения в хранилище.
  • Управлять форматом отчета по хранилищу.

Для команды пакетного запуска конфигуратора ConfigurationRepositoryReport реализованы параметры DateBegin, DateEnd, DoNotIncludeVersionsWithLabel, IncludeOnlyVersionsWithLabel, IncludeCommentLineWithDoubleSlash, ConfigurationVersion, ReportFormat.

Данные возможности не предоставлялись.Расширены возможности работы с отчетом по хранилищу с помощью пакетного режима запуска конфигуратора.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Работа в ОС Linux.
После установки приложения 1С:Предприятие - оповещения и запуск (в ОС Linux) на рабочем столе создается ярлык для запуска этого приложения. Ярлык относится к подкатегории Finance категории Office.При работе под управлением ОС Linux, запустить приложение 1С:Предприятие - оповещения и запуск можно было только из каталога ~/bin/1cecla.Пользователям ОС Linux стало проще найти и запустить приложение 1С:Предприятие - оповещения и запуск.
Веб-клиент.
Работа с файлами.
Если при использовании в веб-клиенте (без установленного расширения работы с файлами) методов НачатьПомещениеФайлаНаСервер() и НачатьПомещениеФайловНаСервер() используется параметр типа ПараметрыДиалогаПомещенияФайлов, то в диалоге открытия файлов стало возможно выбирать один из фильтров, заданных при создании объекта ПараметрыДиалогаПомещенияФайлов.

При создании объекта ПараметрыДиалогаПомещенияФайлов появилась возможность указания фильтра по умолчанию, который будет использован при открытии диалога выбора файлов.

Если при использовании в веб-клиенте (без установленного расширения работы с файлами) методов НачатьПомещениеФайлаНаСервер() и НачатьПомещениеФайловНаСервер() используется параметр типа ПараметрыДиалогаПомещенияФайлов, то в диалоге открытия файлов было невозможно выбирать фильтр.Если в веб-клиенте не установлено расширение работы с файлами, то выбор файлов для обработки прикладным решением стал более удобным.
В документации данное изменение описано здесь.
Работа с криптографией.
Значение свойств, начинающихся с префикса OID, которые получаются из свойств Субъект и Издатель объекта СертификатКриптографии имеют максимальную длину, равную 2 048 байт.Значение свойств, начинающихся с префикса OID, которые получаются из свойств Субъект и Издатель объекта СертификатКриптографии имели максимальную длину, равную 128 байтам.Устранено некорректное поведение системы.
Глобальный поиск.
Не поддерживается создание объекта ЭлементРезультатаГлобальногоПоиска на основании следующих стандартных видов глобального поиска: ГлобальныеСтандартныеКоманды и ФункцииДляТехническогоСпециалиста.Допускалось создание объекта ЭлементРезультатаГлобальногоПоиска на основании стандартных видов глобального поиска: ГлобальныеСтандартныеКоманды и ФункцииДляТехническогоСпециалиста, что могло привести к некорректному результату обработки результатов глобального поиска.Устранено незапланированное поведение системы.
Динамический список.
Если форма настроек динамического списка содержит измененные настройки, то при попытке закрыть эту форму, пользователю будет выдано предупреждение о измененных настройках и будет предложено сохранить измененные настройки.

Для расширения формы клиентского приложения для компоновщика настроек реализованы свойства ПользовательскиеНастройкиМодифицированы и НастройкиМодифицированы. Стандартная обработка формы компоновщика настроек выполняет анализ признака модифицированности настроек и предлагает выполнить сохранение настроек при необходимости.

Если форма настроек динамического списка содержит измененные настройки, то при попытке закрыть эту форму - форма закрывалась без каких-либо предупреждений.Снижена вероятность потери результатов работы по изменению настроек динамического списка.
Работа с XML, XDTO.
При экспорте пакета XDTO в схему XML, для свойств с вариантом представления «Элемент», выполняется экспорт значения по умолчанию (или фиксированного значения) также, как это делается для свойств с вариантом представления «Атрибут».

В режиме совместимости с версией 8.3.16 поведение не изменилось.

При экспорте пакета XDTO в схему XML, для свойств с вариантом представления «Элемент», не выполнялся экспорт значения по умолчанию (или фиксированного значения).Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
При экспорте табличного документа в форматы XLS (Microsoft Excel 95-2003), Microsoft Office OpenXML (Microsoft Excel 2007 и последующих, Microsoft Word 2007 и последующих), ODS (OpenDocument Spreadsheet) улучшено формирование ячеек, которые содержат символы табуляции или текст в которых начинается с пробельного символа.При экспорте табличного документа в форматы XLS (Microsoft Excel 95-2003), Microsoft Office OpenXML (Microsoft Excel 2007 и последующих, Microsoft Word 2007 и последующих), ODS (OpenDocument Spreadsheet) ячейки, которые содержат символы табуляции или текст в которых начинается с пробельного символа, формировались таким образом, что результирующий документ имел визуальные отличия от оригинала.Уменьшены визуальные отличия между оригинальным табличным документом системы программ «1С:Предприятие» и документом, который получается в результате экспорта табличного документа в форматы XLS (Microsoft Excel 95-2003), Microsoft Office OpenXML (Microsoft Excel 2007 и последующих, Microsoft Word 2007 и последующих), ODS (OpenDocument Spreadsheet).
Работа с запросами.
Если временная таблица формируется на основании таблицы значений, то будет выдана ошибка времен исполнения, если в таблице значений присутствует колонка с неустановленным типом и эта колонка попадает во временную таблицу. Ошибка возникнет также и в том случае, если не типизированная колонка будет участвовать в каком-либо выражении (например ВЫБОР или ЕСТЬNULL).

В режиме совместимости с версией 8.3.16 поведение не изменилось.

Если временная таблица формируется на основании таблицы значений в которой присутствует колонка с неустановленным типом и эта колонка попадает во временную таблицу, то ошибки времени исполнения не формировалось, но результат запроса мог оказать некорректным.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Веб-клиент.
Трансляция экрана в системе взаимодействия, работающей в веб-клиенте:
  • В веб-браузере Google Chrome:
    • Работает, начиная с версии Google Chrome 72.
    • Позволяет демонстрировать весь экран, окно произвольного приложения и любую вкладку веб-браузера.
    • Для работы трансляции экрана не требуется установка расширения веб-браузера.
  • В веб-браузере Mozilla Firefox:
    • Позволяет демонстрировать весь экран, окно произвольного приложения.
Трансляция экрана в системе взаимодействия, работающей в веб-клиенте:
  • В веб-браузере Google Chrome:
    • Работала, начиная с версии Google Chrome 56.
    • Позволяла демонстрировать весь экран и любую вкладку веб-браузера.
    • Для работы трансляции экрана требовалась установка расширения веб-браузера.
  • В веб-браузере Mozilla Firefox:
    • Позволяла демонстрировать весь экран.
Улучшен инструмент трансляции экрана при работе системы взаимодействия в веб-клиенте.
Средства администрирования.
В режиме совместимости Версия 8.3.10 и последующих, функция ПолучитьСтруктуруХраненияБазыДанных() возвращает таблицу значений, в которой колонка Индексы содержит короткие названия индексов. При этом имена индексов отображаются одинаково для любых СУБД.В колонке Индексы таблицы значений, возвращаемой методом ПолучитьСтруктуруХраненияБазыДанных() указывались длинные названия индексов, а имена индексов различались в разных СУБД.Уточнены названия индексов в схеме базы данных.
Расширение конфигурации.
Подсказки к флажку, который управляет поведением свойства объекта в расширении, стали более понятными и стали лучше описывать суть состояния флажка.Подсказки к флажку, который управляет поведением свойства объекта в расширении, плохо описывали суть состояния флажка.Улучшены подсказки флажка, описывающего поведение свойства объекта в расширении.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Форма клиентского приложения.
Если таблица не отображается на форме или в таблице отсутствуют строки или в метод объекта ТаблицаФормы передана строка, отсутствующая в таблице, то:
  • Результатом работы методов ТаблицаФормы.ДанныеСтроки(), ТаблицаФормы.ПроверитьСтроку(), ТаблицаФормы.Развернут() является значение Неопределено.
  • При вызове методов ТаблицаФормы.Развернуть() и ТаблицаФормы.Свернуть() генерируется исключение.

Если таблица не отображается на форме или в таблице отсутствуют строки, то при вызове методов ТаблицаФормы.ИзменитьСтроку() и ТаблицаФормы.СкопироватьСтроку() будет генерироваться исключение.

Если таблица не отображается на форме, то при вызове методов ТаблицаФормы.ДобавитьСтроку(), ТаблицаФормы.ЗакончитьРедактированиеСтроки() и ТаблицаФормы.Обновить() будет генерироваться исключение.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

В тонком и толстом клиентских приложениях:
  • Если таблица не отображается на форме, то:
    • Методы ТаблицаФормы.ДанныеСтроки(), ТаблицаФормы.ПроверитьСтроку() и ТаблицаФормы.Развернут() возвращают Неопределено.
    • Остальные методы объекта ТаблицаФормы будут исполнены, но никакого результата не будет.
  • Если в таблице нет строк или передана строка, отсутствующая в таблице, то:
    • Функция ТаблицаФормы.ДанныеСтроки() возвращает Неопределено.
    • Методы ТаблицаФормы.ПроверитьСтроку(), ТаблицаФормы.Развернут(), ТаблицаФормы.Развернуть() и ТаблицаФормы.Свернуть() генерируют исключение.
    • Если в таблице нет строк, то вызов методов ТаблицаФормы.ИзменитьСтроку(), ТаблицаФормы.СкопироватьСтроку() генерируют исключение.

Веб-клиент:

  • Если таблица не отображается на форме, то:
    • Вызов функции ТаблицаФормы.ДанныеСтроки() возвращает NULL.
    • Вызов функции ТаблицаФормы.Развернут() возвращает Неопределено.
    • Вызов функции ТаблицаФормы.ПроверитьСтроку() возвращает Ложь.
    • Остальные методы объекта ТаблицаФормы будут исполнены, но никакого результата не будет.
  • Если в таблице нет строк или передана строка, отсутствующая в таблице, то:
    • Вызов функции ТаблицаФормы.ДанныеСтроки() возвращает Неопределено.
    • Вызов функций ТаблицаФормы.ПроверитьСтроку() и ТаблицаФормы.Развернут() возвращает Ложь.
    • Остальные методы объекта ТаблицаФормы будут исполнены, но никакого результата не будет.
  • Если в таблице нет строк, то вызов методов ТаблицаФормы.ИзменитьСтроку() и ТаблицаФормы.СкопироватьСтроку() – вызов игнорируется.
Система стала работать одинаково в тонком и веб-клиентах. Устранено некорректное поведение системы.
Клиентское приложение.
Для описания провайдера OpenID Connect в файле default.vrd реализована возможность указать, по каким полям будет выполняться сопоставление пользователя информационной базы системы «1С:Предприятие» и провайдера OpenID Connect.Данная возможность не предоставлялась.

Сопоставление пользователей всегда выполнялось по адресу электронной почты и имени пользователя информационной базы.

Стало возможно использование механизма OpenID Connect с большим количеством провайдеров, например, с Microsoft Azure.
В документации данное изменение описано здесь, здесь и здесь.
Система компоновки данных.
Если выражение системы компоновки данных языка запросов содержит фигурные скобки, то при разборе запроса эти символы не будут удалены.

Если в языке запросов выражение системы компоновки данных не завершается символом «}» до конца запроса, то будет выдана ошибка.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

Если выражение системы компоновки данных языка запросов содержит фигурные скобки, то при разборе запроса эти символы удалялись из текста запроса.

Если в языке запросов выражение системы компоновки данных не завершается символом «}» до конца запроса, то ошибка не формировалась.

Устранено некорректное поведение системы.
Работа с СУБД.
Работа с запросами.
При использовании файлового или клиент-серверного варианта (при использовании СУБД Microsoft SQL Server) оператор языка запросов В, который отвечает всем следующим критериям, всегда возвращает значение типа Булево:
  • Оператор В содержит подзапрос.
  • Подзапрос оператора В содержит операции ПЕРВЫЕ или УПОРЯДОЧИТЬ ПО.
  • В левой части оператора В и подзапросе содержатся значения разных типов или тип ЛюбаяСсылка.

Рекомендуется проанализировать подобные запросы и выполнить их рефакторинг, при необходимости.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

При использовании файлового или клиент-серверного варианта (при использовании СУБД Microsoft SQL Server) оператор языка запросов В, который отвечает всем следующим критериям, возвращал значение типа Булево или NULL:
  • Оператор В содержит подзапрос.
  • Подзапрос оператора В содержит операции ПЕРВЫЕ или УПОРЯДОЧИТЬ ПО.
  • В левой части оператора В и подзапросе содержатся значения разных типов или тип ЛюбаяСсылка.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если в запросах системы компоновки данных используются запросы с объединениями, то при использовании метода ПроцессорКомпоновкиДанных.Инициализировать() с параметром ОграничиватьПолучениеПолейПоСсылкамПоПравуПросмотра установлено в значение Истина, права Просмотр учитываются для всех частей объединения.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

Если в запросах системы компоновки данных используются запросы с объединениями, то при использовании метода ПроцессорКомпоновкиДанных.Инициализировать() с параметром ОграничиватьПолучениеПолейПоСсылкамПоПравуПросмотра установлено в значение Истина, права Просмотр учитывалось только для первой части объединения.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства администрирования.
Снижено время подключения пользователя к информационной базе при массовом подключении. +При запуске кластера серверов выполняется кеширование значений параметров PublishDistributiveLocation* рабочим процессом. Если в файле conf.cfg выполнено изменение параметров PublishDistributiveLocation*, то система «1С:Предприятие» начнет использовать новые значения каталогов не позднее, чем через 10 секунд после сохранения файла cong.cfg.Значения параметров PublishDistributiveLocation* считывались из файла conf.cfg каждый раз, когда значения параметров требовались системе. Это могло привести к существенным задержкам при массовом подключении пользователей к информационной базе.Снижено время подключения пользователя к информационной базе при массовом подключении.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Переименованы некоторые элементы библиотеки картинок. Старые имена сохранены для совместимости, но могут указывать на другие картинки.
  • Календарь.
  • Калькулятор.
  • Лупа.
  • ВыбратьТип.
  • Выбрать.
  • Очистить.
  • Справка.
  • ПолеВводаКалендарь.
  • ПолеВводаКалькулятор.
  • ПолеВводаОткрыть.
  • ПолеВводаВыбратьТип.
  • ПолеВводаВыбрать.
  • ПолеВводаОчистить.
  • СправкаФормы.
Сервис кластера, хранящий динамическую информацию о составе и состоянии кластера.
  • Сервис блокировок кластера.
  • Сервис состояния кластера.
В документации данное изменение описано здесь.
Упоминание фразы «все функции» в заголовках параметров настройки конфигуратора и клиентских приложений.
  • Параметр Отображать команду «Все функции» в диалоге настройки запуска конфигуратора.
  • Пункт главного меню Все функции и заголовок открывающейся при этом формы.
  • Ключевое слово для глобального поиска Все функции.
  • Отображение результата глобального поиска - Все функции.
  • Параметр Режим технического специалиста в диалоге настройки запуска конфигуратора.
  • Пункт главного меню Функции для технического специалиста и аналогичный заголовок открывающейся при этом формы.
  • Ключевое слово для глобального поиска Функции для технического специалиста.
  • Отображение результата глобального поиска - Функции для технического специалиста.
В документации данное изменение описано здесь, здесь и здесь.
Имена, использующие фразу «все функции». Cтарые имена используются для совместимости.
  • Право доступа РежимВсеФункции.
  • Значение системного перечисления СтандартныйВидГлобальногоПоиска.ВсеФункции.
  • Параметр командной строки запуска клиентского приложения DisplayAllFunctions.
  • Право доступа РежимТехническогоСпециалиста .
  • Значение системного перечисления СтандартныйВидГлобальногоПоиска.ФункцииДляТехническогоСпециалиста.
  • Параметр командной строки запуска клиентского приложения TechnicalSpecialistMode.
В документации данное изменение описано здесь, здесь, здесь и здесь.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильный клиент.
В мобильном клиенте реализована возможность отображения рисунков формата SVG. При работе с данным форматом картинки не поддерживаются фильтры и эффекты.

Реализовано свойство системного перечисления ФорматКартинки.SVG.

Данная возможность не предоставлялась.Мобильный клиент системы «1С:Предприятие» стал поддерживать отображение картинок формата SVG.
Внешние компоненты.
Мобильная платформа.
Мобильный клиент.
Для внешних компонент, которые работают на мобильных устройствах, под управлением ОС iOS, реализована возможность включать в состав внешней компоненты системные динамические библиотеки.

Доработана документация по технологии внешних компонент (см. здесь).

Данная возможность не предоставлялась.

Для внешней компоненты, работающей под управлением ОС iOS, можно было указывать только необходимые компоненты подсистем.

Расширены возможности разработки внешних компонент, работающих под управлением ОС iOS.
Мобильный клиент.
Динамическая установка внешних компонент более не поддерживается в собранном приложении для мобильного клиента (включая мобильного клиента с возможностью автономной работы), который выполняется под управлением ОС Android. Метод ПоддерживаетсяДинамическаяУстановкаВнешнихКомпонент() всегда возвращает значение Ложь на мобильном устройстве (кроме мобильной версии для разработчика).При работе под управлением ОС Android, поддерживалась возможность динамической установки внешних компонент для собранного приложения для мобильного клиента (включая мобильного клиента с возможностью автономной работы).В связи с изменением политики безопасности компанией Google, внешние компоненты, используемые в мобильном клиенте, должны всегда включаться в состав собираемого мобильного приложения.
Форматированный документ.
Изменен внешний вид панели инструментов для форматированного документа и HTML-документа в мобильной версии системы «1С:Предприятие». Возможности, предоставляемые панелью инструментов, не изменились.

Панель форматирования стала выглядеть одинаково для мобильных телефонов и планшетов.

Внешний вид панели инструментов для форматированного документа и HTML-документа в мобильной версии системы «1С:Предприятие» был другим. Панель форматирования выглядела по разному для мобильных телефонов и планшетов.Панель форматирования для форматированного документа и HTML-документа стала проще и понятнее для пользователя.
Мобильная платформа.
Мобильный клиент.
Реализована возможность подключения сервисов статистики использования приложений к собираемому мобильному приложению. Поддерживаются следующие сервисы статистики:
  • FirebaseAnalytics (для Android и iOS).
  • AppMetrica (для Android, iOS и Windows).
  • Appsee (для Android и iOS).

Реализовано свойство глобального контекста СтатистикаИспользованияПриложения.

Данная возможность не предоставлялась.Стала доступна возможность интеграции мобильных приложений для мобильной версии системы «1С:Предприятие» с различными сервисами получения статистики использования мобильных приложений.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Улучшен интерфейс пользователя при выполнении операций фотографирования, записи звука и видео. Реализована возможность ознакомиться с результатом выполненного действия и, при необходимости, повторить действие.Интерфейс пользователя при выполнении операций фотографирования, записи звука и видео был другим. Не предоставлялась возможность предварительного просмотра и прослушивания сделанного. Не предоставлялась возможность повторить действие.Использовать инструменты мобильной версии для записи звука, видео и получения фотографий стало более комфортно и удобно.
Мобильная платформа.
Средства разработки.
В мобильной платформе разработчика стало возможно подключаться к веб-серверу, на котором опубликована конфигурация мобильного приложения, по протоколу HTTPS. В диалоге добавления информационной базы реализована возможность открыть диалог настройки HTTPS-подключения.Данная возможность не предоставлялась.Подключение мобильной платформы разработчику к веб-серверу можно сделать более безопасным (с помощью протокола HTTPS).

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Обработка ошибок.
При аварийном завершении работы программы, может выполняться вызов HTTP-сервиса регистрации ошибок, расположенного по адресу https://pult.1c.com/pult/platform/errors.

Чтобы предотвратить отправку отчетов, необходимо отключить отправку отчетов об аварийном завершении работы с помощью объекта ОбработкаОшибок.

При аварийном завершении работы программы никакие сервисы не использовались.При аварийном завершении работы системы, выполняется автоматическая отправка информации об ошибке в фирму 1С.
В документации данное изменение описано здесь.
Обработка ошибок.
Изменены стандартные тексты сообщений об ошибках. Изменен стандартный диалог отправки отчета об ошибке.

Если желательно, чтобы пользователь отправил отчет о конкретной ошибке в сервис регистрации ошибок, то из сервиса регистрации ошибок рекомендуется вернуть сообщение, мотивирующее пользователя отправить отчет об ошибке. Это сообщение будет отображаться на форме ошибки.

Стандартные тексты сообщений об ошибках были другими. Диалог отправки отчета об ошибке был другим.Улучшено отображение ошибок.
В документации данное изменение описано здесь.
Регистры сведений.
При записи набора записей регистра сведений, для строковых измерений выполняется удаление незначащих символов, расположенных правее последнего значащего символа в строке.При записи набора записей регистра сведений, для строковых измерений не выполнялось удаление незначащих символов, расположенных правее последнего значащего символа в строке.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Если в таблице формы, в результате обновления отображения, все строки в отображаемой области стали невидимы, то для определения первой строки отображения используется свойство таблицы формы НачальноеОтображениеСписка.

Если невидимой стала текущая строка таблицы, то текущей строкой становится ближайшая (по ключу) строка списка, относительно которой и формируется новый список для отображения.

Если прежнее поведение списка использовалось в логике прикладных решений - рекомендуется пересмотреть логику поведения или реализацию механизма.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

Если в таблице формы, в результате обновления отображения, все строки в отображаемой области стали невидимы, то всегда выполнялся переход в начало списка.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если в настройках системы компоновки данных указан отбор с видом сравнения Заполнено или Не заполнено для поля, которое в запросе задано как агрегатная функция, то такое условие в результирующем запросе помещается в секцию запроса ИМЕЮЩИЕ.

В режиме совместимости с версией 8.3.16 поведение не изменилось.

Если в настройках системы компоновки данных указан отбор с видом сравнения Заполнено или Не заполнено для поля, которое в запросе задано как агрегатная функция, то такое условие в результирующем запросе помещалось в секцию запроса ГДЕ.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства администрирования.
Свойство СеансИнформационнойБазы.IPАдресКлиента содержит IP-адрес для сеанса, отличного от текущего, в том случае, если у пользователя имеется право Администрирование. В противном случае данное свойство содержит пустую строку для сеанса, отличного от текущего.Свойство СеансИнформационнойБазы.IPАдресКлиента всегда содержало IP-адрес для сеанса, отличного от текущего.Повышена безопасность при работе со списком сеансов информационной базы.
Обработка ошибок.
Для системного перечисления КатегорияОшибки реализованы значения ОшибкаПолнотекстовогоПоиска, ОшибкаВнешнегоИсточникаДанных и ОшибкаПереходаПоНавигационнойСсылке.

Для формы ошибки и отчета об ошибке отключена возможность открыть справочную информацию, т.к. при отображении этих форм может отсутствовать связь с сервером, откуда получается справочная информация.

Изменен формат файла report.json, в который помещается автоматически собираемая информация об ошибке. Изменения отражены в документации.

При необходимости включения в отчет об ошибке скриншотов, будут включены скриншоты всех окон приложения (даже если приложение не активно в момент возникновения ошибки).

Для объекта НастройкиОбработкиОшибок реализованы свойства ВключатьСнимокОконВОтчет, ВключатьПодробныйТекстОшибкиВОтчет, ВключатьСведенияОбИнформационнойБазеВОтчет, ДополнительнаяИнформацияОтчета.

Доработан внешний вид формы отчета об ошибке.

Для метода getInfo веб-сервиса регистрации ошибок доработан формат файла запроса. Доработка позволит возвращать локализованные тексты сообщений пользователю, а также указывать, какой формат дампа следует сформировать для передачи в сервис (возможность указания типа дампа доступна только при работе клиентского приложения под управлением ОС Windows).

Данные возможности не предоставлялись.Улучшен механизм обработки ошибок времени выполнения.
В документации данное изменение описано здесь и здесь.
Локализация.
Веб-клиент.
Реализована локализация интерфейса веб-клиента для арабского языка (код ar).Данная возможность не предоставлялась.Стало возможно использование веб-клиента системы «1С:Предприятие» пользователями, говорящими и читающими на арабском языке.
Работа с запросами.
Оптимизирована выполнение запросов, использующих оператор языка запросов В со списком значений, в котором существует значение НЕОПРЕДЕЛЕНО.Выполнение запросов, использующих оператор языка запросов В со списком значений, в котором существует значение НЕОПРЕДЕЛЕНО, было неоптимальным.Оптимизация может привести к ускорению выполнения запроса, если в используемом индексе после поля, используемого в выражении Поле В (Неопределено), существуют еще поля, которые используются в отборе.
Работа с СУБД.
Системные требования.
Реализована возможность работы с СУБД Microsoft SQL Server 2019.СУБД Microsoft SQL Server 2019 не поддерживалась.Реализована поддержка новой версии СУБД компании Microsoft.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Клиентское приложение.
Веб-клиент.
Обработка ошибок.
При возникновении невосстановимой ошибки реализована возможность автоматического завершения клиентского приложения без отображения диалога, требующего реакции пользователя. Реализована команда строки запуска клиентского приложения /DisableUnrecoverableErrorMessage.Данная возможность не предоставлялась.

При возникновении невосстановимой ошибки формировалось диалоговое окно, требующее обязательной реакции пользователя.

Упрощено использование системы в режимах, когда работа клиентского приложения не предполагает наличие пользователя (например, в режиме автоматизированного тестирования).
В документации данное изменение описано здесь, здесь и здесь.
Табличный документ.
Отображение информации.
Реализована возможность сохранения направления написания языка в табличном документе при экспорте табличного документа и при его печати. Данная возможность реализована для тонкого клиента, толстого клиента и веб-клиента. Направление текста сохраняется при экспорте во все форматы, которые поддерживают возможность сохранения направления текста.

Направление текста поддерживается при открытии табличного документа системы «1С:Предприятие», а также импорте данных в табличный документ из табличных форматов XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) или ODS (OpenDocument).

Для табличного документа реализовано свойство НаправлениеТекста. Данное свойство позволяет явно указывать направление текста в табличном документе: слева-направо или справа-налево.

При выводе отчетов в табличный документ, если для ячейки установлено автоматическое выравнивание по горизонтали, то числа всегда выравниваются по правому краю, а остальные значения - в зависимости от направления текста интерфейса.

Экспорт и печать табличного документа всегда выполнялась с направлением текста слева-направо. Режим экспорта и печати не зависел от используемой операционной системы.Устранено некорректное поведение системы.
Система взаимодействия.
Реализована возможность выполнения видеозвонков в том случае, если тонкий или толстый клиент работает в окне удаленного рабочего стола (RDP).Не поддерживалась возможность совершения видеозвонков в том случае, если тонкий или толстый клиент работает в окне удаленного рабочего стола (RDP).Устранено ограничение по использованию видеозвонков в тонком и толстом клиентах.
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Для мобильной версии «1С:Предприятие» реализована поддержка аппаратной или внешней клавиатуры в полях формы клиентского приложения, которые отображают данные типа Число и Дата.

Реализована поддержка клавиш Tab и Shift+Tab для перемещения по полям формы. Реализовано перемещение по полям формы с помощью курсорных клавиш аппаратной или внешней клавиатуры, джойстика или другого механизма управления курсором.

Реализована поддержка сочетаний клавиш, заданных разработчиком для элементов формы. Стандартные сочетания клавиш, используемые в версии для персонального компьютера, не поддерживаются.

Реализована поддержка клавиш Esc и Enter на аппаратной или внешней клавиатуре.

Данная возможность не предоставлялась.Улучшен ввод информации на мобильных устройствах, оборудованных аппаратной или внешней клавиатурой.
В документации данное изменение описано здесь.
Регистры накопления.
При установке максимального периода рассчитанных итогов регистра накопления невозможно выполнять запись движений этого регистра.При установке максимального периода рассчитанных итогов регистра накопления было возможно выполнять запись движений этого регистра. При выполнении одновременного изменения максимального периода рассчитанных итогов и записи движений, могло происходить нарушение корректности итогов регистра.Устранено некорректное поведение системы.
Система аналитики.
Для менеджера системы аналитики реализован метод ПолучитьСоединение(), возвращающий объект СоединениеССерверомСистемыАналитики. Реализован объект СхемаСистемыАналитики.

Для стандартной обработки управления аналитикой реализованы возможности управления дополнительными источниками.

Метод глобального контекста ОбновитьИнтерфейс() изменяет видимость пункта Аналитика меню Сервис и настройки (в зависимости от текущего состояния настроек работы с системой аналитики).

Данные возможности не предоставлялась.Расширен программный интерфейс взаимодействия с системой аналитики.
Система аналитики.
Система взаимодействия.
Если информационная база подключена к системе взаимодействия, то из системы аналитики предоставляется возможность открыть информацию по объекту ссылочного типа одновременно во всех клиентских приложениях данного пользователя.Данная возможность не предоставлялась.Улучшен интерфейс системы аналитики.
Полнотекстовый поиск.
Общие реквизиты / Разделение данных.
Уменьшено использование оперативной памяти во время индексации записей регистров сведений.

Ускорено построение индекса для разделенных информационных баз.

Изменен формат временных файлов полнотекстового поиска: формат автоматически изменится при обновлении индекса до актуального состояния. При переходе на предыдущую версию платформы индекс будет очищен.

Индексация записей регистров сведений требовало больше оперативной памяти.

Построение индекса полнотекстового поиска для разделенной информационной базы требовало больше времени.

Оптимизировано построение индекса полнотекстового поиска.
Форма клиентского приложения.
Мобильная платформа.
Мобильный клиент.
Если поле ввода используется для ввода значения типа Число и свойство СпециальныйРежимВводаТекста установлено в значение Цифры, то для ввода используется специальный вид калькулятора, который содержит только цифры, запятую и кнопку удаления последнего символа, ОК и Отмена.Если поле ввода используется для ввода значения типа Число и свойство СпециальныйРежимВводаТекста установлено в значение Цифры, то для ввода использовался обычный вид калькулятора, который включал избыточные возможности.Упрощен ввод чисел в мобильных приложениях.
Автоматизированное тестирование.
Ускорена работа методов НайтиОбъект(), НайтиОбъекты(), ПолучитьОбъект() объекта ТестируемоеПриложение, а также объектов, описывающих оконную модель клиентского приложения.Исполнение методов НайтиОбъект(), НайтиОбъекты(), ПолучитьОбъект() объекта ТестируемоеПриложение, а также объектов, описывающих оконную модель клиентского приложения. занимало больше времени.Повышена производительность механизма автоматизированного тестирования клиентского приложения.
Сборщик мобильных приложений.
Для сборщика мобильных приложений реализована возможность автоматизированной загрузки новых мобильных версий системы «1С:Предприятие». Механизм доступен только в клиент-серверном варианте информационной базы сборщика мобильных приложений.

В сборщике, работающем в файловом варианте информационной базы, недоступны следующие возможности (и соответствующие настройки):

  • Очистка информационной базы от устаревших данных.
  • Очистка кеша сборщика от устаревших данных.

+

Загрузка новой мобильной версии в сборщик мобильных приложений была доступна только интерактивным способом.

Механизмы очистки информационной базы и каталога кеша от устаревших данных работали в файловом варианте информационной базы, что могло приводить к различным незапланированным последствиям из-за особенностей работы механизма регламентных заданий в файловом варианте информационной базы.

Упрощена и ускорена загрузка новой мобильной версии платформы в базу сборщика мобильных приложений.
В документации данное изменение описано здесь и здесь.
Тестирование и исправление информационной базы.
В механизме тестирования и исправления информационной базы реализована возможность выполнения проверки логической целостности расширений конфигурации. Поддерживается как проверка, так и восстановление некоторых проблем, связанных с расширениями.

Для команды пакетного запуска конфигуратора /IBCheckAndRepair реализован параметр -ConfigurationExtensionsLogIntegrity, отвечающий за выполнение проверки логической целостности расширений конфигурации.

Механизм тестирования и исправления информационной базы не поддерживал возможность нахождения (и исправления) проблем, связанных с хранением расширений в информационной базе. Некоторые проблемы могли приводить к полной неработоспособности информационной базы.Повышена стабильность информационной базы, содержащей расширения.
В документации данное изменение описано здесь и здесь.
Выгрузка/загрузка конфигурации в файлы.
Версия формата выгрузки конфигурации в XML-файлы стала равной 2.11.Версия формата выгрузки конфигурации в XML-файлы была равна 2.10.Выгрузка конфигурации в XML-файлы поддерживает новые возможности платформы.
В документации данное изменение описано здесь.
Обработка ошибок.
Переработан механизм информирования об ошибках сети. Тексты ошибок более точно сообщают о сути ошибки и ее причинах (если это возможно).

Если проблема с сетевым соединением возникла при запросе к кластеру серверов «1С:Предприятия» и выполняемое действие может быть повторено после восстановление соединения, то окно с предложением повторить выполняемое действие будет закрыто после восстановления соединения с кластером серверов и будет открыто окно оповещения с информацией о том, что соединение пропадало и потом было восстановлено.

В диалоге с ошибкой отсутствует кнопка отправки отчета об ошибке, если в момент отображения диалога отсутствует сетевое соединение.

Разработчикам прикладных решений рекомендуется переработать код прикладного решения следующим образом:

  • Для выполнения действий, инициированных пользователем, например для отложенного запуска какой-либо процедуры, отображения информации для текущей строки списка и т.д. - использовать однократные обработчики ожидания.
  • Для выполнения действий, которые выполняются автоматически, без вмешательства пользователя, например, периодическое обновление какого-либо статуса - использовать повторяющиеся обработчики ожидания.
  • Для конфигураций, находящихся в режиме совместимости с версией 8.3.16 и предыдущих, для улучшения восприятия пользователем ошибок, рекомендуется переключить вариант отображения ошибок на вариант Сообщение об ошибке для пользователя (с помощью стандартной функции управления настройками обработки ошибок).
Сообщения об ошибках сети были менее понятными и более навязчивыми.

В диалоге отображения ошибки гиперссылка отправки отчета об ошибке присутствовала даже в том случае, когда отсутствовало сетевое соединение (т.е. отправка отчета невозможна).

Диалоги с ошибками сетевой работы стали менее навязчивыми.
В документации данное изменение описано здесь.
Клиентское приложение.
В диалоге аутентификации (для всех клиентских приложений) кнопка подтверждения ввода имени пользователя и пароля называется Войти.

Для поля ввода пароля реализована возможность просмотра введенного пароля открытым текстом. Для этого в правой части поля ввода пароля реализована специальная кнопка.

Улучшено отображение формы аутентификации OpenID Connect на экранах мобильных устройств.

В диалоге аутентификации (для всех клиентских приложений) кнопка подтверждения ввода имени пользователя и пароля называлась Ок.

В поле ввода пароля было невозможно просмотреть введенный пароль открытым текстом.

Диалог аутентификации пользователя стал более удобным и понятным для пользователя.
В документации данное изменение описано здесь.
Копии базы данных.
Оптимизировано первоначальное заполнение таблицы копии базы данных в том случае, когда по переносимой таблице создается много транзакций.Первоначальное заполнение таблицы копии базы данных занимало больше времени в том случае, когда по переносимой таблице создается много транзакций.Ускорено первоначальное заполнение таблицы копии базы данных в том случае, когда по переносимой таблице создается много транзакций.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Мобильные приложения, собранные с использованием мобильной версии 8.3.17.67, будут удовлетворять требованиям магазина приложений Google в части загрузки новых приложений. Целевая версия SDK установлено в значение 29.

Для того, чтобы загрузить мобильное приложение в магазин Google Play, необходимо собрать мобильное приложение с использованием мобильной версии 8.3.17.67 или последующих.

Мобильные приложения, собранные с использованием мобильных версий, предшествующих версии 8.3.17.67, не могли быть загружены в магазин Google Play после 3 августа 2020 года.Мобильная версия системы «1С:Предприятие» удовлетворяет требованиям магазина приложений Google Play.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
Для инструментов мобильной версии, отвечающих за запись звука на мобильном устройстве, реализованы следующие возможности:
  • Управление параметрами записи звука: формат результата, запись моно или стерео звука, характеристики звукового потока и т.д. Реализован объект ПараметрыАудиозаписи.
  • Для метода СредстваМультимедиа.СделатьАудиозапись() реализованы параметры ПараметрыАудиозаписи, НачатьЗаписьСразу, ОтображатьОкноПрослушивания. Параметры позволяют управлять записью звука при использовании мобильного приложения.
  • Реализована возможность управления фоновой записью звука микрофонами устройства. Для свойства глобального контекста СредстваМультимедиа реализованы методы ВключитьАудиозапись(), ОтключитьАудиозапись().
Не поддерживалась возможность настройки параметров записи звука на мобильном устройстве. Не поддерживалась возможность фоновой записи звука на мобильном устройстве.Расширены возможности записи звука на мобильном устройстве.
В документации данное изменение описано здесь.
Сервис интеграции.
Повышена производительность отправки и получения сообщений сервисов интеграции.При работе с сервисами интеграции отправка и получение сообщений выполнялась с недостаточной производительностью.Повышена производительность отправки и получения сообщений сервисов интеграции.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Из списка поддерживаемых сервисов статистики исключен сервис AppSee.

Мобильная версия «1С:Предприятия» поддерживала сервис статистики AppSee.Мобильная версия системы «1С:Предприятие» не поддерживает сервис статистики AppSee.
В документации данное изменение описано здесь и здесь.
Специальные возможности мобильного устройства.
Методы ВключитьАудиозапись() и СделатьАудиозапись() препятствуют переходу устройства в спящий режим, чтобы предотвратить остановку аудиозаписи.

Обработчик остановки аудиозаписи, передаваемый в метод ВключитьАудиозапись(), вызывается таким образом, чтобы не вызывать блокировки интерфейса пользователя.

Значением по умолчанию для параметра РасположениеКнопки метода ВключитьАудиозапись() выступает значение Неопределено.

Улучшен интерфейс аудиозаписи.

Методы ВключитьАудиозапись() и СделатьАудиозапись() не препятствовали переходу устройства в спящий режим, в результате аудиозапись могла прерваться.

Обработчик остановки аудиозаписи, передаваемый в метод ВключитьАудиозапись(), вызывался таким образом, что продолжительный серверный вызов из этого обработчика мог привести к блокировке интерфейса пользователя.

Значением по умолчанию для параметра РасположениеКнопки метода ВключитьАудиозапись() выступало значение, при котором платформа выбирала место расположение кнопки остановки записи автоматически.

Улучшен интерфейс (как пользовательский, так и программный) записи звука в мобильном приложении.
Мобильный клиент.
Мобильный клиент пытается корректно завершить сеанс в кластере серверов в случае аварийного завершения работы. Аварийное завершение может возникнуть, в частности, в том случае, когда мобильная операционная система удаляет приложение мобильного клиента из оперативной памяти при переходе устройства в спящий режим.Мобильный клиент при аварийном завершении не пытался корректно завершить сеанс в кластере серверов.Снижено количество «зависших» сеансов мобильных клиентов. Это приводит к уменьшению количества занятых лицензий, снижению количества блокировок от неактивных устройств.
Системные требования.
Уточнены системные требования для работы клиентского приложения:
  • Минимальные системные требования:
    • Процессор Intel Celeron с тактовой частотой 2 700 МГц и последующие модели.
    • Оперативная память: 4 Гб.
    • Экран с разрешением 1280x768 точек.
  • Рекомендуемые системные требования:
    • Процессоры Intel Core i5, AMD Ryzen 5 и последующие модели.
    • Оперативная память: 8 Гб.
    • Дисковый накопитель: SSD или HDD.
    • Экран с разрешением 1920x1080 точек.
Системные требования для работы клиентского приложения были следующими:
  • Минимальные системные требования:
    • Процессор Intel Pentium/Celeron с тактовой частотой 1 800 МГц и последующие модели.
    • Оперативная память: 1 Гб.
    • Экран с разрешением 800x600 точек.
  • Рекомендуемые системные требования:
    • Intel Pentium/Celeron с тактовой частотой 2 400 МГц и последующие модели.
    • Оперативная память: 4 Гб.
    • Экран с разрешением 800x600 точек.
Уточнены системные требования для работы клиентских приложений (в т.ч. конфигуратора).
В документации данное изменение описано здесь, здесь и здесь.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
Для того, чтобы мобильное приложение, работающее под управлением ОС Android версии 10 и последующих, могло использовать геопозиционирование в фоновом режиме, необходимо в конфигураторе установить разрешение Геопозиционирование в фоновом режиме, выгрузить конфигурацию и повторно собрать мобильное приложение с помощью сборщика мобильных приложений.Мобильное приложение, работающее под управлением ОС Android версии 10 и последующих, не могло использовать геопозиционирование в фоновом режиме.Учтены ограничения операционной системы Android 10 и последующих.
Мобильный клиент.
Переработан механизм проверки возможности подключения к выбранной информационной базе в мобильном клиенте. Проверка подписи мобильного клиента выполняется не только на самом мобильном клиенте, но и на стороне сервера. Мобильный клиент может подключиться к информационной базе в том случае, если конфигурация мобильного клиента и конфигурация сервера совпадают не менее, чем на 80%.

Изменена настройка формирования подписи конфигурации информационной базы.

Ошибки, возникающие в процессе проверки возможности подключения мобильного клиента к выбранной информационной базе, стали более понятными пользователю.

Проверка возможности подключения мобильного клиента к информационной базе выполнялась только на стороне мобильного клиента.

Требование соответствия конфигураций мобильного клиента и основной информационной базы было более строгим.

Мобильный клиент может подключиться к информационной базе в большем количестве случаев. Необходимость обновления мобильного клиента стала менее острой. Ранее опубликованный мобильный клиент может работать с информационной базой в случае небольших доработок конфигурации информационной базы.
В документации данное изменение описано здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Для того, чтобы восстановить возможность доступа мобильного приложения к файлам на мобильном устройстве, необходимо выполнить следующее:
  • Установить SDK Platform для API 29 в Android Studio, которая используется сборщиком мобильным приложений.
  • Загрузить в сборщик мобильных приложений мобильную версию 8.3.17.80 или последующую версию.
  • Выполнить сборку мобильного приложения с новой мобильной версией.
  • Заново опубликовать мобильное приложение в магазине Google Play.

Целевая версия Android возвращена к значению 10.0 (API 29).

Целевая версия Android была равна 11 (API 30). В результате изменения целевой версии Android, мобильное приложение потеряло доступ к файлам на мобильном устройстве.Восстановлен доступа к файлам на мобильном устройстве.
Сборщик мобильных приложений.
В сборщике мобильных приложений реализована поддержка Xcode версии 12.Сборщик мобильных приложений не поддерживал сборку с использованием Xcode версии 12.Сборщик мобильных приложений стал поддерживать актуальную версию Xcode.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Для мобильной версии реализована поддержка операционных систем Android версии 11 и iOS версии 14.Мобильной версия не поддерживала работу под управлением операционных систем Android версии 11 и iOS версии 14.В мобильной версии системы «1С:Предприятие» реализована поддержка актуальных мобильных операционных систем.
В документации данное изменение описано здесь.
Система лицензирования.
При работе в файловой версии выполняется проверка наличия лицензии для тестирования выделенной функциональности.

В частности, использование сервисов интеграции в файловом варианте информационной базы возможно только при наличии лицензии для тестирования выделенной функциональности.

В клиент-серверном варианте поведение не изменилось.

Проверка лицензии для тестирования выделенной функциональности зависела от варианта работы информационной базы:
  • В клиент-серверном варианте проверка выполнялась.
  • В файловом варианте проверка не выполнялась.
Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Картинки.
При получении SVG-картинки из временного хранилища, информационной базы или по прямой ссылке, из картинки удаляются секции, которые содержат JavaScript.При получении SVG-картинки из временного хранилища, информационной базы или по прямой ссылке, удаление из картинки секций, которые содержат JavaScript, не выполнялось.Снижена вероятность выполнения деструктивных действий с помощью JavaScript, встроенного в SVG-картинку.
В документации данное изменение описано здесь.
Средства разработки.
Мобильный клиент.
Конфигурация мобильного клиента, которая подписывалась в версии 8.3.16 (и подпись не изменялась в версии 8.3.17 и последующих версиях), принимается мобильным клиентом версии 8.3.17 и последующих версий.

Не рекомендуется выполнять изменение подписи конфигурации в версии 8.3.16, если конфигурация исполняется на версии 8.3.17.

Конфигурация мобильного клиента, которая подписывалась в версии 8.3.16 (и подпись не изменялась в версии 8.3.17 и последующих версиях), не принималась мобильным клиентом версии 8.3.17 и последующих версий. Платформа версии 8.3.17 и последующие версии, считала такую конфигурации неподписанной.В результате, после обновления платформы на компьютере кластера серверов до версии 8.3.17, мобильные клиенты, работающие под управлением iOS сохранят работоспособность.
Клиентское приложение.
При аутентификации «1С:Предприятия» и в том случае, если доступ к информационной базе выполняется с помощью тонкого клиента и веб-клиента по протоколу HTTP, для передачи пароля пользователя используется хеширование SHA-256 и шифрование AES-256 CBC.Тонкий клиент и веб-клиент передавали пароль пользователя в открытом виде, если для аутентификации использовалась аутентификация «1С:Предприятия» и доступ в информационной базе выполнялся по протоколу HTTP.Повышена безопасность процедуры аутентификации тонкого клиента и веб-клиента при доступе к информационной базе по протоколу HTTP.
Специальные возможности мобильного устройства.
При отправке PUSH-уведомлений с платформы для персонального компьютера через сервис APNS, используется протокол HTTP/2, порт 443.При отправке PUSH-уведомлений с платформы для персонального компьютера через сервис APNS, использовался двоичный протокол, который стал устаревшим.Восстановлена возможность отправки PUSH-оповещений через сервис APNS.
В документации данное изменение описано здесь.
Журнал регистрации.
Кластер серверов.
Ограничено количество потоков индексации журнала регистрации. Реализовано событие технологического журнала <EVENTLOG>.Индексация журналов регистрации могла создавать высокую нагрузку на систему, особенно при большом количестве информационных баз.Снижена нагрузка на систему, вызванная индексацией журнала регистрации, в том случае, когда в кластере серверов расположено большое количество информационных баз.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Веб-клиент.
Системные требования.
Реализована работа веб-клиента в следующих веб-браузерах:
  • Google Chrome 49 и последующих версий, работающего под управлением ОС Linux.
  • chromium-gost версии 49 и последующих, работающих под управлением ОС Linux, macOS и Windows.
Не поддерживалось использование веб-клиента в веб-браузерах:
  • Google Chrome любых версий, работающего под управлением ОС Linux.
  • chromium-gost любых версий.
Расширен список веб-браузеров, в которых можно запускать веб-клиента.
В документации данное изменение описано здесь.
Журнал регистрации.
В файловом варианте информационной базы отключено индексирование журнала регистрации и использование уже построенного индекса.В файловом варианте информационной базы выполнялось индексирование журнала регистрации и при работе с журналом регистрации использовался построенный индекс.Снижена нагрузка на инфраструктуру, особенно при сетевом использовании файловой информационной базы. Повышена стабильность работы клиентского приложения.
В документации данное изменение описано здесь.
Кластер серверов.
Устранено замедление работы пользователей при недостатке оперативной памяти на компьютерах, на которых исполняются рабочие процессы кластера. При этом возможна ситуация, когда вырастет потребление оперативной памяти рабочими процессами кластера.При недостатке оперативной памяти на компьютерах, на которых исполняются рабочие процессы кластера, наблюдалось существенное снижение производительности.Устранено замедление работы пользователей при недостатке оперативной памяти на компьютерах, на которых исполняются рабочие процессы кластера.
Работа с XML, XDTO.
Ускорено чтение секции CDATA большого размера для XML-документа, для которого установлена кодировка UTF-8.Чтение секции CDATA большого размера для XML-документа, для которого установлена кодировка UTF-8, выполнялось медленно.В некоторых случаях ускорена работа с XML-документами.
Работа в ОС Linux.
Кластер серверов.
Средства администрирования.
Для клиентских приложений «1С:Предприятие», работающих под управлением ОС Linux, реализована поддержка аутентификации операционной системы с использованием протокола Kerberos.Данная возможность не предоставлялась.Пользователи, работающие на Linux-машинах в сети с доменом Windows, смогу использовать аутентификацию операционной системы для доступа к информационным базам, которые работают под управлением кластера серверов, развернутого под управлением Windows.
Автономный сервер.
Реализована обязательная аутентификация в информационной базе, при выполнении операций с ней через утилиту администрирования автономного сервера (ibcmd) для следующего набора команд:
  • Выгрузка информационной базы в dt-файл (infobase dump).
  • Загрузка информационной базы из dt-файла (infobase restore).
  • Очистка информационной базы (infobase clear).
  • Загрузка конфигурации (infobase config load).
  • Выгрузка конфигурации (infobase config save).
  • Проверка конфигурации (infobase config check).
  • Обновление конфигурации базы данных (infobase config apply).
  • Возврат к конфигурации базы данных (infobase config reset).
  • Экспорт конфигурации в xml-файлы (infobase config export).
  • Импорт конфигурации из xml-файлов (infobase config import).

Если для работы утилиты администрирования автономного сервера (ibcmd) необходимо указать пароль для соединения с информационной базой и этот пароль не указан в параметрах утилиты, то для ввода пароля в консоли отображается соответствующее предложение.

Для утилиты администрирования автономного сервера (ibcmd) реализованы параметры командной строки --user и --password.

При выполнении операций с информационной базой с помощью утилиты администрирования автономного сервера (ibcmd) не требовалась аутентификация. Если для подключения к СУБД утилите администрирования требовался пароль и этот пароль был не задан - утилита администрирования данный пароль не запрашивала.Работа с информационной базой с помощью утилиты администрирования автономного сервера (ibcmd) стало более безопасным.
В документации данное изменение описано здесь и здесь.
Веб-клиент.
Системные требования.
Реализована поддержка веб-браузера Яндекс.Браузер версии 22 и последующих версий. Яндекс.Браузер поддерживается при работе под управлением операционных систем Linux, macOS и Windows.Данная возможность не предоставлялась.Расширен список поддерживаемых веб-браузеров.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Если для таблицы формы клиентского приложения отключена видимость (в том числе пользователем, таблица находится в свернутой группе и т.п.), то игнорируются вызовы методов Развернуть(), Свернуть(), ДобавитьСтроку(), ИзменитьСтроку(), СкопироватьСтроку(), ЗакончитьРедактированиеСтроки(), Обновить() этой таблицы.

+

Если для таблицы формы клиентского приложения отключена видимость (в том числе пользователем, таблица находится в свернутой группе и т.п.), то вызовы методов Развернуть(), Свернуть(), ДобавитьСтроку(), ИзменитьСтроку(), СкопироватьСтроку(), ЗакончитьРедактированиеСтроки(), Обновить() приводили к формированию исключения.Устранено некорректное поведение системы.
Средства разработки.
Реализована возможность управлять удаленной отладкой и возможностями отладки для разделенных информационных баз. С этой целью реализована возможность указания пользователей, которые могут выполнять отладку конфигураций (в разрезе информационных баз). При подключении к отладчику будет запрашиваться ввод имени пользователя и пароля.

Для командой строки утилит ragent и dbgs реализован команда debugServerUsers. Формат файла описания пользователей приведен в документации.

В диалоге параметров конфигуратора, на вкладке Отладка, удалено поле ввода Пароль.

Реализованы события журнала регистрации Отладка. Подключение предмета отладки, Отладка. Отключение предмета отладки, Отладка. Вычисление выражения.

Данная возможность не предоставлялась.

Имелась возможность указать один пароль для отладки любой базы данных, которая обслуживается кластером.

Расширены возможности разработки прикладных решений, работающих в разделенных информационных базах.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Веб-клиент.
Системные требования.
При работе в веб-клиенте версия веб-браузера Google Chrome должна быть не ниже 88.

При работе веб-клиента в веб-браузере Google Chrome для работы с буфером обмена не требуется расширение работы с файлами. Однако требуется, чтобы веб-клиент был доступен по протоколу HTTPS или опубликован на локальном компьютере. Если эти требования не выполняются - работа с буфером обмена будет недоступна.

При работе в веб-клиенте версия веб-браузера Google Chrome должна была быть не ниже 49.

В веб-клиенте, работающем в веб-браузере Google Chrome, для работы с буфером обмена было необходимо установить расширение работы с файлами.

Прекращена поддержка устаревших версий веб-браузера Google Chrome.
В документации данное изменение описано здесь.
Средства администрирования.
Для работы с паролями пользователей реализованы следующие возможности:
  • Задание минимальной сложности пароля с указанием требований к составу пароля и его сложности.
  • Задание минимального и максимального времени действия пароля.
  • Запрет на использование пользователем паролей, которые уже были использованы ранее.
  • Группировать правила, которым должны соответствовать пароли пользователей, в профили паролей.
  • Назначать пользователям профили паролей.
  • Проверить какой-либо пароль на соответствие текущим политикам паролей без записи пользователя (реального или фиктивного) в информационную базу.
  • Для пользователя с административными правами реализована возможность изменять пароль пользователя, у которого установлен флажок запрета смены пароля.

Реализованы методы глобального контекста УстановитьМинимальныйСрокДействияПаролейПользователей(), ПолучитьМинимальныйСрокДействияПаролейПользователей(), УстановитьМаксимальныйСрокДействияПаролейПользователей(), ПолучитьМаксимальныйСрокДействияПаролейПользователей(), УстановитьОграничениеПовторенияПаролейПользователейСредиПоследних(), ПолучитьОграничениеПовторенияПаролейПользователейСредиПоследних(), УстановитьСрокПредупрежденияОбИстеченииСрокаДействияПаролейПользователей(), ПолучитьСрокПредупрежденияОбИстеченииСрокаДействияПаролейПользователей().

Реализовано свойство глобального контекста ПолитикиПаролейПользователей.

Реализовано свойство ШаблоныНастроекВторогоФактораАутентификации.ПолитикиПаролейПользователей.

Для объекта ПользовательИнформаицоннойБазы реализованы свойства ИмяПолитикиПаролей, ДатаУстановкиПароля, ЗаписываемаяДатаУстановкиПароля.

Данные возможности не предоставлялись.

Некоторые возможности можно было реализовать с помощью встроенного языка, что оставляло возможность обхода требований.

Улучшены инструменты работы с паролями пользователей. В результате стало возможно повысить безопасность системы в целом.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Система лицензирования.
При отображении списка используемых (и использованных) лицензий в диалоге О программе больше не отображается адрес владельца лицензии. Для лицензий, отображаемых в разделах Информационная база и Конфигурация, адреса не скрываются для тех строк, которые получались предыдущими версиями платформы «1С:Предприятие».В информации о лицензиях, которая отображается в диалоге О программе, отображался адрес владельца лицензии.В информации о лицензиях, которая отображается в диалоге О программе, больше не отображается адрес владельца лицензии.

Оглавление

Переход с предыдущей версии на версию 8.3.17

Оглавление

Версия 8.3.16

Версия 8.3.16 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8316doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.15. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.14. +Возможность запуска конфигураций, разработанных в версии 8.3.15 и более младших, в версии 8.3.16, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.16 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.16, при необходимости, использовать для работы с информационной базой и версию 8.3.15. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Системные требования.
Реализована версия для обучения программирования, работающая под управлением ОС Linux и macOS.Версия для обучения программирования работала только под управлением ОС Windows.Версия для обучения программированию работает на всех поддерживаемых операционных системах.
Системные требования.
Работа в macOS.
Прекращена поддержка операционных систем семейства OS X (версия 10.11 и младше). Клиентское приложение работает только под управлением ОС macOS (версия 10.12 и старше).Клиентское приложение могло работать под управлением ОС OS X (версия 10.8 и старше).Прекращена поддержка устаревших операционных систем.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Средства администрирования.
В клиент-серверном варианте работы реализована возможность ограничить количество попыток входа с неверным паролем.

Для информационной базы реализованы следующие параметры: максимальное количество неудачных попыток аутентификации перед блокировкой пользователя; интервал времени, в течении которого будет невозможна попытка повторить аутентификации для пользователя, который совершил пороговое количество попыток аутентификации; суффиксы имени пользователя, которые следует использовать при необходимости выполнить аутентификацию от имени пользователя, находящегося под блокировкой.

Реализовано свойство глобального контекста БлокировкаАутентификации.

Реализована форма просмотра блокировок аутентификации в конфигураторе (Администрирование - Блокировки аутентификации). Команда доступна только пользователю с административными правами.

Реализованы события журнала регистрации:

  • Пользователи. Блокировка аутентификации (_$User$_.AuthenticationLock).
  • Пользователи. Разблокировка аутентификации (_$User$_.AuthenticationUnlock).
  • Пользователи. Ошибка разблокировки аутентификации (_$User$_.AuthenticationUnlockError).

Изменен состав данных событий журнала регистрации:

  • Информационная база. Изменение параметров информационной базы.
  • Сеанс. Аутентификация.
  • Доступ. Доступ (только для Z-версии).
  • Доступ. Отказ в доступе.

В форме отображения списка активных пользователей конфигуратора реализована возможность просмотра колонки с характеристиками разделения данных пользователя.

Данная возможность не предоставлялась.

Платформа никак не противодействовала подбору пароля методом прямого перебора.

Снижена вероятность подбора пароля пользователя информационной базы методом прямого перебора.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с запросами.
В языке запросов реализована поддержка группирующих наборов (grouping set).

В языке запросов реализована поддержка ключевых слов ГРУППИРУЮЩИМ НАБОРАМ для предложения СГРУППИРОВАТЬ ПО.

Реализована функция языка запросов СгруппированоПо(), позволяющая определить, что параметр функции является группируемым.

Данная возможность не предоставлялась.Ускорено выполнение группировки по нескольким наборам полей, т.к. группировка выполняется за одно сканирование таблицы.
В документации данное изменение описано здесь, здесь и здесь.
Диаграммы.
Система компоновки данных.
При использовании диаграмм реализована возможность сохранять соответствие между объектом, который отображается различными диаграммами, и его цветом.

Для диаграмм, отображаемых на форме, для этого требуется использовать код на встроенном языке. Для системы компоновки данных эта возможность реализуется с помощью настроек.

Соответствие объекта и цвета сохраняется системном хранилище настроек.

Реализован метод Диаграмма.ЗаполнитьЦветаСерий().

Для объектов

ЗначенияПараметровВыводаКомпоновкиДанных,

ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и

ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы свойства ТипДиаграммы.СохранениеЦветов и ТипДиаграммы.КлючСохраненияЦветов. Реализовано свойство ПроцессорВыводаРезультатаКомпоновкиДанныхВТабличныйДокумент.ОформлениеДляЗначений. Реализовано свойство МакетГруппировкиДиаграммыОбластиКомпоновкиДанных.Представление.

Данная возможность не предоставлялась.

Один и тот же объект мог отображаться диаграммами разным цветом, что ухудшало восприятие отчета.

Один и тот же объект может выводиться диаграммами одинаковым цветом, что улучшает восприятие диаграмм пользователем и делает диаграммы более информативными.
В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
При использовании системы взаимодействия реализована возможность при видеозвонке включать трансляцию экрана компьютера абоненту.

При работе в веб-клиенте трансляция экрана поддерживается только в веб-браузерах Google Chrome и Mozilla Firefox. При работе в веб-клиенте в веб-браузере Google Chrome доступна трансляция текущей вкладки веб-браузера.

Данная возможность не предоставлялась.Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь.
Система взаимодействия.
При установке из встроенного языка свойства СообщениеСистемыВзаимодействия.Текст значения типа ФорматированнаяСтрока, оформление сохраняется (кроме картинок, которые удаляются). Такое сообщение отображается системой с учетом форматирования. Интерактивное создание сообщения с оформлением не поддерживается.

Реализована поддержка смайликов, заданных эмотиконами (специальными символами Unicode).

Данная возможность не предоставлялась.Расширены возможности программной работы с сообщениями системы взаимодействия.
В документации данное изменение описано здесь.
Средства администрирования.
Кластер серверов.
Реализована возможность получения версии кластера серверов с помощью интерфейсов программного администрирования. Получение версии кластера серверов доступно только в том случае, если кластер серверов работает под управлением системы «1С:Предприятие» версии 8.3.11 и старше.

Реализован метод АдминистрированиеСервера.ПолучитьВерсию().

Реализована команда agent version утилиты rac.

Данная возможность не предоставлялась.При программном администрировании кластера серверов стало возможно определить, какие возможности можно использовать, а какие - нельзя в зависимости от версии «1С:Предприятия» под управлением которой работает кластер серверов.
Табличный документ.
Форматированный документ.
Работа с PDF-документами.
При сохранении документа в формате PDF реализовано встраивание шрифта OpenType, если таковой используется при оформлении сохраняемого документа.Данная возможность не предоставлялась. При сохранении в формат PDF встраивались только шрифты TrueType.Улучшена совместимость документов PDF, формируемых системой «1С:Предприятие», с различными устройствами отображения PDF-документа.
Диаграммы.
Реализована возможность интерактивного изменения значений, отображаемых диаграммами вида: график, график по шагам, график с областями (включая серии с суммированием и нормированием). Данная возможность не поддерживается в режиме совместимости с версией 8.3.15.

Реализовано свойство РежимРедактированияЗначений для объектов Диаграмма и СерияДиаграммы. Реализовано свойство ЗначениеДиаграммы.РежимРедактирования. Для расширения поле формы диаграммы реализовано событие ПриРедактированииЗначения.

Событие расширения поля формы для табличного документа ПриИзмененииСодержимогоОбласти будет вызываться при интерактивном редактировании диаграммы и диаграммы Гантта, вставленных в табличный документ, а в самом обработчике реализован параметр ДополнительныеПараметры.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Данная возможность не предоставлялась.

Событие расширения поля формы для табличного документа ПриИзмененииСодержимогоОбласти не вызывалось при интерактивном редактировании диаграммы Гантта, вставленной в табличный документ.

Расширены возможности интерактивной работы с диаграммами.
В документации данное изменение описано здесь.
Веб-клиент.
Реализована возможность встраивания веб-клиента в сторонние сайты и обеспечить взаимодействие веб-клиента с этими сайтами.

Реализовано свойство глобального контекста ОкноВнешнегоСайта. Реализовано значение системного перечисления РежимОсновногоОкнаКлиентскогоПриложения.ВстроенноеРабочееМесто.

Реализована команда MainWindowMode командной строки запуска клиентского приложения и веб-клиента.

Реализованы права доступа РежимОсновногоОкнаОбычный, РежимОсновногоОкнаРабочееМесто, РежимОсновногоОкнаВстроенноеРабочееМесто, РежимОсновногоОкнаПолноэкранноеРабочееМесто, РежимОсновногоОкнаКиоск, позволяющие запускать клиентское приложение в том или ином режиме основного окна.

Реализован Embedded WebClient API, позволяющий сайту взаимодействовать с веб-клиентом.

Данная возможность не предоставлялась.

Веб-клиент нельзя было встроить в сторонний сайт.

Расширены возможности использования веб-клиента.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Табличный документ.
Работа с PDF-документами.
Реализована возможность сохранения табличного документа в форматы PDF/A-2 и PDF/A-3 (версии формата PDF/A, предназначенного для долговременного хранения).

Для системного перечисления ТипФайлаТабличногоДокумента реализованы значения PDF_A_2 и PDF_A_3.

Для метода ТабличныйДокумент.Записать() реализованы два варианта синтаксиса. Для метода ТабличныйДокумент.НачатьЗапись() реализован параметр Вложения.

Реализованы объекты ЧтениеPDF, ЗаписьPDF.

Предоставлялась возможность сохранения табличного документа только в формате PDF/A-1.Расширены возможности экспорта табличного документа.
В документации данное изменение описано здесь.
План видов характеристик.
Для объектов ПланВидовХарактеристикСсылка и ПланВидовХарактеристикОбъект реализован метод ПолноеНаименование().Данная возможность не предоставлялась.Унифицировано поведение плана видов характеристик и справочника в части получения представления элемента с учетом иерархии.
Табличный документ.
Реализована возможность записи табличного документа (методом ТабличныйДокумент.Записать() в варианте записи в поток) в поток в формате XLSX.Не поддерживалась запись табличного документа (методом ТабличныйДокумент.Записать() в варианте записи в поток) в поток в формате XLSX.Расширены возможности экспорта табличного документа в потоки.
Расширение конфигурации.
Реализована возможность создания в расширении конфигурации:
  • констант;
  • функциональных опций и параметров функциональных опций;
  • критериев отбора.

Реализована возможность расширения:

  • состава заимствованных функциональных опций (собственными и заимствованными объектами);
  • состава заимствованных критериев отбора реквизитами собственных объектов расширения.
Данные возможности не предоставлялись.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь, здесь и здесь.
Управляемая форма.
Реализована возможность формирования контекстного меню планировщика из встроенного языка, а также возможность задавать действие, вызываемое по нажатию левой кнопки мыши (в зависимости от области нажатия).

Для расширения поля формы для поля планировщика реализованы события ОбработкаФормированияКоманд,

НажатиеНаЭлементеИзмерения,

НажатиеНаЭлементеШкалыВремени,

НажатиеНаПеренесенномЗаголовкеШкалыВремени.

Для расширения поля формы для поля планировщика реализованы свойства ГиперссылкаЭлементаШкалыВремени, ГиперссылкаЭлементаИзмерения,

ГиперссылкаПеренесенногоЗаголовкаШкалыВремени.

+

Данные возможности не предоставлялись.Расширены возможности планировщика.
Управляемая форма.
Реализована возможность использования строки поиска для таблицы формы, которая отображает таблицу значений, дерево значений или список значений.

История поиска хранится в хранилище системных настроек с ключом Общее/ИсторияПоискаТаблицы/<Имя формы>.<Имя таблицы>.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Реализована возможность использования команды Найти по текущему значению во всех таблицах формы без учета режима совместимости конфигурации.

Строка поиска была доступна только для тех таблиц формы, которые отображали динамический список. В остальных таблицах поиск выполнялся обычным диалогом поиска, который выполнял позиционирование.

Поиск по текущему значению был недоступен.

Улучшен поиск в таблицах управляемых форм, включая наглядное представление того, что в таблице используется поиск.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Система компоновки данных.
Картинки.
Реализована возможность использовать картинки для условного оформления отчетов в системе компоновки данных. Реализовано свойство ОформлениеКомпоновкиданных.Картинка.

Для библиотеки картинок реализованы картинки: ОформлениеТреугольникВверхЗеленый, ОформлениеДефисЖелтый, ОформлениеТреугольникВнизКрасный, ОформлениеСтрелкаВверхЗеленая, ОформлениеСтрелкаНаклоннаяВверхЗеленая, ОформлениеСтрелкаНаклоннаяВверхЖелтая, ОформлениеСтрелкаВправоЖелтая, ОформлениеСтрелкаНаклоннаяВнизЖелтая, ОформлениеСтрелкаВнизКрасная, ОформлениеСтрелкаНаклоннаяВнизКрасная, ОформлениеСтрелкаВверхСерая, ОформлениеСтрелкаНаклоннаяВверхСерая, ОформлениеСтрелкаВправоСерая, ОформлениеСтрелкаНаклоннаяВнизСерая, ОформлениеСтрелкаВнизСерая, ОформлениеКругЗеленый, ОформлениеКругЖелтый, ОформлениеКругКрасный, ОформлениеКругЧерный, ОформлениеЗнакФлажок, ОформлениеЗнакВоcклицательныйЗнак, ОформлениеЗнакКрест, ОформлениеФлажок, ОформлениеВоcклицательныйЗнак, ОформлениеКрест, ОформлениеФлагЗеленый, ОформлениеФлагЖелтый, ОформлениеФлагКрасный, ОформлениеЗвездаЗаполненная, ОформлениеЗвездаЗаполненнаяНаполовину, ОформлениеЗвездаПустая, ОформлениеКругЗаполненный, ОформлениеКругЗаполненныйНаТриЧетверти, ОформлениеКругЗаполненныйНаДвеЧетверти, ОформлениеКругЗаполненныйНаОднуЧетверть, ОформлениеКругПустой, ОформлениеКвадратыЗаполненныеЧетыре, ОформлениеКвадратыЗаполненныеТри, ОформлениеКвадратыЗаполненныеДва, ОформлениеКвадратыЗаполненныеОдин , ОформлениеКвадратыПустые.

В условном оформлении можно использовать только вышеперечисленные картинки из библиотеки картинок.

Если в конфигурации уже присутствуют картинки, имеющие аналогичные имена, то в коллекцию добавляется картинка из конфигурации, а при обновлении конфигурации выдается предупреждение.

Данная возможность не предоставлялась. Условное оформление системы компоновки данных не позволяло использовать картинки для условного оформления отчетов.Упрощено указание картинок в условном оформлении отчетов, построенных с помощью системы компоновки данных.
Картинки.
Для общих картинок реализована возможность указать, что общая картинка может использоваться:
  • Для выбора картинки в ячейке, рисунке или колонтитуле табличного документа в режиме 1С:Предприятие. Реализовано свойство ОбщаяКартинка.ДоступностьДляВыбора.
  • Для выбора использования в условном оформлении отчетов системы компоновки данных. Реализовано свойство ОбщаяКартинка.ДоступностьДляОформления.

Свойство ОбщаяКартинка.ДоступностьДляВыбора игнорируется в режиме совместимости с версией 8.3.15. Свойство ОбщаяКартинка.ДоступностьДляОформления поддерживается в режиме совместимости с версией 8.3.15.

Данная возможность не предоставлялась.Стало возможно указывать, какие общие картинки могут использовать при работе с табличным документом в режиме 1С:Предприятия и условном оформлении. В результате уменьшается количество картинок, которые доступны пользователю для выбора в этих ситуациях.
Работа с XML, XDTO.
Реализована возможность использования в платформе XSD-схем, содержащих типы, в которых атрибуты определены через ссылки на глобальные атрибуты, но переопределяющие такие свойства как default или fixed.При попытке использования в платформе XSD-схем, содержащих типы, в которых атрибуты определены через ссылки на глобальные атрибуты, но переопределяющие такие свойства как default или fixed, в процессе проверки модели XDTO выдавались ошибки и работа с такими схемами была невозможна.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Система компоновки данных.
Реализована возможность строить комбинированные диаграммы и выводить дополнительную шкалу значений для следующих типов диаграмм:
  • Гистограмма,
  • ГистограммаГоризонтальная,
  • ГистограммаНормированная,
  • ГистограммаНормированнаяГоризонтальная,
  • ГистограммаСНакоплением,
  • ГистограммаСНакоплениемГоризонтальная,
  • График,
  • ГрафикПоШагам,
  • ГрафикСНакоплением,
  • ГрафикСОбластями,
  • ГрафикСОбластямиИНакоплением,
  • ГрафикСОбластямиНормированный,
  • ГистограммаОбъемная,
  • ГистограммаСНакоплениемОбъемная,
  • ГистограммаНормированнаяОбъемная,
  • ГистограммаГоризонтальнаяОбъемная,
  • ГистограммаСНакоплениемГоризонтальнаяОбъемная,
  • ГистограммаНормированнаяГоризонтальнаяОбъемная.

Реализована анимация при изменении значений диаграммы.

Реализованы свойства Диаграмма.ДополнительнаяОсьЗначений и ОбластьПостроенияДиаграммы.ДополнительнаяШкалаЗначений. Реализовано свойство ШкалаДиаграммы.Отображение. Для объекта СерияДиаграммы реализованы свойства ТипГрафическогоПредставления, ТипНакопления, ГруппаНакопления, ИспользуемаяОсьЗначений, ФорматЗначенийВПодписях, ФорматПроцентовВПодписях, ФорматВТаблицеДанных.

Свойство СерияДиаграммы.Индикатор является устаревшим, не рекомендуется к использованию, поддерживается для совместимости. Рекомендуется использование свойства СерияДиаграммы.ТипГрафическогоПредставления.

Значение свойства Диаграмма.ТипДиаграммы по умолчанию равно Гистограмма.

Значение свойства Диаграмма.Окантовка по умолчанию равно Ложь.

Для объектов ОформлениеГруппировкиДиаграммыОбластиКомпоновкиДанных и ОформлениеКомпоновкиДанных реализованы свойства ТипГрафическогоПредставленияВДиаграмме, ТипНакопленияВДиаграмме, ИспользуемаяОсьЗначенийВДиаграмме. Реализовано свойство ОформлениеГруппировкиДиаграммыОбластиКомпоновкиДанных.ГруппаНакопленияВДиаграмме. Для объектов

ЗначенияПараметровВыводаКомпоновкиДанных,

ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и

ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры ТипДиаграммы.ДополнительнаяШкалаЗначений, ТипДиаграммы.ДополнительнаяОсьЗначений.

Параметр ТипДиаграммы.ИндикаторВДиаграмме является устаревшим, не рекомендуется к использованию, поддерживается для совместимости. Рекомендуется использование параметра ТипДиаграммы.ТипГрафическогоПредставленияВДиаграмме.

Для объекта ОформлениеГруппировкиДиаграммыОбластиКомпоновкиДанных реализованы параметры ФорматЗначенийВПодписяхДиаграммы и ФорматВТаблицеДанныхДиаграммы.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Не поддерживалась возможность строить комбинированные диаграммы и выводить дополнительную шкалу значений.

Значение свойства Диаграмма.ТипДиаграммы по умолчанию равно ГистрограммаОбъемная.

Значение свойства Диаграмма.Окантовка по умолчанию равно Истина.

Расширены возможности построения диаграмм.
В документации данное изменение описано здесь, здесь и здесь.
Кластер серверов.
Реализована возможность запуска резервных рабочих процессов. Резервный рабочий процесс запускается заранее и для него синхронизируются служебные данные кластера серверов. Данная возможность позволяет уменьшить время переключения клиентского приложения на новый рабочий процесс в случае аварийного завершения рабочего процесса, обслуживающего это клиентское приложение.

Признак необходимости резервирования устанавливается для информационной базы. Количество резервных рабочих процессов рассчитывается исходя из свойства рабочего сервера Количество ИБ на процесс.

Реализованы свойства АдминистрированиеИнформационнаяБаза.РезервированиеРабочихПроцессов и АдминистрированиеРабочийПроцесс.Резервный.

В интерфейсе работы с сервером администрирования из языка Java реализованы методы IWorkingProcessInfo.isReserve(), IInfobaseInfo.getReserveWorkingProcesses() и IInfobaseInfo.setReserveWorkingProcesses().

Для утилиты командной строки (rac) кластера серверов реализованы:

  • Параметр reserve-working-process для команд infobase insert и infobase update.
  • Поле reserve-working-processes для результата работы команды infobase info.
  • Поле reserve для результата работы команды process info.
Данная возможность не предоставлялась.

Новый рабочий процесс запускался только после того, когда аварийно завершался текущий рабочий процесс, что могло приводить к существенным временным задержкам при переподключении клиентского приложения. С точки зрения пользователя это выглядело как «замерзание» интерфейса клиентского приложения в момент подключения к новому рабочему процессу.

Снижены временные задержки, возникающие во время переключения клиентского приложения на новый рабочий процесс. Повышена реактивность работы системы.
В документации данное изменение описано здесь, здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Управляемая форма.
В таблице формы клиентского приложения, отображающей дерево значений (включая диалог Все функции), поиск через строку поиска выполняется с учетом родителя и по словам.

В форме истории дата и время записи больше не участвуют в поиске.

В таблице формы клиентского приложения, отображающей дерево значений, поиск выполнялся без учета родителя и по подстроке.

В форме истории дата и время записи участвовали в поиске.

Улучшен поиск в таблицах формы клиентского приложения, отображающих деревья (в том числе в диалоге Все функции).
В документации данное изменение описано здесь.
Веб-клиент.
Работа с файлами.
Переработан механизм проверки безопасности доступа к файловой системе и буферу обмена при работе веб-клиента в веб-браузерах Google Chrome и Mozilla Firefox (включая расширения веб-браузеров и расширения работы с файлами).

После обновление расширения веб-браузера и расширения работы с файлами, при необходимости получить доступ к файловой системе, пользователь должен будет подтвердить, что он доверяет сайту (на котором опубликован веб-клиент) работать с файловой системой его локального компьютера. После этого вопросов больше не задается до момента отзыва этого разрешения (через настройки расширения веб-браузера). Если пользователь отказывает в доверии - продолжает работать старый механизм получения разрешений (отдельный запрос на каждое действие).

Аналогичным образом разрешается работа с буфером обмена.

Разрешения хранятся в разрезе адресов сайтов, на которых опубликованы веб-клиенты.

При работе в веб-клиенте, пользователю выводился отдельный вопрос при каждой операции работы с файлами, чтобы было не очень удобно для пользователя.Упрощена работы с файлами в веб-клиенте в части разрешения пользователя на операции с файловой системой и буфером обмена.
Система взаимодействия.
В истории пользователя реализовано отображение признака участия данного пользователя в контекстном обсуждении по объекту, связанному с формой в истории.

Оптимизировано открытие истории работы пользователя.

В истории пользователя не отображался признак участия данного пользователя в контекстном обсуждении по объекту, связанному с формой.Пользователю стало проще найти в истории работы формы объектов, в контекстном обсуждении которых для этот пользователь выступал получателем сообщений.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Кластер серверов.
Оптимизирована работа платформы «1С:Предприятие» при работе под управлением ОС Windows 8 и выше, в том случае, когда клиентское приложение и кластер серверов расположены на одном компьютере.Работа платформы «1С:Предприятие» при работе под управлением ОС Windows 8 и выше, в том случае, когда клиентское приложение и кластер серверов расположены на одном компьютере была менее оптимальной. Межпроцессные взаимодействия требовали больше времени.Оптимизирована работа системы «1С:Предприятие» при работе под управлением ОС Windows 8 и выше.
Табличный документ.
Уменьшено количество оперативной памяти, которое занимает табличный документ, содержащий большое количество ячеек с текстом.Табличный документ, который содержит большое количество ячеек с текстом, занимал больше места в оперативной памяти.Уменьшено потребление оперативной памяти табличным документом.
Кластер серверов.
Оптимизирована работа кластера серверов при работе с большими объемами сеансовых данных. Ускорено открытие управляемой формы, выполнение контекстного серверного вызова, работа с временным хранилищем.

Реализовано событие технологического журнала <SDGC>.

Кластер серверов тратил больше времени на работу с большими объемами сеансовых данных. Открытие управляемой формы, выполнение контекстного серверного вызова, работа с временным хранилищем занимало больше времени.Оптимизирована работа кластера серверов.
В документации данное изменение описано здесь и здесь.
Регистры накопления.
Оптимизирована работы виртуальной таблицы остатков регистра накопления.При использование виртуальной таблицы остатков регистра накопления тратилось больше времени на получение результата запроса.Оптимизирована работы виртуальной таблицы остатков регистра накопления.
Работа с запросами.
При работе в клиент-серверном варианте информационной базы оптимизировано исполнение запроса, включающее оператор языка запросов В со списком значений, в том случае, если слева в операторе В находится поле ссылочного типа, включающее несколько основных таблиц, а в списке значений находятся ссылки на разные таблицы (из списка составного типа) и отсутствует значение Неопределено.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При работе в клиент-серверном варианте информационной базы выполнение запроса, в котором располагался оператор языка запросов В со списком значений, в том случае, если слева в операторе В находилось поле ссылочного типа, включающее несколько основных таблиц, а в списке значений находились ссылки на разные таблицы (из списка составного типа) и отсутствовало значение Неопределено, занимало больше времени.Ускорено исполнение запросов, содержащих оператор В с полями составного типа.
Работа с Интернет.
Оптимизировано получение заголовков сообщения электронной почты с помощью метода ИнтернетПочтовоеСообщение.ПолучитьПолеЗаголовка().Получение заголовков сообщения электронной почты с помощью метода ИнтернетПочтовоеСообщение.ПолучитьПолеЗаголовка() занимало существенное время.Оптимизировано получение заголовков сообщения электронной почты.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Отображение информации.
Клиентские приложения (кроме веб-клиента), работающие под управлением ОС macOS, Linux и Windows, переведены на использование графической подсистемы, основанной на библиотеке Cairo.Клиентские приложения (кроме веб-клиента), работающие под управлением ОС macOS, Linux и Windows, в каждой операционной системе использовали свои варианты графических подсистем, основанных на разных технологиях и библиотеках.Унификация и оптимизация отображения пользовательского интерфейса в поддерживаемых операционных системах.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
В диалоге публикации конфигурации на веб-сервере надписи приведены в соответствие с текущим составом клиентских приложений платформы.В диалоге публикации конфигурации на веб-сервере надписи не учитывали наличие мобильного клиента.Диалог публикации конфигурации на веб-сервере учитывает наличие мобильного клиента.
В документации данное изменение описано здесь, здесь и здесь.
Полнотекстовый поиск.
В механизме полнотекстового поиска реализована возможность поиска по хештегу (строки вида #Слово, от символа # до первого пробела).

Для применения нечеткого поиска (как в интерактивном режиме, так и при поиске из встроенного языка с помощью объект МенеджерПолнотекстовогоПоиска) необходимо использовать символ ~.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Собственно поиск по хештегу не поддерживался, но было возможно найти «значение» хештега (слово после символа #) обычным образом или заключив искомый хештег в двойные кавычки.

Символ # использовался для операции нечеткого поиска.

Стало возможно отмечать объекты, участвующие в полнотекстовом поиске, хештегами. В результате стало возможно просто находить несколько разных типов объектов, объединенных только хештегом.
В документации данное изменение описано здесь и здесь.
Права доступа.
Если права доступа не позволяют сохранить в файл табличный документ, текстовый документ, графическую схему, географическую схему, пакет отображаемых документов и HTML-документ, но после создания указанных объектов был включен привилегированный режим, то сохранение файла становится возможным.Если права доступа не позволяют сохранить в файл табличный документ, текстовый документ, графическую схему, географическую схему, пакет отображаемых документов и HTML-документ, то включение привилегированного режима игнорировалось системой и возможность сохранения документов в файл не появлялась.Устранено некорректное поведение системы.
Ввод по строке.
При использовании ввода по строке для управляемого приложения в результатах поиска выделяются все искомые слова в том случае, если для выполнения ввода по строке не используется полнотекстовый поиск или полнотекстовый поиск завершился с ошибкой.

Если при вводе по строке используется полнотекстовый поиск в данных, то при успешном применении полнотекстового поиска игнорируется настройка Способ поиска строки при вводе по строке, искомый текст всегда разбивается на слова и поиск выполняется по началу слов.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При использовании ввода по строке для управляемого приложения в том случае, если для выполнения ввода по строке не использовался полнотекстовый поиск или полнотекстовый поиск завершился с ошибкой, то не выделялись два идущих подряд вхождения одной и той же строки, в первой половине результатов выделялось только первое вхождение искомого слова (при поиске одного слова).Улучшено выделение результатов поиска при вводе по строке.
Отображение информации.
При работе под управлением ОС Windows, повышена стабильность и скорость отклика клиентского приложения при работе с недоступными принтерами.При работе под управлением ОС Windows возникали проблемы при работе с недоступными принтерами, вплоть до аварийного завершения работы клиентского приложения, а также существенные замедления при начале работы клиентского приложения.При работе под управлением ОС Windows, повышена стабильность и скорость отклика клиентского приложения при работе с недоступными принтерами.
Кластер серверов.
Данное изменение отменено.

Реализована возможность параллельного пересчета итогов регистров при реструктуризации информационной базы и при выполнении тестирования и исправления информационной базы. Для пересчета используются системные фоновые задания (идентификатор такого фонового задания SystemBackgroundJob.RecalcTotals). Реализован параметр Количество заданий пересчета итогов для диалога Параметры информационной базы. По умолчанию количество фоновых заданий пересчета итогов равно 4.

Реализованы методы глобального контекста ПолучитьКоличествоЗаданийПересчетаИтогов() и УстановитьКоличествоЗаданийПересчетаИтогов().

Пересчет итогов регистров во время реструктуризации информационной базы и при выполнении тестирования и исправления информационной базы выполнялся последовательно, по всем необходимым регистрам информационной базы.Ускорена операция пересчета итогов при выполнении реструктуризации и тестирования и исправления информационной базы.
В документации данное изменение описано здесь и здесь.
Автоматизированное тестирование.
Реализована возможность использования в механизме автоматизированного тестирования дополнения элемента формы. Реализован объект ТестируемоеДополнениеЭлементаФормы.

Для объекта ТестируемаяТаблицаФормы результат, возвращаемый методами ПолучитьПодчиненныеОбъекты(), ПолучитьОбъект(), НайтиОбъекты() и НайтиОбъект() может включать объекты типа ТестируемоеДополнениеЭлементаФормы.

Для метода ТестируемаяТаблицаФормы.ПерейтиНаУровеньВниз() реализован параметр ОписаниеСтроки, позволяющий указать представление дочерней группы, в которую необходимо перейти.

Для метода ТестируемаяТаблицаФормы.ПерейтиНаУровеньВверх() реализован параметр ОписаниеСтроки, позволяющий указать представление родительской группы, в которую необходимо перейти.

Для метода ТестируемаяТаблицаФормы.Развернут() реализован параметр ОписаниеСтроки, позволяющий указать представление строки таблицы, для которой необходимо проверить свернута эта строка или развернута.

Для метода ТестируемаяТаблицаФормы.ВозможноРазвернуть() реализован параметр ОписаниеСтроки, позволяющий указать представление строки таблицы, для которой проверяется возможность развертывания.

Реализована функция ТестируемоеПолеФормы.ПолучитьОтображениеСостояния() возвращающая текущее состояние поля табличного документа.

Реализована функция ТестируемоеПриложение.ОжидатьСостояния(), предназначенная для выполнения ожидания в течении указанного времени.

Реализована функция ТестируемаяГруппаФормы.ТекущееОткрыта(), возвращающая статус группы: свернута или развернута.

Реализована функция ТестируемаяКнопкаФормы.ТекущееПометка(), возвращающая признак того, что кнопка нажата или отображает пометку.

Реализована возможность передавать в метод ВыполнитьОбработкуОповещения() ссылку на функцию, которая вернет платформе результат обработки оповещения.

Данные возможности не предоставлялись.Расширены возможности автоматизированного тестирования. В механизме учтены новые возможности интерфейса Такси.
Управляемая форма.
Расширение конфигурации.
В редакторе заимствованной формы реализовано отображение измененных и неизменных заимствованных элементов формы разными цветами.

Реализована команда редактора формы, позволяющая отобразить в дереве элементов формы только измененные заимствованные и собственные элементы формы.

В панели свойств объектов расширения реализовано отображение другим цветом свойств объекта конфигурации, измененного в расширении относительно расширяемой конфигурации.

В панели свойств объектов расширения реализована команда, позволяющая показать только те свойства, которые были изменены относительно расширяемой конфигурации.

В редакторе заимствованной формы не было возможности скрыть неизменные заимствованные элементы в дереве элементов формы. Элементы формы не отличались цветом.

В панели свойств не предоставлялось возможности быстро различить измененные и неизменные свойства заимствованного объекта конфигурации.

Упрощено редактирование заимствованных объектов конфигурации.
В документации данное изменение описано здесь.
Динамический список.
В динамическом списке не поддерживается использование полей с разными выражениями для выбора и отбора в качестве ключевых полей динамического списка.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

В динамическом списке было возможно использование полей с разными выражениями для выбора и отбора в качестве ключевых полей динамического списка. В этом случае при работе динамического списка могли наблюдаться различные труднодиагностируемые ошибки.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
При открытии в системе «1С:Предприятие» табличного документа в формате Microsoft Office OpenXML (*.xlsx) и Microsoft Excel (*.xls), условное форматирование импортируется только для области исходного документа, которая содержит данные. При импорте данных условного форматирования снижено потребление оперативной памяти.

При просмотре табличного документа, полученного в результате импорта, возможны ситуации, когда форматирование получившегося документа отличается от оригинала (в части оформления области документа, которая не содержит данные).

При открытии в системе «1С:Предприятие» табличного документа в формате Microsoft Office OpenXML (*.xlsx) и Microsoft Excel (*.xls), условное форматирование импортировалось для всего документа. При этом могло происходить аварийное завершение работы системы из-за нехватки оперативной памяти.Повышена устойчивость работы системы при импорте табличных документов в формате Microsoft Office OpenXML (*.xlsx) и Microsoft Excel (*.xls), в том случае, когда условное форматирование задано целиком для листа, а не только для значимой области.
Система компоновки данных.
Типом поля системы компоновки данных, которое получается в результате использования агрегатных функций языка запросов СУММА() и СРЕДНЕЕ() будет считаться число неограниченной длины.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Типом поля системы компоновки данных, которое получается в результате использования агрегатных функций языка запросов СУММА() и СРЕДНЕЕ() принимался тип поля, которое являлось параметром указанных агрегатных функций.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с СУБД.
В данные (поле Назначение), возвращаемые методом глобального контекста ПолучитьСтруктуруХраненияБазыДанных(), внесена информация, описывающая таблицы, которые создаются при использовании механизма копий базы данных.В данных, возвращаемые методом глобального контекста ПолучитьСтруктуруХраненияБазыДанных(), отсутствовала информация, описывающая таблицы, которые создаются при использовании механизма копий базы данных. В качестве назначения таблицы для всех таблиц механизма копий базы данных было указано значение Основная.Устранено некорректное поведение системы.
Табличный документ.
При отображении табличного документа, содержащего картинки в ячейках либо рисунки типа Картинка:
  • Значение АвтоРазмерБезУчетаМасштаба свойства РазмерКартинки области табличного документа или картинки табличного документа интерпретируется как значение АвтоРазмер.
  • Значение РеальныйРазмерБезУчетаМасштаба свойства РазмерКартинки области табличного документа или картинки табличного документа интерпретируется как значение РеальныйРазмер.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При отображении табличного документа, содержащего картинки в ячейках либо рисунки типа Картинка, наблюдалось следующее поведение:
  • Картинка в ячейке, для которой свойство РазмерКартинки имело значение АвтоРазмерБезУчетаМасштаба или РеальныйРазмерБезУчетаМасштаба, не отображалась.
  • Высота строки, в которой есть ячейка с картинкой, для которой свойство РазмерКартинки имеет значение АвтоРазмерБезУчетаМасштаба, рассчитывалась по реальной высоте картинки.
  • В интерфейсе Такси для рисунка табличного документа типа Картинка, для которой свойство РазмерКартинки имеет значение АвтоРазмерБезУчетаМасштаба или РеальныйРазмерБезУчетаМасштаба картинка отображалась с меньшим размером, чем должна.
Обеспечено корректное отображение картинок в табличном документе.
Форма клиентского приложения.
Меню дополнения элемента формы Управление поиском состоит только из тех команд, которые должны находиться в данном меню: поиск по текущему значению, расширенный поиск, история поиска, отмена поиска).

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Меню дополнения элемента формы Управление поиском состояло из всех команд связанной таблицы формы (аналогично автозаполнению командной панели таблицы). «Лишним» командам отключалась видимость.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Кластер серверов.
При вызове метода ОбновитьИндекс() менеджера полнотекстового поиска, в клиент-серверном варианте информационной базы, подготовительные действия перед непосредственно индексированием выполняются с помощью системного фонового задания (параметры которого аналогичны системному фоновому заданию индексирования). Это фоновое задание выполняется на том же рабочем сервере, что и сервис полнотекстового поиска. Аналогичное поведение будет и при нажатии кнопки Обновить индекс стандартной функции Управление полнотекстовым поиском.

Если в настройках полнотекстового поиска установлено одно задание индексирования, то оно будет выполняться в отдельном фоновом задании.

При вызове метода ОбновитьИндекс() менеджера полнотекстового поиска, в клиент-серверном варианте информационной базы, подготовительные действия перед собственно индексированием выполнялись на том же компьютере, на котором вызван метод.

Если в настройках полнотекстового поиска установлено одно задание индексирования, то оно выполнялось в основном потоке исполнения сервера.

Повышена надежность и скорость работы индексирования полнотекстового поиска. Все действия по индексации выполняются на рабочем сервере, на который назначено выполнения сервиса полнотекстового поиска.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа с запросами.
При исполнении запроса в файловом варианте информационной базы, если число не может быть представлено в требуемой точностью, формируется исключение.При исполнении запроса в файловом варианте информационной базы, если число не может быть представлено в требуемой точностью, то в результат запроса помещается число, состоящее из цифр 9.Устранено некорректное поведение системы.
Средства администрирования.
Для интерфейса работы с сервером администрирования из языка Java реализована поддержка использования Java версии 9 и старше.Интерфейс работы с сервером администрирования из языка Java не поддерживал работу с Java версии 9 и старше. Поддерживалась только Java версии 1.8.Реализована поддержка современных версий Java.
Программное лицензирование.
Утилита лицензирования, при выполнении команд, по умолчанию отправляет обезличенную статистическую информацию в сервис 1С:Пульт. Реализована возможность отключить такое действие при выполнении одной команды с помощью параметра --send-statistics.Утилита лицензирования не взаимодействовала с сервисом 1С:Пульт.Реализовано накопление статистической информации по работе утилиты лицензирования.
В документации данное изменение описано здесь.
Функциональные опции.
Если функциональная опция хранится в справочнике, то после удаления элемента справочника, выполняется пересчет значения функциональной опции.Если функциональная опция хранится в справочнике, то после удаления элемента справочника, не выполнялся пересчет значения функциональной опции и код на встроенном языке мог получить старое значение функциональной опции.Устранено некорректное поведение системы.
Веб-клиент.
Системные требования.
При работе под управлением macOS реализована возможность использовать веб-браузеры Google Chrome и Mozilla Firefox для работы в веб-клиенте.При работе под управлением macOS использовать веб-клиент можно было только с помощью веб-браузера Safari.Расширен список поддерживаемых веб-браузеров при работе под управлением macOS.
В документации данное изменение описано здесь.
Веб-клиент.
Системные требования.
Прекращена поддержка веб-браузера Google Chrome версии 48 и младше. Работа веб-клиента поддерживается в веб-браузере Google Chrome начиная с версии 49.Веб-браузер Google Chrome версии 48 и младше, поддерживался системой.Прекращена поддержка устаревших версий веб-браузера Google Chrome.
В документации данное изменение описано здесь.
Веб-клиент.
При работе под управлением macOS, реализована поддержка расширения работы с файлами и внешними компонентами в веб-браузерах Google Chrome и Mozilla Firefox.

Реализована библиотека адаптера внешних компонент для веб-браузеров Google Chrome и Mozilla Firefox, работающих в macOS. Внесены изменения в технологию разработки внешних компонент (см. здесь).

При работе под управлением macOS, не поддерживалась работа расширения работы с файлами и внешними компонентами в веб-браузерах Google Chrome и Mozilla Firefox.Расширены возможности работы с файлами при работе в macOS с использованием веб-клиента.
Работа с файлами.
Следующие методы объявлены устаревшими, поддерживаются для совместимости не рекомендуются к использованию (во всех клиентских приложениях):
  • УстановитьРасширениеРаботыСФайлами();
  • ПодключитьРасширениеРаботыСФайлами();
  • УстановитьРасширениеРаботыСКриптографией();
  • ПодключитьРасширениеРаботыСКриптографией();
  • УстановитьВнешнююКомпоненту().

Рекомендуется использовать асинхронные аналоги данных методов.

Следующие методы можно было использовать при создании прикладных решений:
  • УстановитьРасширениеРаботыСФайлами();
  • ПодключитьРасширениеРаботыСФайлами();
  • УстановитьРасширениеРаботыСКриптографией();
  • ПодключитьРасширениеРаботыСКриптографией();
  • УстановитьВнешнююКомпоненту().
Исключена поддержка устаревших методов.
Работа с файлами.
После вызова методов НачатьПомещениеФайловНаСервер() или НачатьПомещениеФайлаНаСервер() нет необходимости дожидаться окончания исполнения метода для повторного вызова этих методов.После вызова методов НачатьПомещениеФайловНаСервер() или НачатьПомещениеФайлаНаСервер() для повторного вызова этих методов было необходимо дождаться завершения работы ранее выполненного вызова. Попытка повторного вызова приводила к возникновению ошибки в тонком клиенте или ожиданию завершения предыдущего вызова в веб-клиенте..Стало возможно загружать одновременно несколько файлов (или групп файлов).
Копии базы данных.
Реализована возможность выбирать состав свойств объектов конфигурации, которые передаются в копию базы данных при включенной стандартной репликации. Для настройки доступны следующие объекты:
  • Для ссылочных объектов: реквизиты, табличные части и реквизиты табличных частей.
  • Для регистров: ресурсы и реквизиты.

Остальные реквизиты (стандартные реквизиты, измерения регистров и общие реквизиты, входящие в состав разделителей) передаются всегда.

Запрос, который пытается получить доступ к реквизитам, которые не попадают в копию, исполняется на основной базе данных.

При использовании копии базы данных, созданной в версии 8.3.16 с ограничениями по составу копируемых объектов, эта копия при попытке использования на предыдущих версиях будет считаться неактуальной, а при выполнении синхронизации - будет полностью перезаполнена данными.

Для объекта МенеджерКопииБазыДанных реализованы свойства ИспользованиеТабличныхЧастей, ИспользованиеХранилищЗначения, ИспользованиеСтрокНеограниченнойДлины, ИспользованиеПрочихПолей.

У объекта МенеджерКопииБазыДанных свойства ТипСУБД, СерверБазыДанных и БазаДанных стали доступны на запись.

Параметры метода МенеджерКопииБазыДанных.Добавить() стали необязательными.

Для объекта ЭлементСоставаКопииБазыДанных реализованы свойства Поля, ИспользованиеТабличныхЧастей, ИспользованиеХранилищЗначения, ИспользованиеСтрокНеограниченнойДлины, ИспользованиеПрочихПолей.

Свойство ЭлементСоставаКопииБазыДанных.Метаданные стало доступно на запись. Параметр Элемент методов Вставить() и Добавить() объекта СоставКопииБазыДанны является обязательным. В режиме совместимости с версией 8.3.15 поведение не изменилось.

Изменена стандартная обработка управления копиями базы данных.

В копию базы данных переносились все данные выбранных объектов конфигурации при использовании стандартной репликации. Состав свойств переносимых данных не управлялся.

У объекта МенеджерКопииБазыДанных свойства ТипСУБД, СерверБазыДанных и БазаДанных были доступны только для чтения.

Параметры метода МенеджерКопииБазыДанных.Добавить() были обязательными.

Свойство ЭлементСоставаКопииБазыДанных.Метаданные было доступно только для чтения. Параметр Элемент методов Вставить() и Добавить() объекта СоставКопииБазыДанны был необязательным.

При формировании состава данных копии базы данных стало возможно более точно настраивать состав и объем данных, хранимых в копии базы данных.
В документации данное изменение описано здесь, здесь и здесь.
Внешние отчеты и обработки.
При вызове метода ПолучитьФорму() объектов ОбработкаМенеджер и ОтчетМенеджер будет выполняться проверка наличия у пользователя только права Просмотр на используемую обработку/отчет. Право Использование в этом случае больше не проверяется.

При вызове метода ПолучитьМакет() объектов ОбработкаМенеджер и ОтчетМенеджер не будет выполняться проверка каких-либо прав доступа.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При вызове метода ПолучитьФорму() и ПолучитьМакет() объектов ОбработкаМенеджер и ОтчетМенеджер возникала ошибка, если у пользователя отсутствовало право Использование на обработку или отчет.Устранено некорректное поведение системы.
Система компоновки данных.
Реализована возможность управлять применением условного оформления к областям заголовков полей ресурсов и итогов. Возможность управления реализована как из встроенного языка, так и из формы выбора области применения условного оформления.

Для объекта ЭлементУсловногоОформленияКомпоновкиДанных реализованы свойства ИспользоватьВЗаголовкеПолейРесурсов, ИспользоватьВЗаголовкеОбщегоИтога, ИспользоватьВЗаголовкеПолейРесурсовОбщегоИтога. Данные свойства не поддерживаются в режиме совместимости с версией 8.3.15.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Не поддерживалась возможность управлять применением условного оформления к заголовкам полей ресурсов и итогов.Расширены возможности использования условного оформления в отчетах, построенных с помощью системы компоновки данных.
В документации данное изменение описано здесь.
Динамический список.
При получении данных динамическим списком проверяется наличие всех полей отбора среди доступных полей отбора. При обнаружении первого недоступного для отбора поля генерируется ошибка.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При получении данных динамическим списком не проверялось наличие полей отбора среди доступных полей отбора.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с базой данных.
При работе в файловом варианте информационной базы создаются уникальные индексы в тех же случаях, в которых уникальные индексы создаются при использовании в клиент-серверном варианте информационной базы.

Для принудительного переформирования индексов необходимо изменить режим совместимости и выполнить тестирование и исправление информационной базы с включенным флажком Реструктуризация таблиц информационной базы.

При отключенном режиме совместимости, при записи данных, будет выполняться проверка на уникальность ключей индексов для тех индексов, которые были перестроены во время операции тестирования и исправления.

Во время операции тестирования и исправления (в любом режиме совместимости) уникальность ключей индексов не проверяется.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При работе в файловом варианте информационной базы создавались неуникальные индексы таблиц информационной базы даже в том случае, если в других поддерживаемых СУБД в этом же случае создавались уникальные индексы.

При записи данных система «1С:Предприятие» не выполняла проверки уникальности ключей индексов, что могло приводить к проблемам при переносе информационной базы из файлового в клиент-серверный вариант использования.

Унифицировано поведение системы «1С:Предприятие» между клиент-серверным и файловым вариантами работы в части работы с уникальными индексами. Снижено количество проблем, возникающих при переносе информационной базы из файлового в клиент-серверный вариант информационной базы.
Динамический список.
При нажатии клавиши Enter (или двойном щелчке левой клавишей мыши на строке) в строке таблицы, связанной с динамическим списком, а также при вызове метода таблицы формы ИзменитьСтроку(), расширение таблицы формы будет выполнять открытие формы связанной с этой строкой независимо от того, есть ли в составе команд таблицы команда Изменить.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

При нажатии клавиши Enter (или двойном щелчке левой клавишей мыши на строке) в строке таблицы, связанной с динамическим списком, а также при вызове метода таблицы формы ИзменитьСтроку(), расширение таблицы формы будет выполнять открытие формы связанной с этой строкой:
  • В режиме совместимости с версиями от 8.3.11 до 8.3.15 - только в том случае, если в составе таблицы есть команда Изменить.
  • В режиме совместимости с версией 8.3.10 - независимо от того, есть ли в составе команд таблицы команда Изменить.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Регистры сведений.
Если набор записей независимого регистра сведений записывается в информационную базу без замещения, то в режиме загрузки данных (свойство ОбменДанными.Загрузка установлено в значение Истина) будет выполняться проверка уникальности записей.

Уточнен текст ошибки, возникающий при нарушении уникальности данных.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Если набор записей независимого регистра сведений записывается в информационную базу без замещения, то в режиме загрузки данных (свойство ОбменДанными.Загрузка установлено в значение Истина) проверка уникальности записей не выполнялась. Такое поведение могло приводить к нарушению целостности данных.Устранено некорректное поведение системы.
Работа с СУБД.
Поведение оператора языка запросов В с подзапросом стало одинаковым при работе с использованием любой СУБД.

Возможно изменение результата такого запроса при использовании СУБД IBM DB2, PostgreSQL или Oracle Database. Рекомендуется проанализировать места использования оператора В с подзапросом и при необходимости переработать эти запросы.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Поведение оператора языка запросов В с подзапросом зависело от того, на какой СУБД исполняется запрос.Результат работы оператора языка запросов В с подзапросом перестал зависеть от используемой СУБД.

При использовании СУБД PostgreSQL уменьшено временя выполнения запросов, содержащих оператор В с подзапросом.

Работа с запросами.
При выполнении в языке запросов операции сложения или вычитания, в том случае, если левый операнд операции не мог быть NULL, а правый операнд мог быть NULL, принимается, что результат операции может быть NULL.При выполнении в языке запросов операции сложения или вычитания, в том случае, если левый операнд операции не мог быть NULL, а правый операнд мог быть NULL, принималось, что результат операции не мог быть NULL.Устранено некорректное поведение системы.
Кластер серверов.
При работе в клиент-серверном варианте, для профиля безопасности реализована возможность указывать роли, которые будут применяться в сеансе при переходе в привилегированный режим. При включении привилегированного режима в сеансе будут использовать роли, указанные в профиле безопасности, а при отключении - вернуться к ролям, указанным пользователю. Если в профиле безопасности установлен полный доступ к привилегированному режиму - набор ролей при включении привилегированного режима не изменяется.

Для профиля безопасности реализовано свойство Роли привилегированного режима.

Для объекта АдминистрированиеПрофильБезопасности реализованы свойства РолиПривилегированногоРежима и ПолныйПривилегированныйРежим. Для объекта ISecurityProfile реализованы свойства PrivilegedModeRoles и FullPrivilegedMode.

В интерфейсе работы с сервером администрирования из языка Java для объекта ISecurityProfile реализованы свойства PrivilegedModeRoles и FullPrivilegedMode.

Для утилиты командной строки (rac) кластера серверов реализованы параметры privileged-mode-roles, full–privileged-mode команды profile.

Свойства АдминистрированиеПрофильБезопасности.РазрешитьУстановкуПривилегированногоРежима, ISecurityProfile.PrivilegedModeInSafeModeAllowed (COM-интерфейс администрирования кластера серверов и интерфейс работы с сервером администрирования из языка Java) объявлены устаревшими, не рекомендуются к использованию и поддерживаются для совместимости.

Данная возможность не предоставлялась.

Было невозможно явно указать список ролей, которые будут действовать в сеансе, при переходе в привилегированный режим.

Расширены возможности профилей безопасности в клиент-серверном варианте работы.
В документации данное изменение описано здесь и здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Изменено представление следующих свойств диаграммы в палитре свойств:
  • РежимСглаживания,
  • НатяжениеСглаживания,
  • Текст,
  • АвтоРаздвижениеСерий,
  • ВнутреннийРадиусКольцевойДиаграммы,
  • МаксимумСерийКоличество,
  • МаксимумСерийПроцент,
  • АвтоУстановкаТекстаСерий,
  • АвтоУстановкаТекстаТочек.
  • Режим сглаживание. Режим сглаживания гистограмм непрерывного типа.
  • Натяжение сглаживания. Натяжение гладкой кривой в точках гистограмм непрерывного типа (0 - 100).
  • Текст. Текст серии который будет отображаться на диаграмме.
  • Автоматическое раздвижение секторов. Режим раздвижения секторов круговых диаграмм.
  • Внутренний радиус.
  • Количество. Максимальное количество отображаемых серий.
  • Величина. Процент абсолютного максимума значений для отображаемых серий.
  • Автоустановка текста серий. Генерация текста по умолчанию для новых серий.
  • Автоустановка текста точек. Генерация текста по умолчанию для новых точек.
  • Режим сглаживания. Режим сглаживания линий серии.
  • Натяжение сглаживания. Натяжение гладкой кривой линий серий (0 - 100).
  • Текст. Текст серии, который будет отображаться на диаграмме.
  • Автоматическое раздвижение серий. Режим автоматического раздвижения серий круговых и кольцевых диаграмм.
  • Внутренний радиус. Внутренний радиус кольцевой диаграммы в процентах от внешнего.
  • Максимум серий - количество. Максимальное количество отображаемых серий.
  • Максимум серий - процент. Процент абсолютного максимума значений для отображаемых серий.
  • Автоматическая установка текста серий. Генерация текста по умолчанию для новых серий.
  • Автоматическая установка текста точек. Генерация текста по умолчанию для новых точек.
Имя системного фонового задания индексации полнотекстового поиска.
  • BackgroundJob.FullTextSearchIndexAdditionalUpdate.
  • BackgroundJob.FullTextSearchIndexUpdate.
В документации данное изменение описано здесь.
Настройка информационной базы в мобильном клиенте с автономным режимом работы, отвечающая за включение возможности работы в условиях плохого соединения сети Интернет.
  • Плохое соединение.
  • Рассчитывать на плохое соединение.
Методы и события формы клиентского приложения.
  • Метод ЗаполнитьПриПереоткрытии().
  • Обработчик события ПередПереоткрытием().
  • Обработчик события ПриПереоткрытии().
  • Метод ЗаполнитьПриПереоткрытииСДругогоСервера().
  • Обработчик события ПередПереоткрытиемСДругогоСервера().
  • Обработчик события ПриПереоткрытииСДругогоСервера().
Свойство объекта МенеджерКопииБазыДанных.
  • ИспользованиеХранилищЗначения.
  • ИспользованиеХранилищЗначений.

+

Свойства объектов, используемых для работы с диаграммами.
  • Свойство ПроцессорВыводаРезультатаКомпоновкиДанныхВТабличныйДокумент.ОформлениеДляЗначений.

+

  • Свойство ПроцессорВыводаРезультатаКомпоновкиДанныхВТабличныйДокумент.ОформлениеЗначений.
Картинка библиотеки картинок.
  • ОформлениеКвадратыЗаполненныеЧетыре.

+

  • ОформлениеКвадратыЗаполненные.
Значение системного перечисления ТипСвязиВложенияPDF.
  • НеУказано.
  • НеУстановлено.
Значения системного перечисления РазрешенияДоступаИзмененияPDF.
  • ЗаполнениеИПодпись.
  • ЗаполнениеПодписьИАннотация.
  • ЗаполнениеПодписание.
  • ЗаполнениеПодписаниеАннотирование.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильный клиент.
Реализована поддержка аутентификации по протоколу OpenID Connect для мобильного клиента. Аутентификация использует системный веб-браузер мобильного устройства.

Аутентификация с помощью OpenID Connect поддерживается для устройств, работающих под управлением ОС iOS версии 9.0 и последующих, а также ОС Android с установленным веб-браузером Google Chrome.

Данная возможность не предоставлялась.Для мобильного клиента реализована возможность аутентификации, которая была доступна в тонком клиенте и веб-клиенте.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
Синоним конфигурации не проверяется на совпадение при запуске мобильного клиента. Запуск мобильного клиента будет выполнен в том случае, если имя конфигурации не изменилось с момента сборки мобильного приложения и подпись конфигурации соответствует ее дайджесту.После изменения синонима конфигурации, эту конфигурацию нельзя было использовать с мобильным приложением мобильного клиента, которое было собрано с другим синонимом (например, в котором не было синонима на каком-либо языке).Устранено требование повторной сборки мобильного приложения мобильного клиента в тех случаях, когда изменяется только синоним конфигурации.
В документации данное изменение описано здесь.
Мобильный клиент.
Сборщик мобильных приложений.
Реализован мобильный клиент с возможностью автономной работы. Данное клиентское приложение позволяет работать как в режиме on-line (как мобильный клиент), так и в режиме off-line (как автономное мобильное приложение). Реализована возможность перехода из режима on-line в режим off-line и обратно.

Реализована возможность автономной конфигурации, которые будут доступны на мобильном устройстве в режиме off-line. Автономная конфигурация является подмножеством основной конфигурации. В состав автономной конфигурации могут входить все метаданные, которые существуют в платформе для персонального компьютера. Объекты конфигурации могут входить в состав автономной конфигурации не полностью. Расширения конфигурации не могут быть включены в состав автономной конфигурации.

Реализовано свойство глобального контекста ОсновнойСервер. Реализован метод глобального контекста ОсновнойСерверДоступен(). Реализовано событие модуля клиентского приложения ПриИзмененииДоступностиОсновногоСервера(). Для объекта ФормаКлиентскогоПриложения реализованы:

  • Методы ПереоткрытьСДругогоСервера(), ЗаполнитьПриПереоткрытии().
  • События ПриИзмененииДоступностиОсновногоСервера, ПередПереоткрытием, ПриПереоткрытии.

Для элементов формы поле ввода, кнопка, декорация и таблица реализовано свойство ПоведениеПриНедоступностиОсновногоСервера.

Для объекта конфигурация реализованы свойства СоставАвтономнойКонфигурации, РолиОграниченияАвтономнойКонфигурации. Для общей команды и общей формы реализовано свойство ПоведениеПриНедоступностиОсновногоСервера.

Для редактора формы клиентского приложения реализован предварительный просмотр формы в режима мобильного клиента в автономном режиме. В редакторе формы клиентского приложения реализовано отображение элементов и реквизитов, которые недоступны в автономном режиме на мобильном устройстве.

Реализована возможность выполнять проверку конфигурации в режиме мобильного клиента в автономном режиме.

В настройках конфигуратора реализована возможность указания, в каком режиме будет запускаться мобильный клиент.

Для отладчика реализованы новые предметы отладки.

Сборщик мобильных приложений позволяет собирать приложение мобильного клиента с возможностью автономной работы.

Данная возможность не предоставлялась.

Предоставлялась возможность создания или автономного мобильного приложения или мобильного клиента, который работал в режиме on-line.

Расширены возможности создания мобильных приложений с помощью системы «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Специальные возможности мобильного устройства.
Реализована возможность управлять автоматически резервным копированием данных мобильного приложения средствами мобильной операционной системы. Реализовано разрешение мобильного приложения Резервное копирование средствами ОС. Резервное копирование выполняется:
  • ОС Android - сервис Google Drive или вручную, с помощью Android Debug Bridge.
  • ОС iOS - сервис Apple iCloud.
  • ОС Windows - сервис Microsoft OneDrive.

Сборщик мобильных приложений использует данное разрешение для корректной настройки собираемого мобильного приложения. +

Данная возможность не предоставлялась.Стало возможным выполнять автоматическое резервное копирование данных мобильного приложения (без участия пользователя).
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Специальные возможности мобильного устройства.
Реализовано разрешение мобильного приложения, позволяющая управлять возможностью установки сторонних приложений. Данная возможность поддерживается сборщиком мобильных приложений при сборке для ОС Android.

Реализовано разрешение УстановкаПриложений.

Данная возможность не предоставлялась.

Возможность установки сторонних приложений была всегда разрешена.

Если возможность установки сторонних приложений не требуется для прикладного решения, можно снизить общее количество разрешений, которое требует мобильное приложение при работе под управлением ОС Android.
В документации данное изменение описано здесь.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Средства разработки.
Для конфигуратора реализована возможность выгружать в файл 1Cv8.cf конфигурацию, размер которой превышает 2 Гбайта. Для загрузки такой конфигурации можно использовать только конфигуратор версии 8.3.16 и последующих.При попытке выгрузить в файл 1Cv8.cf конфигурацию, размер которой превышает 2 Гбайта, выгрузка прерывалась с малоинформативным сообщением об ошибке.Стало возможно выгружать в файл 1Cv8.cf очень большие конфигурации.
Отображение информации.
Методы ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() возвращают не более 10 вариантов склонения переданного словосочетания.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Методы ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() не имели ограничений по количеству возвращаемых вариантов склонения переданного словосочетания.Ускорена работа методов ПолучитьСклоненияСтроки() и ПолучитьСклоненияСтрокиПоЧислу() за счет сокращения количества вариантов склонения.
Система компоновки данных.
Динамический список.
Компоновщик макета компоновки данных добавляет упорядочивание из настроек системы компоновки данных в начало списка упорядочивания запроса макета компоновки данных.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

Компоновщик макета компоновки данных добавляет упорядочивание из настроек системы компоновки данных в конец списка упорядочивания запроса макета компоновки данных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Отображение информации.
При автоматическом вычислении цвета текста элемента интерфейса, выбирается более контрастный цвет относительно цвета фона элемента.При автоматическом вычислении цвета текста элемента интерфейса, выбирался менее контрастный цвет относительно цвета фона элемента.Устранено некорректное поведение системы.
Дата акселератор.
Снижен расход оперативной памяти для хранения в Дата акселераторе полей переменной длины (строки переменной длины и хранилища значений).

Оптимизировано выполнение некоторых типов запросов.

Дата акселератор использовал требовал больше оперативной памяти для хранения полей переменной длины (строки переменной длины и хранилища значений).

Выполнение некоторых типов запросов было не оптимальным.

Оптимизирована работа Дата акселератора.
Работа с PDF-документами.
Реализована возможность использования электронной цифровой подписи в документах PDF. Также доступна возможность внедрения в документ визуального представления электронной цифровой подписи.

Реализован объект ОписаниеПодписиPDF. Для объекта ВложениеPDF реализованы свойства ТипСвязи и ТипСодержимого. Для метода КоллекцияВложенийPDF.Добавить() реализованы параметры ТипСодержимого и ТипСвязи.

Объект ЧтениеPDF стал доступен в тонком клиенте и в веб-клиенте. Для работы в веб-клиенте требуется установка расширения работы с файлами. Для объекта ЧтениеPDF реализованы методы ПроверитьПодписи(), ПроверитьПодпись(), ПолучитьОписаниеПодписей(), НачатьОткрытие(), НачатьПолучениеВложений(), НачатьПроверкуПодписей(), НачатьПроверкуПодписи(), НачатьПолучениеОписанияПодписи(), НачатьЗакрытие().

Объект ЗаписьPDF стал доступен в тонком клиенте и в веб-клиенте. Для работы в веб-клиенте требуется установка расширения работы с файлами. Для объекта ЗаписьPDF реализованы методы ЗаписатьПодпись(), НачатьОткрытие(), НачатьЗаписьВложений(), НачатьЗаписьУдаленияВложений(), НачатьЗаписьПодписи(), НачатьЗакрытие().

Данная возможность не предоставлялась.

Предоставлялась возможность сформировать отдельный файл цифровой подписи. +

Расширены возможности работы с PDF-документами. Стало возможно гарантировать неизменность документа с момента его подписи.
В документации данное изменение описано здесь и здесь.
Форма клиентского приложения.
После вызова метода ЗавершитьРаботуСистемы(Ложь), вызов обработчика события ПриЗакрытии выполняется с параметром ЗавершениеРаботы, установленным в значение Истина.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

После вызова метода ЗавершитьРаботуСистемы(Ложь), вызов обработчика события ПриЗакрытии выполнялся с параметром ЗавершениеРаботы, установленным в значение Истина в веб-клиенте и значением Ложь - во всех остальных клиентских приложениях.Устранено некорректное поведение системы.
Глобальный поиск.
Если при выполнении глобального поиска произошла ошибка, то в результат поиска помещается объект ЭлементРезультатаГлобальногоПоиска, у которого в свойство Значение помещен объект ИнформацияОбОшибке с описанием проблемы.

При отображении результатов ошибка будет показана с использованием стилевого цвета ЦветОсобогоТекста.

Для объекта ИнформацияОбОшибке реализована возможность сериализации и XDTO-сериализации.

Ошибки, возникающие при выполнении глобального поиска, не отображались пользователю.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Копии базы данных.
Устранены случаи чрезмерного использования оперативной памяти при переносе данных в копию (в том числе и в Дата акселератор).При переносе данных в копию были возможны случаи чрезмерного использования оперативной памяти.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Общие реквизиты / Разделение данных.
В случае использования двух (и более) разделителей, которые используются одновременно (т.е. хранят свое значение и признак условного разделения в одних объектах конфигурации), метод УдалитьДанныеИнформационнойБазы() будет считать, что объект конфигурации входит в текущую область, если он разделен хотя-бы одним из разделителей из списка разделителей использующих одни и те же объекты конфигурации для хранения своих параметров.

Рекомендуется проанализировать места использования метода УдалитьДанныеИнформационнойБазы() в разделенных конфигурациях и, при необходимости, выполнить рефакторинг этого кода.

В режиме совместимости с версией 8.3.15 поведение не изменилось.

В случае использования двух (и более) разделителей, которые используются одновременно (т.е. хранят свое значение и признак условного разделения в одних объектах конфигурации), метод УдалитьДанныеИнформационнойБазы() считал, что объект конфигурации входит в текущую область, если он был разделен всеми разделителями из списка разделителей использующих одни и те же объекты конфигурации для хранения своих параметров.Изменен подход к определению области данных при использовании метода УдалитьДанныеИнформационнойБазы().
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Ускорено выполнение некоторых операций (запуск, создание информационной базы и т.д.) в мобильных приложениях, собираемых для работы под управлением ОС Android. Размер мобильных приложений, собираемых для работы под управлением ОС Android, несколько увеличился.Выполнение некоторых операций (запуск, создание информационной базы и т.д.) в мобильных приложениях, собираемых для работы под управлением ОС Android, занимало больше времени.Оптимизирована мобильная версия «1С:Предприятия», работающая под управлением ОС Android.
Мобильный клиент.
В мобильном клиенте с автономным режимом работы, форма, которая переоткрывается после изменения доступности основного сервера, переоткрывается с тем же набором параметров формы, что и оригинальная форма.

В документации описана рекомендация по формированию начальной страницы мобильного клиента с автономным режимом.

Для команды пакетного режима запуска конфигуратора CheckConfig реализован параметр -MobileStandalone, позволяющий выполнить проверку конфигурации для работы в автономной конфигурации.

Для команды пакетного режима запуска конфигуратора IBCheckAndRepair реализован параметр -RebuildStandaloneCfg, позволяющий выполнить пересоздание автономной конфигурации.

В мобильном клиенте с автономным режимом работы, форма, которая переоткрывается после изменения доступности основного сервера, переоткрывалась с набором параметров, который включал только ключевые параметры оригинальной формы.Улучшена работа мобильного клиента с автономным режимом работы.
В документации данное изменение описано здесь, здесь и здесь.
Работа в macOS.
Работа в ОС Linux.
Общие объекты.
Объект УникальныйИдентификатор, при использовании в системах, работающих под управлением ОС Linux и macOS, создает уникальные идентификаторы версии 4 (полностью случайный уникальный идентификатор).Объект УникальныйИдентификатор, при использовании в системах, работающих под управлением ОС Linux и macOS, создавал уникальные идентификаторы версии 1 (уникальный идентификатор, зависящий от времени и MAC-адреса сетевого адаптера).Стало возможно использовать встроенные возможности платформы в том случае, если при интеграции требуется передавать во внешний сервис уникальный идентификатор версии 4 и существующий уникальный идентификатор не подходил для такой передачи.
Динамический список.
Полнотекстовый поиск.
При разбиении на слова, которое выполняется при вводе по строке и при поиске в динамическом списке, в качестве разделителя используется только символ « « (пробел). Символы «.», «,»,"-», «/» и «\» больше не считаются разделителями и поиск по ним выполняется как по обычным символам.

При индексации, в индекс полнотекстового поиска добавляются не только строки между каждыми двумя разделителями, но и строки от каждого разделителя до конца строки.

При разбиении на слова, которое выполняется при вводе по строке и при поиске в динамическом списке, в качестве разделителя использовались символы « «, «.», «,»,"-», «/» и «\».Поиск при вводе и в динамическом списке стал лучше соответствовать привычкам пользователя.
В документации данное изменение описано здесь.
Мобильный клиент.
Реализована возможность устанавливать принудительное использование основного сервера. Данную возможность рекомендуется использовать при начальном заполнении информационной базы мобильного клиента с возможностью автономного режима работы.

Реализованы методы глобального контекста УстановитьПреимущественноеИспользованиеОсновногоСервера()/ПолучитьПреимущественноеИспользованиеОсновногоСервера().

Данная возможность не предоставлялась.Стало возможно исключить обращение к локальной информационной базе мобильного клиента во время начального заполнения этой базы данными.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Реализована возможность управлять возможность перехода мобильного устройства в спящий режим во время работы мобильного приложения. Реализованы методы глобального контекста УстановитьЗапретЗасыпанияКомпьютера() и ПолучитьЗапретЗасыпанияКомпьютера().Данная возможность не предоставлялась.Стало возможно блокировать переход мобильного устройства в спящий режим, что может упростить использование мобильного приложения в некоторых сценариях использования.
В документации данное изменение описано здесь.
Мобильный клиент.
В диалоге аутентификации мобильного клиента реализован флажок Запомнить меня. Если данный флажок установлен и используется обычная аутентификация (без использования биометрии), то данные аутентификации запоминаются в безопасном хранилище мобильного устройства.

Для QR-кода, который используется для добавления информационной базы в мобильный клиент, реализованы следующие команды:

  • DisableUseBiometrics - отключает видимость флажка Использовать биометрию.
  • UseBiometrics - описывает состояние флажка Использовать биометрию.
  • DisableRememberMe - отключает видимость флажка Запомнить меня.
  • RememberMe - описывает состояние флажка Запомнить меня.

Для команды /AddInfoBase схемы e1c:// реализованы параметры:

  • DisplayAuthDialog - показывать диалог аутентификации при первом запуске.
  • DisableUseBiometrics - отключает видимость флажка Использовать биометрию.
  • UseBiometrics - описывает состояние флажка Использовать биометрию.
  • DisableRememberMe - отключает видимость флажка Запомнить меня.
  • RememberMe - описывает состояние флажка Запомнить меня.
Данные возможности не предоставлялись.Настройки запуска мобильного клиента стали более подробными.
В документации данное изменение описано здесь, здесь и здесь.
Полнотекстовый поиск.
Во время индексации данных информационной базы, если строка содержит не алфавитно-цифровые символы, то в индекс полнотекстового поиска попадают подстроки от каждого не алфавитно-цифрового символа и до конца строки только в том случае, если длина исходной строки меньше 64 символов.

+

Во время индексации данных информационной базы, если строка содержит не алфавитно-цифровые символы, то в индекс полнотекстового поиска попадали подстроки от каждого не алфавитно-цифрового символа и до конца строки. В результате процесс индексации потреблял много оперативной памяти.Устранено некорректное поведение системы.
Мобильный клиент.
При выполнении мобильного клиента с возможность автономной работы на мобильном устройстве, модули на встроенном языке компилируются с использованием следующих директив препроцессора:
  • На стороне клиента - с использованием директивы препроцессора МобильныйКлиент.
  • На стороне автономного сервера - с использованием директивы препроцессора МобильныйАвтономныйСервер.
  • На стороне сервера для персонального компьютера - с использованием директивы препроцессора Сервер.

Реализована возможность определить сервер, который в данный момент используется в форме клиентского приложения и будет использован при серверном вызове. Реализовано свойство ФормаКлиентскогоПриложения.ИспользуемыйСерверФормы. Реализован метод глобального контекста ПолучитьИспользуемыйСервер().

Для обработчика события формы клиентского приложения ПриИзмененииДоступностиОсновногоСервера реализован параметр СтандартнаяОбработка, позволяющий управлять появлением диалога с вопросом о необходимости переоткрыть форму.

Для свойства СеансИнформационнойБазы.ИмяПриложение реализовано значение MobileClient, описывающий работы сеанса под управлением мобильного клиента. Для метода ПредставлениеПриложения() реализована поддержка значения параметра MobileClient.

При выполнении автономного клиента с возможность автономной работы на мобильном устройстве, модули на встроенном языке компилировались с использованием следующих директив препроцессора:
  • На стороне клиента - с использованием директивы препроцессора МобильноеПриложениеКлиент.
  • На стороне автономного сервера - с использованием директивы препроцессора МобильноеПриложениеСервер.
  • На стороне сервера для персонального компьютера - с использованием директивы препроцессора Сервер.
Директивы препроцессора, которые используются для разделения методов клиент-серверного взаимодействия стали более понятными и логичными в случае использования мобильного клиента с возможность автономной работы.

В прикладном решении стало проще определить, какой сервер будет использоваться в форме и при следующем вызове сервера во встроенном языке.

В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Система взаимодействия.
Для развертывания собственного экземпляра сервера системы взаимодействия можно приобрести отдельный программный продукт (см. здесь), который не требует лицензии уровня КОРП.Для развертывания собственного сервера системы взаимодействия требовалась лицензия уровня КОРП.Для использования собственного экземпляра сервера системы взаимодействие необходимо выполнения одного из условий:
  • Наличие лицензии уровня КОРП.
  • Приобретение отдельного программного продукта «1С:Сервер взаимодействия».
В документации данное изменение описано здесь.
Локализация.
Реализована локализация интерфейса клиентского приложения для армянского языка (код hy).Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» пользователями, говорящими и читающими на армянском языке.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
При выводе сообщения системы взаимодействия, заданных форматированной строкой, выполняется автоматическое распознавание навигационных ссылок, заданных в этой форматированной строке. Если навигационная ссылка указана с оформлением (цвет, шрифт и т.д.), то такая навигационная ссылка не будет распознаваться.При выводе сообщения системы взаимодействия, заданных форматированной строкой, не выполнялось автоматическое распознавание навигационных ссылок, заданных в этой форматированной строке. Устранено некорректное поведение системы.
Работа с СУБД.
При использованием СУБД PostgreSQL в клиент-серверном варианте, выполнение любой реструктуризации информационной базы приводит к изменениям в структуре базы данных. Эти изменения необходимы для поддержки СУБД PostgreSQL 12.

Изменение не влияет на работу системы.

Структура базы данных при использовании СУБД PostgreSQL не позволяла реализовать поддержку СУБД PostgreSQL 12.Структура базы данных позволяет реализовать поддержку СУБД PostgreSQL 12.
Форма клиентского приложения.
Для таблицы формы, связанной с данными типа ДанныеФормаКоллекция и СписокЗначений, реализована доступность команд ПереместитьВверх и ПереместитьВниз при установленном отборе строк.

Для таблиц, связанных с данными типа СписокЗначений, реализована возможность использовать команды ПереместитьВверх и ПереместитьВниз в том случае, если в таблице выделены несколько строк.

Для таблицы формы, связанной с данными типа ДанныеФормаКоллекция и СписокЗначений, при установленном отборе строк команды ПереместитьВверх и ПереместитьВниз были недоступны.

Для таблиц, связанных с данными типа СписокЗначений, не поддерживалась возможность использования команд ПереместитьВверх и ПереместитьВниз в том случае, если в таблице выделены несколько строк.

Устранено некорректное поведение системы.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Реализована поддержка семейства устройств Apple iPhone 11.

Реализована поддержка операционной системы iOS версии 13.

Не поддерживалась работа на семействе устройствах Apple iPhone 11.

Не поддерживалась работа под управлением операционной системы iOS версии 13. +

Реализована поддержка актуальных операционных систем и устройств.
Работа с Интернет.
При работе с электронной почтой реализована поддержка протокола OAuth2 в случае использования протокола SMTP. Для аутентификации используется свойство ИнтернетПочтовыйПрофиль.ТокенДоступа.При работе с электронной почтой протокол OAuth2 использовался только для протокола IMAP.Реализована поддержка почтовых серверов, использующих протокол аутентификации OAuth2 при работе по SMTP.
Система взаимодействия.
В диалоге настройки системы взаимодействия реализована возможность отдельной настройки звуковых уведомлений для сообщений и для видеозвонков.

Настройка оповещений, сделанная в предыдущих версиях, действует для сообщений. По умолчанию оповещение для видеозвонков включено.

Оповещение для видеозвонков разрешает воспроизводить звуковые оповещения во время:

  • Входящего звонка.
  • Завершения звонка.
  • Во время ожидания принятия звонка абонентом.
В диалоге настройки системы взаимодействия была единая настройка звуковых уведомлений для сообщений и видеозвонков.Пользователи смогут отдельно настраивать слышимость оповещений о видеовзонке и обычном оповещении. Это позволит снизить количество пропущенных видозвонков.
Система взаимодействия.
Во время видеозвонка, для добавления нового абонента, предназначена команда Добавить участников в видеозвонок. Изменение реализовано в следующих формах:
  • В форме Обсуждения.
  • В форме контекстного обсуждения.
  • В диалоге параметров пользователя.
  • В подменю видеозвонка в заголовке главного окна.
Во время видеозвонка, для добавления нового абонента, использовалась команда Начать видеозвонок в следующих формах:
  • В форме Обсуждения.
  • В форме контекстного обсуждения.
  • В диалоге параметров пользователя.
  • В подменю видеозвонка в заголовке главного окна.
Наименование команды добавления нового абонента к видеозвонку стало более понятным для пользователя.
Клиентское приложение.
При работе под управлением операционной системы Windows с помощью тонкого или толстого клиентских приложений, изменено отображение заголовков независимых окон (главное окно приложения, окна калькулятора, календаря, системных диалогов и т.д.):
  • В режиме удаленного рабочего стола (RDP) заголовок операционной системы не отображается.
  • Для удаленного приложения RemoteApp заголовок операционной системы:
    • Отображается при запуске под управлением ОС Windows XP.
    • Не отображается при запуске под управлением ОС Windows версии старше, чем Windows XP.
При работе под управлением операционной системы Windows с помощью тонкого или толстого клиентских приложений, независимые окна (главное окно приложения, окна калькулятора, календаря, системных диалогов и т.д.) всегда отображались с заголовком операционной системы при работе в режиме удаленного рабочего стола (RDP) или удаленного приложения RemoteApp.Улучшен внешний вид приложения. При работе с клиентским приложением в терминальном режиме - внешний вид приложения стал более привычным и удобным для работы.
В документации данное изменение описано здесь.
Система взаимодействия.
Изменен внешний вид диалога настройки системы взаимодействия. Настройки, внесенные в диалоге настройки системы взаимодействия, применяются сразу, без необходимости нажатии каких-либо кнопок. Кнопка открытия диалога перенесена в верхнюю часть окна Обсуждения.

В диалоге настройки системы взаимодействия реализована кнопка для вызова диалога выбора оборудования, который позволяет:

  • Выбрать камеру для использования и протестировать изображение с выбранной камеры.
  • Выбрать используемый микрофон и проверить уровень сигнала, идущего с микрофона.
  • Выбрать устройство, используемое для воспроизведения звука.

При выполнении видеозвонка реализована возможность открытия диалога настройки оборудования.

В веб-клиенте диалог настройки оборудования отображается только в веб-браузерах Google Chrome и Mozilla Firefox, если веб-клиент опубликован по протоколу HTTPS (или по адресу localhost) и для адреса публикации предоставлен доступ к микрофону и камере. В диалоге настройки оборудования, список устройств и их названия могут отличаться от списка устройств и их названий в тонком и толстом клиентских приложения (для одного и того же компьютера).

Кнопка вызова диалога настройки системы взаимодействия располагалась в нижней части окна Обсуждения. Настройки, внесенные в диалоге настройки системы взаимодействия, применялись после нажатия кнопки ОК. Возможность указания используемого оборудования отсутствовала.Улучшены возможности настройки системы взаимодействия при наличии на компьютере нескольких устройств, которые могут использоваться при звонках (аудио- и видеозвонки).
Средства администрирования.
Клиентское приложение.
При работе под управлением ОС Windows реализована возможность установки клиентского приложения пользователем, который не обладает административными правами (установка «для пользователя»). В этом случае приложение устанавливается в каталог %LOCALAPPDATA%\Programs.

При такой установке недоступна установка кластера серверов «1С:Предприятие» как сервиса операционной системы.

Установка клиентских приложений в режиме «для компьютера» (при наличии административных прав) сохранена. Установки «для пользователя» и «для компьютера» могут существовать совместно. При выборе клиентского приложения будут использоваться оба списка установленных приложений.

Рекомендуется проанализировать конфигурации на предмет использования явно заданных каталогов размещения системы и вместо явного указания пути использовать метод глобального контекста КаталогПрограммы().

При работе под управлением ОС Windows установка клиентского приложения была возможна только в том случае, если пользователь обладал административными правами или требовало ввод пароля администратора, если пользователь такими правами не обладал.Стало возможно установить клиентское приложение пользователем, который не обладает административными правами.
Мобильный клиент.
Система взаимодействия.
Для мобильного клиента реализована возможность использования видеозвонков системы взаимодействия. При использовании видеозвонка учитывается положение мобильного устройства: перед глазами или около уха.Данная возможность не предоставлялась.Стало возможно использование видеозвонков системы взаимодействия в мобильном клиенте.
Система взаимодействия.
Если клиентское приложение подключено к агенту клиентского приложения, то оповещение о входящем видеозвонке показывается даже в том случае, если клиентское приложение не запущено.

Если пользователь принимает входящий звонок, то запускается клиентское приложение, в котором автоматически начинается видеозвонок к вызывающим абонентом.

Если клиентское приложение подключено к агенту клиентского приложения, то оповещение о входящем видеозвонке не отображалось, если клиентское приложение не было запущено на компьютере.Пользователи станут получать оповещения о входящих видеозвонках при закрытом клиентском приложении. Ранее такие видеозвонки оказывались пропущенными.
Установка клиентского приложения.
Если в ОС Windows XP и Windows Server 2003 установлен Windows Installer версии 3.1, то платформа «1С:Предприятие» может быть установлена только в варианте «для компьютера» (у пользователя должны быть административные права). Если, при работе в ОС Windows XP или Windows 2003, выполнить обновление Windows Installer до версии 4.5, то будет возможно установить платформу «для пользователя» (если у пользователя нет административных прав).

Если в ОС Windows XP и Windows Server 2003 был установлен Windows Installer версии 3.1, то платформа «1С:Предприятие» не устанавливалась на такой компьютер с сообщением о том, что пакет установки не предназначен для этой версии системы установки ОС.Устранено некорректное поведение системы.
Система взаимодействия.
В заголовке окна клиентского приложения реализовано меню, объединяющее все команды работы с системой взаимодействия. Меню доступно только в том случае, если информационная база подключена к системе взаимодействия.

Доступность некоторых команд в данном меню зависит от наличия соответствующей возможности (например, команда начала видеозвонка будет недоступна, если недоступна возможность выполнить видеозвонок).

Команды работы с системой взаимодействия были рассредоточены по интерфейсу системы.Работа с инструментами системы взаимодействия стала более удобной.
В документации данное изменение описано здесь и здесь.
Картинки.
Мобильная платформа.
Мобильный клиент.
В мобильной версии «1С:Предприятие» реализована поддержка многостраничных TIFF-картинок, аналогично платформе для персонального компьютера.Данная возможность не предоставлялась.В мобильной версии «1С:Предприятие» реализована поддержка многостраничных TIFF-картинок.
Система взаимодействия.
Повышена стабильность системы при использовании видеозвонков системы взаимодействия в тонком и веб-клиентах.

Изменения в диалоге настроек параметров используемого оборудования (меню Обсуждения... - пункт меню Настройки - кнопка Настройки) применяются сразу, без необходимости подтверждать изменение.

Наблюдалась низкая стабильность системы при использовании видеозвонков системы взаимодействия в тонком и веб-клиентах.Повышена стабильность системы при использовании видеозвонков системы взаимодействия в тонком и веб-клиентах.
Работа в macOS.
Системные требования.
Уточнены системные требования для клиентского приложения, работающего под управлением macOS. Работа клиентского приложения поддерживается только на macOS 10, начиная с версии 10.12 и последующих.Системные требования для работы клиентского приложения под управлением macOS описывались как версия 10.12 и последующие.Уточнены системные требования клиентского приложения, работающего под управлением macOS.
Кластер серверов.
При аварийном завершении рабочего процесса, переключение сеанса на резервный рабочий процесс занимает меньше времени.При аварийном завершении рабочего процесса, переключение сеанса на резервный рабочий процесс занимало больше времени.В кластере с резервированием, аварийные ситуации с рабочими процессами стали менее заметны пользователям.
Документация.
В документации отражена рекомендация по использованию протокола HTTPs при работе с информационной базой, находящейся в промышленной эксплуатации.В документации отсутствовала рекомендация по использованию протокола HTTPs при работе с информационной базой, находящейся в промышленной эксплуатации.Документация рекомендует использовать более безопасные способы работы через Интернет.
В документации данное изменение описано здесь.
Региональные установки.
Для Российской Федерации учитывается однократный сдвиг часовых зон на один час в связи с принятием закона № 432-ФЗ (Волгоградская область). Изменения касаются всех компонентов системы «1С:Предприятие», кроме веб-клиента. Веб-клиент пользуется информацией о временных зонах, которую предоставляет ОС и веб-браузер. +Изменения, внесенные законом № 432-ФЗ, не учитывались платформой.Учтены изменения законодательства об исчислении времени.
Работа с PDF-документами.
Табличный документ.
Для документа PDF реализована возможность вставки произвольной картинки или табличного документа в требуемое место PDF-документа.

Реализован объект ОписаниеОтображаемогоОбъектаPDF. Для объекта ЗаписьPDF реализованы методы ЗаписатьОтображаемыйОбъект() и НачатьЗаписьОтображаемогоОбъекта().

Данная возможность не предоставлялась.Расширены возможности по работе с документом PDF.
В документации данное изменение описано здесь.
Клиентское приложение.
Установка клиентского приложения.
Веб-клиент.
Файлы платформы, расширений для веб-браузеров и дистрибутивы, которые используются в ОС Windows, подписываются только алгоритмом SHA256.

При использовании веб-браузера Microsoft Internet Explorer (при работе под управлением ОС Windows XP, Windows Vista, Windows Server 2003 и Windows Server 2008) необходимо включить возможность загрузки и подключения неподписанных дополнений.

Рекомендуется для работы с системой «1С:Предприятие» использовать операционные системы Windows 7 и последующие версии (включая работу в веб-клиенте).

Файлы платформы, расширений для веб-браузеров и дистрибутивы, которые используются в ОС Windows, подписывались алгоритмами SHA1 и SHA256.Отказ от поддержки устаревшего и небезопасного алгоритма криптографического хеширования данных SHA1.
Клиентское приложение.
Средства администрирования.
Реализована возможность выбирать режим установки системы «1С:Предприятие»: для всех пользователей или для текущего пользователя. Данная возможность реализована как в интерактивном режиме, так и в виде параметров командной строки/параметров конфигурационных файлов.

Для конфигурационного файла 1cestart.cfg реализован параметр InstallForUsers. Для утилиты setup.exe реализована команда командной строки запуска ALLUSERS.

Режим установки клиентского приложения выбирался исключительно по правам текущего пользователя. Даже если пользователь знал пароль администратора - установка для всех пользователей могла быть запущена только в том случае, если утилита setup.exe запускалась с правами администратора.Упрощено администрирование платформы «1С:Предприятие». Режим установки клиентского приложения можно выбирать так, как требуют текущие политики администрирования.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 9.6.24.1,
  • Postgres Pro 1C 10.19.1,
  • Postgres Pro 1C 11.14.1,
  • Postgres Pro Standard 9.6.24.1,
  • Postgres Pro Standard 10.19.1,
  • Postgres Pro Standard 11.14.1,
  • Postgres Pro Enterprise 9.6.24.1,
  • Postgres Pro Enterprise 10.19.1,
  • Postgres Pro Enterprise 11.14.1.
Данные версии СУБД не поддерживались.Расширен список поддерживаемых СУБД.

Оглавление

Переход с предыдущей версии на версию 8.3.16

Оглавление

Версия 8.3.15

Версия 8.3.15 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8315doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.14. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.13. +Возможность запуска конфигураций, разработанных в версии 8.3.14 и более младших, в версии 8.3.15, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.15 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.15, при необходимости, использовать для работы с информационной базой и версию 8.3.14. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Встроенный язык.
При возникновении некоторых ошибок, реализован вывод стека вызовов (не связанный с вложенными исключениями), которые привели к ошибке, в подробной информации об ошибке.

В 1C:Enterprise Development Tools реализована возможность навигации по стеку вызовов.

При возникновении сообщений об ошибке, подробная информация об ошибке не содержала стек вызовов, который привел к строке с ошибкой (кроме случаев вложенных исключений).Улучшена диагностика ошибок, возникающих при работе прикладного решения.
Работа с Интернет.
Средства администрирования.
Журнал регистрации.
Реализована возможность двухфакторной аутентификации пользователя.

Изменен состав данных для событий журнала регистрации: _$Session$_.Authentication, _$Session$_.AuthenticationError, _$User$_.New, _$User$_.Update.

Реализованы события журнала регистрации: _$Session$_.AuthenticationFirstFactor, _$InfoBase$_.SecondFactorAuthTemplateNew, _$InfoBase$_.SecondFactorAuthTemplateUpdate, _$InfoBase$_.SecondFactorAuthTemplateDelete.

Данная возможность не предоставлялась.Расширены возможности аутентификации пользователей. Реализована возможность реализовать более безопасную аутентификацию пользователей.
В документации данное изменение описано здесь и здесь.
Диаграммы.
Система компоновки данных.
Реализована возможность построения кольцевой и объемной кольцевой диаграмм.

Для системного перечисления ТипДиаграммы реализованы свойства Кольцевая и КольцеваяОбъемная.

Реализовано свойство

Диаграмма.ВнутреннийРадиусКольцевойДиаграммы.

Для объектов ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализован параметр ТипДиаграммы.ВнутреннийРадиусКольцевойДиаграммы.

Данная возможность не предоставлялась.Расширены возможности построения диаграмм.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность указывать форматированную строку в качестве колонтитула табличного документа.

Для свойств ТекстСлева, ТекстВЦентре и ТекстСправа объекта КолонтитулТабличногоДокумента в состав типов включен тип ФорматированнаяСтрока.

Редактор колонтитулов табличного документа позволяет редактировать форматированную строку. При начале редактирования соответствующего поля с текстом колонтитула автоматически включается флажок вывода соответствующего колонтитула в табличный документ. Форматирование колонтитулов сохраняется при экспорте табличного документа в форматы PDF (*.pdf), Microsoft Office OpenXML (*.xlsx и *.docx), Microsoft Excel (*.xls) и Open Document Spreadsheet (*.ods).

Особенности применения форматированной строки для отображения колонтитулов приведены в документации.

Данная возможность не предоставлялась.Расширены возможности оформления табличного документа.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность сохранения табличного документа в формате PDF/A-1 (формат, предназначенный для долговременного хранения). При сохранении в формат PDF/A-1 следует помнить о следующих основных особенностях:
  • Документ записывается в формате PDF 1.4.
  • Не поддерживается двусторонняя печать.
  • Не поддерживается прозрачность.

Реализовано значение системного перечисления ТипФайлаТабличногоДокумента.PDF_A_1.

Данная возможность не предоставлялась.Расширены возможности экспорта табличного документа.
В документации данное изменение описано здесь.
Работа в macOS.
Система взаимодействия.
В клиентском приложении, работающем под управлением ОС macOS, реализована возможность использовать видеозвонки системы взаимодействия.Данная возможность не предоставлялась.Расширены возможности использования системы взаимодействия при работе под управлением ОС macOS.
В документации данное изменение описано здесь.
Система компоновки данных.
Для форм настроек отчета и редактирования варианта отчета реализовано сохранение изменений при закрытии формы. Перед сохранением формируется запрос пользователю. Данное поведение будет наблюдаться в том случае, если параметр СтандартнаяОбработка обработчика события формы ПередЗакрытием установлен в значение Истина.Данная возможность не предоставлялась.

При закрытии формы изменения, выполненные в форме, терялись.

Снижена вероятность утери изменений, выполненных в форме настроек отчета или варианта отчета, при неаккуратном закрытии формы редактирования.
Копии базы данных.
Регистры сведений.
Регистры накопления.
Стандартные функции.
Для регистров сведений и регистров накопления реализована возможность передачи в копию не всех данных регистра, а данных только за определенный период времени. Данная возможность доступна только для стандартной репликации.

Реализовано свойство ЭлементСоставаКопииБазыДанных.Отбор.

Для стандартной обработки Управление копиями базы данных реализована возможность указания отбора по периоду для регистров сведений и регистров накопления.

При определении места выполнения запроса реализован анализ условия на период, дополнительно к существующим проверкам.

Данная возможность не предоставлялась.Расширены возможности механизма копий базы данных. Повышена производительность работы механизма за счет сокращения объема данных, передаваемых в копию.
В документации данное изменение описано здесь и здесь.
Работа с базой данных.
Общие реквизиты / Разделение данных.
Реализована возможность получить размер данных, которые они (данные) занимают в таблицах СУБД (в том числе и для конкретной области данных). При расчете размера не учитывается размер истории данных, расширений и служебных таблиц платформы (индексы и т.д.).

Реализован метод глобального контекста ПолучитьРазмерДанныхБазыДанных().

Данная возможность не предоставлялась.Стало возможно оценивать размер данных, которые находятся в какой-либо области или таблице базы данных.
Расширение конфигурации.
Реализована возможность помечать какое-либо контролируемое свойство расширения таким образом, что несовпадение этого свойства в расширяемой конфигурации и в расширении не будет блокировать применение расширения, но пользователь получит предупреждение о том, что значение свойства в расширении и расширяемой конфигурации различаются.Данная возможность не предоставлялась.Стало возможно предупреждать об изменении каких-либо свойств расширяемой конфигурации. Изменение таких свойств не должно блокировать применение расширения, но сам факт такого изменения должен отдельно отрабатываться разработчиком расширения.
В документации данное изменение описано здесь, здесь и здесь.
Расширение конфигурации.
Средства разработки.
Реализована возможность сопоставлять объекты расширяемой конфигурации и расширения по идентификаторам. При обнаружении конфликтов переименования реализован механизм, помогающий в разрешении конфликтов.

Возможность сопоставлять объекты по идентификаторам может быть отключена.

Для расширения конфигурации реализовано свойство Поддерживать соответствие объектам расширяемой конфигурации по внутренним идентификаторам. Для заимствованных объектов расширения реализовано свойство Объект расширяемой конфигурации.

Сопоставление объектов расширяемой конфигурации и расширения выполнялось только по именам.Упрощена диагностика ситуаций переименования объекта расширяемой конфигурации, которые заимствованы в расширение. Предоставлен инструмент разрешения конфликтов, возникающих при таком переименовании.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
При создании нового расширения, свойство расширения Режим совместимости больше не является контролируемым свойством.При создании нового расширения, свойство расширения Режим совместимости являлось контролируемым свойством.Упрощено создание и применение расширений.
Отображение информации.
В библиотеку картинок добавлены картинки Оповещать, НеОповещать, НеБеспокоить, ОтправитьСообщение.В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.
Расширение конфигурации.
Реализована возможность точечной доработки методов расширяемой конфигурации. В расширение полностью копируется расширяемый метод, в котором директивами препроцессора обрамляется изменяемый код.

Во время применения проверяется, что расширяемый метод не изменен относительно метода в расширении.

Реализована аннотация ИзменениеИКонтроль. Реализованы директивы препроцессора Удалить и Вставить.

Поддерживается возможность вносить изменение в один метод только в одном расширении. Если обнаруживается два расширения, которые расширяют один и тот же метод с помощью аннотации ИзменениеИКонтроль, к информационной базе будет применено только одно расширение.

При обнаружении изменения метода в расширяемой конфигурации поддерживается трехсторонее объединение только с использованием внешней программы. Если в конфигураторе не настроена внешняя программа для сравнения/объединения модулей - объединение будет недоступно.

Вносить изменения в метод с возможностью контроля неизменности исходного текста модуля была недоступна.Упрощено расширение метода расширяемой конфигурации в том случае, если требуется выполнить небольшое изменение внутри метода.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Веб-клиент.
При запуске веб-клиента на мобильных устройствах не отображается предупреждение о том, что используемая версия веб-браузера не поддерживается. Реализована частичная поддержка работы веб-клиента на мобильных устройствах. Полная поддержка работы веб-клиента на мобильных устройствах не реализована.

Исправлены проблемы при работе веб-клиента на мобильных устройствах в основных сценариях.

Работа веб-клиента поддерживалась только на устройствах iPad.Ограниченно доступен веб-клиент при работе на мобильных устройствах.
Общие объекты.
При решении системы линейных уравнений реализована возможность поиска компонент связности различного типа для графов, построенных на основе системы линейных уравнений.

Для метода РасчетСистемЛинейныхУравнений.ПолучитьКомпонентыСвязности() реализован параметр СпособПолученияКомпонент. В режиме совместимости с версией 8.3.14 данный параметр будет принимать значение КомпонентыСильнойСвязностиБезТребованияСвязиВнутриКомпонент.

Данная возможность не предоставлялась.Расширены возможности, предоставляемые системой, для решения системы линейных уравнений.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Реализована навигационная ссылка на сообщения системы взаимодействия.

Реализовано значение системного перечисления СтандартнаяКомандаСистемыВзаимодействия.ПолучитьНавигационнуюСсылкуСообщения.

Данная возможность не предоставлялась.Стало возможно запоминать ссылки на конкретные сообщения системы взаимодействия.
В документации данное изменение описано здесь.
Управляемая форма.
Для поля флажка формы клиентского приложения реализована возможность отображения в виде двухпозиционного выключателя. Реализовано свойство системного перечисления ВидФлажка.Выключатель.

В режиме совместимости ниже Версия 8.3.7 и в платформе младше, чем версия 8.3.15, значение свойство ВидФлажка установленное в значение Выключатель, трактуется как значение Авто.

Данная возможность не предоставлялась.Расширение презентационных возможностей системы.
В документации данное изменение описано здесь.
Управляемая форма.
Клиентское приложение отображает текстовый и табличный документ, графическую схему и картинку, в системной форме клиентского приложения. Такое отображение выполняется в следующих случаях:
  • При создании или открытии документа через меню Файл.
  • При вызове метода Показать() соответствующего объекта встроенного языка или метода ПоказатьЗначение() для объекта типа Картинка.
  • При перетаскивании файла из операционной системы.
  • При открытии вложения системы взаимодействия.

При этом форма, в которой отображается табличный документ или графическая схема, содержит командную панель, упрощающую редактирование соответствующего документа.

Для расширения поля формы для табличного документа, текстового документа и графической схемы реализованы события ПередЗаписью, ПослеЗаписи и ПередПечатью.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Клиентское приложение отображало текстовый документ, табличный документ, графическую схему и картинку в специального вида формах. Эти формы не содержали командных панелей.Редактирование документов платформы стало более понятным и очевидным. Стало возможно обрабатывать сохранение и печать текстового документа, табличного документа и графической схемы.
Управляемая форма.
Реализована возможность управлять начальным положением команды в командной панели:
  • Только в меню Еще.
  • Только в командной панели.
  • Одновременно (командная панель и меню Еще).
  • Определить автоматически.

Реализовано свойство кнопки формы ПоложениеВКоманднойПанели.

Свойство кнопки формы ТолькоВоВсехДействиях признано устаревшим и поддерживается только для совместимости. Реализовано автоматическое заполнение свойства ПоложениеВКоманднойПанели на основании свойства ТолькоВоВсехДействиях.

Для кнопки формы клиентского приложения реализована возможность включить режим, когда внутри автоматически заполняемой группы формы будет находиться не более одной кнопки, связанной с одной командой.

Реализовано свойство кнопки клиентского приложения УникальностьКоманды.

Для расширения поля картинки и декорации вида картинка реализовано свойство Масштаб. В режиме совместимости с версией 8.3.6 и ниже свойство игнорируется.

Для команды формы клиентского приложения было доступно только указание на то, что команда располагается или в командной панели или в меню Еще.Улучшены возможности формирования командного интерфейса формы клиентского приложения.
В документации данное изменение описано здесь.
Отображение информации.
В библиотеку картинок добавлены картинки УменьшитьМасштаб, УвеличитьМасштаб.В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.
Управляемая форма.
Для объекта Планировщик реализованы следующие возможности:
  • Возможность управления отображением элементов планировщика при нехватке места в поле: отображать все элементы путем изменения высоты строки или сохранять высоту строки и отображать меню Еще. Реализовано свойство Планировщик.ПоведениеЭлементовПриНедостаткеМеста.
  • Возможность задания минимальной высоты строки и ширины колонки планировщика. В результате вместо постоянного уменьшения элементов планировщика, станет возможно сохранить минимальный размер элемента и добавить полосу прокрутки в том случае, если элементы не помещаются в поле, отведенное планировщику на форме. Для объекта Планировщик реализованы свойства МинимальнаяШиринаКолонки, АвтоМинимальнаяШиринаКолонки, МинимальнаяВысотаСтроки, АвтоМинимальнаяВысотаСтроки.
  • Возможность фиксации заголовка измерений и шкалы времени планировщика. При прокрутке планировщика зафиксированные объекты не будут исчезать из поля видимости пользователя. Для объекта Планировщик реализованы свойства ФиксироватьЗаголовокИзмерений и ФиксироватьЗаголовокШкалыВремени.
Данные возможности не предоставлялись.Расширены возможности планировщика.
В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
Реализована возможность переопределять список выбора пользователей системы взаимодействия при создании сообщения контекстного обсуждения, неконтекстного обсуждения или видеозвонка. Реализована возможность создания формы выбора пользователя системы взаимодействия.

Для объекта ФормаКлиентскогоПриложения и модуля клиентского приложения реализовано событие АвтоПодборПользователейСистемыВзаимодействия.

Для объекта ФормаКлиентскогоПриложения и модуля клиентского приложения реализовано событие ОбработкаПолученияФормыВыбораПользователейСистемыВзаимодействия.

Реализовано свойство конфигурации ОсновнаяФормаВыбораПользователейСистемыВзаимодействия.

Реализована возможность получения идентификатора контекстного обсуждения в форме клиентского приложения (на стороне клиентского приложения). Реализован метод НачатьПолучениеОбсуждения().

Отсутствовала возможность переопределять список выбора пользователей системы взаимодействия во время выбора пользователя.

Идентификатор контекстного обсуждения можно было получить только на стороне сервера.

Расширены возможности работы с системой взаимодействия при выборе пользователей при создании сообщений, обсуждений и видеозвонков.
В документации данное изменение описано здесь, здесь и здесь.
Интерфейс.
Глобальный поиск.
Изменен внешний вид интерфейса Такси. Новый внешний вид включает в себя следующие основные изменения:
  • Основное окно приложения (при работе в ОС Windows) по умолчанию открывается без заголовка окна.
  • Реализована главная панель, содержащая доступ к основным инструментам командного интерфейса системы.
  • Команды панели инструментов перераспределены между другими элементами интерфейса. Панель инструментов более недоступна как отдельная панель.
  • Системная командная панель более недоступна.
  • Изменен состав и расположение главного меню.
  • Изменен вид вспомогательных окон и диалогов.
  • Реализовано поле глобального поиска, отображаемое в главной панели основного окна приложения. Поле глобального поиска недоступно в следующих режимах основного окна приложения: киоск, рабочее место и полноэкранное рабочее место. Поведение поиска может быть настроено с помощью встроенного языка. Реализовано свойство глобального контекста ГлобальныйПоиск. Реализованы события модуля приложения ПриГлобальномПоиске, ПриВыбореРезультатаГлобальногоПоиска.
  • С помощью поля поиска реализована возможность выполнять переход по навигационной ссылке, по URL внешнего ресурса, выполнять арифметические операции и т.д.
  • Реализована команда Искать везде в контекстном меню некоторых элементов формы (где поддерживается выделение). Поиск осуществляется с использованием поля поиска.
  • Реализована кнопка получения навигационной ссылки в заголовке вспомогательного окна.

Реализован метод глобального контекста СтрНайтиИВыделитьОформлением(), позволяющий выделить с помощью оформления некоторые подстроки в строке.

Объект ЭлементНастройкиСоставаИнтерфейсаКлиентскогоПриложения невозможно создать для панели ПанельИнструментов. Панель инструментов игнорируется в составе настроек панелей основного окна приложения.

Для объекта КлиентскоеПриложение реализованы методы ПолучитьОтображениеЗаголовкаОС() и УстановитьОтображениеЗаголовкаОС().

Свойство конфигурации Основная форма поиска признано устаревшим. Вместо него рекомендуется использовать механизм глобального поиска.

Интерфейс Такси имел другой внешний вид.Улучшение навигации по прикладному решению, повышение комфорта использования, развитие в соответствии с современными тенденциями построения интерфейсов.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Табличный документ.
При редактировании колонтитулов табличного документа реализована возможность автоматического расчета размера полей для страницы в том случае, если заданный колонтитул не может быть размещен в текущих размерах полей страницы. Расчет выполняется при нажатии кнопки Ок в форме редактирования колонтитулов и в форме настройки параметров страницы.

Реализована возможность получения размера колонтитула в верхней и нижней части страницы. Реализована возможность получить размер полей страницы.

Для объекта ТабличныйДокумент реализованы методы РассчитатьРазмерКолонтитулаСверху(), РассчитатьРазмерКолонтитулаСнизу(), ПолучитьРазмерПоляПринтераСверху(), ПолучитьРазмерПоляПринтераСнизу(), ПолучитьРазмерПоляПринтераСлева(), ПолучитьРазмерПоляПринтераСправа().

Данная возможность не предоставлялась.

Подобрать размер полей и колонтитула можно было только вручную, итеративным подбором.

Реализована возможность автоматической установки полей страницы табличного документа в соответствии с заданным колонтитулом.
Полнотекстовый поиск.
Реализована возможность поиска по значащим частям слова. В результатах поиска реализована возможность подсветки слова, если в его составе обнаружена значащая часть.

Реализована возможность задавать значащие части слов в пользовательских словарях полнотекстового поиска. Для файла описания пользовательского словаря полнотекстового поиска реализован элемент <Roots>.

Для включения поиска по значащим частям слов необходимо выполнить перестроение индекса полнотекстового поиска.

Данный механизм работает автоматически, если в региональных установках информационной базы выбран русский язык или для информационной базы задан пользовательский словарь полнотекстового поиска со списком значащих частей слов.

Для менеджера полнотекстового поиска реализованы методы ПолучитьРежимРазделенияСоставныхСлов() и УстановитьРежимРазделенияСоставныхСлов().

Данная возможность не предоставлялась.Использование полнотекстового поиска стало более удобным и комфортным.
В документации данное изменение описано здесь, здесь и здесь.
Выгрузка/загрузка конфигурации в файлы.
При необходимости выгрузить информацию о конфигурации (команда пакетного запуска конфигуратора DumpConfigToFiles) в файле с объектами, предназначенными для выгрузки (параметр listFiles команды выгрузки) достаточно указать идентификатор Configuration. При этом имя конфигурации можно не указывать.

+

При необходимости выгрузить информацию о конфигурации (команда пакетного запуска конфигуратора DumpConfigToFiles) в файле с объектами, предназначенными для выгрузки (параметр listFiles команды выгрузки) было необходимо указать идентификатор Configuration и имя конфигурации (через точку).Упрощена работа с выгрузкой конфигурации в файлы XML.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализована возможность блокировать пользователя системы взаимодействия. Заблокированный пользователь не может взаимодействовать с системой взаимодействия. По пользователю системы взаимодействия стало возможно определить связанного пользователя информационной базы.

Для объекта ПользовательСистемыВзаимодействия реализованы свойства Заблокирован и ИдентификаторПользователяИнформационнойБазы. Для менеджера системы взаимодействия реализован метод ПолучитьПользователей().

Стандартная обработка управления системой взаимодействия поддерживает возможность блокировать и разблокировать пользователей системы взаимодействия.

Данные возможности не предоставлялись.Расширены возможности работы с пользователями системы взаимодействия. Стало возможно отключать пользователя от работы в системе взаимодействия, например, в случае увольнения пользователя из компании.
В документации данное изменение описано здесь и здесь.
Отображение информации.
В библиотеку картинок добавлены картинки ДиалогВосклицание, ДиалогВопрос, ДиалогСтоп, ДиалогИнформация.В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Динамический список.
Управляемая форма.
Набор текста в таблице формы, связанной с динамическим списком, не приводит к смене фокуса ввода и началу поиска, при соблюдении следующих условий:
  • На форму выведено дополнение элемента формы Строка поиска.
  • Для таблицы формы свойство Поиск при вводе символов установлено в значение Не использовать.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Набор текста в таблице формы, связанной с динамическим списком, приводил к смене фокуса ввода на строку поиска и начинал поиск, при соблюдении следующих условий:
  • На форму выведено дополнение элемента формы Строка поиска.
  • Для таблицы формы свойство Поиск при вводе символов установлено в значение Не использовать.
Устранено некорректное поведение системы.
Стандартные функции.
Для стандартной функции Активные пользователи кнопка обновления списка перенесена в начало командной панели формы списка.Для стандартной функции Активные пользователи кнопка обновления списка находилась в конце командной панели формы списка.Унифицировано расположение команд обновления списков в различных формах стандартных функций.
Стандартные функции.
Кластер серверов.
Реализована стандартная функция Управление серверами. Данная функция работает аналогично консоли управления кластером. Для своей работы она требует сервер администрирования кластера серверов для всех серверов, которыми требуется управлять. Работа с серверами выполняется с помощью объекта АдминистрированиеСервера. Перечень функциональных отличий стандартной функции от консоли кластера приведен в документации. Системные требования стандартной функции полностью эквивалентны системным требованиям объекта АдминистрированиеСервера.Данная возможность не предоставлялась.

Управление кластером серверов в интерактивном режиме было доступно только из консоли управления кластером.

Интерактивное управление кластером серверов стало возможно не только при работе под управлением ОС семейства Windows. Средства управления кластером доступны в клиентском приложении с помощью диалога Все функции.
Стандартные функции.
История данных.
Реализована стандартная функция, позволяющая просматривать историю данных с установкой произвольного отбора и интерактивным обновлением истории данных.Платформа предоставляла встроенную возможность просмотра истории данных только по конкретному объекту данных. Возможность произвольной настройки отбора для просмотра истории была недоступна.Расширены возможности интерактивной работы с историей данных.
В документации данное изменение описано здесь.
Управляемая форма.
Интерфейс.
Система взаимодействия.
При масштабировании формы, шкала масштабирования отображается в логарифмическом масштабе. При этом значение 100% расположено в середине шкалы.

Реализована возможность использования средней кнопки мыши для:

  • Закрытия элементов состояния поиска (в динамическом списке).
  • Удаления получателей из контекстных обсуждений системы взаимодействия.
  • Удаления вложений из неотправленных сообщений системы взаимодействия.
При масштабировании формы, шкала масштабирования отображалась в линейном масштабе. При этом значение 100% располагалось в начале шкалы.

Закрытие элементов состояния поиска (в динамическом списке), удаление получателей из контекстных обсуждений системы взаимодействия,

удаления вложений из неотправленных сообщений системы взаимодействия можно было выполнять только используя элемент управления у необходимого объекта («крестик» в правой части элемента).

Работа с интерфейсом приложения стала более удобной.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Работа с запросами.
В языке запросов реализована оптимизация вычислений выражений, которые выступают параметрами виртуальных таблиц. Оптимизация полностью эквивалента оптимизации обычных выражений языка запросов.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

В языке запросов отсутствовала оптимизация вычислений выражений, которые выступают параметрами виртуальных таблиц.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа в ОС Linux.
Оптимизировано использование оперативной памяти при работе под управлением ОС Linux.При работе под управлением ОС Linux оперативная память использовалась менее эффективно.Уменьшена фрагментация оперативной памяти и, как следствие, уменьшено количество используемой оперативной памяти при работе под управлением ОС Linux. Незначительно повышена производительность работы системы.
Работа с запросами.
Кластер серверов.
Оптимизировано исполнение запроса, содержащего константные значения в списке выборки. Константные значения, находящиеся в теле запроса, реализуются параметрами запроса. Это приводит к уменьшению количества перекомпиляций планов в СУБД, и как следствие, увеличению производительности таких же запросов, если они отличались только значением константы.Данная возможность не предоставлялась.

Константные значения не выносились параметрами и использовались непосредственно в теле запроса.

В некоторых случаях уменьшено время исполнения запросов, содержащих константные значения. В частности, может уменьшиться время пересчета итогов регистров в клиент-серверном варианте использования системы.
Управляемые блокировки.
Оптимизирована работа менеджера управляемых блокировок при завершении транзакции, если существует большое количество транзакций, которые установили блокировки на диапазона ключа одного пространства.Менеджер управляемых блокировок тратил больше времени на завершение транзакции в том случае, если существует большое количество транзакций, которые установили блокировки на диапазона ключа одного пространства.Повышена параллельность работы в случае однотипной нагрузки, порожденной большим количеством сеансов.
Сравнение/объединение конфигураций.
Оптимизирована операция сравнения/объединения конфигураций.Операция сравнения/объединения конфигураций занимала больше времени.Ускорена операция сравнения/объединения конфигураций.
Работа с запросами.
Если текст запроса содержит условие, в котором принимают участие два константных выражения, и каждое из этих выражений не является строкой, то данное условие будет заменено на результат выражения перед тем, как запрос будет передан на исполнение СУБД.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Не выполнялось упрощение условий, которые состояли из константных выражений.В ряде случаев повышена производительность исполнения запросов.
Двоичные данные.
Сброс буферов, используемых при работе объектов типа ФайловыйПоток, выполняется только при явном выполнении метода ФайловыйПоток.СброситьБуферы().Сброс буферов, используемых при работе объектов типа ФайловыйПоток, выполнялся:
  • При явном выполнении метода ФайловыйПоток.СброситьБуферы().
  • При вызове метода ФайловыйПоток.Закрыть().
  • При уничтожении объекта ФайловыйПоток.
Снижена нагрузка на дисковый накопитель при интенсивной работе с объектами типа ФайловыйПоток.
Система компоновки данных.
Оптимизирована работа функции Значение() языка выражений системы компоновки данных. Функция Значение() языка выражений системы компоновки данных работала с меньшей скоростью.Ускорена работа функции Значение() языка выражений системы компоновки данных.
Работа с СУБД.
Работа с запросами.
При исполнении запроса, ускорено создание временной таблицы из таблицы значений, переданной в качестве параметра запроса.При исполнении запроса, создание временной таблицы из таблицы значений, переданной в качестве параметра запроса, занимало больше времени.Ускорено создание временной таблицы на основании таблицы значений с помощью языка запросов.
Установка клиентского приложения.
Системные требования.
Из состава дистрибутива тонкого клиента (для работы под управлением ОС Windows) удален распространяемый пакет Microsoft VC++ Runtime.В состав дистрибутива тонкого клиента (для работы под управлением ОС Windows) входил распространяемый пакет Microsoft VC++ Runtime.Уменьшен размер дистрибутива тонкого клиента для работы под управлением ОС Windows.
Системные требования.
Из состава дистрибутива платформы (для работы под управлением ОС Windows) удален пакет Microsoft Windows Installer 3.0.В состав дистрибутива платформы (для работы под управлением ОС Windows) входил пакет пакет Microsoft Windows Installer 3.0.Уменьшен размер дистрибутива платформы для работы под управлением ОС Windows.
Система компоновки данных.
Компоновщик макета системы компоновки данных считает задействованными поля, использующиеся в элементе условного оформления компоновки данных только тогда, когда этот элемент условного оформления применяется как минимум к одному из выводимых полей (в том числе и при применении условного оформления ко всем полям). Если элемент условного оформления ни к одному полю не применяется, то поля, которые в нем задействованы считаются не используемыми и не добавляются в результирующий запрос макета компоновки данных.

В результате в запрос получения данных не добавляются поля, которые не используются в условном оформлении.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Компоновщик макета системы компоновки данных считал задействованными все поля, которые есть в элементе условного оформления, даже если этот элемент условного оформления не применялся ни к одному полю.

В запрос получения данных помещались все поля, которые формально участвовали в условном оформлении.

Оптимизировано формирование запроса получения данных системы компоновки данных.
В документации данное изменение описано здесь.
Работа с запросами.
Если в запросе с объединениями обнаруживается заведомо ложное условие, то та часть объединения, где обнаружено ложное условие, не будет передаваться на исполнение в СУБД. Обнаружение заведомо ложных условий используется только для данных типа Число или перечисление.

При оптимизации объединения, платформа может, при необходимости, добавить в результирующий запрос требование получения различных записей.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Данная возможность не предоставлялась.В ряде случаев будет уменьшено время выполнения запросов.
Кластер серверов.
Оптимизирован механизм переноса клиентских соединений на новый рабочий процесс во время автоматического перезапуска рабочего процесса.Механизм переноса клиентских соединений на новый рабочий процесс во время автоматического перезапуска рабочего процесса занимал существенно больше времени.Существенно уменьшено время переноса существующих сеансов на новый рабочий процесс. Снижена (вплоть до полного исчезновения) задержка в работе клиентского приложения во время переноса. Существенно улучшена интерактивность клиентского приложения в этой ситуации.
В документации данное изменение описано здесь.
Регистры бухгалтерии.
Ускорена работа с виртуальными таблицами регистра бухгалтерии, обновление итогов при записи движений по регистру и пересчет итогов регистра бухгалтерии.

При этом увеличивается объем хранимых данных и незначительно увеличивается время сохранения набора записей.

Для того, чтобы ускорение работы с регистром бухгалтерии стало заметно, необходимо отключить режим совместимости. При этом будет выполнена реструктуризация регистров бухгалтерии. В том случае, если размер информационной базы превышает 10 Гбайт, рекомендуется для реструктуризации использовать оптимизированный механизм обновления конфигурации базы данных.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Работа с виртуальными таблицами регистра бухгалтерии, обновление итогов при записи движений по регистру и пересчет итогов регистра бухгалтерии занимали больше времени.Ускорено получение данных из регистров бухгалтерии.
Регистры бухгалтерии.
Работа с запросами.
Ускорено выполнение запроса к регистру бухгалтерии в том случае, если запрос содержит условие на попадание регистратора в некоторый список, формирующийся подзапросом: Регистратор В (подзапрос).

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Запроса к регистру бухгалтерии в том случае, если запрос содержит условие на попадание регистратора в некоторый список, формирующийся подзапросом: Регистратор В (подзапрос), работал недостаточно быстро.В некоторых случаях ускорено получение данных из регистра бухгалтерии.
Работа с запросами.
Если в файловом варианте информационной базы выполняется запрос, в котором выбираются данные из двух таблиц, эти таблицы связаны внутренним соединением и есть индексы по полям связи в обеих таблицах, то первой будет выполняться обход той таблицы, где меньше записей.При выполнении в файловом варианте информационной базы запроса, в котором выбираются данные из двух таблиц, эти таблицы связаны внутренним объединением и есть индексы по полям связи в обеих таблицах, не анализировалось количество записей в таблицах.В ряде случаев повышена производительность работы запроса в файловом варианте информационной базы.
Система компоновки данных.
Оптимизирован процесс компоновки макета системы компоновки данных в том случае, если запрос схемы компоновки данных содержит большое количество объединений (400 и более объединений).Процесс компоновки макета системы компоновки данных в том случае, если запрос схемы компоновки данных содержит большое количество объединений (400 и более объединений), занимал существенное время.Повышена производительность исполнения системы компоновки данных при большом количестве объединений в запросе схемы компоновки данных.
Кластер серверов.
Работа с СУБД.
При работе с использованием СУБД PostgreSQL, оптимизировано выполнение проведения больших документов по регистру бухгалтерии, а также использование виртуальной таблицы ДвиженияССубконто.Выполнение проведения больших документов по регистру бухгалтерии, а также использование виртуальной таблицы ДвиженияССубконто занимало больше времени при использованием СУБД PostgreSQL.Оптимизировано использование регистра бухгалтерии при работе с использованием СУБД PostgreSQL.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Система компоновки данных.
Если в выражении системы компоновки данных тип одного из операндов является произвольным, то и результирующее выражение будет иметь произвольный тип.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Если в выражении системы компоновки данных участвует значение с произвольным типом, то при вычислении типа результирующего выражения произвольный тип игнорировался.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Интерфейс.
В интерфейсе клиентского приложения изменены картинки ( в том числе в библиотеке картинок) для команд табличного документа, отвечающих за сворачивание и разворачивание всех групп.В интерфейсе клиентского приложения картинки ( в том числе в библиотеке картинок) для команд табличного документа, отвечающих за сворачивание и разворачивание всех групп выглядели по-другому.Картинки команд табличного документа, отвечающие за сворачивание и разворачивание всех групп табличного документа, стали лучше соответствовать выполняемым действиям.
Средства разработки.
В редакторе формы, свойство Действие команды заимствованной формы содержит имя метода, который является обработчиком команды в расширяемой конфигурации. Переход к обработчику команды недоступен.В редакторе формы, свойство Действие команды заимствованной формы содержит имя метода, который является обработчиком команды в расширяемой конфигурации. Переход к обработчику команды приводил к ошибке.Устранено некорректное поведение системы.
Работа с запросами.
Операция языка запросов ВЫБОР будет считаться константой и заменяться на константу, если все ветки операции содержат только константные выражения. Как следствие, операцию ВЫБОР можно будет использовать в константных параметрах виртуальных таблиц, при условии, что все ветки операции ВЫБОР содержат только константные выражения.

Если операнд операции ВЫБОР в итогах запроса содержит NULL, то результатом операции будет значение, указанное в разделе ИНАЧЕ или NULL, если его нет.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Операция языка запросов ВЫБОР не заменялась на константу и не могла использоваться в константных параметрах виртуальных таблиц. При расчете операции ВЫБОР в итогах запроса, если операнд операции содержал NULL, то результатом операции NULL.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Реализована возможность изменения свойств элементов формы клиентского приложения без обращения к серверу:
  • Декорация:
    • Заголовок,
    • ЦветТекста.
  • Расширение надписи для декорации:
    • Гиперссылка,
    • ГоризонтальноеПоложение,
    • ВертикальноеПоложение.
  • Расширение группы формы для командной панели:
    • ГоризонтальноеПоложение.
  • Расширение группы формы для страницы:
    • Группировка.
  • Расширение группы формы для обычной группы:
    • Группировка.
  • Кнопка
    • Картинка,
    • ПоложениеВКоманднойПанели (кроме веб-клиента),
    • Ширина,
    • АвтоМаксимальнаяШирина,
    • МаксимальнаяШирина,
    • Высота,
    • АвтоМаксимальнаяВысота,
    • МаксимальнаяВысота,
    • Заголовок,
    • Шрифт,
    • ВертикальноеПоложениеВГруппе,
    • ГоризонтальноеПоложениеВГруппе,
    • РастягиватьПоВертикали,
    • РастягиватьПоГоризонтали,
    • Фигура,
    • ОтображениеФигуры,
    • ПоложениеКартинки,
    • КнопкаПоУмолчанию.
  • Расширение поля формы для поля картинки:
    • Ширина,
    • МаксимальнаяШирина,
    • Высота,
    • МаксимальнаяВысота,
    • РастягиватьПоВертикали,
    • РастягиватьПоГоризонтали,
    • КартинкаЗначений.
Данная возможность не предоставлялась. Обращение к указанным свойствам элементов формы клиентского приложения требовало обращения к серверу.Уменьшено клиент-серверное взаимодействие при управлении формой клиентского приложения из встроенного языка.
Система взаимодействия.
В интерфейсе системы взаимодействия реализованы следующие возможности:
  • При редактировании сообщения курсор устанавливается в конец текста сообщения.
  • При отправке сообщения удаляются концевые пробелы в сообщении.
  • Карточка пользователя системы взаимодействия открывается при нажатии левой кнопки мыши на картинке пользователя.
  • Отметка непрочитанности с обсуждения снимается при выполнении любого из следующих действия:
    • Нажатие левой кнопки мыши на ссылку в сообщении.
    • Нажатие левой кнопки мыши на имени или картинке пользователя.
    • Нажатие левой кнопки мыши на вложении в сообщении.
    • Нажатие левой кнопки мыши на действие сообщения.
    • Нажатие правой кнопки мыши (открытие контекстного меню).
  • При первом открытии основной формы системы взаимодействия не активизируется первое обсуждение.
  • В тонком и толстом клиентских приложениях выбор оповещения в центре оповещений можно осуществлять нажатием на картинку сообщения. В веб-клиенте поведение не изменилось.

Изменена стандартная картинка группы пользователей в выпадающем списке подбора пользователей.

В интерфейсе системы взаимодействия наблюдалось другое поведение:
  • При редактировании сообщения курсор не устанавливался в конец сообщения.
  • При отправке сообщения удалялись лидирующие и концевые пробелы.
  • Карточка пользователя открывалась при нажатии левой кнопки мыши по имени пользователя.
  • При первом открытии основной формы системы взаимодействия активировалось первое обсуждение.
  • В тонком и толстом клиентских приложениях выбор оповещения в центре оповещений можно было выполнить только нажатие левой кнопки мыши на текст сообщения. В веб-клиенте выбор осуществлялся при нажатии на текст и на картинку сообщения.
Улучшен пользовательский интерфейс системы взаимодействия.
Система компоновки данных.
Команды Сформировать, Печать, Сохранить, Компактный режим будут добавлены в командную панель формы отчета (с установленным признаком автоматического заполнения) в том случае, если задано свойство формы отчета Результат отчета. Если свойство формы отчета Результат отчета не задано, то команды Сформировать, Печать, Сохранить, Компактный режим не будут добавлены в автоматически заполняемую командную панель формы отчета.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Команды Сформировать, Печать, Сохранить, Компактный режим всегда добавлялись в командную панель формы отчета с установленным признаком автоматического заполнения.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Если в настройках диаграммы для представления чисел явно не задан формат, то к числам будет применяться формат по умолчанию (учитывающий региональные настройки информационной базы).

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Если в настройках диаграммы для представления чисел явно не задан формат, то к числам не применялось никакого специального форматирования.Устранено некорректное поведение системы.
Управляемая форма.
Если поле ввода находится в режиме выбора из списка, то поиск значения выполняется следующим образом:
  • Вначале выполняется поиск в представлениях по началу строки, в том случае, если представление задано явно.
  • Затем выполняется поиск в зависимости от типа значения списка:
    • Для чисел - выполняется поиск по началу строки в строковом представлении числа, сформированном без форматирования (т.е. без разделителей групп). При этом для разделителя дробной части допускается использовать символы точки и запятой.
    • Для дат - выполняется поиск по началу строки в строковом представлении даты. При этом для разделителей частей даты допускается использование символов точки, тире и прямого слеша. Выполняется автодополнение числа и месяца лидирующими нулями, а года - до полной длины (состоящего из 4 символов).
    • Для остальных типов - выполняется поиск по началу строки в строковом представлении значения.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Если поле ввода находится в режиме выбора из списка, то для всех типов поиск выполнялся по началу строки в заданном представлении или, если представление было не задано, в строковом представлении значений из списка выбора.Поиск в полях ввода, использующих список выбора, стал более предсказуем и лучше соответствует ожиданиям пользователя.
Система взаимодействия.
В системе взаимодействия реализована возможность управлять количеством получаемых уведомлений для контекстных и неконтекстных обсуждений. Предоставляется возможность совсем отказаться от получения уведомлений по какому-то обсуждению, получать уведомления только для тех сообщений, которые адресованы пользователю или получать оповещения обо всех сообщениях.

Настройка это возможности возможна как с помощью пользовательского интерфейса, так и с помощью встроенного языка.

Реализована возможность использовать методы ПолучитьРежимНаблюдения() и УстановитьРежимНаблюдения() для неконтекстных обсуждений. Для методов ПолучитьРежимНаблюдения() и УстановитьРежимНаблюдения() реализован параметр Пользователь.

Для менеджера системы взаимодействия реализован методы УстановитьОтображениеОповещенийОбсуждения() и ПолучитьОтображениеОповещенийОбсуждения().

При работе с системой взаимодействия предоставлялась возможность только полностью отказать от получения оповещений.

Методы ПолучитьРежимНаблюдения() и УстановитьРежимНаблюдения() использовались только для контекстных обсуждений.

Расширены возможности интерфейса системы взаимодействия.
В документации данное изменение описано здесь.
Управляемые блокировки.
Система взаимодействия.
В клиентском приложении (тонкий, толстый и веб-клиент) реализована возможность снимать объектную блокировку, установленную другим пользователем или этим же пользователем, но в другом сеансе. Под «объектной блокировкой» понимается блокировка, установленная интерактивно, при редактировании объекта в форме или методами Заблокировать(), ЗаблокироватьДанныеДляРедактирования(), ЗаблокироватьДанныеФормыДляРедактирования().

При обнаружении блокировки реализована возможность начать обсуждение с инициатором блокировки по системе взаимодействия (если информационная база подключена к системе взаимодействия).

Данная возможность не предоставлялась.Упрощена работа с данными информационной базы в ряде случаев.
В документации данное изменение описано здесь.
Интерфейс.
Для диалоговых окон, которые формируются методами встроенного языка Вопрос(), ПоказатьВопрос(), Предупреждение(), ПоказатьПредупреждение() (во всех клиентских приложениях и интерфейсах Версия 8.2 и Такси) реализовано следующее:
  • Изменен внешний вид диалоговых окон.
  • Если для диалога не указан заголовок (в соответствующем параметре метода), то диалог открывается без заголовка.
  • При создании диалоговых окон учитывается масштабирование, установленное для всех форм в интерфейсе Такси.
  • Изменены картинки, отображаемые в соответствующих диалогах при работе в интерфейсе Такси.
Диалоговые окна, которые формируются методами встроенного языка Вопрос(), ПоказатьВопрос(), Предупреждение(), ПоказатьПредупреждение(), имели другой внешний вид и не учитывали масштабирование форм в интерфейсе Такси.Улучшен внешний вид диалоговых окон, формируемых методами встроенного языка Вопрос(), ПоказатьВопрос(), Предупреждение(), ПоказатьПредупреждение().
Табличный документ.
Ориентация текста, заданная для области ячеек табличного документа, учитывается при выводе текста в том случае, если в качестве шрифта выбран системный шрифт Windows.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

В том случае, если в качестве шрифта области ячеек табличного документа выбран системный шрифт Windows, ориентация текста, заданная для области ячеек табличного документа, не учитывалась при выводе текста.Устранено некорректное поведение системы.
Система компоновки данных.
Реализована возможность применения условного оформления колонки таблицы отчета системы компоновки данных ко всей колонке, в том случае, если для элемента условного оформления выбрана область использования В группировке, В иерархической группировке или <Везде>.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Если при оформлении колонки таблицы отчета системы компоновки данных для элемента условного оформления выбрана область использования В группировке, В иерархической группировке или <Везде>, то оформление задавалось только для заголовка таблицы и итога по колонке.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Если форма клиентского приложения содержит один из следующих элементов: поле табличного документа, поле текстового документа, поле графической схемы, поле HTML-документа, поле форматированного документа, поле географической схемы или поле планировщика, то в заголовке формы формируется подменю, содержащее команды Печать, Сохранить и Предварительный просмотр. Если вышеуказанных элементов на форме более одного, то команды меню действуют для текущего элемента указанного вида.

В веб-клиенте команда предварительного просмотра не отображается.

Данная возможность не предоставлялась.Работа с формой стала более удобной.
Работа в macOS.
Внешние компоненты корректно работают в тонком клиенте (под управлением ОС macOS) и веб-браузере Safari. Доработок внешних компонент не требуется.Внешние компоненты некорректно работали в веб-браузере Safari, но корректно работали в тонком клиенте (под управлением ОС macOS).Устранено некорректное поведение системы.
Работа с запросами.
Следующие функции языка запросов могут использоваться в качестве параметров виртуальных таблиц, принимающих только константные значения: ПОДСТРОКА(), ГОД(), КВАРТАЛ(), МЕСЯЦ(), ДЕНЬГОДА(), ДЕНЬ(), НЕДЕЛЯ(), ДЕНЬНЕДЕЛИ(), ЧАС(), МИНУТА(), СЕКУНДА(). Использование возможно в том случае, если в указанных функциях все параметры содержат константные значения параметров. В этом случае в качестве значения параметра подставляется вычисленное значение функции.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Следующие функции языка запросов в любом случае не могли использоваться в качестве параметров виртуальных таблиц, принимающих только константные значения: ПОДСТРОКА(), ГОД(), КВАРТАЛ(), МЕСЯЦ(), ДЕНЬГОДА(), ДЕНЬ(), НЕДЕЛЯ(), ДЕНЬНЕДЕЛИ(), ЧАС(), МИНУТА(), СЕКУНДА().Стало возможно использование функций работы с датой/временем в качестве параметров, принимающих только константные значения, виртуальных таблиц регистров в языке запросов. Такое использование допустимо только в том случае, если функции содержат в качестве параметров константные значения.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность редактирования (как интерактивно, так и с помощью встроенного языка) параметров страницы табличного документа, который преобразован в компактный режим.

Для компактного табличного документа реализована возможность вызова метода УстановитьРастягиваниеПоГоризонтали().

При редактировании компактного табличного документа изменяется как компактный, так и оригинальный табличный документ.

Компактный табличный документ не поддерживал возможность настраивать параметры страницы.Настройки параметров табличного документа для печати и просмотра стали более логичными.
Управляемая форма.
В форме или группе формы вида Обычная или Страница с установленной горизонтальной группировкой и свойстве ГоризонтальноеПоложениеПодчиненных установленным в значение Лево, Центр или Авто (которое интерпретируется как Лево или Центр), вправо выравниваются все последние элементы формы или группы, для которых значение свойства ГоризонтальноеПоложениеВГруппе установлено в значение Право, вплоть до элемента, у которого значение свойства ГоризонтальноеПоложениеВГруппе не равно Право.

В форме или группе формы вида Обычная или Страница с установленной горизонтальной группировкой и свойстве ВертикальноеПоложениеПодчиненных установленным в значение Верх, Центр или Авто (которое интерпретируется как Верх или Центр), вниз выравниваются все последние элементы формы или группы, для которых значение свойства ВертикальноеПоложениеВГруппе установлено в значение Низ, вплоть до элемента, у которого значение свойства ВертикальноеПоложениеВГруппе не равно Низ.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

В форме или группе формы вида Обычная или Страница с установленной горизонтальной группировкой и свойстве ГоризонтальноеПоложениеПодчиненных установленным в значение Лево, Центр или Авто (которое интерпретируется как Лево или Центр), вправо выравнивался только один, последний элемент в форме или группе.

В форме или группе формы вида Обычная или Страница с установленной горизонтальной группировкой и свойстве ВертикальноеПоложениеПодчиненных установленным в значение Верх, Центр или Авто (которое интерпретируется как Верх или Центр), вниз выравнивался только последний элемент формы или группы.

Устранено некорректное поведение системы.
Сборщик мобильных приложений.
Реализован механизм очистки каталога кеша сборщика мобильных приложений. Из каталога удаляются артефакты, которые размещены в каталоге кеша более, чем 30 дней назад. Также удаляются временные каталоги сборки, которые остались после время аварийного завершения или прерывания сборки.

Механизм не требует настройки и работает в полностью автоматическом режиме.

Кеш сборщика мобильных приложений мог только увеличиваться в размерах. В сборщике мобильных приложений не было предусмотрено механизма очистки неиспользуемых артефактов, размещенных в кеше.Прекращен неконтролируемый рост размера каталога кеша мобильных приложений. Сборщик оставляет в кеше только те артефакты, которые использовались в процессе сборки за последние 30 дней.
Полнотекстовый поиск.
Кластер серверов.
Количество слов в поисковой строке полнотекстового поиска не может превышать 1 000 слов. При превышении генерируется ошибка. Служебные слова и поисковые операторы при подсчете количества слов не учитываются.Количество слов в поисковой строке полнотекстового поиска было неограниченно. Указание очень большого количества слов в поиске могло приводить к существенному снижению производительности работы кластера серверов.Повышена стабильность работы системы. Снижена вероятность негативно повлиять на отзывчивость системы в целом указанием очень большой строки полнотекстового поиска.
В документации данное изменение описано здесь.
Работа с базой данных.
При обновлении конфигурации базы данных усилена проверка целостности базы данных. В частности, более невозможна ситуация, когда несколько таблиц базы данных получают одинаковый внутренний номер. В этой ситуации генерируется ошибка и обновление базы данных не выполняется.При обновлении конфигурации базы данных не выполнялся контроль уникальности внутренних номеров таблиц базы данных. В результате, при эксплуатации информационной системы могли наблюдаться различные, труднообъяснимые ошибки.Устранено некорректное поведение системы.
Работа с файлами.
Если тонкий клиент подключается к информационной базе через веб-сервер, с использованием протокола HTTPS, то при использовании методов ПолучитьФайл(), ПолучитьФайлы(), НачатьПолучениеФайлов(), НачатьПолучениеФайлаССервера() и НачатьПолучениеФайловССервера() больше не требуется повторная аутентификация на веб-сервере.Если тонкий клиент подключается к информационной базе через веб-сервер, с использованием протокола HTTPS, то при использовании методов ПолучитьФайл(), ПолучитьФайлы(), НачатьПолучениеФайлов(), НачатьПолучениеФайлаССервера() и НачатьПолучениеФайловССервера() требовалась повторная аутентификация на веб-сервере.Устранено незапланированное поведение системы.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Система компоновки данных.
Компоновщик макета компоновки данных, при формировании выражения групповых и итоговых записей для вычисляемых полей, являющихся ресурсами, не использует выражение представления, указанное у вычисляемого поля. Таким образом, выражение представления для вычисляемых полей, являющихся ресурсами, будет выдаваться в отчет только в детальных записях.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Компоновщик макета компоновки данных, использовал выражение представления вычисляемого поля являющегося ресурсом в детальных, групповых и итоговых записях.Поведение компоновщика макета компоновки данных стало одинаковым при работе с вычисляемыми полями, полями наборов данных и вычисляемыми полями-ресурсами.
В документации данное изменение описано здесь.
Работа с запросами.
Система компоновки данных.
При обработке текста запроса конструктором запроса, схемой запроса, системой компоновки данных и построителем отчета не выполняется автоматическая замена правых соединений на аналогичные левые соединения.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

При обработке текста запроса конструктором запроса, схемой запроса, системой компоновки данных и построителем отчета выполнялась автоматическая замена правых соединений на аналогичные левые соединения. Если конвертацию выполнить не получалось - соединение удалялось из запроса.Устранено поведение системы, которое могло приводить к некорректному запросу.
В документации данное изменение описано здесь.
Работа с файлами.
Веб-клиент.
Реализованы методы глобального контекста НачатьПолучениеФайлаССервера(), НачатьПолучениеФайловССервера(). В интерактивном режиме, при работе в веб-клиенте, методы не требуют установки расширения работы с файлами. Реализована возможность получить несколько файлов с сервера в виде архива.

Метод НачатьЗапросРазрешенияПользователя() позволяет запрашивать разрешение пользователя для новых методов.

Методы ПолучитьФайл(), НачатьПолучениеФайлов(), ЗапроситьРазрешениеПользователя() являются устаревшими, не рекомендуются к использованию и поддерживаются для совместимости.

Рекомендуется, по мере возможности, переводить прикладные решения на использование новых методов.

Существующие методы получения файлов с сервера были не логичными. Метод получения нескольких файлов с сервера (НачатьПолучениеФайлов()) в веб-клиенте требовал расширение работы с файлами.Получение файлов с сервера стало более простым и логичным. Для интерактивной работы в веб-клиенте больше не требуется использование расширения работы с файлами.
В документации данное изменение описано здесь.
Работа с файлами.
Веб-клиент.
Реализованы методы глобального контекста НачатьПомещениеФайлаНаСервере(), НачатьПомещениеФайловНаСервере(). В интерактивном режиме, при работе в веб-клиенте, методы не требуют установки расширения работы с файлами. Реализована возможность отображения прогресса помещения файла на сервер. Реализована возможность отказаться от помещения файла на сервер. Реализована возможность выполнить одновременную передачу на сервер нескольких файлов с клиентского компьютера, при этом передаваемые файлы задаются строкой поиска файлов.

Метод НачатьЗапросРазрешенияПользователя() позволяет запрашивать разрешение пользователя для новых методов.

Методы НачатьПомещениеФайла(), НачатьПомещениеФайлов(), ЗапроситьРазрешениеПользователя() являются устаревшими, не рекомендуются к использованию и поддерживаются для совместимости.

Рекомендуется, по мере возможности, переводить прикладные решения на использование новых методов.

Существующие методы передачи файлов на сервер (НачатьПомещениеФайла(), НачатьПомещениеФайлов()) не позволяли отменить помещение файлов во время передачи и не позволяли отображать прогресс передачи.Помещение файлов на сервер стало более простым и логичным. Для интерактивной работы в веб-клиенте больше не требуется использование расширения работы с файлами.
В документации данное изменение описано здесь и здесь.
Работа с базой данных.
Общие реквизиты / Разделение данных.
Встроенный язык.
Метод НайтиПомеченныеНаУдаление() будет выполнять поиск среди всех доступных объектов текущей области данных только в том случае, если значение Неопределено передано в качестве значения первого и второго параметров метода.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Метод НайтиПомеченныеНаУдаление() выполнял поиск среди всех доступных объектов текущей области данных только в том случае, если значение Неопределено передано в качестве значения только первого параметра метода.Унифицирован набор параметров и поведение методов, выполняющих похожие действия.
Работа с запросами.
Изменяется поведение языка запросов в том случае, если: запрос представляет собой объединение нескольких запросов, применяется упорядочивание к объединенному запросу и в каждом запросе объединения используется модификатор ПЕРВЫЕ. В этом случае каждый запрос в объединении превращается во вложенный запрос с упорядочиванием. Если в каком-либо из вложенных запросов нет модификатора ПЕРВЫЕ, то подзапрос упорядочиванием не строится.

Рекомендуется проанализировать случаи использования запросов, попадающих под такие условия. При отключении режима совместимости результат исполнения таких запросов может отличаться от результата исполнения этого же запроса в режиме совместимости.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Поведение языка запросов в том случае, если: запрос представляет собой объединение нескольких запросов, применяется упорядочивание к объединенному запросу и в каждом запросе объединения используется модификатор ПЕРВЫЕ, зависело от варианта информационной базы:
  • Для файлового варианта: сначала производилось упорядочивание, затем выборка первых записей.
  • Для клиент-серверного варианта: сначала производилась выборка первых (для каждого простого запроса). При этом упорядочивание в рамках простых запросов не производилось. Упорядочивание выполнялось только для результата объединения. При этом повторяемость результата не гарантировалась, т.к. выборка первых элементов происходила из запроса без упорядочивания.
Реализовано одинаковое поведение запроса, содержащего объединение, упорядочивание и модификатор ПЕРВЫЕ, в различных вариантах работы информационной базы.
Кластер серверов.
При редактировании счетчика потребления ресурсов кластера серверов очистка счетчика происходит только при изменении свойства Группировка.

Реализована возможность очистки экземпляра счетчика потребления ресурсов:

  • В консоли кластера реализована команда Удалить для экземпляра счетчика потребления ресурсов.
  • Для команды rac counter реализована команда clear.
  • Для Java-интерфейса управления кластером серверов реализован метод IAgentAdminConnection.clearAccumulatedValues().
  • Во встроенном языке реализован метод АдминистрированиеСчетчикПотребленияРесурсов.ОчиститьНакопленныеЗначения().

Реализована возможность получения списка значений счетчика потребления ресурсов:

  • Для команды rac counter реализована команда accumalated-values.
  • Для Java-интерфейса управления кластером серверов реализован метод IAgentAdminConnection.getAccumulatedResourceConsumptionCounterValues().
  • Во встроенном языке реализован метод АдминистрированиеСчетчикПотребленияРесурсов.ПолучитьНакопленныеЗначения().

Для экземпляра счетчика потребления ресурсов реализовано поле, хранящее время данного измерения. Для получения времени измерения:

  • В выводе команды rac counter реализовано свойство time.
  • Для Java-интерфейса управления кластером серверов реализован метод IresourceConsumptionCounterValue.getTime().
  • Во встроенном языке реализовано свойство АдминистрированиеЗначениеСчетчикаПотребленияРесурсов.Время.
При редактировании счетчика потребления ресурсов кластера серверов очистка счетчика происходила при любом редактировании свойств счетчика.

Остальные возможности не предоставлялись.

Улучшен механизм управления потреблением ресурсов кластера серверов. Упрощена настройка счетчиков и ограничений потребления ресурсов. Предоставлена возможность анализа изменения накопленных данных.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Функциональные опции.
В системе компоновки данных для поля, которое получается «через точку» от поля временной таблицы или вложенного запроса, проверка доступности включает проверку того, что поле не отключено функциональной опцией.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

В системе компоновки данных для поля, которое получается «через точку» от поля временной таблицы или вложенного запроса, проверка доступности не включала проверку того, что поле не отключено функциональной опцией. Если поле временной таблицы или вложенного запроса было доступно, то считалось, что все поля, доступные «через точку», также будут доступными.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
План видов характеристик.
В системе компоновки данных учитывается тип значения характеристики при получении значения характеристики (для любых целей, например сортировки или отбора по ней). Если в информационной базе записано значение, не соответствующе типу значения используемой характеристики, то вместо него будет использоваться NULL.

Рекомендуется проанализировать использование дополнительных характеристик в системе компоновки данных и убедиться, что фактический тип значения характеристики соответствует типу.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

В системе компоновки данных не учитывается тип значения характеристики при получении значения характеристики (для любых целей, например сортировки или отбора по ней). Даже если в информационной базе записано значение не соответствующее типу значения используемой характеристики, оно будет использовано.Оптимизирована работа системы компоновки данных дополнительными характеристиками (планами видов характеристик) за счет сокращения количества таблиц, используемых в запросах.
В документации данное изменение описано здесь.
Кластер серверов.
Изменены правила и настройки системы мониторинга кластера серверов «1С:Предприятия». Оптимизировано использование оперативной памяти сервера. В частности, при определении объема используемой памяти используются не только параметры рабочих процессов, но и параметры менеджеров кластера.

Для кластера серверов реализована настройка, позволяющая указать необходимость создавать дамп процесса при превышении критического объема памяти.

Для рабочего сервера реализованы свойства, описывающие временно допустимый объем памяти процессов, интервал времени, описывающий длительность превышения допустимого объема памяти процессов, критический объем памяти процессов.

Из свойств кластера удалены настройки:

  • Допустимый объем памяти.
  • Интервал превышения допустимого объема памяти.
  • Допустимое отклонение количества ошибок сервера.

Из свойств рабочего процесса удалены настройки, описывающие объем памяти рабочих процессов, до которого сервер считается производительным, максимальный объем памяти рабочих процессов.

Удаленные параметры, тем не менее, будут сохранены в настройках кластера и будут использоваться при установке предыдущей версии платформы «1С:Предприятие».

При создании нового кластера некоторые параметры будут иметь следующие значения по умолчанию:

  • Принудительно завершать проблемные процессы - включен.
  • Проблемные процессы завершать через 60 секунд.

При создании нового рабочего сервера, по умолчанию будет установлено 256 соединений на один процесс.

Если настройках кластера изменялись удаленные параметры - рекомендуется пересмотреть настройки кластера и при необходимости скорректировать их.

Реализованы:

  • Свойство АдминистрированиеКластер.ЗаписыватьДампПриЗавершенииПоПревышениюПамяти.
  • Свойства для объекта КритическийОбъемПамятиПроцессов, ВременноДопустимыйОбъемПамятиПроцессов и ПериодПревышенияВременноДопустимогоОбъемаПамятиПроцессов для объекта АдминистрированиеРабочийСервер.
  • Свойство IClusterInfo.KillByMemoryWithDump.
  • Свойства CriticalProcessesTotalMemory, TemporaryAllowedProcessesTotalMemory, TemporaryAllowedProcessesTotalMemoryTimeLimit для объекта IWorkingServerInfo.

В интерфейсе работы с сервером администрирования из языка Java реализовано:

  • Методы isClusterRecyclingKillByMemoryWithDump() и setClusterRecyclingKillByMemoryWithDump() интерфейса IClusterInfo.
  • Методы getCriticalProcessesTotalMemory(), setCriticalProcessesTotalMemory(), getTemporaryAllowedProcessesTotalMemory(), setTemporaryAllowedProcessesTotalMemory(), getTemporaryAllowedProcessesTotalMemoryTimeLimit(), setTemporaryAllowedProcessesTotalMemoryTimeLimit() интерфейса IWorkingServerInfo.

Для утилиты командной строки (rac) кластера серверов:

  • Для вывода команды cluster info реализовано поле kill-by-memory-with-dump.
  • Для команд cluster update и cluster insert реализован параметр kill-by-memory-with-dump.
  • Для команд server insert и server update реализованы параметры командной строки critical-total-memory, temporary-allowed-total-memory и temporary-allowed-total-memory-time-limit.

Следующие свойства объявляются устаревшими и поддерживаются для совместимости и взаимодействия с кластером прежних версий:

  • Свойства ОграничениеПоПамятиПроцесса, МаксимальныйПериодПревышенияПамяти, ОграничениеПоКоличествуОшибокПроцесса объекта АдминистрированиеКластер.
  • Свойства MaxMemorySize, MaxMemoryTimeLimit, ErrorsCountThreshold объекта IClusterInfo.
Логика мониторинга кластера серверов была другой. При определении объема используемой оперативной памяти использовались параметры только рабочих процессов. По умолчанию предлагалось не более 128 соединений на один процесс.Оптимизировано использование оперативной памяти кластером серверов.
В документации данное изменение описано здесь, здесь и здесь.
Кластер серверов.
Переработан механизм балансировки нагрузки при создании нового соединения с кластером серверов. Изменен алгоритм оценки производительности рабочего процесса.Механизм балансировки нагрузки недостаточно хорошо обрабатывал некоторые ситуации. В частности, наблюдалось неоптимальная загрузка рабочих процессов, процесс перераспределения нагрузки занимал длительное время.Новые соединения будут более равномерно использовать доступные ресурсы. Ускорится перераспределение нагрузки между серверами кластера. Улучшена балансировка нагрузки при массовых подключениях/отключениях пользователей к кластеру серверов.
В документации данное изменение описано здесь.
История данных.
В форме различия версий отображается информация о перемещенных строках в табличных частях объектов. Отображается номер строки до и после перемещения.

В результате вызова метода ПолучитьРазличиеВерсий() будет содержаться следующая информация для перемещенной строки:

  • Свойство НомерСтрокиВВерсииПослеИзменения - номер «новой» строки (после перемещения).
  • Свойство НомерСтрокаВВерсииДоИзменения - номер «старой» строки (до перемещения).
В форме различия версий номер строки после изменения корректировался с учетом действий, выполняемых между первым и вторым действием перемещения, номер строки до изменения содержал номер строки в версии после изменения.Устранено некорректное поведение системы.
История данных.
При работе с историей данных реализована возможность выполнения действий после того, как будет записана версия данных. Реализовано событие модуля менеджера объекта ОбработкаПослеЗаписиВерсийИсторииДанных (для объектов, поддерживаемых историю данных). Для объектов, поддерживаемых историей данных, реализовано свойство ЗаписьИсторииДанных.ОбработкаПослеЗаписиИсторииДанных, с помощью которого можно управлять необходимостью вызывать обработчик события ОбработкаПослеЗаписиВерсийИсторииДанных. Объекты, для которых необходимо выполнить обработку после записи истории данных, хранятся в специальной очереди. Для удаления объектов из этой очереди реализован метод ИсторияДанных.УдалитьИзОбработкиПослеЗаписиВерсий().

Для объекта конфигурации реализовано свойство ВыполнятьОбработкуПослеЗаписиВерсииИсторииДанных.

Реализована возможность обновлять историю данных сразу после записи объекта. Обновление истории будет выполняться фоновым заданием после окончания транзакции записи объекта. Реализовано свойство ЗаписьИсторииДанных.ОбновлятьИсториюСразуПослеЗаписи.

Для объекта конфигурации реализовано свойство ОбновлятьИсториюДанныхСразуПослеЗаписи.

Для менеджера истории данных реализован метод ВыполнитьОбработкуПослеЗаписиВерсий().

Реализована возможность добавлять в запись истории данных новые поля и табличные части. Табличные части могут быть добавлены только в те объекты, где в метаданных присутствуют табличные части. Реализовано свойство ЗаписьИсторииДанных.ДополнительныеДанные. Метод ПолучитьМетаданные() (по версии данных) менеджера истории данных, возвращает информацию с учетом добавленных свойств и табличных частей. Для объекта ЗаписьИсторииДанных реализованы методы ДобавитьДополнительныеДанные() и ДобавитьПредставлениеПоляДополнительныхДанных().

Реализована возможность отменять запись истории данных. Реализовано свойство ПараметрыЗаписиИсторииДанных.Отказ.

Для записи комментария версии реализовано свойство ЗаписьИсторииДанных.КомментарийВерсии.

Методы объектов, поддерживающих историю данных, УстановитьКомментарийВерсииИсторииДанных() и ПолучитьКомментарийВерсииИсторииДанных() объявлены устаревшими и поддерживаются для совместимости.

Для метода ОбновитьИсторию() (во всех вариантах синтаксиса) менеджера истории данных реализованы параметры ВыполнитьОбработкуПослеЗаписиВерсий и АвтоУдалениеИзОбработкиПослеЗаписиВерсий.

Для констант реализован модуль менеджера.

Реализованы системные фоновые задания для обработки после записи версий и для обновления истории данных сразу после записи.

Данные возможности не предоставлялись.Расширены инструменты работы с историей данных.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Работа с запросами.
Система компоновки данных.
Если в файловом варианте информационной базы используется операция ПОДОБНО в языке запросов (в том числе при расчете функции в предложении ИТОГИ) или языке выражений системы компоновки данных, то специальный символ, указанный с помощью ключевого слова СПЕЦСИМВОЛ, работает внутри квадратных скобок.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Если в файловом варианте информационной базы используется операция ПОДОБНО в языке запросов (в том числе при расчете функции в предложении ИТОГИ) или языке выражений системы компоновки данных, то специальный символ, указанный с помощью ключевого слова СПЕЦСИМВОЛ, не работал внутри квадратных скобок.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Реализована возможность выполнить регистрацию (и отменить регистрацию) информационной базы в системе взаимодействия на стороне сервера «1С:Предприятия».

Для менеджера системы взаимодействия реализованы методы ВыполнитьРегистрациюИнформационнойБазы() и ОтменитьРегистрациюИнформационнойБазы().

Регистрация и отмена регистрации информационной базы в системе взаимодействия была доступна только на стороне клиентского приложения системы «1С:Предприятие».Расширены возможности административных действий в системе взаимодействия.
В документации данное изменение описано здесь.
Управляемая форма.
Система компоновки данных.
При открытии настроек условного оформления (сохраненных в ранних версиях платформы) с отключенным режимом совместимости, значения следующих параметров условного оформления формы и отчета будут установлены в значения по умолчанию:
  • Элементы условного оформления формы (объект ЗначениеПараметраКомпоновкиДанных): Линия, Цвет, Шрифт.
  • Элементы условного оформления отчета (коллекция объектов ОформлениеКомпоновкиДанных): Линия, Цвет, Шрифт, ВертикальноеПоложение, ГоризонтальноеПоложение, Размещение, ПоложениеТекстаОтносительноКартинки, РазмерКартинки.

Изменения произойдут в том случае, если значения этих параметров условного оформления задавались строкой, а не значениями соответствующего типа.

Рекомендуется проанализировать места использования указанных выше параметров условного оформления и устранить места задания значений параметров в виде строки.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Значения (объект ЗначениеПараметраКомпоновкиДанных) следующих параметров условного оформления формы и отчета (коллекция объектов ОформлениеКомпоновкиДанных) могли задаваться не только значениями соответствующих типов, но и строкой:
  • Элементы условного оформления формы: Линия, Цвет, Шрифт.
  • Элементы условного оформления отчета: Линия, Цвет, Шрифт, ВертикальноеПоложение, ГоризонтальноеПоложение, Размещение, ПоложениеТекстаОтносительноКартинки, РазмерКартинки.

При этом наблюдалось следующее поведение:

  • В условном оформлении отчетов и при чтении из XML - выполнялось преобразование строки в значение, соответствующее типу параметра. Параметры применялись с использованием значений, полученных в результате преобразования.
  • В условном оформлении динамических списков - не выполнялось преобразование строки в значение. Параметры применялись с использованием значений по умолчанию.
  • В условном оформлении форм (в тонком клиенте) - выполнялось преобразование строки в значение. Параметры применялись с использованием значений, полученных в результате преобразования.
  • В условном оформлении форм (в тонком клиенте) - не выполнялось преобразование строки в значение. Параметры применялись с использованием значений по умолчанию. В версии 8.3.14 в этом случае наблюдалась ошибка.
Устранено некорректное поведение системы.
Система компоновки данных.
При расчете следующих полей системы компоновки данных, если значение ресурса, от которого получено данное поле, в текущей группировке равно 0, то значением поля будет 0:
  • % общий,
  • % в группировке,
  • % в группе иерархии,
  • % в строке или серии,
  • % в колонке или точке,
  • % в группировке строки или серии,
  • % в группировке колонки или точки,
  • % в группе иерархии строки или серии,
  • % в группе иерархии колонки или точки.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

При расчете следующих полей системы компоновки данных:
  • % общий,
  • % в группировке,
  • % в группе иерархии,
  • % в строке или серии,
  • % в колонке или точке,
  • % в группировке строки или серии,
  • % в группировке колонки или точки,
  • % в группе иерархии строки или серии,
  • % в группе иерархии колонки или точки,

наблюдалось следующее поведение: деление на значение родительской группировки (или общего итога) выполнялось всегда, кроме случая, когда значение ресурса в группировке было равно NULL. В результате во время выполнения могла формироваться ошибка деления на 0.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Когда свойству Диаграмма.ИсточникДанных присваивается новое значение, то во время присваивания вначале выполняется удаление существующих точек и серий, а затем создаются новые точки и серии по новому источнику данных. В результате присваивания нового значения будет удаляться текущее выделение.

Рекомендуется перед установкой новых данных запомнить текущее выделение и восстановить его, если это необходимо.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Если свойству Диаграмма.ИсточникДанных присваивается новое значение, то после присваивания точки и серии не удалялись, выделение не очищалось.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Мобильный клиент.
Средства разработки.
В панели предварительного просмотра редактора формы реализована поддержка экранов с закругленными краями и вырезом (для мобильных устройств, работающих под управлением ОС iOS).

В список моделей устройств для предварительного просмотра в редакторе формы добавлены модели iPhone X/XS/XS Max/XR.

Данная возможность не предоставлялась.Стало проще разрабатывать формы для работы на устройствах iPhone последних версий.
Специальные возможности мобильного устройства.
Мобильный клиент.
Мобильная платформа.
Реализована возможность размещать на сделанном фотоснимке штамп с датой и временем съемки, а также произвольный текст.

Реализован объект ОтметкаНаФотоснимке.

Для метода СредстваМультимедиа.СделатьФотоснимок() реализован параметр Отметка.

Данная возможность не предоставлялась.Расширены возможности работы с фотоснимками.
В документации данное изменение описано здесь.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
При работе мобильного приложения под управлением ОС Android, запись звука выполняется в формате MPEG4 с использованием кодека AAC.

При работе мобильного приложения под управлением любой мобильной операционной системы, запись звука выполняется в формате стерео, битрейт 128 Кбит/с и частота дискретизации 44 кГц.

В результате работы метода СредстваМультимедиа.СделатьАудиозапись() возвращают объект ДанныеМультимедиа, где расширение файла установлено в значение m4a, а MIME-тип - в значение audio/mp4.

Качество аудиозаписи и результат работы метода СредстваМультимедиа.СделатьАудиозапись() зависел от используемой мобильной операционной системы:
  • ОС Android: формат 3gp, моно, частота дискретизации 8 кГц. Расширение 3gp, MIME-тип - audio/3gp.
  • ОС iOS: формат m4a, стерео, частота дискретизации 44 кГц. Расширение m4a, MIME-тип - audio/mp4.
  • ОС Windows: формат m4a, моно, качество звука выбиралось автоматически. Расширение aac, MIME-тип - audio/aac.
Унифицирован результат записи аудиоинформации при работе под управлением различных мобильный операционных систем.

Результат записи звука с помощью мобильной версии системы «1С:Предприятие» можно прослушать с помощью стандартных инструментов операционных систем на персональных компьютерах.

В документации данное изменение описано здесь.
Фоновые и регламентные задания.
Мобильный клиент.
На мобильном клиенте реализована возможность работать с диалогом расписания регламентного задания. На мобильном клиенте реализована доступность объекта ДиалогРасписанияРегламентногоЗадания. На мобильном клиенте было недоступно редактирование расписания регламентного задания.На мобильном клиенте стало возможно редактировать расписание регламентного задания.
Мобильный клиент.
Сборщик мобильных приложений.
Для мобильного клиента реализована возможность добавлять информационную базу в список с помощью сканирования QR-кода. Данная возможность доступна в том случае, если для приложения мобильного клиента разрешено добавление информационной базы с произвольным адресом.

Данная возможность также доступна в мобильной версии для разработчика.

В сборщике мобильных приложений реализована возможность разрешить добавлять информационные базы с использованием QR-кода.

В адресах, принадлежащих схеме e1c://, реализована возможность использовать команды:

  • /AddByQRCode - запускает сканирование QR-кода.
  • /AddInfoBase - позволяет добавить информационную базу в список информационных баз клиентского приложения.
Данная возможность не предоставлялась.Расширены возможности по добавлению информационных баз в список мобильного клиента или мобильной платформы. Добавление информационных баз стало более простым.
В документации данное изменение описано здесь и здесь.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Копии базы данных.
Ускорено первоначальное заполнение копии базы данных в том случае, если в исходных данных присутствуют документы, выполняющие движения по регистрам и содержащим большое количество строк в табличных частях.Первоначальное заполнение копии базы данных занимало больше времени в том случае, если в исходных данных присутствовали документы, выполняющие движения по регистрам и содержащим большое количество строк в табличных частях.Ускорено первоначальное заполнение копии базы данных.
Система взаимодействия.
При переопределении списка выбора пользователей системы взаимодействия, при создании сообщения контекстного обсуждения, необходимость отказа от оповещения пользователей (отображается в пользовательском интерфейсе как значение Никого не оповещать) передается в виде особого значения параметра ДанныеВыбора обработчика АвтоПодборПользователейСистемыВзаимодействия.

Особое значение может быть создано с помощью конструктора объекта ИдентификаторПользователяСистемыВзаимодействия без указания идентификатора пользователя системы взаимодействия.

Значение Неопределено в качестве значения параметра ДанныеВыбора обработчика ИдентификаторПользователяСистемыВзаимодействия более не допускается.

При переопределении списка выбора пользователей системы взаимодействия при создании сообщения контекстного обсуждения необходимость отказа от оповещения пользователей (отображается в пользовательском интерфейсе как значение Никого не оповещать) передавалась в виде значения Неопределено, что не позволяло различить отказ от оповещения и закрытие формы выбора пользователей без какого-либо выбора.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Управляемые блокировки.
Пессимистическая объектная блокировка, в клиент-серверном варианте, будет безусловно снята кластером серверов при выполнении всех следующих условий:
  • Выполняется попытка снять объектную блокировку, установленную другим пользователем (в удаленном клиентском приложении).
  • Для снятия блокировки используется система взаимодействия.
  • Удаленное клиентское приложение в течении 5 секунд, после отправки сообщения системы взаимодействия, не сняло блокировку.
Попытка снятия пессимистической объектной блокировка, в клиент-серверном варианте, приводило к сообщению о невозможности редактирования при выполнении всех следующих условий:
  • Выполнялась попытка снять объектную блокировку, установленную другим пользователем (в удаленном клиентском приложении).
  • Для снятия блокировки использовалась система взаимодействия.
  • Удаленное клиентское приложение в течении 5 секунд, после отправки сообщения системы взаимодействия, не сняло блокировку.
Устранено некорректное поведение системы.
Кластер серверов.
Повышена надежность работы отказоустойчивого кластера.Отказоустойчивый кластер работал ненадежно.Повышена надежность работы отказоустойчивого кластера.
Мобильный клиент.
Мобильная платформа.
Сборщик мобильных приложений.
Для мобильной версии платформы «1С:Предприятие», работающей под управлением ОС Android, реализована поддержка 64-разрядной архитектуры процессоров.

Сборщик мобильных приложений, при сборке приложения для работы под управлением ОС Android, собирает 4 варианта приложения: 32-разрядное приложение архитектуры x86 и ARM и 64-разрядное приложение архитектур x86_64 и ARM64. Также реализована возможность публикации 64-разрядных приложений в магазин Google Play.

Изменен состав файлов в архиве дистрибутива мобильной версии mobile.zip.

Мобильная версия платформы «1С:Предприятие», работающая под управлением ОС Android, поддерживала только 32-разрядные архитектуры процессоров. Сборщик мобильных приложений не мог собирать и публиковать в магазине Google Play 64-разрядные версии мобильных приложений.Расширен список поддерживаемых архитектур процессоров при работе мобильной версии под управлением ОС Android.

Увеличился размер собранных мобильных приложений, работающих под управлением ОС Android. Повысилась скорость работы собранных мобильных приложений под управлением ОС Android.

В документации данное изменение описано здесь, здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
В соответствии с требованиям владельцев магазинов приложений, произошла замена некоторых разрешений мобильного приложения на несколько разрешений:
  • Разрешение Телефония заменено на следующие:
    • Набор номера;
    • Чтение журнала звонков;
    • Обработка звонков;
    • Автоматическая отправка SMS сообщений;
    • Получение SMS сообщений;
    • Журнал SMS сообщений.
  • Разрешение Мультимедиа заменено на следующие:
    • Камера;
    • Микрофон;
    • Библиотека музыки;
    • Библиотека картинок и видео;
    • Воспроизведение аудио и видео.

Новые разрешение сгруппированы по смыслу и функциональной связности.

Конфигурации, выгруженные версией 8.3.14 и более ранними, невозможно собрать с использованием мобильной версии версии 8.3.15 и последующими. Обратное правило также верно.

Разрешения мобильного приложения имели другой состав.Разрешения мобильного приложения учитывают изменившиеся требования владельцев магазинов приложений.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
В конфигураторе реализована возможность редактирования текстов запросов разрешений, которые требуются мобильному приложению для своей работы. Для редактирования доступны тексты запросов тех разрешений, которые имеют прикладной смысл для пользователя.

Сборщик мобильных приложений позволяет собирать мобильные приложения, которые содержат как конфигурации с указанными текстами запросов разрешений, так и без таковых (выгруженные в предыдущих версиях платформы «1С:Предприятие»).

Тексты запросов разрешений не редактировались в конфигураторе.Стало возможно указывать такие тексты запросов разрешений, которые максимально точно соответствуют требованиям мобильных приложений.
В документации данное изменение описано здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Глобальный поиск.
В мобильной версии системы «1С:Предприятие» реализован механизм глобального поиска.Данная функциональность не поддерживалась на мобильной версии.В мобильной версии «1С:Предприятие» реализованы возможности, ранее реализованные в версии системы «1С:Предприятие» для персонального компьютера.
Средства разработки.
В синтакс-помощнике реализованы следующие изменения:
  • Устаревшие объекты (свойства, функции, процедуры и т.д.) не удаляются из синтакс-помощника, а сохраняются в нем.
  • Доступность нерекомендуемых объектов (объекты, которые еще недоступны или не рекомендуются к использованию в текущем режиме совместимости) в дереве синтакс-помощника регулируется флажком в настройках синтакс-помощника: Отображать нерекомендуемые объекты.
  • Реализовано отображение версии привнесения, версия устаревания и версия, в которой смысловая информация об объекте редактировалась в последний раз.
  • Для устаревших объектов реализовано отображение объектов, рекомендуемых к использования вместо устаревшего.
  • Шрифт статьи синтакс-помощника установлен равным шрифту по умолчанию для библотеки WebKit, которая используется для отображения HTML-документов.
  • Для окна содержимого синтакс-помощника установлено ограничение по ширине в 1 000 пикселей.
  • Уменьшены отступы до и после маркированных списков.

Несмотря на состояние флажка настройки Отображать нерекомендуемые объекты, поиск с помощью сочетания клавиш Ctrl+F1 всегда приводит к отображению информации об объекте синтакс-помощника.

Информация о версии привнесения заполнена для всех объектов синтакс-помощника. Информация о версии удаления заполнена для всех объектов синтакс-помощника. Рекомендуемые объекты для замены заполнены только в тех случаях, если объявление об устаревании объекта выполнялось в версии 8.3.14 и последующих.

Указанные изменения в синтакс-помощнике действуют начиная с версии 8.3.15 и последующих.

В синтакс-помощнике отсутствовала информация о версиях объектов (привнесения, устаревания, изменения), а также об объектах, рекомендованных для использования вместо устаревших. Устаревшие объекты удалялись из синтакс-помощника. Получить доступ к таким объектам было невозможно.Синтакс-помощник стало более информативен и полезен для разработчика.
В документации данное изменение описано здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Реализована возможность использовать дополнительную проверку для получения доступа к возможностям мобильного приложения. Проверка выполняется используемой мобильной операционной системой и включает в себя проверку с использованием биометрии (отпечаток пальца, распознавание лица, распознавание радужной оболочки глаза) или ввода пароля (графического ключа и т.д.). Реализовано свойство глобального контекста ДополнительнаяПроверкаПользователя.

Реализовано безопасное хранение конфиденциальной информации на мобильном устройстве пользователя. Защита информации осуществляется средствами мобильной операционной системы. Реализована возможность управлять необходимостью дополнительной аутентификации для доступа к конфиденциальной информации. Реализовано свойство глобального контекста БезопасноеХранилище.

Данные возможности не предоставлялись.Расширены возможности мобильной версии «1С:Предприятие» в части дополнительной проверки пользователя и хранения конфиденциальной информации.
В документации данное изменение описано здесь.
Мобильный клиент.
Для мобильного клиента реализована возможность использовать биометрическую аутентификацию для упрощенного входа в приложение.

На мобильных устройствах, поддерживающих биометрическую аутентификацию, в свойствах информационной базы мобильного клиента, а также в диалогах ввода имени пользователя и пароля, формируемых мобильным клиентом, становится доступен флажок Использовать биометрию.

Данная возможность не предоставлялась.Стало возможно упростить процесс аутентификации в приложении для устройств, поддерживающих биометрическую аутентификацию.
В документации данное изменение описано здесь.
Установка клиентского приложения.
Для программы установки клиентского приложения в ОС Windows реализована поддержка вьетнамского языка.Программа установки клиентского приложения в ОС Windows не поддерживала вьетнамский язык.Устранено некорректное поведение системы.
История данных.
Для стандартной обработки История изменений данных реализованы возможности:
  • Запустить выполнение обработки очереди объектов после записи версий.
  • Удалить объекты из очереди обработки объектов после записи версий.

Данные возможности доступны с форме обработки с помощью команды Еще - Управление историей данных.

Данные возможности не предоставлялись.В стандартной обработке поддержаны новые возможности механизма работы с историей данных, ранее реализованные в платформе.
В документации данное изменение описано здесь.
Система взаимодействия.
Форма клиентского приложения.
При вызове метода формы НачатьПолучениеОбсуждения() реализовано создание контекстного обсуждения, если к моменту вызова метода получаемое контекстное обсуждение отсутствует.При вызове метода формы НачатьПолучениеОбсуждения() не выполнялось создание контекстного обсуждения, которое отсутствовало к моменту вызова метода.При вызове метода формы НачатьПолучениеОбсуждения() автоматически создается контекстное обсуждение, если к моменту вызова метода получаемое контекстное обсуждение отсутствует.
Документация.
В документации уточнено, что для работы с кластером, созданным стандартной версией СУБД PostgreSQL, пригодна только версия СУБД PostgreSQL, которая выпускается фирмой «1С».Информация в документации о том, что для работы с кластером, созданным стандартной версией СУБД PostgreSQL, пригодна только версия СУБД PostgreSQL, которая выпускается фирмой «1С», была явно не указана.Уточнена документация.
В документации данное изменение описано здесь.
Кластер серверов.
Оптимизирована работа финального шага алгоритма балансировки нагрузки (в режиме выбора с приоритетом по производительности) в том случае, когда отобранные на предыдущих шагах рабочие процессы отличаются по доступной производительности.Финальный шаг алгоритма балансировки нагрузки (в режиме выбора с приоритетом по производительности) работал неоптимально в том случае, когда отобранные на предыдущих шагах рабочие процессы отличаются по доступной производительности.Оптимизирован алгоритм балансировки нагрузки в кластере серверов.
В документации данное изменение описано здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
В документации приведена информация по настройке веб-серверов для корректной работы механизма фоновых заданий в файловом варианте информационной базы.В документации отсутствовала информация по настройке веб-серверов для корректной работы механизма фоновых заданий в файловом варианте информационной базы.Уточнена документация к платформе.
В документации данное изменение описано здесь и здесь.
Работа с файлами.
При использовании методов НачатьПомещениеФайла()/НачатьПомещениеФайлов() загружаемый файл/файлы разбиваются на части и передача на сервер выполняется по частям. В результате сохраняется работоспособность пользовательского интерфейса.

Также реализована возможность начать помещение новых файлов, даже если файлы, помещение которых было начато ранее, еще не завершено.

При использовании методов НачатьПомещениеФайла()/НачатьПомещениеФайлов() загружаемый файл/файлы передавались целиком. Во время передачи клиентское приложение не реагировало на действия пользователя.

Начать помещение нового файла было невозможно, пока не завершилась ранее начатое помещение одного или нескольких файлов.

Устранено некорректное поведение системы.
Регистры расчета.
Прикладные объекты.
Реализована возможность включать последовательности и перерасчеты в состав общих реквизитов.

В режиме совместимости с версией 8.3.14 поведение не изменилось.

Данная возможность не предоставлялась.Расширен состав объектов конфигурации, которые могут входить в состав общих реквизитов.
В документации данное изменение описано здесь.
Программное лицензирование.
Ускорен запуск клиентского приложения и конфигуратора на компьютерах, работающих под управлением ОС Linux и macOS, при использовании базовых конфигураций, в том случае, когда на компьютере имеется большое количество дисковых разделов или ядер процессора.

Список ключевых параметров оборудования, используемых при активации базовой программной лицензии в операционных системах Linux и macOS, приведен в соответствие со списком ключевых параметров в операционной системе Windows.

Запуск клиентского приложения и конфигуратора на компьютерах, работающих под управлением ОС Linux и macOS, при использовании базовых конфигураций, в том случае, когда на компьютере имеется большое количество дисковых разделов или ядер процессора, выполнялся очень долго

Список ключевых параметров оборудования, используемых при активации базовой программной лицензии в операционных системах Linux и macOS, отличался от списка ключевых параметров в операционной системе Windows.

Ускорен запуск клиентского приложения и конфигуратора при работе с базовой конфигурацией под управлением ОС Linux и macOS.
Мобильный клиент.
Реализована доступность объекта ТекстовыйДокумент при работе в мобильном клиенте.Объекта ТекстовыйДокумент был недоступен при работе в мобильном клиенте.Расширены возможности мобильного клиента.
Кластер серверов.
Параметры Критический объем памяти процессов, Временно допустимый объем памяти процессов и Интервал превышения допустимого объема памяти процессов допустимо изменять с лицензией уровня ПРОФ.

Однако эти параметры влияют только на перезапуск процессов. Влияние данных параметров на прерывание серверных вызовов поддерживается только для лицензий уровня КОРП.

Если сервер работает с лицензией уровня ПРОФ, то значение предельного объёма памяти, после которого прерывается выполнение клиентского вызова сервера, определяется как 80% объема физической памяти компьютера, независимо от значения параметра Временно допустимый объем памяти процессов.

Параметры Критический объем памяти процессов, Временно допустимый объем памяти процессов и Интервал превышения допустимого объема памяти процессов было допустимо изменять только с лицензией уровня КОРП.Для кластера серверов, работающий с лицензией уровня ПРОФ, стало возможно управлять перезапуском рабочих процессов по критерию превышения объема потребляемой оперативной памяти.
В документации данное изменение описано здесь и здесь.
Форма клиентского приложения.
Интерфейс.
Для команды контекстного меню элементов формы Искать везде установлено сочетание клавиш Alt+L.Для команды контекстного меню элементов формы Искать везде использовалось сочетание клавиш Ctrl+Shift+C.Устранено пресечение сочетания клавиш для механизма платформы и устоявшегося сочетания клавиш типовых прикладных решений.
Интерфейс.
В интерфейсе Такси реализовано меню формы - отображается тремя точками, размещается в правой верхней части формы (кроме диалогов, формируемых методами Вопрос(), ПоказатьВопрос(), Предупреждение() и ПоказатьПредупреждение()). На начальной странице отображается одно меню формы. Состав меню формы зависит от текущего (активного) элемента формы:
  • Подменю Файл доступно, если для текущего элемента доступны команды сохранения и печати.
  • Команды поиска отображаются в том случае, если в текущем элементе поддерживается поиск или замена. Команды поиска не будут отображены, если текущим элементом формы выступает таблица, отображающая динамический список или коллекцию данных формы.
  • Команды работы с буфером обмена отображаются в том случае, если текущий элемент поддерживает работу с буфером обмена.
  • Если текущий элемент поддерживает команды отмены и возврата - в меню формы доступны эти команды.
  • Команда отображения свойств доступна при возможности просмотр свойств текущего элемента.
  • Команда специальной вставки отображается при наличии такой возможности (только в тонком и толстом клиентских приложениях).
  • Команда настройки панели навигации формы отображается только при наличии такой возможности.
  • Команда Сообщения отображается в том случае, если в форме выводились сообщения.
  • Команды объединения и закрепления окон не отображаются в меню формы, если форма отображается во вспомогательном окне.

В меню Сервис и настройки выполнены следующие изменения:

  • Из подменю Окна убраны команды объединения и закрепления окон.
  • Из подменю Настройки убраны команды отображения окна сообщений и настройки панели навигации формы.
  • Команды сохранения, печати (и настройки печати) действуют только на текущий (активный) элемент текущей формы клиентского приложения.

Команды работы с буфером обмена для чисел (поместить в буфер, прибавить к/вычесть из содержимого буфера) могут отображаться в заголовке главного окна приложения или вспомогательного окна приложения. Для включения/выключения этих команд предназначена команда Показать М, М+, М- меню Сервис и настройка.

В таблице формы, отображающей динамический список, сочетание клавиш Alt+F открывает диалог расширенного поиска.

Меню формы отсутствовало. Команды меню формы располагались в меню Сервис и настройки.Улучшена навигация в прикладном решении.
Полнотекстовый поиск.
Устранена проблема поиска слов, оканчивающихся на «*» с помощью полнотекстового поиска.

Если платформа сможет установить некорректность текущего индекса полнотекстового поиска - она автоматически удалит его.

Рекомендуется очистить и перестроить индекс полнотекстового поиска при переходе на версию 8.3.15.

С помощью полнотекстового поиска было невозможно найти слова, оканчивающихся на «*».Устранено некорректное поведение системы.
Средства администрирования.
В составе дистрибутива системы «1С:Предприятие» выделены отдельные файлы, предназначеные для работы программы установки на ОС Windows XP (имена этих файлов оканчиваются на суффикс _xp).

Программы установки приложений системы «1С:Предприятие» для ОС Windows используют кодировку UTF-8 для хранения отображаемых текстов. Программы установки для ОС Windows XP используют кодировку ANSI.

Программа установки системы «1С:Предприятие» для ОС Windows XP не поддерживает установку на вьетнамском языке.

Если для обновления системы «1С:Предприятие» используется веб-сервер и в организации не используется ОС Windows XP, рекомендуется не включать в архив клиентского приложения файлы дистрибутива для ОС Windows XP (имеющие суффикс имени _xp), для уменьшения размера загружаемого архива.

Программа установки системы «1С:Предприятие» на ОС Windows XP могла некорректно отображать символы на национальных языках.Поддержка устаревшей и неподдерживаемой производителем операционной системы Windows XP вынесена в отдельный дистрибутив.
В документации данное изменение описано здесь, здесь и здесь.
Табличный документ.
Команды управления поиском стали доступны с помощью меню Еще формы отчета и формы табличного документа.

Команды работы с таблицей и команды, связанные с редактированием, более недоступны в меню Еще формы табличного документа. +

Команды управления поиском были доступны только через меню формы отчета и табличного документа.

В форме табличного документа, в меню Еще, были доступны команды работы с таблицей и команды, связанные с редактированием. Эти же команды были доступны и в меню формы. +

Распределение команд между меню формы и меню Еще, в формах отчета и табличного документа, стало более логичным и понятным.
Интерфейс.
Команды сохранения и настройки печати более недоступны в меню Сервис и настройки - Файл.Команды сохранения и настройки печати были доступны в меню Сервис и настройки - Файл.Устранено дублирование команд в различных меню приложения.
Интерфейс.
Команда Изменить масштаб перенесена в меню формы.Команда Изменить масштаб размещалась в меню Сервис и настройка.Контекстная команда формы теперь находится непосредственно в форме.
В документации данное изменение описано здесь и здесь.
Средства администрирования.
Для утилиты контроля целостности системы реализована возможность вычислять хеш-функцию файлов с помощью алгоритмов SHA-256 и ГОСТ Р 31.11-2012 (512 бит).

Для режима работы make утилиты реализован параметр --method, который позволяет указать используемый алгоритм расчета хеш-функции.

Утилита контроля целостности системы всегда вычисляла хеш-функцию файлов с помощью алгоритма SHA-1.Для расчета хеш-функций стало возможно использовать более стойкие алгоритмы.
В документации данное изменение описано здесь.
История данных.
Существенно ускорено обновление истории данных (вызов метод ИсторияДанных.ОбновитьИсторию()) в том случае, если в системе существует большое количество версий, которые необходимо перенести в историю данных.Обновление истории данных (вызов метод ИсторияДанных.ОбновитьИсторию()) в том случае, если в системе существует большое количество версий, которые необходимо перенести в историю данных, занимало очень много времени.Ускорено обновление истории данных. Обновление истории данных можно выполнять одновременно с обычной работой пользователей.
Полнотекстовый поиск.
Уменьшено время формирования индекса полнотекстового поиска. Уменьшено дисковое пространство, занимаемое индексом полнотекстового поиска.

В случае ввода поисковой строки, состоящей из одного или двух символов и символа подстановки «*» (любая последовательность символов) может возникать ошибка с предложением уточнить поисковую строку (при большом результате поиска).

Формирования индекса полнотекстового поиска занимало больше времени, а сам индекс занимал больше дискового пространства.

В случае ввода поисковой строки, состоящей из одного или двух символов и символа подстановки «*» (любая последовательность символов) не возникала ошибка с предложением уточнить поисковую строку (при большом результате поиска).

Ускорено формирование индекса полнотекстового поиска. Уменьшено дисковое пространство, занимаемое индексом полнотекстового поиска.
Обновление конфигурации базы данных.
Реструктуризация таблицы базы данных не будет выполняться при одновременном выполнении всех следующих условий:
  • Используется оптимизированный механизм реструктуризации (режим v2).
  • Используется СУБД Microsoft SQL Server.
  • У объекта имеются подчиненные объекты (реквизиты, измерения и т.д.) типа хранилище значения, строка неограниченной длины или дата.
  • Объекты вышеперечисленных типов были добавлены в режиме совместимости с версией 8.3.7 и предыдущих.
  • После установки режима совместимости 8.3.8 и последующих, для такого объекта конфигурации не выполнялась реструктуризация.
  • Все изменения в объекте конфигурации не касаются реквизитов вышеперечисленных типов.

При выполнении всех вышеперечисленных условий оптимизированный механизм реструктуризации будет выполнять только выполненные изменения (при возможности) и не будет изменять выполнять полной реструктуризации таблицы базы данных.

Обычная реструктуризация информационной базы всегда выполняется реструктуризацию информационной базы при любых изменения в метаданных объекта конфигурации.

При одновременном выполнении всех нижеследующих условий выполнялась реструктуризация таблицы базы данных:
  • Используется оптимизированный механизм реструктуризации (режим v2).
  • Используется СУБД Microsoft SQL Server.
  • У объекта имеются подчиненные объекты (реквизиты, измерения и т.д.) типа хранилище значения, строка неограниченной длины или дата.
  • Объекты вышеперечисленных типов были добавлены в режиме совместимости с версией 8.3.7 и предыдущих.
  • После установки режима совместимости 8.3.8 и последующих, для такого объекта конфигурации не выполнялась реструктуризация.
  • Все изменения в объекте конфигурации не касаются реквизитов вышеперечисленных типов.
В некоторых случаях (условия перечислены в разделе «Как стало») оптимизированный механизм реструктуризации будет обновлять таблицы базы данных существенно быстрее, чем обычный механизм реструктуризации.
Технологический журнал.
В документации актуализировано описание свойств события CLSTR.В документации было приведено устаревшее описание свойств события CLSTR.Актуализирована документация.
В документации данное изменение описано здесь.
Форма клиентского приложения.
Командный интерфейс.
В заголовке формы клиентского приложения реализованы кнопки Сохранить, Печать и Предварительный просмотр. Данные кнопки, а также подменю Файл в меню формы, отображаются в том случае, если в текущей форме есть хотя-бы одно видимое поле следующего вида:
  • Поле табличного документа.
  • Поле текстового документа.
  • Поле графической схемы.
  • Поле HTML-документа.
  • Поле форматированного документа.
  • Поле географической схемы.
  • Поле планировщика.

Команды печати и сохранения будут доступны в том случае, если на форме есть единственный элемент из списка приведенных выше, поддерживающий эти команды или текущий элемент формы поддерживает эти команды.

Для вызова меню формы реализована команда Alt + -.

Команды Сохранить, Печать и Предварительный просмотр отображались в системной командной панели и в главном меню. Команды были доступны, если текущий элемент формы поддерживал эту команду, или на форме был только один видимый элемент из перечисленных далее и элемент поддерживал эту команду:
  • Поле табличного документа.
  • Поле текстового документа.
  • Поле графической схемы.
  • Поле HTML-документа.
  • Поле форматированного документа.
  • Поле географической схемы.
  • Поле планировщика.
Если в форме есть элементы, поддерживающие сохранение и печать, то работа с ними стала более понятной для пользователя.
В документации данное изменение описано здесь.
Мобильная платформа.
Мобильный клиент.
Системные требования.
Для устройств на базе операционной системы iOS прекращена поддержка версии 7.x. Минимальная версия iOS - 8.0.Поддерживалась версия 7.x операционной системы iOS.Прекращена поддержка устаревшей версии операционной системы iOS. Прекращена поддержка устройства Apple iPhone 4.
В документации данное изменение описано здесь.
Расширение конфигурации.
Реализована возможность использовать расширения для базовых конфигураций. Для этого расширение должно быть подписано тем же ключом, что и сама базовая конфигурация.

Для пакетного режима запуска конфигуратора реализована команда /SignCfg.

Для конфигуратора, запущенного в режиме агента, реализована команда sign-cfg режима config.

Использование расширения не поддерживалось при использовании базовых конфигураций.Разработчик базовых конфигураций получил возможность выпускать исправления для базовых конфигураций, без перевыпуска всей конфигурации.
В документации данное изменение описано здесь, здесь и здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
При выполнении публикации для веб-сервера Apache, публикация недоступна, если разрядность веб-сервера не совпадает с разрядностью конфигуратора, которым выполняется публикация.При выполнении публикации для веб-сервера Apache, не выполнялась проверка соответствия разрядности веб-сервера и конфигуратора, которым выполнялась публикация.Снижено количество труднообъяснимых ошибок, которые могли возникать при публикации на веб-сервер Apache с отличающейся разрядностью.
В документации данное изменение описано здесь.
Средства администрирования.
Возможность обновления клиентского приложения через веб-сервер доступна для использования с лицензией ПРОФ.Возможность обновления клиентского приложения через веб-сервер была доступна для использования только с лицензией КОРП.Упрощено обновление клиентских приложений при подключении к информационной базе с использованием веб-сервера.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Кластер серверов.
Система мониторинга кластера анализирует не только настройки использования памяти, заданных в настройках кластера, но и объем используемой памяти каждого рабочего процесса:
  • Если объем используемой памяти превысит 80% от объема виртуального адресного пространства, то такой рабочий процесс будет завершен в штатном режиме.
  • Если объем используемой памяти превысит 95% от объема виртуального адресного пространства, то такой рабочий процесс будет завершен аварийно.

Механизмы кластера, использующие данные о доступной оперативной памяти компьютера, учитывают изменения, которые происходят с объемом оперативной памяти в течении работы компьютера (например, при смене параметров виртуальной машины, в которой работает кластер серверов).

+

Система мониторинга кластера не использовала для анализа объем используемой памяти каждого рабочего процесса.

Механизмы кластера, использующие данные о доступной оперативной памяти компьютера, использовали данные об оперативной памяти, которые получались один раз, при старте кластера.

Повышена стабильность работы кластера серверов в том случае, если работает 32-разрядный кластер серверов системы «1С:Предприятие» под управлением 64-разрядной операционной системы.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность открытия табличного документа, сохраненного в «1С:Предприятии» версии 8.3.17 и последующих.При попытке открытия табличного документа, сохраненного в «1С:Предприятии» версии 8.3.17 и последующих, формировалось исключение и документ не открывался.Устранено некорректное поведение системы.
Картинки.
Реализована поддержка многостраничных TIFF-картинок.

Реализованы методы Картинка.КоличествоКадров() и ОбрабатываемаяКартинка.ПолучитьКартинки().

Для объекта ОбрабатываемаяКартинка реализован вариант конструктора, получающего на вход массив картинок и формат результирующей картинки. Для конструктора объекта ОбрабатываемаяКартинка реализованы параметры Кадры и Формат.

Для расширения поля формы клиентского приложения для картинки реализовано свойство НомерТекущегоКадра и метод КоличествоКадров().

При загрузке многостраничной TIFF-картинки использовался только первый кадр.Реализована поддержка многостраничных TIFF-картинок.
В документации данное изменение описано здесь.
Клиентское приложение.
Средства администрирования.
Реализована возможность размещать в диалоге ввода логина и пароля пользователя гиперссылки для перехода на страницу со справочной информацией и для восстановления пароля.

Восстановление пароля может быть выполнено с помощью специальной страницы сайта, по электронной почте и с помощью инструментов провайдера OpenID. Реализовано управление возможностью восстановления пароля для каждого пользователя информационной базы. Для настроенной системы не требуется участие человека для восстановления пароля пользователя.

Для объекта ПользовательИнформационнойБазы реализованы свойства АдресЭлектроннойПочты и ЗапрещеноВосстанавливатьПароль.

Реализовано свойство глобального контекста ДополнительныеНастройкиАутентификации.

Реализованы события журнала регистрации Сеанс. Попытка восстановления пароля, Сеанс. Ошибка попытки восстановления пароля, Информационная база. Изменение дополнительных настроек аутентификации, Информационная база. Ошибка изменения дополнительных настроек аутентификации.

Восстановление пароля пользователя было возможно только с привлечением администратора информационной базы.Упрощена процедура восстановления пароля пользователем. Для восстановления пароля больше не требуется непосредственное участие администратора.
В документации данное изменение описано здесь и здесь.
Динамический список.
Система компоновки данных.
Исключена ошибка восстановления настроек системы компоновки данных и динамического списка в том случае, когда настройки были сохранены в версии 8.3.16 и последующих, но режим совместимости конфигурации установлен в значения Версия 8.3.15.Если режим совместимости конфигурации установлен в значения Версия 8.3.15, а сохранение настроек системы компоновки данных или динамического списка выполнялось в версии платформы 8.3.16 и последующих, то восстановить настройки было невозможно.Устранено некорректное поведение системы.
Клиентское приложение.
Установка клиентского приложения.
Средства администрирования.
Реализована возможность распространения клиентского приложения через веб-сервер, без настройки файла default.vrd, средствами расширения веб-сервера. Поиск дистрибутива клиентского приложения будет выполняться в каталоге distr каталога той версии, чье расширение веб-сервера работает на веб-сервере.

Реализованы новые варианты дистрибутивов клиентских приложений, которые могут быть установлены дополнительно к полноценному дистрибутиву системы «1С:Предприятие» и содержат упакованные дистрибутивы клиентских приложений. Такой вариант поставки клиентских приложений поддерживается только для ОС Windows и macOS.

Данная возможность не предоставлялась.

Дистрибутив клиентского приложения можно было получить с веб-сервера только после корректной настройки файла default.vrd.

Упрощена настройка распространения дистрибутивов клиентского приложения при обновлении версии системы «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.

Оглавление

Переход с предыдущей версии на версию 8.3.15

Оглавление

Версия 8.3.14

Версия 8.3.14 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8314doc) документации к текущей версии.

Оптимизированный механизм обновления конфигурации базы данных вышел из статуса бета-версии. В документации данное изменение описано здесь, здесь и здесь.

64-разрядное клиентское приложение (тонкий клиент, толстый клиент, конфигуратор), работающее под управлением ОС Windows, вышло из статуса бета-версии.

Мобильный клиент вышел из статуса бета-версии.

Поддержка ОС Windows в мобильной платформе вышла из статуса бета-версии.

Тонкий клиент для работы под управлением ОС macOS вышел из статуса бета-версии. Толстый клиент и конфигуратор для работы под управлением ОС macOS по-прежнему находятся в статусе бета-версии.

+

Термин «управляемое приложение» заменен на термин «клиентское приложение». Без особой необходимости, в файле V8Update, справке и документации, прекращается использование термина «управляемое». Таким образом, выражение «управляемое приложение» заменяется на «клиентское приложение», выражение «расширение поля ввода управляемой формы» заменяется на «расширение поля ввода формы» и т.д. Выполнены переименования соответствующих выражений пользовательского интерфейса конфигуратора и клиентских приложений.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.13. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.12. +Возможность запуска конфигураций, разработанных в версии 8.3.13 и более младших, в версии 8.3.14, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.14 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.14, при необходимости, использовать для работы с информационной базой и версию 8.3.13. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Кластер серверов.
Автономный сервер.
Реализован автономный сервер системы «1С:Предприятие». Это приложение, способное обслуживать клиентские приложения, работающие с информационной базой по протоколу HTTP.

Автономный сервер сам обеспечивает работу по протоколу HTTP, не требуя для этого выделенного веб-сервера. Автономный сервер более эффективно использует ресурсы компьютера, на котором сервер запущен.

Один экземпляр автономного сервера обслуживает одну информационную базу. Не поддерживается работа конфигуратора с автономным сервером. Автономный сервер управляется с помощью утилиты командной строки. Автономный сервер поддерживает работу с файловым и клиент-серверным вариантами информационной базы.

В случае работы с файловым вариантом базы, допускается использование до 3-х клиентских сеансов (без учета сеансов фоновых заданий, интернет-сервисов и т.д.) без приобретения серверной лицензии. Во всех остальных случаях требуется наличие любой серверной лицензии.

Автономный сервер имеет ряд ограничений, описанных в документации.

Автономный сервер обладает собственными средствами администрирования.

Данная возможность включена в статусе бета-версии.

Данная возможность не предоставлялась.Новая архитектура призвана повысить эффективность и надежность работы сервера 1С:Предприятия.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Копии базы данных.
Кластер серверов.
Работа с СУБД.
Реализована возможность размещать во внешней базе данных (относительно базы данных «1С:Предприятия») копии таблиц, использование которых в отчетах или запросах, вызывает повышенную нагрузку на используемую СУБД. Данный механизм поддерживается только при работе в клиент-серверном варианте работы.

Реализована возможность указания, в какой базе данных будет выполняться запрос или отчет.

В качестве СУБД, используемой для размещения таблиц-копий, допускается использование какой-либо из следующих СУБД: Microsoft SQL Server, Oracle Database, PostgreSQL. СУБД кластера серверов и копии базы данных могут различаться.

Синхронизация информации между базой данных кластера серверов и копией базы данных может выполняться как средствами платформы «1С:Предприятие», так и средствами используемых СУБД.

Реализовано свойство глобального контекста КопииБазыДанных. Для объекта Запрос реализованы свойства ТребуемаяАктуальностьДанных, ТребуемоеВремяАктуальностиДанных. Для объекта РезультатЗапроса реализованы свойства ДанныеАктуальны, ВремяАктуальностиДанных, КопияБазыДанных. Для объекта ЗначенияПараметровВыводаКомпоновкиДанных реализованы свойства ТребуемаяАктуальностьДанных, ТребуемоеВремяАктуальностиДанных, ВыводитьАктуальностьДанных, ВывводитьКопиюБазыДанных. Реализованы функции языка выражений системы компоновки данных ДанныеАктуальны(), ВремяАктуальностиДанных() и КопияБазыДанны().

Реализованы системные фоновые задания Первоначальное заполнение копии базы данных и Обработка оповещения копии базы данных.

Реализованы сервисы кластера Сервис копий базы данных и Сервис времени копий базы данных.

Реализована стандартная функция Управление копиями базы данных.

Реализовано событие технологического журнала <DBCOPIES>.

Механизм копий базы данных требует лицензию КОРП.

Данная возможность включена в статусе бета-версии.

Данная возможность не предоставлялась.Реализована возможность разделить нагрузку на информационную базу между различными физическими СУБД. Например, в основной базе данных будут выполняться все операции по вводу документов, а в копии базы данных будут выполняться отчеты и запросы, существенно нагружающие СУБД.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Кластер серверов.
Системные требования.
Реализован механизм ускорения формирования аналитических отчетов (Дата акселератор). С этой целью в кластере серверов реализован сервис, выполняющий функцию базы данных, хранимой в оперативной памяти. Для работы Дата акселератора требуется использование механизма копий баз данных.

Реализован сервис кластера серверов Сервис Дата акселератора.

Дата акселератор работает под управлением только в 64-разрядной операционной системы. Работа под управлением операционных систем Windows XP и Windows Vista не поддерживается.

Механизм копий базы данных требует лицензию КОРП.

Данная возможность включена в статусе бета-версии. Для использования сервиса Дата акселератора требуется лицензия на тестирование выделенной функциональности. При отсутствии лицензии на тестирование выделенной функицональности использование Дата акселератора будет невозможно.

Данная возможность не предоставлялась.Реализована возможность существенного ускорения формирования сложных аналитических отчетов.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Система взаимодействия.
Реализована возможность работы с файлами в системе взаимодействия. Сервер системы взаимодействия позволяет использовать следующие хранилища: Amazon S3, Google Cloud и другие хранилища, реализующие протокол Amazon S3.

На сервере системы взаимодействия реализована возможность задания ограничений на:

  • Размер одного загружаемого файла.
  • Суммарный размер загружаемых файлов в сутки.
  • Суммарный размер получаемых файлов в сутки.

Реализовано свойство СообщениеСистемыВзаимодействия.Вложения. Для менеджера системы взаимодействия реализованы методы: ПоддерживаетсяРаботаСВложениями(), ПодключитьОбработчикФормированияКоманд(), ОтключитьОбработчикФормированияКоманд().

Данная возможность не предоставлялась.Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
Реализована возможность проведения видеоконференций с количеством участников больше двух. Состав участников видеоконференции может изменяться в любой момент времени. Реализована поддержка видеоконференции между клиентскими приложениями «1С:Предприятие» версий 8.3.13 и 8.3.14. В этом случае видеоконференция может быть только в режиме «один на один».Данная возможность не предоставлялась.

Можно было использовать только видеозвонок (видеоконференция в режиме «один на один»).

Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь.
Средства разработки.
Для конфигуратора, работающего в режиме агента, реализованы следующие возможности (аналогичные возможностям командной строки запуска конфигуратора):
  • Выгрузка конфигурации в XML мобильной платформы.
  • Формирование подписи для мобильного клиента.
  • Выгрузка конфигурации мобильного клиента.
  • Выгрузка конфигурации или расширения в файл.
  • Загрузка конфигурации или расширения из файла.
  • Снятие конфигурации с поддержки.
  • Выгрузка информационной базы.
  • Загрузка информационной базы.
  • Удаление данных информационной базы.

Для конфигуратора, работающего в режиме агента, реализованы следующие возможности (данные возможности доступны только в режиме агента):

  • Создание пустого расширения.
  • Удаление расширения.
  • Получение свойств расширения.
  • Установка свойств расширения.

Реализована возможность отображения состояния выполнения длительных операций при работе в режиме агента (не для всех команд).

Расширен перечень ситуаций, которые описываются специальным кодом ошибки в поле error-type.

Расширен формат сообщений, которые возвращаются после выполнения команд в режиме агента.

Данные возможности не предоставлялись.Расширены возможности работы конфигуратора в режиме агента.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Кластер серверов.
Средства администрирования.
Реализована возможность управления кластером сервером из встроенного языка. Управление выполняется с использованием сервера ras, без использования технологии COM. Допускается подключение к кластеру серверов, не совпадающего по номеру версии с используемым клиентским приложением. Доступ к механизму администрирования предоставляется при работе на стороне тонкого клиента и на сервере.

Реализован объект АдминистрированиеСервера.

Данная возможность не предоставлялась.

Доступ к администрированию кластера серверов с помощью встроенного языка предоставлялся только с использованием COM-соединения и был доступен только на стороне сервера при работе под управлением ОС Windows. Версия администрируемого сервера должна была полностью совпадать с версией используемого для администрирования «1С:Предприятия».

Реализована возможность реализовать кроссплатформенный интерфейс администрирования кластера серверов «1С:Предприятия», не требующий точного совпадения версий клиентского приложения и кластера серверов. Стало возможно реализовать консоль кластера при работе под управлением ОС Linux. Стало возможно отказаться от консоли кластера, работающей под управлением Microsoft Management Console.
В документации данное изменение описано здесь.
Отображение информации.
Реализована возможность согласования словосочетания с числительным. Реализован метод глобального контекста ПолучитьСклоненияСтрокиПоЧислу().Данная возможность не предоставлялась.Упрощено формирование фраз, которые содержат какое-либо значение (числом или прописью) и согласованную с этим числом фразу.
Общие объекты.
Во встроенном языке реализована возможность решения систем линейных алгебраических уравнений. Реализован объект РасчетСистемЛинейныхУравнений.Данная возможность не предоставлялась.Реализована возможность ускорения расчетов в тех случаях, когда требуется решение больших систем линейных алгебраических уравнений.
В документации данное изменение описано здесь.
Отображение информации.
В библиотеку картинок добавлена картинка Прикрепить.В библиотеке картинок отсутствовала добавленная картинка.Расширен состав библиотеки картинок.
Расширение конфигурации.
Реализована возможность расширять состав значений заимствованного перечисления.

При удалении расширения, в котором расширен список значений перечисления, реквизиты объектов информационной базы, хранящие удаляемые значения, заполняются пустой ссылкой на перечисление.

Данная возможность не предоставлялась.Расширены возможности расширений по работе с перечислениями.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Для объектов метаданных, заимствованных в расширение, реализовано свойство Комментарий. Свойство предназначено для использования в процессе разработки расширения и не используется при формировании результирующей конфигурации и проверках применимости расширения.Данная возможность не предоставлялась.Стало возможно комментировать описывать назначение тех или иных объектов расширения непосредственно в самом расширении, не прибегая к сторонним инструментам.
В документации данное изменение описано здесь.
Расширение конфигурации.
Общие объекты.
В расширении конфигурации реализована возможность создания собственных параметров сеанса. Такие параметры сеанса могут использоваться в текстах ограничений доступа.Данная возможность не предоставлялась.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Регистры расчета.
Реализована возможность получить фактический период действия набора записей регистра расчета до записи этого набора. Для набора записей регистра расчета реализован метод ПолучитьФактическийПериодДействия().Фактический период действия записей рассчитывался платформой только при записи набора записей регистра расчета. За счет отказа от лишней записи набора записей регистра расчета улучшена параллельность работы с регистрами расчета и повышена производительность для некоторых сценариев применения.
Кластер серверов.
Для счетчиков потребления ресурсов реализована возможность отбора по признаку использования безопасного режима работы и профиля безопасности (добавлены новые типы фильтров).

Для выражений отбора счетчика потребления ресурсов реализована возможность сравнения на неравенство.

Для выражений отбора счетчика потребления ресурсов реализована возможность объединять «по И» несколько условий на один тип фильтра.

Данные возможности не предоставлялись.Расширены возможности анализа работы прикладного решения в клиент-серверном варианте.
В документации данное изменение описано здесь.
Система компоновки данных.
Для системы компоновки данных реализована возможность отображения картинок, расположенных в информационной базе. В отчете могут отображаться картинки, заданные в качестве навигационной ссылки на картинку и собственно картинкой, размещенной в реквизите типа ХранилищеЗначения.

Для объектов ОформлениеКомпоновкиДанных и ОформлениеЯчейкиТаблицыОбластиКомпоновкиДанных реализованы свойства ВыводитьКартинку, РазмерКартинки, ПоложениеТекстаОтносительноКартинки, ГоризонтальноеПоложениеКартинки, ВертикальноеПоложениеКартиинки.

В режиме совместимости с версией 8.3.13 поведение по умолчанию не изменилось.

Система компоновки данных не предоставляла возможность отображения картинок из информационной базы.Расширены оформительские возможности системы компоновки данных.
Диаграммы.
Реализована возможность редактировать состав серий и точек диаграмм. Для объектов ТочкиДиаграммы и СерииДиаграммы реализованы методы Вставить(), Сдвинуть(), Удалить(), Очистить().Данная возможность не предоставлялась.

При необходимости изменить одну точку или значение было необходимо заново заполнить диаграмму данными.

Расширены возможности диаграмм.

Например, стало возможно делать график с автоматической прокруткой, когда с определенным интервалом времени удаляется первая точка графика и добавляется последняя.

В документации данное изменение описано здесь.
Клиентское приложение.
Реализован пакетный режим работы тонкого и толстого клиентских приложений. Пакетный режим распространяется от начала запуска клиентского приложения до окончания работы обработчика ПередНачаломРаботыСистемы модуля приложения. После окончания работы обработчика пакетный режим автоматически отключается. В пакетном режиме запуска подавляется вывод любых диалогов системы.

Признаком пакетного режима работы клиентского приложения является команда командной строки запуска /DisableStartupDialogs. В документации отражены особенности поведения системы в пакетном режиме запуска клиентского приложения.

Реализован метод глобального контекста ЗапрещеноОткрытиеФорм().

В настройках параметров запуска клиентского приложения из конфигуратора реализована возможность запуска в пакетном режиме.

Если во время исполнения методов ЗапуститьПриложение()/НачатьЗапускПриложения() будут обнаружены ошибки времени исполнения, то при работе в пакетном режиме будет сформировано исключение.

Данная возможность не предоставлялась.

Пакетный режим запуска был доступен только при использовании конфигуратора.

Если во время исполнения методов ЗапуститьПриложение()/НачатьЗапускПриложения() будут обнаружены ошибки времени исполнения, то при работе на стороне сервера формировался диалог с ошибкой.

Реализована возможность организовывать такие сценарии запуска клиентских приложений, когда наличие интерактивных диалогов препятствовали запуску приложения и не позволяли «программно» отреагировать на проблемы запуска.
В документации данное изменение описано здесь, здесь и здесь.
Системные требования.
Реализована лицензия для проведения тестирования выделенной функциональности (программная лицензия). Данная лицензия является дополнением к серверной лицензии «1С:Предприятия». Лицензия для тестирования выделенной функциональности не дает права использования сервера «1С:Предприятия». Количество лицензий для тестирования выделенной функциональности должно быть не меньше, чем количество серверных лицензий в кластере серверов, на котором выполняется тестирование.

Необходимость лицензии для выполнения тестирования механизма определяется при анонсе соответствующего механизма.

Запрос на получение лицензии для тестирования выделенной функциональности следует направлять письмом по адресу betaplatform@1c.ru.

Для утилиты лицензирования реализована возможность работы с лицензиями для проведения тестирования выделенной функциональности.

Использование бета-версий механизмов не требовало наличие специальной лицензии.В некоторых случаях тестирование бета-версий механизмов платформы будет требовать специальной лицензии для тестирования выделенной функциональности.
В документации данное изменение описано здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Веб-клиент более не поддерживает конфигурации, которые используют интерфейс версии 8.2. При работе в веб-клиенте отключена возможность переключения интерфейса между интерфейсом версии 8.2 и интерфейсом Такси. Игнорируются команды командной строки запуска itdi и itaxi. Данные команды являются устаревшими и не должны больше использоваться. Вне зависимости от значения свойства НастройкиКлиентскогоПриложения.ВариантИнтерфейсаКлиентскогоПриложения всегда используется интерфейс Такси. Веб-клиент поддерживал использование интерфейса версии 8.2.Отключена поддержка устаревшего вида интерфейса клиентского приложения. Повышена стабильность работы веб-клиента.
В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
Во время осуществления видеозвонка реализована возможность независимого отключения видеокамеры и микрофона.Во время осуществления видеозвонка отключение видеокамеры приводило к одновременному отключению микрофона.Устранено некорректное поведение системы.
Командный интерфейс.
При отображении подсказки к разделам и командам командного интерфейса убрано отображение гиперссылки «Справка» в том случае, если для раздела или команды была задана справочная информация.

Однако справочная информация по разделу или команде по-прежнему доступна через окно отображения справочной информации.

В панели функций текущего раздела и меню функций отображается подсказка с пояснением или расширенным представлением для списков и объектов конфигурации.

Отображение подсказки выполнялось следующим образом:
  • Если для раздела была задана справочная информация, то в подсказке для этого раздела в панели разделов отображалась гиперссылка «Справка».
  • Если для команды была задана справочная информация, то в подсказке для этой команды в панели функций текущего раздела отображалась гиперссылка «Справка».
  • В меню функций у команд подсказка не отображалась.
  • В веб-клиенте подсказка для раздела в панели разделов содержала синоним раздела, а не пояснение.
  • В веб-клиенте подсказка для команды в панели функций текущего раздела содержала синоним команды, а не пояснение или расширенное представление для списков и объектов.
Ускорено отображение командного интерфейса в тонком клиенте. Унифицировано отображение подсказки для разделов и команд в различных клиентских приложениях.
В документации данное изменение описано здесь.
Расширение конфигурации.
Веб-клиент.
При работе в веб-клиенте, при наличии расширений в информационной базе, веб-браузер кеширует картинки следующим образом:
  • для картинок расширяемой конфигурации - для всех сеансов данной информационной базы;
  • для картинок расширения - для каждого сеанса.
При работе в веб-клиенте, при наличии расширений в информационной базе, веб-браузер кешировал все картинки конфигурации для каждого сеанса.Устранено некорректное поведение системы.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Диаграммы.
Оптимизирована работа с диаграммами, содержащими большое количество данных.

Рекомендуется проанализировать использование диаграмм в прикладных решениях и выполнить следующий рефакторинг:

  • первоначальное заполнение данными следует выполнять на сервере;
  • существенные изменения данных (включая полное заполнение) следует выполнять на сервере;
  • небольшие изменения данных можно выполнять на клиенте.
Производительность диаграмм, содержащих большое количество данных, была недостаточной.Ускорена работа диаграмм, отображающих большое количество данных.
Средства администрирования.
Ускорено открытие списка пользователей в конфигураторе. Ускорение будет особенно заметно при большом количестве пользователей и ролей.В информационной базе, содержащей большое количество пользователей и ролей, список пользователей открывался продолжительное время.Ускорено открытие списка пользователей в информационной базе с большим количеством пользователей.
Регистры бухгалтерии.
Регистры накопления.
Уменьшено время полного пересчета итогов для регистров бухгалтерии и накопления в следующих случаях:
  • пересчет итогов во время операции Тестирование и исправление из конфигуратора;
  • использование метода ПересчитатьИтоги() при выполнении следующих условий:
    • монопольный доступ к информационной базе;
    • наличие административных прав у пользователя, от имени которого выполняется пересчет итогов;
    • метод исполняется в сеансе, в котором не используется ни одного разделителя.
Полный пересчет итогов для регистров бухгалтерии и накопления занимал существенное время.Уменьшено время полного пересчета итогов для регистров бухгалтерии и накопления.
Полнотекстовый поиск.
Ускорен поиск выражений вида «слово*» в том случае, когда «слово» упоминается достаточно часто. Также уменьшена вероятность возникновения ошибки превышения допустимого количества слов поиска при попытке поиска часто возникающих выражений вида «слово*».

В режиме совместимости с версией 8.3.13 поведение не изменилось.

При выполнении поиска выражений вида «слово*», поиск могу не завершиться вовсе с ошибкой превышения количества допустимых слов поиска.Оптимизирован механизм полнотекстового поиска.
В документации данное изменение описано здесь.
Работа с СУБД.
Ускорено выполнение реструктуризации информационной базы при использовании СУБД Microsoft SQL Server и IBM DB2.Выполнение реструктуризации информационной базы при использовании СУБД Microsoft SQL Server и IBM DB2 требовало больше времени.Ускорено выполнение реструктуризации информационной базы при использовании СУБД Microsoft SQL Server и IBM DB2.
Работа с СУБД.
Уменьшилась вероятность одновременного закрытия множества соединений с Microsoft SQL Server, что положительно влияет на производительность работы с TempDB.Существовала вероятность одновременного закрытия множества соединений с Microsoft SQL Server, что приводило у существенному снижению производительности при работе с TempDB.Оптимизировано использование TempDB при работе с СУБД Microsoft SQL Server.
Регистры расчета.
Для регистра расчета реализован кластерный индекс по регистратору. Перестройка индекса будет выполнена при реструктуризации регистра расчета или при переиндексации во время выполнения операции тестирования и обновления.

Если при удалении записей из таблицы фактического периода действия не установлен отбор по измерениям регистра, то для запроса удаления не формируется соединение с основной таблицей регистра.

Для регистра расчета отсутствовал кластерный индекс.

При удалении записей из таблицы фактического периода действия, запроса удаления всегда содержал соединение с основной таблицей регистра.

Снижена вероятность табличной блокировки при удалении записей фактического периода действия регистра расчета.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Для тонкого клиента (при подключении по HTTP/HTTPS) реализована поддержка использования произвольного провайдера OpenID-аутентификации. Используемый провайдер должен поддерживать протокол OpenID Connect.Данная возможность не предоставлялась.

Использование произвольного провайдера OpenID-аутентификации было возможно только при использовании веб-клиента.

Расширен список вариантов аутентификации пользователя при использовании тонкого клиента.
В документации данное изменение описано здесь, здесь и здесь.
Клиентское приложение.
При использовании веб-клиента или тонкого клиента (при подключении по HTTP/HTTPS) реализована возможность использовать для аутентификации систему ЕСИА (единая система идентификации и аутентификации).

В описании провайдера OpenID Connect, в файле default.vrd (элемент <providers>), реализованы свойства dialect и crypto.

В тонком клиенте аутентификация с использованием ЕСИА возможно только в том случае, если информаицонная база опубликована на веб-сервере Apache.

Данная возможность не предоставлялась.Расширен список вариантов аутентификации пользователя.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с запросами.
Система компоновки данных.
При работе с запросом с помощью объекта СхемаЗапроса реализована возможность использования расширения языка запросов для системы компоновки данных.

Реализованов свойство СхемаЗапроса.РежимКомпоновкиДанных. Для объекта ЗапросВыбораСхемыЗапроса реализованы свойства ПоляВыбораКомпоновкиДанных, Характеристики. Реализовано свойство ОператорВыбратьСхемыЗапроса.ВыражениеОтбораКомпоновкиДанных. Реализовано свойство ТаблицаСхемыЗапроса.ПараметрыКомпоновкиДанных.

Для конструктора запросов, работающего в режиме «1С:Предприятия», реализована поддержка расширения языка запросов для системы компоновки данных.

Реализовано свойство КонструкторЗапроса.РежимКомпоновкиДанных.

Объект СхемаЗапроса не поддерживала работу с расширением языка запросов для системы компоновки данных.

Конструктор запросов, работающий в режиме «1С:Предприятие», не поддерживал работу с расширением языка запросов для системы компоновки данных.

Расширены возможности при работе с запросами, использующими расширения языка запросов для системы компоновки данных, при работе в режиме «1С:Предприятие».
В документации данное изменение описано здесь.
Кластер серверов.
При аварийном завершении менеджера кластера сохраняется информация о исполняющихся в данный момент фоновых заданиях и о результатах работы ранее завершенных фоновых заданий. Запуск и обработка регламентных заданий не прекращается.В случае аварийного завершения менеджера кластера:
  • Терялась информация о результатах выполнения всех ранее запущенных фоновых заданий и всех выполняемых в данный момент фоновых заданиях и все соответствующие им сообщения для всех информационных баз.
  • Приложение пользователя «зависало» на неограниченное время в случае, если пользователь ожидал завершения каких-либо фоновых заданий.
  • Выполнение регламентных заданий было невозможно в течении 1 минуты, пока информация о них не будет снова считана из информационных баз.
Повышена устойчивость работы кластера серверов в части работы с фоновыми и регламентными заданиями. При работе с фоновыми и регламентными заданиями пользователь не должен замечать аварийное завершение работы менеджера кластера.
В документации данное изменение описано здесь.
Динамический список.
Для динамического списка реализована возможность указания полей, которые будут использоваться в качестве ключевых полей выборки. Для объекта ДинамическийСписок реализованы свойства ВидКлюча и ПоляКлюча. Реализован объект КлючСтрокиДинамическогоСписка. В диалоге настройки запроса динамического списка реализована возможность настройки полей, участвующих в формировании ключа строки.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Рекомендуется пересмотреть все динамические списки, в которых не указана основная таблица или в качестве основной таблицы используется виртуальная таблица без ключа (все, кроме ДвиженияССубконто, ЗадачиПоИсполнителю, критерий отбора, таблицы среза регистра сведений) в пользу использования произвольного ключа с видом Значение поля или Ключ строки.

Данная возможность не предоставлялась.

Ключевые поля определялись используемой основной таблицей динамического списка.

Расширены возможности работы с динамическим списком с отсутствующей основной таблицей. Повышена производительность при использовании динамических списков с отсутствующей основной таблицей. Например, для динамического списка без основной таблицы, стало возможно использование группировки.
В документации данное изменение описано здесь и здесь.
Средства разработки.
При использовании конфигуратора в режиме агента, рабочие каталоги пользователя имеют цифровую нумерацию. Соответствие каталога и пользователя указывается в файле agentbasedir.json, который расположен в рабочем каталоге агента (параметр командной строки запуска AgentBaseDir).При использовании конфигуратора в режиме агента, рабочие каталоги пользователя включали имя пользователя в название каталога.По имени рабочего каталога невозможно определить имя пользователя, использующего конфигуратор в режиме агента. Сокращен путь к рабочему каталогу пользователя.
В документации данное изменение описано здесь.
Расширение конфигурации.
При заимствовании формы в расширение, заимствуются только ее элементы. После заимствования свойства элементов могут изменяться в редакторе формы из расширения в полном объеме. Остальные объекты формы (реквизиты, команды, параметры и т.д.) по умолчанию автоматически не заимствуются, следовательно свойства этих объектов формы не могут редактироваться. Для включения возможности редактирования требуемый объект следует добавить в расширение.

При заимствовании формы не выполняется заимствование родительского объекта конфигурации этой формы.

Работа с формами, добавленными в расширение в предыдущих версиях, не изменяется.

При заимствовании формы, в расширение добавлялся родительский объект конфигурации и все объекты расширения.Существенно упрощена работа с заимствованными формами объектов конфигурации. Упростилась адаптация расширений к новым версиям расширяемой конфигурации.
В документации данное изменение описано здесь, здесь и здесь.
Диаграммы.
Система компоновки данных.
При печати отчета, содержащего диаграмму, диаграмма всегда целиком печатается на одной странице. Для этого процессор вывода системы компоновки данных, для строк табличного документа, следующих за диаграммой, устанавливает свойство ВместеСоСледующим в значение Истина.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

При печати отчета, содержащего диаграмму, диаграмма могла быть «разрезана» разрывом страниц.Отчет стал лучше пригоден для использования в распечатанном виде.
В документации данное изменение описано здесь.
Управляемая форма.
В тонком, толстом и веб-клиентах, форма снимает блокировку объекта через 1 минуту после снятия признака модифицированности.В тонком, толстом и веб-клиентах, блокировка объекта снималась после закрытия формы.В ряде случаев повышена параллельность работы системы.
В документации данное изменение описано здесь.
Диаграммы.
Изменен автоматический расчет размера области построения для круговой диаграммы - добавлен запас места, для того, чтобы корректно отображался сектор, на который навели курсор мыши.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Область построения для круговой диаграммы занимала все свободное пространство. При наведении курсора мыши было возможно обрезание подсвечиваемой области сектора, на который навели курсор.Устранено некорректное поведение системы.
Расширение конфигурации.
При применении расширения конфигурации не контролируется количество параметров и наличие ключевого слова Знач перед параметром для обработчиков событий.При применении расширения конфигурация проверялось совпадение количества параметров и наличие ключевого слова Знач для обработчиков событий в расширении и расширяемой конфигурации. В расширении и расширяемой конфигурации должно было быть одинаковое количество параметров.Поведение расширения приведено в соответствие с поведением платформы для основной конфигурации. При вызове обработчика событий не проверяется точное совпадение состава параметров.
Система компоновки данных.
Псевдоним поля при генерации макета компоновки данных включает в себя псевдоним исходного поля и описание дополнительной информации (представление реквизита поля, агрегатной функции и т.д.).

В режиме совместимости с версией 8.3.13 поведение не изменилось. +

Псевдоним поля при генерации макета компоновки данных формировался по стандартным правилам правилам конструктора запросов.Псевдоним поля системы компоновки данных стал лучше соответствовать содержимому поля.
В документации данное изменение описано здесь.
Картинки.
Для картинок формата GIF реализована поддержка расширения формата «XMP DataXMP».Данная возможность не предоставлялась.Расширен список поддерживаемых вариантов картинок. Картинки формата GIF, которые сделаны с использованием продуктов компании Adobe, стали поддерживаться системой «1С:Предприятие».
В документации данное изменение описано здесь.
Работа с СУБД.
Технологический журнал.
При работе под управлением СУБД PostgreSQL, в технологический журнал (событие <plansql>) помещаются планы запросов для запросов UPDATE, DELETE и INSERT.При работе под управлением СУБД PostgreSQL, в технологический журнал (событие <plansql>) помещались планы запросов только для запроса SELECT.Упрощен подробный анализ работы прикладного решения при исполдьзовании СУБД PostgreSQL.
Средства разработки.
При выполнении операции сравнения модулей конфигураций, реализовано отображение метода, который, будучи неизменным, был перемещен в другую область или другое условие препроцессора.

+

При выполнении операции сравнения модулей конфигураций, методы, которые, будучи неизменными, был перемещен в другую область или другое условие препроцессора, отображались как измененные, что вводило в заблуждение.Сравнение модулей на встроенном языке стало более простым и понятным.
Табличный документ.
Диаграммы.
При отображении табличного документа в режиме редактирования в тонком клиенте, толстом клиенте и конфигураторе, для того, чтобы открыть свойство какой-либо области диаграммы, достаточно указать курсором мыши на требуемую область диаграммы.При отображении табличного документа в режиме редактирования в тонком клиенте, толстом клиенте и конфигураторе, для того, чтобы открыть свойство какой-либо области диаграммы, было необходимо вначале перейти в режим редактирования диаграммы с помощью двойного клика по диаграмме, а лишь затем указать нужную область.Взаимодействие с диаграммой в табличном документе стало более простым и понятным для пользователя.
Обновление конфигурации базы данных.
Реализовано отображение критических ошибок оптимизированного механизма обновления конфигурации базы данных в конфигураторе и в событии <EXCP> технологического журнала.Критические ошибки оптимизированного механизма обновления конфигурации базы данных не отображались в конфигураторе и технологическом журнале.Улучшена диагностика критических ошибок при использовании оптимизированного механизма обновления конфигурации базы.
Табличный документ.
Переработан механизм импорта данных из документов формата Microsoft Office OpenXML (Microsoft Excel 2007 и старше) и ODT (OpenDocument). Устранены ошибки, возникающие при импорте документов в данном формате.При импорте информации из документов в формате Microsoft Office OpenXML (Microsoft Excel 2007 и старше) и ODT (OpenDocument) могли возникать ошибки, в результате которых импорт становился невозможен.Устранено некорректное поведение системы.
Табличный документ.
При импорте табличного документа из файла формата XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) или ODS (OpenDocument), если у рисунка-фигуры и рисунка-картинки текст рисунка пустой или состоит только из пробелов, рисунок типа Текст в результирующем табличном документе не создается.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

При импорте табличного документа из файла формата XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) или ODS (OpenDocument), наблюдалось следующее поведение:
  • Для рисунка-фигуры импорт не выполнялся если текст рисунка был пустой, но импорт выполнялся, если текст рисунка состоял только из пробелов.
  • Для рисунка-картинки импорт выполнялся в любом случае, даже если текст рисунка был пустой или состоял только из пробелов.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
При частичной загрузке из XML корня конфигурации, если отсутствует файл внешнего свойства с информацией о настройках поддержки, то настройки поддержки сбрасываются. В результате конфигурация перестает находиться на поддержке.При частичной загрузке из XML корня конфигурации, если отсутствует файл внешнего свойства с информацией о настройках поддержки, то настройки поддержки не изменялись. В результате состояние поддержки конфигурации оставалось в том виде, в каком оно было до начала загрузки конфигурации из файлов.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
Значением свойства ТипРисунка для рисунка-примечания ячейки табличного документа является ТипРисункаТабличногоДокумента.Примечание.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Значением свойства ТипРисунка для рисунка-примечания ячейки табличного документа являлось ТипРисункаТабличногоДокумента.Текст.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
Изменилось отображение текста в ячейке табличного документа, если для ячейки установлено выравнивание «По ширине». Отображение текста стало корректным.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Отображение текста в ячейке табличного документа, если для ячейки установлено выравнивание «По ширине», выглядело как выравнивание «Влево».Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Генератор макета системы компоновки данных выводит в макет группировки поля ресурсов, даже если для вывода родительской группировки используется предопределенный макет и в выбранных полях не указаны ресурсы, а у дочерней группировки ресурсы указаны.

Возможно изменение внешнего вида формируемого отчета.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Генератор макета системы компоновки данных не выводил в макет группировки поля ресурсов, если для вывода родительской группировки использовался предопределенный макет и в выбранных полях не указаны ресурсы, а у дочерней группировки ресурсы указаны.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Технологический журнал.
В технологическом журнале реализованы свойства Dbms, Database, DBCopy для событий обращения к СУБД (DB2, DBMSSQL, DBPOSTGRS, DBORACLE), событий EXCP и SDBL.Данная возможность не предоставлялась.Упрощена диагностика выбора СУБД при работе с механизмом копий базы данных.
В документации данное изменение описано здесь.
Средства разработки.
При сравнении конфигураций реализована возможность просмотра различий в справочной информации. Реализована возможность сравнения справочной информации по выбранному языку (аналогично другим многоязычным механизмам платформы).При различии справочной информации выводилась только информация о том, что справочная информация различается. Было невозможно увидеть подробную информацию о различиях в справочной информации.Упрощено определение различий в составе справочной информации сравниваемых конфигураций.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Средства администрирования.
Программное лицензирование.
Утилита командной строки ring и модуль license этой утилиты выделены в отдельный программный продукт со своим дистрибутивом - Утилита лицензирования 1С:Предприятия. Дистрибутив доступен для использования на операционных системах Windows 7 и старше и Linux с архитектурами x86 и x86-64.

Архив с дистрибутивом имеет имя вида 1c-enterprise-license-tools-a.b.c+d-os-arch.zip. Архив с дистрибутивом поставляется вместе с дистрибутивом системы «1С:Предприятие».

Размещение установочных файлов утилиты ring и модуля license этой утилиты в каталоге ExtDst больше не выполняется.

Документация к установщику «1С:Предприятия» размещена на диске ИТС (см. здесь).

Утилита командной строки ring и модуль license этой утилиты поставлялись в составе дистрибутива «1С:Предприятие», в каталоге ExtDst. Установка утилиты была доступна после установки собственно «1С:Предприятия».Упрощено распространение и обновление утилиты ring и модуля license этой утилиты. Теперь установить (или обновить) утилиту лицензирования можно без необходимости устанавливать систему «1С:Предприятие», которая содержала дистрибутив утилиты.
В документации данное изменение описано здесь.
Программное лицензирование.
При активации программной лицензии (команда activate) и при формировании файла ответа на запрос (команда aсquire) с помощью утилиты ring реализована возможность указания альтернативного центра лицензирования. Выбор центра лицензирования выполняется в соответствии с параметром ExternalResourceMode файла conf.cfg.

Для команд ring license activate и ring license acqurie реализован параметр --conf-location, позволяющий указать каталог размещения файла conf.cfg, в соответствии с которым будет определяться используемый центр лицензирования.

Данная возможность не предоставлялась.

При работе с программными лицензиями всегда использовался один центр лицензирования.

Выбор используемого центра лицензирования сделан аналогично выбору используемых служебных ресурсов. Поведение стало идентичным.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Отображение информации.
Клиентские приложения, работающие под управление ОС Windows, для работы со справочной системой, синтакс-помощником, а также с полем HTML-документа, планировщиком, форматированным документом и редактором HTML-документа используют библиотеку WebKit. Microsoft Internet Explorer для данных целей больше не используется.

Библиотека поставляется вместе с платформой и не требует дополнительной установки.

Типом значения свойства ПолеHTMLДокумента.Документ стал ВнешнийОбъект. Изменилась DOM-модель, которая доступна при обращении к данному свойству.

Рекомендуется провести анализ использования элемента формы ПолеHTMLДокумента и исправить реализацию в том случае, если реализация использовала возможности, которые специфичны только для Microsoft Internet Explorer.

Клиентские приложения, работающие под управление ОС Windows, для работы со справочной системой, синтакс-помощником, а также с полем HTML-документа, планировщиком, форматированным документом и редактором HTML-документа использовали Microsoft Internet Explorer.Отображение и работа с HTML-документом стала единой, вне зависимости от используемой операционной системы.
В документации данное изменение описано здесь.
Работа с информационными базами.
Реализована возможность устанавливать год начала столетия для целей корректного определения года при вводе этого значения двумя цифрами. Дата начала столетия по умолчанию изменена с 1930 на 1950 год. Это означает. что ввод значения 49 будет трактоваться как 2049 год, а ввод значения 50 - как 1950 год. Год начала столетия задается в разрезе независимых разделителей.

Реализованы методы глобального контекста УстановитьНачалоСтолетияИнформационнойБазы(), ПолучитьНачалоСтолетияИнформационнойБазы(), НачалоСтолетияСеанса().

Годом начала столетия для целей корректного определения года при вводе этого значения двумя цифрами выступал 1930 год. Средств для изменения этого значения не предоставлялось.По умолчанию поведение системы при вводе значения года в дате двумя цифрами стало более логичным. Стало возможно устанавливать год начала столетия индивидуально в каждом конкретном случае (в зависимости от действующих предпочтений).
В документации данное изменение описано здесь.
Веб-клиент.
Средства разработки.
Для подключения веб-клиента в режиме отладчика к файловой информационной базе, опубликованной на веб-сервере, необходимо, чтобы информационная база была опубликована с разрешенной возможностью отладки. В противном случае отладка будет невозможна.

В том случае, если для веб-клиента требуется отладка с использованием файлового варианта информационной базы, рекомендуется заново выполнить публикацию, указав в настройках публикации возможность отладки.

Отладка веб-клиента для файлового варианта, была возможна при любом состоянии признака отладки в настройках публикации.Устранено некорректное поведение системы.
Расширение конфигурации.
Права доступа.
Изменена схема взаимодействия между ролями и расширениями:
  • У пользователя есть доступ ко всем объектам расширения, если в расширении и расширяемой конфигурации нет ролей.
  • Свойство роли Устанавливать права для новых объектов (в расширяемой конфигурации) действует и на объекты расширения.
  • Свойство роли Устанавливать права для реквизитов и табличных частей по умолчанию (в расширяемой конфигурации) действует и на объекты расширения.
  • Свойство роли Устанавливать права для реквизитов и табличных частей по умолчанию (в собственной роли расширения) действует на реквизиты и табличные части заимствованных объектов расширения.

Заимствование роли в расширение необходимо только в том случае, если требуется настроить права на объекты расширения, которые отличаются от прав по умолчанию для расширяемой конфигурации.

Реализована возможность расширять свойство конфигурации ОсновныеРоли.

В режиме совместимости расширения с версией 8.3.13 поведение не изменилось.

Использовалась следующая схема взаимодействия между ролями и расширениями:
  • У пользователя был доступ ко всем объектам расширения, если в расширении не было ролей.
  • Для установки прав доступа на объекты (включая реквизиты и табличные части) расширения было необходимо заимствовать в расширение все изменяемые роли.
Упрощена схема взаимодействия ролей и объектов расширения. Логика взаимодействия стала более простой и понятной.
В документации данное изменение описано здесь, здесь и здесь.
Диаграммы.
Система компоновки данных.
Реализована возможность управлять способом отображения и видом подсказки, отображаемой на диаграмме. Реализована возможность отображения информационной линии на диаграмме одновременно с отображением подсказки.

Для объекта Диаграмма реализованы свойства ОтображениеПодсказкиЗначений, ЗаполнениеПодсказкиЗначений, ОтображатьВсплывающуюИнформационнуюЛиниюТочек и ОтображатьВсплывающуюИнформационнуюЛиниюЗначений.

Реализована возможность выделения (интерактивного и программного) одного или нескольких (включая несмежные) элементов диаграммы.

Для объекта Диаграмма реализовано свойство РежимВыделения. Для расширения поля формы для поля диаграммы реализовано событие ПриАктивизации, а также реализованы методы ПолучитьВыделенныеЭлементы() и УстановитьВыделенныеЭлементы(). Для объекта РисунокТабличногоДокумента реализованы методы ПолучитьВыделенныеЭлементы() и УстановитьВыделенныеЭлементы().

Для объектов ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных, ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы свойства ТипДиаграммы.ОтображениеПодсказкиЗначений, ТипДиаграммы.ЗаполнениеПодсказкиЗначений, ТипДиаграммы.ОтображатьВсплывающуюИнформационнуюЛиниюТочек, ТипДиаграммы.ОтображатьВсплывающуюИнформационнуюЛиниюЗначений, ТипДиаграммы.РежимВыделения.

При работе с диаграммой были доступны только следующие операции:
  • Отображение всплывающей подсказки с текстом при наведении на элемент диаграммы.
  • Вызов события Выбор при двойном щелчке мыши на элементе диаграммы.
  • Вызов события ОбработкаРасшифровки при двойном щелчке мыши на значении, точке, серии диаграммы, для которых установлено значение расшифровки.
Расширены интерактивные возможности работы с диаграммами.
В документации данное изменение описано здесь, здесь и здесь.
Управляемая форма.
Значение Авто для свойства ВыборГруппИЭлементов поля ввода формы трактуется как Элементы, если поле отображает значение ссылочного типа.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Значение Авто для свойства ВыборГруппИЭлементов поля ввода формы трактовалось как ГруппыИЭлементы, если поле отображает значение ссылочного типа.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Генератор макета компоновки данных, при создании запроса, используемого для получения набора, пытается использовать язык запросов СУБД для агрегации данных. Для агрегации данных используются функции СУММА(), МАКСИМУМ() и МИНИМУМ() языка запросов, применяемые к одному полю.

Реализовано свойство НаборДанныхЗапросСхемыКомпоновкиДанных.ИспользоватьГруппировкиЗапросаЕслиВозможно, которое управляет возможностью вычисления агрегатов с помощью языка запросов.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Система компоновки данных не использовала группировку в запросах для агрегации данных, за исключением случаев, когда в запросе явно указывалось предложение СГРУППИРОВАТЬ ПО.В ряде случаев ускорено получение данных системой компоновки данных.
В документации данное изменение описано здесь.
Система компоновки данных.
В системе компоновки данных изменен алгоритм сравнения массивов, таблиц значений и других не примитивных типов:
  • при сравнении массивов, результатом сравнения выступает результат последовательного сравнения элементов массива;
  • при сравнении таблиц значений, результатом сравнения выступает результат последовательного сравнения элементов таблиц значений;
  • при сравнении объектов, типы которые не являются примитивными, ссылочными, массивами или таблицами значений, сравнение выполняется следующим образом:
    • при выполнении упорядочивания используется строковое представление упорядочиваемых объектов;
    • при выполнении операций «=» или «<>», в качестве результат сравнения используется проверка на то, что объект сравнивается сам с собой;генерируется исключение, если в выражении сравнения используются операции «<«, «>», «<=», «>=».

В режиме совместимости с версией 8.3.13 поведение не изменилось.

При сравнении друг с другом объектов одного типа (включая массив и таблицу значений), не примитивного типа, не ссылочного типа, в качестве результата сравнения использовалось сравнение адресов расположения сравниваемых объектов в оперативной памяти компьютера.

+

Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Средства администрирования.
Для объекта IClusterInfo реализованы свойства ErrorsCountThreshold (допустимое количество ошибок сервера, которое не считается потенциальной проблемой) и KillProblemProcesses (принудительно завершать проблемные процессы).Данная возможность не предоставлялась.Устранено некорректное поведение системы.
Работа с запросами.
В запросе, не содержащем в списке выборки реквизитов табличной части, но содержащем сравнение нескольких реквизитов табличной части, объединенных «по И», условия исполняются вместе для каждой строки табличной части.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

В запросе, не содержащем в списке выборки реквизитов табличной части, но содержащем сравнение нескольких реквизитов табличной части, объединенных «по И», условия исполнялись изолировано, что могло приводить к неверным результатам сравнения.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Картинки.
Реализована возможность выполнять изменение параметров картинок с помощью встроенного языка: формат, размер, плотность точек, глубину цвета и т.д. Изменена логика работы с картинками:
  • Объект Картинка служит только для отображения информации о картинке с возможностью прочитать или записать картинку.
  • Для выполнения преобразований картинки реализован объект ОбрабатываемаяКартинка.

Для объекта Картинка реализованы методы Ширина(), Высота(), ГлубинаЦвета(), ОттенкиСерого(), ПлотностьПоГоризонтали(), ПлотностьПоВертикали(), РазмерФайла().

Метод Картинка.Преобразовать() является устаревшим и не рекомендуется для использования. Объект ОбработкаКартинок является устаревшим и не рекомендуется для использования. Методы объекта ОбработкаКартинок имеют полные аналоги в объекте ОбрабатываемаяКартинка.

Рекомендуется выполнить анализ прикладных решений и отказаться от использования устаревших методов и объектов. +

Данные возможности не предоставлялись.

Можно было только изменить формат картинки, без изменение остальных характеристик.

Стало возможно выполнять преобразование картинки, хранимой в информационной базе, в том случае, если необходимо поставлять в сторонние организации картинки, к которым предъявляются особые требования.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Название типа, описывающего форму клиентского приложения.
  • УправляемаяФорма.
  • ФормаКлиентскогоПриложения.
Обработчик расширения поля формы табличного документа, который вызывается при выделении области табличного документа или какого-ли действия в диаграмме.

В режиме совместимости с версией 8.3.13 вызывается обработчик со старым наименованием.

Рекомендуется изменить наименование обработчиков событий, если они используются в прикладном решении.

  • ПриАктивизацииОбласти().
  • ПриАктивизации().
Колонки в конструкторе запросов, на вкладке Компоновка данных.Использовать дочерниеИспользовать реквизиты

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Мобильная платформа.
Средства разработки.
На мобильной платформе реализована возможность выполнения отчетов, использующих систему компоновки данных (включая диалоги настройки системы компоновки данных).

При разработке прикладного решения, работающего на мобильной платформе, становятся доступными свойства конфигурации Основная форма отчета, Основная форма настроек отчета, Основная форма варианта отчета.

Формы настроек системы компоновки данных адаптированы для работы на мобильных устройствах.

Данная возможность не предоставлялась.

На мобильной платформе не были доступны отчеты. Имелась возможность только программной работы с системой компоновки данных (без интерактивных возможностей).

На мобильной платформе реализована возможность использования отчетов (включая интерактивные возможности по настройке отчетов).
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
При сборке мобильного приложения реализована возможность исключать из собираемого приложения часть функциональность работы с рекламой. Для этого необходимо выключить флажок Реклама в требуемых разрешениях мобильного приложения.Данная возможность не предоставлялась.Упрощена публикация мобильного приложения в магазине мобильных приложений.
Мобильная платформа.
Мобильный клиент.
В мобильной версии «1С:Предприятие» реализована доступность объектов ДиалогВыбораШрифта и ДиалогВыбораЦвета.Объекты ДиалогВыбораШрифта и ДиалогВыбораЦвета были недоступны в мобильной версии «1С:Предприятия».В мобильной версии расширены возможности работы с цветом и шрифтом.
Мобильная платформа.
Сборщик мобильных приложений.
Ускорено создание информационной базы при первом запуске мобильного приложения (после установки) на мобильном устройстве. Указанное ускорение будет наблюдаться только в том случае, если мобильное приложение собрано с использованием выгрузки (файл 1cema.zip), выполненной в конфигураторе версии 8.3.14.

Изменен формат выгрузки конфигурации из конфигуратора. Выгрузка конфигурации в файле .xml более не поддерживается.

Сборщик мобильных приложений версии 2.0.8 и младше не поддерживает конфигурации, выгруженные в новом формате.

+

Создание информационной базы, выполняемое при первом запуске мобильного приложения на мобильном устройстве, занимало существенно больше времени.Реализована возможность ускорить первый запуск мобильного приложения на мобильном устройстве.
Специальные возможности мобильного устройства.
Мобильная платформа.
Реализована возможность работать с сервисами покупок в приложениях на мобильной платформе, работающих под управлением ОС Windows (сервис Windows InAppPurchase).

Реализовано свойство СервисВстроенныхПокупок.WindowsInAppPurchase. Для объекта КвитанцияВстроеннойПокупки реализован конструктор.

Реализована возможность работать с сервисами покупок в приложениях на мобильной платформе, были доступны только для приложений, работающих под управлением ОС iOS и Android. Реализована возможность использовать сервис встроенных покупок при работе под управлением ОС Windows.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Реализована возможность показывать видеорекламу с вознаграждением.

Реализована возможность получать статус рекламного объявления.

Для объекта МенеджерОтображенияРекламы реализованы методы ПолучитьСтатусРекламы(), УстановитьИдентификаторВидеообъявленияСВознаграждением(), ПолучитьИдентификаторВидеообъявленияСВознаграждением(), ПоказатьВидеообъявлениеСВознаграждением(), НачатьЗагрузкуПолноэкраннойРекламы(), НачатьЗагрузкуРекламногоБаннера(), НачатьЗагрузкуВидеообъявленияСВознаграждением().

Данная возможность не предоставлялась.Расширены возможности использования рекламы в мобильном приложении.
В документации данное изменение описано здесь, здесь и здесь.
Отображение информации.
Мобильная платформа.
В мобильной платформе реализована возможность создавать пользовательские стили и элементы стиля. Для реализации данной возможности необходимо использовать для сборки конфигурацию, выгруженную из конфигуратора системы «1С:Предприятие» версии 8.3.14 и старше.

При формировании цветовой схемы мобильного приложения не используются свойства стиля ЦветНавигации, ЦветДополнительнойНавигации и ЦветВажного.

Данная возможность не предоставлялась.Расширены возможности управления внешним видом мобильного приложения.
В документации данное изменение описано здесь.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Работа с запросами.
Улучшено сообщение, возникающее при попытке создания временной таблицы в запросе в том случае, если установленный менеджер временных таблиц уже закрыт к моменту выполнения запроса. В качестве ошибки выступает текст Попытка использования закрытого менеджера временных таблиц.Сообщение, возникающее при попытке создания временной таблицы в запросе в том случае, если установленный менеджер временных таблиц уже закрыт к моменту выполнения запроса, вводило в заблуждение. Текст ошибки был следующим Не установлен менеджер временных таблиц.Устранено некорректное поведение системы.
Система компоновки данных.
Генератор макетов системы компоновки данных, при выводе полей в макеты группировок диаграмм, применяет условное оформление ко всем выводимым полям. Таким образом, при выводе отчета, созданного при помощи системы компоновки данных, условное оформление, применяемое к полям-ресурсам, будет отрабатываться и в диаграмме.

В результате может измениться внешний вид отчета, если в нем используется диаграмма, в которой используются ресурсы с настроенным условным оформлением.

Генератор макетов системы компоновки данных, при выводе полей в макеты группировок диаграмм, применял условное оформление только к полям, которые не являются ресурсами.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если расшифровка отчета запрашивается из отчета, отображаемого в компактном режиме, то и отчет-расшифровка также будет отображаться в компактном режиме.

Необходимость сжатия результата сохраняется в соответствующей настройке. Имя ключа настройки зависит от используемого клиентского приложения.

Для формы отчета реализован параметр РежимОтображенияРезультата, который позволяет явным образом указать режим отображения отчета.

Реализован метод ПолучитьРекомендуемуюШиринуСжатия(), возвращающий ширину поля табличного документа. Полученное значение можно использовать в качестве параметра метода табличного документа ПреобразоватьВКомпактныйДокумент().

Отчет-расшифровка, который открывался из отчета, не учитывал режим отображения отчета (компактный или обычный).Отчет-расшифровка отображается на клиентском устройстве в том же режиме, что и отчет, которого эта расшифровка вызывается.
В документации данное изменение описано здесь.
Работа в macOS.
Клиентское приложение.
Средства администрирования.
Реализован дистрибутив тонкого клиента, работающего под управлением ОС macOS.

При работе под управлением ОС macOS, реализована возможность подбора версии и типа клиентского приложения.

Реализована интерактивная программа удаления клиентского приложения.

Изменена структура директорий в каталоге Программы для ОС macOS.

Изменены места расположения некоторых файлов системы программ «1С:Предприятие».

Реализована возможность создания самораспаковывающегося архива (DMG-образ) клиентского приложения для размещения на веб-сайте. В состав архива можно поместить конфигурационный файл 1cestart.cfg, содержащий настройки, необходимые для установки, запуска и обновления клиентского приложения. Созданный исполняемый файл предназначен для использования только в ОС macOS. Реализована утилита 1CEClientSetupMake (см. здесь).

Отсутствовал дистрибутив тонкого клиента для ОС macOS. При запуске клиентского приложения отсутствовала возможность подбора версии запускаемого клиентского приложения, а подбор типа запускаемого клиентского приложения выполнялся только в рамках одной версии.

Структура директорий в каталоге Программы была другой.

Отсутствовала утилита 1CEClientSetupMake.

Упрощено администрирования клиентского приложения при работе под управлением ОС macOS.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа в macOS.
Клиентское приложение.
Средства администрирования.
При работе под управлением ОС macOS, реализована возможность обновления клиентского приложения по сети. В диалоге публикации прикладного решения на веб-сервере реализовано поле для указания расположения дистрибутива клиентского приложения для ОС macOS и переименованы поля указания дистрибутивов клиентского приложения для ОС Windows (разной разрядности).

Для конфигурационного файла conf.cfg реализованы параметры PublishDistributiveLocationMacOS64, PublishDistributiveLocationWindows32, PublishDistributiveLocationWindows64. Параметры PublishDistributiveLocation32 и PublishDistributiveLocation64 конфигурационного файла conf.cfg объявлены устаревшими и не рекомендуются для использования.

Для элемента <point> конфигурационного файла default.vrd реализованы атрибуты pubdstmac64, pubdstwin32, pubdstwin64. Атрибуты pubdst, pubdst32 и pubdst64 элемента <point> конфигурационного файла default.vrd объявлены устаревшими и не рекомендуются для использования.

При работе под управлением ОС macOS реализована возможность использования программ запуска, расположенных на сетевых накопителях.

Для Web-сервиса получения дистрибутива клиентского приложения реализована возможность получать дистрибутив клиентского приложения для ОС macOS.

Данные возможности не предоставлялись.Упрощено обновление клиентского приложения при необходимости выполнить такую процедуру, например, в случае обновления версии сервера «1С:Предприятия».
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Кластер серверов.
Автономный сервер.
В конфигурационном файле автономного сервера реализованы параметры, отвечающие за расположение дистрибутивов клиентского приложения для ОС Windows и macOS: win32, win64, mac64. Параметры x86 и x86_64 объявлены устаревшими и не поддерживаются.Конфигурационный файл автономного сервера обеспечивал указание расположения дистрибутивов клиентского приложения только для ОС Windows.Автономный сервер стал поддерживать возможность обновления клиентского приложения для ОС macOS.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Результат сериализации табличного документа не зависит от того, передавался документ между клиентом и сервером или нет. Получившийся документ всегда имеет одинаковую структуру.

Данное изменение не влияет на внешний вид табличного документа и работу с ним с помощью встроенного языка.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Результат сериализации табличного документа зависел от того, передавался документ между клиентом и сервером или нет. Получившиеся документы могли иметь различную структуру.Упрощено сравнение табличных документов, сериализованных в XML-документ.
Мобильный клиент.
Система взаимодействия.
В мобильном клиенте реализована поддержка передачи файлов с помощью системы взаимодействия.Данная возможность не предоставлялась.Для мобильного клиента реализована поддержка новых возможностей системы взаимодействия.
Мобильная платформа.
Сборщик мобильных приложений.
Реализован новый формат выгрузки конфигурации, предназначенной для использования в сборщике мобильных приложений. В сборщике мобильных приложений (версия 2.0.9 и старше) реализована поддержка нового формата выгрузки конфигурации. Сборщик мобильных приложений (версия 2.0.8 и младше) не поддерживает работу с новым форматом выгрузки.

Реализовано ускорение первого запуска собранного мобильного приложения, если для сборки используется конфигурация, выгруженная конфигуратором версии 8.3.14.

Данные возможности не предоставлялись.

Первый запуск собранного мобильного приложения требовал больше времени.

Мобильное приложение, собранное с использованием нового формата выгрузки, будет выполнять первый запуск на мобильном устройстве за меньшее время.
Сборщик мобильных приложений.
Для мобильного приложения, включающего несколько конфигураций, реализована возможность задания представления приложения (на нескольких языках). Заданное представление будет автоматически использоваться для создания новых версий мобильного приложения.Представление каждой новой версии мобильного приложения, состоящего из нескольких конфигураций, формировалось по представлению первой конфигурации, используемой для сборки. Автоматически заданное представление надо было каждый раз изменять вручную.Упрощено создание представления для мобильного приложения, состоящего из нескольких конфигураций.
В документации данное изменение описано здесь.
Табличный документ.
Работа в ОС Linux.
Кластер серверов.
Ускорены операции, выполняемые с табличным документом на сервере «1С:Предприятия» в том случае, если кластер серверов работает под управлением ОС Linux.Операции, выполняемые с табличным документом на сервере «1С:Предприятия», работающего под управлением ОС Linux, занимали больше времени.Ускорено открытие форм, содержащих табличный документ, а также выполнение операций по работе с табличным документом на стороне сервера «1С:Предприятия» в том случае, когда кластер серверов функционирует под управлением ОС Linux.
Работа с СУБД.
При работе СУБД PostgreSQL под управлением ОС Windows, устранено ограничение на использование не более 1200 одновременно открытых файлов каждым процессом PostgreSQL (параметр СУБД max_files_per_process).При работе СУБД PostgreSQL под управлением ОС Windows, каждый процесс PostgreSQL имел ограничение в 1200 одновременно открытых файлов.Ускорена работа СУБД PostgreSQL при использовании больших конфигураций (например 1С:ERP).
Выгрузка/загрузка конфигурации в файлы.
При выгрузке конфигурации в файлы в «1С:Предприятии» версии 8.3.14 и старше (формат выгрузки 2.8 и старше), событие расширения поля формы табличного документа, который вызывается при выделении области табличного документа или какого-ли действия в диаграмме, имеет имя OnActivate, вне зависимости от режима совместимости.

При загрузке из выгрузки с версией формата 2.8 и младше, имена событий OnActivate и OnActivateArea считаются эквивалентными.

Для события расширения поля формы табличного документа, который вызывается при выделении области табличного документа или какого-ли действия в диаграмме, имя, которое формировалось в файле выгрузки, зависело от режима совместимости конфигурации.Имя события элемента формы не зависит от режима совместимости конфигурации.
Динамический список.
При работе в тонком клиенте, для колонки динамического списка доступны варианты поиска по подстроке и по части строки, если тип колонки является составным.При работе в тонком клиенте, для колонки динамического списка были недоступны варианты поиска по подстроке и по части строки, если тип колонки является составным.Устранено некорректное поведение системы.
Сборщик мобильных приложений.
Во время сборки мобильного приложения для работы под управлением ОС Android, реализовано более корректная установка размера оперативной памяти, используемой Java для сборки.

Если для сборки в 64-разрядном окружении используется 32-разрядная версия Java, в журнал сборки записывается предупреждение с рекомендацией указать 64-разрядную версию Java в настройках сборщика мобильных приложений.

Во время сборки мобильного приложения для работы под управлением ОС Android, установка размера оперативной памяти, используемой Java для сборки, выполнялась не всегда корректно. Это могло приводить к ошибке сборки, связанной с нехваткой оперативной памяти, используемой Java.

Если для сборки в 64-разрядном окружении используется 32-разрядная версия Java, в журнал сборки не записывалась рекомендация установить 64-разрядную версию Java в настройках сборщика мобильных приложений.

Уменьшено количество ошибок сборки мобильного приложения для работы под управлением ОС Android, связанных с нехваткой оперативной памяти для работы сборочной инфраструктуры.
Управляемая форма.
Если при работе в тонком или толстом клиентах (в интерфейсе Такси) у поля формы установлен режим выбора из списка, а в обработчике события НачалоВыбора выполнен отказ от стандартной обработки и данные выбора не заполнены, то выпадающий список не будет отображаться. В веб-клиенте поведение не изменилось.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Если при работе в тонком или толстом клиентах (в интерфейсе Такси) у поля формы установлен режим выбора из списка, а в обработчике события НачалоВыбора выполнен отказ от стандартной обработки и данные выбора не заполнены, то выпадающий список отображался заполненным данными из списка выбора.

В веб-клиенте список, при указанных условиях, не отображался.

Устранено незапланированное поведение системы.
Расширение конфигурации.
Для расширения конфигурации реализовано свойство ОсновныеРоли. Данное свойство позволяет указать роли, которые описывают доступность объектов расширения при пустом списке пользователей.

Для расширения конфигурации реализовано свойство ИспользоватьОсновныеРолиДляВсехПользователей. Данное свойство позволяет указать, что в подключаемом расширении любой пользователь будет обладать правами, заданными основными ролями расширения. Редактирование данного свойства выполняется в конфигураторе (в списке расширений) и с помощью стандартной функции управления расширениями.

При настройке прав доступа пользователя в конфигураторе, стало доступно полное имя роли, которая добавлена расширением конфигурации.

При создании расширения, в нем автоматически создается собственная роль, предоставляющая все права на собственные объекты расширения. Эта роль автоматически указывается в свойство расширения ОсновныеРоли. Ограничений на редактирование данной роли не накладывается.

В расширении, подключенном для файлового варианта информационной базы в безопасном режиме, невозможно предоставить права доступа для объектов расширяемой конфигурации. В режиме совместимости расширения конфигурации с версией 8.3.13 поведение не изменилось.

Для расширения конфигурации было невозможно указать список основных ролей.

Во время настройки прав пользователя в конфигураторе было недоступно название роли, которая добавлена расширением конфигурации.

При создании расширения конфигурации не создавалась роль, которая по умолчанию предоставляет все права для собственных объектов расширения.

В расширении, подключенном для файлового варианта информационной базы в безопасном режиме, было возможно предоставить права доступа для объектов расширяемой конфигурации.

Упрощена работе с правами доступа в расширениях конфигурации.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
Сборщик мобильных приложений.
Реализована возможность отправки PUSH-уведомлений для сервисов Windows Push Notification Services (WNS) и Firebase Cloud Messaging (FCM) с помощью вспомогательного сервиса фирмы «1С» https://pushnotifications.1c.com.

В сборщике мобильных приложений реализована поддержка новых возможностей вспомогательного сервиса фирмы «1С» по отправки PUSH-уведомлений.

Данная возможность не предоставлялась.

Вспомогательный сервис фирмы «1С» по отправке PUSH-уведомлений поддерживал работу только с сервисами Google Cloud Messaging (GCM) и Apple Push Notification Service (APNs).

Возможности вспомогательного сервиса фирмы «1С» по отправке PUSH-уведомлений приведены в соответствие с возможностями мобильной версии «1С:Предприятие».
Мобильная платформа.
Мобильный клиент.
В мобильной версии «1С:Предприятие» реализована поддержка всплывающей группы формы и группы формы, у которой свойство Объединенная установлено в значение Ложь.Данные возможности не предоставлялась.Расширены возможности настройки форм мобильной версии «1С:Предприятия».
Работа с запросами.
Функция ТипЗначения() языка запросов, применяемая к выражению, содержащее поле ЭтоГруппа, возвращает правильное значение.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Функция ТипЗначения() языка запросов, применяемая к выражению, содержащее поле ЭтоГруппа, возвращала неверное значение. Результат вычислялся так, как будто значение поля ЭтоГруппа содержало инвертированное значение.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
Функция языка запросов ТипЗначения() возвращает корректное значение в том случае, если в выражении параметра функции участвует как виртуальное поле, так и значение примитивного типа.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

Функция языка запросов ТипЗначения() возвращала некорректное значение в том случае, если в выражении параметра функции участвует как виртуальное поле, так и значение примитивного типа.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система взаимодействия.
Поиск пользователей в системе взаимодействия выполняется только по началу слов.

Улучшен поиск в заголовках неконтекстных групповых обсуждений и списке участников обсуждений «один на один». Более высоко в результатах поиска отображаются обсуждения, в которых:

  • существуют недавние сообщения (исходя из даты сообщения);
  • искомая строка находится в начале слова.
Поиск пользователей в системе взаимодействия выполнялся по вхождению строки (по подстроке).

Результат поиска формировался в порядке нахождения обсуждений в базе системы взаимодействия.

Улучшен механизм поиска в системе взаимодействия.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Системные требования.
Прекращена поддержка операционных систем Windows 8.1 и Windows Phone 8.1 мобильной версией системы «1С:Предприятие».

Реализована поддержка операционной системы Windows 10 для архитектуры ARM.

Изменен состав дистриубтива мобильной версии системы «1С:Предприятие» (файл mobile.zip).

Сборщик мобильных приложений не сможет собирать мобильные приложения для операционных систем Windows 8.1 и Windows Phone 8.1 с использованием мобильной версии системы «1С:Предприятие» версии 8.3.14 и старше.

Мобильная версия системы «1С:Предприятие» поддерживала работу с операционными системами Windows 8.1 и Windows Phone 8.1.

Мобильная версия системы «1С:Предприятие» не поддерживала работу с операционной системой Windows 10 для архитектуры ARM.

Актуализирован список поддерживаемых версий операционной системы Windows.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Реализовано свойство АдминистрированиеМенеджераКластера.ИдентификаторМенеджераКластера.Данная возможность не предоставлялась.Стало возможно однозначно идентифицировать менеджер кластера при работе через объект АдминистрированиеСервера.
Система компоновки данных.
При добавлении отбора в запрос набора данных схемы компоновки данных, содержащего объединения, отбор обязательно добавляется во все части объединения, если у набора данных включено автоматическое заполнение доступных полей или поле, к которому применяется отбор, получается через точку от поля, доступного для отбора.

Кроме того, если группа элементов отбора содержала поле, которое было недоступно в одном из объединений, и другое поле, которое было доступно и при этом в другой части объединения все поля были доступными, то такой отбор будет применен и в той части, в которой он был недоступен, с заменой недоступных полей на NULL.

Если в отчете или динамическом списке используется запрос, содержащий объединения и нужно, чтобы отбор на некоторое поле помещался только в определенные части объединения, то рекомендуется отключить для набора данных автоматическое заполнение доступных полей и добавить требуемое поле только в нужные части объединения.

В режиме совместимости с версией 8.3.13 поведение не изменилось.

При добавлении отбора в запрос набора данных схемы компоновки данных, содержащего объединения, отбор обязательно добавлялся во все части объединения, если отбор удалось поместить хотя бы в одну часть объединения. При этом, в тех частях объединения, в которых отбор применить не удавалось из-за отсутствия в них полей, использующихся в отборе, в добавляемые условия вместо отсутствующих полей проставлялось выражение NULL.

Кроме того, если группа элементов отбора содержала поле, которое было недоступно в одном из объединений, и другое поле, которое было доступно и при этом в другой части объединения все поля были доступными, то такой отбор применялся вне запроса, на уровне набора данных макета компоновки данных.

Стало возможно создавать отчеты, которые используют запросы с объединениями и в которых отбор на некоторые поля применяется не во всех запросах, участвующих в объединении.
Дата акселератор.
Работа с запросами.
Для механизма Дата акселератора реализована поддержка запросов, содержащих выражение В ИЕРАРХИИ.Механизм Дата акселератора не поддерживал исполнение запросов, содержащих выражение В ИЕРАРХИИ.Расширены возможности использования Дата акселератора.
В документации данное изменение описано здесь.
Картинки.
Системное перечисление ГлубинаЦвета доступно на русском языке только в режиме совместимости Версия 8.3.14 и выше.

В режиме совместимости Версия 8.3.13 и ниже данное перечисление доступно только в английском варианте ColorDepth.

Системное перечисление ГлубинаЦвета было доступно на русском языке в любом режиме совместимости.Устранен конфликт между идентификаторами платформы и именами переменных выпушенных прикладных решений.
Сборщик мобильных приложений.
Полный номер мобильного приложения, собранного сборщиком мобильных приложений и предназначенного для работы под управлением ОС Windows, всегда имеет число «0» в качестве последнего разряда полного номера версии приложения.Полный номер мобильного приложения, собранного сборщиком мобильных приложений и предназначенного для работы под управлением ОС Windows, в качестве последнего разряда полного номера версии содержало текущий номер сборки, который был уникален в рамках одного мобильного приложения.Сборщик мобильных приложений стал учитывать требования магазина Windows Store к номеру версии публикуемого мобильного приложения.
Сборщик мобильных приложений.
Мобильный клиент.
При настройке сборки приложения мобильного клиента, реализована возможность указать:
  • Способ проверки сертификата сервера.
  • Какой сертификат используется для проверки подлинности сервера.
  • Какой сертификат используется для удостоверения клиента.

Указанные возможности можно использовать в том случае, если адрес информационной базы или веб-сервиса со списком общих информационных баз, начинается с префикса «https://». В противном случае работа с сертификатами не предоставляется. +

Данная возможность не предоставлялась.Стало возможно использовать мобильный клиент в том случае, если для доступа к информационной базе требуется защищенное соединение, при этом размещение требуемых сертификатов на мобильных устройствах конечных пользователей затруднено.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Реализована возможность использования в платформе XSD-схем, содержащих типы, в которых определены атрибуты через ссылки на глобальные атрибуты, но переопределяющие такие свойства как default или fixed.При попытке использования в платформе XSD-схем, содержащих типы, в которых определены атрибуты через ссылки на глобальные атрибуты, но переопределящие такие свойства как default или fixed, в процессе проверки модели XDTO выдавались ошибки и работа с такими схемами была невозможна.Устранено некорректное поведение системы.
Дата акселератор.
Работа с запросами.
Для механизма Дата акселератора реализована поддержка запросов, использующих табличные части и функцию языка запросов АВТОНОМЕРЗАПИСИ().Механизм Дата акселератора не поддерживал исполнение запросов, использующих табличные части и функцию языка запросов АВТОНОМЕРЗАПИСИ().Расширены возможности использования Дата акселератора.
В документации данное изменение описано здесь.
Локализация.
Реализована локализация интерфейса клиентского приложения для итальянского языка (код it).Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» италоговорящими пользователями.
В документации данное изменение описано здесь и здесь.
Интерфейс.
В диалоге Все функции реализована строка поиска. Поиск начинается при попытке набрать поисковое выражение в дереве объектов конфигурации. Поиск выполняется по всему списку объектов в диалоге, вне зависимости от того, развернуты ветви дерева объектов конфигурации или нет. В строке поиска можно ввести несколько поисковых слов. В этом случае поиск будет выполнен с использованием всех введенных слов поискового запроса. Также строка поиска доступа с помощью сочетания клавиш Ctrl+F.

Поиск с помощью стандартного диалога доступен с помощью сочетания клавиш Alt+F. Поиск по-прежнему выполняется только по развернутым ветвям дерева объектов конфигурации.

Поиск в диалоге Все функции был доступен только с помощью стандартного диалога поиска, который искал только по развернутым ветвям дерева объектов конфигурации. Этот диалог был доступен с помощью сочетания клавиш Ctrl+F. В диалоге Все функции был недоступен поиск по нескольким словам.Поиск в диалоге Все функции стал более простым и удобным.
В документации данное изменение описано здесь.
Программное лицензирование.
Использование профилей безопасности в системе «1С:Предприятие» технически не блокируется при использовании лицензии уровня ПРОФ. При этом для использования профилей безопасности по прежнему требуется наличие у пользователя лицензии уровня КОРП.Использование профилей безопасности в системе «1С:Предприятие» технически блокировалось при использовании лицензии уровня ПРОФ.Изменен состав функций в лицензиях уровня КОРП, возможность работы с которыми проверяется технически.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL 9.6.6 из состава ОС AstraLinux Special Edition 1.6 при условии, что в данной ОС настроена локаль en_US.UTF8.СУБД PostgreSQL 9.6.6 из состава ОС AstraLinux Special Edition 1.6 не поддерживалась.Расширен список поддерживаемых СУБД.
Мобильный клиент.
Push-уведомления от системы взаимодействия доставляются на мобильное устройство с использованием Firebase Cloud Messaging.Push-уведомления от системы взаимодействия доставлялись на мобильное устройство с использованием Google Cloud Messaging.Прекращено использование устаревшей технологии доставки push-уведомлений в системе взаимодействия. В результате этого ускорена доставка push-уведомлений от системы взаимодействия на клиентские мобильные устройства.
Мобильная платформа.
Мобильный клиент.
В случае аварийного завершения работы мобильного приложения происходит переход в список приложений.В случае аварийного завершения работы мобильного приложения происходило завершения работы и самого мобильного приложения. В результате было невозможно восстановить информационную базу из резервной копии (при использовании мобильной платформе) или изменить настройки подключения (при использовании мобильного клиента).Улучшено поведение мобильного приложения в случае аварийного завершения.
Мобильная платформа.
Мобильный клиент.
Сборщик мобильных приложений.
Для мобильной версии платформы «1С:Предприятие» реализована поддержка заставок размером 1244x2208 и 2208x1244 при работе под управлением ОС Android.

В сборщик мобильных приложений включена поддержка заставки данных размеров.

Мобильная версия платформы «1С:Предприятие» не поддерживала заставки размером 1244x2208 и 2208x1244 при работе под управлением ОС Android.

Сборщик мобильных приложений не поддерживал возможность указания заставки данных размеров.

Реализована поддержка заставки для экранов больших разрешений при работе под управлением ОС Android.
В документации данное изменение описано здесь.
Средства разработки.
Мобильная платформа.
Мобильный клиент.
Запись в файл конфигурации для мобильной платформы выполняется только в формате zip-файла. Возможность сохранить конфигурацию в формате xml-файла более не предоставляется. Изменение касается как выгрузки с помощью конфигуратора (в интерактивном режиме), так и с помощью командной строки запуска конфигуратора (команда /MobileAppWriteFile).Запись в файл конфигурации для мобильной платформы выполнялась в формате zip-файла или xml-файла.Изменился формат выгрузки конфигурации для мобильной платформы системы «1С:Предприятие».
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.8.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.9.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.10.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Средства администрирования.
Программное лицензирование.
В состав дистрибутива Утилиты лицензирования 1С:Предприятия входят следующие версии утилит:
  • Утилита командной строки ring - версия 0.17.0+1.
  • Модуль license - версия 0.12.0+3.
  • Установщик «1С:Предприятия» - версия 1.6.0+4.
В составе дистрибутива Утилиты лицензирования 1С:Предприятия входили предыдущие версии утилит.Исправлены мелкие ошибки и опечатки.
Мобильная платформа.
Документация.
В документации описана структура каталогов, возникающая при публикации мобильного приложения на веб-сервере с помощью конфигуратора. Также описаны типы MIME, которые должен поддерживать веб-сервер, для использования веб-сервера для размещения конфигураций мобильного приложения и отладки прикладного решения.В документации отсутствовала информация о том, какие данные размещаются на веб-сервере после публикации мобильного приложения из конфигуратора.Уточнена документация к платформе.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализовано свойство ВложениеСистемыВзаимодействия.СодержимоеУдалено для отображении факта того, что вложение удалено из файлового хранилища системы.

Переработаны сообщения, которые отображаются при возникновении проблем с передачей файлов с использованием системы взаимодействия. +

Из встроенного языка было недоступно определение того, что вложение удалено из хранилища файлов системы взаимодействия.Стало возможно определить, что вложение удалено из файлового хранилища системы взаимодействия.
Система взаимодействия.
Если для работы системы взаимодействия используется сервис «1С:Диалог», то возможность передачи файлов в этом случае обладает некоторыми ограничениями. Список ограничений (см. здесь).Условия хранения файлов в сервисе «1С:Диалог» были не определены.Определены условия по хранению файлов в сервисе «1С:Диалог».
В документации данное изменение описано здесь.
Работа с СУБД.
Системные требования.
Для работы кластера серверов с СУБД Oracle Database необходимо установить на компьютер с кластером Oracle Instant Client версии 10.2.0.5.

Клиентские библиотеки для работы с Oracle Database более не входят в состав дистрибутива системы «1С:Предприятие».

Клиентские библиотеки для работы с Oracle Database входили в состав дистрибутива системы «1С:Предприятие».

Для работы кластера серверов с СУБД Oracle Database не было необходимости в установке дополнительного программного обеспечения. +

Изменен состав дистрибутива системы «1С:Предприятие».
В документации данное изменение описано здесь.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Прекращена поддержка операционной системы Android версии 4.0.Поддерживалась операционная система Android версии 4.0.Исключение поддержки устаревшей версии операционной системы Android.
В документации данное изменение описано здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 11.5 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Сборщик мобильных приложений.
В сборщике мобильных приложений реализована поддержка сервисов отправки push-уведомлений Firebase Cloud Messaging (FCM, для ОС Android) и Windows Push Notification Services (WNS, для ОС Windows) при работе через вспомогательный сервис фирмы 1С (https://pushnotifications.1c.com).

Сервис отправки push-уведомлений Google Cloud Messaging (GCM, для ОС Android) недоступен при использовании вспомогательного сервиса фирмы 1С (https://pushnotifications.1c.com) с помощью сборщика мобильных приложений.

При использовании вспомогательного сервиса фирмы 1С (https://pushnotifications.1c.com) с помощью сборщика мобильных приложений фактически были доступны сервисы Apple Push Notification Service (APNs, для ОС iOS) и Google Cloud Messaging (GCM, для ОС Android).При использовании вспомогательного сервиса фирмы 1С (https://pushnotifications.1c.com) из сборщика мобильных приложений, сборщик стал соответствовать фактическим возможностям сервиса.
Работа в macOS.
Средства разработки.
Из состава дистрибутива клиентских приложений для macOS исключен дистрибутив драйвера ключа HASP. Для установки драйвера ключа защиты его будет необходимо предварительно скачать с сайта компании Gemalto.В состав дистрибутива клиентских приложений для macOS входил дистрибутив драйвера ключа HASP.Стало возможно выполнять требования компании Apple, без соблюдения которых невозможно сформировать дистрибутив системы «1С:Предприятие», который можно установить на ОС macOS версии 10.15 и последующих.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.12.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 11.7.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Системные требования.
Администрирование.
В дистрибутивах системы «1С:Предприятие» для ОС Windows и macOS поставляется HASP Device Driver версии 7.92.В дистрибутивах системы «1С:Предприятие» для ОС Windows и macOS поставлялся HASP Device Driver версии 7.63.Дистрибутив системы «1С:Предприятие» содержит более актуальную и безопасную версию HASP Device Driver.
Интерфейс.
В диалоге О программе реализована гиперссылка Лицензии используемых компонентов, при нажатии на которую открывается диалог со списком используемых в «1С:Предприятии» компонентов, разработанных другими компаниями.В диалоге О программе отсутствовала возможность получить информацию о компонентах системы «1С:Предприятие», разработанных другими компаниями.Реализация требований LGPL v2.1.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 9.6.18.1,
  • Postgres Pro 1C 10.13.1,
  • Postgres Pro 1C 11.8.1,
  • Postgres Pro Standard 9.6.18.1,
  • Postgres Pro Standard 10.13.1,
  • Postgres Pro Standard 11.8.1,
  • Postgres Pro Enterprise 9.6.18.1,
  • Postgres Pro Enterprise 10.13.1,
  • Postgres Pro Enterprise 11.8.1.
Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 9.6.18.1,
  • Postgres Pro 1C 10.13.1,
  • Postgres Pro 1C 11.8.1,
  • Postgres Pro Standard 9.6.18.1,
  • Postgres Pro Standard 10.13.1,
  • Postgres Pro Standard 11.8.1,
  • Postgres Pro Enterprise 9.6.18.1,
  • Postgres Pro Enterprise 10.13.1,
  • Postgres Pro Enterprise 11.8.1.
Расширен список поддерживаемых СУБД.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 9.6.19.1,
  • Postgres Pro 1C 10.14.1,
  • Postgres Pro 1C 11.9.1,
  • Postgres Pro Standard 9.6.19.1,
  • Postgres Pro Standard 10.14.1,
  • Postgres Pro Standard 11.9.1,
  • Postgres Pro Enterprise 9.6.19.1,
  • Postgres Pro Enterprise 10.14.1,
  • Postgres Pro Enterprise 11.9.1.
Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 9.6.19.1,
  • Postgres Pro 1C 10.14.1,
  • Postgres Pro 1C 11.9.1,
  • Postgres Pro Standard 9.6.19.1,
  • Postgres Pro Standard 10.14.1,
  • Postgres Pro Standard 11.9.1,
  • Postgres Pro Enterprise 9.6.19.1,
  • Postgres Pro Enterprise 10.14.1,
  • Postgres Pro Enterprise 11.9.1.
Расширен список поддерживаемых СУБД.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.13 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 11.8 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 12.3 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 10.14 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 11.9 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 12.4 (x86-64).Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.

Оглавление

Переход с предыдущей версии на версию 8.3.14

Оглавление

Версия 8.3.13

Версия 8.3.13 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8313doc) документации к текущей версии.

Возможность запуска конфигуратора в режиме агента вышла из статуса бета-версии.

Возможность развертывания собственного сервера системы взаимодействия вышла из статуса бета-версии. Для использования собственного сервера системы взаимодействия требуются клиентские и серверные лицензии уровня КОРП (см. здесь). В документации данное изменение описано здесь.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.12. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.11. +Возможность запуска конфигураций, разработанных в версии 8.3.12 и более младших, в версии 8.3.13, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.13 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.12, при необходимости, использовать для работы с информационной базой и версию 8.3.12. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 10.СУБД PostgreSQL версии 10 не поддерживалась.Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Система взаимодействия.
Реализовано приложение «1С:Предприятие - оповещения и запуск», которое выполняет следующие функции:
  • Централизованное отображение оповещений для всех клиентских приложений (включая веб-клиент).
  • Отображение оповещений, в том числе в тех случаях, когда приложение закрыто (для тех информационных баз, которые подключились к агенту).
  • Запуск клиентского приложения или разворачивание окна (в случае, если клиентское приложение запущено) с переходом к конкретному обсуждению.
  • Возможность отключения показа оповещений от конкретной информационной базы.
  • Получение возможности быстрого доступа к системе «1С:Предприятие».

Приложение работает под управлением ОС Windows и Linux, а также для веб-браузеров Google Chrome, Mozilla Firefox и Microsoft Internet Explorer. +Реализована возможность отображения непрочитанных сообщений из системы взаимодействия и центра оповещений при старте клиентского приложения. Для тонкого, толстого и веб-клиента реализованы команды командной строки запуска клиентского приложения DisplayUserNotificationList.

Оповещения отображались только в том случае, если на компьютере было запущено соответствующее приложение.Стало возможно получать оповещения, рассылаемые сервером взаимодействия, даже в тех случаях, когда приложение-приемник сообщений не запущено.
В документации данное изменение описано здесь и здесь.
Веб-клиент.
При использовании OpenID-аутентификации в веб-клиенте реализована возможность указать произвольный (один или несколько) провайдер OpenID-аутентификации. Используемый провайдер должен поддерживать протокол OpenID Connect.

В файле default.vrd реализован элемент openidconnect.

Реализован параметр OidcSelectedProvider командной строки веб-клиента.

Настройка произвольного провайдера OpenID-аутентификации при публикации из конфигуратора не поддерживается.

Прочие клиентские приложения (кроме веб-клиента) не поддерживают использование произвольного провайдера OpenID-аутентификации.

Данная возможность не предоставлялась.

В качестве провайдера OpenID-аутентификации при работе веб-клиента могла использовать только информационная база системы «1С:Предприятие».

Расширен список вариантов аутентификации пользователя при использовании веб-клиента.
В документации данное изменение описано здесь и здесь.
Автоматизированное тестирование.
Для объектов ТестируемаяДекорацияФормы и ТестируемоеПолеФормы реализован метод НажатьНаГиперссылкуВФорматированнойСтроке(). Данный метод позволяет эмулировать нажатие гиперссылки, расположенной в форматированной строке.Данная возможность не предоставлялась.Расширены возможности автоматизированного тестирования.
Интерфейс.
Расширение конфигурации.
Мобильная платформа.
Мобильный клиент.
Реализована возможность создавать пользовательские стили и элементы стиля.

Свойство конфигурации ОсновнойСтиль стало доступно для управляемого приложения.

В ветви Общие дерева метаданных доступны элементы Элементы стиля и Стили.

Реализованы системные стилевые цвета ЦветНавигации, ЦветДополнительнойНавигации, ЦветАктивности, ЦветВажного, ЦветАкцента.

В режиме совместимости с версией 8.3.12, элементы стиля типа Цвет и Шрифт, попавшие в состав стиля, будут иметь значения, заданные в самом элементе стиля, если стиль не использовался для обычного приложения и для этого элемента стиля не были изменены значения.

Незначительно изменено цветовое оформление разных элементов интерфейса.

В расширении конфигурации реализована возможность заимствовать и создавать собственные элементы стиля и стили. Реализована возможность переопределять значение свойства ОсновнойСтиль в расширении конфигурации.

Данная возможность не предоставлялась.Расширены возможности управления внешним видом клиентского приложения.
В документации данное изменение описано здесь, здесь и здесь.
Клиентское приложение.
Реализована возможность отключать отображение заставки при старте клиентского приложения. Реализован параметр командной строки запуска клиентского приложения DisableSplash. Параметр доступен для тонкого клиента, толстого клиента и веб-клиента.Данная возможность не предоставлялась.

Было невозможно отключить заставку при старте клиентского приложения.

Расширены возможности интеграции систем на базе «1С:Предприятие» с другими приложениями.
В документации данное изменение описано здесь.
Расширение конфигурации.
В расширении конфигурации реализована возможность создания следующих собственных объектов:
  • планы видов характеристик;
  • планы счетов;
  • планы видов расчета;
  • регистры накопления;
  • регистры бухгалтерии;
  • регистры расчета.

Для собственных регистров накопления не поддерживается создание агрегатов.

Реализована возможность включать собственные регистры любого вида в состав движений собственных и заимствованных документов расширения. +

Данная возможность не предоставлялась.Расширены возможности использования расширений конфигурации.
В документации данное изменение описано здесь.
Отображение информации.
Реализована возможность склонять фразы. Реализован метод глобального контекста ПолучитьСклоненияСтроки().Данная возможность не предоставлялась.Для приведения должностей и личных данных сотрудников в соответствующую падежную форму при формировании различных отчетов и документов стало достаточно встроенных возможностей платформы «1С:Предприятие».
Фоновые и регламентные задания.
Реализована возможность ожидать завершение работы одного или нескольких фоновых заданий в течение заданного промежутка времени. Реализован метод ОжидатьЗавершенияВыполнения() для объектов ФоновоеЗадание и МенеджерФоновыхЗаданий.

Метод ОжидатьЗавершения() считается устаревшим и не рекомендуется к использованию.

Рекомендуется выполнить анализ прикладного решения и изменить алгоритмы работы с фоновыми заданиями.

Улучшено диагностическое сообщение, которое формируется при попытке ожидать завершения фонового задания, которое отсутствует в списке выполняющихся или завершившихся фоновых заданий.

Реализована диагностика ситуации, когда выполняется попытка ожидания завершения фонового задания, запущенного другим пользователем, при условии, что у текущего пользователя отсутствует право Администрирование. +

Данная возможность не предоставлялась.

Была доступна возможность ожидать завершение работы одного или нескольких фоновых заданий с установкой таймаута, однако любое изменение состояния фонового задания, не являющееся нормальным завершением, сопровождалось исключением.

Диагностика аварийных ситуаций при ожидании завершения несуществующего фонового задания была некорректной.

Упрощено ожидание завершения работы фоновых заданий. Упрощена реализация каких-либо действий во время ожидания завершения работы фоновых заданий.
В документации данное изменение описано здесь.
Кластер серверов.
Реализована возможность оценивать использование процессора за время работы сеанса:
  • за текущий серверный вызов;
  • за последние 5 минут;
  • за все время работы сеанса.

Для утилиты rac при выводе информации о сеансе реализованы свойства cpu-time-current, cpu-time-5min-last, cpu-time-total. Для объекта ISessionInfo реализованы свойства cpuTimeCurrent, cpuTimeLast5Min, cpuTimeAll.

Для события <CALL> реализовано свойство CpuTime, которое содержит длительность завершившегося серверного вызова, в микросекундах.

Реализована возможность создания счетчиков потребления ресурсов, которые могут включать в себя большой набор различных показателей (использование процессорного времени, использование памяти, объем дискового ввода/вывода и т.д.).

Для консоли кластера реализована возможность работы со счетчиками потребления ресурсов.

Для утилиты rac реализованы команды:

  • counter update - для создания или редактирования счетчика потребления ресурсов;
  • counter remove - для удаления ранее добавленного счетчика;
  • counter values - для получения текущих значений счетчика;
  • counter list - для вывода текущих настроек выбранного счетчика;

Реализована возможность управлять работой сеансов на основании значений счетчиков потребления ресурсов. Если обнаруживается, что сеанс превышает установленные ограничения по ресурсам, предоставляется возможность:

  • прервать серверный вызов и завершить работу сеанса;
  • прервать серверный вызов, не прерывая работу сеанса (если такое возможно);
  • понижение приоритета потока, который в данный момент выполняется серверный вызов;
  • зафиксировать факт нарушения в технологическом журнале (событие <ATTN>).

Для консоли кластера реализована возможность настраивать ограничения потребления ресурсов.

Для утилиты rac реализованы команды:

  • limit update - для создания ограничения;
  • limit list - для просмотра списка созданных ограничений;

Реализована работа с механизмом управления потреблением ресурсов в Java-интерфейсе для администрирования кластера серверов «1С:Предприятие» (см. здесь). +Механизм управления потреблением ресурсов требует лицензию уровня КОРП.

Данные возможности не предоставлялись.Стало возможно ограничивать потребление ресурсов компьютера, на котором функционирует кластер серверов. В результате стало возможно реализовывать более стабильные системы.
В документации данное изменение описано здесь, здесь и здесь.
Система компоновки данных.
Реализован метод ПользовательскиеНастройкиКомпоновкиДанных.ПолучитьОсновныеНастройкиПоИдентификаторуПользовательскойНастройки(). Метод позволяет получить массив объектов основных настроек по идентификатору пользовательской настройки. Эти объекты можно использовать для доступа к свойствам, значения которых не установлены у объектов пользовательских настроек, поскольку они недоступны для редактирования пользователю.Данная возможность не предоставлялась.Упрощена работа с пользовательскими настройками системы компоновки данных.
Табличный документ.
Реализована возможность преобразования табличного документа для отображения на экранах с небольшой шириной (например, на мобильных устройствах). Преобразование заключается в том, чтобы исключить горизонтальную прокрутку документа.

Для табличного документа реализован метод ПолучитьКомпактныйДокумент(), который возвращает компактную версию табличного документа. Для табличного документа реализован метод УстановитьРастягиваниеПоГоризонтали(), который задает режим растягивания колонок табличного документа.

Для табличного документа реализованы методы ПреобразоватьВКомпактныйДокумент() и ОтменитьПреобразованиеДокумента(), которые позволяют в существующем табличном документе создать или удалить копию документа, пригодную для отображения на экране с маленькой шириной. При печати (или сохранении на диск) табличного документа, он печатается в оригинальном, не преобразованном, виде.

Для расширения управляемой формы отчета реализовано свойство РежимОтображенияРезультата, который позволяет управлять трансформацией отчета. Для расширения управляемой формы отчета реализована команда Компактный режим, который позволяет изменить значение свойства РежимОтображенияРезультата.

Информация о режиме отображения отчета сохраняется в хранилище системных настроек отдельно для мобильного клиента и для остальных клиентских приложений.

Данные возможности не предоставлялись.

Табличный документ не мог быть преобразован к виду, более пригодному для отображения на экранах с небольшой шириной.

Стало возможно более комфортно отображать табличный документ на экранах с небольшой шириной, например, на мобильных устройствах.
Объекты метаданных.
Реализована возможность анализа метаданных, расположенных в файлах .cf или .cfe. Реализован конструктор для объекта ОбъектМетаданныхКонфигурация.

Реализована возможность получения имени конфигурации, номера версии и поставщика на основании файлов .cf или .cfe. Реализован объект ОписаниеКонфигурации.

Реализована возможность получить из файла .cfu список версий конфигурации, которые могут быть обновлены данным обновлением, а также версию конфигурации, которая получится в результате обновления. Реализован объект ОписаниеОбновленияКонфигурации.

Данная возможность не предоставлялась.

Получение информации о конфигурации или обновления конфигурации было недоступно.

Упрощено создание различных инструментов автоматизации обновления конфигураций и создания комплектов поставки.
В документации данное изменение описано здесь.
Расширение конфигурации.
Реализована возможность расширять следующие свойства конфигурации: картинка основного раздела, заставка, логотип.

Реализована возможность расширять объекты конфигурации типа Картинка путем замены существующей картинки.

Для расширения конфигурации реализована возможность указания:

  • краткой информации о расширении;
  • подробной информации о расширении;
  • информации об авторских правах на расширение;
  • веб-адрес информации о поставщике;
  • веб-адрес информации о расширении.
Данные возможности не предоставлялись.Расширены возможности использования расширений конфигурации.
В документации данное изменение описано здесь.
Расширение конфигурации.
Обмен данными.
Реализована возможность включать в состав собственного плана обмена заимствованные объекты расширения конфигурации.

Реализована возможность расширения хранимых данных планов обмена (создание реквизитов, табличных частей и реквизитов табличных частей планов обмена).

В состав собственного плана обмена могли входить только собственные объекты расширения.

Не поддерживалась возможность расширения состава хранимых данных заимствованных планов обмена.

Расширение конфигурации стало предоставлять больше возможностей.
В документации данное изменение описано здесь.
История данных.
Реализована возможность переопределять стандартные формы, используемые механизмом истории данных. Для объекта, описывающего собственно конфигурацию, реализованы свойства ОсновнаяФормаИсторииИзмененийИсторииДанных, ОсновнаяФормаДанныхВерсииИсторииДанных­­, ОсновнаяФормаРазличийВерсийИсторииДанных.

Реализованы объекты ДиалогОтбораВерсийИсторииДанных, ДиалогВыбораПользователейИсторииДанных.

Система не предоставляла возможность переопределить формы, которые используются механизмом истории данных.Расширены возможности работы с механизмом истории данных.
В документации данное изменение описано здесь.
Работа с Интернет.
При работе с HTML-документом реализованы следующие возможности:
  • Удалить все элементы документа определенной категории. Реализован метод ДокументHTML.УдалитьПоКатегории().
  • Получить весь читабельный текст документа как строку. Реализован метод ДокументHTML.ИзвлечьТолькоТекст().
  • Найти все элементы документа, отвечающих некоторому условию. Реализован метод ДокументHTML.НайтиПоФильтру().
  • Удалить все элементы документа, соответствующие определенному условию. Реализован метод ДокументHTML.УдалитьПоФильтру().
Данные возможности не предоставлялись.

Была доступна только возможность обхода DOM-модели HTML-документа с возможностью выполнять какие-то действия с полученными элементами.

Для некоторых вариантов использования упрощена и ускорена обработка HTML-документа (например, если надо удалить из документа все вхождения элемента <script>).
Работа с Интернет.
При работе с электронной почтой реализована поддержка протокола OAuth2 в случае использования протокола IMAP.

Для объекта ИнтернетПочтовыйПрофиль реализованы свойства АутентификацияПоТокену и ТокенДоступа.

Данная возможность не предоставлялась.Реализована поддержка почтовых серверов, использующих протокол аутентификации OAuth2.
Работа с запросами.
Реализована возможность создания поля с уникальными (в рамках одной таблицы), последовательно возрастающими значениями.

Реализована функция языка запросов АВТОНОМЕРЗАПИСИ(), которая может быть использована только при создании временной таблицы.

Не поддерживается использование функции АВТОНОМЕРЗАПИСИ():

  • в запросах, содержащих ОБЪЕДИНИТЬ на верхнем уровне;
  • в запросах, не формирующих временную таблицу;
  • вне списка выборки;
  • в выражениях.
Данная возможность не предоставлялась.Упрощено создание монотонно возрастающего уникального ключевого поля для временной таблицы.
В документации данное изменение описано здесь и здесь.
Автоматизированное тестирование.
Для расширения табличного документа для объекта ТестируемоеПолеФормы реализованы следующие возможности:
  • Получить максимальный номер колонки, содержащей данные. Реализован метод ПолучитьРазмерОбластиДанныхДокументаПоГоризонтали().
  • Получить максимальный номер строки, содержащей данные. Реализован метод ПолучитьРазмерОбластиДанныхДокументаПоВертикали().
Данные возможности не предоставлялись.Расширены возможности автоматизированного тестирования.
История данных.
Реализована возможность обработать факт восстановления версии данных в модуле объекта и в модуле управляемой формы.

Если форма отображает какую-либо версию объекта (кроме актуальной) - в заголовке формы выводится номер отображаемой версии.

Для динамического списка, отображающего список объектов, поддерживающих историю данных, реализована команда, позволяющая открыть историю по объекту, не открывая его формы. Команда доступна при наличии у пользователя права доступа ПросмотрИсторииДанных.

Реализован параметр управляемой формы НомерВерсииПереходаНаВерсиюИсторииДанных.

Для модулей объектов справочника, документа, плана счетов, бизнес-процесса, задачи и модуля набора записей регистра сведений реализован обработчик события ОбработкаФормированияПоВерсииИсторииДанных(), который вызывается во время создания объекта на основании истории.

+

+

При восстановлении версии объекта разработчик не мог обработать это действие.

Просмотр истории данных по объекту был доступен только из формы объекта или формы набора записей.

Расширены возможности работы с историей данных. Повышена безопасность использования истории данных.
В документации данное изменение описано здесь.
Отображение информации.
В библиотеку картинок добавлены новые картинки: Обсуждения, НовоеОбсуждение, Оповещения.В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.
История данных.
Реализована поддержка истории данных для плана обмена, плана видов расчета и константы.Данная возможность не предоставлялась.История данных стала поддерживать большее количество объектов.
Прикладные объекты.
Реализован объект КонстантаКлючЗначения.

Для менеджера константы реализованы методы СоздатьКлючЗначения().

Данная возможность не предоставлялась.Расширены возможности работы с константами.
В документации данное изменение описано здесь и здесь.
Средства разработки.
Реализована возможность формировать дистрибутив поставки прикладного решения, который может быть запущен под управлением macOS.

При формировании комплекта поставки прикладного решения формируется .zip-архив, который содержит собственно файл поставки и исполняемые файлы программы установки для всех поддерживаемых операционных систем (Windows, Linux, macOS). При этом для исполняемых файлов установлены корректные признаки исполняемых файлов (Linux, macOS), поэтому после распаковки дистрибутива на целевой операционной системе можно будет сразу запускать установку прикладного решения.

Для командной строки запуска пакетного режима работы конфигуратора реализована команда CreativeDistributivePackage. Команда командной строки пакетного запуска конфигуратора CreateDistributive является устаревшей и не рекомендуется для использования.

Было возможно формировать дистрибутив поставки прикладного решения, который мог функционировать только под управлением ОС Windows и Linux. Установить прикладное решение под управлением ОС macOS было невозможно.

При формировании дистрибутива прикладного решения было невозможно сформировать архив комплекта поставки с корректно оформленными исполняемыми файлами для всех поддерживаемых операционных систем. Для установки прикладного решения под управлением ОС Linux требовалось предварительно установить корректный признак исполняемого файла для программы установки.

Стало возможно установить прикладное решение под управлением любой поддерживаемой операционной системы.

Комплект поставки формируется в архиве, который может быть распакован на любой поддерживаемой операционной системы без дополнительной установки стороннего программного обеспечения.

В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Системные требования.
Хранилище конфигурации.
Реализован 64-разрядный сервер хранилища конфигураций, работающий под управлением ОС Linux.При работе под управлением ОС Linux, сервер хранилища конфигураций был доступен только в виде 32-разрядного приложения.Работа с сервером хранилища конфигураций стала штатным образом доступна при работе под управлением 64-разрядной ОС Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
История данных.
Реализована возможность принудительно обновить историю данных по конкретному объекту информационной базы. Реализован метод ИсторияДанных.ОбновитьИсторию().Данная возможность не предоставлялась.

Историю данных можно было обновить только по всем объектам информационной базы, в результате чего при открытии формы истории по конкретному объекту, в истории могли отсутствовать версии, еще не перенесенных из специальной очереди.

Форма отображения истории данных по объекту всегда будет отображать полную историю.
В документации данное изменение описано здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
В том случае, когда участник обсуждения вводит текст сообщения, другие участники обсуждения информируются об этом (если у них открыто соответствующее обсуждение).

Реализовано отображение статусов пользователя: не в сети, отошел, не беспокоить, доступен. Статус «отошел» формируется только в тонком или толстом клиентских приложениях, работающих под управлением ОС Windows.

Переработан внешний вид оповещений о новых сообщениях.

Из окна с параметрами пользователя предоставляется возможность открыть обсуждение только с этим пользователем (один на один).

Изменен внешний вид основного окна системы взаимодействия.

Переработана стандартная функция Управление системой взаимодействия. Изменены формы регистрации и отмены регистрации.

Данные возможности не предоставлялись.Улучшены интерфейсные возможности системы взаимодействия.
Интерфейс.
При работе в интерфейсе Такси реализованы следующие изменения:
  • Отступы ячейки таблицы управляемой формы при отображении с масштабом меньшим, чем 100%, уменьшаются пропорционально масштабу с дополнительным коэффициентом.
  • При масштабе 80% высота строки таблицы примерно соответствует высоте строки таблицы в компактном режиме (зависит от установленного шрифта и DPI используемого монитора).
  • Уменьшены отступы слева и справа в ячейках таблицы (в любом масштабе).
  • Уменьшены отступы слева и справа в колонках табличного документа, сформированного по команде таблицы Вывести список.

При работе в интерфейсе Такси наблюдалось следующее поведение:
  • Отступы в ячейки таблицы управляемой формы при отображении с масштабом меньшим, чем 100%, уменьшались пропорционально без дополнительного коэффициента.
  • Отступы слева и справа в ячейках таблицы были больше.
  • Отступы слева и справа в колонках табличного документа, сформированного по команде таблицы Вывести список, были больше.
Оптимизировано отображение таблицы управляемой формы и табличного документа при использовании нестандартного масштаба формы.
Интерфейс.
Все некорректные навигационные ссылки в интерфейсе представляются в виде самой ссылки. После закрытия диалога настройки избранного работы пользователя такие ссылки не удаляются из избранного и сохраняется возможность редактировать и использовать такие ссылки.

Реализован метод ПредставлениеНавигационнойСсылки.Представление().

Метод ПолучитьПредставленияНавигационныхСсылок() всегда возвращает массив объектов ПредставлениеНавигационнойСсылки. При этом в зависимости от навигационной ссылки поля каждого объекта ПредставлениеНавигационнойСсылки будут заполнены по разному.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Некорректные навигационные ссылки отображались в интерфейсе с пустым представлением и не могли быть использованы.

После закрытия диалога настройки избранного работы пользователя такие ссылки удалялись из истории.

Метод ПолучитьПредставленияНавигационныхСсылок() для некорректных навигационных ссылок возвращал значение Неопределено.

Улучшена работа с навигационными ссылками.
Веб-клиент.
Табличный документ.
Доработана печать табличного документа в веб-клиенте (при использовании способа печати HTML) с целью устранения дефектов печати.Печать табличного документа в веб-клиенте (при использовании способа печати HTML) могла выполняться с дефектами.Устранено некорректное поведение системы.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Регистры сведений.
Для регистров сведений реализовано формирование кластерного индекса по измерениям для физических таблиц среза первых и среза последних. Описание структуры индекса (см. здесь).

Отключен контроль уникальности индексов.

Оптимизированы запросы получения данных из таблиц срезов.

Построение новых индексов выполняется во время реструктуризации соответствующего регистра сведений или при выполнении реструктуризации базы данных во время выполнения операции тестирования и исправления.

Физические таблицы среза первых и среза последних не содержали индексов.

Запросы получения данных из таблиц срезов были недостаточно оптимальны.

Повышена производительность работы физических таблиц срезов при большом количестве пользователей. Исключены взаимоблокировки при обновлениях физических таблиц срезов первых/последних.
Полнотекстовый поиск.
Уменьшен размер временных файлов, создаваемых платформой при обновлении индекса полнотекстового поиска. Данное изменение наиболее заметно в информационных базах с большим количеством разделителей.

Новый формат временных файлов будет использоваться после отключения режима совместимости.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Временные файлы, создаваемые платформой при обновлении полнотекстового поиска, имели существенно больший размер.Уменьшено использование дискового пространства при построении индекса полнотекстового поиска для информационной базы, содержащей большое количество разделителей.
Работа с СУБД.
Оптимизирована работа виртуальных таблиц оборотов регистров накопления и бухгалтерии в случае использования группировок по дню, месяцу или году, а также при использовании функции языка запросов НачалоПериода().

Оптимизация используется для любых версий поддерживаемых СУБД, кроме Microsoft SQL Server, где оптимизация действует, начиная с версии 2012.

Работа виртуальных таблиц оборотов регистров накопления и бухгалтерии в случае использования группировок по дню, месяцу или году, а также при использовании функции языка запросов НачалоПериода() выполнялась недостаточно оптимально.Ускорена работа виртуальных таблиц оборотов регистров накопления и бухгалтерии.
Общие объекты.
Оптимизирована работа следующих методов объекта КоллекцияСтрокДереваЗначений: Удалить(), Вставить(), Индекс(), Сдвинуть(). Следующие методы объекта КоллекцияСтрокДереваЗначений работали не оптимально: Удалить(), Вставить(), Индекс(), Сдвинуть(). Ускорена работы с коллекциями строк дерева значений из встроенного языка.
Внешние отчеты и обработки.
Ускорена загрузка внешних обработок и отчетов в том случае, когда с загружаемой обработкой или отчетом работают много пользователей.Загрузка внешних обработок и отчетов занимала больше времени в том случае, если загружаемая внешняя обработка или отчет активно использовалась в многопользовательской работе.Использование внешних ответов и обработок при активной многопользовательской работе стало более комфортным.
Фоновые и регламентные задания.
Расширение конфигурации.
При работе в файловом варианте с использованием расширений, ускорен второй и последующие запуски фонового задания, если запускаемое фоновое задание использует тот же набор расширений, что и при предыдущем запуске.При работе в файловом варианте с использованием расширений, запуск фонового задания занимал больше времени, даже если запускаемое фоновое задание использовало тот же набор расширений, что и в предыдущий запуск.Ускорен запуск фоновых заданий в файловом варианте информационной базы при работе с расширениями.
Общие объекты.
Оптимизированы операции заполнения и удаления строк таблицы значений.Операции заполнения и удаления строк таблицы значений занимали больше времени.Ускорена работа с таблицей значений.
Веб-клиент.
Оптимизирована и ускорена отрисовка заголовков страниц (закладок) при работе в веб-клиенте.Отрисовка заголовков страниц (закладок) при работе в веб-клиенте выполнялась не оптимально и занимала больше времени.Устранено некорректное поведение системы.
Общие реквизиты / Разделение данных.
Оптимизировано получение форм в конфигурациях, использующих общие реквизиты.Получение форм в конфигурациях, использующих общие реквизиты, выполнялось недостаточно оптимально.Ускорено открытие форм в конфигурациях, использующих общие реквизиты.
Система компоновки данных.
В некоторых случаях компоновщик макета системы компоновки данных, при генерации макета выполняет попытку выполнить упорядочивание детальных записей в наборе данных с использованием СУБД. В этом случае система компоновки данных не выполняет упорядочивание своими средствами. Однако результат компоновки может измениться из-за того, что результат сравнения строк в различных СУБД и платформе может различаться.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Компоновщик макета системы компоновки данных, при генерации макета всегда выполнял сортировку детальных записей средствами компоновки данных.В некоторых случаях повышается производительность упорядочивания при построении отчета.
Система компоновки данных.
Оптимизирован процесс компоновки макета компоновки данных при наличии в запросе схемы компоновки данных большого количества запросов, которые формируют временные таблицы, большое количество полей которых не задействовано в процессе компоновки.Процесс компоновки макета компоновки данных при наличии в запросе схемы компоновки данных большого количества запросов, которые формируют временные таблицы, большое количество полей которых не задействовано в процессе компоновки, требовал больше времени.Повышена скорость построения сложных отчетов с большим количество временных таблиц.
Работа с запросами.
В том случае, если в запросе используется оператор В с подзапросом, то вместо подзапроса будет использоваться соединение с таблицей, которая используется в операторе В. Данная замена применяется только в том случае, если в результате замены не изменяется результат запроса.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При использовании в запросе оператора В с подзапросом, в СУБД всегда использовался подзапрос.В результате выполненных изменений улучшается план запроса, который выполняет СУБД.
Средства разработки.
Кластер серверов.
Ускорено обновление конфигурации базы данных при работе в клиент-серверном варианте в режиме отладки.Обновление конфигурации базы данных при работе в клиент-серверном варианте в режиме отладки занимало больше времени.Ускорено обновление конфигурации базы данных при работе в клиент-серверном варианте в режиме отладки.
Табличный документ.
Ускорена работа метода ПроверитьВывод() для табличного документа, содержащего большое количество страниц.Работа метода ПроверитьВывод() для табличного документа, содержащего большое количество страниц, требовала больше времени. Ускорена проверка вывода информации в табличный документ.
Табличный документ.
Оптимизировано выполнение операции копирования в буфер обмена и работа метода табличного документа ПолучитьОбласть() для области табличного документа, которая содержит большое количество строк с индивидуальным форматом колонок.Выполнение операции копирования в буфер обмена и работа метода табличного документа ПолучитьОбласть() для области табличного документа, которая содержит большое количество строк с индивидуальным форматом колонок, требовало больше времени.Ускорена работа по получению области табличного документа, которая содержит большое количество строк с индивидуальным форматом колонок.
Табличный документ.
Веб-клиент.
При работе в веб-клиенте оптимизировано разворачивание и сворачивание групп табличного документа.При работе в веб-клиенте разворачивание и сворачивание групп табличного документа занимало больше времени.Оптимизирована в работа с табличным документом в веб-клиенте.
Фоновые и регламентные задания.
Оптимизирован запуск и ожидание завершения фоновых заданий.Запуск и ожидание завершения фоновых заданий занимало больше времени.Ускорена работа с фоновыми заданиями.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Система взаимодействия.
Реализована корректная обработка смены области данных при работе с сервером взаимодействия. Если новая область данных также зарегистрирована в сервере взаимодействия - будет использоваться регистрация новой области данных.Данная возможность не предоставлялась.

При смене области данных не выполнялось переподключение к серверу взаимодействия для новой области данных.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Для интерфейса Такси изменено отображение выделенной строки таблицы управляемой формы. При отображении выделенной строки выполняется максимальное сохранение цветового оформления текущей строки.При отображение выделенной строки таблицы управляемой формы в интерфейсе Такси игнорировалось цветовое оформление строки.Улучшено отображение выделенной строки таблицы управляемой формы при работе в интерфейсе Такси.
Средства разработки.
В пакетном режиме запуска конфигуратора игнорируются модули, для доступа к которым требуется пароль.

При этом формируется соответствующее диагностическое сообщение.

В пакетном режиме запуска конфигуратора обращение к модулям, для доступа к которым требуется пароль, в некоторых случаях приводило к открытию диалога ввода пароля.Исключены интерактивные действия при работе режима, не предполагающего таких (интерактивных) действий.
В документации данное изменение описано здесь.
Отображение информации.
Если в конструкторе форматной строки в качестве разделителя групп выбран символ «пробел», то в форматную строку будет фактически подставлен символ неразрывного пробела.Если в конструкторе форматной строки в качестве разделителя групп выбран символ «пробел», то в форматную строку подставлялся символ обычного пробела.Устранено некорректное поведение системы.

Снижено количество проблем, возникающих из-за того, что разделение групп в числе было оформлено неверным разделителем.

Система взаимодействия.
Реализованы неконтекстные обсуждения с двумя участниками (один на один). Добавление участников в такое обсуждение не поддерживается.

Реализованы свойства ОбсуждениеСистемыВзаимодействия.Групповое, ОтборОбсужденийСистемыВзаимодействия.Групповое.

Реализована возможность объединения приложений (информационной базы или области данных) одного абонента. Реализована возможность сопоставлять пользователей различных приложений. Реализована возможность объединения контекстных обсуждений разных приложений. Все вышеуказанные действия может выполнять только владелец абонента.

Для стандартной функции Управление системой взаимодействия реализована возможность выполнять объединение приложений, отменять объединение, сопоставлять пользователей и контекстов обсуждений.

Реализовано свойство ПользовательСистемыВзаимодействия.КлючСопоставления. Для менеджера системы взаимодействия реализованы методы ИдентификаторТекущегоПриложения(), ПолучитьПриложение(), ПолучитьПриложенияАбонента(), УстановитьСовместноеИспользованиеПриложенийАбонента(), ОтменитьСовместноеИспользованиеПриложенийАбонента(), ПолучитьСовместноеИспользованиеПриложенийАбонента().

Указанные возможности не предоставлялись.

Взаимодействие могло выполняться только между пользователями одного приложения абонента.

Расширены возможности системы взаимодействия.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Средства разработки.
Ошибки и предупреждения, которые формируются во время проверки метаданных, выводятся в виде сообщений dbstru.

Для сообщения error-type реализовано значение DBRestuctError описывающее ошибку реструктуризации информационной базы.

Для сообщения error-type реализовано значение CommandFormatError описывающее ошибку, возникающую в результате неверного формата команды.

Ошибки и предупреждения, которые формируются во время проверки метаданных, выводились в виде сообщений log.Улучшена диагностика проблем, возникающих при работе конфигуратора в режиме агента.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Дочерние поля составного типа доступны в пользовательских настройках, если есть право Просмотр хотя бы на одну таблицу из составного типа и на само поле. Дочерние поля становятся доступным для выбора, могут участвовать в отборе, сортировке, условном оформлении и в других местах пользовательских настроек, где представлены доступные поля.

Для метода ПроцессорКомпоновкиДанных.Инициализировать() реализован параметр ОграничиватьПолучениеПолейПоСсылкамПоПравуПросмотр.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если у пользователя нет права Просмотр на одну из таблиц поля, имеющего составной тип, то в пользовательских настройках отсутствовали все дочерние поля недоступного типа.Для дочерних полей составного типа пользователь может получать данные тех типов, на которые у него есть право просмотра.
В документации данное изменение описано здесь и здесь.
Диаграммы.
Для поля ввода типа диаграммы реализованы следующие возможности:
  • В поле ввода отображается картинка выбранного типа диаграммы.
  • В списке выбора типа диаграммы реализовано отображение картинки с типом диаграммы.
  • Реализована возможность автоподбора типа диаграммы при наборе имени диаграммы.
  • Для поля ввода реализована кнопка выбора, при нажатии на которую открывается диалог выбора типа диаграммы.

Реализован объект ДиалогВыбораТипаДиаграммы.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Поле ввода типа диаграммы работало следующим образом:
  • В поле ввода не отображалась картинка выбранного типа диаграммы.
  • В списке выбора не отображалась картинка с типом диаграммы.
  • Не поддерживалась возможность автоподбора диаграммы при наборе имени.
  • Отсутствовала кнопка выбора, при нажатии на которую открывался диалог выбора типа диаграммы.
В ряде случаев улучшен выбор типа диаграммы.
Система взаимодействия.
Видеозвонок не может быть выполнен в том случае, если у любой из сторон предполагаемого разговора недоступен микрофон. При этом формируется соответствующее диагностическое сообщение.

В процессе разговора система отображает в окне видеозвонка картинки с диагностикой камеры и микрофона.

Диагностика оборудования перед началом и в процессе выполнения видеозвонка не выполнялась.Устранено некорректное поведение системы.
Средства разработки.
Не поддерживается использование имени Представление в качестве имени реквизита или табличной части объекта, который может быть сохранен в базе данных.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Использование имени Представление в качестве имени реквизита или табличной части объекта было возможно, однако такое использование могло сопровождаться ошибками.Устранено некорректное поведение системы.
Управляемая форма.
При отображении заголовков закладок в управляемой форме слева или справа от элемента Страницы, реализованы следующие изменения:
  • Высота формы не влияет на высоту заголовков страниц. Если все заголовки не умещаются в доступную область экрана - реализована возможность выполнять прокрутку заголовков по вертикали.
  • Реализована возможность прокручивать закладки с помощью колеса мыши.
  • Реализовано управлением прокруткой закладок с помощью сенсорного экрана при работе тонкого клиента под управлением ОС Windows.
При отображении заголовков закладок в управляемой форме слева или справа от элемента Страницы, если все заголовки не умещаются в доступную область экрана - высота заголовков уменьшалась так, чтобы все заголовки попали в отведенное место на экране.Устранено незапланированное поведение системы.
Управляемая форма.
Мобильный клиент.
Свойство таблицы управляемой формы ВариантУправленияВысотой, установленное в значение, отличное от Авто, будет учитываться в том случае, если режим совместимости конфигурации установлен в значение Версия 8.3.7 и старше.Свойство таблицы управляемой формы ВариантУправленияВысотой учитывалось в том случае, если режим совместимости конфигурации был установлен в значение Версия 8.3.10 и старше.Возможности управления высотой таблицы управляемой формы приведены в соответствие с требованиями мобильного клиента.
Управляемая форма.
Динамический список.
Если в динамическом списке указана основная таблица, в которой есть деление на группы и элементы, то для всех колонок, не связанных с полями основной таблицы, условное оформление формы применяется независимо от того, отображается в строке элемент или группа основной таблицы.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если в динамическом списке указана основная таблица, в которой есть деление на группы и элементы, то для всех колонок, не связанных с полями основной таблицы, условное оформление формы применялось следующим образом:
  • Для колонок связанных с присутствующими в запросе обычными полями (не полями через точку, выражениями и т.п.) не основной таблицы – если в строке отображается элемент основной таблицы.
  • Для остальных, не связанных с полями основной таблицы, колонок – если в строке отображается группа основной таблицы.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Регистры бухгалтерии.
Если у регистра бухгалтерии значение свойства Уточнение периода больше 0, то стандартный реквизит УточнениеПериода появляется в форме редактирования стандартных реквизитов и становится доступным в коллекции СтандартныеРеквизиты объекта метаданных РегистрБухгалтерии (в режиме совместимости с версией 8.3.12 свойство отсутствует в данной коллекции).Стандартный реквизит УточнениеПериода ни при каких условиях не появлялся в форме редактирования стандартных реквизитов и был недоступен в коллекции СтандартныеРеквизиты объекта метаданных РегистрБухгалтерии.Устранено незапланированное поведение системы.
Обновление конфигурации базы данных.
Если для информационной базы установлен режим совместимости Версия 8.3.10 (и младше), и конфигурация базы данных была изменена в версии 8.3.10 (и младше), то при открытии этой информационной базы в клиентском приложении версии 8.3.13 (и старше), снижена вероятность появления сообщения о незавершенной операции конвертации структуры конфигурации.Если для информационной базы установлен режим совместимости Версия 8.3.10 (и младше), и конфигурация базы данных была изменена в версии 8.3.10 (и младше), то при открытии этой информационной базы в клиентском приложении версии 8.3.11 (и старше), запуск блокировался с выдачей сообщения о незавершенной операции конвертации структуры конфигурации. Восстановить возможность работы с этой информационной базой можно было только запуском Конфигуратора версии 8.3.11 (и старше) и выполнение реструктуризации информационной базы.Переход между версией 8.3.10 и более старшими версиями стал более плавным.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Система компоновки данных.
Диаграммы.
При выводе диаграммы в табличный документ, процессор вывода системы компоновки данных устанавливает автоматический расчет ширины колонок для всех ячеек той области табличного документа, которая занята диаграммой.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При выводе диаграммы в табличный документ, процессор вывода системы компоновки данных не устанавливал автоматический расчет ширины колонок для последней колонки в области ячеек, которая занята диаграммой.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если для вывода колонок таблицы используются предопределенные макеты группировок, то высота макета общих итогов рассчитывается таким образом, чтобы в макете отображались заголовки всех выводимых ресурсов. Если предполагаемая генератором макетов высота макета общих итогов больше, чем высота предопределенного макета группировок, то генератор макетов увеличивает высоту макетов группировок колонок таблицы.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если для вывода колонок таблицы используются предопределенные макеты группировок, в макете общих итогов могут не выводиться заголовки полей ресурсов в случае, если высота предопределенного макета группировки колонок меньше, чем предполагаемая генератором макетов высота макета общих итогов.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система взаимодействия.
Реализован метод МенеджерСистемыВзаимодействия.ИспользованиеДоступно(), который позволяет определить, что информационная база зарегистрирована в сервисе взаимодействия, регистрация не отключена и есть пользователи системы взаимодействия.

Метод МенеджерСистемыВзаимодействия.ИнформационнаяБазаЗарегистрирована() позволяет определить только тот факт, что информационная база зарегистрирована и регистрация не отключена. В режиме совместимости с версией 8.3.12 поведение не изменилось.

Метод МенеджерСистемыВзаимодействия.ИнформационнаяБазаЗарегистрирована() позволял определить только тот факт, что информационная база зарегистрирована, регистрация не отключена и есть пользователи системы взаимодействия.Стало возможно разделить определение необходимости регистрации информационной базы и возможность использования системы взаимодействия.
В документации данное изменение описано здесь.
Табличный документ.
Высота и ширина страницы табличного документа (свойства ВысотаСтраницы и ШиринаСтраницы) ограничены значением 5000 мм.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Высота и ширина страницы табличного документа (свойства ВысотаСтраницы и ШиринаСтраницы) не имели ограничений.Уменьшено количество проблем, которые могли возникать при экспорте табличных документов с очень большим размером страницы, в сторонние форматы.
В документации данное изменение описано здесь.
Система компоновки данных.
При обращении к не используемым свойствам объектов системы компоновки данных, находящихся в пользовательских настройках, генерируется исключение:
  • Свойство ПредставлениеПользовательскойНастройки объектов ОтборКомпоновкиДанных, ВыбранныеПоляКомпоновкиДанных, УсловноеОформлениеКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Представление, ЛевоеЗначение, Применение, Родитель объекта ЭлементОтбораКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Представление, Применение, Родитель, ТипГруппы, Элементы объекта ГруппаЭлементовОтбораКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Представление, Поля, Отбор, ИспользоватьВГруппировке, ИспользоватьВЗаголовке, ИспользоватьВЗаголовкеПолей, ИспользоватьВИерархическойГруппировке, ИспользоватьВОбщемИтоге, ИспользоватьВОтборе, ИспользоватьВПараметрах объекта ЭлементУсловногоОформленияКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, ЗначенияВложенныхПараметров, Родитель, Параметр (только при попытке установить значение свойства) объекта ЗначениеПараметраНастроекКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Идентификатор, Имя, Выбор, Отбор, ПараметрыВывода, ПоляГруппировки, Порядок, Родитель, Состояние, Структура, УсловноеОформление объектов ГруппировкаКомпоновкиДанных, ГруппировкаТаблицыКомпоновкиДанных, ГруппировкаДиаграммыКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Выбор, Идентификатор, Имя, Колонки, ПараметрыВывода, Родитель, Строки, УсловноеОформление объекта ТаблицаКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Выбор, Идентификатор, Имя, ПараметрыВывода, Родитель, Серии, Точки, УсловноеОформление объекта ДиаграммаКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, Идентификатор, ИдентификаторОбъекта, Имя, Настройки, Родитель объекта НастройкиВложенногоОбъектаКомпоновкиДанных.
  • Свойства ПредставлениеПользовательскойНастройки, РежимОтображения объекта КоллекцияЭлементовСтруктурыНастроекКомпоновкиДанных, владельцем которого является объект типа СтруктураНастроекКомпоновкиДанных, содержащийся в коллекции КоллекцияЭлементовПользовательскихНастроекКомпоновкиДанных.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Обращение к перечисленным свойствам указанных объектов, находящихся в пользовательских настройках, не имело смысла и не приводило к формированию исключения.Исключены ошибочные обращения к неиспользуемым свойствам объектов системы компоновки данных.
Фоновые и регламентные задания.
Параметры фонового задания, в сериализованном виде, не могут превышать размер в 1 Гбайт. Если размер сериализованных параметров фонового задания превышает значение 1 Гбайт - формируется исключение.

В режиме совместимости с версией 8.3.12 исключение формируется в том случае, если параметры фонового задания, в сериализованном виде, превышают размер в 2 Гбайта.

Происходило аварийное завершение работы системы, если размер параметров фонового задания в сериализованном виде превышал размер в 2 Гбайта.Повышена стабильность работы фоновых заданий. Уменьшена вероятность снижения производительности фоновых заданий при передаче параметров очень большого размера.
В документации данное изменение описано здесь и здесь.
Динамический список.
В тонком клиенте, при удалении любого количества строк динамического списка, событие ПриИзменении этого списка вызывается только один раз.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

В тонком клиенте, при удалении строк в динамическом списке, количество вызовов события ПриИзменении этого списка зависело от количества удаляемых строк:
  • 100 строк и меньше - событие вызывается по числу удаляемых строк.
  • 101 строка и больше - событие вызывается один раз.
Устранено некорректное поведение системы.
Общие объекты.
Конструктор объекта Шрифт возвращает стилевой шрифт Обычный шрифт текста, если параметр конструктора ИмяШрифта не задан или в нем передана пустая строка.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Конструктор объекта Шрифт возвращал стилевой шрифт Шрифт диалогов и меню, если параметр конструктора ИмяШрифта не задан или в нем передана пустая строка.Устранено некорректное поведение системы.
Системные требования.
Работа в ОС Linux.
При работе в ОС Linux, система использует библиотеку ImageMagick, входящую в состав дистрибутива платформы.При работе в ОС Linux, система использовала библиотеку ImageMagick, входящую в состав операционной системы.Снижено количество проблем, возникающих из-за некорректной версии библиотеки ImageMagic, которая установлена в операционной системе.
В документации данное изменение описано здесь, здесь и здесь.
Управляемая форма.
При вызове методов ДобавитьСтроку(), ИзменитьСтроку(), СкопироватьСтроку() и ЗакончитьРедактированиеСтроки() объекта ТаблицаФормы не выполняется никаких действий, если недоступны интерактивные команды, соответствующие данным методам.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При вызове методов ДобавитьСтроку(), ИзменитьСтроку(), СкопироватьСтроку() и ЗакончитьРедактированиеСтроки() объекта ТаблицаФормы поведение зависело от вида клиентского приложения:
  • В тонком клиенте выполнялись соответствующие действия;
  • В веб-клиенте никаких действий не выполнялось.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства разработки.
При сохранении в файл настроек объединения конфигураций, идентификаторы, имена реквизитов и объектов метаданных записываются на английском языке.

При загрузке данных из файла настроек объединения конфигураций, вначале выполняется попытка чтения в предположении, что все идентификаторы указаны на английском языке, а при ошибках чтения - попытка выполняется исходя из предположения, что идентификаторы указаны на русском языке.

При сохранении в файл настроек объединения конфигураций, идентификаторы, имена реквизитов и объектов метаданных записывались на языке, соответствующему варианту встроенного языка конфигурации.Загрузка данных из файла настроек объединения конфигураций больше не зависит от варианта встроенного языка используемой конфигурации.
Веб-клиент.
Работа с файлами.
Модифицирована схема работы с файлами в веб-клиенте.

Реализован новый диалог выбора файлов, допускающий выбор нескольких файлов и поддерживающий перетаскивание. Диалог не требует установки расширения работы с файлами.

При использовании методов НачатьПомещениеФайла() и НачатьПомещениеФайлов() реализована возможность ограниченной настройки используемого диалога работы с файлами.

Метод НачатьПомещениеФайлов() для своей работы не требует расширение работы с файлами.

Реализована возможность контролировать некоторые параметры файлов, которые планируются к передаче на сервер. Для методов НачатьПомещениеФайла() и НачатьПомещениеФайлов() реализован параметр ОписаниеОповещенияПередНачаломПомещенияФайлов.

Для объекта ОписаниеПереданногоФайла реализованы свойства ПолноеИмя и ИдентификаторФайла. Свойство Имя данного объекта содержит только имя передаваемого файла. В тонком клиенте исполнение метода НачатьПомещениеФайла() не блокирует исполнение кода на встроенном языке на время помещения файла во временное хранилище.

В режиме совместимости с версией 8.3.12 поведение не изменилось. +Реализована возможность выполнять перетаскивание файлов на расширение поля управляемой формы для картинки, расширение декорации управляемой формы для картинки и на таблицу управляемой формы. Для указанных элементов управляемой формы реализовано свойство СпособПеретаскиванияФайлов. Реализован объект СсылкаНаФайл.

Методы ПоместитьФайл(), ПоместитьФайлы(), ПолучитьФайлы() являются устаревшими и не рекомендуются к использованию.

Рекомендуется переработать работу с файлами в прикладных решениях, с учетом новых возможностей платформы.

Без установленного расширения работы с файлами, методы работы с файлами в веб-клиенте, были очень ограниченными.

В тонком клиенте исполнение метода НачатьПомещениеФайла() блокировало исполнение кода на встроенном языке на время помещения файла во временное хранилище.

Свойство ОписаниеПереданногоФайла.Имя содержало полный путь к переданному файлу.

Расширены возможности по работе с файлами в веб-клиенте без необходимости установки расширения работы с файлами. В веб-клиенте стало доступно перетаскивание файлов (и обработка этого действия в веб-клиенте).
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Диаграммы.
Реализована возможность определять поведение диаграмм в том случае, если в качестве значения в данных указано нечисловое значение (например, NULL или Неопределено). Для объекта Диаграмма реализованы свойства ИспользованиеНечисловыхЗначений и СоединениеТочекПриПропущенныхЗначениях.

Для объектов ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных, ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы свойства ТипДиаграммы.ИспользованиеНечисловыхЗначений и ТипДиаграммы.СоединениеТочекПриПропущенныхЗначениях.

Если у серии выключено отображение маркера (установлен ТипМаркераДиаграммы.Нет) и значение серии в точке не соединяется с другими (значения в предыдущей и последующей точках пропущены) то на месте этого значения отображается кружок, толщиной с линию серии. При отображении линий диаграммы используется закругленное соединение линий. В режиме совместимости с версией 8.3.12 поведение не изменилось.

Не поддерживалась возможность управлять поведением диаграммы для случаев, когда в данных были указаны нечисловые значения.

Если у серии выключено отображение маркера (установлен ТипМаркераДиаграммы.Нет) и значение серии в точке не соединяется с другими (значения в предыдущей и последующей точках пропущены) то такое значение никак не отображалось на диаграмме.

При отображении линий диаграммы использовалось уголковое соединения линий.

Расширены возможности по построению диаграмм.
В документации данное изменение описано здесь.
Автоматизированное тестирование.
Для метода ТестируемаяТаблицаФормы.Развернуть() реализована возможность разворачивать не только все подчиненные узлы, но и подчиненные узлы только первого уровня (относительно разворачиваемого узла). Реализован параметр метода СПодчиненными.

В режиме совместимости с версией 8.3.12 поведение не изменилось. +Рекомендуется проанализировать места использования метода Развернуть() объекта ТестируемаяТаблицаФормы с целью учесть изменения в работе метода.

Метод ТестируемаяТаблицаФормы.Развернуть() разворачивал указанный узел и все подчиненные узлы.Работа механизма автоматизированного тестирования приведена в соответствие с возможностями работы платформы.
Система компоновки данных.
Динамический список.
Внешние источники данных.
Упорядочивание в динамическом списке по полю, которое может принимать значение NULL, приведено к таковому в отчетах: в начале идут значения NULL, потом - все остальные значения.

Упорядочивание в динамическом списке по полю таблицы внешнего источника данных, в котором применяется конструкция ВЫБОР ... КОГДА и в котором могут встречаться значения NULL, приведено к таковому в отчетах: вначале идет значение NULL, потом - все остальные значения.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

В динамическом списке, при упорядочивании по полю, которое может принимать значение NULL, строки, содержащие такое значение, помещались вместе со строками, в которых это поле принимало значение по умолчанию для типа поля.

В динамическом списке, при упорядочивании по полям таблиц любых внешних источников данных, порядок значений NULL будет зависеть от используемой СУБД.

В динамическом списке строки со значением NULL в колонке, по которой выполняется упорядочивание, стали отображаться аналогично другим механизмам платформы.
Управляемая форма.
При установке свойства АвтоОтметкаНезаполненного таблицы управляемой формы в значение Истина, свойство этой таблицы ОтметкаНезаполненного будет содержать актуальное значение отметки незаполненного после выполнения кода на встроенном языке.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Значение свойства таблицы управляемой формы ОтметкаНезаполненного обновлялось только после обновления таблицы или при изменении текущей ячейки.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Работа с запросами.
В том случае, если оператор языка запросов ЕСТЬ NULL применяется к выражению, в котором используется комбинация нескольких виртуальных полей или комбинация виртуального поля и выражения, не содержащего виртуальных полей, то результатом работы функции будет значение ИСТИНА, если результат выражения равен NULL и ЛОЖЬ в противном случае.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Рекомендуется провести анализ использования оператора ЕСТЬ NULL в запросах прикладных решений.

В том случае, если оператор языка запросов ЕСТЬ NULL применяется к выражению, в котором используется комбинация нескольких виртуальных полей или комбинация виртуального поля и выражения, не содержащего виртуальных полей, то результатом работы функции всегда было значение ЛОЖЬ.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с файлами.
Кластер серверов.
В том случае, когда для информационной базы настроен профиль безопасности, в котором запрещен доступ к файловой системе, то методы глобального контекста КаталогВременныхФайлов() и ПолучитьИмяВременногоФайла() возвращают пути с разделителями, принятыми в используемой операционной системе.В том случае, когда для информационной базы настроен профиль безопасности, в котором запрещен доступ к файловой системе, то методы глобального контекста КаталогВременныхФайлов() и ПолучитьИмяВременногоФайла() возвращали пути с разделителями, используемыми в ОС Linux.Устранено некорректное поведение системы.
Работа с файлами.
В том случае, если при работе под управлением ОС Windows, в качестве параметра методов УстановитьВремяИзменения(), УстановитьУниверсальноеВремяИзменения(), НачатьУстановкуВремениИзменения() и НачатьУстановкуУниверсальногоВремениИзменения() объекта Файл будет передано значение меньшее, чем 1 января 1601 года, то метод не будет выполнен и возникнет исключение Ошибка доступа к файлу.

Эта же ошибка будет возникать в случае возникновения любых ошибок исполнения методов объекта Файл.

В том случае, если при работе под управлением ОС Windows, в качестве параметра методов УстановитьВремяИзменения(), УстановитьУниверсальноеВремяИзменения(), НачатьУстановкуВремениИзменения() и НачатьУстановкуУниверсальногоВремениИзменения() объекта Файл будет передано значение меньшее, чем 1 января 1601 года, то время изменения файла получало случайное значение даты.Устранено некорректное поведение системы.
Система компоновки данных.
Если в вычисляемом выражении системы компоновки данных используется конструкция ВЫБОР, в секциях которой получаются поля, тип которых неизвестен (например, если поля получаются из таблицы значений и у поля не указан тип) и в секции ИНАЧЕ указано значение Неопределено, то при выводе такого поля в коллекцию значений, в качестве типа колонки будет указан тип Произвольный (описание типов не будет содержать ни одного типа).

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если в вычисляемом выражении системы компоновки данных используется конструкция ВЫБОР, в секциях которой получаются поля, тип которых неизвестен (например, если поля получаются из таблицы значений и у поля не указан тип) и в секции ИНАЧЕ указано значение Неопределено, то при выводе такого поля в коллекцию значений, в качестве типа колонки был указан только тип NULL.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Для вызова с использованием ЭтотОбъект доступны только методы, описанные с указанием ключевого слова Экспорт. Данное поведение касается как модуля формы, так и любого другого модуля, куда передано значение ЭтотОбъект.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Для вызова с использованием ЭтотОбъект были доступны любые методы, а не только описанные с указанием ключевого слова Экспорт.Устранено некорректное поведение системы.
Система компоновки данных.
Если в настройках системы компоновки данных применяется отбор с видом сравнения Заполнено/НеЗаполнено к вычисляемому полю, которое может принимать тип как у поля с типом Характеристика или типом, определяемым пользователем, или с типом – любой ссылкой, то отбор будет учитывать типы, входящие в Характеристику, определяемый тип или любую ссылку.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если в настройках системы компоновки данных применяется отбор с видом сравнения Заполнено/НеЗаполнено к вычисляемому полю, которое может принимать тип как у поля с типом Характеристика или типом, определяемым пользователем, или с типом – любой ссылкой, то отбор игнорировал типы, входящие в Характеристику, определяемый тип или любую ссылку.

+

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
При формировании временной таблицы с помощью оператора языка запросов ПОМЕСТИТЬ, тип поля временной таблицы, куда помещается NULL, становится составным. Составной тип включает в себя следующие типы: Число с точностью 1.0, Строка длиной 1 символ, ДатаВремя, Булево и NULL.

Рекомендуется провести анализ использования полей временных таблиц, которые могут принимать NULL.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При формировании временной таблицы с помощью оператора языка запросов ПОМЕСТИТЬ, поле, значением которого могло быть NULL, имело тип NULL.Стало возможно использовать поля, которые во временной таблице содержат значения NULL в выражениях, которые не поддерживают использование NULL. В этом случае можно использовать функцию языка запросов ВЫРАЗИТЬ() для получения нужного типа.
В документации данное изменение описано здесь.
Функциональные опции.
При получении значения функциональной опции, значение которой хранится в ресурсе периодического регистра сведений, используется только значение, полученное из среза последних. В качестве даты среза используется дата, заданная для параметра функциональной опции Период или текущая дата (если параметр Период не задан).

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Значение функциональной опции, которое хранится в ресурсе периодического регистра сведений, вычислялось с помощью операции логического ИЛИ среди всех хранимых значений, не ограничиваясь срезом последних. Такое поведение наблюдалось в том случае, если при получении значения функциональной опции указывался только параметр Период.Устранено некорректное поведение системы.

Поведение системы стало соответствовать документации.

В документации данное изменение описано здесь и здесь.
Управляемая форма.
Для таблицы управляемой формы выполняется отбор строк, если в устанавливаемом отборе более одного элемента и для первого элемента значение отбора равно Неопределено.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Для таблицы управляемой формы не выполнялся отбор строк, если в устанавливаемом отборе более одного элемента и для первого элемента значение отбора равно Неопределено.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Упоминания шрифта начертанием bold в тексте и свойствах объектов.

Старые наименования поддерживаются для совместимости.

  • могло использоваться как написание «полужирный», так и «жирный»;
  • свойство Шрифт.Жирный;
  • параметр Жирный конструктора объекта Шрифт.
  • используется только написание «полужирный»;
  • свойство Шрифт.Полужирный;
  • параметр Полужирный конструктора объекта Шрифт.

+

Имена методов получения/установки HTML-документа для расширения форматированного документа объекта ТестируемоеПолеФормы.

Старые наименования поддерживаются для совместимости.

  • ПолучитьHTML();
  • УстановитьHTML().
  • ПолучитьHTMLДокумент();
  • УстановитьHTMLДокумент().

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Специальные возможности мобильного устройства.
При работе с PUSH-уведомлениями при работе под управлением ОС Android используется сервис Firebase Cloud Messaging. Рекомендуется в существующих приложениях перевести работу с PUSH-уведомлениями на эту платформу.

Реализовано значение перечисления ТипПодписчикаДоставляемыхУведомлений.FCM.

Использование сервиса Google Cloud Messaging поддерживается для совместимости и не рекомендуется для использования.

Значение ТипПодписчикаДоставляемыхУведомлений.GCM устарело и используется для совместимости. Параметр НомерПриложенияGoogleCloud метода ПолучитьИдентификаторПодписчикаУведомлений() является необязательным при работе под управлением ОС Android

Для работы с PUSH-уведомлениями при работе под управлением ОС Android использовался сервис Google Cloud Messaging.Отказ от использования устаревшего сервиса доставки PUSH-уведомлений и переход на актуальную реализацию этого сервиса.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
Реализована возможность управления подсветкой камеры при выполнении фотосъемки интерактивно (при работе под управлением ОС Android и Windows Phone) и с помощью встроенного языка (для всех мобильных ОС).

Реализовано свойство глобального контекста СредстваУстройства. Для метода СредстваМультимедиа.СделатьФотоснимок() реализован параметр ТипПодсветкиКамеры.

Реализована возможность использовать вспышку камеры в роли фонарика. Реализовано свойство глобального контекста СредстваУстройства. Реализованы методы менеджера средств устройства ПоддерживаетсяФонарик() и ВключитьФонарик().

Управление подсветкой камеры с помощью встроенного языка была недоступна.

Управление подсветкой камеры в интерактивном режиме было доступно только при работе под управлением ОС iOS.

Отсутствовала возможность использовать вспышку в качестве фонарика.

Расширены возможности работы с камерой и вспышкой на мобильных устройствах.
В документации данное изменение описано здесь и здесь.
Табличный документ.
Мобильная платформа.
PDF-документ, формируемый на мобильной платформе, стал лучше соответствовать аналогичному PDF-документу, который сформирован на персональном компьютере.PDF-документ, формируемый на мобильной платформе, отличался от аналогичного PDF-документа, который был сформирован на персональном компьютере.Уменьшены расхождения в PDF-документе, формируемом на разных устройствах (мобильное устройство и персональный компьютер).
Специальные возможности мобильного устройства.
Мобильный клиент.
Мобильная платформа.
В мобильной версии «1С:Предприятия» реализована возможность получения квитанций ранее совершенных покупок и возможность проверки квитанции совершенной покупки непосредственно на мобильном устройстве.

Для объекта МенеджерВстроенныхПокупок реализованы методы ПоддерживаетсяИсторияПриобретений(), ПолучитьИсториюПриобретений(), ПолучитьКвитанцииВстроенныхПокупок(), ПолучитьДанныеКвитанцийВстроенныхПокупок().

Для объекта МенеджерПроверкиВстроенныхПокупок реализована доступность в клиентской части мобильной платформы и в мобильном клиенте. Для мобильного клиента и клиентской части мобильной платформы реализован метод МенеджерПроверкиВстроенныхПокупок.ПроверитьКвитанциюВстроеннойПокупкиНаМобильномУстройстве().

Реализована доступность свойства глобального контекста ПроверкаВстроенныхПокупок в клиентской части мобильной платформы и в мобильном клиенте.

В эмуляторе покупок сборщика мобильных приложений реализована поддержка получения списка встроенных покупок.

Возможность получения квитанций ранее совершенных покупок не поддерживалась.

Объект МенеджерПроверкиВстроенныхПокупок (и свойство глобального контекста ПроверкаВстроенныхПокупок) были доступны только на сервере платформы для обычного компьютера.

+

Расширены возможности работы с механизмом встроенных покупок, предоставляемые магазинами приложений соответствующих мобильных операционных систем.
Мобильная платформа.
Для элементов формы реализованы свойства:
  • для всех элементов - ВажностьПриОтображении;
  • для таблицы формы - ИспользованиеТекущейСтроки, ПоведениеТаблицыПриСжатииПоГоризонтали.

Для многострочных полей ввода реализована подсказка ввода. +

Данные возможности были доступны только при работе с мобильным клиентом.Унифицированы возможности различных вариантов мобильной версии «1С:Предприятия» в части управления отображением управляемых форм на мобильном устройстве.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Интерфейс.
В интерфейсе Такси унифицировано отображение пометки команды в меню в различных вариантах отображения, а также устранены отличия отображения пометки команды в меню между различными видами клиентских приложений.Отображение пометки команды в меню могло отображаться по-разному.Унифицировано отображение пометки команды в меню во всех вариантах использования.
Система компоновки данных.
При добавлении отбора в запрос набора данных схемы компоновки данных, содержащего объединения, отбор обязательно добавляется во все части объединения, если отбор удалось поместить хотя бы в одну часть объединения. При этом, в тех частях объединения, в которых отбор применить не удается из-за отсутствия в них полей, использующихся в отборе, в добавляемые условия вместо отсутствующего поля проставляется выражение NULL.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При добавлении отбора в запрос набора данных схемы компоновки данных, содержащего объединения, отбор помещался только в те части объединения, в которых было доступно поле, к которому применяется отбор.Унифицировано применение отборов в системе компоновки данных между набором данных-объединение и набором данных-запрос с объединением в запросе.
Работа с Интернет.
В синтакс-помощнике переименованы параметры методов Получить() и Записать() объекта FTPСоединение.

Изменения коснулись только текста синтакс-помощника.

В синтакс-помощнике параметры методов Получить() и Записать() объекта FTPСоединение имели другие имена.Имена параметров методов работы с FTP стали более логичными и понятными.
Специальные возможности мобильного устройства.
Мобильная платформа.
Мобильный клиент.
При работе под управлением ОС iOS старше версии 8.2 значение свойства ДоставляемоеУведомление.Заголовок стало использоваться при отображении уведомления.Значение свойства ДоставляемоеУведомление.Заголовок использовалось при отображении уведомления только при работе под управлением ОС Android.Улучшено отображение уведомлений при работе под управлением ОС iOS.
Система взаимодействия.
Мобильная платформа.
Мобильный клиент.
В уведомлениях, отправляемых системой взаимодействия, стало отображаться имя отправителя, а заголовок неконтекстного обсуждения отображается в заголовке уведомления.В уведомлениях, отправляемых системой взаимодействия, не отображалось имя отправителя, а заголовок неконтекстного обсуждения отображался и в заголовке уведомления и в его тексте.Улучшено отображение уведомлений от системы взаимодействия.
Работа с Интернет.
Реализована работа с хранилищем сертификатов ОС macOS.

Реализованы объекты СертификатыУдостоверяющихЦентровMacOS, СпособВыбораСертификатаMacOS, СертификатКлиентаMacOS.

Для объекта СертификатыУдостоверяющихЦентровОС реализована возможность работы с хранилищем сертификатов ОС macOS.

Реализован параметр -macos команд командой строки запуска клиентского приложения /HttpsCA и /HttpsCert.

Реализовано событие технологического журнала <MACCERT>.

Не поддерживалась работа с хранилищем сертификатов ОС macOS. Организация защищенного соединения была доступна только при хранении сертификатов в виде файлов.При работе под управлением ОС macOS стало возможно использование системного хранилища сертификатов для организации защищенного соединения.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Система взаимодействия.
Для агента клиентского приложения реализована возможность работать с различными версиями протокола обмена с сервером системы взаимодействия.

Реализовано приложение 1ceclac, для установленного агента клиентского приложения изменена структура каталогов.

Агент клиентского приложения мог работать только с одной версией протокола обмена с сервером системы взаимодействия.Для агента клиентского приложения обеспечена возможность работы с предыдущими версиями протокола обмена с сервером системы взаимодействия.
В документации данное изменение описано здесь.
Динамический список.
При выполнении поиска в динамическом списке вводятся ограничения:
  • Общий размер искомого текста не должен превышать 1000 символов.
  • Количество отдельных слов в искомом тексте не должно быть больше 20.

При нарушении данных ограничений генерируется ошибка. Правила разбиения поискового запроса на отдельные слова приведены в документации. +

При выполнении поиска в динамическом списке отсутствовали ограничения на искомый текст.Повышена надежность работы сервера приложений при выполнении поиска в динамическом списке.
В документации данное изменение описано здесь.
Динамический список.
Система компоновки данных.
При открытии форм отчетов и динамических списков, если в хранилище отсутствуют пользовательские настройки, система выполняет следующие действия:
  • Из основных настроек динамического списка и настроек варианта отчета, отмеченных как пользовательские, удаляются элементы с недоступными и отсутствующими полями.
  • Из пользовательских настроек, сформированных по умолчанию, удаляются элементы, содержащие недоступные и несуществующие поля.
  • Вызываются обработчики событий ПередЗагрузкойПользовательскихНастроекНаСервере и ПриЗагрузкеПользовательскихНастроекНаСервере.

Для обработчиков событий ПередЗагрузкойПользовательскихНастроекНаСервере и ПриЗагрузкеПользовательскихНастроекНаСервере реализован параметр ИспользуютсяСтандартныеНастройки.

При выполнении команды Установить стандартные настройки форм отчетов и динамических списков выполняются следующие действия:

  • Из основных настроек динамического списка и настроек варианта отчета, отмеченных как пользовательские, удаляются элементы с недоступными и отсутствующими полями.
  • Из пользовательских настроек, сформированных по умолчанию, удаляются элементы, содержащие недоступные и несуществующие поля.
  • Если за время использования отчета или динамического списка пользовательские настройки не изменялись на стороне клиента ни интерактивно, ни с помощью встроенного языка, то при закрытии формы отчета или динамического списка, текущие пользовательские настройки удаляются из системного хранилища.

Метод КомпоновщикНастроекКомпоновкиДанных.Восстановить(), вызванный с параметром СпособВосстановленияНастроекКомпоновкиДанных.Полное, выполняет следующие действия: отключает флаг Использование у элементов основных настроек, потерявших связь с доступными полями, удаляет элементы пользовательских настроек и основных настроек, отмеченных, как пользовательские, но которые содержат поля, отсутствующие в коллекции доступных полей или недоступные для текущих функциональных опций и прав.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При открытии форм отчетов и динамических списков, если в хранилище отсутствуют пользовательские настройки, наблюдалось следующее поведение:
  • Из основных настроек динамического списка и настроек варианта отчета, отмеченных как пользовательские, не удалялись элементы с недоступными и отсутствующими полями.
  • Из пользовательских настроек, сформированных по умолчанию, не удалялись элементы, содержащие недоступные и несуществующие поля.
  • Не вызывались обработчики событий ПередЗагрузкойПользовательскихНастроекНаСервере и ПриЗагрузкеПользовательскихНастроекНаСервере.

При выполнении команды Установить стандартные настройки форм отчетов и динамических списков наблюдалось следующее поведение:

  • Из основных настроек динамического списка и настроек варианта отчета, отмеченных как пользовательские, не удалялись элементы с недоступными и отсутствующими полями.
  • Из пользовательских настроек, сформированных по умолчанию, не удалялись элементы, содержащие недоступные и несуществующие поля.
  • Если за время использования отчета или динамического списка пользовательские настройки не изменялись на стороне клиента ни интерактивно, ни с помощью встроенного языка, то при закрытии формы отчета или динамического списка, в качестве пользовательских настроек сохранялись стандартные настройки, сформированные на основании текущего варианта (основных настроек динамического списка).

Метод КомпоновщикНастроекКомпоновкиДанных.Восстановить(), вызванный с параметром СпособВосстановленияНастроекКомпоновкиДанных.Полное, отключал флаг Использование у элементов основных настроек, потерявших связь с доступными полями.

Исключено попадание недоступных полей в пользовательские настройки по умолчанию для отчета или динамического списка.
В документации данное изменение описано здесь.
Механизм анализа данных.
При расчете медианы в механизме анализа данных, если анализируемая выборка содержит четное количество элементов, включая два элемента, то в качестве медианы будет использоваться среднее арифметическое двух средних элементов выборки.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

При расчете медианы в механизме анализа данных, если анализируемая выборка содержит четное количество элементов, то в качестве медианы использовалось:
  • Среднее арифметическое двух средних элементов выборки, если выборка содержит более 2 значений.
  • Значение второго элемента, если выборка содержала 2 значения.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с Интернет.
При работе с почтовым сервером по протоколу SMTP реализована поддержка параметра NOTIFY для команды RCPT и параметра RET для команды MAIL. Стало возможно получать уведомление о доставке электронного письма от почтового сервера в соответствии с RFC 1891.

Свойство ИнтернетПочтовоеСообщение.АдресаУведомленияОДоставке считается устаревшим и не рекомендуется для использования. Данное свойство доступно только в режиме совместимости с версией 8.3.12.

Возможность получения уведомления о доставке зависит от используемого почтового сервера и его настроек.

Рекомендуется исключить использование свойства АдресаУведомленияОДоставке объекта ИнтернетПочтовоеСообщение. Для получения уведомлений рекомендуется использовать:

  • Уведомление о прочтении - свойства АдресаУведомленияОПрочтении и УведомитьОПрочтении.
  • Уведомление о доставке - свойство УведомитьОДоставке.
Уведомление о доставке фактически не работало. Вместо него формировалось уведомление о прочтении.Устранено некорректное поведение системы.

Стало возможно получать и уведомления о доставке сообщения и уведомления о прочтении сообщения получателями. +

Работа с Интернет.
Если метод ИнтернетПочта.ПолучитьФлагиСообщений() в текущем почтовом ящике не обнаружил ни одного сообщения, которые соответствуют переданным в качестве параметра идентификаторам, то возвращается пустое соответствие.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если метод ИнтернетПочта.ПолучитьФлагиСообщений() в текущем почтовом ящике не обнаружил ни одного сообщения, которые соответствуют переданным в качестве параметра идентификаторам, то генерировалось исключение.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
При попытке сохранить на сервере или во внешнем соединении табличный документ, содержащий картинки, в формате табличного документа «1С:Предприятия» версии 7.7 генерируется исключение. Табличный документ в таком формате может быть сохранен только в том случае, если он не содержит картинок.Попытка сохранить на сервере или во внешнем соединении табличный документ, содержащий картинки, в формате табличного документа «1С:Предприятия» версии 7.7 приводила к формированию документа, который было невозможно открыть.Устранено некорректное поведение системы.
Управляемая форма.
Если для поля формы свойство Ширина установлено в значение, отличное от 0 и поле не растягивается по горизонтали, то значение, указанное в свойстве Ширина всегда задает ширину поля без учета специальных кнопок поля ввода (очистка, открытие и так далее). Результирующая ширина поля будет равна сумме значения свойства Ширина и ширины всех установленных специальных кнопок поля ввода.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если для поля формы свойство Ширина установлено в значение, отличное от 0 и поле не растягивается по горизонтали, то значение, указанное в свойстве Ширина задавало ширину поля:
  • При наличии специальных кнопок - без учета эти кнопок.
  • В отсутствие специальных кнопок - несколько больше указанного значения.

Таким образом, полная ширина поля могла изменяться при добавлении или удалении специальных кнопок поля ввода. +

Устранено некорректное поведение системы.
Система взаимодействия.
При совместном использовании приложений, счетчик сообщений агента клиентского приложения одно сообщение учитывает один раз.При совместном использовании приложений, счетчик сообщений агента клиентского приложения одно сообщение учитывал несколько раз (по количеству совместно используемых приложений).Устранено некорректное поведение системы.
Внешние компоненты.
Работа в macOS.
Реализована поддержка работы внешних компонент, выполненных по технологии Native API, в клиентском приложении, работающем под управлением ОС macOS.

Доработаны примеры и документация по технологии внешних компонент (см. здесь).

В клиентском приложении, работающем под управлением ОС macOS, не поддерживалась работа внешних компонент, созданных по технологии Native API.В клиентском приложении, работающем под управлением ОС macOS, реализована поддержка внешних компонент.
Внешние компоненты.
Мобильная платформа.
Мобильный клиент.
Для внешних компонент, выполняющихся под управлением ОС iOS, реализована возможность указать набор свойств, которые должны быть включены в свойства собираемого приложения (файл info.plist). Включение свойств, требуемых внешней компоненте, выполняет сборщик мобильных приложений.

Доработана документация по технологии внешних компонент (см. здесь).

Данная возможность не предоставлялась.

Внешние компоненты не могли добавить необходимые свойства в файл info.plist собираемого приложения.

Упрощено создание внешних компонент для мобильных устройств, работающих под управлением ОС iOS.
Система взаимодействия.
Клиентское приложение.
При удалении оповещения системы взаимодействия из центра оповещений, обсуждение, к которому относится удаляемое оповещение, помечается прочитанным. Под «удалением оповещения» понимается как удаление конкретного оповещения, так и полная очистка списка оповещений.При удалении оповещения системы взаимодействия из центра оповещений, обсуждение, к которому относится удаляемое оповещение, не помечалось прочитанным. Под «удалением оповещения» понимается как удаление конкретного оповещения, так и полная очистка списка оповещений.Поведение системы стало более логичным и предсказуемым.
Система компоновки данных.
Работа с XML, XDTO.
При XDTO-десериализации параметров компоновки данных, десериализуются только те параметры, которые присутствуют в списке доступных параметров текущей версии. Для параметров, которые отсутствуют в списке доступных, попытка десериализации не выполняется и параметры восстанавливаются успешно.При XDTO-десериализации параметров компоновки данных, выполнялась попытка десериализации всех сериализованных параметров. Это приводило к ошибкам при попытке восстановить настройки компоновки данных из более старшей версии, где были параметры, недоступные в той версии, в которой выполняется десериализация.Стало возможно восстановить в предыдущей версии платформы схему компоновки данных или настройки схемы компоновки данных, которые сохранены в новой версии платформы. Параметры компоновки данных, которые есть только в новой версии платформы, будут игнорироваться в старой версии платформы.
Мобильный клиент.
Кластер серверов.
История данных.
Если мобильный клиент версии 8.3.12 подключается к серверу «1С:Предприятия» версии 8.3.13, то:
  • При попытке просмотра истории изменений всегда открывается форма истории изменений, используемая по умолчанию.
  • Попытка открыть историю изменений для константы завершается ошибкой.

Если мобильный клиент версии 8.3.13 и старше подключается к серверу «1С:Предприятия» версии 8.3.12, то для просмотра истории изменений всегда используется форма истории изменений по умолчанию. +

При подключении мобильного клиента версии 8.3.12 к серверу «1С:Предприятия» версии 8.3.13 было невозможно выполнить просмотр истории изменений.Устранено некорректное поведение системы.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 10.3.СУБД PostgreSQL версии 10.3 не поддерживалась.Расширен список поддерживаемых СУБД.
Управляемая форма.
Клиентское приложение.
Если в таблице формы нет текущей строки (в том числе, если таблица пустая) и у группы колонок выключено отображение в шапке, то группа колонок верхнего уровня в заголовке не отображается.

Если в таблице есть текущая строка и у группы колонок включено отображение в шапке, то вложенная группа колонок отображается в шапке таблицы только тогда, когда в текущей строке есть ячейки из данной группы колонок.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Если в таблице формы нет текущей строки (в том числе, если таблица пустая) и у группы колонок выключено отображение в шапке, то для группы колонок верхнего уровня в заголовке создавалась пустая колонка.

Если в таблице есть текущая строка и у группы колонок включено отображение в шапке, то вложенная группа колонок всегда отображалась в шапке.

Устранено некорректное поведение системы.
Система компоновки данных.
Предопределенные макеты ресурсов, созданные для пересечения группировок строк таблицы (тип макета Заголовок или Подвал) с группировками колонок таблицы (тип макета Общий итог заголовок или Общий итог подвал), выводятся в случае, даже если в колонках таблицы не выводятся поля-ресурсы.

В режиме совместимости с версией 8.3.12 поведение не изменилось.

Предопределенные макеты ресурсов не выводятся для общих итогов по строке таблицы системы компоновки данных в случае, если в колонках таблицы не выводятся поля-ресурсы.Устранено некорректное поведение системы.
История данных.
В структуре данных, которая формируется при вызове метода ИсторияДанных.ПолучитьРазличиеВерсий(), для перемещения строки табличной части:
  • Свойство НомерСтрокиВВерсииДоИзменения - содержит номер строки, который был у перемещаемой строки до выполнения всех изменений версии.
  • Свойство НомерСтрокиВВерсииПослеИзменения - содержит номер строки, который стал у перемещаемой строки после выполнения всех изменений версии.

Аналогичное изменение выполнено в стандартном отчете о различия в версиях.

В структуре данных, которая формируется при вызове метода ИсторияДанных.ПолучитьРазличиеВерсий(), для перемещения строки табличной части:
  • Свойство НомерСтрокиВВерсииДоИзменения - содержало номер строки, который был у перемещаемой строки до выполнения текущего изменения, но после выполнения всех предыдущих изменений версии.
  • Свойство НомерСтрокиВВерсииПослеИзменения - содержит номер строки, который стал у перемещаемой строки после выполнения одного, текущего, изменения версии.
Устранено некорректное поведение системы.

Нумерация строк стала лучше соответствовать ожиданиям пользователя.

Работа с криптографией.
Реализован интерактивный режим работы менеджера криптографии в части работы с паролем. Если менеджер криптографии инициализируется в интерактивном режиме, то пароль доступа к закрытому ключу, заданный в объекте, игнорируется, а пароль запрашивается у пользователя. При этом реализована возможность запомнить пароль. Интерактивный режим работы менеджера криптопровайдера поддерживается только на стороне клиентского приложения. Попытка использовать интерактивный режим на сервере приводит к ошибке.

Для конструктора объекта МенеджерКриптографии и для метода МенеджерКриптографии.НачатьИнициализацию() реализован параметр ИспользованиеИнтерактивногоРежима.

Рекомендуется выполнить анализ мест использования менеджера криптографии и реализовать использование интерактивного режима работы на стороне клиентского приложения с целью повышения удобства работы пользователей.

Пароль доступа к закрытому ключу можно было указать только через соответствующее свойство менеджера криптографии. Отсутствовал возможность интерактивного указания пароля самим пользователем.Стал возможно реализовать более безопасный и комфортный для пользователя режим использования пароля к закрытому ключу.
Управляемая форма.
Для поля ввода форм, содержащего модифицированные данные и являющегося текущим элементом формы, попытка установить в значение Ложь свойства Видимость, Доступность или РедактированиеТекста, а также установить в значение Истина свойство ТолькоПросмотр, приводит к следующим действиям:
  • Вызывается обработчик события ОкончаниеВводаТекста.
  • Если по окончанию работы обработчика события ОкончаниеВводаТекста значение параметра СтандартнаяОбработка установлено в значение Истина, то:
    • Вызывается обработчик события ПриИзменении, если удалось сформировать корректное значение по введенным данным.
    • В поле ввода устанавливается текущее значение реквизита, связанного с полем ввода если не удалось сформировать корректное значение по введенным данным.
  • Если по окончанию работы обработчика события ОкончаниеВводаТекста значение параметра СтандартнаяОбработка установлено в значение Ложь, то в поле ввода устанавливается текущее значение реквизита, связанного с полем ввода если не удалось сформировать корректное значение по введенным данным.

Для поля ввода форм, содержащего не модифицированные данные и являющегося текущим элементом формы, попытка установить в значение Ложь свойства Видимость, Доступность или РедактированиеТекста, а также установить в значение Истина свойство ТолькоПросмотр, приводит к закрытию выпадающего списка, если таковой был открыт. +В режиме совместимости с версией 8.3.13 поведение не изменилось.

При установке полю ввода свойства Видимость в значение Ложь, будут выполнены следующие действия:
  • Для поля, связанного с текстовым значением, будет сформировано значение из введенного текста, и вызывается обработчик события ПриИзменении.
  • Поле, связанное со ссылочным значением, может остаться в не консистентном состоянии при незавершенном вводе.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Мобильный клиент.
Работа с Интернет.
Реализована возможность использовать HTTPS-соединение для подключения мобильного клиента к информационной базе. В настройках параметров доступа к информационной базе, на мобильном клиенте, реализована возможность выбрать, откуда будет получаться клиентский сертификат и как будет выполняться проверка серверного сертификата.

Клиентские сертификаты выбираются из хранилища сертификатов приложения или файла (для ОС iOS и Android).

При проверке сертификата сервера, список корневых сертификатов получается из системного хранилища сертификатов, из хранилища сертификатов приложения или из файла (для ОС iOS и Android).

Данная возможность не предоставлялась.Расширены возможности мобильного клиента.
Мобильный клиент.
Управляемая форма.
Реализована возможность формировать отдельный состав командной панели формы для мобильного клиента. Реализовано свойство формы СоставКоманднойПанелиНаМобильномУстройстве.

При работе на мобильном клиенте состав данного свойства (если оно не пустое) будет отображаться в командной панели формы, замещая собой стандартную командную панель формы. Не поддерживается включение командной панели формы в состав свойства СоставКоманднойПанелиНаМобильномУстройстве.

Если у группы формы задан заголовок, но его отображение отключено, то такой заголовок все равно участвует в формировании заголовка автоматически сворачиваемой группы при отображении формы на мобильном клиенте.

Не поддерживалась возможность отдельного формирования состава командной панели формы для мобильного клиента.

Если у группы формы задан заголовок, но его отображение отключено, то такой заголовок участвовал в формировании заголовка автоматически сворачиваемой группы при отображении формы на мобильном клиенте.

Расширены возможности настройки формы для работы в мобильном клиенте.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 10.5 (для 32- и 64-разрядных операционных систем).СУБД PostgreSQL версии 10.5 не поддерживалась.Расширен список поддерживаемых СУБД.
Мобильный клиент.
Система взаимодействия.
Для мобильного клиента реализованы следующие возможности системы взаимодействия:
  • Информирование о том, что какой-либо участник обсуждения вводит текст.
  • Обсуждения «один на один».
  • Статусы пользователей. Блокируется поступление PUSH-уведомлений, если установлен статус «Не беспокоить».

Для мобильного клиента реализована доступность следующих объектов:

  • Свойство ОбсуждениеСистемыВзаимодействия.Групповое.
  • Метод ИдентификаторТекущегоПриложения() менеджера системы взаимодействия.

Версия системы взаимодействия, используемая мобильным клиентом, определяется версией системы взаимодействия, используемой сервером «1С:Предприятие».

Возможности системы взаимодействия мобильного клиента определяются версией мобильного клиента «1С:Предприятие» и не зависят от версии сервера «1С:Предприятие».

Данные возможности не предоставлялись.Возможности мобильного клиента, в части системы взаимодействия, синхронизированы с тонкий клиентом.
Системные требования.
Мобильная платформа.
Мобильный клиент.
Для мобильной версии «1С:Предприятия» реализована поддержка операционных систем Android версии 9, iOS версии 12, а также следующих устройств компании Apple: iPhone Xs, Xs Max, Xr.Мобильная версия «1С:Предприятие» не поддерживала работу под управлением операционных систем Android версии 9, iOS версии 12.

Не поддерживалась работа на следующих устройствах компании Apple: iPhone Xs, Xs Max, Xr.

Реализована поддержка актуальных операционных систем и устройств.
Сборщик мобильных приложений.
Реализована возможность более тонко управлять разрешениями мобильного приложения для работы под управлением ОС Android в том случае, если в прикладном решении указано необходимость предоставить разрешение Телефония.

Если таковое разрешение требуется, то сборщик предлагает указать, какое конкретно разрешение (на выбор из 6 разрешений) требует мобильное приложение.

Если прикладное решение заявляло необходимость разрешения Телефония, сборщик мобильных приложений предоставлял мобильному приложения сразу 6 разрешений.Учтены требования по разрешениям, которые появились в новой редакции Правил для разработчиков в Google Play. Стало возможно указывать только те разрешения, которые фактически нужны мобильному приложению.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий:
  • Postgres Pro 1C 9.4.19,
  • Postgres Pro 1C 9.6.11,
  • Postgres Pro 1C 10.6,
  • Postgres Pro Enterprise 9.6.11,
  • Postgres Pro Enterprise 10.3.3,
  • Postgres Pro Enterprise 10.6,
  • Postgres Pro Standard 10.6.
Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 9.4.19,
  • Postgres Pro 1C 9.6.11,
  • Postgres Pro 1C 10.6,
  • Postgres Pro Enterprise 9.6.11,
  • Postgres Pro Enterprise 10.3.3,
  • Postgres Pro Enterprise 10.6,
  • Postgres Pro Standard 10.6.
Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Локализация.
Реализована локализация интерфейса клиентского приложения для испанского языка (код es).Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» испаноговорящими пользователями.
В документации данное изменение описано здесь и здесь.
Локализация.
Реализована локализация интерфейса клиентского приложения для греческого языка (код el).Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» грекоговорящими пользователями.
В документации данное изменение описано здесь и здесь.
Работа с HTML.
При чтении HTML-документа с помощью объекта ЧтениеHTML (с помощью методов ОткрытьФайл(), ОткрытьПоток() и УстановитьСтроку()), разбор документа будет прекращен при достижении уровня вложенности в 1 024 тега. Пользователь получит доступ только к части документа.При чтении HTML-документа с помощью объекта ЧтениеHTML отсутствовали ограничения по количеству вложенных тегов, что могло приводить к аварийному завершению работы системы.Повышена надежность системы при разборе HTML-документов с большим уровнем вложенности тегов.
Работа с СУБД.
Реализована поддержка следующих СУБД (только 64-разрядные версии) :
  • PostgresPro PostgreSQL 10.9.1.
  • PostgresPro PostgreSQL 11.4.1.
  • PostgresPro Standard 9.6.14.1.
  • PostgresPro Standard 10.9.1.
  • PostgresPro Standard 11.4.1.
  • PostgresPro Enterprise 9.6.14.1.
  • PostgresPro Enterprise 10.9.1.
  • PostgresPro Enterprise 11.4.1.
  • PostgresPro Enterprise 11.4.2.
Данные версия СУБД PostgresPro не поддерживалась.Расширен список поддерживаемых версий СУБД PostgresPro.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 9.6.16,
  • Postgres Pro 1C 10.11.1,
  • Postgres Pro 1C 11.6.1,
  • Postgres Pro Standard 9.6.16,
  • Postgres Pro Standard 10.11.1,
  • Postgres Pro Standard 11.6.1,
  • Postgres Pro Enterprise 9.6.16,
  • Postgres Pro Enterprise 10.11.1,
  • Postgres Pro Enterprise 11.6.1.
Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 9.6.16,
  • Postgres Pro 1C 10.11.1,
  • Postgres Pro 1C 11.6.1,
  • Postgres Pro Standard 9.6.16,
  • Postgres Pro Standard 10.11.1,
  • Postgres Pro Standard 11.6.1,
  • Postgres Pro Enterprise 9.6.16,
  • Postgres Pro Enterprise 10.11.1,
  • Postgres Pro Enterprise 11.6.1.
Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Мобильная платформа.
При создании защищенного соединения OpenSSL, проверка сертификата сервера выполняется с использованием сертификатов, установленных на мобильном устройстве, если в качестве значения параметра СертификатыУдостоверяющихЦентров конструктора ЗащищенноеСоединениеOpenSSL указано Неопределено или значение типа СертификатыУдостоверяющихЦентровОС.При создании защищенного соединения OpenSSL, проверка сертификата сервера не выполнялась, если в качестве значения параметра СертификатыУдостоверяющихЦентров конструктора ЗащищенноеСоединениеOpenSSL указано Неопределено или значение типа СертификатыУдостоверяющихЦентровОС.Устранено некорректное поведение системы.
Системные требования.
Работа с СУБД.
Реализована поддержка СУБД Postgres Pro следующих версий (только для архитектуры x86-64):
  • Postgres Pro 1C 9.6.17,
  • Postgres Pro 1C 10.12.1,
  • Postgres Pro 1C 11.7.1,
  • Postgres Pro Standard 9.6.17,
  • Postgres Pro Standard 10.12.1,
  • Postgres Pro Standard 11.7.1,
  • Postgres Pro Enterprise 9.6.17,
  • Postgres Pro Enterprise 10.12.1,
  • Postgres Pro Enterprise 11.7.1.
Не поддерживались следующие версии СУБД Postgres Pro:
  • Postgres Pro 1C 9.6.17,
  • Postgres Pro 1C 10.12.1,
  • Postgres Pro 1C 11.7.1,
  • Postgres Pro Standard 9.6.17,
  • Postgres Pro Standard 10.12.1,
  • Postgres Pro Standard 11.7.1,
  • Postgres Pro Enterprise 9.6.17,
  • Postgres Pro Enterprise 10.12.1,
  • Postgres Pro Enterprise 11.7.1.
Расширен список поддерживаемых СУБД.

Оглавление

Переход с предыдущей версии на версию 8.3.13

Оглавление

Версия 8.3.12

Версия 8.3.12 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8312doc) документации к текущей версии.

Перед адаптацией прикладного решения к особенностям эксплуатации на мобильном клиенте, рекомендуется ознакомиться со статьей на диске ИТС (см. здесь).

Возможность отладки прикладных решений по протоколу HTTP вышла из статуса бета-версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.11. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.10. +Возможность запуска конфигураций, разработанных в версии 8.3.11 и более младших, в версии 8.3.12, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.12 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.12, при необходимости, использовать для работы с информационной базой и версию 8.3.11. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Клиентское приложение.
Реализована возможность управлять разрядностью запускаемого клиентского приложения при работе под управлением 64-разрядной ОС Windows.

В диалоге настройки интерактивной программы запуска реализована возможность указывать разрядность запускаемого приложения. Данная настройка сохраняется в ключе DefaultVersion файла 1CEStart.cfg.

В свойствах информационной базы реализована возможность указания разрядности клиентского приложения, используемого для работы с данной информационной базой. Настройка сохраняется в ключе AppArch файла ibases.v8i.

Реализован ключ командной строки запуска тонкого и толстого клиентских приложений /AppArch.

Данная возможность не предоставлялась.

У пользователя не было возможности управлять тем, клиентское приложение какой разрядности будет запущено при работе под управлением 64-разрядной ОС Windows.

Стало возможно управлять разрядностью клиентского приложения, которое используется при работе под управлением 64-разрядной ОС Windows.

Стало возможно явно указать необходимость использования 32-разрядного клиентского приложения в тех случаях, когда прикладное решение не работоспособно при выборе 64-разрядного приложения, например, из-за того, что отсутствуют 64-разрядные внешние компоненты.

В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Расширение конфигурации.
Реализована возможность управлять областью действия расширения конфигурации и активностью установленных расширений.

Областью действия расширения может быть или текущая область данных или вся информационная база.

Управление активностью позволяет отключить расширение, не удаляя его из информационной базы.

Для объекта РасширениеКонфигурации реализованы свойства ОбластьДействия и Активно.

Изменен порядок подключения расширений: в первую очередь подключаются расширения, имеющие областью действия всю информационную базу.

Данные возможности не предоставлялись.

Расширения всегда подключались в конкретную область данных информационной базы.

Отключить расширение, не удаляя его, было невозможно.

Расширение конфигурации стало предоставлять больше возможностей.

Стало возможно устанавливать расширения конфигурации сразу для всех областей данных информационной базы, например, для оперативного исправления ошибок конфигурации.

В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
Реализована поддержка автоматической конвертации текстовых последовательностей в графические изображения («смайлики»).

Реализовано звуковое оповещение при наступлении следующих событий: новое сообщение, входящий звонок, ожидание ответа при видеозвонке, окончание видеозвонка.

Реализованы ссылки на обсуждения, получение ссылки на обсуждение и переход по ссылкам (интерактивный и с помощью метода ПерейтиПоНавигационнойСсылке()). Реализована возможность добавить ссылку на обсуждение в избранное. Реализована возможность получить представление навигационной ссылки на обсуждение с помощью метода ПолучитьПредставленияНавигационныхСсылок(). Ссылки на обсуждения в тексте сообщения отображаются в виде гиперссылки.

При получении оповещения реализовано мигание панели задач при работе под управлением ОС Windows в тонком и толстом клиенте.

Реализовано контекстное меню в списке обсуждений основной формы системы взаимодействия. Реализовано контекстное меню у сообщения системы взаимодействия.

Реализованы служебные сообщения системы взаимодействия для неконтестных обсуждений: изменение темы обсуждения, подключение пользователя к обсуждению, покидание пользователем обсуждения. Не поддерживается поиск по служебным сообщениям.

Изменено отображение списка участников обсуждения.

Реализована индикация того, что сообщение не отправлено, но ожидает отправки.

Реализован диалог настройки параметров системы взаимодействия.

Реализован редактор картинки пользователя («аватара»).

Изменено отображение списка сообщений.

Указанные возможности не предоставлялись.Повышен комфорт работы пользователя с системой взаимодействия.
В документации данное изменение описано здесь и здесь.
История данных.
Реализована поддержка истории данных для плана счетов и плана видов характеристик.

Реализованы методы УстановитьКомментарийВерсииИсторииДанных() и ПолучитьКомментарийВерсииИсторииДанных() для объектов ПланСчетовОбъект и ПланВидовХарактеристикОбъект.

Данная возможность не предоставлялась.История данных стала поддерживать большее количество объектов.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Для собственных и заимствованных документов расширения реализована возможность формировать движения по любым заимствованным регистрам, кроме оборотных регистров накопления с включенными агрегатами.Данная возможность не предоставлялась.

Документы расширения могли формировать движения только по собственным регистрам сведений расширения.

Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь.
Расширение конфигурации.
Средства разработки.
Хранение настроек.
Реализована возможность хранения расширения конфигурации в хранилище конфигурации. Реализована поддержка работы с расширениями для всех команд пакетного режима запуска конфигуратора, работающих с хранилищем конфигурации.

Для пакетного режима запуска конфигуратора выполнены следующие изменения:

  • Реализован параметр командной строки -Extension для ключей командной строки СonfigurationRepositoryAddUser, ConfigurationRepositoryBindCfg, ConfigurationRepositoryDumpCfg, ConfigurationRepositoryClearCache, ConfigurationRepositoryClearGlobalCache, ConfigurationRepositoryClearLocalCache, ConfigurationRepositoryCommit, ConfigurationRepositoryCopyUsers, ConfigurationRepositoryCreate, ConfigurationRepositoryLock, ConfigurationRepositoryOptimizeData, ConfigurationRepositoryReport, ConfigurationRepositorySetLabel, ConfigurationRepositoryUpdateCfg, ConfigurationRepositoryUnbindCfg, ConfigurationRepositoryUnlock.
  • Реализовано значение ExtensionConfigurationRepository для параметров -FirstConfigurationType и -SecondConfigurationType ключа CompareCfg.
  • Для ключа CompareCfg реализованы параметры -FirstName, -FirstFile, -FirstVersion, -FirstName, -FirstFile, -FirstVersion.
Данная возможность не предоставлялась.

Расширение конфигурации могло разрабатываться отдельно от хранилища конфигурации.

При разработке расширений упрощена коллективная разработка. Упрощено версионирование разрабатываемого расширения.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Расширение конфигурации.
Реализована возможность создавать собственные перечисления в расширении конфигурации.Данная возможность не предоставлялась.Расширены возможности расширения конфигурации.
В документации данное изменение описано здесь.
Работа с Интернет.
Реализована возможность перемещения электронного письма из одного почтового ящика в другой при использовании протокола IMAP. Реализован метод ИнтернетПочта.ПереместитьВПочтовыйЯщик().

Реализована возможность получать и изменять флаги электронного письма при работе по протоколу IMAP. Для объекта ИнтернетПочта реализованы методы ПолучитьФлагиСообщений(), УстановитьФлагиСообщений().

Данные возможности не предоставлялись.Расширены возможности работы с почтой по протоколу IMAP.
Диаграммы.
Система компоновки данных.
Реализована возможность визуального выделения в диаграмме определенного интервала или значения. Данная возможность реализована для следующих видов диаграмм: биржевая (все виды), гистограмма (все виды), график (все виды), точечная, пузырьковая, радарный график (все виды), измерительная.

Для объекта Диаграмма реализованы свойства: ОписаниеПалитрыЦветов, ОписаниеПалитрыЦветовИнформационныхИнтервалов, ИнформационныеЛинииЗначений, ИнформационныеЛинииТочек, ИнформационныеИнтервалыЗначений, ИнформационныеИнтервалыТочек.

Для объекта ОбластьПодписиДиаграммы реализованы свойства: Ориентация, УголНаклона.

Для объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных,

ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и

ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры

ТипДиаграммы.ОписаниеПалитрыЦветов, ТипДиаграммы.ОписаниеПалитрыЦветовИнформационныхИнтервалов,

ТипДиаграммы.ИнформационныеЛинииЗначений,

ТипДиаграммы.ИнформационныеЛинииТочек,

ТипДиаграммы.ИнформационныеИнтервалыЗначений,

ТипДиаграммы.ИнформационныеИнтервалыТочек.

Следующие свойства и методы объекта Диаграмма устарели и не рекомендуются к использованию: ПалитраЦветов, ЦветНачалаГрадиентнойПалитры, ЦветКонцаГрадиентнойПалитры, МаксимальноеКоличествоЦветовГрадиентнойПалитры, ПолучитьПалитру(), УстановитьПалитру().

Данные возможности не предоставлялись.Расширены оформительские возможности при работе с диаграммами.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность экспорта пакета отображаемых документов в форматы XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) и ODT (OpenDocument). При этом реализована возможность сохранения каждого табличного документа пакета на отдельном листе результирующего документа.

Реализовано свойство ЭлементПакетаОтображаемыхДокументов.Наименование, которое используется для указания имени листа.

Для объекта ПакетОтображаемыхДокументов реализованы методы Записать() и НачатьЗапись().

Данная возможность не предоставлялась.Стало возможно сохранять несколько табличных документов системы «1С:Предприятие» на разных листах результирующего документа в формате табличных процессоров (XLS, XLSX, ODT).
Полнотекстовый поиск.
Кластер серверов.
Технологический журнал.
Реализована возможность управлять количеством фоновых заданий, выполняющих обновление индекса полнотекстового поиска при работе в клиент-серверном варианте информационной базы. Управление размещением фоновых заданий обновления индекса полнотекстового поиска может выполняться с помощью требований назначения функциональности.

Для объекта МенеджерПолнотекстовогоПоиска реализованы методы УстановитьКоличествоЗаданийИндексирования() и ПолучитьКоличествоЗаданийИндексирования().

Для события технологического журнала FTEXTUpd реализованы свойства MinDataId, MemoryUsed, BackgroundJobCreated, JobCanceledByLoadLimit, TotalJobsCount, FailedJobsCount.

Данная возможность не предоставлялась.

Обновление индекса полнотекстового поиска всегда выполнялось одним фоновым заданием.

Стало возможно ускорить обновление индекса полнотекстового поиска (особенно при полной переиндексации информационной базы).
В документации данное изменение описано здесь, здесь и здесь.
Расширение конфигурации.
Распределенные информационные базы.
Реализована возможность использования расширений конфигурации в распределенной информационной базе.

Для плана обмена реализовано свойство ВключатьРасширенияКонфигурации.

Для расширения конфигурации реализованы свойства ИспользуетсяВРаспределеннойИнформационнойБазе и ГлавныйУзел.

Данная возможность не предоставлялась.Расширены возможности использования расширений конфигурации. Стало возможно централизованно управлять распространением расширений конфигурации в распределенной информационной базе.
В документации данное изменение описано здесь, здесь и здесь.
Диаграммы.
Реализована возможность управлять автоматическим размещением и расчетом размера областей заголовка, легенды и области построения диаграммы. Для объектов ОбластьЛегендыДиаграммы , ОбластьЛегендыДиаграммыГанта , ОбластьЛегендыСводнойДиаграммы , ОбластьПостроенияДиаграммы, ОбластьПостроенияДиаграммыГанта, ОбластьПостроенияСводнойДиаграммы, ОбластьЗаголовкаДиаграммы, ОбластьЗаголовкаДиаграммыГанта, ОбластьЗаголовкаСводнойДиаграммы реализовано свойство Расположение.

Свойство ОтображатьЛегенду объектов Диаграмма, ДиаграммаГанта, СводнаяДиаграмма является устаревшим и не рекомендуется для использования.

Свойство ОтображатьЗаголовок объектов Диаграмма, ДиаграммаГанта, СводнаяДиаграмма является устаревшим и не рекомендуется для использования.

В диаграммах предоставлялась только возможность управлять отображением областей заголовка и легенды.Расширены оформительские возможности диаграмм.
В документации данное изменение описано здесь.
Работа с запросами.
В языке запросов расширена поддержка значений следующих типов: УникальныйИдентификатор, ХранилищеЗначений.

Реализована возможность создания временных таблиц на основании таблиц значений, содержащих колонки вышеуказанных типов.

Реализована возможность использовать поля и выражения типа УникальныйИдентификатор в операции множественного В.

Данная возможность не предоставлялась.Расширены возможности языка запросов.
В документации данное изменение описано здесь.
Система компоновки данных.
В настройках компоновки данных реализована возможность дополнения периодов в тех случаях, когда отчетный период не совпадает с календарным. При этом имеется возможность указывать размер месяца: календарный или «4-4-5». Во втором случае год разделяется на 4 квартала, а каждый квартал разделяется на два месяца по 4 недели и один (последний) месяц размером в 5 недель.

Для системного перечисления ТипДополненияПериодаКомпоновкиДанных реализованы значения:

  • ГодОтНачалаПериода;
  • ДеньОтНачалаПериода;
  • КварталОтНачалаПериода;
  • МесяцОтНачалаПериода;
  • МинутаОтНачалаПериода;
  • НеделяОтНачалаПериода;
  • ПолугодиеОтНачалаПериода;
  • ЧасОтНачалаПериода;
  • ГодОтНачалаПериода445;
  • КварталОтНачалаПериода445;
  • МесяцОтНачалаПериода445;
  • ПолугодиеОтНачалаПериода445.
Компоновка данных всегда выполняла дополнения периодов по календарному началу квартала и года.Упрощено построение отчетности в том случае, когда отчетный период не совпадает с календарным.
Управляемая форма.
Для управляемой формы реализована всплывающая группа - сворачиваемая группа, которая отображается в виде своего заголовка, нажатие на которой приводит к формированию специального окна поверх текущей формы, которое содержит все элементы всплывающей группы. В рамках одной формы, в один момент времени, может отображаться одна всплывающая группа.

Реализована возможность программного управления состоянием сворачиваемой и всплывающих групп.

Реализовано значение системного перечисления ПоведениеОбычнойГруппы.Всплывающая.

Для расширения группы управляемой формы для обычной группы реализованы методы: Скрыта(), Показать(), Скрыть().

Для расширения группы формы для управляемой формы реализовано свойство ЦветФонаЗаголовкаСкрытогоОтображения.

Данные возможности не предоставлялись.Расширены возможности группировки элементов на управляемой форме.
В документации данное изменение описано здесь и здесь.
Обновление конфигурации базы данных.
Для оптимизированного механизма реструктуризации (режим v2) реализована поддержка реструктуризации объектов конфигурации, для которых в любой из областей данных подключено хотя бы одно расширение, расширяющее данные. Данная поддержка используется только в том случае, когда выполняется реструктуризация основной конфигурации базы данных. Реструктуризация, выполняемая при обновлении расширения, не использует оптимизированный механизм реструктуризации (режим v2).Данная возможность не предоставлялась.

При реструктуризации основной конфигурации базы данных, если в любую из областей было подключено хотя бы одно расширение, расширяющее данные, то использовался обычный механизм реструктуризации (режим v1).

Улучшено взаимодействие различных механизмов платформы.
Автоматизированное тестирование.
Для объекта ТестируемоеПолеФормы, который описывает элементы формы типа поля переключателя, поля ввода, поля надписи (с установленным признаком гиперссылки) реализован метод ПолучитьОтображаемыйТекст(), который позволяет получить текст, который отображается пользователю элементом формы.

Для объекта ТестируемоеПолеФормы, который описывает элементы формы типа поля переключателя, поля ввода реализован метод ПолучитьПредставлениеСпискаВыбора(), который позволяет получить фиксированный массив, содержащий представления значений списка выбора элемента формы.

Данная возможность не предоставлялась.Расширены возможности автоматизированного тестирования.
Мобильный клиент.
Реализован мобильный клиент, являющийся аналогом тонкого клиента, работающим на мобильном устройстве. По интерфейсу мобильный клиент является аналогом мобильной платформы. Подключение мобильного клиента к информационной базе выполняется только по протоколу HTTP. Подключение по протоколу TCP не поддерживается. При работе мобильного клиента не требуется точного соответствия версий собственно клиента и сервера (или расширения веб-сервера).

Мобильный клиент позволяет с минимальными доработками, в режиме онлайн, получить доступ с мобильных устройств практически ко всей функциональности приложений, для доступа к которым используется тонкий клиент или веб-клиент. Мобильный клиент поддерживает все возможности, специфичные для работы на мобильных устройствах (доступ к фотокамере, геопозиционированию, уведомлениям и т.д.).

Система взаимодействия использует PUSH-уведомления для доставки сообщений, что позволяет доставлять сообщения в то время, когда приложение не запущено и не активно.

Приложение мобильного клиента собирается для работы с определенным списком конфигураций. При этом не поддерживается изменение состава объектов конфигурации для какой-либо информационной базы, к которой подключено приложение мобильного клиента. Изменение конфигурации, без изменения состава объектов, допустимо. При изменении состава объектов необходимо заново опубликовать мобильное приложение. Не поддерживается возможность использования другой конфигурации, которая не включена в собранное приложение. Это обусловлено требованиями размещения приложения мобильного клиента в магазинах приложений. Для контроля соблюдения этого требования применяется цифровая подпись конфигурации, используемой в мобильном клиенте.

Реализована возможность автоматической и полуавтоматической (с использованием новых свойств элементов формы) адаптации форм конфигурации к работе на экранах мобильных устройств. В редакторе управляемой формы реализован предварительный просмотр в режиме мобильного клиента.

Начальная страница в мобильном клиенте, в отличии от мобильной платформы, содержит тот же перечень форм, что и в тонком клиенте и веб-клиенте. При запуске приложения отображается первая форма из этого списка, а остальные доступны по нажатию на кнопку.

В мобильном клиенте поддерживается технология внешних компонент.

В мобильном клиенте не поддерживается интерактивное открытие внешних обработок и отчетов.

Для работы конфигурации в мобильном клиенте требуется установить свойство конфигурации Режим совместимости в значение Версия 8.3.7 и более поздних.

Для конфигуратора реализованы команды интерактивного запуска мобильного клиента на мобильном устройстве.

Для сборщика мобильных приложений реализована возможность выполнять сборку приложения мобильного клиента. При сборке выбирается, является собираемое приложение мобильным клиентом или приложением мобильной платформы.

Реализовано право доступа МобильныйКлиент. Реализована инструкция препроцессора МобильныйКлиент. В синтакс-помощнике реализован новый режим доступности объектов, свойств и методов.

Для управляемой формы реализовано свойство СворачиваниеЭлементовПоВажности. Для элементов управляемой формы реализовано свойство ВажностьПриОтображении, установка которого помогает механизму адаптации формы. Для таблицы управляемой формы реализованы свойства ИспользованиеТекущейСтроки, ПоведениеПриСжатииПоГоризонтали. Для группы формы реализованы свойства ИспользованиеТекущейСтроки, ИспользуемаяТаблица. Реализованы ключи командной строки пакетного режима запуска конфигуратора MobileClientWriteFile, MobileClientDigiSign. Для ключей командной строки пакетного запуска конфигуратора CheckModules и CheckConfig реализован параметр -MobileClient. Для ключа командной строки пакетного запуска конфигуратора CheckConfig реализован параметр -MobileClientDigiSign.

Изменен состав дистрибутива мобильной платформы (mobile.zip). Дистрибутив включает файлы, необходимые для использования мобильного клиента как в процессе разработки, так и для сборки приложения для распространения через магазины приложений.

Перед адаптацией прикладного решения к особенностям эксплуатации на мобильном клиенте, рекомендуется ознакомиться со статьей на диске ИТС (см. здесь).

Данная возможность включена в данную версию для целей бета-тестирования.

Данная возможность не предоставлялась.

Существовала возможность создания автономно работающих специализированных приложений мобильной платформы.

Появилась новая возможность организации работы на мобильных устройствах. В дополнение к существующей возможности мобильной платформы (созданию автономно работающих специализированных мобильных приложений) появилась возможность работы в режиме онлайн, с полной функциональностью приложений (аналогично тонкому и веб-клиенту) без существенной переработки конфигураций.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства администрирования.
Для ключей командной строки пакетного запуска конфигуратора CreateDistributionFiles и CreateDistributive реализован параметр -WarningAsError.Данная возможность не предоставлялась.При формировании дистрибутива прикладного решения стало возможно выполнять более строгую проверку, когда все предупреждения трактуются как ошибки.
Кластер серверов.
В свойствах сеанса и соединения реализованы значения, показывающие время, которое затрачено на выполнение вызовов сервисов кластера от имени сеанса или соединения. Данные значения реализованы для всех средств администрирования: консоль кластера, COM-соединение, интерфейс администрирования из языка Java, сервер администрирования.

Для объектов IInfoBaseConnectionInfo и ISessionInfo реализованы свойства:

  • durationCurrentService - текущее время работы сервиса кластера;
  • CurrentServiceName - имя исполняемого сервиса;
  • durationLast5MinService - время работы сервисов кластера за последние 5 минут;
  • durationAllService - время работы сервисов кластера с начала сеанса или соединения.

Аналогичные свойства реализованы в консоли кластера для списка сеансов, списка соединений и диалога свойств соединения.

Для утилиты командной строки (rac) кластера серверов реализованы параметры duration-current-service, current-service-name, duration-last-5min-service и duration-all-service команд connection list и session list.

Данная возможность не предоставлялась.Стало возможно анализировать время, затраченное на работу сервисов кластера в рамках конкретного сеанса или соединения с информационной базой.
В документации данное изменение описано здесь и здесь.
Системные требования.
Клиентское приложение.
Для работы клиентского приложения под управлением ОС Linux требуется установленная библиотека webkitgtk-3.0 версии 1.4.3 и старше.Для работы клиентского приложения под управлением ОС Linux требовалась установленная библиотека webkitgtk-1.0 версии 1.4.3 и старше.Унифицировано поведение клиентского приложения при работе под управлением ОС Linux и macOS.
В документации данное изменение описано здесь.
Внешние компоненты.
Для определения возможности загрузки внешних компонент из информационной базы реализован метод глобального контекста ПоддерживаетсяДинамическаяУстановкаВнешнихКомпонент().

На мобильных устройствах динамическая загрузка внешних компонент поддерживается только при работе мобильного клиента под управлением ОС Android. В остальных случаях внешние компоненты должны быть включены в состав мобильного приложения и могут использоваться только из макетов конфигурации вида Внешняя компонента.

Также динамическая загрузка внешних компонент поддерживается в толстом клиенте, тонком клиенте и в веб-клиенте (поведение не изменилось).

Внешние компоненты в мобильном приложении могли только входить в состав собранного приложения на этапе сборки и не могли загружаться из информационной базы.

Не предоставлялось возможности определить в конфигурации доступность динамической загрузки внешних компонент.

На мобильном устройстве стало возможно определять возможность загрузки внешних компонент из информационной базы.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Управляемая форма.
Реализована возможность клавиатурной навигации по декорации управляемой формы и полю управляемой формы, если у этих элементов отключено свойство Гиперссылка и они отображают значение типа ФорматированнаяСтрока. +Клавиатурная навигация позволяет перемещаться между различными гиперссылками, установленными в форматированной строке.Данная возможность не предоставлялась.Повышен комфорт работы с управляемой формой.
Веб-клиент.
Табличный документ.
В веб-клиенте реализована возможность интерактивного редактирования табличного документа в полном объеме.

Реализованы команды табличного документа: ВыровнятьРисунокВлево, ВыровнятьРисунокПоЦентру, ВыровнятьРисунокВправо, ВыровнятьРисунокВверх, ВыровнятьРисунокПоСередине, ВыровнятьРисунокВниз, ОдинаковаяШиринаРисунков,

ОдинаковаяВысотаРисунков, ОдинаковыйРазмерРисунков, РаспределитьПоВертикалиРисунки, РаспределитьПоГоризонталиРисунки, ПереместитьВпередРисунок, ПереместитьНазадРисунок, ПереместитьНаПереднийПланРисунок, ПереместитьНаЗаднийПланРисунок.

Функциональность интерактивного изменения табличного документа была ограничена.

Интерактивные команды, настраивающие отображение табличного документа, были доступны в ограниченном объеме.

Не поддерживались возможности отображения заголовков колонок/строк и отображения линий сетки.

Расширены интерактивные возможности работы с табличным документом в веб-клиенте.
В документации данное изменение описано здесь.
Табличный документ.
В диалоге специальной вставки табличного документа в тонком клиенте реализованы возможности управлять вставкой следующих элементов:
  • объединенные ячейки;
  • картинки ячеек;
  • рисунки;
  • группы строк/колонок;
  • колонтитулы.

В диалоге специальной вставки табличного документа удален флажок Все, вместо которого реализованы кнопки отметки и снятия отметки со всех флажков, доступных в диалоге.

Диалог специальной вставки табличного документа в тонком клиенте не позволял управлять вставкой следующих элементов:
  • объединенные ячейки;
  • картинки ячеек;
  • рисунки;
  • группы строк/колонок;
  • колонтитулы.

В диалоге специальной вставки табличного документа присутствовал флажок Все.

Расширены возможности специальной вставки в табличном документе.
Интерфейс.
В формах настройки панели навигации и панели действий для команды Переместить в группу установлена корректная картинка.В формах настройки панели навигации и панели действий для команды Переместить в группу была установлена некорректная картинка.Устранено некорректное поведение системы.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Ускорена отрисовка интерфейса клиентского приложения.

Уменьшено потребление ресурсов операционной системы клиентским приложением.

Отрисовка интерфейса клиентского приложения занимала больше времени, при этом клиентское приложение использовало больше ресурсов операционной системы.Работа с клиентским приложением стала более комфортна для пользователя.
Фоновые и регламентные задания.
Ускорен запуск фоновых заданий.Запуск фоновых заданий требовал больше времени.Ускорен запуск фоновых заданий.
Двоичные данные.
Оптимизирована работа (с точки зрения производительности и использования памяти) следующих функций встроенного языка:
  • ПолучитьСтрокуИзДвоичныхДанных();
  • ПолучитьСтрокуИзБуфераДвоичныхДанных();
  • ПолучитьHexСтрокуИзДвоичныхДанных();
  • ПолучитьHexСтрокуИзБуфераДвоичныхДанных();
  • ПолучитьBase64СтрокуИзДвоичныхДанных();
  • ПолучитьBase64СтрокуИзБуфераДвоичныхДанных().
Следующие функции работали не оптимально с точки зрения производительности и использования памяти:
  • ПолучитьСтрокуИзДвоичныхДанных();
  • ПолучитьСтрокуИзБуфераДвоичныхДанных();
  • ПолучитьHexСтрокуИзДвоичныхДанных();
  • ПолучитьHexСтрокуИзБуфераДвоичныхДанных();
  • ПолучитьBase64СтрокуИзДвоичныхДанных();
  • ПолучитьBase64СтрокуИзБуфераДвоичныхДанных().
Повышена стабильность и скорость работы некоторых функций работы с двоичными данными.
Расширение конфигурации.
Ускорено обновление конфигурации базы данных для расширений конфигурации, не влияющих на структуру базы данных.Обновление конфигурации базы данных для расширений конфигурации, не влияющих на структуру базы данных, занимало больше времени.Ускорено обновление информационной базы в том случае, если применяются изменения для расширений, не оказывающих влияния на структуру информационной базы.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Диаграммы.
Реализована возможность гарантированного отображения на диаграмме Ганта интервалов, размер которых при текущем масштабе диаграммы менее 2-х пикселей. В этом случае размер такого интервала будет равен 2-м пикселям.Интервалы диаграммы Ганта, размер которых при текущем масштабе диаграммы, были менее 2-х пикселей, могли не отображаться на диаграмме в произвольных случаях.Устранено некорректное поведение системы.
Система компоновки данных.
Значение параметра настроек системы компоновки данных АвтоПозицияРесурсов не влияет на вывод общих итогов по вертикали в таблице отчета системы компоновки данных.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Общие итоги по вертикали в таблице отчета системы компоновки данных не выводились, если параметр настроек системы компоновки данных АвтоПозицияРесурсов был установлен в значение НеИспользовать.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства разработки.
В отчете о сравнении конфигураций улучшено отображение различий для свойства ПакетыXDTO объекта Web-сервис. В отчете стала отображаться информация о том, какой пакет добавлен или удален (с указанием имен пакетов), а также информация о пространствах имен этих пакетов.При сравнении конфигураций, отчет для свойства ПакетыXDTO объекта Web-сервис был менее подробным и информативным.Устранено некорректное поведение системы.
Диаграммы.
Табличный документ.
В режиме черно-белого просмотра:
  • диаграммы отображаются в черно-белом режиме;
  • географическая схема отображается в черно-белом режиме;
  • картинки и OLE-объекты отображаются оттенками серого.

В режиме черно-белой печати:

  • диаграммы печатаются в черно-белом режиме (поведение не изменилось);
  • географическая схема печатается в черно-белом режиме (поведение не изменилось);
  • картинки и OLE-объекты печатаются оттенками серого.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

В режиме черно-белого просмотра:
  • диаграммы отображались цветными;
  • географическая схема отображалась цветной;
  • OLE-объекты отображались цветными;
  • картинки в форматах svg, emf и wmf отображались цветными;
  • картинки в других форматах отображались оттенками серого.

В режиме черно-белой печати:

  • диаграммы печатались в черно-белом режиме;
  • географическая схема печатались в черно-белом режиме;
  • OLE-объекты печатались цветными;
  • картинки в форматах svg, emf и wmf печатались цветными;
  • картинки в других форматах печатались оттенками серого.
Устранено различие в поведении при черно-белом просмотре и черно-белой печати для различных объектов, которые могут быть размещены в табличном документе.
В документации данное изменение описано здесь.
Диаграммы.
Узор заливки при печати диаграммы в черно-белом виде подбирается на основе цвета, но если полученный узор уже используется в данной диаграмме - используется следующий узор из доступных. В случае, если использованы все доступные узоры - они начинают использоваться повторно. Количество доступных узоров заливки увеличено до 27.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Узор заливки при печати диаграммы в черно-белом виде подбирался на основе цвета, без анализа использования. Количество доступных узоров заливки было равно 12.Улучшено отображение диаграммы при черно-белой печати.
В документации данное изменение описано здесь.
Внешние источники данных.
При обновлении конфигурации выполняется проверка команд кубов и таблиц измерений внешних источников данных на указание значения для свойства Группа у команды указанных объектов. Если свойство не заполнено - обновление не выполняется.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При обновлении конфигурации не выполнялась проверка команд кубов и таблиц измерений внешних источников данных на указание значения для свойства Группа у команды указанных объектов.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
История данных.
Расширение конфигурации.
Реализована возможность использовать историю данных для собственных и заимствованных объектов расширения.Использование истории данных было недоступно для собственных и заимствованных объектов расширения конфигурации.Стало возможно совместное использование истории данных и расширений конфигурации.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность управления нумерацией страниц, выводимых в колонтитулах табличного документа.

Реализовано свойство ТабличныйДокумент.НомерПервойСтраницы. В диалоге редактирования колонтитулов табличного документа реализована возможность указания номера первой страницы.

При экспорте табличного документа в форматы Open XML и OpenDocument, номер первой страницы подставляется в соответствующее свойство документа.

Данная возможность не предоставлялась.

Страницы всегда нумеровались с 1.

Позволяет обеспечить формирование табличных документов, отвечающих требованиям контролирующих органов.
Работа с Интернет.
Прекращено использование библиотеки imaplib.

Поведение объекта ИнтернетПочта не изменилось и обеспечивается текущими средствами платформы.

Платформа «1С:Предприятие» использовала библиотеку imaplib для обеспечения работы объекта ИнтернетПочта в режиме совместимости Версия 8.3.5 и младше.Повышена стабильность и безопасность платформы.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Интерфейс.
Переработан внешний вид стандартной формы полнотекстового поиска.

В библиотеку картинок добавлена картинка История.

Стандартная форма полнотекстового поиска имела другой внешний вид.Стандартная форма полнотекстового поиска стала более удобна для использования.
В документации данное изменение описано здесь.
Средства разработки.
В редакторе управляемой формы реализовано:
  • В подменю выбора устройства (для просмотра формы «на мобильном устройстве») реализована отметка выбранного в данный момент устройства.
  • В подменю выбора масштаба просмотра (для просмотра формы «на мобильном устройстве») реализована отметка текущего масштаба. Также в данном меню реализованы варианты масштаба, аналогичные просмотру формы «на персональном компьютере».
  • В подменю выбора масштаба просмотра (для просмотра формы «на персональном компьютере») реализована отметка текущего масштаба.
  • В подменю выбора разрешения просмотра (для просмотра форма «на персональном компьютере») реализованы:
    • отображение текущего разрешения;
    • возможность выбора текущего монитора (монитора, на котором отображается окно конфигуратора);
    • отображение для каждого разрешения типичной плотности точек для этого разрешения;
    • возможность выбора мониторов с разрешение 4К (3840*2160 точек) и 5К (5120*2880 точек).
Данная возможности отсутствовали в редакторе формы.Улучшена эргономика редактора формы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если параметр запроса находится в выражении языка запросов, для которого было установлено имя, или параметр присутствует в выражении как самостоятельное выражение, то такой параметр будет считаться доступным для использования в параметрах данных системы компоновки данных, с ограничением видимости для конечного пользователя.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если параметр запроса находился в выражении языка запросов, для которого было установлено имя, или параметр присутствовал в выражении как самостоятельное выражение, то такой параметр не помещался в список доступных параметров данных системы компоновки данных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
Если колонка таблицы, связанной с динамическим списком, находится в группе колонок с группировкой В ячейке, то в документе, полученном путем выполнения команды Вывести список, для этой колонки в качестве заголовка будет использоваться заголовок колонки таблицы управляемой формы.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если колонка таблицы, связанной с динамическим списком, находится в группе колонок с группировкой В ячейке, то в документе, полученном путем выполнения команды Вывести список:
  • В тонком клиенте для этой колонки в качестве заголовка использовалось имя колонки таблицы формы.
  • В веб-клиенте для этой колонки в качестве заголовка использовался заголовок колонки таблицы формы.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Автоматизированное тестирование.
Реализована возможность устанавливать и получать максимальное время выполнения действия в тестируемом приложении.

Для объекта ТестируемоеПриложение реализованы методы УстановитьМаксимальноеВремяВыполненияДействия() и ПолучитьМаксимальноеВремяВыполненияДействия().

Уточнены тексты сообщений об ошибках, которые возникают во время попытки подключиться к тестируемому приложению и выполнить требуемые действия.

Установка и получение максимального времени выполнения действия в тестируемом приложении было недоступно.

Тексты сообщений об ошибках, которые возникают во время попытки подключиться к тестируемому приложению и выполнить требуемые действия, были менее подробны и точны.

Стало возможно устанавливать максимальное время выполнения действий в тестируемом приложении.

Улучшена диагностика ошибок при работе механизмов автоматизированного тестирования.

Табличный документ.
Если у табличного документа установлены области фиксации строк или колонок, то линии фиксации отображаются в табличном документе только в том случае, если в табличном документе выполнена прокрутка в вертикальном или горизонтальном положении (соответственно).

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если у табличного документа установлены области фиксации строк или колонок, то линии фиксации отображались в табличном документе всегда.Улучшен внешний вид отчетов.
Управляемая форма.
Если у группы управляемой формы задана ширина, которая меньше минимальной ширины подчиненных элементов, то заданная ширина игнорируется и определятся следующим образом:
  • для вертикальной группировки - как максимальное значение из минимальных (несжимаемых) размеров подчиненных элементов;
  • для горизонтальной группировки - как сумма минимальных (несжимаемых) размеров элементов плюс сумма всех расстояний между элементами группы.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если у группы управляемой формы задана ширина, в которую не помещались подчиненные элементы, то группа могла уменьшаться даже в том случае, когда вложенные элементы дальше уменьшаться не могли.Устранено некорректное поведение системы.
В документации данное изменение описано здесь, здесь и здесь.
Работа с запросами.
При исполнении запроса, который содержит во вложенном запросе предложение АВТОУПОРЯДОЧИВАНИЕ, формируется ошибка Во вложенных запросах нельзя применять операцию АВТОУПОРЯДОЧИВАНИЕ.При исполнении запроса, который содержит во вложенном запросе предложение АВТОУПОРЯДОЧИВАНИЕ, формировалась ошибка Во вложенных запросах нельзя применять операцию УПОРЯДОЧИТЬ ПО без использования конструкции ПЕРВЫЕ.Сообщение об ошибке стало более точно описывать причину ошибки.
Расширение конфигурации.
Сообщения, которые формируются системой во время применения расширений, отображаются со статусом Важное. Такие сообщения сохраняются в центре уведомлений и могут быть прочитаны пользователем даже если он не увидел эти сообщения в момент их (сообщений) генерации.Сообщения, которые формируются системой во время применения расширений, отображались со статусом Информация. Такие сообщения не сохранялись в центре уведомлений и пользователь не знал, что возникли проблемы с подключением расширения, если он не мог увидеть эти сообщения непосредственно в момент их (сообщений) формирования.Улучшена диагностика проблем, возникающих при подключении расширений.
Система компоновки данных.
Динамический список.
Конструктор схемы компоновки данных при добавлении нового параметра в запрос набора данных, автоматически устанавливает возможность использования списка значений для добавляемого параметра, если в запросе этот параметр используется в операции В.

Если в схеме компоновки данных отсутствует описание параметра, используемого в запросе, то в источнике доступных настроек компоновки данных в доступном параметре автоматически устанавливается возможность использовать в параметре списка значений, если в запросе этот параметр находится в операции В.

Если в запросе динамического списка параметр расположен в операции В, то в настройках компоновки данных динамического списка данный параметр может принимать список значений и динамический список будет корректно передавать установленный список значений в запрос.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Конструктор схемы компоновки данных автоматически не заполнял признак возможности использования списка значений в параметре схемы компоновки данных.

Если в схеме компоновки данных отсутствует описание параметра, то считалось, что в данный параметр можно передавать только единичные значения.

Динамический список некорректно отрабатывал установку списка значений для параметра запроса.

Устранено некорректное поведение системы.

Улучшено поведение системы компоновки данных в том случае, если запрос позволяет использовать списки значений для установки отбора.

Система компоновки данных.
После макетов заголовков (отчета, таблицы, группировки, диаграммы) системы компоновки данных не выводится макет с пустой строкой. В результате после заголовков таблиц и диаграмм будет выводиться только одна пустая строка.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

После макетов заголовков (отчета, таблицы, группировки, диаграммы) системы компоновки данных в некоторых случаях выводился макет с пустой строкой. В результате после заголовков таблиц и диаграмм выводилось две пустые строки.Устранено некорректное поведение системы.

После заголовков таблиц и диаграмм будет выводиться одна пустая строка, а не две.

В документации данное изменение описано здесь.
Стандартные функции.
В стандартной функции управления полнотекстовым поиском реализована возможность установки максимального размера объекта, индексируемого полнотекстовым поиском и количества фоновых заданий, используемых для выполнения индексирования.

Для установки этих параметров предназначен диалог, который открывается при нажатии кнопки Дополнительные параметры, размещенной в форме стандартной функции.

Данная возможность не предоставлялась.Стало возможно настраивать значения дополнительных параметров работы полнотекстового поиска.
В документации данное изменение описано здесь.
Табличный документ.
При сохранении табличного документа в тонком клиенте в формате PDF, в качестве размера страницы используется размер страницы текущего принтера в том случае, если для табличного документа не указан размер страницы.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При сохранении табличного документа в тонком клиенте в формате PDF, в качестве размера страницы использовался размер формата А4 в том случае, если для табличного документа не был указан размер страницы.Устранено некорректное поведение системы.
Отображение информации.
При указании абсолютного шрифта в диалоге выбора шрифта (в конфигураторе, тонком и толстом клиентах) учитывается свойство Масштаб.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При указании абсолютного шрифта в диалоге выбора шрифта (в конфигураторе, тонком и толстом клиентах) игнорировалось свойство Масштаб.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
В управляемом приложении, при интерактивном редактировании параметров оформления и параметров вывода системы компоновки данных, установка признака использования у редактируемого параметра не приводит к установке этого флага у родительского параметра.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

В управляемом приложении, при интерактивном редактировании параметров оформления и параметров вывода системы компоновки данных, установка признака использования у редактируемого параметра приводило к установке этого флага у родительского параметра.Устранено некорректное поведение системы.
Управляемая форма.
Поле ввода, которое в палитре свойств связано со свойством, содержащим шрифт, отображает имя выбранного шрифта, его стиль, оформление и масштаб.Поле ввода, которое в палитре свойств связано со свойством, содержащим шрифт, отображало имя выбранного шрифта и его стиль.Характеристики установленного шрифта стало можно оценить без открытия диалога выбора шрифта, а сразу в палитре свойств.
Управляемая форма.
Для системного перечисления ГруппировкаПодчиненныхЭлементовФормы реализовано значение ГоризонтальнаяВсегда.

Значение системного перечисления ГруппировкаПодчиненныхЭлементовФормы.Горизонтальная считается устаревшим.

В том случае, если в существующем прикладном решении используется значение Горизонтальная, то на платформе для персонального компьютера фактически будет использоваться значение ГоризонтальнаяВсегда, а на мобильных устройствах - ГоризонтальнаяЕслиВозможно.

В прикладных решениях, в большинстве случаев, рекомендуется заменить значение Горизонтальная на ГоризонтальнаяЕслиВозможно. Значение ГоризонтальнаяВсегда рекомендуется устанавливать только в тех случаях, когда группа должна быть горизонтальной при любой ширине экрана (включая и смартфон). Например, если группа включает поле ввода и кнопку с картинкой без текста, логически связанную с этим полем.

Для формы и группы предоставлялась возможность указывать следующие варианты расположения элементов по горизонтали: Горизонтальная и ГоризонтальнаяЕслиВозможно.Обеспечена возможность плавного перехода ранее созданных форм к работе в мобильном клиенте.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Хранение настроек.
Если при открытии формы отчета указан параметр КлючПользовательскихНастроек и не указан параметр ПользовательскиеНастройки, то:
  • Если в хранилище пользовательских настроек отчетов есть настройки с указанным ключом - будут загружены они.
  • В противном случае будут загружены пользовательские настройки по умолчанию для текущего варианта отчета.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если при открытии формы отчета указан параметр КлючПользовательскихНастроек и не указан параметр ПользовательскиеНастройки, то:
  • Если для текущего варианта отчета в хранилище системных настроек были сохранены пользовательские настройки, то будут загружены именно они.
  • В противном случае, если в хранилище пользовательских настроек существуют настройки с указанным ключом, то будут загружены эти настройки.
  • Иначе будут установлены настройки по умолчанию для текущего варианта.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Установка клиентского приложения.
При автоматическом поиске версий для установки, интерактивная программа запуска выполняет поиск дистрибутива для установки в каталогах Setup (дистрибутив 32-разрядной версии платформы) и Setup64full (дистрибутив 64-разрядной версии платформы) каталога с номером версии платформы.При автоматическом поиске версий для установки, интерактивная программа запуска выполняла поиск дистрибутива для установки только в каталоге с номером версии платформы. Все подкаталоги данного каталога игнорировались,Автоматическое обновление клиентского приложения стало учитывать, что клиентское приложение может быть одновременно и 32- и 64-разрядным.
В документации данное изменение описано здесь.
Диаграммы.
При вызове обработчика события ПриОкончанииРедактированияИнтервала элемента формы, отображающего диаграмму Ганта:
  • В качестве значения параметра Интервал передается сам интервал диаграммы.
  • Значения, измененные в переданном интервале, будут перенесены в диаграмму, если параметр обработчика ОтменаРедактирования не установлен в значение Истина.
  • Если параметр обработчика ОтменаРедактирования установлен в значение Истина, то в свойства интервала Начало и Конец будут установлены значения, которые были до начала редактирования, а в остальные значения будут скопированы значения из интервала.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При вызове обработчика события ПриОкончанииРедактированияИнтервала элемента формы, отображающего диаграмму Ганта:
  • В качестве значения параметра Интервал передавалась копия интервала диаграммы.
  • Изменения, сделанные в переданном интервале, никогда не сохранялись в диаграмме.
Поведение обработчика события ПриОкончанииРедактированияИнтервала для элемента формы, отображающего диаграмму Ганта, стало более ожидаемым для разработчика.
В документации данное изменение описано здесь.
Журнал регистрации.
Реализована возможность интерактивного изменения формата журнала регистрации.

Смена формата журнала регистрации фиксируется новым событием журнала регистрации (_$InfoBase$_.EventLogSettingsUpdate).

При работе в файловом варианте информационной базы для смены формата журнала регистрации требуется монопольный доступ к базе.

Метод глобального контекста ОчиститьЖурналРегистрации() применим только к журналу в формата SQLite, признан устаревшим и его использование не рекомендуется.

Реализована возможность прерывать длительную выборку из журнала регистрации с помощью удаления соответствующего сеанса.

Реализовано ограничение на одновременное количество сеансов, выполняющих длительные выборки из журнала регистрации:

  • в обычной информационной базе - 4 сеанса;
  • в разделенной информационной базе - 1 сеанс на область данных.

При создании новой информационной базы в качестве формата по умолчанию используется последовательный формат журнала регистрации.

Возможность интерактивной смены формата журнала регистрации была недоступна.

При создании новой информационной базы использовался технологический журнал в формате SQLite.

Стало возможно интерактивно выбирать формат журнала регистрации.

Исключены «зависания» системы при выполнении длительных выборок из журнала регистрации.

В документации данное изменение описано здесь, здесь и здесь.
Временное хранилище.
Повторное указание в качестве параметра Адрес метода ПоместитьВоВременноеХранилище() значения, для которого применялся метод УдалитьИзВременногоХранилища(), приведет к исключению.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Повторное указание в качестве параметра Адрес метода ПоместитьВоВременноеХранилище() значения, для которого применялся метод УдалитьИзВременногоХранилища(), было возможно только в том случае, если форма, уникальный идентификатор которой передавался в качестве параметра метода ПоместитьВоВременноеХранилище(), была открыта во время последующих помещений во временное хранилище.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь и здесь.
Диаграммы.
Изменен алгоритм отображения диаграмм с накоплением, при условии наличия отрицательных значений:
  • Для диаграмм, поддерживающих базовое значение:
    • Для каждой точки рассчитываются две суммы: больше и меньше базового значения.
    • Перед накоплением из текущего значения вычитается базовое значение.
    • Получившееся значение накапливается по абсолютному значению в соответствующей сумме (в зависимости от знака).
  • Для диаграмм, не поддерживающих базовое значение:
    • Для каждой точки рассчитываются две суммы: больше и меньше значение 0.
    • Текущее значение накапливается по абсолютному значению в соответствующей сумме (в зависимости от знака).
  • Для каждой точки отображается два столбца диаграммы: накопленная сумма положительных и отрицательных значений.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При расчете высоты столбцов в диаграммах с накоплением использовалась одна сумма по каждой точке, с которой выполнялось суммированием значений с учетом знака.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При установке источника доступных настроек компоновщику настроек системы компоновки данных, если значение параметра данных содержит массив, и при этом у параметра включена возможность использования списка значений, то в значение параметра помещается список значений, содержащий все значения, которые были в исходном массиве значений.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При установке источника доступных настроек компоновщику настроек системы компоновки данных, если значение параметра данных содержит массив, и при этом у параметра включена возможность использования списка значений, то в значение параметра помещался список значений, содержащий один элемент, со значением, равным значению по умолчанию для типа значения, указанного у параметра.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
При установке из встроенного языка, а также при загрузке конфигурации из файлов XML, свойств элемента формы ПутьКДанным, ПутьКДаннымПодвала, ПутькДаннымШапки, ПутьКДаннымЗаголовка и ПутьКДаннымКартинкиСтроки генерируется ошибка, если устанавливается путь, ссылающийся на элемент формы и при этом содержащий индекс строки.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если при установке из встроенного языка, а также при загрузке конфигурации из файлов XML, в качестве значения свойства элемента формы ПутьКДанным, ПутьКДаннымПодвала, ПутькДаннымШапки, ПутьКДаннымПодвала и ПутьКДаннымКартинкиСтроки устанавливался путь, ссылающийся на элемент формы и при этом содержащий индекс строки, то ошибка не генерировалась, значение устанавливалось, но установленное значение свойства игнорировалось (по сути - присваивание не работало).Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
В источнике доступных настроек системы компоновки данных для динамического списка, недоступны для отбора, сортировки и группировки поля, которые являются дочерними полями-характеристиками полей табличных частей, полученных через точку (например, Ссылка.Товары.Товар.[Страна происхождения]).

В режиме совместимости с версией 8.3.11 поведение не изменилось.

В источнике доступных настроек системы компоновки данных для динамического списка, были доступны для отбора, сортировки и группировки поля, которые являются дочерними полями-характеристиками полей табличных частей, полученных через точку (например, Ссылка.Товары.Товар.[Страна происхождения]). Однако, попытка установить отбор по значению такого поля приводил к ошибке.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если для вычисляемого поля системы компоновки данных указано пустое выражение, то в качестве значения такого поля в детальных записях будет использоваться NULL.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если для вычисляемого поля системы компоновки данных указано пустое выражение, то при попытке использовать такое поле в детальных записях генерировалась ошибка с сообщением о том, что поле не найдено.Устранено некорректное поведение системы.

При выборе пользователем пользовательского поля без указанного выражения, поведение стало более корректным.

В документации данное изменение описано здесь.
Система компоновки данных.
Если во время вычисления функции системы компоновки данных ВычислитьВыражение() будет обнаружено деление на 0, то результат вычисления выражения, включающего вызов функции ВычислитьВыражение(), будет равно строке Деление на 0.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Если во время вычисления функции системы компоновки данных ВычислитьВыражение() будет обнаружено деление на 0, то выражение, включающее вызов этой функции, полностью вычислялось, но в качестве результата работы функции ВычислитьВыражение() выступала строка Деление на 0.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Хранение настроек.
Проверка права доступа СохранениеДанныхПользователя выполняется перед выполнением любой операции с хранилищем стандартных настроек.

Реализована проверка права доступа СохранениеДанныхПользователя при вызове метода СтандартноеХранилищеНастроекМенеджер.УстановитьОписание().

Проверка права доступа СохранениеДанныхПользователя выполнялась перед выполнением операции с хранилищем стандартных настроек только при обращении из встроенного языка.

При вызове метода СтандартноеХранилищеНастроекМенеджер.УстановитьОписание() проверка права доступа СохранениеДанныхПользователя не выполнялась.

Устранено незапланированное поведение системы. В частности, стали недоступны команды работы с настройками динамического списка для пользователя, у которого отсутствует право доступа СохранениеДанныхПользователя.
Система компоновки данных.
Элементы условного оформления системы компоновки данных применяются в соответствии со следующими приоритетами:
  • Чем «ближе» к области применения находится элемент условного оформления, тем выше у него приоритет (поведение не изменилось). Например, если есть условное оформление у всего отчета, у таблицы и у группировки таблицы, то наивысший приоритет будет у условного оформления группировки, потом – таблицы, потом – всего отчета.
  • В рамках одного списка элементов условного оформления, чем ниже элемент условного оформления находится в списке элементов условного оформления, тем выше у него приоритет.

В режиме совместимости с версией 8.3.11 поведение не изменилось. +

Элементы условного оформления системы компоновки данных применялись в соответствии со следующими приоритетами:
  • Чем «ближе» к области применения находился элемент условного оформления, тем выше у него приоритет.
  • В рамках одного списка элементов условного оформления, чем ниже элемент условного оформления находился в списке элементов условного оформления, тем выше у него приоритет. Исключение составлял случай, когда в списке условных оформлений присутствуют оформления с заданными и не заданными оформляемыми полями и у них есть заданные отборы. В этом случае сначала применялись условные оформления, которым заданы оформляемые поля, а затем условные оформления с не заданными оформляемыми полями.
Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При формировании строки представления отбора системы компоновки данных (в формах отчета и динамического списка) учитывается квалификатор, который указан для поля компоновки данных, по которому выполняется отбор.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При формировании строки представления отбора системы компоновки данных (в формах отчета и динамического списка) не учитывался квалификатор, который указан для поля компоновки данных, по которому выполняется отбор.Улучшено представление отборов в отчетах, построенных с помощью системы компоновки данных, и динамических списках.
В документации данное изменение описано здесь.
Работа с информационными базами.
Изменено поведение системы при установке административных параметров информационной базы из встроенного языка в том случае, если установка параметров происходит в рамках транзакции. Подробности приведены в документации.Поведение системы при установке административных параметров информационной базы из встроенного языка в том случае, если установка параметров происходит в рамках транзакции, было другим и не было документировано.Поведение системы при установке административных параметров информационной базе стало более очевидным и предсказуемым.
В документации данное изменение описано здесь.
Интерфейс.
Вызов метода глобального контекста ПереключитьИнтерфейс() игнорируется при работе в управляемом режиме в любом клиентском приложении.

Не рекомендуется использовать обычные формы при работе в управляемом режиме клиентского приложения.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Вызов метода глобального контекста ПереключитьИнтерфейс() при работе в управляемом режиме приводил к отображению командных панелей, настроенных в конфигурации.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Встроенный язык.
Функция глобального контекста ТекущийЯзык() при выполнении на сервере, в толстом клиенте и во внешнем соединении возвращает язык интерфейса, выбранный для текущего пользователя или основной язык конфигурации в том случае, если отсутствует текущий пользователь, для текущего пользователя не указан язык или указан несуществующий в конфигурации язык.

Функция ТекущийЯзык() работает одинаково во всех вариантах использования.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Функция глобального контекста ТекущийЯзык() при выполнении на сервере, в толстом клиенте и во внешнем соединении возвращала значение Неопределено в том случае, если для текущего пользователя указан несуществующий в конфигурации язык.

Поведение функции ТекущийЯзык() различалось при работе на стороне сервера и на стороне клиентских приложений.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Если во вложенном запросе, находящемся в правой части левого соединения, поле явно не указано в предложении {ГДЕ}, и во внешнем запросе для поля с таким же именем компоновки данных используется не точно это же поле, то компоновщик макета компоновки данных не будет размещать отбор во вложенном запросе.

При необходимости обеспечить прежнее поведение, разработчику следует явно указать поле доступным для отбора в запросе с помощью предложения {ГДЕ}.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При использовании автоматического заполнения доступных полей набора данных, компоновщик макета компоновки данных всегда размещал отбор во вложенном запросе.Повышена предсказуемость результата компоновки данных при использовании автоматического заполнения доступных полей набора данных-запроса.
Работа с Интернет.
При использовании метода ИнтернетПочта.Подключиться() реализована попытка аутентификации с помощью имени пользователя и пароля, если аутентификация по протоколу APOP закончилась неудачей.При использовании метода ИнтернетПочта.Подключиться() генерировалась ошибка, если аутентификация по протоколу APOP закончилась неудачей. Попытка аутентификации с помощью имени пользователя и пароля не выполнялась.Работа с почтовым сервером при выполнении аутентификации пользователя стала лучше соответствовать стандарту RFC 1939.
Управляемая форма.
При выполнении метода ОткрытьФорму() изменен алгоритм поиска открытого экземпляра открываемой формы:
  • При открытии форм обработок и любых форм отчетов - поиск открытой формы учитывает владельца открываемой формы.
  • При открытии основной формы, установленной в свойствах конфигурации, или формы, переопределенной в обработчике ОбработкаПолученияФормы(), без указания владельца, без необходимости блокировки окна владельца и в случае наличия открытого экземпляра открываемой формы - будет найдена уже открытая форма (в тонком и веб-клиентах).

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При выполнении метода ОткрытьФорму() использовался следующий алгоритм поиска открытого экземпляра открываемой формы:
  • При открытии форм обработок и любых форм отчетов - поиск открытой формы не учитывал владельца открываемой формы.
  • При открытии основной формы, установленной в свойствах конфигурации, или формы, переопределенной в обработчике ОбработкаПолученияФормы(), без указания владельца, без необходимости блокировки окна владельца и в случае наличия открытого экземпляра открываемой формы - открывался новый экземпляр формы (в тонком и веб-клиентах).
Устранено некорректное поведение системы. Унифицирован алгоритм поиска открытой формы для различных клиентских приложений.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Параметры ключа командной строки пакетного запуска конфигуратора CompareCfg, отвечающие за определение первой и второй конфигураций для сравнения.
  • FirstConfigurationKey,
  • SecondConfigurationKey.
  • FirstConfigurationType,
  • SecondConfigurationType.
Ключи командной строки пакетного запуска конфигуратора при работе с приложением для мобильного устройства. Старые наименования поддерживаются для совместимости.
  • MAUpdatePublication;
  • MAWriteFile.
  • MobileAppUpdatePublication;
  • MobileAppWriteFile.
Назначения использования конфигурации и управляемых форм. Старые наименования поддерживаются для совместимости.
  • МобильноеУстройство;
  • ПерсональныйКомпьютер.
  • ПриложениеМобильнойПлатформы;
  • ПриложениеПлатформы.
Группы команд табличного документа.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

  • Печать;
  • Вид;
  • Форматирование;
  • Шрифт;
  • Границы;
  • Выравнивание;
  • Группы;
  • Имена;
  • НастройкиПечати;
  • Рисунки;
  • Выравнивание1;
  • Размер;
  • Распределить;
  • Порядок;
  • Примечания;
  • Ячейки;
  • Объединение;
  • Вставить;
  • ВставкаСтрок;
  • ВставкаКолонок;
  • ОтобразитьСкрытьЯчейки;
  • Размеры;
  • Прочее;
  • Прочее1;
  • Прочее2;
  • Прочее3.
  • КомандыПечать;
  • КомандыВид;
  • КомандыФорматирование;
  • КомандыШрифт;
  • КомандыГраницы;
  • КомандыВыравнивание;
  • КомандыГруппы;
  • КомандыИмена;
  • КомандыНастройкиПечати;
  • КомандыРисунки;
  • КомандыВыравниваниеРисунков;
  • КомандыРазмер;
  • КомандыРаспределить;
  • КомандыПорядок;
  • КомандыПримечания;
  • КомандыЯчейки;
  • КомандыОбъединение;
  • КомандыВставить;
  • КомандыВставкаСтрок;
  • КомандыВставкаКолонок;
  • КомандыОтобразитьСкрытьЯчейки;
  • КомандыРазмеры;
  • КомандыПрочее;
  • КомандыПрочееОткат;
  • КомандыПрочееБуферОбмена;
  • КомандыПрочееСвойства.

Оглавление

Мобильная версия «1С:Предприятия»

ФункциональностьКак сталоКак былоРезультат изменения
Управляемая форма.
Контекстное меню (при работе под управлением ОС Android) открывается непосредственно рядом с элементом формы, откуда вызывается это меню. При этом не происходит перестроения формы, в котором выполняется открытие контекстного меню.Контекстное меню формировалось в верхней части формы, в которой располагался элемент для которого требовалось открыть контекстное меню. Это приводило к перестроению формы и смещению элементов формы.При работе под управлением ОС Android, работа с формой в мобильном приложении стала более комфортной при использовании контекстных меню.
Специальные возможности мобильного устройства.
Оптимизирован процесс формирования объекта ДанныеМультимедиа при работе с камерой мобильного устройства.

В документации отражены рекомендации работе с фотокамерой мобильного устройства.

Формирование объекта ДанныеМультимедиа при работе с камерой мобильного устройства выполнялось недостаточно оптимально.Ускорена работа мобильного приложения при использовании фотокамеры мобильного устройства.
В документации данное изменение описано здесь.
Интерфейс.
Изменено отображение календаря на мобильном устройстве:
  • текущая дата отображается более заметно;
  • реализована возможность переключаться между выбором одной даты или нескольких дат;
  • реализовано контекстное меню;
  • реализовано событие Выбор.
Календарь на мобильном устройстве работал по-другому:
  • текущая дата отображалась менее заметно;
  • не поддерживалась возможность переключаться между выбором одной даты или нескольких дат (всегда использовался выбор нескольких дат);
  • отсутствовало контекстное меню;
  • отсутствовало реализовано событие Выбор.
Календарь на мобильном устройстве стал более комфортным в использовании.

Оглавление

Обновление используемых библиотек

Оглавление

Изменения в демонстрационных конфигурациях

Оглавление

Изменения, выполненные после публикации версии

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Для расширения работы с файлами, которое применяется для веб-браузеров Google Chrome и Mozilla Firefox, реализованы следующие возможности:
  • Аутентификация на веб-сервере с использованием сертификата. Пользователю будет предложен диалог выбора сертификата, который будет использован для аутентификации.
  • Использование аутентификации ОС в том случае, если компьютер, на котором запущен веб-клиент, не входит в домен, а на веб-сервере настроена аутентификация ОС. Пользователю будет предложено указать имя пользователя и пароль для доступа к домену. +
Расширение работы с файлами, которое применяется для веб-браузеров Google Chrome и Mozilla Firefox, не поддерживало следующие возможности:
  • Аутентификация на веб-сервере с использованием сертификата.
  • Использование аутентификации ОС в том случае, если компьютер, на котором запущен веб-клиент, не входит в домен, а на веб-сервере настроена аутентификация ОС.
Расширены возможности работы с защищенным соединением. Повышена безопасность использования веб-клиента.
Веб-клиент.
Перетаскивания ячеек и рисунков табличного документа, который отображается в веб-клиенте, обрабатывается общепринятым способом: выделенные элементы копируются, если во время перетаскивания нажата клавиша Ctrl и перемещаются, если клавиша Ctrl не нажата.

Поведение веб-клиента стало аналогичным поведению тонкого клиента.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

В табличном документе, который отображается в веб-клиенте, не поддерживались операции перетаскивания для ячеек и рисунков.Расширены интерактивные возможности работы с табличным документом в веб-клиенте.
Автоматизированное тестирование.
Значение свойства ТекстЗаголовка объектов типа ТестируемоеПолеФормы (и аналогичных), которые получены с помощью методов НайтиОбъект() или НайтиОбъекты(), во всех случаях содержит значение заголовка, заданное в конфигураторе.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Значение свойства ТекстЗаголовка объектов типа ТестируемоеПолеФормы (и аналогичных), которые получены с помощью методов НайтиОбъект() или НайтиОбъекты(), могло в некоторых случаях не содержать двоеточие, если заголовок для элемента управления задавался в редакторе формы, а не генерировался автоматически.Устранено некорректное поведение системы.
Управляемая форма.
Изменение доступности групп элементов управляемой формы и элементов формы, расположенных в таблицах управляемой формы, не требует обращения к серверу.

При установке полю ввода свойства Видимость в значение Ложь, будут выполнены следующие действия:

  • Для поля, связанного с текстовым значением, будет сформировано значение из введенного текста, и вызывается обработчик события ПриИзменении.
  • Поле, связанное со ссылочным значением, может остаться в не консистентном состоянии при незавершенном вводе.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Изменение доступности групп элементов управляемой формы и элементов формы, расположенных в таблицах управляемой формы, приводило к вызову сервера.

При установке полю ввода свойства Видимость в значение Ложь, выполнялись следующие действия:

  • Для поля, связанного с текстовым значением, будет сформировано значение из введенного текста, но обработчик события ПриИзменении вызван не будет.
  • Для поля, связанного со ссылочным значением, восстанавливалось предыдущее значение.
Снижены затраты на изменение доступности некоторых элементов управляемой формы.
Мобильная платформа.
Мобильный клиент.
В списке приложений, доступного из главного меню мобильного приложения и мобильного клиента, реализованы возможности:
  • выполнить ручное упорядочивание списка;
  • упорядочить список приложений по алфавиту;
  • работать со списком общих информационных баз (только для мобильного клиента).

В списке приложений, для каждого приложения, реализована возможность указывать параметры командной строки запуска клиентского приложения. Для мобильного приложения и мобильного клиента реализована поддержка следующих параметров командной строки запуска клиентского приложения: N, P, ClearCache, C, WSA, OIDA, Autooff, DisableStartupMessahes, Z, UsePrivilegedMode, HttpsForceSSLv3, HttpsForceTLS1_0, O, L, VL, WSN, WSP, URL. Реализована возможность однократно запустить приложение с необходимым набором поддерживаемых параметров командной строки запуска.

Данные возможности не предоставлялись.Расширены возможности по управлению списком приложений. Для приложений стало возможно указывать параметры командной строки, позволяющие более тонко управлять запуском этих приложений.
В документации данное изменение описано здесь.
Управляемая форма.
Элементы управляемой формы сжимаются меньше своей минимальной ширины в том случае, если ширины формы становится недостаточно для размещения элемента формы минимальной ширины. Изменение действует во всех клиентских приложениях и в мобильной платформе.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Элементы управляемой формы не сжимались меньше своей минимальной ширины в том случае, если ширины формы становилось недостаточно для размещения элемента формы минимальной ширины.Устранено некорректное поведение системы.
Система компоновки данных.
При генерации макета заголовков компоновки данных на основе предопределенного макета, при необходимости, устанавливается фиксация строк и колонок.

Фиксация колонок (свойство ячейки области макета компоновки данных ФиксироватьСлева) устанавливается в том случае, если параметр отчета ФиксироватьСлева установлен в значение Авто или не установлен. Фиксация строк (свойство ФиксироватьСверху) устанавливается в том случае, если параметр отчета ФиксироватьСверху имеет значение Авто или не установлен.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При генерации макета заголовка компоновки данных на основе предопределенного макета никогда не устанавливалась фиксация строк и колонок. Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
В запросе, который содержит выражение ОБЪЕДИНИТЬ (без ключевого слова ВСЕ), операция ВЫРАЗИТЬ КАК Ссылка в результате будет содержать одну строку со значением NULL.

Функция ЕСТЬNULL() от выражения ВЫРАЗИТЬ КАК Ссылка возвращает корректный результат.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

Запрос с предложением ОБЪЕДИНИТЬ мог не удалять дублирующиеся NULL, полученные операцией ВЫРАЗИТЬ КАК Ссылка.

Функция ЕСТЬNULL() от выражения ВЫРАЗИТЬ КАК Ссылка могла вернуть некорректный результат.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система взаимодействия.
Уточнены сообщения об ошибках для некоторых сценариев использования системы взаимодействия.Сообщения об ошибках для некоторых сценариев использования системы взаимодействия были менее информативными.Повышена информативность сообщений об ошибках при работе системы взаимодействия.
Система компоновки данных.
При установке источника доступных настроек компоновщику настроек системы компоновки данных, если значение параметра данных содержит фиксированный массив, и при этом у параметра включена возможность использования списка значений, то в значение параметра помещается список значений, содержащий все значения, которые были в исходном фиксированном массиве значений.

В режиме совместимости с версией 8.3.11 поведение не изменилось.

При установке источника доступных настроек компоновщику настроек системы компоновки данных, если значение параметра данных содержит фиксированный массив, и при этом у параметра включена возможность использования списка значений, то в значение параметра помещался список значений, содержащий один элемент, со значением, равным значению по умолчанию для типа значения, указанного у параметра.Устранено некорректное поведение системы.
Управляемая форма.
Для элемента управляемой формы улучшен и унифицирован (для разных элементов формы) внешний вид подсказки в том случае, если свойство ОтображениеПодсказки установлено в значение Кнопка.Для элемента управляемой формы внешний вид подсказки в том случае, если свойство ОтображениеПодсказки установлено в значение Кнопка, мог различаться для разных элементов формыУнифицировано визуально оформление всплывающей подсказки для различных элементов формы.
Мобильная платформа.
Мобильный клиент.
Управляемая форма.
Работа с Интернет.
В мобильном приложении реализована доступность свойства Документ расширения поля управляемой формы для поля HTML-документа.

В мобильном приложении для параметра ДанныеСобытия обработчика события ПриНажатии расширения поля управляемой формы для поля HTML-документа реализована доступность свойств Document и Href.

Сообщения, формируемые платформой при обращении к несуществующим свойствам и методам, могут отличаться от аналогичных диагностических сообщений при работе на персональном компьютере.

Данные возможности не предоставлялись.

При работе на мобильном устройстве было невозможно получить доступ к HTML-документу, отображаемому формой.

Расширены возможности мобильной версии «1С:Предприятия» по работе с HTML-документом.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Microsoft SQL Server 2017.СУБД Microsoft SQL Server 2017 не поддерживалась.Реализована поддержка СУБД Microsoft SQL Server 2017.
В документации данное изменение описано здесь.
Средства разработки.
Для свойств кнопки управляемой формы ЦветТекста и ЦветФона, в палитре свойств и диалоге выбора цвета, будет отображаться тот цвет, который будет использоваться для соответствующего свойства. Данное поведение будет наблюдаться в том случае, если для указанных свойств выбрано значение Авто или какой-либо элемент системного стиля.Для свойств кнопки управляемой формы ЦветТекста и ЦветФона, в палитре свойств и диалоге выбора цвета, отображался тот цвет, который соответствовал системному элементу стиля. Данное поведение наблюдалось в том случае, если для указанных свойств было выбрано значение Авто или какой-либо элемент системного стиля.Палитра свойств более точно стала отображать значения свойств.
Локализация.
Реализована локализация интерфейса клиентского приложения для французского языка.Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» франкоговорящими пользователями.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
Расширен состав информации, отображаемой в диалоге О программе приложения мобильного клиента.В диалоге О программе приложения мобильного клиента, содержалось меньше информации.В приложении мобильного клиента, диалог О программе стал больше соответствовать этому диалогу в тонком клиенте.
Мобильная платформа.
Мобильный клиент.
Система взаимодействия.
Реализована возможность получения и обработки PUSH-оповещений, формируемых системой взаимодействия. При этом приложение для мобильного устройства должно быть собрано с включенным разрешением работы с PUSH-оповещениями. Оповещения формируются с помощью сервиса фирмы «1С» pushnotifications.1c.com. Регистрация в сервисе выполняется автоматически.Система взаимодействия не формировала PUSH-оповещения для использования на мобильных устройствах.Снижена вероятность пропустить сообщение от системы взаимодействия в тех случаях, когда приложение не запущено, находится в фоновом режиме или пользователь работает в другой информационной базе (в рамках одного приложения).
Работа с Интернет.
Реализована возможность использования внешних провайдеров для выполнения OpenID-аутентификации.

В документации описаны особенности использования внешнего провайдера.

Данная возможность не предоставлялась.Расширены возможности по обеспечению OpenID-аутентификации.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Мобильная платформа.
Мобильный клиент.
В мобильной версии «1С:Предприятия» реализована поддержка экрана iPhone X.Данная возможность не предоставлялась.Интерфейс мобильной версии «1С:Предприятия» адаптирован для работы на iPhone X.
Работа с Интернет.
Для механизмов работы с Интернет, предоставляемых платформой «1С:Предприятие», реализована поддержка криптографических алгоритмов по стандартам ГОСТ Р 34.10-2012, 34.11-2012.Данная возможность не предоставлялась.Стало возможно использовать ресурсы сети Интернет, если для работы с ними требуется возможность работы в соответствии с ГОСТ Р 34.10-2012 и 34.11-2012.
В документации данное изменение описано здесь и здесь.
Мобильная платформа.
Мобильный клиент.
Специальные возможности мобильного устройства.
При работе на платформе Windows Desktop не поддерживается сканирование штрих-кодов и использование фото- и видеосъемки.

Методы ПоддерживаетсяСканированиеШтрихКодов(), ПоддерживаетсяФотоснимок() и ПоддерживаетсяВидеозапись() объекта СредстваМультимедиа при работе под управлением ОС Windows Desktop возвращают значение Ложь.

При работе на платформе Windows Desktop, методы ПоддерживаетсяСканированиеШтрихКодов(), ПоддерживаетсяФотоснимок() и ПоддерживаетсяВидеозапись() объекта СредстваМультимедиа возвращали значение Истина.Поведение системы приведено к реальному.
Картинки.
В том случае, если картинка в библиотеке картинок платформы совпадает по имени с картинкой в конфигурации (в списке общих картинок), при обновлении конфигурации базы данных формируется предупреждение, но обновление будет продолжено. При этом при обращении к такой картинке по имени приоритет будет отдан картинке конфигурации.

В случае получения таких предупреждений рекомендуется максимально оперативно переименовывать картинки в конфигурации для предотвращения конфликта имен.

В том случае, если картинка в библиотеке картинок платформы совпадает по имени с картинкой в конфигурации (в списке общих картинок), обновление конфигурации базы данных было невозможно.Стало возможным обновить конфигурацию базы данных и продолжить работу в том случае, если в платформе добавлена картинка, имя которой совпало с картинкой конфигурации.
Мобильная платформа.
Мобильный клиент.
Средства администрирования.
Для мобильной версии «1С:Предприятия» реализована поддержка аутентификации ОС.

Для конструктора объекта HTTPСоединение реализована поддержка параметра ИспользоватьАутентификациюОС.

Данная возможность не предоставлялась.Мобильную версию «1С:Предприятия» стало возможно использовать в тех случаях, когда доступ к веб-серверу или информационной базе требует использование аутентификации ОС.
Отображение информации.
Мобильный клиент.
Для мобильной версии системы «1С:Предприятие» реализовано отображение информационных сообщений в виде специального вида окон, характерных для таких оповещений на мобильном устройстве. Такие сообщения формируются с помощью метода ПоказатьОповещениеПользователя() с параметром СтатусОповещенияПользователя, установленным в значение СтатусОповещенияПользователя.Информация.Сообщения, формируемые в мобильном клиенте с помощью метода ПоказатьОповещениеПользователя() с параметром СтатусОповещенияПользователя, установленным в значение СтатусОповещенияПользователя.Информация игнорировались и никак не отображались пользователю.При работе в мобильном клиенте стали полностью доступны возможности метода ПоказатьОповещениеПользователя() в части описания статуса сообщения.
Мобильная платформа.
Мобильный клиент.
Управляемая форма.
Изменен состав команд и способ отображения контекстного меню строки таблицы управляемой формы в мобильной версии «1С:Предприятия».Состав команд и способ отображения контекстного меню строки таблицы управляемой формы в мобильной версии «1С:Предприятия» были другими.Улучшен пользовательский интерфейс мобильной версии «1С:Предприятия».
Работа с Интернет.
Диагностика проверки отзыва корневого сертификата стала более подробной.

Реализована возможность управлять поведением системы для тех случаев, когда платформа не может однозначно проверить отзыв сертификата. Реализован параметр IgnoreServerCertificatesChainRevocationSoftFail файла conf.cfg.

Указанные изменения задействованы для всех механизмов работы с Интернет платформы «1С:Предприятие».

Диагностика результата проверки отзыва корневого сертификата всегда была одинаковой, вне зависимости от причины, по которой удаленный узел не проходил проверку.

Поведение системы в случае, когда невозможно однозначно проверить отзыв сертификата, не настраивалось.

Расширена диагностика при работе с Интернет. В некоторых случаях стало возможно более гибко настраивать поведение платформы при работе с Интернет.
В документации данное изменение описано здесь.
Мобильная платформа.
Для механизма тестирования и исправления мобильной платформы реализован режим проверки корректности файла базы данных.

Во время работы системы диагностируется ситуация поврежденного файла базы данных и предлагается несколько вариантов решения.

Данные возможности не предоставлялись.

Механизм тестирования и исправления не позволял проверить корректность файла базы данных.

При обнаружении поврежденного файла базы данных во время работы системы происходило аварийное завершение работы системы.

Улучшены возможности диагностики состояния файла базы данных.
Расширение конфигурации.
Отключена возможность удаления активного расширения в том случае, если расширение изменяет структуру базы данных. Для удаления такого расширения необходимо сделать его неактивным. При удалении неактивного расширения, изменяющего структуру базы данных, пользователю предлагается подтвердить это действие.

Реализован метод РасширениеКонфигурации.ИзменяетСтруктуруДанных(), позволяющий определить, что расширение конфигурации изменяет структуру базы данных.

При удалении расширения, изменяющего структуру базы данных, не предпринималось никаких дополнительных действий, позволяющих снизить вероятность потери данных, внесенных с помощью удаляемого расширения.Снижена вероятность потери данных, которые вводились с помощью расширения конфигурации.
В документации данное изменение описано здесь и здесь.
Мобильный клиент.
Сборщик мобильных приложений.
Для мобильного клиента реализована возможность указать веб-страницу, с помощью которой пользователь может самостоятельно выполнить регистрацию в информационной базе (или сервисе), которой он собирается пользоваться с помощью мобильного клиента. Эта страница может быть открыта как автоматически (если в мобильном клиенте отсутствуют зарегистрированные информационные базы) так и вручную.

Реализована возможность указать адреса веб-страниц, которые могут являться личными кабинетами в различных сервисах, информационные базы которых используются с помощью мобильного клиента. Может быть задано несколько таких страниц.

Для мобильного клиента реализована возможность получать с сервера списки общих информационных баз с помощью специальных веб-сервисов. Реализована возможность указания как конкретного адреса (или адресов) такого веб-сервиса, так и возможность указать любой адрес веб-сервиса.

При сборке приложения мобильного клиента реализованы следующие возможности:

  • Возможность указания начальной страницы, на которую будет выполнен переход в том случае, если в списке информационных баз мобильного клиента отсутствует хотя бы одна запись.
  • Возможность указания в списке баз ссылки на произвольную веб-страницу, которая будет отображаться встроенными возможностями мобильного клиента.
  • Возможность указания одного или нескольких веб-сервисов, возвращающих списки общих информационных баз.
  • Возможность разрешить ввод произвольного адреса веб-сервиса для получения списка общих информационных баз.

Для мобильного клиента реализована обработка гиперссылок со схемой e1c:// для тех веб-страниц, которые указаны в виде начальной страницы и в списке информационных баз.

Для мобильного клиента реализована команда командной строки запуска AddToStartCfg. Команда позволяет добавить информационную базу в список информационных баз мобильного клиента. Команда может быть размещена в веб-страницах, заданных при настройке собираемого мобильного приложения.

Не поддерживается OpenID-аутентификация для доступа к веб-серверам, возвращающим списки общих информационных баз.

Данные возможности не предоставлялись.Реализована возможность максимально простой и понятной регистрации информационных баз в мобильном клиенте и регистрации в сервисах, например, построенных по технологии 1cFresh..
Журнал регистрации.
Реализованы события журнала регистрации, фиксирующие следующие случаи:
  • Работа с пользователями:
    • Ошибка добавления пользователя (_$User$_.NewError);
    • Ошибка изменения пользователя (_$User$_.UpdateError);
    • Ошибка удаления пользователя (_$User$_.DeleteError).
  • Работа с информационной базой:
    • Сокращение журнала регистрации (_$InfoBase$_.EventLogReduce);
    • Ошибка сокращения журнала регистрации (_$InfoBase$_.EventLogReduceError);
    • Ошибка изменения параметров журнала регистрации (_$InfoBase$_.EventLogSettingsUpdateError);
    • Ошибка изменения параметров информационной базы (_$InfoBase$_.InfoBaseAdmParamsUpdateError);
    • Начало выгрузки информационной базы в файл (_$InfoBase$_.DumpStart);
    • Окончание выгрузки информационной базы в файл (_$InfoBase$_.DumpFinish);
    • Ошибка выгрузки информационной базы в файл (_$InfoBase$_.DumpError);
    • Начало загрузки информационной базы из файла (_$InfoBase$_.RestoreStart);
    • Окончание загрузки информационной базы из файла (_$InfoBase$_.RestoreFinish);
    • Ошибка загрузки информационной базы из файла (_$InfoBase$_.RestoreError);
    • Ошибка обновления конфигурации базы данных (_$InfoBase$_.DBConfigUpdateError);
    • Ошибка обновления конфигурации базы данных для расширения (_$InfoBase$_.DBConfigExtensionUpdateError).

Расширен состав данных, регистрируемых событиями _$Access$_.AccessDenied, _$InfoBase$_.EventLogSettingsUpdate.

Для просмотра новых событий, кроме событий работы с пользователями и событий _$InfoBase$_.DBConfigUpdateError и _$InfoBase$_.DBConfigExtensionUpdateError, требуется наличие права АдминистрированиеДанных.

Состав регистрируемых событий и объем регистрируемых данных был меньше.Улучшено журналирование различных ситуаций, которые могут происходить во время эксплуатации прикладного решения.
В документации данное изменение описано здесь.
Система компоновки данных.
Диаграммы.
В зависимости от установленного для конфигурации режима совместимости, в настройках системы компоновки данных не выполняется сохранение следующих параметров вывода, если для них не установлен флажок Использование:
  • Режим совместимости Версия 8.3.10 и ниже: ТипДиаграммы.ШкалаТочек, ТипДиаграммы.ШкалаЗначений, ТипДиаграммы.ШкалаСерий.
  • Режим совместимости Версия 8.3.11 и ниже: ТипДиаграммы.ОписаниеПалитрыЦветов, ТипДиаграммы.ОписаниеПалитрыЦветовИнформационныхИнтервалов, ТипДиаграммы.ИнформационныеЛинииЗначений, ТипДиаграммы.ИнформационныеИнтервалыЗначений, ТипДиаграммы.ИнформационныеЛинииТочек, ТипДиаграммы.ИнформационныеИнтервалыТочек.
В настройках системы компоновки данных сохранялись все измененные значения параметров вывода, что приводило к проблемам при открытии настроек системы компоновки данных в младшей версии системы «1С:Предприятие».Стало возможно использовать настройки диаграммы системы компоновки данных в том случае, если настройки открываются в младшей версии.
Веб-клиент.
Дополнение веб-браузера Mozilla Firefox, которое необходимо для функционирования расширений системы «1С:Предприятие» и внешних компонент, доступно в магазине дополнений https://addons.mozilla.org. Установленное дополнение будет автоматически обновляться с указанного сайта.Дополнение веб-браузера Mozilla Firefox, которое необходимо для функционирования расширений системы «1С:Предприятие» и внешних компонент, отсутствовало в магазине дополнений https://addons.mozilla.org. Обновление выполнялось в случае установки новой версии «1С:Предприятие», в которой входила новая версия дополнения.Обновление дополнения веб-браузера Mozilla Firefox стало выполняться прозрачно для пользователя.
Мобильный клиент.
Мобильная платформа.
Управляемая форма.
При работе в мобильной версии «1С:Предприятия» реализована возможность полноценно выполнять редактирование текста в полях ввода HTML-страницы, отображаемой в поле HTML-документа (для элементов, отмеченных атрибутом contentEditable). При редактировании поддерживаются возможности форматированного документа.При работе в мобильной версии «1С:Предприятия» было практически невозможно выполнять полноценное редактирование текста в полях ввода HTML-страницы, отображаемой в поле HTML-документа (для элементов, отмеченных атрибутом contentEditable).Расширены возможности использования HTML-документа в мобильной версии «1С:Предприятия».
Программное лицензирование.
Реализована возможность привязки программной лицензии к аппаратному ключу защиты.

Реализовано добавление в конец файла с активированной программной лицензией информации о лицензии в человекочитаемом виде. Такой файл активированной программной лицензии совместим с предыдущими версиями системы программ «1С:Предприятие».

Возможность привязки программной лицензии к аппаратному ключу защиты была невозможна.

Файл активированной программной лицензии не содержал в себе человекочитаемого описания активированной лицензии.

Расширены возможности системы программного лицензирования.
В документации данное изменение описано здесь, здесь и здесь.
Программное лицензирование.
Реализована КОРП-лицензия сервера «1С:Предприятие». Реализована техническая проверка наличия КОРП-лицензии в том случае, если используемая возможность требует КОРП-лицензии. Для КОРП-лицензий реализованы следующие возможности:
  • использование более 12 физических ядер процессора;
  • одновременная работа более 500 сеансов клиентских приложений (включая сеансы конфигуратора и внешнего соединения).

Реализованы КОРП-лицензии:

  • Программные: на 64-разрядный сервер, на 1, 5, 10, 20, 50, 100, 300, 500, 1000 пользователей.
  • Аппаратные: на 64-разрядный сервер, на 50, 100, 300, 500, 1000 пользователей.

Для утилиты лицензирования реализована возможность работы с лицензиями уровня КОРП.

Реализована команда ring license update, позволяющая обновить все лицензии, расположенные в хранилище.

Наличие КОРП-лицензии было юридическим, а не техническим требованием.Реализованы лицензии уровня КОРП.
В документации данное изменение описано здесь.
Работа с Интернет.
Внешние компоненты.
Работа с криптографией.
Работа с файлами.
В случае использования веб-браузера Microsoft Internet Explorer, установочные пакеты расширений работы с файлами и криптографией, а также внешних компонент, переведены в формат exe-файлов. Установочные пакеты в формате cab-файлов являются устаревшими, но продолжают поддерживаться платформой.

Доработана документация по технологии внешних компонент (см. здесь).

В случае использования веб-браузера Microsoft Internet Explorer, установочные пакеты расширений работы с файлами и криптографией, а также внешних компонент, использовали формат cab-файлов. Для обычного пользователя, работающего с веб-браузером Microsoft Internet Explorer, упрощен процесс установки расширений работы с файлами и криптографией и внешних компонент.
Системные требования.
Работа в ОС Linux.
Реализована поддержка следующих дистрибутивов ОС Linux:
  • Альт Линукс СПТ 7 ;
  • Альт Сервер 8;
  • Альт Рабочая станция К 8;
  • Альт Рабочая станция 8;
  • Альт Образование 8;
  • Альт СП 8.

Указанные дистрибутивы поддерживаются в 32- и 64-разрядном вариантах. Поддерживается работа как клиентских приложений так и кластера серверов «1С:Предприятия». +

Данные дистрибутивы не поддерживались.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Данные пользователя, которые используются создании объектов WS-ссылка и WSОпределение, используются для аутентификации только на том ресурсе, с которого загружается WSDL-определение. Если загружаемая схема включает схемы с других ресурсов - для обращения к этим ресурсам будет использоваться анонимный доступ.Данные пользователя, которые используются создании объектов WS-ссылка и WSОпределение, использовались для аутентификации на всех ресурсах, с которых было необходимо загрузить WSDL-определения.Если получение определения Web-сервиса требует авторизации, то для получения элементов получаемой схемы с других ресурсов, логин/пароль пользователя, используемые для получения схемы, не передаются на другие ресурсы.
Командный интерфейс.
В диалоге Все функции в тонком и толстом клиентских приложениях отменена возможность поиска путем набора начальных символов. Поиск выполняется с использованием диалога, вызываемого с помощью сочетания клавиш Ctrl+F и последующего перехода к следующему/предыдущему результату поиска с помощью кнопок F3/Ctrl+F3.В диалоге Все функции поиск выполнялся двумя способами:
  • С использованием диалога, вызываемого с помощью сочетания клавиш Ctrl+F (во всех клиентских приложениях).
  • Путем набора искомого текста непосредственно в списке объектов конфигурации (только в тонком и толстом клиентских приложениях). В веб-клиенте поиск с помощью непосредственного набора текста в списке не поддерживался.
Устранено незапланированное поведение системы.
Региональные установки.
Для Российской Федерации учитывается однократный сдвиг часовых зон на один час в связи с принятием закона № 368-ФЗ (Волгоградская область). Изменения касаются всех компонентов системы «1С:Предприятие», кроме веб-клиента. Веб-клиент пользуется информацией о временных зонах, которую предоставляет ОС и веб-браузер. +Изменения, внесенные законом № 368-ФЗ, не учитывались платформой.Учтены изменения законодательства об исчислении времени.
Сравнение/объединение конфигураций.
При сравнении двух конфигураций отображается изменение порядка следования команд, в том случае, если команды были размещены в стандартных группах команд.При сравнении двух конфигураций не отображалось изменение порядка следования команд, в том случае, если команды были размещены в стандартных группах команд. Как следствие, подобные изменения не переносились в конфигурацию, которая получалась в результате объединения.Устранено некорректное поведение системы.
Сборщик мобильных приложений.
Сборщик мобильных приложений игнорирует ситуацию, когда внешняя компонента, используемая собираемым мобильным приложением, отсутствует для какой-либо мобильной операционной системы, поддерживаемой собираемым мобильным приложением. В журнал сборки мобильного приложения записывается предупреждение для тех операционных систем, для которых внешняя компонента отсутствует.

При попытке использования отсутствующей внешней компоненты на мобильном устройстве будет сформировано исключение.

Сборщик мобильных приложений не позволял собрать мобильное приложение в том случае, если используемая в мобильном приложении внешняя компонента собрана не для всех операционных систем, для которых должно быть собрано мобильное приложение.Стало возможно собирать мобильные приложения в том случае, если внешняя компонента требуется не на всех используемых мобильным приложением операционных системах.
Мобильный клиент.
История данных.
При работе мобильного клиента версии 8.3.12 с сервером «1С:Предприятия» версии 8.3.13 и старше, в мобильном клиенте не отображается команда История изменений в контекстном меню динамического списка.При работе мобильного клиента версии 8.3.12 с сервером «1С:Предприятия» версии 8.3.13 и старше, в мобильном клиенте отображались две команды История изменений в контекстном меню динамического списка. При этом обе команды не работали.Устранено некорректное поведение системы.
Клиентское приложение.
Уменьшен объем оперативной памяти, занимаемой клиентским приложением при работе с картинками.При работе с картинками клиентское приложение использовало больше оперативной памяти.При работе с картинками в клиентском приложении снижены требования к оперативной памяти.
Кластер серверов.
Устранена периодическая деградация производительности нагруженного кластера серверов.Периодически наблюдалась деградация производительности нагруженного кластера серверов.Работа кластера серверов стала более стабильной.
Системные требования.
Работа в ОС Linux.
Изменена схема поддержки дистрибутивов ОС Linux. Обеспечивается поддержка строго тех дистрибутивов, которые указаны в системных требованиях на систему «1С:Предприятие». В общем случае обеспечивается поддержка одинакового списка дистрибутивов клиентским и серверным приложением «1С:Предприятия» (с возможными исключениями). В документации обновлен список поддерживаемых дистрибутивов ОС Linux.В документации был приведен неактуальный список поддерживаемых дистрибутивов ОС Linux.Актуализирован список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Мобильный клиент.
Если в приложение мобильного клиента, работающего под управлением ОС iOS, добавлено приложение с помощью начальной страницы, то проверка возможности работы с таким приложением осуществляется с использованием цифровой подписи всех конфигураций, которые добавлены в собранное мобильное приложение во время сборки.Если в приложение мобильного клиента, работающего под управлением ОС iOS, добавлено приложение с помощью начальной страницы, то работать в таком приложении было невозможно.В мобильный клиент, с помощью начальной страницы, стало возможно добавить приложение, построенное на основании конфигурации, уже присутствующей в приложении мобильного клиента.
Мобильный клиент.
В форме настроек избранного реализован поясняющий текст по работе с этой формой.

Если у формы мобильного клиента существует навигационная ссылка, то команды добавления в избранное и получения навигационной ссылки всегда присутствуют в командной панели формы, в меню Еще.

В диалоге получения навигационной ссылки мобильного клиента реализована команда добавления получаемой ссылки в избранное пользователя.

В форме настроек избранного отсутствовал поясняющий текст по работе с этой формой.

Если у формы мобильного клиента существует навигационная ссылка, то:

  • Команды добавления в избранное и получения навигационной ссылки добавлялись в меню Еще только при соблюдении следующих условий: у формы пустая командная панель, в командной панели формы есть не пустое меню Еще.
  • Команды добавления в избранное и получения навигационной ссылки были недоступны, если командная панель формы отсутствуют или в ней есть только одна, важная, команда.

В диалоге получения навигационной ссылки мобильного клиента отсутствовала команда добавления получаемой ссылки в избранное пользователя.

Улучшен пользовательский интерфейс мобильного клиента.
Мобильный клиент.
В мобильном клиенте, команда перестановки строк в таблице автоматически добавляется в контекстное меню таблицы, вместо команд перемещения строки вверх и вниз (даже если отключено автозаполнение командной панели).

Команда выбора нескольких строк в таблице (в мобильном клиенте) автоматически добавляется в контекстное меню таблицы и командную панель таблицы, если у таблицы установлен множественный выбор (даже если отключено автозаполнение командной панели).

В мобильном клиенте команда перестановки строк в таблице добавлялась в контекстное меню таблицы, только в случае автоматического заполнения контекстного меню или вручную.

Команда выбора нескольких строк в таблице (в мобильном клиенте) добавлялась в контекстное меню таблицы и командную панель таблицы, только в случае автоматического заполнения контекстного меню и командной панели таблицы, или вручную.

Улучшен пользовательский интерфейс мобильного клиента.

Оглавление

Переход с предыдущей версии на версию 8.3.12

Оглавление

Версия 8.3.11

Версия 8.3.11 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8311doc) документации к текущей версии.

В списке изменений версии 8.3.8 описано изменение по оптимизации работы списка истории работы пользователей.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.10. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.9. +Возможность запуска конфигураций, разработанных в версии 8.3.10 и более младших, в версии 8.3.11, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.11 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.11, при необходимости, использовать для работы с информационной базой и версию 8.3.10. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Сравнение/объединение конфигураций.
Реализована возможность объединения составных типов и составов планов обмена, подсистем и функциональных опций. Для указанных объектов реализована возможность просмотра различий: в интерактивном режиме (в диалоге) и в отчете о сравнении конфигураций.

Реализована возможность автоматического объединения составных типов и составов планов обмена, подсистем и функциональных опций с возможностью указания приоритетной конфигурации.

Изменен формат файла сохранения настроек сравнения и объединения конфигураций.

При объединении конфигураций отсутствовала возможность объединять составные типы, а так же состав планов обмена, подсистем и функциональных опций. Предоставлялась только возможность целиком заимствовать указанные объекты из загружаемой конфигурации или оставить без изменений существующие объекты.Упрощен процесс сравнения и объединения конфигураций.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
История данных.
Реализован механизм отслеживания истории изменения объектов базы данных. Реализовано свойство История данных для следующих объектов конфигурации: справочники, документы, бизнес-процессы, задачи, регистры сведений. Реализована настройка отслеживания истории изменений реквизитов указанных объектов (включая стандартные реквизиты и реквизиты табличных частей), общих реквизитов (если они не являются разделителями) и ресурсов регистров сведений. Реализованы возможности просматривать историю изменений, изменять ее, комментировать записи в истории, выполнять переход на выбранную версию данных.

Не поддерживается настройка истории данных для собственных объектов расширений конфигурации.

Реализованы права доступа ЧтениеИсторииДанных, ЧтениеИсторииДанныхОтсутствующихДанных, ИзменениеИсторииДанных, ИзменениеИсторииДанныхОтсутствующихДанных, ИзменениеНастроекИсторииДанных, ИзменениеКомментарияВерсииИсторииДанных, ПросмотрИсторииДанных, РедактированиеКомментарияВерсииИсторииДанных, ПереходНаВерсиюИсторииДанных.

Реализовано свойство глобального контекста ИсторияДанных, с помощью которого имеется возможность программного доступа к истории изменений.

Реализован пользовательский интерфейс для доступа к истории изменений.

Данная возможность не предоставлялась.

Историю изменений можно было реализовать с помощью встроенных средств системы «1С:Предприятие».

Реализована возможность использовать историю изменений на уровне платформы, за счет чего упрощается разработка и сопровождение прикладного решения.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Средства разработки.
В редакторе управляемой формы реализована возможность просмотра редактируемой формы в варианте мобильного приложения. Для просмотра управляемой формы в варианте мобильного приложения, режим совместимости редактируемой конфигурации должен быть больше или равен версии 8.3.7.В редакторе управляемой формы не предоставлялась возможность просмотра редактируемой формы в варианте мобильного приложения. Просмотр был доступен только в варианте персонального компьютера.Улучшены средства разработки форм при разработке конфигурации для работы на мобильных устройствах.
В документации данное изменение описано здесь, здесь и здесь.
Двоичные данные.
Реализован набор функций для работы с целыми числами на уровне битов. Числа интерпретируются как беззнаковые 32-разрядные числа.

Реализованы методы глобального контекста ПроверитьБит(), ПроверитьПоБитовойМаске(), УстановитьБит(), ПобитовоеИ(), ПобитовоеИли(), ПобитовоеНе(), ПобитовоеИНе(), ПобитовоеИсключительноеИли(), ПобитовыйСдвигВлево(), ПобитовыйСдвигВправо().

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Система «1С:Предприятие» предоставляла методы, позволяющие выполнять логические операции только с данными, расположенными в буфере двоичных данных.Упрощено использование побитовых логических операций с числовыми операндами.
В документации данное изменение описано здесь и здесь.
Обновление конфигурации базы данных.
Кластер серверов.
Реализован новый механизм реструктуризации информационной базы. Основные отличия этого механизма:
  • При выполнении реструктуризации обрабатываются только те физические таблицы базы данных, в которых есть реальные изменения.
  • Максимальное количество изменений выполняется без создания копии таблицы и копирования информации между копиями.
  • Если копирование информации между версиями таблиц все-таки требуется, это копирование будет выполняться средствами СУБД во всех возможных случаях.

Данная возможность включена в статусе бета-версии. Новый механизм реструктуризации используется только в клиент-серверном варианте, при работе с СУБД Microsoft SQL Server и PostgreSQL.

Для работы нового механизма реструктуризации требуется наличие Java 1.8 на компьютере, где установлен сервер «1С:Предприятия».

Для файла conf.cfg реализованы параметры JavaHome, JavaOpts, UpdateDBCfg.

Данная возможность не предоставлялась.При использовании нового механизма возможно существенное ускорение процесса реструктуризации информационной базы. Это, в свою очередь, позволяет уменьшить технологические простои при обновлении прикладного решения на производственных серверах.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Отображение информации.
Для форматной строки функции Формат() реализована возможность указывать форматную строку, которая включает в себя шаблон форматирования числа. Для этого реализован параметр ЧФ строки форматирования. Шаблон форматирования позволяет указать место, в которое будет выводиться число.

Поиск в динамическом списке учитывает параметры форматирования, которые указаны для колонок. При подсветке результатов поиска учитывается наличие константных строк как справа, так и слева от найденного числа.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Данные возможности не предоставлялись.Стало возможно выводить форматированные значения с указанием единицы измерения в диаграммах и других элементах интерфейса, поддерживающих указание строки форматирования.
Средства разработки.
Реализована возможность проверки использования синхронных вызовов при выполнении проверки конфигурации во время пакетного запуска конфигуратора.

Для команды /CheckConfig пакетного запуска конфигуратора реализован параметр -CheckUseSynchronousCalls. Параметр может использоваться только совместно с параметром -ExtendedModulesCheck этой же команды.

Отсутствовала возможность проверки использования синхронных вызовов при выполнении проверки конфигурации во время пакетного запуска конфигуратора. Данная возможность была доступна только при интерактивном запуске.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Расширение конфигурации.
Для Web-сервисов и HTTP-сервисов, являющихся собственными объектами расширения конфигурации, реализована поддержка повторного использования сеансов с возможностью настройки.Управление повторным использованием сесансов было недоступно для Web-сервисов и HTTP-сервисов, которые являются собственными объектами расширения.Унифицировано поведение системы при использовании одинаковых механизмов из расширения и обычной конфигурации.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Реализована возможность отправлять сообщения со стороны сервера «1С:Предприятия» на сторону клиентского приложения. Передача сообщений использует в качестве транспорта настроенную систему взаимодействия. Получение сообщений клиентским приложением может быть как синхронным, так и асинхронным - в зависимости от того, каким образом вызван сервер: обычным вызовом или с помощью фонового задания.

Для менеджера системы взаимодействия реализованы методы СоздатьПользователя(), УдалитьСообщение(), НачатьПодключениеОбработчикаНовыхСообщений(), НачатьОтключениеОбработчикаНовыхСообщений(), а также реализован новый вариант метода ПолучитьОбсуждение(). Для объекта ОбсуждениеСистемыВзаимодействия реализованы свойства Ключ, Отображаемое. Для объекта ОтборОбсужденийСистемыВзаимодействия реализованы свойства Отображаемое, Ключ. Объект СообщениеСистемыВзаимодействия и некоторые его свойства (Автор, Дата, Идентификатор, Получатели, Текст) стали доступны на стороне клиентского приложения. Для объекта СообщениеСистемыВзаимодействия реализованы свойства Данные, Обсуждение. Объекты ИдентификаторОбсужденияСистемыВзаимодействия и ИдентификаторСообщенияСистемыВзаимодействия стали доступен на стороне клиентского приложения. Объекты ИдентификаторПользователяСистемыВзаимодействия и КоллекцияИдентификаторовПользователейСистемыВзаимодействия, а также их свойства и методы, стали доступны на стороне клиентского приложения.

Данная возможность не предоставлялась.

Объект СообщениеСистемыВзаимодействия и некоторые его свойства (Автор, Дата, Идентификатор, Получатели, Текст) были доступны только на стороне сервера «1С:Предприятия». Объекты ИдентификаторОбсужденияСистемыВзаимодействия и ИдентификаторСообщенияСистемыВзаимодействия были доступны только на стороне сервера «1С:Предприятия». Объекты ИдентификаторПользователяСистемыВзаимодействия и КоллекцияИдентификаторовПользователейСистемыВзаимодействия, а также их свойства и методы, были доступны только на стороне сервера «1С:Предприятия».

Стало возможно информировать клиентское приложение о событиях на стороне сервера «1С:Предприятия».
В документации данное изменение описано здесь, здесь и здесь.
Система взаимодействия.
Реализована возможность подключать обработчик, который вызывается после отправки сообщения системы взаимодействия. Реализована возможность помещать в сообщение гиперссылки, при нажатии на которые будет выполняться заданный обработчик (или стандартное действие).

Для объекта МенеджерСистемыВзаимодействия реализованы методы ПодключитьОбработчикПослеОтправкиСообщения(), ОтключитьОбработчикПослеОтправкиСообщения(), ПодключитьОбработчикДействияСообщения(), ОтключитьОбработчикДействияСообщения(). Реализовано свойство СообщениеСистемыВзаимодействия.Действия.

Реализована доступность объектов ОбсуждениеСистемыВзаимодействия и КонтекстОбсужденияСистемыВзаимодействия на стороне клиентского приложения.

Данные возможности не предоставлялись.

Объекты ОбсуждениеСистемыВзаимодействия и КонтекстОбсужденияСистемыВзаимодействия были доступны только на стороне сервера «1С:Предприятия».

Расширены возможности системы взаимодействия. Стало возможно реализовать автоматические средства ответа на входящие сообщения.
В документации данное изменение описано здесь, здесь и здесь.
Работа с запросами.
Для объектов ПакетЗапросовСхемыЗапроса, ОператорыСхемыЗапроса, КолонкиСхемыЗапроса, ВыраженияИндексаСхемыЗапроса, ВыраженияПорядкаСхемыЗапроса, КонтрольныеТочкиИтоговСхемыЗапроса реализован метод Переместить(), который перемещает элемент коллекции в указанную позицию.Данная возможность не предоставлялась.Расширены средства работы с некоторыми коллекциями схемы запроса.
Расширение конфигурации.
Прикладные объекты.
Реализована возможность добавлять в расширение конфигурации собственные справочники, документы, планы обмена и регистры сведений.

Для заимствованных справочников и документов реализована возможность добавления реквизитов и табличных частей в расширении.

В состав собственного плана обмена могут входить только собственные объекты расширения. Собственный план обмена расширения не может участвовать в распределенной информационной базе. Для заимствованных планов обмена реализована возможность включать в состав плана обмена собственные объекты расширения. +

Список ограничений приведен в документации.

При удалении расширения, все данные, которые были внесены в собственные объекты расширения, будут удалены из информационной базы.

Данная возможность не предоставлялась.Расширение конфигурации стало предоставлять больше возможностей.

Стало возможно создавать расширения, которые хранят собственные данные в информационной базе, к которой их (расширения) подключают.

+

В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Регистры сведений.
Для объекта РегистрСведенийКлючЗаписи реализована возможность получения связанного объекта метаданных. Реализован метод РегистрСведенийКлючЗаписи.Метаданные().

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Получение связанного объекта метаданных непосредственно у объекта РегистрСведенийКлючЗаписи было недоступно. Получение метаданных приведено к общему подходу, принятому для других объектов конфигурации.
В документации данное изменение описано здесь.
Диаграммы.
При работе с биржевыми диаграммами реализована поддержка следующих свойств объекта ОсьЗначений: СпособОпределенияМинимальногоЗначения, МинимальноеЗначение, СпособОпределенияМаксимальногоЗначения, МаксимальноеЗначение.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При работе с биржевыми диаграммами следующие свойства объекта ОсьЗначений не влияли на отображение диаграммы: СпособОпределенияМинимальногоЗначения, МинимальноеЗначение, СпособОпределенияМаксимальногоЗначения, МаксимальноеЗначение.Улучшены возможности настройки отображения биржевой диаграммы.
В документации данное изменение описано здесь.
Стандартные функции.
Журнал регистрации.
При получении данных журнала регистрации, для событий Пользователи.Добавление и Пользователи.Изменение реализованы свойства АутентификацияOpenID и ЗащитаОтОпасныхДействий в структуре Данные записи о событии.

В инструментах просмотра журнале регистрации реализовано отображение свойств Аутентификация OpenID и Защита от опасных действий при просмотре событий Пользователи.Добавление и Пользователи.Изменение.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Для событий добавления и изменения пользователя было невозможно получить информацию о аутентификации OpenID и состоянии флага защиты от опасных действий. В тоже время указанные данные фиксировались в журнале регистрации.Устранено некорректное поведение системы. Стало возможно получать ранее недоступные данные.
Программное лицензирование.
В диалоге получения лицензии реализована возможность выбора страны из списка.В диалоге получения лицензии в качестве названия страны была возможность ввести любую последовательность символов.Устранены проблемы, которые возникали при ошибках во время ввода страны при активации программной лицензии.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Oracle Database версии 11.2.0.4 (Linux) при условии установки патча 20954292.

Работа с СУБД Oracle Database версии 11.2.0.4 для Windows возможна при условии установки патчей 24591646 и 24591637.

СУБД Oracle Database версии 11.2.0.4 для Linux не поддерживалась.

Требования для работы под ОС Windows не включали требования по установленным патчам.

Расширен список поддерживаемых версий СУБД Oracle Database.
В документации данное изменение описано здесь и здесь.
Технологический журнал.
Реализовано событие технологического журнала <WINCERT>. Событие предназначено для расследования событий, связанных с ошибками проверки действительности сертификатов средствами Windows API.

Событие формируется только при работе под управлением ОС Windows.

Данная возможность не предоставлялась.Упрощено расследование ситуаций, связанных с ошибками проверки действительности сертификатов при работе системы «1С:Предприятие» под управлением ОС Windows.
В документации данное изменение описано здесь и здесь.
Система взаимодействия.
Реализована возможность развертывания собственного сервера системы взаимодействия. Сервер поставляется в виде отдельного дистрибутива и требует отдельной установки. Документация по установке размещена на диске ИТС (см. здесь).

Данная возможность включена в статусе бета-версии.

Данная возможность не предоставлялась. Для работы системы взаимодействия можно было использовать только сервис 1cDialog.com.Реализована возможность развертывания собственного сервера системы взаимодействия.
Программное лицензирование.
Системные требования.
Если в ключевых параметрах компьютера произошло только одно изменение, то лицензия, активированная в «1С:Предприятии» версии 8.2.15 и старше, будет считаться валидной при проверке ее командой ring license с ключом validate.

Указание параметра --validate для ключа activate или prepare-request приводит к ошибке, если при попытке получения какого-либо из ключевых параметров возникла ошибка времени исполнения. Без указания параметра поведение не изменилось.

Для использования команды license требуется утилита ring версии 0.8.

Если в ключевых параметрах компьютера произошло только одно изменение, то лицензия, активированная в «1С:Предприятии» версии 8.2.15 и старше, считалась невалидной при проверке ее командой ring license с ключом validate.

Если при попытке получения какого-либо из ключевых параметров возникла ошибка времени исполнения, то лицензия активировалась успешно, поля лицензии, соответствующие неполученным параметрам, заполнялись пустыми значениями, что приводило к невозможности дальнейшего использования активированной лицензии.

Для использования команды license требовалась утилита ring версии 0.6.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 9.4.5 из состава ОС AstraLinux Special Edition 1.5.

Поддержка реализована начиная с версии 8.3.11.3034.

СУБД PostgreSQL версии 9.4.5 из состава ОС AstraLinux Special Edition 1.5 не поддерживалась.Расширен список поддерживаемых СУБД.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Управляемая форма.
Улучшено выделение диапазонов строк в таблице управляемой формы. Реализована возможность выделения блоков с помощью клавиш Ctrl, Shift и кнопок мыши.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Выделение диапазонов строк в таблице управляемой формы было возможно только путем выделения каждой конкретной строки с помощью клавиши Ctrl.Повышено удобство выделения строк в таблице управляемой формы.
Веб-клиент.
Реализована возможность работы с одним и тем же приложением из разных закладок одного веб-браузера.При попытке запуска в разных закладках веб-браузера одного и того же приложения диагностировалась ошибка и открытие второго экземпляра приложения прекращалось.Стало возможно запускать более одного сеанса работы с веб-клиентом из одного веб-браузера.
В документации данное изменение описано здесь.
Установка клиентского приложения.
В текстах сообщений, возникающих при обновлении клиентского приложения по протоколу HTTP, изменен термин, используемый для описания различных вариантов клиентского приложения. Для описания клиентского приложения везде используется термин «программа доступа».В текстах сообщений, возникающих при обновлении клиентского приложения по протоколу HTTP, в некоторых случаях использовался термин «программа просмотра», а в некоторых «программа доступа».Унифицирована терминология в разных сообщениях, касающихся одного механизма (обновление программы доступа по протоколу HTTP).
Управляемая форма.
Отображение информации.
При выводе таблицы управляемой формы с помощью команды Вывести список:
  • Пустые значения типа Число и Дата выводятся в точности так же, как и в самой форме;
  • Символы табуляции, используемые в качестве разделителя колонок при выводе содержимого таблицы в текстовый документ, вставляются между всеми колонками.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выводе таблицы управляемой формы с помощью команды Вывести список:
  • Пустые значения типа Число и Дата могли выводиться не так, как они отображались в самой форме;
  • Символы табуляции, используемые в качестве разделителя колонок при выводе содержимого таблицы в текстовый документ, начинали размещаться после первого непустого значения колонки.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Отображение информации.
При выводе выделенных строк (установлен флажок Только выделенные) таблицы управляемой формы с помощью команды Вывести список:
  • строки выводятся в том порядке, в котором они располагаются в таблице;
  • выводятся все строки, вне зависимости от уровня иерархии, если таблица отображает динамический список в режиме Иерархический список или Дерево.

Повышена эффективность работы команды Вывести список, если выводятся только выделенные строки (установлен флажок Только выделенные), таблица отображает динамический список, имелось большое количество выделенных строк и задан не эффективный запрос динамического списка.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выводе выделенных строк (установлен флажок Только выделенные) таблицы управляемой формы с помощью команды Вывести список:
  • строки выводились в порядке выделения;
  • выводились не все строки, если таблица отображает динамический список в режиме Иерархический список или Дерево.

Команда Вывести список работала недостаточно быстро в том случае, если выводились только выделенные строки (установлен флажок Только выделенные), таблица отображает динамический список, имелось большое количество выделенных строк и задан не эффективный запрос динамического списка.

Улучшен механизм вывода таблицы управляемой формы в табличный или текстовый документ.
В документации данное изменение описано здесь.
Система взаимодействия.
Модифицирован выбор адресата при создании сообщения в контекстном обсуждении системы взаимодействия. В том случае, если не требуется оповещать никого из пользователей, которые видят это сообщение (в соответствии с правами доступа к объекту, образующему контекст обсуждения), необходимо это явно указать выбором пункта Никого не оповещать.

Отправка сообщения с пустым списком адресатов невозможна.

Была возможна отправка сообщения контекстного обсуждения с пустым списком адресатов.Работа с оповещениями стала более понятной.
Табличный документ.
В меню Таблица главного меню приложения реализованы команды работы с рисунками, позволяющие управлять:
  • выравниванием рисунков (подменю Выравнивание);
  • размером рисунков (подменю Размер);
  • распределением нескольких рисунков в группе (подменю Распределить);
  • порядком следования рисунков (подменю Порядок).
Данные команды были недоступны в управляемом клиентском приложении.Обеспечена возможность интерактивной работы с рисунками в управляемом приложении.
Система взаимодействия.
При использовании видео-звонка в тонком и веб-клиентах, выполняется диагностика качества интернет-соединения и поверх изображения выводится диагностика в том случае, если качество интернет-соединения не является удовлетворительным.При неудовлетворительном качестве интернет-соединения при использовании видео-звонков никакой диагностики не выводилось. В некоторых случаях наблюдалось «замерзание» картинки без какой-либо диагностики.Реализована диагностика качества интернет-соединения при использовании видео-звонков системы взаимодействия.
Стандартные функции.
Если в прикладном решении отсутствуют объекты, для которых может использоваться управление итогами, то при попытке открыть диалог управления итогами в обычном режиме запуска (Главное меню - Операции - Управление итогами) формируется диагностическое сообщение и диалог не открывается.Если в прикладном решении отсутствуют объекты, для которых может использоваться управление итогами, то при попытке открыть диалог управления итогами в обычном режиме запуска (Главное меню - Операции - Управление итогами) диалог не открывался без формирования диагностического сообщения.Поведение системы стало более понятно.
Управляемая форма.
Порядок обхода в группах управляемой формы не зависит от значения свойства Объединенная в подчиненных группах: элементы обходятся в соответствии с настройками групп (вертикальная или горизонтальная).

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Порядок обхода в группах управляемой формы зависел от значения свойства Объединенная в подчиненных группах. Группа со значением свойства Объединенная равное Ложь, игнорировалась и не задавала порядок обхода. Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Клиентское приложение.
При работе в различных клиентских приложениях и различных режимах интерфейса, вызов справки с помощью кнопки F1 или главного меню приложения приведет к открытию одинаковой страницы справки.Страница справки, полученная при нажатии кнопки F1 или с помощью главного меню приложения, могла различаться в зависимости от способа вызова, клиентского приложения и режима интерфейса.Устранено некорректное поведение системы.
Система взаимодействия.
Если переход в поле ввода получателей контекстного обсуждения системы взаимодействия был выполнен принудительно (при попытке отправить сообщение без получателей), то после выбора получателя фокус ввода устанавливается в поле ввода сообщения.Если переход в поле ввода получателей контекстного обсуждения системы взаимодействия был выполнен принудительно (при попытке отправить сообщение без получателей), то после выбора получателя (кроме варианте Никого не оповещать) фокус ввода оставался в поле выбора получателей.Улучшен интерфейс отправки сообщений в контекстных обсуждениях системы взаимодействия.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
Работа с запросами.
При работе с СУБД PostgreSQL реализовано преобразование операции языка запросов ПОДОБНО `ТЕКСТ%` в более оптимальную операцию SQL-запроса.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При работе с СУБД PostgreSQL операция языка запросов ПОДОБНО `ТЕКСТ%` преобразовывалась в недостаточно оптимальную операцию SQL-запроса.Повышена скорость работы поиска по началу строки в языке запросов при работе с СУБД PostgreSQL.
Полнотекстовый поиск.
Оптимизирована проверка прав доступа на данные, полученные в результате полнотекстового поиска, в том случае, если в результате поиска получено более 100 записей.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Проверка прав доступа на данные, полученные в результате полнотекстового поиска, в том случае, если в результате поиска получено более 100 записей, выполнялась недостаточно эффективно.Уменьшено время получения результатов полнотекстового поиска для пользователей с ограниченными правами и большим объемом найденных записей (более 100).
Табличный документ.
Оптимизирована работа метода табличного документа ПроверитьВывод().Метод табличного документа ПроверитьВывод() работал недостаточно быстро.Ускорен вывод табличного документа, в котором требуется проверка того, что выводимая область помещается на страницу результирующего документа без разрыва.
Внешние отчеты и обработки.
Кластер серверов.
Клиентское приложение.
Ускорена загрузка внешних отчетов и обработок в клиентском приложении и на сервере «1С:Предприятия». При интенсивной работе с внешними отчетами и обработками исключено замедление работы пользователей.Загрузка внешних отчетов и обработок в клиентском приложении и на сервере «1С:Предприятия» выполнялась недостаточно быстро. При интенсивной работе с внешними отчетами и обработками наблюдалось замедление работы пользователей.Устранено замедление работы сервера «1С:Предприятия» в случае интенсивного использования внешних отчетов и обработок.
Работа с Интернет.
Улучшена производительность и масштабируемость при использовании на стороне сервера «1С:Предприятия» объектов HTTPСоединение и FTPСоединение в том случае, если используется несколько соединений из различных сеансов.Наблюдалось существенное снижение производительности при использовании на стороне сервера «1С:Предприятия» объектов HTTPСоединение и FTPСоединение в том случае, если использовалось несколько соединений из различных сеансов.Повышена производительность сервера «1С:Предприятия» при одновременном использовании нескольких HTTP- или FTP-соединений из различных сеансов.
Работа с СУБД.
Ускорена работа с временными таблицами, при использовании СУБД Microsoft SQL Server следующих версий:
  • 2012, версия 11.0.5548.0 и старше.
  • 2014, версия 12.0.2430.0 и старше.
  • 2016.
Производительность работы с временными таблицами, при использовании некоторых версий СУБД Microsoft SQL Server, была недостаточной.Ускорена работа с временными таблицами при использовании СУБД Microsoft SQL Server определенных версий.
Работа с криптографией.
Работа с Интернет.
При работе под управлением ОС Windows повышена производительность операций работы с криптографией и операций работы по протоколам SSL/TLS, при использовании указанных средств, одновременно в большом количестве сеансов.При работе под управлением ОС Windows наблюдалось снижение производительности операций работы с криптографией и операций работы по протоколам SSL/TLS, при использовании указанных средств, одновременно в большом количестве сеансов.Повышена производительность, при работе под управлением ОС Windows, операций работы с криптографией и по протоколам SSL/TLS одновременно в большом количестве сеансов.
Фоновые и регламентные задания.
Расширение конфигурации.
При работе в файловом варианте информационной базы, использующей расширения, ускорен запуск фоновых заданий.При работе в файловом варианте информационной базы, использующей расширения, запуск фоновых заданий занимал существенное время.Устранено некорректное поведение системы.
Средства разработки.
Ускорено выполнение следующих операций в конфигураторе:
  • открытие редактора текстов на встроенном языке;
  • расширенная проверка модуля на встроенном языке.
Следующие операций в конфигураторе выполнялись недостаточно быстро:
  • открытие редактора текстов на встроенном языке;
  • расширенная проверка модуля на встроенном языке.
Ускорено выполнение некоторых часто используемых операций при разработке прикладного решения.
Системные требования.
Уменьшен размер исполняемых файлов системы «1С:Предприятие».Исполняемые файлы системы «1С:Предприятие» требовали больше места на дисковом накопителе.Уменьшены требования системы «1С:Предприятие» к занимаемому месту на дисковом накопителе.
Средства разработки.
При работе с редактором текстов на встроенном языке ускорены следующие операции:
  • Открытие редактора текстов с модулем, который содержит большое количество строк.
  • Срабатывание контекстной подсказки.
  • Переход к определению метода и переменной.
  • Синтаксическая проверка модуля.
Редактор текстов на встроенном языке работал недостаточно быстро в том случае, если модуль имел большой объем.Работа разработчика стала более комфортной.
Работа с информационными базами.
Ускорена загрузка информационной базы из файла *.dt при работе с использованием СУБД IBM DB2.Загрузка информационной базы из файла *.dt при работе с использованием СУБД IBM DB2 занимала больше времени.Уменьшено время, которое потребуется при переносе информационной базы на СУБД IBM DB2.
В документации данное изменение описано здесь.
Управляемые блокировки.
Кластер серверов.
Повышена скорость работы сервера «1С:Предприятия» в том случае, когда одновременно проводятся документы, содержащие большое количество (десятки тысяч) строк.При одновременном проведении документов, содержащие большое количество (десятки тысяч) строк, были возможны «зависания» работы кластера серверов.Улучшена работа сервера «1С:Предприятия» в условиях высокой нагрузки.
Табличный документ.
Оптимизировано отображение табличного документа, содержащего большое количество картинок в скрытых строках.Отображение табличного документа, содержащего большое количество картинок в скрытых строках, занимало больше времени.Повышена скорость работы с табличным документом, содержащим большое количество картинок.
Работа с СУБД.
Оптимизирована работа с большими временными таблицами под управлением СУБД PostgreSQL.Работа с большими временными таблицами под управлением СУБД PostgreSQL была недостаточно оптимальна.При работе под управлением СУБД PostgreSQL ускорена работа системы при использовании больших временных таблиц.
Работа с СУБД.
Оптимизированы операции удаления записей из временных таблиц при выполнении некоторых операций в СУБД PostgreSQL и IBM DB2.Операции удаления записей из временных таблиц при выполнении некоторых операций в СУБД PostgreSQL и IBM DB2 работали недостаточно быстро.Ускорена работа системы при работе с временными таблицами.
Работа с информационными базами.
В файловом варианте информационной базы, содержащей большой объем метаданных, ускорено обновление информации о метаданных при выполнении реструктуризации информационной базы. Скорость реструктуризации таблиц с данными не изменилась.В файловом варианте информационной базы, содержащей большой объем метаданных, обновление информации о метаданных при выполнении реструктуризации информационной базы занимало больше времени.В случае изменения в структуре метаданных для конфигурации, содержащей много метаданных, уменьшено время, необходимое для выполнения реструктуризации в файловом варианте информационной базы.
Управляемая форма.
Ускорена вставка новых строк в реквизиты формы типа ДанныеФормыДерево. Ускорение особенно заметно в том случае, если дерево значений содержит большое количество строк.

Ускорение проявляется в тонком клиенте, толстом клиенте и на сервере «1С:Предприятие».

Вставка новых строк в реквизит формы типа ДанныеФормыДерево занимало больше времени в случае, если в дереве значений находилось большое количество строк.Ускорена работа с данными формы.
Динамический список.
Ускорено открытие форм, содержащих динамические списки.Открытие формы, содержащих динамические списки, занимало больше времени.Ускорено открытие форм, содержащих динамические списки.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
При работе системы «1С:Предприятие» с информационной базой, которая не зарегистрирована в списке информационных баз, для каждой такой базы создается каталог для хранения служебной информации этой базы. Каталог создается для каждой уникальной строки подключения к информационной базе в рамках одного пользователя операционной системы. Имя каталога является уникальным. Одновременно может существовать не более 20 таких каталогов.При работе системы «1С:Предприятие» с информационной базой, которая не зарегистрирована в списке информационных баз, для хранения служебной информации таких баз использовался предопределенный каталог с именем 00000000-0000-0000-0000-00000000000.Хранение служебных данных для информационных баз, доступ к которым выполняется без их регистрации в списке информационных баз, выполняется в специальных каталогах, что позволяет более гибко управлять дисковым пространством и не допускает разрастания одного каталога.
Средства разработки.
При редактировании имени пользовательской команды и при проверке логической целостности конфигурации выполняется проверка того, что имя пользовательской команды не совпадает с именем стандартной команды объекта метаданных, для которого создана пользовательская команда.Данная возможность не предоставлялась.

Можно было создать пользовательскую команду, имя которой совпадало с именем стандартной команды объекта конфигурации, для которого создавалась команда.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Расширены возможности по настройке отображения шкал диаграмм: отображение, цвет и расположение шкал диаграмм, угол отображения подписей шкал диаграмм, отображение и цвет линий сетки и т.д.

Для объекта ШкалаДиаграммы реализованы свойства: ОтображениеЛинийСетки, ЛинияСетки, ЦветЛинииСетки, ШрифтПодписей, ЦветПодписей, ОриентацияПодписей, МаксимальноеКоличествоРядовПодписей, УголНаклонаПодписей, ФорматПодписей, ПоложениеШкалы, ЛинияШкалы, ЦветЛинийШкалы, ШагШкалы, ПоложениеОтметокШкалы, ПоложениеПодписейШкалы.

Следующие свойства объекта ОбластьПостроенияДиаграммы являются устаревшими, не рекомендуются для использования и поддерживаются для совместимости:

  • ОтображатьПодписиШкалыСерии. Для доступа рекомендуется использовать ШкалаСерий.ПоложениеПодписейШкалы.
  • ОтображатьПодписиШкалыТочек. Для доступа рекомендуется использовать ШкалаТочек.ПоложениеПодписейШкалы.
  • ОтображатьПодписиШкалыЗначений. Для доступа рекомендуется использовать ШкалаЗначений.ПоложениеПодписейШкалы.
  • ОтображатьЛинииЗначенийШкалы. Для доступа рекомендуется использовать ШкалаЗначений.ОтображениеЛинийСетки.
  • ФорматШкалыЗначений. Для доступа рекомендуется использовать ШкалаЗначений.ФорматПодписей.
  • ОриентацияМеток. Для доступа рекомендуется использовать ШкалаТочек.ОриентацияПодписей.

В режиме совместимости с версией 8.3.10 следующие свойства скрываются из палитры свойств и не используются при построении диаграммы:

  • УголНаклонаПодписей,
  • ПоложениеШкалы,
  • МаксимальноеКоличестовРядовПодписей,
  • ПоложениеОтметокШкалы,
  • ПоложениеПодписейШкалы.
Данные возможности не предоставлялись.

Настройка отображения шкал диаграмм была более простой.

Расширены возможности по оформлению диаграмм.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Реализованы следующие возможности при использовании полнотекстового поиска:
  • При включенном привилегированном режиме не выполняется проверка прав доступа к обрабатываемым объектам.
  • Реализована возможность управлять получением представления объектов, которые возвращаются в результате полнотекстового поиска. Реализовано свойство СписокПолнотекстовогоПоиска.ПолучатьПредставление. Вне зависимости от значения данного свойства, всегда проверяются права доступа на поля объекта, участвующие в формировании представления.
  • Всегда проверяются права доступа на поля объекта, которые участвуют в формировании описания объекта. Эта проверка не зависит от значения свойства СписокПолнотекстовогоПоиска.ПолучатьОписание.

Для того, чтобы данные изменения стали использоваться, необходимо отключить режим совместимости и выполнить перестроение индекса полнотекстового поиска. Предыдущие версии системы «1С:Предприятие» не могут работать с индексом, который построен в версии 8.3.11 с отключенным режимом совместимости.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При использовании полнотекстового поиска:
  • При включенном привилегированном режиме выполнялась проверка прав доступа к обрабатываемым объектам.
  • Не выполнялась проверка права доступа на поля объекта, которые участвуют в формировании описания объекта, если свойство СписокПолнотекстовогоПоиска.ПолучатьОписание было установлено в значение Ложь.
Оптимизирована работа полнотекстового поиска.
В документации данное изменение описано здесь.
Система компоновки данных.
Табличный документ.
При работе системы компоновки данных, вложенные диаграммы и таблицы в результирующем табличном документе будут располагаться в группировках табличного документа. Генератор макетов системы компоновки данных создает пустые макеты с установленным свойством ВертикальныйУровень, расположенные после макетов диаграмм и таблиц, вложенных в группировки.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При работе системы компоновки данных, группировки в результирующем табличном документе системы компоновки данных не формировались вокруг диаграмм и вложенных таблиц, у которых отсутствуют группировки строк. Генератор макетов не создавал пустые макеты с установленным свойством ВертикальныйУровень, расположенные после макетов диаграмм. Для таблиц, вложенных в группировки, пустой макет создавался и для него свойство ВертикальныйУровень устанавливалось в значение 0.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Реализована возможность загрузки XSD-документа, который импортирует схемы, для получения которых необходимо обращение к внешнему серверу (по протоколу HTTP) с переадресацией.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Не поддерживалась загрузка XSD-документа, который импортирует схемы, для получения которых необходимо обращение к внешнему серверу (по протоколу HTTP) с переадресацией.Устранено некорректное поведение системы.
Средства разработки.
Клиентское приложение.
При нажатии кнопки Заменить в диалоге поиска и замены, доступного в редакторе текстов, реализовано следующее поведение:
  • если выделенный текст соответствует искомому тексту, выполняется замена и происходит поиск следующего вхождения;
  • в противном случае выполняется поиск вхождения и замена выполняется после повторного нажатия кнопки Заменить.
При нажатии кнопки Заменить в диалоге поиска и замены, доступного в редакторе текстов, выполнялся поиск следующего вхождения искомого текста и замена выполнялась после повторного нажатия кнопки Заменить.Устранено некорректное поведение системы. Поведение системы стало более ожидаемым.
Табличный документ.
Новое имя области табличного документа, которое отображается в диалоге установки нового имени области, формируется на языке, который соответствует текущему варианту встроенного языка конфигурации.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Новое имя области табличного документа, которое отображается в диалоге установки нового имени области, формировалось на языке, который соответствует текущему языку локализации клиентского приложения.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства разработки.
При создании файла обновления конфигурации больше не формируется сообщение о том, что для обновления конфигурации следует использовать платформу «1С:Предприятие» версии не ниже 8.3.9.2033.При создании файла обновления конфигурации формировалось сообщение о том, что для обновления конфигурации следует использовать платформу «1С:Предприятие» версии не ниже 8.3.9.2033.Отключен вывод неактуального сообщения.
Работа с XML, XDTO.
При импорте XSD-схемы в пакет XDTO, для ссылок на глобальные элементы и атрибуты, свойства default и fixed импортируются в свойства ЗначениеПоУмолчанию и Фиксированное соответственно, вне зависимости от вида объявления соответствующего элемента или атрибута.При импорте XSD-схемы в пакет XDTO, для ссылок на глобальные элементы и атрибуты, не выполнялся импорт свойств default и fixed, указанных локально.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
При использовании в динамическом списке полей ИмяПредопределенныхДанных и ВерсияДанных, для этих полей:
  • Доступны только виды сравнений Равно, Не равно, В списке, Не в списке, Заполнено и Не заполнено.
  • Не поддерживается поиск через строку поиска динамического списка.
  • Расширенный поиск возможен только по точному соответствию.
При использовании в динамическом списке полей ИмяПредопределенныхДанных и ВерсияДанных, для этих полей:
  • Были доступны все виды сравнения.
  • При поиске через строку поиска динамического списка генерировалась ошибка.
  • Расширенный поиск позволял указать любой вариант поиска, но при поиске по вхождению или началу строки генерировалась ошибка.
Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Встроенный язык.
Реализована возможность не создавать пустой обработчик оповещения в том случае, если результат выполнения асинхронного метода не важен, а обработчик ошибок выполнения асинхронного метода необходим.

Для конструктора объекта ОписаниеОповещения стало допустимо не указывать любые параметры.

При необходимости создать обработчик ошибок асинхронного метода, было необходимо также создать пустой обработчик результата выполнения асинхронного метода.Упрощена обработка ошибок при работе с асинхронными методами.
Работа с ZIP-архивами.
При доступе к имени файла (в том числе при записи такого файла на диск) с помощью свойств объекта ЭлементZipФайла, выполняется замена символов, недопустимых в именах файлов, символами «_». Запрещенными (при работе под управлением любой ОС) считаются все символы, которые недопустимо использовать в именах файлов при работе в ОС Windows. Замена выполняется при работе под управлением любой операционной системы. В режиме совместимости с версией 8.3.10 поведение не изменилось.

Для доступа к оригинальным именам файлов (до замены недопустимых символов) для объекта ЭлементZipФайла реализованы свойства ИсходноеПолноеИмя, ИсходноеИмя, ИсходныйПуть, ИсходноеРасширение, ИсходноеИмяБезРасширения.

При обнаружении в имени файла, помещенного в ZIP-архив, запрещенного символа, использовалось имя файла, которое содержало только те символы имени файла, которые были до первого запрещенного символа. Запрещенными считались все символы, которые недопустимо использовать в именах файлов при работе в ОС Windows. В результате могли возникать проблемы при извлечении из архива файлов, чьи имена недопустимы в ОС Windows.Для любого состава файлов ZIP-архива гарантируется, что он будет распакован на любой поддерживаемой операционной системе без ошибок. При этом возможно преобразование получившихся имен файлов.
В документации данное изменение описано здесь.
Отображение информации.
Табличный документ.
Табличный документ, который содержит картинки в формате SVG, отображается аналогично этому же табличному документу в тонком клиенте в следующих случаях:
  • При отображении в веб-клиенте.
  • При экспорте в формате HTML5.
Внешний вид табличного документа, содержащего картинки в формате SVG, мог отличаться от внешнего вида этого же табличного документа в тонком клиенте в следующих случаях:
  • При отображении в веб-клиенте.
  • При экспорте в формате HTML5.
Унифицировано отображение табличного документа в разных клиентских приложениях и форматах экспорта.
Работа с информационными базами.
Кластер серверов.
Повышена надежность работы платформы «1С:Предприятие» в клиент-серверном варианте работы при выполнении следующих операций:
  • реструктуризация конфигурации базы данных;
  • создание начального образа распределенной информационной базы;
  • загрузка информационной базы из файла .dt.
При выполнении платформой «1С:Предприятие» следующих операций в клиент-серверном варианте работы могли возникать проблемы:
  • реструктуризация конфигурации базы данных;
  • создание начального образа распределенной информационной базы;
  • загрузка информационной базы из файла .dt.
Повышена надежность при выполнении некоторых операций с информационной базой в клиент-серверном варианте работы.
Табличный документ.
Веб-клиент.
При экспорте табличного документа в формат PDF, в результирующий документ включается информация о размере и ориентации страниц документа (свойство PDF-документа PickTrayByPDFSize).

При необходимости использовать печать с нестандартным размером бумаги из веб-браузеров, рекомендуется использовать свойство ТочностьПечати табличного документа. При печати с помощью PDF-документа из веб-браузера Microsoft Internet Explorer нет необходимости использовать свойство ТочностьПечати.

При экспорте табличного документа в формат PDF, в результирующий документ не включалась информация о размере и ориентации страниц документа. Перед печатью было необходимо вручную проверить корректность установки размера и ориентации бумаги в используемой программе просмотра PDF-документов.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Общие объекты.
Свойства конфигурации.
Свойство НазначенияИспользования для всей конфигурации и управляемой формы имеет значение Неопределено при доступе из кода на встроенном языке. Свойство НазначенияИспользования для всей конфигурации и управляемой формы имело значение типа ФиксированныйМассив, где элементами массива выступали выбранные назначения.Устранено незапланированное поведение системы. Поведение унифицировано с другими свойствами, которые не влияют на работу системы в режиме «1С:Предприятие».
Веб-клиент.
В веб-клиенте ускорилось открытие системных диалогов и диалогов, показываемых методами ПоказатьВопрос(), ПоказатьПредупреждение().В веб-клиенте открытие системных диалогов и диалогов, показываемых методами ПоказатьВопрос(), ПоказатьПредупреждение(), занимало больше времени.Повышена надежность и скорость работы оконной подсистемы веб-клиента.
Табличный документ.
Рамки рисунков в табличном документе выводятся вплотную к рисунку, который эти рамки обрамляют.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выводе рисунков в табличный документ, между рамками рисунков и обрамляемым рисунком могло наблюдаться пустое пространство.Устранено некорректное поведение системы.
Полнотекстовый поиск.
При выполнении полнотекстового поиска по именам реквизитов реализована возможность использовать морфологию.

Для использования данной возможности рекомендуется выполнить перестроение индекса полнотекстового поиска.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выполнении полнотекстового поиска по именам реквизитов морфология не использовалась.Полнотекстовый поиск стал более дружествен к пользователям при поиске по именам реквизитам объектов.
Обмен данными.
Метод плана обмена ЭтотУзел() всегда возвращает ссылку на элемент плана обмена, у которого свойство ЭтотУзел установлено в значение Истина.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Метод плана обмена ЭтотУзел() не всегда возвращал ссылку на элемент плана обмена, у которого свойство ЭтотУзел было установлено в значение Истина.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
При работе языка запросов результат вычисления значения операции ВЫБОР будет корректным, если в операции используется другая операция ВЫБОР или функция ЕСТЬNULL(), и в них используется виртуальное и не виртуальное поле.При работе языка запросов результат вычисления значения операции ВЫБОР был некорректным, если в операции используется другая операция ВЫБОР или функция ЕСТЬNULL(), и в них используется виртуальное и не виртуальное поле. Также в этом случае было возможно аварийное завершение работы системы.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Устраняются различия отображения диаграмм в тонком и веб-клиентах:
  • размеры областей, указанные в реквизите формы, всегда используются при отображении диаграммы;
  • не различается поведение в разных клиентских приложениях;
  • размеры областей, которые используются для отображения диаграммы, совпадают с размерами областей, которые можно получить из встроенного языка.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Отображение диаграмм в тонком и веб-клиентах имели различия:
  • размеры областей, указанные в реквизите формы, не всегда использовались при отображении диаграммы;
  • различалось поведение в разных клиентских приложениях;
  • размеры областей, которые использовались для отображения диаграммы, не всегда совпадали с размерами областей, которые можно получить из встроенного языка.
Устранено некорректное поведение системы. Отображение диаграмм становится более предсказуемым.
Средства разработки.
При отладке прикладного решения реализована доступность свойств переменной (если они есть) в том случае, если для самой переменной недоступно получение представления.В том случае, если в отладчике было невозможно получить представление переменной, также были недоступны для просмотра и все свойства этой переменной (если таковые присутствовали).Устранено некорректное поведение системы.
Выгрузка/загрузка конфигурации в файлы.
Интерактивная выгрузка конфигурации в файлы всегда выполняется в иерархическом формате. Возможность выгрузки конфигурации в файлы в линейном формате поддерживается только в режиме пакетного запуска конфигуратора.

Рекомендуется пользоваться только иерархическим форматом выгрузки конфигурации в файлы.

При интерактивной выгрузке конфигурации в файлы имелась возможность выбора формата выгрузки: линейный или иерархический.В интерактивном режиме отключена возможность выгрузки конфигурации в файлов в линейном формате из-за наличия проблем при работе с таким форматом, например, проблемы при переносе файлов выгрузки между файловыми системами.
В документации данное изменение описано здесь и здесь.
Средства разработки.
При выполнении отладки по протоколу TCP устранено зависание отладчика при выполнении вычисления выражения и изменения значения переменной.При выполнении отладки по протоколу TCP могли наблюдаться случаи зависания отладчика при выполнении вычисления выражения и изменения значения переменной.Отладка приложений (при использовании протокола TCP) стала более предсказуемой и надежной.
Клиентское приложение.
Ярлык программы запуска системы «1С:Предприятие» в меню Пуск один и для 32- и для 64-разрядных версий.

После установки системы в меню Пуск отображаются все ярлыки установленной версии на всех поддерживаемых ОС семейства Windows.

При закреплении на панели задач запущенного приложения, фактически происходит закрепление ярлыка исполняемого файла 1cestart.exe. При этом запущенные приложения группируются на панели задач с этим ярлыком. +Список переходов доступен только в том случае, если на панели задач закреплен ярлык исполняемого файла 1cestart.exe.

В меню Пуск было два ярлыка программы запуска: для 32- и для 64-разрядных версий системы.

После установки системы в меню Пуск отображались не все ярлыки установленной версии при работе под управлением ОС Windows 8 и старше.

При закреплении на панели задач запущенного приложения, происходило закрепление именно этого приложения. При этом запущенные приложения группировались на панели задач с этим ярлыком. Список переходов был доступен для любого ярлыка.

Через меню Пуск стали доступны все компоненты системы. Поведение списка переходов стало более предсказуемым.
Система компоновки данных.
При разборе запроса системы компоновки данных, если в операции сравнения используется параметр с типом Строка (неограниченной длины), то данная операция не считается некорректной. Разбор вызывается при открытии конструктора схемы компоновки данных и при инициализации источника доступных настроек на основании схемы (в том числе, при открытии отчета).При разборе запроса системы компоновки данных, если в операции сравнения используется параметр с типом Строка (неограниченной длины), это приводило к формированию ошибки языка запросов о том, что в операции сравнения невозможно использовать строку неограниченной длины.Устранено незапланированное поведение системы.
Система взаимодействия.
Видеозвонки в системе взаимодействия осуществляются по технологии «точка-точка» (peer-to-peer), без использования центрального сервера. Центральный сервер используется для установки соединения и определения участников разговора.Видеозвонки в системе взаимодействия выполнялись с использованием сервера системы, без использования технологии «точка-точка» (peer-to-peer).Снижена нагрузка на центральный сервер системы взаимодействия. При условии расположения обоих абонентов в пределах локальной сети - трафик видеозвонков не выходит за пределы локальной сети.
В документации данное изменение описано здесь.
Система взаимодействия.
Если доступ к серверу сервиса взаимодействия осуществляется через прокси-сервер, то настройки прокси-сервера получаются из системных настроек операционной системы или из конфигурационного файла inetcfg.xml. NTLM-аутентификация на прокси-сервере не поддерживается.Работа с сервером сервиса взаимодействия не поддерживалась при использовании прокси-сервера.Упрощена настройка системы взаимодействия при использовании прокси-сервера.
В документации данное изменение описано здесь.
Динамический список.
При использовании русского варианта встроенного языка добавление или удаление стандартного псевдонима для стандартного реквизита более не приводит:
  • к разрыву связи между полем динамического списка и отображающим это поле элементом формы;
  • потере значения признака ИспользоватьВсегда поля динамического списка.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

+

+

При использовании русского варианта встроенного языка добавление или удаление стандартного псевдонима для стандартного реквизита приводило:
  • к разрыву связи между полем динамического списка и отображающим это поле элементом формы;
  • потере значения признака ИспользоватьВсегда поля динамического списка.
Уменьшено количество ошибок при редактировании запроса динамического списка с помощью конструктора запроса.
Регистры сведений.
При записи набора записей регистра сведений с помощью встроенного языка (РегистрСведенийНаборЗаписей.Записать()) значение Неопределено не игнорируется при установке управляемой блокировки.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При записи набора записей регистра сведений с помощью встроенного языка (РегистрСведенийНаборЗаписей.Записать()) значение Неопределено игнорировалось при установке управляемой блокировки и приводило к блокировке избыточного набора данных.Увеличена параллельность записи наборов данных регистров сведений при многопользовательской работе в том случае, если записываются измерения составного типа с возможностью указания «пустых» значений измерений.
Локализация.
Восстановлена поддержка интерфейса системы на казахском языке (код kk).Интерфейс системы на казахском языке не поддерживался.Стало возможно использование системы «1С:Предприятие» с казахским интерфейсом.
В документации данное изменение описано здесь и здесь.
Локализация.
Не поддерживается интерфейс системы на французском языке (код fr).Поддерживался интерфейс системы на французском языке (код fr).Не поддерживается интерфейс системы на французском языке.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
При работе под управлением ОС Linux, параметр рабочего процесса Занято памяти, вычисляется на основании значения VmRSS (resident set size). Значение параметра Занято памяти стало меньше в абсолютном выражении и более точно соответствует реальности.

Рекомендуется провести переоценку параметров перезапуска рабочих процессов в свойствах рабочего сервера.

При работе под управлением ОС Linux, параметр рабочего процесса Занято памяти, вычислялось на основании значения VmSize (virtual memory usage).При работе под управлением ОС Linux система мониторинга состояния кластера стала использовать параметр, более точно отражающий текущую ситуацию.
Локализация.
Реализована возможность ввода с клавиатуры символа валюты «российский рубль» (код ISO 4217 643, символ ₽).

+

+

Данная возможность не предоставлялась.Устранено некорректное поведение системы.
Кластер серверов.
В документацию включено описание сервиса кластера Сервис нумерации таблиц и полей базы данных. Сервис используется при обновлении конфигурации базы данных, если структура базы данных изменилась.В документации отсутствовало описание сервиса кластера серверов Сервис нумерации таблиц и полей базы данных.Актуализирована документация к системе «1С:Предприятие».
В документации данное изменение описано здесь.
Прикладные объекты.
При преобразовании чисел с плавающей точкой между форматом системы «1С:Предприятие» и внешними (по отношению к платформе) форматами устранены случаи потери точного представления числа.

Преобразования чисел в таких случаях стало работать одинаково при работе под управлением различных операционных систем.

При преобразовании чисел с плавающей точкой между форматом системы «1С:Предприятие» и внешними (по отношению к платформе) форматами могли наблюдаться случаи потери точности.

Преобразования чисел в таких случаях работало по разному при работе под управлением различных операционных систем.

Для чисел со значимыми цифрами после запятой (числа с плавающей точкой) уменьшено количество случаев, когда при конвертации таких чисел между форматом системы «1С:Предприятие» и внешним форматом (например файлы формата XLS) происходит потеря точности.
Работа в ОС Linux.
В ряде случаев повышена надежность системы «1С:Предприятие» при работе под управлением ОС Linux.В ряде случаев система «1С:Предприятие» при работе под управлением ОС Linux работала недостаточно надежно.Повышена стабильность работы системы «1С:Предприятие» при работе под управлением ОС Linux.
Технологический журнал.
В документации и обработке редактирования файла настройки технологического журнала (см. здесь)актуализирован состав и описание свойств события <ADMIN>.В документации и обработке редактирования файла настройки технологического журнала содержался неактуальный состав и описание свойств события <ADMIN>.Актуализирована документация и обработка редактирования файла настройки технологического журнала.
Обновление конфигурации базы данных.
Исключена ситуация, когда после нажатия кнопки Принять в диалоге Реорганизация информации, возникала ошибка Ссылка на таблицу ... недопустима, что приводило к невозможности выполнить обновление конфигурации базы данных.

Информация о проблеме отображается до нажатия на кнопку Принять.Проблема может быть устранена с помощью операции тестирования и исправления информационной базы.

После нажатия кнопки Принять в диалоге Реорганизация информации, могла возникнуть ошибка Ссылка на таблицу ... недопустима, что приводило к невозможности выполнить обновление конфигурации базы данных.Устранено некорректное поведение системы.
Динамический список.
При нажатии клавиши Enter (или двойном щелчке левой кнопкой мыши) в строке таблицы, связанной с динамическим списком, а также при вызове метода таблицы формы ИзменитьСтроку(), расширение таблицы формы будет выполнять открытие формы связанной с этой строкой, только в том случае, если если в составе команд есть команда Изменить.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При нажатии клавиши Enter (или двойном щелчке левой кнопкой мыши) в строке таблицы, связанной с динамическим списком, а также при вызове метода таблицы формы ИзменитьСтроку(), расширение таблицы формы выполняло открытие формы связанной с этой строкой в любом случае.Устранено некорректное поведение системы.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа с Интернет.
Веб-клиент.
Системные требования.
При работе веб-клиента прекращена поддержка веб-браузеров Microsoft Internet Explorer версий 8 и 9.Веб-браузеры Microsoft Internet Explorer версий 8 и 9 поддерживались веб-клиентом «1С:Предприятия».Прекращена поддержка устаревших версий веб-браузеров компании Microsoft.
В документации данное изменение описано здесь.
Встроенный язык.
Средства разработки.
При работе в тонком и веб-клиентах реализована диагностика при попытке присваивания значения необъявленной переменной с именем общего модуля, доступного на стороне клиентского приложения. Присваивание не срабатывает и генерируется сообщение об ошибке.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При работе в тонком и веб-клиентах попытке присваивания значения необъявленной переменной с именем общего модуля, доступного на стороне клиентского приложения, не срабатывала и не диагностировалась. При работе в веб-клиенте, в этом случае, наблюдалось аварийное завершение работы клиентского приложения.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
Метод Сдвинуть() для объектов ПакетЗапросовСхемыЗапроса, ОператорыСхемыЗапроса, КолонкиСхемыЗапроса, ВыраженияИндексаСхемыЗапроса, ВыраженияПорядкаСхемыЗапроса, КонтрольныеТочкиИтоговСхемыЗапроса перемещает указанный элемент коллекции на требуемое количество позиций.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Поведение метода Сдвинуть() отличалось от принятого и различалось в разных коллекциях:
  • ПакетЗапросовСхемыЗапроса, ОператорыСхемыЗапроса - метод перемещал элемент, индекс которого бы указан первым параметром метода в позицию, которая рассчитывалась как максимальное значение между первым и вторым параметром метода.
  • КолонкиСхемыЗапроса, ВыраженияИндексаСхемыЗапроса, ВыраженияПорядкаСхемыЗапроса, КонтрольныеТочкиИтоговСхемыЗапроса - метод перемещал элемент, индекс которого бы указан первым параметром метода в позицию, указанную вторым параметром метода.
Поведение метода Сдвинуть() приведено в соответствие с поведением аналогичного метода в других коллекциях.
В документации данное изменение описано здесь.
Управляемая форма.
Динамический список.
Права доступа.
Элементы, связанные с командами расширений таблицы или формы для динамического списка и недоступные текущему пользователю, удаляются с формы вне зависимости от того, добавлены они явно, прикладным разработчиком, или автоматически, расширением таблицы или формы.

Из контекстного меню таблицы управляемой формы удалены следующие команды: ВывестиСписок, НастройкаСписка, ЗагрузитьНастройкиДинамическогоСписка, СохранитьНастройкиДинамическогоСписка, СтандартныеНастройкиДинамическогоСписка, Список, ИерархическийСписок, Дерево. Подменю Создать на основании всегда добавляется последним пунктом меню, вне зависимости от наличия иерархии в отображаемом списке.

Для таблицы, отображающей динамический список с основной таблицей, критерием отбора или перечислением, добавляются команды управления расширенным поиском и настройками списка.

Во время создания формы выполняется удаление всех команд, связанных с таблицей, которая удаляется во время создания формы, например, по причине отсутствия у пользователя права Просмотр на основную таблицу динамического списка, с которым связана таблица формы.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Элементы, связанные с командами расширений таблицы или формы для динамического списка которые недоступны текущему пользователю, удалялись только в том случае, если они были добавлены автоматически, расширениями таблицы или формы, и не удалялись (и не работали), если они были добавлены явно, прикладным разработчиком.

Если таблица управляемой формы отображала динамический список без основной таблицы, то в контектное меню добавлялись команды: ВывестиСписок, НастройкаСписка, ЗагрузитьНастройкиДинамическогоСписка, СохранитьНастройкиДинамическогоСписка, СтандартныеНастройкиДинамическогоСписка. Если таблица управляемой формы отображала динамический список с основной таблицей, которая поддерживает иерархию, то в контектное меню добавлялись команды: Список, ИерархическийСписок, Дерево. Подменю Создать на основании добавлялось в разные места контекстного меню, в зависимости от отображаемой таблицы.

Для таблицы, отображающей динамический список с основной таблицей, критерием отбора или перечислением, не добавлялись команды управления расширенным поиском и настройками списка.

Во время создания формы выполнялось удаление большинства команд, связанных с таблицей, которая удаляется во время создания формы, например, по причине отсутствия у пользователя права Просмотр на основную таблицу динамического списка, с которым связана таблица формы. Однако, какая-либо одна команда оставалась (обычно это команда «Обновить»).

+

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность отключить отображение картинок папок в строках для иерархических динамических списков. Для этого следует очистить свойство ПутьКДаннымКартинкиСтрок таблицы, отображающей иерархический динамический список.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Отключить отображение картинок папок в строках для иерархических динамических списков было невозможно. Очистка свойства ПутьКДаннымКартинкиСтрок таблицы, отображающей иерархический динамический список, не приводило к отключению отображения картинок папок.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Установка клиентского приложения.
Отключено прерывание по таймауту загрузки дистрибутива клиентского приложения при обновлении по протоколу HTTP.

Прервать «зависшую» загрузку можно нажатием кнопки Отмена в диалоге, отображающем процесс скачивания дистрибутива.

Загрузка дистрибутива клиентского приложения при обновлении по протоколу HTTP прерывалась, если с момента начала загрузки проходило 600 секунд.Стало возможно загрузить дистрибутив клиентского приложения при работе по медленным каналам связи.
Общие объекты.
Пропущенные параметры РазделительСтрок и КонвертируемыйРазделительСтрок в конструкторе объекта ЧтениеТекста интерпретируются как Символы.ПС и Символы.ПС+Символы.ВК (соответственно).

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Пропущенные параметры РазделительСтрок и КонвертируемыйРазделительСтрок в конструкторе объекта ЧтениеТекста интерпретировались как пустая строка.Устранено некорректное поведение системы. Значения пропущенных параметров стали соответствовать описанным в Синтакс-помощнике.
В документации данное изменение описано здесь.
Работа с информационными базами.
Составной индекс, который включает в себя реквизиты, для которых свойство Индексировать установлено в значение Индексировать с доп.упорядочиванием, более не зависит от порядка следования таких реквизитов. Реквизиты включаются в индекс в фиксированном порядке.

При первой реструктуризации соответствующего объекта после отключения режима совместимости также выполняется и перестроение индекса.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Составной индекс, который включает в себя реквизиты, для которых свойство Индексировать установлено в значение Индексировать с доп.упорядочиванием, включал такие реквизиты в порядке следования. При смене порядка следования реквизитов - выполнялось перестроение индексов.Уменьшено влияние порядка следования реквизитов на структуру индексов базы данных.
Работа с запросами.
При выполнении запроса генерируется ошибка, если в тексте запроса используется агрегатная функция МАКСИМУМ() или МИНИМУМ(), в параметрах которых одновременно используются значения типа УникальныйИдентификатор или системное перечисление в сочетании друг с другом или значениями примитивных типов.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выполнении запроса не оценивалась как ошибка ситуация, когда в тексте запроса используется агрегатная функция МАКСИМУМ() или МИНИМУМ(), в параметрах которых одновременно используются значения типа УникальныйИдентификатор или системное перечисление в сочетании друг с другом или значениями примитивных типов. В таких случаях запрос мог возвращать некорректный результат или происходить аварийное завершение работы системы.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
При выполнении запроса, содержащего операцию ЕСТЬNULL или ВЫБОР, которая применяется к результатам работы функций МАКСИМУМ() или МИНИМУМ(), а параметрах которых используются значения типа УникальныйИдентификатор или системное перечисление и в другом операнде ЕСТЬNULL или ВЫБОР используется значение примитивного типа или другое системное перечисление, возвращается корректный результат.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выполнении запроса, содержащего операцию ЕСТЬNULL или ВЫБОР, которая применяется к результатам работы функций МАКСИМУМ() или МИНИМУМ(), а параметрах которых используются значения типа УникальныйИдентификатор или системное перечисление и в другом операнде ЕСТЬNULL или ВЫБОР используется значение примитивного типа или другое системное перечисление, возвращалось значение НЕОПРЕДЕЛЕНО .Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Изменяется цвет по умолчанию для шкал диаграмм и цвета серий в том случае, если используется палитра по умолчанию.

Реализовано значение системного перечисления ПалитраЦветовДиаграммы.МягкаяАдаптивная.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Цвет по умолчанию для шкал диаграмм и цвета серий в том случае, если используется палитра по умолчанию, был другим.Улучшен внешний вид диаграмм при настройках по умолчанию.
В документации данное изменение описано здесь.
Управляемая форма.
В стандартной обработке обработчика события менеджера объекта конфигурации ОбработкаПолученияДанныхВыбора реализована корректная обработка значения Неопределено для параметра обработчика Параметры.СтрокаПоиска. Считается, что если значение параметра Параметры.СтрокаПоиска равно Неопределено, то поведение системы аналогично быстрому выбору и возвращается список всех элементов, которые имеются в базе данных для данного объекта конфигурации.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

В стандартной обработке обработчика события менеджера объекта конфигурации ОбработкаПолученияДанныхВыбора считалось, что если параметр обработчика Параметры.СтрокаПоиска установлен в значение Неопределено, то это равноценно указанию в качестве строки поиска пустой строки.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Работа с запросами.
В коллекции Параметры объекта Запрос тип параметра, который используется в операции сравнения (>, >=, <, <=, =, <>) является типом другого параметра операции сравнения, но не включает квалификаторы типа другого параметра. Например, если параметр операции сравнения является строкой, то тип параметра, используемого в этой операции, будет позволять указать строку без ограничения длины.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

В коллекции Параметры объекта Запрос тип параметра, который использовался в операции сравнения (>, >=, <, <=, =, <>) являлся типом другого параметра операции сравнения, который включал квалификаторы типа другого параметра.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Система компоновки данных, при помещении в запрос условия с видом сравнения Не заполнено, размещает условие во вложенные запросы, находящиеся в правой части левого соединения только, если это условие не удается поместить во внешний запрос. В противном случае это условие в такой вложенный запрос не помещается.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Система компоновки данных при помещении условия отбора в запрос всегда старалась поместить условие во вложенный запрос. При этом, если вложенный запрос находился в правой части левого соединения, то условие также дублировалось во внешнем запросе.Системы компоновки данных формирует более ожидаемый результат, при использовании в запросе вложенного запроса, находящегося в правой части левого соединения.
В документации данное изменение описано здесь.
Работа с файлами.
При выполнении методов СоздатьКаталог()/НачатьСозданиеКаталога() генерируется исключение в том случае, если имя создаваемого каталога содержит недопустимые символы.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

При выполнении методов СоздатьКаталог()/НачатьСозданиеКаталога() имя создаваемого каталога не анализировалось. Если в имени каталога встречались недопустимые символы, то каталог не создавался и сообщений об ошибке не генерировалось.Реализована диагностика корректности имени создаваемого каталога.
В документации данное изменение описано здесь.
Управляемая форма.
Группа управляемой формы, для которой свойство ГоризонтальноеПоложениеВГруппе установлено в значение Центр, располагается по центру относительно родительской группы.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Группа управляемой формы, для которой свойство ГоризонтальноеПоложениеВГруппе установлено в значение Центр, прижималась к левой границе родительской группы.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Фон кнопки управляемой формы не будет отображаться (будет прозрачным), в том случае, если свойство ОтображениеФигуры установлено в значение Нет и свойство ЦветФона установлено в значение, отличное от Авто.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

Фон кнопки управляемой формы отображался указанным цветом (свойство ЦветФона), в том случае, если свойство ОтображениеФигуры установлено в значение Нет и свойство ЦветФона установлено в значение, отличное от Авто.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
Если публикация на веб-сервере выполняется с помощью утилиты webinst с параметром -descriptor, то заполненные атрибуты pubdst, pubdst32 и pubdst64 корневого элемента point переносятся из шаблона публикации в результирующий файл default.vrd.Если публикация на веб-сервере выполняется с помощью утилиты webinst с параметром -descriptor, то заполненные атрибуты pubdst, pubdst32 и pubdst64 корневого элемента point не переносились из шаблона публикации в результирующий файл default.vrd.Устранено некорректное поведение системы.
Работа с СУБД.
Уточнена документация по особенности использования системы «1С:Предприятие» при работе с СУБД Oracle Database. Поведение платформы не изменилось.

При работе с СУБД Oracle Database отсутствует возможность использования внутри оператора В вложенного запроса с модификатором ПЕРВЫЕ, если внутри вложенного запроса есть обращения к полям внешнего запроса. Это ограничение не относится к случаям, когда оператор В используется для проверки наличия строк, то есть в подзапросе есть ПЕРВЫЕ 1, а также выражения слева от В и в списке выборки являются константами и равны между собой.

При работе с СУБД Oracle Database отсутствовала возможность использования внутри оператора В вложенного запроса с модификатором ПЕРВЫЕ и разделом УПОРЯДОЧИТЬ ПО, если внутри вложенного запроса было обращения к полям внешнего запроса.Уточнена документация по особенности использования СУБД Oracle Database.
В документации данное изменение описано здесь.
Документация.
В описание метода ПараметрыСеанса.Очистить() в синтакс-помощнике внесена информация о том, что при вызове метода требуются права на изменение всех параметров сеанса, которые используются в данном методе (в пределе - всех параметров сеанса).В описании метода ПараметрыСеанса.Очистить() в синтакс-помощнике была отражена некорректная информация.Актуализирован синтакс-помощник.
Управляемая форма.
Доступ к реквизитам управляемой формы, созданным из встроенного языка, возможно только с использованием префикса ЭтотОбъект..

В режиме совместимости с версией 8.3.10 поведение не изменилось.

В некоторых случаях доступ к реквизитам управляемой формы, созданным из встроенного языка, был возможен без использования выражения ЭтотОбъект..Устранено некорректное поведение системы.
Средства администрирования.
На диске ИТС размещена версия интерфейса работы с сервером администрирования из языка Java, совместимая с системой «1С:Предприятие» версии 8.3.11 (см. здесь).На диске ИТС была доступна версия интерфейса работы с сервером администрирования из языка Java, совместимая с системой «1С:Предприятие» версии 8.3.10 и младше.Стало возможно выбрать для скачивания версию интерфейса работы с сервером администрирования из языка Java, которая совместима с применяемой пользователем версией системы «1С:Предприятие».
Системные требования.
Уточнены минимальные поддерживаемые версии для некоторых операционных систем семейства Windows:
  • Windows XP пакет обновления 3;
  • Windows Vista пакет обновления 2;
  • Windows 7 пакет обновления 1;
  • Windows Server 2008 пакет обновления 2;
  • Windows Server 2008R2 пакет обновления 1.

Для остальных ОС Windows поддерживаемые версии не изменились.

В том случае, если используемая операционная система не удовлетворяет указанным требованиям, формируется предупреждение с описанием проблемы и предложением выполнить установку необходимых обновлений.

Если установка выполняется без использования интерфейса пользователя на операционной системе без необходимого пакета обновления, то не выполняется регистрация консоли кластера и модуля COM-соединения.

В состав дистрибутива системы «1С:Предприятие» для ОС Windows включен распространяемый пакет Visual C++ для Visual Studio 2015.

Утилита 1CEClientMakeSetup при формировании дистрибутива для версии 8.3.11 и старше требует наличие распространяемого пакета во время формирования дистрибутива. +

Минимальные поддерживаемые версии для некоторых операционных систем семейства Windows были следующими:
  • Windows XP пакет обновления 3 (без проверки необходимости);
  • Windows Vista;
  • Windows 7;
  • Windows Server 2008;
  • Windows Server 2008R2.
Инсталлятор платформы устанавливает необходимые для новой версии распространяемые пакеты и сообщает пользователю о неподдерживаемых операционных системах.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Кластер серверов.
Средства администрирования.
Средства администрирования кластера серверов (из языка Java и сервер администрирования) могут использоваться для администрирования произвольной версии кластера серверов «1С:Предприятие», начиная с версии 8.3.9. При этом для использования доступны возможности, ограниченные используемой версией сервера администрирования (ras) и кластера серверов.

В документации уточнены характеристики совместимости кластера серверов, сервера администрирования и средств администрирования на языке Java.

Средства администрирования кластера серверов (из языка Java и сервер администрирования) могли использоваться для администрирования только совместимой версии кластера серверов «1С:Предприятие». Как правило, версии утилит администрирования были должны точно соответствовать используемой версии кластера серверов.Упрощено администрирование кластера серверов. Снижены накладные расходы на адаптацию административной инфраструктуры к изменившейся версии кластера серверов «1С:Предприятия».
В документации данное изменение описано здесь.
Система взаимодействия.
Не поддерживается программное создание контекстного и видимого обсуждения с заданным списком участников. Вызов метода ОбсуждениеСистемыВзаимодействия.Записать() в этом случае приведет к формированию исключения.Программное создание контекстного и видимого обсуждения с заданным списком участников было возможно.Устранено незапланированное поведение системы.
Работа с Интернет.
Ограничения профиля безопасности не влияет на работу с объектами ЗащищенноеСоединениеOpenSSL, СертификатыУдостоверяющихЦентровОС, СертификатыУдостоверяющихЦентровWindows, СертификатыУдостоверяющихЦентровLinux, СертификатКлиентаWindows.При использовании профиля безопасности работа с объектами ЗащищенноеСоединениеOpenSSL, СертификатыУдостоверяющихЦентровОС, СертификатыУдостоверяющихЦентровWindows, СертификатыУдостоверяющихЦентровLinux, СертификатКлиентаWindows была недоступна.Устранено незапланированное поведение системы.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Наименование параметра ключа командной строки CREATEINFOBASE, отвечающий за добавление создаваемой информационной базы в список информационных баз. Старое наименование поддерживается для совместимости.
  • AddInList.
  • AddToList.
В документации данное изменение описано здесь.
Наименование системного перечисления, описывающего ориентацию подписей к шкалам диаграммы. Старое наименование поддерживается для совместимости.
  • ОриентацияМетокДиаграммы.
  • ОриентацияПодписейДиаграммы.
Названия свойств объекта ОбластьПостроенияДиаграммы. Старые наименования поддерживаются для совместимости.
  • ОтображатьШкалу,
  • ЛинииШкалы,
  • ЦветШкалы.
  • ОтображатьШкалы,
  • ЛинииШкал,
  • ЦветШкал.
Изменены представления некоторых команд в стандартной функции управления расширениями конфигурации, а также текст сообщения о успешной проверке применимости расширения.Представление команды:
  • Проверить применимость;
  • Проверить применимость для всех;
  • Проверять применимость при добавлении и загрузке расширений.

Сообщение о успешной проверке:

  • Проверка применимости прошла успешно.

Представление команды:
  • Проверить возможность применения;
  • Проверить возможность применения для всех;
  • Проверять возможность применения при добавлении и загрузке расширений.

Сообщение о успешной проверке:

  • Проверка возможности применения прошла успешно.

Представление команд работы с закладками в конфигураторе.Команды меню Текст:
  • Установить/снять закладку;
  • Убрать все закладки.

Команда диалога Закладки (Главное меню - Правка - Список закладок):

  • Убрать все закладки.
Команды меню Текст:
  • Установить/удалить закладку;
  • Удалить все закладки.

Команда диалога Закладки (Главное меню - Правка - Список закладок):

  • Удалить все закладки.
Англоязычное наименование свойства параметра вывода системы компоновки данных ТипДиаграммы.ВлияниеРазмерНаПузырек.

В режиме совместимости с версией 8.3.10 используется старое наименование (во встроенном языке и при записи параметра в XML), если установлен английский вариант встроенного языка.

  • ChartType.ChartBubbleSizing.
  • ChartType.BubbleSizing.

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Специальные возможности мобильного устройства.
Для мобильного приложения, разрабатываемого для ОС iOS, реализованы разрешения:
  • Геопозиционирование в фоновом режиме - позволяет указать, что мобильное приложение должно получать информацию об изменении местоположения, даже если оно не активно.
  • Воспроизведение аудио в фоновом режиме - позволяет указать, что приложению требуется выполнять воспроизведение аудио даже если приложение не активно.
  • Обмен файлами с персональным компьютером - данное разрешение необходимо указать в том случае, если мобильное приложение будет использовать обмен файлами через iTunes.
Данные возможности не предоставлялись.Расширены возможности настройки параметров мобильного приложения, которое разрабатывается для эксплуатации под управлением ОС iOS.
Управляемая форма.
В мобильной платформе реализована возможность использовать объект для визуализации данных планирования (планировщик).

Особенности использования механизма приведены в документации.

Планировщик был доступен только в платформе для персонального компьютера.Расширены возможности предоставления информации на мобильных устройствах.
Специальные возможности мобильного устройства.
В мобильной платформе, работающей под управлением ОС Windows, реализована возможность использования локальных и push-уведомлений. Для работы используются Windows Notification Services. Специальный вспомогательный сервис для отправки уведомлений фирмы «1С» не поддерживает использование Windows Notification Services.

Реализовано значение системного перечисления ТипПодписчикаДоставляемыхУведомлений.WNS. Реализован метод МенеджерОтправкиДоставляемыхУведомлений.ПолучитьМаркерДоступа().

Ошибки отправки уведомлений возвращаются в качестве кода возврата метода МенеджерОтправкиДоставляемыхУведомлений.Отправить(). В режиме совместимости с версией 8.3.10 поведение не изменилось.

Реализовано системное перечисление ТипОшибкиОтправкиДоставляемогоУведомления. Реализован объект ИнформацияОПроблемеОтправкиДоставляемогоУведомления.

Для метода МенеджерОтправкиДоставляемыхУведомлений.Отправить() реализован параметр ИнформацияОПроблемахОтправкиДоставляемыхУведомлений.

При работе с геозонами реализована возможность получения локального уведомления в том случае, когда мобильное устройство пересекает границы установленных геозон.

Работа с уведомлениями (локальными и push-уведомлениями) была доступна только на мобильных устройствах, работающих под управлением ОС Android и iOS.

При возникновении ошибки при отправке уведомления генерировалось исключение.

При работе под управлением ОС Windows стало возможно пользоваться штатными возможностями оповещения пользователей на мобильных устройствах. Оповещение может формировать как мобильное приложение непосредственно на устройстве (локальные уведомления), так и прикладное решение, функционирующее на персональном компьютере (push-уведомление).
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Системные требования.
Прекращена поддержка ОС Android версий младше 4.0. Минимальный уровень используемого API равен API 14 (Android 4.0).Поддерживались ОС Android, начиная с API 9 (Android 2.3).Исключена поддержка устаревших версии операционной системы Android.
В документации данное изменение описано здесь.
Средства печати.
Табличный документ.
В мобильной платформе реализована поддержка пакетной печати.Данная возможность не предоставлялась.В мобильной платформе стали доступны возможности пакетной печати формируемых документов.
Работа с файлами.
В диалоге выбора файлов мобильной платформы стало возможно отбирать файлы с использованием нескольких масок. Поиск по маске в диалоге выбора файлов и с помощью метода НайтиФайлы() стал регистронезависимым. В диалоге выбора файлов и в методе НайтиФайлы() стало возможно использовать символы подстановки, характерные для ОС Android и iOS.Диалог выбора файлов не позволял отбирать файлы с использованием нескольких масок. Поиск по маске в диалоге выбора файлов и с помощью метода НайтиФайлы() был регистрозависимым. В диалоге выбора файлов и в методе НайтиФайлы() было невозможно использовать символы подстановки, характерные для ОС Android и iOS.Расширены средства работы с файлами в мобильной платформе. Эти средства унифицированы с возможностями платформы для персонального компьютера.
Форматированный документ.
В мобильной платформе реализована поддержка объекта ФорматированныйДокумент (вместе с отображением в управляемой форме).Данная возможность не предоставлялась.Расширены возможности мобильного приложения по работе с форматированным текстом.
Специальные возможности мобильного устройства.
В мобильной платформе, работающей под управлением ОС Windows (кроме Windows 8.1) реализована работа с картами. Реализована доступность методов ПоказатьНаКарте(), ПолучитьАдресПоМестоположению(), ПолучитьМестоположениеПоАдресу().

Реализован метод глобального контекста ПоддерживаетсяОтображениеКарты().

Работа с картами была недоступна при работе под управлением ОС Windows.Расширены возможности мобильной платформы при работе под управлением ОС Windows. Определение возможности работы с картами приведено в соответствие с общей схемой работы с возможностями, доступными не на всех мобильных устройствах или операционных системах.
В документации данное изменение описано здесь.
Мобильное приложение.
При загрузке в мобильное приложение конфигурации, выгруженной более старшей версией платформы для персонального компьютера, на экране мобильного устройства формируется предупреждение с возможностью отказаться от загрузки.При загрузке конфигурации на мобильном устройстве отсутствовала проверка того факта, что конфигурация выгружена на более старшей версии платформы для персонального компьютера.Реализована диагностика потенциальных проблем несовместимости мобильной платформы и загружаемой конфигурации, если версия платформы, в которой разрабатывалась конфигурация, старше, чем версия мобильной платформы.
Специальные возможности мобильного устройства.
При работе с SMS-сообщениями под управлением ОС Android реализованы следующие возможности:
  • Получить журнал SMS-сообщений и проверить возможность получения этого журнала. Реализованы методы ПоддерживаетсяЖурналSMS() и ПолучитьЖурналSMS() объекта СредстваТелефонии. Реализован объект ЖурналSMS.
  • Реализована возможность отбирать SMS-сообщения по заданным условиям.
  • Создать новое сообщение на основании существующего. Реализован конструктор SMS-сообщения на основании записи журнала SMS-сообщений.

При работе с методом ЖурналЗвонков.НайтиЗаписи() под управлением ОС Android элементы отбора (заданные без указания групп) складываются «по И». +

При работе с SMS-сообщениями под управлением ОС Android был недоступен доступ к журналу SMS-сообщений.

При работе с методом ЖурналЗвонков.НайтиЗаписи() под управлением ОС Android элементы отбора (заданные без указания групп) складывались «по ИЛИ». +

Расширены средства работы с SMS-сообщениями при работе под управлением ОС Android.

При выполнении поиска в журнале звонков поведение отбора приведено в соответствие с принятым в платформе для аналогичных случаев.

В документации данное изменение описано здесь.
Обновление конфигурации базы данных.
В собранном мобильном приложении, при обновлении конфигурации, больше не формируется предупреждение о том, что обновление удалит данные, которые больше не будут использоваться.

Мобильная платформа разработчика при обновлении конфигурации формирует предупреждение о том, что обновление изменяет структуру метаданных (только в том случае, если такое изменение действительно выполняется).

Разработчик должен самостоятельно позаботиться о том, чтобы при обновлении конфигурации не произошло потери данных.

Если обновление конфигурации содержало изменения структуры метаданных, то после обновления конфигурации выдавалось предупреждение о том, что обновление удалит неиспользуемые данные.

Предупреждение выдавалось как в собранном мобильном приложении, так и в мобильной платформе разработчика.

Процесс обновления конфигурации стал менее пугающим для пользователя. В частности, пользователя не предупреждают о том, что фактически может не произойти (удаление данных). В тоже время разработчику необходимо особо внимательно подходить к вопросу изменений конфигурации, которые приводят к потере пользовательских данных.
Специальные возможности мобильного устройства.
В качестве значений свойств ЗаписьЖурналаЗвонков.Дата, ДанныеСобытияКалендаря.Начало и ДанныеСобытияКалендаря.Конец используется универсальная дата.

В режиме совместимости с версией 8.3.10 поведение не изменилось.

В качестве значений свойств ЗаписьЖурналаЗвонков.Дата, ДанныеСобытияКалендаря.Начало и ДанныеСобытияКалендаря.Конец использовалась локальная дата.Представление даты и времени приведено в соответствие с общими правилами платформы.
Специальные возможности мобильного устройства.
В мобильной платформе отключена поддержка режима разделенного экрана (реализованного в ОС Android версии 7).В мобильной платформе формально присутствовала, но работала некорректно, поддержка режима разделенного экрана (реализованного в ОС Android версии 7).Устранено незапланированное поведение системы.
Специальные возможности мобильного устройства.
Мобильное приложение содержит набор строк, описывающих потребность в том или ином разрешении, которое требуется мобильному приложению. Данный текст будет отображаться в том случае, когда мобильному приложению потребуется соответствующее разрешение.

Разработчик не может изменять эти тексты.

В том случае, когда мобильному приложению было необходимо получить какое-либо разрешение, то выводился запрос с именем разрешения и возможностью выбрать ответ. Причина, по которой требовалось разрешение, не выводилась.При запросе разрешений мобильные приложения соответствуют требованиям владельцев магазинов приложений и предоставляют пользователям больше информации для принятия решения о предоставления разрешения.

Оглавление

Обновление используемых библиотек

Оглавление

Переход с предыдущей версии на версию 8.3.11

Оглавление

Версия 8.3.10

Версия 8.3.10 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v8310doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.9. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.8. +Возможность запуска конфигураций, разработанных в версии 8.3.9 и более младших, в версии 8.3.10, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.10 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.10, при необходимости, использовать для работы с информационной базой и версию 8.3.9. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
В диалоге публикации на веб-сервере параметры, описывающие OpenID-аутентификацию вынесены на отдельную закладку.

Также, в этом диалоге реализована возможность задания списка URL, допустимых для переадресации после выполнении OpenID-аутентификации.

Задать URL, допустимые для переадресации после OpenID-аутентификации можно было только ручным редактированием файла default.vrd.Интерактивная публикация позволяет задавать все параметры файла default.vrd.
В документации данное изменение описано здесь.
Установка клиентского приложения.
Доработана установка системы для украинского языка. При установке клиентских приложений на ОС Windows, программа установки работает на украинском языке, а украинский язык указывается основным для устанавливаемой платформы в том случае, если хотя бы по двум из нижеперечисленных параметров можно определить, что система устанавливается на компьютере для использования с украинским интерфейсом:
  • в качестве основного местоположения в настройках ОС указана Украина;
  • установлена украинская раскладка клавиатуры;
  • в качестве денежной единицы выбрана гривна;
  • в настройках ОС выбран украинский языковой стандарт;
  • в качестве основного языка ОС указан украинский.
При установке клиентских приложений на ОС Windows, программа установки работала на украинском языке, а украинский язык указывался основным для устанавливаемой платформы только в том случае, если основным языком операционной системы был выбран украинский язык. Принудительно выбрать украинский язык для программы установки можно было с помощью параметра командной строки /luk.Повышено удобство установки системы для украинского языка.
Встроенный язык.
Средства администрирования.
Реализована возможность сбора информации о циклических ссылках при выполнении кода на встроенном языке. Использование данной возможности может негативно сказаться на производительности прикладного решения. Рекомендуется использовать данную возможность только для целей тестирования.

Реализован метод глобального контекста ПроверитьЦиклическиеСсылкиВстроенногоЯзыка(). Для файла настройки технологического журнала (logcfg.xml) реализован элемент <SCRIPTCIRCREFS>. Реализовано событие технологического журнала <SCRIPTCIRCREFS>.

Реализован ключ командной строки запуска тонкого и толстого клиентских приложений /EnableCheckScriptCircularRefs. Реализован параметр командной строки запуска сервера «1С:Предприятие» -EnableCheckScriptCircularRefs.

В диалоге настройки параметров запуска клиентского приложения из конфигуратора реализован параметр Проверка циклических ссылок встроенного языка.

Реализован параметр EnableCheckScriptCircularRefs файла conf.cfg.

При работе системы «1С:Предприятие» с использованием ключа/параметра EnableCheckScriptCircularRefs, при обнаружении циклической ссылки будет формироваться невосстановимая ошибка, в тексте которой будет приведена информация об обнаруженной циклической ссылке.

Данная возможность не предоставлялась.Упрощена диагностика использования циклических ссылок при работе встроенного языка.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Расширение конфигурации.
В редакторе модулей, при работе с расширяемой конфигурацией, реализована возможность добавления в расширение конкретного метода.

Реализована возможность перехода к расширяемому методу из аннотации расширяющего метода в редакторе модулей (при работе с расширением).

Для команды Добавить в расширение реализовано сочетание клавиш Alt+Shift+F2. Сочетание клавиш Alt+F2 для этой команды больше не используется.

Отсутствовала удобная возможность добавления в расширение редактируемого метода.

Отсутствовала возможность перехода к расширяемому методу из аннотации расширяющего метода.

Для команды Добавить в расширение использовалось клавиатурное сокращение Alt+F2.

Повышен комфорт разработчика при создании расширений модулей на встроенном языке.
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность дополнительно обработать данные, которые получил динамический список для отображения. Реализовано событие ПриПолученииДанныхНаСервере.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Данные возможности не предоставлялись.Упрощен вывод в динамическом списке связанной информации, которую очень затруднительно, неэффективно или невозможно получить в запросе динамического списка.
В документации данное изменение описано здесь.
Управляемая форма.
Реализована возможность произвольного масштабирования управляемой формы в интерфейсе Такси. Интерактивное изменение масштаба недоступно в том случае, если для всего приложения установлен компактный режим отображения. Настройки размера форм сохраняются в разрезе значения DPI и масштаба формы. Реализовано свойство управляемой формы Масштаб, команда Изменить масштаб в меню Вид клиентского приложения и кнопка вызова диалога изменения масштаба в системной командной панели. В режиме совместимости с версией 8.3.6 поведение не изменилось.

Реализована поддержка набора картинок в клиентских приложениях для персонального компьютера (тонкий, толстый и веб-клиенты).

Системные картинки клиентских приложений перерисованы для различных вариантов масштаба.

Для набора картинок реализованы новые варианты разрешений: bldpi (масштаб 85%), aldpi (масштаб 125%), amdpi (масштаб 175%), udpi (масштаб 400%). В манифесте набора картинок реализована возможность указания, для какого интерфейса предназначена картинка. Для корректного расчета размера одиночной картинки из коллекции картинок, в манифесте набора картинок реализована возможность указания ширины и высоты одиночной картинки.

Для системного перечисления РазмерКартинки реализованы значения РеальныйРазмерБезУчетаМасштаба, АвтоРазмерБезУчетаМасштаба.

Данная возможность не предоставлялась.

Имелась возможность установить компактный режим отображения для конкретных форм или всего приложения в целом (с помощью встроенного языка).

Наборы картинок поддерживались только в мобильном приложении.

Пользователям стало проще подстраивать интерфейс под индивидуальные особенности.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Встроенный язык.
Реализована поддержка формирования текстовых строк, текст которых зависит от числа, указанного в строке, например, время выполнения 2 секунды и время выполнения 14 секунд. Реализована функция СтрокаСЧислом().

Поддержка реализована для следующих языков: английский, азербайджанский, белорусский, болгарский, венгерский, вьетнамский, казахский, киргизский, китайский, грузинский, латышский, литовский, немецкий, польский, румынский, русский, турецкий, туркменский, украинский, финский, французский, эстонский.

Данная возможность не предоставлялась.Упрощено формирование текстовых строк, содержимое которых зависит от значения числа, записанного в строке.
Табличный документ.
Реализована возможность получать размер области данных при импорте из внешних табличных форматов: XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument).

Для объекта ТабличныйДокумент реализованы методы ПолучитьРазмерОбластиДанныхПоГоризонтали() и ПолучитьРазмерОбластиДанныхПоВертикали().

Данная возможность не предоставлялась.Упрощен корректный импорт документов внешних табличных форматов с четко неопределенным размером области загружаемых данных.
Средства разработки.
Интерфейс OData.
Реализован серверный предмет отладки Стандартный интерфейс OData, позволяющий отлаживать код на встроенном языке, работающий во время выполнения запросов к стандартному интерфейсу OData.

Изменены правила сортировки предметов отладки при отображении в списках предметов отладки для протокола отладки HTTP. Изменен диалог автоматического подключения при использовании протокола отладки TCP.

Не поддерживалась отладка серверного кода на встроенном языке, работающего во время обращения к информационной базе через стандартный интерфейс OData.

Правила сортировки предметов отладки при отображении в списках предметов отладки для протокола отладки HTTP были другими. Диалог автоматического подключения при использовании протокола отладки TCP отображал предметы отладки в другом порядке.

Упрощена отладка при работе с использованием стандартного интерфейса OData.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
Реализована возможность управления высотой таблицы управляемой формы, которая отображает данные, отличные от динамического списка. В результате появилась возможность настроить таблицу таким образом, что ее высота будет автоматически соответствовать количеству отображаемых данных. Реализовано свойство таблицы управляемой формы ВариантУправленияВысотой.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Данная возможность не предоставлялась в платформе для персонального компьютера. Управление высотой таблицы формы было доступно только в мобильной платформе.

В платформе для персонального компьютера свойство таблицы управляемой формы ВариантУправленияВысотой игнорировалось.

Стало возможно разработать форму, в которой таблица будет отображать то количество строк, которое в ней находится (если эта таблица не отображает данные динамического списка), тем самым уменьшив количество полос прокрутки на форме и сделав саму форму более компактной.
В документации данное изменение описано здесь и здесь.
Система лицензирования.
Технологический журнал.
В технологическом журнале реализовано отражение событий, связанных с:
  • получением и освобождением лицензий (как программных, так и ключей HASP);
  • получением лицензий на базовые версии;
  • регулярным мониторингом соответствия реального оборудования и списка оборудования, зафиксированного в лицензии.

Реализовано событие технологического журнала <LIC>.

Событие технологического журнала <HASP> предоставляет возможность анализа только технологических аспектов работы с ключами HASP (вызовы интерфейса работы с HASP), не предоставляя возможности отслеживать получение и освобождение лицензий, получаемых с ключей HASP.

Технологический журнал предоставлял возможность анализировать только технические аспекты взаимодействия с ключами HASP (с помощью события <HASP>).Расследовать ситуации, связанные с поведением системы лицензирования, стало удобнее.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
В коллекцию ПоляНабораДанныхСхемыКомпоновкиДанных стало возможно включать значения типа ВложенныйНаборДанныхСхемыКомпоновкиДанных. Для методов Добавить() и Вставить() объекта ПоляНабораДанныхСхемыКомпоновкиДанных реализована возможность использовать значения типа ПоляНабораДанныхСхемыКомпоновкиДанных.В коллекцию ПоляНабораДанныхСхемыКомпоновкиДанных было нельзя добавлять значения типа ВложенныйНаборДанныхСхемыКомпоновкиДанных.Из встроенного языка стало возможно создавать схему компоновки данных с вложенными наборами данных.
Управляемая форма.
Реализована возможность управлять цветом фона интервала планировщика в зависимости от значений измерений, связанных с этим интервалом.

Реализовано свойство ИнтервалФонаПланировщика.ЗначенияИзмерений.

Не предоставлялась возможность управлять цветом фона интервала планировщика в зависимости от значений измерений, связанных с этим интервалом. Изменять цвет фона интервала планировщика было возможно только для диапазонов дат.Расширены возможности оформления планировщика.
Средства разработки.
Реализована возможность запуска конфигуратора в режиме агента - особого варианта пакетного режима, в котором конфигуратор выполняет функции SSH- или SFTP-сервера и принимает команды по этим протоколам.

При работе в режиме агента, конфигуратор в один момент времени может работать только с одной информационной базой. Если нужно одновременно работать с несколькими информационными базами - необходимо запускать несколько конфигураторов в режиме агента.

Реализованы параметры командной строки запуска пакетного режима /AgentMode, /AgentPort, /AgentListenAddress, /AgentSSHHostKey, /AgentSSHHostKeyAuto, /AgentBaseDir.

Изменено поведение параметра командной строки /Visible и /LoadConfigFromFiles в случае использования режима агента.

В качестве клиентского приложения для подключения к SSH- или SFTP-серверам, можно использовать любые приложения, умеющие выполнять такие функции и позволяющие обмениваться текстовыми командами с SSH- и SFTP-серверами (например, putty, winscp, MobaXTerm и т.д.).

Данная возможность включена в статусе бета-версии.

Данная возможность не предоставлялась.Расширены возможности автоматизации взаимодействия с конфигуратором. Ускорено взаимодействие с конфигуратором за счет того, что не тратится время на запуск экземпляра конфигуратора при каждом обращении к нему.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Форматированный документ.
Реализована возможность сохранения форматированного документа в формате PDF (интерактивно и с помощью метода ФорматированныйДокумент.Записать()) .

Реализовано значение ТипФайлаФорматированногоДокумента.PDF.

Данная возможность не предоставлялась.

Сохранение форматированного документа было возможно в форматах HTML и текст без форматирования.

Расширены возможности работы с форматированным документом.
Табличный документ.
Реализована возможность управлять отображением имен строк, колонок и ячеек табличного документа с помощью встроенного языка.

Для объекта ТабличныйДокумент реализованы свойства ОтображатьИменаСтрокИКолонок, ОтображатьИменаЯчеек.

В меню редактора табличного документа, в режиме «1С:Предприятие», реализованы команды, управляющие отображением именованных областей и назначением имен областей.

Возможность управлять отображением имен строк, колонок и ячеек табличного документа из встроенного языка была недоступна.Стало проще организовать редактирование табличного документа, в котором имеются именованные области.
Технологический журнал.
Реализовано журналирование событий, возникающих при первом соединении сервера «1С:Предприятия» с СУБД Microsoft SQL Server, в технологическом журнале. Журналирование выполняется с помощью события <DBMSSQLCONN>.Данная возможность не предоставлялась.Упрощено расследование ситуаций, связанных с потерей соединения сервера «1С:Предприятия» с СУБД Microsoft SQL Server.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Справка, открываемая в расширяемой конфигурации, включает в себя справочную информацию по объектам расширения.

Справочная информация расширения конфигурации используется при поиске по справке.

Данная возможность не предоставлялась.

Справочная информация, реализованная в расширении конфигурации, была недоступна в дереве справки и для поиска.

Устранено некорректное поведение системы.

Справка расширяемой конфигурации стала включать информацию из расширения, упрощая пользователю использование результирующей конфигурации.

Табличный документ.
При импорте табличного документа из файла формата XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) или ODS (OpenDocument), в результирующем табличном документе области, соответствующие листам оригинального документа, выделяются при помощи именованных областей строк табличного документа. Имена листов исходного документа преобразуются в имена областей для того, чтобы соответствовать правилам формирования идентификаторов встроенного языка системы «1С:Предприятие».

При импорте табличного документа из файла формата Microsoft Office OpenXML (Microsoft Excel 2007 и старше), лист, для которого отсутствует имя, будет успешно загружен и для области, описывающей такой лист, будет установлено автоматически сформированное имя. В режиме совместимости с версией 8.3.9 поведение не изменилось.

При импорте табличного документа из файла формата XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) или ODS (OpenDocument), в результирующем табличном документе области, соответствующие листам оригинального документа, никак не выделялись.

При импорте табличного документа из файла формата Microsoft Office OpenXML (Microsoft Excel 2007 и старше), лист, для которого отсутствует имя, не будет загружен.

Обработка табличного документа, который получен путем загрузки из многостраничного файла формата XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007 и старше) или ODS (OpenDocument), стала более простой. Стало проще выделять страницы загруженного документа.
В документации данное изменение описано здесь.
Расширение конфигурации.
Для расширения конфигурации реализована возможность указывать назначение расширения конфигурации: Исправление, Адаптация и Дополнение.

Расширения подключаются в следующем порядке:

  • все расширения с назначением Исправление;
  • все расширения с назначением Адаптация;
  • все расширения с назначением Дополнение.

Порядок загрузки нескольких расширений с одинаковым значением назначения расширения не определен.

Расширениям, ранее загруженным в информационную базу, назначение расширения автоматически устанавливается в значение Адаптация.

Реализовано свойство РасширениеКонфигурации.Назначение.

Данная возможность не предоставлялась.

Все расширения были равноправны с точки зрения порядка подключения расширений.

Стало возможно структурировать расширения по выполняемым функциям. Упрощено понимание, для чего разработано то или иное расширение.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Табличный документ.
Реализована возможность расширения табличного документа.

Реализована возможность объединять табличные документы при обновлении конфигурации с помощью соответствующего файла .cf или .cfu.

Возможность расширения табличного документа не предоставлялась.

Возможность объединения табличных документов в процессе обновления конфигурации не предоставлялась.

Расширение конфигурации стало предоставлять больше возможностей.

Расширены возможности работы с табличными документами при поддержке конфигурации.

В документации данное изменение описано здесь.
Картинки.
Реализована возможность получения конкретной картинки из коллекции картинок с вариантами, с учетом DPI, масштаба отображения и признака шаблонной картинки.

Для методов Преобразовать(), Записать(), ПолучитьДвоичныеДанные() и ФильтрИменФайлов() объекта Картинка реализованы параметры ВсеВарианты и ПодобратьВариант.

При попытке получения конкретной картинки из коллекции картинок с вариантами, поведение платформы было неопределено. Было возможно аварийное завершение работы системы.Устранено некорректное поведение системы.

Стало возможно получить конкретную картинку из коллекции картинок, которая максимально точно соответствует текущему режиму отображения.

Диаграммы.
Для полос измерительной диаграммы реализована возможность указывать границы интервала дробными значениями.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для полос измерительной диаграммы не поддерживалась возможность указывать границы интервала дробными значениями.Расширены возможности диаграмм.
В документации данное изменение описано здесь.
Диаграммы.
Система компоновки данных.
При отображении диаграмм (в том числе и в системе компоновки данных) реализованы возможности:
  • указывать линии тренда;
  • настраивать отображение серии на диаграмме;
  • настраивать отображение серии в легенде диаграммы.

Реализованы системные перечисления ТипАппроксимацииЛинииТрендаДиаграммы, ФакторЛинииТрендаДиаграммы, ИспользуемоеЗначениеТочкиБиржевойДиаграммы, ОтображениеВДиаграмме, ОтображениеВЛегендеДиаграммы. Для системного перечисления ПоложениеПодписейКДиаграмме реализованы значения: Авто, ВерхЛево, НизЛево, ВерхПраво, НизПраво, УказываетсяЛевоИВерх, СвободноеМесто. Для системного перечисления ТипМаркераДиаграммы реализованы значеня Чередование и Авто.

Реализованы объекты ОбластьПодписиДиаграммы, ЛинияТрендаДиаграммы.

Для объекта СерияДиаграммы реализованы свойства ЛинииТренда, ОтображатьГрафическоеПредставлениеДанныхВДиаграмме,

ОтображатьГрафическоеПредставлениеДанныхВЛегендеДиаграмме.

Для свойства СерияДиаграммы.Маркер значением по умолчанию является Авто. В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для объектов ОформлениеГруппировкиДиаграммыОбластиКомпоновкиДанных и ОформлениеКомпоновкиДанных реализованы параметры ЛинияТрендаДиаграммы,

ОтображатьГрафическоеПредставлениеДанныхВДиаграмме,

ОтображатьГрафическоеПредставлениеДанныхВЛегендеДиаграмме.

Данные возможности не предоставлялись.

Значение свойства СерияДиаграммы.Маркер выбиралось на основании номера серии как одно из значений Квадрат, Круг или Ромб.

Расширены оформительские и аналитические возможности диаграмм.
В документации данное изменение описано здесь, здесь и здесь.
Диаграммы.
Система компоновки данных.
Реализованы новые виды диаграмм: точечная и пузырьковая. Для объекта Диаграмма реализованы свойства ОбщаяСерияРазмераПузырька, ИсточникЗначенияРазмераПузырька, РазмерПузырькаПоУмолчанию, МинимальныйРазмерПузырька, МаксимальныйРазмерПузырька, ВлияниеРазмераНаПузырек, ОтображениеОтрицательныхЗначенийПузырьковойДиаграммы.

Реализованы следующие возможности по работе с диаграммами:

  • Управлять источником данных для оси точек. Для объекта Диаграмма реализованы свойства ИсточникЗначенийОсиТочек и СерияНаОсиТочек.
  • Управлять отображением осей диаграммы. Для объекта Диаграмма реализованы свойства ОсьЗначений и ОсьТочек.
  • Указывать дробные значения для минимального и максимального значений диаграммы. Управлять способом определения максимального и минимального значения диаграммы. В режиме совместимости с версией 8.3.9 поведение не изменилось.
  • Управлять возможностью соединять точки линиями (где это возможно). Реализовано свойство Диаграмма.СоединениеТочек.
  • Установить автоматический расчет прозрачности диаграммы. Для системного перечисления РежимПолупрозрачностиДиаграммы реализовано значение АвтоматическийРасчет.

Расширен набор значений, который может быть указан в подписях к диаграммам. Для системного перечисления ВидПодписейКДиаграмме реализованы значения ЗначениеРазмер, СерияРазмер, СерияЗначениеРазмер, СерияТочкаРазмер, СерияТочкаЗначениеРазмер, ТочкаРазмер, ТочкаЗначениеРазмер.

Для объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры ТипДиаграммы.ОсьЗначений, ТипДиаграммы.ОсьТочек, ТипДиаграммы.ИсточникЗначенийОсиТочек, ТипДиаграммы.СерияНаОсиТочек, ТипДиаграммы.ИсточникЗначенияРазмераПузырька, ТипДиаграммы.ОбщаяСерияРазмераПузырька, ТипДиаграммы.РазмерПузырькаПоУмолчанию, ТипДиаграммы.МинимальныйРазмерПузырька, ТипДиаграммы.МаксимальныйРазмерПузырька, ТипДиаграммы.ВлияниеРазмераНаПузырек, ТипДиаграммы.ОтображениеОтрицательныхЗначенийПузырьковойДиаграммы, ТипДиаграммы.СоединениеТочек. Для объекта системы компоновки данных ОформлениеГруппировкиДиаграммыОбластиКомпоновкиДанных реализованы свойства ВыводитьНаОсиТочекДиаграммы и ИспользоватьКакОбщуюСериюРазмераПузырькаВДиаграмме.

Свойства АвтоМаксимальноеЗначение и АвтоМИнимальноеЗначение являются устаревшими и поддерживаются для совместимости.

Данные возможности не предоставлялись.

Точечная и пузырьковая диаграмма были недоступны для использования.

Свойства объекта Диаграмма МинимальноеЗначение и МаксимальноеЗначение не могли принимать дробные значения. Для расчета минимального и максимального значения диаграммы использовались свойства АвтоМинимальноеЗначение и АвтоМаксимальноеЗначение.

Расширены возможности по использованию диаграмм.
В документации данное изменение описано здесь, здесь и здесь.
Диаграммы.
Система компоновки данных.
Реализована возможность настраивать подписи к шкалам диаграммы. Для объекта ОбластьПостроенияДиаграммы реализованы свойства ШкалаТочек, ШкалаЗначений, ШкалаСерий.

Для объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры ТипДиаграммы.ШкалаТочек, ТипДиаграммы.ШкалаЗначений, ТипДиаграммы.ШкалаСерий.

Данные возможности не предоставлялись.Расширены возможности оформления диаграмм.
В документации данное изменение описано здесь.
Диаграммы.
Система компоновки данных.
Реализована возможность настраивать порядок отображения точек в горизонтальных гистограммах. Для объекта Диаграммы реализовано свойство ПорядокОтображенияТочекГоризонтальнойГистограммы. В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры ТипДиаграммы.ПорядокОтображенияТочекГоризонтальнойГистограммы.

Данные возможности не предоставлялись.

Точки в горизонтальной диаграмме всегда отображались снизу вверх (первая точка располагалась в самом низу).

Расширены возможности оформления диаграмм.
Система компоновки данных.
Диаграммы.
При выводе диаграммы в системе компоновки данных реализована возможность настройки линий шкал, цвета шкал, маркеров серий, индикаторов серий и типов линий серий.

Для объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры ТипДиаграммы.ЛинииШкал, ТипДиаграммы.ЦветШкал.

Для объектов системы компоновки данных ОформлениеГруппировкиДиаграммыОбластиКомпоновкиДанных и ОформлениеКомпоновкиДанных реализованы свойства ЛинияВДиаграмме, МаркерВДиаграмме, ИндикаторВДиаграмме.

Данные возможности не предоставлялись.Расширены возможности оформления диаграмм средствами системы компоновки данных.
Система взаимодействия.
Реализован механизм «система взаимодействия». С помощью этого механизма предоставляется возможность, в рамках одной информационной базы, взаимодействовать между собой клиентским приложениям, серверу и пользователям этой информационной базы. Система взаимодействия призвана упростить автоматизацию бизнес-процессов предприятия и предоставляет пользователям информационной базы простой способ коммуникации в рамках выполнения должностных обязанностей. Пользователи прикладного решения, построенного на платформе «1С:Предприятие», могут общаться между собой как с помощью обмена текстовыми сообщениями, так и с помощью звонков. Звонки могут быть как обычными - только голосовая информация, так и видео - голосовая и видео-информация. Реализована возможность создавать как текстовые обсуждения, которые привязаны к конкретным объектам информационной базы (контекстные обсуждения), так и не привязанные к таким объектам (неконтекстные обсуждения). Доступ к контекстному обсуждению регламентируется правами доступа системы «1С:Предприятие» к соответствующему объекту.

Реализована стандартная функция Управление системой взаимодействия.

Реализована возможность получения оповещений о поступлении новых сообщений.

Доступна работа с обсуждениями с помощью встроенного языка. Реализовано свойство глобального контекста СистемаВзаимодействия. Для объекта УправляемаяФорма реализовано свойство ОтображениеОбсуждений. В режиме совместимости с версией 8.3.9 доступ к данному свойству не поддерживается. Реализовано право доступа для конфигурации РегистрацияИнформационнойБазыСистемыВзаимодействия.

При работе в веб-клиенте, использование системы взаимодействия поддерживается в следующих веб-браузерах: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge, Microsoft Internet Explorer версии старше 10.0.

Все сообщения хранятся на сервере системы взаимодействия. Работа осуществляется с использованием сервера системы взаимодействия, в котором требуется зарегистрировать информационную базу перед началом использования механизма. Функциональность сервера реализуется на начальном этапе в виде сервиса 1cDialog.com, развернутого на мощностях фирмы «1С». Для обеспечения функционирования системы взаимодействия необходимо обеспечить доступ к URL wss://1cdialog.com через Интернет.

В дальнейшем планируется поставка дистрибутива сервера системы взаимодействия, с помощью которого можно развернуть сервер на вычислительных мощностях конкретного предприятия.

Таким образом, будет предоставлено две возможности работы: с помощью сервиса 1cDialog.com или с помощью сервера, развернутого на предприятии.

Использование звонков на этапе бета-тестирования ограничено. Информация по использованию звонков будет доводиться отдельно.

Использование системы взаимодействия включено в статусе бета-версии. Условия доступа к сервису будут публиковаться отдельно. В текст письма с кодом регистрации, который высылает сервис 1cDialog.com при попытке подключения информационной базы к сервису, включена информация по порядку подключения видеозвонков.

Данная возможность не предоставлялась.Создан механизм, поддерживающий общение пользователей, тесно интегрированный в интерфейс и бизнес-логику прикладного решения на платформе «1С:Предприятие».
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Выгрузка/загрузка конфигурации в файлы.
Реализована возможность частичной выгрузки редактируемой конфигурации в файлы XML. Под частичной выгрузкой понимается выгрузка только тех объектов, которые были изменены с момента последней выгрузки. При этом формируется файл с информацией о каждом выгружаемом объекте конфигурации (файл ConfigDumpInfo.xml). В данном файле (среди прочей информации) хранится внутренняя версия каждого выгруженного объекта. Повторная выгрузка объекта будет осуществляться в тех случаях, когда версия объекта в конфигураторе станет отличаться от версии объекта в файле ConfigDumpInfo.xml.

Также во время выгрузки может быть сформирован файл, содержащий информацию о тех изменениях, которые произошли в завершившейся выгрузке.

При загрузке конфигурации из файлов XML имеется возможность указать необходимость обновления файла с информацией о выгружаемых объектах конфигурации. В этом случае в файл вносится информация, соответствующая состоянию конфигурации после завершения загрузки.

Для параметра /DumpConfigToFiles командной строки пакетного запуска конфигуратора реализованы ключи update, force, getChanges, configDumpInfoForChanges, listFile.

Для параметра /LoadConfigFromFiles командной строки пакетного запуска конфигуратора реализован ключ updateConfigDumpInfo.

Частичная выгрузка конфигурации в файлы XML не поддерживалась. Конфигурация всегда выгружалась полностью.Ускорен процесс выгрузки конфигурации в файлы XML, особенно в случае небольших изменений в очень больших конфигурациях.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Динамический список.
Реализована возможность управлять доступностью полей динамического списка (включая подчиненные) для использования в группировке, отборе и настройке порядка. Реализованы методы УстановитьОграниченияИспользованияВГруппировке(), УстановитьОграниченияИспользованияВПорядке(), УстановитьОграниченияИспользованияВОтборе(), ПолучитьОграниченияИспользованияВГруппировке(), ПолучитьОграниченияИспользованияВПорядке(), ПолучитьОграниченияИспользованияВОтборе().

+

Данные возможности не предоставлялись.Разработчик получил возможность явным образом запрещать группировку, упорядочивание и отбор для тех полей, которые не предназначены для такой операции.
В документации данное изменение описано здесь.
Оконная система.
Выгрузка/загрузка конфигурации в файлы.
Реализована возможность управлять отображением заголовка управляемой формы. Реализовано свойство УправляемаяФорма.ОтображатьЗаголовок.

Реализована возможность управлять отображением кнопки закрытия окна формы. Реализовано свойство УправляемаяФорма.ОтображатьКнопкуЗакрытия.

Реализована возможность указывать режим отображения основного окна приложения:

  • Обычный - текущий режим отображения основного окна приложения.
  • Рабочее место - скрывается большинство элементов системной командной панели, скрываются все панели основного окна приложения, скрываются навигационные кнопки начальной страницы (включая саму надпись), отключаются некоторые клавиатурные сокращения.
  • Полноэкранное рабочее место - в дополнение к режиму отображения рабочего места, окно приложения открывается на весь экран.
  • Киоск - в дополнение к полноэкранному рабочему месту из системной командной панели исключается кнопка О программе и гиперссылка с именем пользователя.

Реализовано свойство глобального контекста КлиентскоеПриложение, с помощью которого можно получить доступ к настройкам клиентского приложения (включая получение и изменение заголовка окна клиентского приложения). Для объекта метаданных, описывающего конфигурацию, реализовано свойство РежимОсновногоОкнаКлиентскогоПриложения.

Изменен номер версии формата выгрузки конфигурации в файлы.

Следующие методы глобального контекста объявляются устаревшими и их использование не рекомендуется: УстановитьКраткийЗаголовокПриложения(), ПолучитьКраткийЗаголовокПриложения(), УстановитьЗаголовокКлиентскогоПриложения(), ПолучитьЗаголовокКлиентскогоПриложения(), ТекущийВариантОсновногоШрифтаКлиентскогоПриложения(), ТекущийВариантИнтерфейсаКлиентскогоПриложения().

Данные возможности доступны при работе в интерфейсе Такси.

Данные возможности не предоставлялись.Расширены возможности управления внешним видом клиентского приложения. Стало возможно реализовывать специфические виды интерфейсов (интерфейс кассира, киоск самообслуживания и т.д.).
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Общие реквизиты / Разделение данных.
Реализована возможность указания, что общий реквизит, являющийся разделителем, может разделять или не разделять расширения конфигурации. Для объекта конфигурации ОбщийРеквизит реализовано свойство РазделениеРасширенийКонфигурации.

Не рекомендуется включать разделение расширений для разделителей, находящихся в режиме Независимо и совместно.

Расширения конфигурации всегда разделялись всеми разделителями конфигурации. Было невозможно отключить разделение расширений, если в информационной базе было включено разделение данных.Стало возможно управлять разделением расширений конфигурации, которые будут использоваться в информационной базе. Например, разработчик конфигурации может указать, что расширения конфигурации не должны разделяться никакими разделителями, которые существуют в прикладном решении.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Для тонкого и толстого клиентских приложений, работающих через прямое подключение к серверу «1С:Предприятия», реализовано использование механизма отслеживания разрыва соединений с сервером. В случае обнаружения проблемы с сервером, клиентское приложение автоматически пытается переустановить соединение и повторить серверный вызов. Если переустановить соединение невозможно - работа приложения будет завершена.

Временные интервалы проверки различаются для разных клиентских приложений:

  • Толстый клиент: проверка выполняется каждые 12 секунд, клиентское приложение ожидает установку соединения с сервером 60 секунд.
  • Тонкий клиент: проверка выполняется каждые 3 секунды, клиентское приложение ожидает установку соединения с сервером 15 секунд.

Значения таймаутов не настраиваются.

Если во время работы тонкого и толстого клиентских приложений, использующих прямое подключение к серверу «1С:Предприятия», на сервере «1С:Предприятие» возникали проблемы, то клиентские приложения могли «зависнуть» на очень длительные интервалы времени (минуты). Период «зависания» определяется настройками TCP-стека в используемой операционной системе.Повышена предсказуемость работы клиентского приложения, использующего прямое соединение с сервером «1С:Предприятия». Снижена вероятность возникновения неожиданных «зависаний» при работе.
В документации данное изменение описано здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД PostgreSQL версии 9.6.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Postgres Pro Enterprise версии 9.6 (только в управляемом режиме управления блокировками).СУБД Postgres Pro Enterprise не поддерживалась.Расширен список поддерживаемых СУБД.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Системные требования.
Веб-клиент.
Прекращена поддержка веб-браузера Mozilla Firefox версии 51 и младше.Веб-браузер Mozilla Firefox версии 51 и младше, поддерживался системой.Прекращена поддержка устаревших версий веб-браузера Mozilla Firefox.
В документации данное изменение описано здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Табличный документ.
Для табличного документа в режиме ввода данных, отображаемого в веб-клиенте, реализовано отображение автоотметки незаполненного.Для табличного документа в режиме ввода данных, отображаемого в веб-клиенте, не было реализовано отображение автоотметки незаполненного.Устранено некорректное поведение системы.
Управляемая форма.
Изменился расчет размеров закладок страниц и их отображение в вертикальном режиме.

В тонком и толстом клиентских приложениях реализовано масштабирование картинок в закладках страниц при изменении DPI. В режиме совместимости с версией 8.3.9 поведение не изменилось.

Незначительно изменены размеры и положение некоторых элементов управляемой формы.

Изменен внешний вид полосы регулирования в интерфейсе Такси и в веб-клиенте в интерфейсе Версия 8.2. При этом внешний вид полосы регулирования в веб-клиенте отличается от такового в тонком и толстом клиентских приложениях.

Цветная картинка в поле ввода, которое отображает данные типа Цвет, в веб-клиенте при разных масштабах имеет размеры, отличные от аналогичных размеров в тонком и толстом клиентских приложениях.

Доработан внешний вид системных форм в тонком и толстом клиенте в интерфейсе Такси для большего соответствия общему виду интерфейса.

Увеличена область нажатия на картинки скрытия/раскрытия уровней и узлов дерева в таблице в интерфейсе Такси.

Улучшено отображение элементов управления при нестандартном значении DPI.

Изменён расчёт размеров для поля формы вида полоса регулирования.

Внешний вид интерфейса был другим.

В тонком и толстом клиентских приложениях картинки в закладках страниц не изменяли размер при изменении DPI.

Улучшен внешний вид клиентского приложения.
Управляемая форма.
Изменен дизайн панели навигации формы в интерфейсе Такси. Первый элемент панели называется Основное.

В панели навигации формы отображаются все команды. Для всех команд панели выводятся полные названия. Если команда не помещается на панели действий формы - команда отображается в меню Еще.

Дизайн панели навигации формы был другим. Первый элемент панели назывался Главное.

При отображении команд действовало следующее правило: если в группе Важное было более двух команд - отображались только эти команды, в противном случае - все команды. Команды, которые не помещались в панель навигации формы, отображались в меню Еще.

В тонком и толстом клиентских приложениях длинные названия укорачивались и завершались символом троеточия (...).

Улучшен пользовательский интерфейс приложения.
Интерфейс.
В интерфейсе Такси переработана панель открытых окон:
  • Ширина каждого элемента панели зависит от заголовка окна.
  • При горизонтальном расположении панели, заголовок выводится в одну строку, при вертикальном - количество строк не ограничено.
  • При горизонтальном расположении панели в ее правой части отображается элемент управления для доступа к полному списку открытых окон.
  • При вертикальном расположении панели открытых возможно появление полосы прокрутки. При этом прокрутка панели открытых осуществляется независимо от рабочей области основного окна.
  • Реализована возможность закрытия окна нажатием средней кнопки мыши на соответствующем элементе панели открытых окон.
  • В контекстном меню элемента панели реализованы различные способы закрытия окон.
  • Реализована возможность изменения порядка окон в панели путем перетаскивания.
  • В том случае, если настроено отображение панели открытых, в рабочей области основного окна приложения отсутствует кнопка перехода к начальной странице.
Панель открытых (в интерфейсе Такси) имела другой дизайн и возможности:
  • Ширина элементов панели была фиксированной и не зависела от содержимого.
  • При горизонтальном расположении панели заголовок элемента имел в высоту не более двух строк.
  • Окно панели открытых было нельзя закрыть нажатием средней кнопки мыши по элементу панели.
  • Порядок следования элементов панели открытых не мог быть изменен интерактивно.
  • В рабочей области основного окна приложения всегда присутствует кнопка перехода к начальной странице.
В интерфейсе Такси стало более удобно пользоваться панелью открытых.
В документации данное изменение описано здесь и здесь.
Табличный документ.
Веб-клиент.
В табличном документе, отображаемом в веб-клиенте, отображаются все типы рамок. Внешний вид линий рамок зависит от используемого браузера и может отличаться от вида рамок табличного документа, отображаемого в тонком и толстом клиентских приложениях.При оформлении ячейки табличного документа отображались только следующие типы линий: Сплошная, Точечная и НетЛинии. Другие типы линий заменялись доступными следующим образом:
  • тип линии Двойная заменялся на Сплошная;
  • типы линий РедкийПунктир, ЧастыйПунктир и БольшойПунктир заменялись типом Точечный.

    • +

Устранено некорректное поведение системы.

Рамки ячеек табличного документа веб-клиента стали визуально лучше соответствовать рамкам табличного документа в тонком и толстом клиентских приложениях.

Управляемая форма.
В том случае, если область фиксации таблицы управляемой формы больше видимой области таблицы, выполняется автоматическое отключение фиксации колонок.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Если область фиксации превышала размеры всей таблицы, то таблицу невозможно было прокрутить по горизонтали.Повышен комфорт работы пользователя с таблицей для форм небольшого размера.
В документации данное изменение описано здесь.
Система компоновки данных.
В макете оформления компоновки данных «Основной», используемом в интерфейсе Такси, для всех областей макета (кроме заголовка отчета) цвет текста установлен в значение Авто.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В макете оформления компоновки данных «Основной», используемом в интерфейсе Такси, для некоторых областей макета (кроме заголовка отчета) в качестве цвета текста использовался серый цвет.При отображении и печати отчета система «1С:Предприятие» стала подбирать цвет, наиболее подходящий для восприятия.
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность выполнять сортировку динамического списка с помощью щелчка мыши по заголовку колонки таблицы, отображающей данные динамического списка, при наличии в тексте запроса агрегатных функций и выражений СГРУППИРОВАТЬ ПО.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Не поддерживалась возможность выполнять сортировку динамического списка с помощью щелчка мыши по заголовку колонки таблицы, отображающей данные динамического списка, при наличии в тексте запроса агрегатных функций и выражений СГРУППИРОВАТЬ ПО.Поведение таблицы, отображающей данные динамического списка, стало более привычно и ожидаемо пользователем.
Управляемая форма.
В тонком и толстом клиентских приложениях прокрутка колесом мыши выполняется для того элемента, над которым находится курсор мыши (если такая прокрутка возможна). Прокрутка выполняется также в том случае, когда прокручиваемый элемент не имеет фокуса ввода.

После окончания прокрутки элемента формы начинает прокручиваться родительский элемент формы, если в нем такая прокрутка возможна.

В тонком и толстом клиентских приложениях прокрутка колесом мыши элемента формы была возможно только если прокручиваемый элемент был активным.

В веб-клиенте прокрутка колесом мыши выполнялась и для неактивных элементов управляемой формы.

Навигация в управляемой форме стала более удобной для пользователя.

Унифицировано поведение прокрутки между веб-клиентом, тонким и толстым клиентскими приложениями.

Клиентское приложение.
Отображение информации.
Все стандартные картинки клиентского приложения реализованы в виде наборов картинок, адаптированных к различным значениям DPI и масштабам отображения.

Стандартные картинки перерисованы с изменением дизайна.

Стандартные картинки клиентского приложения не зависели от DPI и масштаба отображения. Из-за этого стандартные картинки могли отображаться размытыми на нестандартных значениях DPI.Улучшено отображение интерфейса клиентского приложения при нестандартных значениях DPI и масштаба отображения.
Установка клиентского приложения.
При возникновении проблем во время обновления тонкого клиента по протоколу HTTP, реализована возможность получить информацию о имени файла, при работе с которым обнаружена проблема. Эта возможность предоставляется в следующих случаях:
  • Если архив поврежден или имеет некорректную структуру. В этом случае будет указано имя файла с архивом.
  • Если цифровая подпись одного из файлов дистрибутива недействительна. В этом случае будет указано имя файла дистрибутива с недействительной цифровой подписью.
При возникновении проблем во время обновления тонкого клиента по протоколу HTTP не предоставлялась возможность получить информацию о имени файла, при работе с которым обнаружена проблема. В частности, не предоставлялась информация об имени файла, если архив был поврежден или его структура была некорректной или какой-либо из файлов дистрибутива клиентского приложения имел недействительную цифровую подпись.Улучшена диагностика проблем при обновлении клиентского приложения по протоколу HTTP.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Кластер серверов.
Повышена масштабируемость кластера серверов в том случае, если:
  • на сервере установлены центральные процессоры с большим количество ядер;
  • обслуживается большое количество пользователей;
  • используется сжатие служебного обмена данными между клиентской и серверной частью системы.

Снижено количество оперативной памяти, используемой сервером «1С:Предприятия», если в прикладном решении используются пакетные запросы.

Кластер серверов плохо масштабировался в том случае, если:
  • на сервере установлены центральные процессоры с большим количество ядер;
  • обслуживается большое количество пользователей;
  • используется сжатие служебного обмена данными между клиентской и серверной частью системы.

Сервер «1С:Предприятия» использовал большее количество оперативной памяти в том случае, если в прикладном решении используются пакетные запросы.

Повышена масштабируемость кластера серверов «1С:Предприятие».
Встроенный язык.
Ускорено исполнение кода на встроенном языке, на стороне сервера системы «1С:Предприятие».На стороне сервера системы «1С:Предприятие» код на встроенном языке исполнялся медленнее.Оптимизировано исполнение встроенного языка на сервере «1С:Предприятие».
Система компоновки данных.
Повышена скорость инициализация компоновщика настроек компоновки данных источником доступных настроек компоновки данных при использовании схемы, которая содержит большое количество вычисляемых полей.Инициализация компоновщика настроек компоновки данных источником доступных настроек компоновки данных при использовании схемы, которая содержит большое количество вычисляемых полей, выполнялась недостаточно быстро.В ряде случаев повышена скорость инициализации системы компоновки данных.
Кластер серверов.
При использовании в прикладном решении пакетных запросов снижен объем используемой оперативной памяти на сервере «1С:Предприятие».При использовании в прикладном решении пакетных запросов использовался большой объем оперативной памяти на сервере «1С:Предприятие».Снижено потребление оперативной памяти сервером «1С:Предприятие» при использовании пакетных запросов.
Хранилище конфигурации.
Оптимизировано обновление локального кеша хранилища конфигурации при выполнении операций помещения и получения объектов из хранилища.Операции помещения и получения объектов из хранилища конфигурации выполнялись недостаточно быстро.Ускорены операции помещения и получения объектов из хранилища конфигурации.
Средства разработки.
Реализовано сохранение индекса поиска по модулям между сеансами работы конфигуратора. Уменьшено время первого формирования индекса поиска по модулям. Существенно уменьшено время формирования индекса поиска по модулям для второго и последующего сеансов работы конфигуратора.

При запуске конфигуратора с ключом командной строки /ClearCache выполняется очистка индекса поиска по модулям.

Индекс поиска по модулям не сохранялся между сеансами работы конфигуратора. Индекс формировался существенно больше времени.Работа разработчика с большими конфигурациями стала более комфортна.
В документации данное изменение описано здесь.
Встроенный язык.
При поиске строк в таблице значений методом НайтиСтроки(), подбор индекса осуществляется только на основании совпадения состава колонок в параметрах поиска и в индексе. Порядок следования колонок в параметрах поиска и в индексе не влияет на выбор индекса.При поиске строк в таблице значений методом НайтиСтроки(), индекса использовался только в том случае, если порядок следования и состав колонок в параметрах поиска совпадал с таковым в индексе.Ускорен поиск в таблице значений по нескольким колонкам при наличии индекса.
Полнотекстовый поиск.
Оптимизировано построение и обновление индекса полнотекстового поиска.Построение и обновление индекса полнотекстового поиска выполнялось с меньшей скоростью.Уменьшены затраты времени на поддержание индекса полнотекстового поиска в актуальном состоянии.
Работа с СУБД.
Работа с запросами.
При работе в файловом варианте информационной базы повышена скорость работы запроса, содержащего ключевое слово РАЗЛИЧНЫЕ и получающего большое количество записей.При работе в файловом варианте информационной базы скорость работы запроса, содержащего ключевое слово РАЗЛИЧНЫЕ и получающего большое количество записей, была недостаточной.Ускорена работа файлового варианта информационной базы в случае получения списка уникальных записей из большого объема записей.
Работа с СУБД.
Работа с запросами.
Повышена скорость удаления больших наборов записей в файловом варианте информационной базы.

Повышена скорость пересчета итогов для таблиц с большим количеством записей в файловом варианте информационной базы.

В файловом варианте информационной базы недостаточно быстро выполнялись следующие операции:
  • удаление больших наборов записей;
  • пересчет итогов для таблиц с большим количеством записей.
В ряде сценариев повышена скорость работы с файловым вариантом информационной базы.
Динамический список.
Повышена производительность получения данных, отображаемых динамическим списком, при использовании условного оформления.

+

Производительность получения данных, отображаемых динамическим списком, при использовании условного оформления была недостаточной.Повышена производительность работы динамического списка с использованием условного оформления.
Динамический список.
Ускорено открытие формы, содержащей динамический список со сложным запросом.Открытие формы, содержащее динамический список со сложным запросом, было недостаточно быстрым.Ускорено открытие форм, содержащих динамические списки, которые формируются сложными запросами.
Динамический список.
Для динамического списка реализована возможность управлять получением представлений для значений ссылочных типов, которые не отображаются на форме или связаны с фактически невидимыми элементами формы. При этом, получение представлений значений ключевых полей для динамического списка, находящегося в режиме выбора, выполняется в любом случае.

Реализовано свойство динамического списка ПолучениеПредставленийДляНевидимыхПолей.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В динамическом списке выполнялось получение представлений для всех значений ссылочного типа, которые передавались на сторону клиентского приложения.Предоставляется возможность ускорить отображение динамического списка в некоторых сценариях использования.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Оптимизировано использование оперативной памяти при компоновке макета компоновки данных в случае использования в схеме компоновки данных больших текстов запросов.Наблюдалось неоптимальное использование оперативной памяти при компоновке макета компоновки данных в случае использования в схеме компоновки данных больших текстов запросов.Компоновка макета компоновки данных при использовании в схеме компоновки данных больших текстов запросов стала использовать меньше оперативной памяти.
Работа с информационными базами.
Незначительно ускорен запуск тонкого клиента в файловом варианте информационной базы при работе с большой конфигурацией.Запуск тонкого клиента в файловом варианте информационной базы при работе с большой конфигурацией занимал больше времени.Ускорен запуск тонкого клиента при работе с файловым вариантом информационной базы при работе с большой конфигурацией.
Хранилище конфигурации.
Оптимизированы операции захвата и отмены захвата объектов в хранилище конфигурации.

Для информационной базы, подключенной к хранилищу, изменен внутренний формат хранилища информации о захваченных объектах.

Изменение формата происходит после выполнения операции оптимизации хранения информации в диалоге Настройка использования локальных данных хранилища. Оптимизация доступна только если конфигурация была подключена к хранилищу конфигурации в предыдущих версиях платформы.

При необходимости работать с оптимизированной информационной базой в предыдущих версиях платформы потребуется заново выполнить подключение к хранилищу в предыдущей версии платформы. +

Операции захвата и отмены захвата объектов в хранилище конфигурации требовали больше времени.Ускорена работа с хранилищем конфигурации для больших конфигураций.
В документации данное изменение описано здесь.
Клиентское приложение.
Ускорен запуск клиентского приложения после использования динамического обновления.После выполнения динамического обновления клиентское приложение запускалось за более продолжительное время.Ускорен запуск клиентского приложения после использования динамического обновления.
Web-сервисы и HTTP-сервисы.
При вызове методов Web- и HTTP-сервисов выполняется кеширование скомпилированного модуля соответствующего сервиса.При каждом вызове методов Web- и HTTP-сервисов выполнялась компиляция модуля соответствующего сервиса.Ускорена работа системы при большом количестве вызовов Web- и HTTP-сервисов.
Регистры бухгалтерии.
Работа с СУБД.
При использовании файлового или клиент-серверного варианта (при работе на СУБД PostgreSQL) информационной базы ускорены следующие операции с набором записей регистра бухгалтерии:
  • Запись набора записей.
  • Чтение набора записей.
  • Открытие формы набора записей.
При использовании файлового или клиент-серверного варианта (при работе на СУБД PostgreSQL) информационной базы следующие операции с набором записей регистра бухгалтерии выполнялись недостаточно быстро:
  • Запись набора записей.
  • Чтение набора записей.
  • Открытие формы набора записей.
Оптимизирована работа с регистром бухгалтерии при использовании некоторых СУБД.
Работа с СУБД.
Оптимизирована работа планировщика запросов СУБД PostgreSQL версии 9.6.3. В результате оптимизации повышена эффективность работы СУБД со сложными запросами, в которых используются шаблоны ограничений доступа к данным.

Оптимизация доступа начиная с PostgreSQL версии 9.6.3-2.1С.

При исполнении сложных запросов, в которых используются шаблоны ограничений доступа к данным, наблюдались снижение эффективности работы СУБД PostgreSQL, которое выражалось в виде «зависания» системы.Повышена эффективность работы СУБД PostgreSQL при работе с системой «1С:Предприятие».

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Фоновые и регламентные задания.
Кластер серверов.
Изменен подход к хранению истории исполнения фоновых и регламентных заданий. В клиент-серверном варианте история хранится в разрезе информационных баз. Для каждой информационной базы хранится история:
  • до 1 000 фоновых заданий, созданных из встроенного языка;
  • до 1 000 регламентных заданий;
  • до 1 000 системных фоновых заданий (формируемых самой системой).

Для каждого задания (фонового, системного фонового и регламентного) будет предприниматься попытка хранить информацию минимум о трех последних запусках. Это количество (три запуска) будет уменьшаться в том случае, если превышен лимит в 1 000 записей на тот или иной вид заданий. +

В файловом варианте история запуска фоновых и регламентных заданий хранилась в разрезе информационной базы. В клиент-серверном варианте история запуска хранилась в разрезе кластера серверов. В обоих случаях информация хранилась не более чем о 1 000 запусков без разделения на виды заданий: фоновые, регламентные или системные фоновые.Улучшена система диагностики работы фоновых и регламентных заданий при их большом количестве. Уменьшена вероятность того, что информация о редком запуске фоновых заданий, стартуемых из встроенного языка, будет вытеснена информацией о большом количестве регламентных или системных фоновых заданий.
В документации данное изменение описано здесь.
Отображение информации.
Диаграммы.
Для объектов Диаграмма, ДиаграммаГанта, СводнаяДиаграмма, Дендрограмма для свойства Шрифт подчиненных объектов, описывающих различные области диаграмм, значение по умолчанию равно Авто, что интерпретируется как Обычный шрифт текста.

В том случае, если веб-клиент функционирует под управлением ОС Windows, то при отображении диаграммы в веб-клиенте, при экспорте табличного документа с диаграммой в формате HTML5 и при экспорте диаграммы в формате SVG выполняется проверка, что для используемых в диаграмме шрифтов операционной системой не выполняется подстановка (замена шрифта с одним именем на другой). Если подстановка выполняется, то в результирующие файлы попадает реальное имя шрифта.

При экспорте табличного документа в формат HTML и при отображении табличного документа в веб-клиенте системные шрифты не заменяются на шрифт Arial, а происходит определение имени реального шрифта, который используется системой для отображения. +

Для объектов Диаграмма, ДиаграммаГанта, СводнаяДиаграмма, Дендрограмма для свойства Шрифт подчиненных объектов, описывающих различные области диаграмм, значение по умолчанию было равно Шрифт текста.

В том случае, если веб-клиент функционирует под управлением ОС Windows, то при отображении диаграммы в веб-клиенте, при экспорте табличного документа с диаграммой в формате HTML5 и при экспорте диаграммы в формате SVG используемые шрифты попадали в результирующие файлы «как есть», без определения реально используемых шрифтов.

При экспорте табличного документа в формат HTML и при отображении табличного документа в веб-клиенте системные шрифты заменялись на шрифт Arial.

Унифицированы шрифты, используемые для отображения диаграмм в различных клиентских приложениях (включая разные веб-браузеры). Унифицированы шрифты, используемые при отображении табличного документа в различных клиентских приложениях.

При экспорте табличного документа, содержащего диаграммы, сохраняются реальные шрифты, которые использованы для отображения диаграммы в табличном документе.

Двоичные данные.
Расширены возможности работы с двоичными данными. Реализована возможность преобразования в двоичные данные и обратно из следующих типов данных: массив двоичных данных, строка, буфер двоичных данных, строка в виде Base64, 16-тиричная строка, двоичные данные, записанные строкой.

Реализована возможность использования двоичных данных в тех методах и конструкторах, где ранее было возможно использовать только файлы.

Реализована возможность выполнения побитовых операций (И, ИЛИ, НЕ, Исключающее ИЛИ, И-НЕ, Инверсия) для двоичных данных, размещенных в буфере двоичных данных.

При разработке внешних компонент реализована возможность обмениваться двоичными данными с внешней компонентой (включая веб-клиент).

Реализована возможность пакетного получения нескольких разрешений при работе с двоичными данными в веб-клиенте.

Реализована возможность напрямую копировать двоичные данные из объекта ЧтениеДанных в объект ЗаписьДанных.

Реализованы методы глобального контекста СоединитьДвоичныеДанные(), РазделитьДвоичныеДанные(), ПолучитьДвоичныеДанныеИзСтроки(), ПолучитьБуферДвоичныхДанныхИзСтроки(), ПолучитьСтрокуИзДвоичныхДанных(), ПолучитьСтрокуИзБуфераДвоичныхДанных(), ПолучитьДвоичныеДанныеИзBase64Строки(), ПолучитьБуферДвоичныхДанныхИзBase64Строки(), ПолучитьBase64СтрокуИзДвоичныхДанных(), ПолучитьBase64ДвоичныеДанныеИзДвоичныхДанных(), ПолучитьДвоичныеДанныеИзBase64ДвоичныхДанных(), ПолучитьBase64БуферДвоичныхДанныхИзБуфераДвоичныхДанных(), ПолучитьБуферДвоичныхДанныхИзBase64БуфераДвоичныхДанных(), ПолучитьДвоичныеДанныеИзHexСтроки(), ПолучитьБуферДвоичныхДанныхИзHexСтроки(), ПолучитьHexСтрокуИзДвоичныхДанных(), ПолучитьHexСтрокуИзБуфераДвоичныхДанных(), ПолучитьHexДвоичныеДанныеИзДвоичныхДанных(), ПолучитьДвоичныеДанныеИзHexДвоичныхДанных(), ПолучитьHexБуферДвоичныхДанныхИзБуфераДвоичныхДанных(), ПолучитьБуферДвоичныхДанныхИзHexБуфераДвоичныхДанных(), ПолучитьДвоичныеДанныеИзБуфераДвоичныхДанных(), ПолучитьБуферДвоичныхДанныхИзДвоичныхДанных(), ЧислоИзШестнадцатеричнойСтроки(), ЧислоИзДвоичнойСтроки().

Реализована возможность использовать поток двоичных данных:

  • В конструкторах объектов ЧтениеТекста, ЗаписьТекста, ЧтениеZipФайла, ЗаписьZipФайла.
  • В методе Открыть() объектов ЧтениеТекста, ЗаписьТекста, ЗаписьZIPФайла, ЧтениеZIPФайла.
  • В методе Записать() объектов ТекстовыйДокумент, ТабличныйДокумент, ФорматированныйДокумент, ГеографическаяСхема, Картинка, FTPСоединение.
  • В методе Прочитать() объектов ТекстовыйДокумент, ТабличныйДокумент, ГеографическаяСхема.
  • В методах объекта МенеджерКриптографии: Зашифровать(), Расшифровать(), Подписать(), ПроверитьПодпись().
  • В методе СертификатКриптографии.Выгрузить().
  • В методе ХешированиеДанных.Добавить().
  • В методе FTPСоединение.Получить().

Реализован метод ОткрытьПоток() для объектов ЧтениеHTML, ЗаписьHTML, ЧтениеJSON, ЗаписьJSON, ЧтениеFastInfoset, ЗаписьFastInfoset, ЧтениеXML, ЗаписьXML.

Реализован метод ПолучитьТелоКакПоток() для объектов HTTPЗапрос, HTTPОтвет, HTTPСервисЗапрос, HTTPСервисОтвет.

Реализован метод ПреобразованиеККаноническомуXML.КанонизироватьВПоток().

Для объекта ПреобразованиеXSL реализованы методы ЗагрузитьТаблицуСтилейXSL(), Преобразовать().

Реализован метод ЗаписьZipФайла.ПолучитьДвоичныеДанные().

Для объекта БуферДвоичныхДанных реализованы методы ЗаписатьПобитовоеИ(), ЗаписатьПобитовоеИли(), ЗаписатьПобитовоеИсключительноеИли(), ЗаписатьПобитовоеИНе(), Инвертировать().

Для объекта ЧтениеДанных реализованы методы КопироватьВ(), НачатьКопированиеВ().

Для методов КопироватьВ() и НачатьКопированиемВ() объекта Поток изменено назначение второго параметра метода и возвращаемое значение: в параметре передается количество байт, которые необходимо скопировать, а возвращается реальное количество скопированных байт. Размер буфера определяется системой автоматически. Описания методов приведены в соответствие с аналогичными методами объекта ЧтениеДанных. В режиме совместимости с версией 8.3.9 поведение не изменилось.

Данные возможности не предоставлялись.

Для методов КопироватьВ() и НачатьКопированиеВ() объекта Поток в качестве второго параметра передавался размер буфера, используемый при копировании, а возвращаемые значения отсутствовали.

Упрощено использование двоичных данных при решении различных прикладных задач.
В документации данное изменение описано здесь, здесь и здесь.
Журнал регистрации.
При работе с журналом регистрации, в том числе открытым из файла, строка представления данных, записанная в журнал при регистрации события, показывается пользователю только в том случае, если у этого пользователя есть права на просмотр этих данных или есть право Администрирование. Если у пользователя нет права Администрирование и есть вероятность, что представление ему недоступно, сохраненное представление от него скрывается.

Если в записи журнала регистрации в поле Данные находится ссылка, то поле Представление данных будет пустым, если есть вероятность, что у пользователя нет прав на соответствующий объект данных.

Представление данных журнала регистрации отображалось без проверки прав доступа пользователя, который просматривает журнал регистрации.Убрана возможность для пользователя с ограниченными правами получить доступ к информации, которая ему недоступна, через ранее сохраненное представление недоступного этому пользователю объекта.
В документации данное изменение описано здесь.
Средства разработки.
В окне стека вызовов в отладчике реализовано корректное отображение параметров метода в том случае, если параметр содержит очень длинную текстовую строку или многострочную строку. В этом случае для формирования представления берется первые 20 символов такого параметра, после чего дописывается текст «...», а затем продолжается список параметров и закрывающая скобка метода.В окне стека вызовов в отладчике отображение параметра метода в том случае, если параметр содержит очень длинную текстовую строку или многострочную строку, выполнялось некорректно: текстовое представление последующих параметров (если таковые есть) и закрывающая скобка метода не отображались.Информация в окне стека вызовов стала более корректной.
Табличный документ.
При экспорте табличного документа в форматы XLS (Microsoft Excel 97-2003) и Microsoft Office OpenXML (Microsoft Excel 2007- 2010) текст в ячейке преобразуется в число только в том случае, если в ячейке установлено горизонтальное выравнивание вправо. В противном случае содержимое ячейки сохраняется в в виде текста.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При экспорте табличного документа в форматы XLS (Microsoft Excel 97-2003) и Microsoft Office OpenXML (Microsoft Excel 2007- 2010) текст в ячейке преобразовывался в число при любом горизонтальном выравнивании содержимого ячейки.Экспорт табличного документа в форматы XLS (Microsoft Excel 97-2003) и Microsoft Office OpenXML (Microsoft Excel 2007- 2010) стал более корректным.
В документации данное изменение описано здесь.
Средства печати.
Реализована возможность настройки умолчания для размера страницы при печати (в том числе при выводе в формат PDF). Данную возможность можно использовать при работе в веб-клиенте и для документов, формируемых в регламентных заданиях. Реализован объект НастройкиПечати.

В диалоге настроек параметров веб-клиента реализована настройка Размер страницы по умолчанию.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В качестве размера бумаги по умолчанию использовался формат А4.

В диалоге настроек параметров веб-клиента отсутствовала настройка Размер страницы по умолчанию.

В веб-клиенте, при печати или сохранении в формате PDF, для разбиения документа на страницы будет использоваться размер бумаги, установленный для конкретного клиентского приложения. В результате документ будет лучше соответствовать ожиданиям пользователя.

Аналогичные возможности стали доступны для документов, формируемых с помощью регламентных заданий.

В документации данное изменение описано здесь.
Система компоновки данных.
При интерактивной загрузке схемы компоновки данных и настроек компоновки данных, из схемы и настроек автоматически удаляются отсутствующие в текущей конфигурации стилевые цвета и шрифты.При интерактивной загрузке схемы компоновки данных и настроек компоновки данных, выдавалась ошибка преобразования XDTO, если в загружаемой схеме или настройках использовались стилевые цвета и шрифты, которые отсутствуют в текущей конфигурации.Стало возможно использовать в прикладном решении схему компоновки данных и настройку компоновки данных, в оформлении которых использовались стилевые цвета и шрифты другой конфигурации.
Динамический список.
В динамическом списке содержимое папки Системные поля недоступно для использования в качестве полей выбора.

Если в динамическом списке не указана основная таблица или в основной таблице отсутствует поле ключа, которое может использовать динамический список, то в таком списке не поддерживается настройка полей группировки.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В динамическом списке содержимое папки Системные поля было доступно для использования в качестве полей выбора.

Если в динамическом списке не указана основная таблица или в основной таблице отсутствует поле ключа, которое может использовать динамический список, настройка группировок была доступна, однако приводило к ошибке получения данных.

Устранено некорректное поведение системы.

Повышена надежность работы динамического списка.

В документации данное изменение описано здесь.
Динамический список.
В толстом клиенте недоступны следующие свойства объекта ДинамическийСписок: ДинамическоеСчитываниеДанных, ОсновнаяТаблица, ПроизвольныйЗапрос, ТекстЗапроса.

Не поддерживается присвоение значения реквизиту формы типа ДинамическийСписок.

Не поддерживается передача реквизита типа ДинамическийСписок в качестве параметра метода или возвращаемого значения клиент-серверного взаимодействия.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В толстом клиенте были доступны следующие свойства объекта ДинамическийСписок: ДинамическоеСчитываниеДанных, ОсновнаяТаблица, ПроизвольныйЗапрос, ТекстЗапроса. Однако их изменение не приводило к каким-либо изменениям в работе динамического списка.

Поддерживалось присвоение значения реквизиту управляемой формы типа ДинамическийСписок. При этом дальнейшее поведение системы было неопределено.

Допускалась передача реквизита типа ДинамическийСписок в качестве параметра метода или возвращаемого значения клиент-серверного взаимодействия. При этом дальнейшее поведение системы было неопределено.

Повышена надежность работы динамического списка. Некорректное использование динамического списка больше не поддерживается.
В документации данное изменение описано здесь.
Диаграммы.
Информация о серии (маркер) в легенде диаграммы зависит от того, каким образом (цвет линии, стиль линии, маркер) отображается в диаграмме эта серия.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В легенде диаграммы всегда выводился квадратный маркер того цвета, которым в диаграмме выводится соответствующая серия.Улучшена читаемость диаграммы, особенно при черно-белой печати.
В документации данное изменение описано здесь.
Система компоновки данных.
Макеты ресурсов, создаваемых на пересечении с соответствующими предопределенными макетами заголовков группировок, создаются пустыми.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В макетах ресурсов, создаваемых на пересечении с соответствующими предопределенными макетами заголовков группировок, отображались ресурсы.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с криптографией.
Если серийный номер сертификата начинается с установленного старшего бита, то к серийному номеру добавляется ведущий нулевой байт.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Серийный номер сертификата не дополнялся ведущим нулевым байтом.Устранены недостатки при работе механизма работы с криптографией.
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность отключать автоматическое заполнение доступных полей динамического списка. Данная возможность доступна только в том случае, если динамический список формируется произвольным запросом.

Поведение системы аналогично такой возможности схемы компоновки данных.

Реализовано свойство динамического списка АвтоЗаполнениеДоступныхПолей.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Для любого запроса динамического списка было включено автоматическое заполнение доступных полей.Стало возможно управлять доступностью полей списка с помощью расширения языка запросов для системы компоновки данных.
В документации данное изменение описано здесь.
Диаграммы.
Система компоновки данных.
Реализована возможность управлять порядком вывода серий в легенде диаграмм, в том числе, реализованных с помощью системы компоновки данных.

Реализовано свойство Диаграмма.ПорядокСерийВЛегенде.

Для объекта ТипДиаграммы объектов ОформлениеДиаграммыОбластиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных, ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных реализован параметр ПорядокСерийВЛегенде.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Порядок следования серий в легенде диаграммы был недоступен для управления.Расширены возможности настройки отображения диаграмм.
В документации данное изменение описано здесь.
Средства разработки.
Пользователю будет задан вопрос о необходимости сохранения результатов работы, если он попытается закрыть диалог редактирования выражения запроса (в конструкторе запроса) с помощью клавиши ESC или кнопки закрытия окна («крестик»), а редактируемое выражение было изменено.Пользователю не задавался вопрос о необходимости сохранения результатов работы, если он пытался закрыть диалог редактирования выражения запроса (в конструкторе запроса) с помощью клавиши ESC или кнопки закрытия окна («крестик»), а редактируемое выражение было изменено. Результат работы в этом случае терялся.Устранено некорректное поведение системы.

Снижена вероятность потери результатов работы при редактировании выражения запроса.

Средства разработки.
Улучшена диагностика и поведение системы в том случае, если архив картинок содержит некорректный или отсутствующий манифест:
  • контроль архива выполняется при интерактивной загрузке;
  • в конфигураторе такая картинка не отображается в форме;
  • при обращении из такому архиву с помощью встроенного языка формируется ошибка, более точно соответствующая проблеме.
Если архив картинок содержит некорректный или отсутствующий манифест, то поведение системы было другим:
  • при интерактивной загрузке не выполнялась проверка архива;
  • попытка отображения такой картинки в конфигураторе или при обращении из встроенного языка могло приводить к аварийному завершению работы или ошибке, не позволяющей точно определить проблему.
Улучшена диагностика и стабильность работы при работе с архивом картинок, у которого манифест сформирован некорректно или отсутствует.
Выгрузка/загрузка конфигурации в файлы.
При выполнении полной загрузки конфигурации из файлов имеются следующие особенности:
  • конфигурацию, которая не стоит на поддержке и не подключена к хранилищу конфигурации, можно загрузить без ограничений (осталось без изменений);
  • конфигурацию, подключенную к хранилищу конфигурации, загрузить невозможно (недоступен соответствующий пункт меню);
  • конфигурацию, стоящую на поддержке, можно загрузить только при соблюдении следующих условий:
    • включена возможность изменений;
    • все объекты конфигурации можно редактировать.

При выполнении частичной загрузки конфигурации из файлов имеются следующие особенности:

  • загрузка возможна, только если все загружаемые объекты захвачены в хранилище конфигурации;
  • загрузка возможна, если для всех загружаемых объектов включена возможность изменения (для конфигурации, стоящей на поддержке).
Выгрузка и загрузка конфигурации из файлов никак не учитывала то, что конфигурация была подключена к хранилищу конфигурации или находилась на поддержке.Устранены проблемы, которые возникали при загрузке конфигурации из файлов в том случае, если конфигурация подключена к хранилищу конфигурации или находится на поддержке.
В документации данное изменение описано здесь, здесь и здесь.
Динамический список.
Усовершенствован механизм поиска через строку поиска динамического списка:
  • реализована возможность искать полную дату (с указанием времени);
  • реализована возможность искать числа с дробной частью без указания дробной части;
  • улучшено отображение результатов поиска.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Поиск через строку поиска динамического списка работал следующим образом:
  • при поиске полной даты (с указанием времени) - отдельно искалась дата и отдельно строка, содержащая время;
  • при поиске значения, похожего на число с указанием дробной части - выполнялся поиск отдельно целой части и отдельно дробной части, результаты объединялись «по И»;
  • отображение результатов поиска не всегда работало корректно.

+

Улучшен поиск в динамическом списке с использованием строки поиска.
Динамический список.
В диалоге расширенного поиска динамического списка недоступны для поиска (отсутствуют в списке полей Где искать) поля, которые недоступны для использования в отборе.

Если текущей колонкой таблицы, связанной со списком, является колонка, которая отображает поле, недоступное для использования в отборе – недоступна команда Найти по значению.

В диалоге расширенного поиска динамического списка были доступны для поиска (присутствовали в списке полей Где искать) поля, которые недоступны для использования в отборе.

Доступность команды Найти по значению не зависело от того, доступно поле, отображаемое текущей колонкой динамического списка, для использования в отборе или нет.

Устранено некорректное поведение системы.
Средства администрирования.
Тестирование и исправление информационной базы.
Во время тестирования и исправления информационной базы в файловом варианте, запись таблицы информационной базы удаляется, если после изменения записи ключ этой записи становится не уникальным. В окно сообщений об этом выводится соответствующее диагностическое сообщение.Во время выполнения тестирования и исправления информационной базы в файловом варианте не выполнялась проверка на уникальность ключа в измененной записи таблицы базы данных. Это приводило к возникновению записей с неуникальными ключами. Ситуация могла быть исправлена только повторным запуском операции тестирования и исправления.Поведение тестирования и исправления в файловом варианте информационной базы унифицировано с поведением в клиент-серверном варианте.
Встроенный язык.
Во всех клиентских приложениях, работающих в режиме управляемого приложения, в диалоге выбора типов и в диалоге описания типов присутствуют перечисления.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В тонком и в толстом клиентских приложениях, работающих в режиме управляемого приложения, диалог выбора типа и диалог описания типов не содержал перечислений.

В веб-клиенте в этих диалогах перечисления присутствовали.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
При экспорте табличного документа в формат Microsoft Office OpenXML (Microsoft Excel 2007 и старше), имя XML-компонента общих строк формируется с маленькой буквы: sharedStrings.xml.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При экспорте табличного документа в формат Microsoft Office OpenXML (Microsoft Excel 2007 и старше), имя XML-компонента общих строк формировалась с заглавной буквы: SharedStrings.xml.Поведение платформы приведено в соответствие со стандартом OpenXML. Повышена совместимость с системами, выполняющими разбор файлов формата OpenXML в тех случаях, когда имена файлов чувствительны к регистру символов.
В документации данное изменение описано здесь.
Управляемая форма.
Динамический список.
Реализована возможность устанавливать флажок Основной реквизит для реквизита управляемой формы типа КомпоновщикНастроекКомпоновкиДанных. В этом случае в качестве расширения формы будет выступать Расширение управляемой формы для компоновщика настроек.

Для такой формы становятся доступными свойство формы Группа пользовательских настроек и обработчик события ПриОбновленииСоставаПользовательскихНастроекНаСервере.

Свойство управляемой формы Основной реквизит устанавливалось только для автоматически генерируемой формы настроек динамического списка. Разработчик не мог создать такую форму.Разработчик может создать универсальную форму редактирования настроек компоновки данных.
Средства разработки.
При сравнении и объединении модулей (без использования внешних программ) учитывается расположение методов в областях, заданных с помощью инструкций препроцессора (#Область, #Если).

Области, заданные инструкциями препроцессора, выделяются как отдельные сущности (наряду с процедурами и функциями). Для таких областей реализована возможность указывать настройки параметров объединения.

Данная возможность не предоставлялась.

Инструкции препроцессора обрабатывались как комментарии, привязанные к процедуре, над которой они находятся.

В результате объединения могла нарушаться структура блоков, заданных инструкциями препроцессора.

Повышено удобство и надежность объединения модулей с помощью встроенных средств конфигуратора.
Управляемая форма.
В панели навигации формы элемента иерархического справочника или плана видов характеристик размещаются:
  • Команды перехода к подчиненным справочникам, для которых установлено подчинение элементам или элементам и группам (не изменилось по сравнению с предыдущими версиями).
  • Команды перехода к регистрам сведений, тип ведущего измерения которого совпадает с типом справочника или плана видов характеристик и у которых для этого измерения свойство Выбор групп и элементов установлено в Элементы или Группы и элементы.

В панели навигации формы группы иерархического справочника или плана видов характеристик размещаются:

  • Команды перехода к подчиненным справочникам, для которых установлено подчинение группам или элементам и группам.
  • Команды перехода к регистрам сведений, тип ведущего измерения которого совпадает с типом справочника или плана видов характеристик и у которых для этого измерения свойство Выбор групп и элементов установлено в Группы или Группы и элементы.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для иерархического справочника или плана видов характеристик все команды перехода к подчиненным справочникам располагались в панели навигации формы элемента. В панели навигации формы группы таких объектов конфигурации команд перехода к подчиненным справочникам не размещалось.

Для иерархического справочника или плана видов характеристик все команды перехода к регистрам сведений располагались в панели навигации формы элемента. В панели навигации формы группы таких объектов конфигурации команд перехода к регистрам сведений не размещалось.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства разработки.
Выгрузка/загрузка конфигурации в файлы.
При выгрузке конфигурации в файлы изменен формат выгрузки информации о динамическом списке, размещенном в управляемой форме.

Рекомендуется заново выгрузить формы, содержащие динамические списки. +

При выгрузке конфигурации в файлы, формат выгрузки информации о динамическом списке, размещенном в управляемой форме, был другим.XML-файлы выгрузки конфигурации стали более корректными.
Обновление конфигурации базы данных.
При обновлении конфигурации базы данных отключен вывод сообщений о создании и удалении таблиц опций планов видов характеристик, планов счетов, планов видов расчета и справочников.При обновлении конфигурации базы данных выводились сообщения о создании и удалении таблиц опций планов видов характеристик, планов счетов, планов видов расчета и справочников.При обновлении конфигурации базы данных исключен вывод сообщений, которые не несут никакой полезной информации пользователю.
Диаграммы.
Расширен набор палитр, которые могут использоваться для оформления диаграмм. Палитры могут содержать как фиксированный набор цветов, так и набор цветов, зависящий от количества серий. Реализована возможность установки собственного набора цветов отображения диаграммы. Для системного перечисления ПалитраЦветовДиаграммы реализованы значения Авто, Произвольная, Градиентная, Синяя, Оранжевая, Зеленая, Желтая, Серая, Теплая, Холодная, Яркая, Мягкая, Пастельная.

Для объекта Диаграмма реализованы:

  • свойства ЦветНачалаГрадиентнойПалитры, ЦветКонцаГрадиентнойПалитры, МаксимальноеКоличествоЦветовГрадиентнойПалитры.
  • методы ПолучитьПалитру(), УстановитьПалитру().

Для объекта ТипДиаграммы объектов системы компоновки данных ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных и ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы параметры ПалитраЦветов, ЦветНачалаГрадиентнойПалитры, ЦветКонцаГрадиентнойПалитры, МаксимальноеКоличествоЦветовГрадиентнойПалитры. +

Для указания цветов, используемых для построения диаграмм, были доступны только две палитры, состоящие из 8 и 32 цветов. Самостоятельная настройка палитры цветов диаграммы была недоступна.Расширены возможности по оформлению диаграмм.
Система компоновки данных.
Процессор вывода результата компоновки данных в табличный документ, при выводе объединенных ячеек, таким образом изменяет ширину колонок, в которых располагаются объединенные ячейки,чтобы содержимое этих ячеек занимало минимальное место по высоте.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Процессор вывода результата компоновки данных в табличный документ, при выводе объединенных ячеек, в некоторых случаях не изменял ширину колонок, в которых располагаются объединенные ячейки. В результате колонки могли иметь слишком маленький размер.В некоторых случаях улучшен расчет ширин колонок табличного документа, выполняемого процессором вывода результат компоновки данных в табличный документ, для объединенных ячеек.
В документации данное изменение описано здесь.
Регистры бухгалтерии.
Тип МоментВремениСУточнениемПериода стал доступен в тонком и веб-клиентах.Типа МоментВремениСУточнениемПериода был доступен только в толстом клиенте и на стороне сервера.Устранено некорректное поведение системы.
Табличный документ.
Для табличного документа реализована возможность выполнять специальную вставку из форматов XLS (Microsoft Excel 97-2003) и ODS (OpenDocument Spreadsheet).Для табличного документа было невозможно выполнить специальную вставку из форматов XLS (Microsoft Excel 97-2003) и ODS (OpenDocument Spreadsheet).При использовании специальной вставки в табличный документ пользователь получил возможность выбора из всех форматов, в которых доступна вставка содержимого буфера обмена.
Табличный документ.
Система компоновки данных.
Для табличного документа реализована возможность автоматической адаптации ширины колонок к ширине области отображения табличного документа: на экране или на листе бумаги при печати.

Для объектов ОбластьЯчеекТабличногоДокумента, ОформлениеЯчейкиТаблицыОбластиКомпоновкиДанных реализованы свойства РастягиватьПоГоризонтали, ВесовойКоэффициентШирины. Для объекта ОформлениеКомпоновкиДанных реализованы параметры оформления РастягиватьПоГоризонтали, ВесовойКоэффициентШирины.

Система компоновки данных выводит диаграмму в табличный документ отчет таким образом, чтобы ширина диаграммы автоматически подстраивалась под ширину области отображения.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Ширина колонок табличного документа не могла адаптироваться под ширину области отображения.

При выводе диаграммы в табличный документ, система компоновки данных устанавливала фиксированную ширину диаграммы.

Улучшены возможности по адаптации табличных документов к области отображения.
Табличный документ.
Для расширения поля управляемой формы для табличного документа:
  • Расширена возможность управления выделением ячеек: стало возможно полностью отключить отображение выделения, а также включить отображение выделения только в том случае, если в табличном документе выделено более одной ячейки (свойство Отображение выделения). Для системного перечисления РежимОтображенияВыделения реализованы свойства НеОтображать, ПриВыделенииНесколькихЯчеек, ПриВыделенииНесколькихЯчеекПриАктивности.
  • Расширены возможности по управлению видимостью полос прокрутки. Стало возможно указать использование полос прокрутки только при необходимости. Тип свойств ВертикальнаяПолосаПрокрутки и ГоризонтальнаяПолосаПрокрутки изменен на ИспользованиеПолосыПрокрутки.
  • Реализована возможность управления видом курсора мыши, который находится над расширением поля управляемой формы для табличного документа. Курсор мыши может иметь вид стандартного курсора, а может изменяться в зависимости от того, над какой областью табличного документа курсор находится. Реализовано свойство ТипКурсоров.
  • Реализована зависимость поведения клавиш управления курсором от свойства Отображение выделения. Когда данное свойство установлено в значение Не показывать, то клавиши управления курсором выполняют функцию прокрутки табличного документа в направлении стрелок. Когда свойство установлено в одно из значений При выделении нескольких ..., то при нажатой клавише Shift клавиши управления курсором изменяют размер выделения, а без нажатой клавиши Shift выполняют прокрутку табличного документа в направлении стрелок (без снятия выделения области). +
Для расширения поля управляемой формы для табличного документа было возможно:
  • Указывать, что выделение отображается всегда или только при активации поля.
  • Полосы прокрутки или всегда отображались или всегда скрывались. Отображение по необходимости было недоступно.
  • Курсор мыши, при нахождении над табличным документом, всегда зависел от содержимого ячейки, над которой он (курсор мыши) находился.
  • Поведение клавиш управления курсором не зависело от каких-либо свойств расширения поля управляемой формы для табличного документа.
Расширены возможности оформления табличного документа, отображаемого в управляемой форме.
В документации данное изменение описано здесь.
Управляемая форма.
Улучшен алгоритм автоматического определения ширины колонки таблицы управляемой формы в зависимости от параметров шрифта.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Алгоритм автоматического определения ширины колонки не всегда адекватно учитывал параметры шрифта.Улучшено отображение таблицы управляемой формы.
Выгрузка/загрузка конфигурации в файлы.
При загрузке справочной информации из файлов XML не выполняется проверка того факта, что в конфигурации существует язык (объект конфигурации Язык), для которого загружается справочная информация.При загрузке справочной информации из файлов XML не выполнялась загрузка справочной информации в том случае, если в конфигурации отсутствовал язык (объект конфигурации Язык), для которого загружалась справочная информация.Упрощена работа со справочной информацией на разных языках при выгрузке/загрузке конфигурации или внешних обработок/отчетов в файлы XML.
Средства разработки.
Расширение конфигурации.
Хранение информации о закладках, точках останова и данных о производительности для расширений конфигурации выполняется по именам расширений.Хранение информации о закладках, точках останова и данных о производительности для расширений конфигурации выполнялось по внутренним идентификаторам расширений.Обеспечивается возможность (в дальнейшем) интеграции отладки расширений с 1C:Enterprise Development Tools.
Работа в macOS.
Табличный документ.
Реализована возможность экспорта табличного документа в формате PDF при работе под управлением ОС macOS.Экспорт табличного документа в формате PDF при работе под управлением ОС macOS завершался с ошибкой.Устранено некорректное поведение системы.
Работа с ОС.
Изменен алгоритм определения часового пояса сеанса при работе под управлением ОС Windows. Часовой пояс определяется следующим образом:
  • Получается представление часового пояса с помощью методов API Windows.
  • Используя полученное представление, выполняется поиск идентификатора часового пояса в реестре Windows.
  • Найденный идентификатор используется для работы с библиотекой ICU.
  • Если часовой пояс определить не удалось - будет использован предыдущий алгоритм определения часового пояса.
При работе под управлением ОС Windows использовался следующий алгоритм для определения часовой пояс:
  • Выполнялось определение часового пояса по реестру Windows.
  • Найденный идентификатор используется для работы с библиотекой ICU.
  • Если для найденного идентификатора часового пояса не было соответствия в ICU, то получалась информация о часовом поясе с помощью API Windows.
  • Используя параметры часового пояса (смещение, летнее время и т.д.) выполняется подбор часового пояса в ICU.
Корректное определение часового пояса сеанса при работе на терминальных серверах ОС Windows.
Работа с СУБД.
При работе в режиме управляемых блокировок (в клиент-серверном варианте) на СУБД PostgreSQL версии 9.3 и старше, поддерживается установка времени ожидания блокировок. Время ожидания получается из параметров информационной базы, аналогично другим СУБД.При работе в режиме управляемых блокировок (в клиент-серверном варианте) на СУБД PostgreSQL версии 9.3 и старше, не поддерживалась установка времени ожидания блокировок. Установка времени ожидания блокировок при работе с этой СУБД поддерживалась только при работе в автоматическом режиме блокировок.При работе с СУБД PostgreSQL время ожидания блокировок в управляемом режиме управления блокировками стало управляться аналогично остальным СУБД.
Диаграммы.
Табличный документ.
При сохранении табличного документа с диаграммой в файл, цвет, автоматически выбранный системой для отображения серии или точки, а также автоматически выбранный маркер серии, записываются таким образом, чтобы обеспечить корректное отображение выбранного цвета и маркера при просмотре как в текущей, так и в предыдущих версиях системы «1С:Предприятие».При сохранении табличного документа с диаграммой в файл, значения автоматических цветов и маркеров сохранялись в виде, которых был «непонятен» для предыдущих версий системы «1С:Предприятие», в результате чего мог существенно нарушаться внешний вид диаграммы при просмотре в предыдущих версиях системы «1С:Предприятие».Табличные документы, которые содержат диаграммы, будут отображаться в предыдущих версиях системы «1С:Предприятие» максимально приближенно к тому виду, который они имеют в версии 8.3.10 и старше.
Работа с Интернет.
В файл cacert.pem (файл корневых сертификатов), поставляемый в составе платформы, добавлен корневой сертификат удостоверяющего центра DigiCert.В файле cacert.pem (файл корневых сертификатов), поставляемый в составе платформы, отсутствовал корневой сертификат удостоверяющего центра DigiCert.Системы на платформе «1С:Предприятие» смогут подключаться к сервисам фирмы «1С» после обновления инфраструктуры сервисов.
Внешние отчеты и обработки.
Реализована возможность отключать предупреждение системы защиты от опасных действий при создании объекта внешнего отчета или обработки в том случае, когда гарантировано известно, что в файле, используемом в качестве параметра метода, расположен доверенный код.

Для метода Создать() объектов ВнешниеОбработкиМенеджер и ВнешниеОтчетыМенеджер реализован параметр ЗащитаОтОпасныхДействий.

Данная возможность не предоставлялась.При подключении внешней обработки (или отчета) из файла стало возможно указать, что подключается доверенный код, для которого не требуется формировать предупреждение системы защиты от опасных действий.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Управляемая форма.
При сворачивании узла дерева значений с подчиненными, отображаемого в управляемой форме, событие ПередСворачиванием формируется для каждого сворачиваемого узла по всей иерархии.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При сворачивании узла дерева значений с подчинеными, отображаемого в управляемой форме, событие ПередСворачиванием формировалось только для элементов дерева верхнего уровня.Устранено некорректное поведение системы.

Стало возможно точно определять сворачиваемые элементы дерева значений при интерактивной работе.

В документации данное изменение описано здесь.
Права доступа.
При вызове метода ПравоДоступа() генерируется исключение, если проверяемое право доступа не может быть применено к объекту метаданных.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При вызове метода ПравоДоступа() всегда возвращалось значение Истина, если проверяемое право доступа не могло быть применено к объекту метаданных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Параметры схемы компоновки данных, тип которых содержит только те типы, которые отключены функциональными опциям, в доступных параметрах компоновки данных создаются с отключенной видимостью. В результате эти параметры не будут доступны для редактирования пользователем, однако по-прежнему будут доступны из встроенного языка. Кроме того, такие параметры не добавляются в список доступных полей – параметров.

При загрузке варианта отчета у параметров данных, которые отключены функциональными опциям, снимается флаг использования.

Метод КомпоновщикНастроекКомпоновкиДанных.Восстановить() отключает свойство Использование у параметров данных, которые отключены функциональными опциям.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Функциональные опции не оказывали влияния на видимость параметров компоновки данных.

При загрузке варианта отчета у параметров данных, которые отключены функциональными опциям, не снимался флаг использования.

Метод КомпоновщикНастроекКомпоновкиДанных.Восстановить() не изменял свойство Использование у параметров данных, которые отключены функциональными опциям.

Пользователям стало более удобно работать с параметрами отчета, которые имеют типы, отключенные функциональными опциями.
В документации данное изменение описано здесь.
Работа с HTML.
Для объекта ОболочкаHTMLДокумента реализовано свойство КодЯзыкаМакета. Если данное свойство установлено, то методы этого объекта ПолучитьCOMОбъект(), ПолучитьДокументHTML(), ПолучитьТекст() будут возвращать результат для указанного языка.Для HTML-макета выбор языка, для которого будут возвращаться результаты работы методов объекта ОболочкаHTMLДокумента, был недоступен.Стало возможно использовать HTML-макеты для языка, отличного от языка текущего сеанса.
Системные требования.
Изменено представление операционной системы Windows, начиная с версии Vista и далее, в свойстве СистемнаяИнформация.ВерсияОС. Текст свойства содержит пользовательское представление названия операционной системы в дополнение к технической информации (версия, номер сборки и т.д.),

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Представление операционной системы Windows, начиная с версии Vista и далее, в свойстве СистемнаяИнформация.ВерсияОС не содержало пользовательского представления названия операционной системы.Информация из свойства СистемнаяИнформация.ВерсияОС (при работе под управлением ОС Windows) предоставляет пользователю более понятную информацию об используемой операционной системе.
В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Работа с Интернет.
При вызове метода HTTPСоединение.ВызватьHTTPМетод() параметр HTTPМетод должен соответствовать RFC 7230 (см. здесь). Если требование не выполняется - будет сгенерировано исключение.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При вызове метода HTTPСоединение.ВызватьHTTPМетод() параметр HTTPМетод мог принимать любое значение.Поведение платформы «1С:Предприятие» более точно соответствует стандартам RFC.
В документации данное изменение описано здесь.
Работа с СУБД.
При работе в клиент-серверном варианте, с использованием СУБД Microsoft SQL Server, в результате запроса, содержащего выражение ВЫРАЗИТЬ(… КАК СТРОКА(…)), выполняется дополнение результата операции пробелами до требуемой длины.

В режиме совместимости с версией 8.3.9 поведение не изменилось. +

При работе в клиент-серверном варианте, с использованием СУБД Microsoft SQL Server, в результате запроса, содержащего выражение ВЫРАЗИТЬ(… КАК СТРОКА(…)), не выполнялось дополнение результата пробелами до требуемой длины.Поведение системы «1С:Предприятие» стало одинаковым на всех используемых СУБД.
Работа с XML, XDTO.
При сериализации объекта типа СписокЗначений с использованием метода ФабрикаXDTO.ЗаписатьXML() будет формироваться XML-документ, соответствующий схеме, которая используется при сериализации этого объекта с помощью метода СериализаторXDTO.ЗаписатьXML().

В результате изменения, список значений:

  • сериализованный в версии 8.3.10, не может быть прочитан в версии 8.3.6 и младше, но может быть прочитан в версиях 8.3.7 и старше с использованием ФабрикаXDTO;
  • сериализованный в версии 8.3.10, может быть прочитан в версии 8.3.6 и младше с использованием СериализаторXDTO;
  • сериализованный в версиях 8.3.7 - 8.3.9 может быть прочитан любой версией.
При сериализации объекта типа СписокЗначений с использованием метода ФабрикаXDTO.ЗаписатьXML() формировался XML-документ, не соответствующий схеме, которая используется при сериализации этого объекта с помощью метода СериализаторXDTO.ЗаписатьXML().Устранено некорректное поведение системы.
Управляемая форма.
Если в ячейке таблицы управляемой формы отображается гиперссылка и для ячейки установлен режим Только просмотр, то двойное нажатие левой кнопки мыши в такой ячейке вызовет однократную генерацию события таблицы Выбор.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Если в ячейке таблицы управляемой формы отображается гиперссылка и для ячейки установлен режим Только просмотр, то двойное нажатие левой кнопки мыши в такой ячейке вызывало генерацию двух событий таблицы Выбор.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства разработки.
Для подписок на события реализована проверка соответствия события и типа источника. Проверка выполняется перед сохранением конфигурации. В случае, если событие не соответствует типу источника - формируется ошибка и конфигурация не сохраняется.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для подписок на события проверка соответствия события и типа источника не выполнялась.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с запросами.
При анализе запроса формируется ошибка в том случае, если в выражении, следующем за именем временной таблицы, отсутствует имя поля.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При анализе запроса, в том случае, если в выражении, следующем за именем временной таблицы, отсутствует имя поля, в качестве имени поля использовалось имя первого поля временной таблицы.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
При отображении табличного документа в интерфейсе Такси, в качестве цвета текста Авто используется:
  • при отображении на экране: стилевой цвет текста редактирования;
  • при печати: черный цвет.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При отображении табличного документа в интерфейсе Такси, в качестве цвета текста Авто всегда использовался черный цвет.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Для реквизита типа Строка или Число, отображаемого полем ввода управляемой формы с включенным режимом выбора из списка:
  • снимаются ограничения на длину вводимой строки;
  • поле ввода, отображающее такие данные, будет автоматически растягиваться по ширине.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При редактировании значения типа Число в поле ввода управляемой формы в режиме выбора из списка, квалификаторы числа, настроенные для реквизита, продолжали влиять на формат редактируемого текста.Повышено удобство работы пользователей.
В документации данное изменение описано здесь.
Табличный документ.
При обработке шаблона в ячейке табличного документа, из результата не удаляется содержимое от последней секции [] и до экранированного символа [.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При отработке шаблона в ячейке табличного документа, в результат не попадает содержимое шаблона, расположенного между секцией [] и экранированным символом [.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с Интернет.
При работе под управлением ОС Windows, проверка сертификата веб-сервера выполняется по всем цепочкам доверенных сертификатов, зарегистрированных в хранилище доверенных сертификатов ОС Windows.При работе под управлением ОС Windows, проверка сертификата веб-сервера могла завершиться неудачей, если в хранилище доверенных сертификатов был не указан какой-либо из родительских доверенных сертификатов проверяемого сертификата.При работе под управлением ОС Windows исправлена ситуация, когда платформа «1С:Предприятие» некорректно выполняет проверку сертификата веб-сервера при работе по протоколу HTTPS/FTPS в случаях, когда издатель сертификата сервера не входит в список доверенных корневых сертификатов.
Полнотекстовый поиск.
Если при выполнении запроса полнотекстового поиска формируется много промежуточных результатов, но сам результат запроса содержит не более 1 млн. записей - пользователь получит этот результат. В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для включения данной возможности необходимо установить режим совместимости конфигурации в значение Не использовать и обновить индекс полнотекстового поиска.

В результатах полнотекстового поиска ближе к началу показываются те данные, изменения в которые вносились позже (в рамках одного объекта конфигурации, например, одного вида документа).

Если при выполнении запроса полнотекстового поиска формировалось много промежуточных результатов, то пользователь получал ошибку Слишком много результатов поиска.При поиске по нескольким словам, которые часто встречаются по отдельности, но не очень часто вместе - полнотекстовый поиск стал возвращать результат поиска.
Установка клиентского приложения.
Ускорен механизм поиска новых версий системы «1С:Предприятие» в каталогах расположения дистрибутивов при открытии окна списка информационных баз. Поиск выполняется по именам каталогов с дистрибутивами.

Определение типа дистрибутива и его разрядности выполняется по имени .msi-файла:

  • 1CEnterprise 8.msi - 32-разрядный вариант, полный дистрибутив;
  • 1CEnterprise 8 Thin client.msi - 32-разрядный вариант, тонкий клиент;
  • 1CEnterprise 8 (x86-64).msi - 64-разрядный вариант, полный дистрибутив;
  • 1CEnterprise 8 Thin client (x86-64).msi - 64-разрядный вариант, тонкий клиент.
Механизм поиска новых версий в каталогах дистрибутивов работал менее быстро, т.к. использовал информацию, расположенную в свойствах файлов .msi.Ускорено открытие диалога со списком информационных баз в том случае, если в настройках диалога указано Устанавливать автоматически новую версию.
Управляемая форма.
При попытке из встроенного языка создать группу управляемой формы с некорректным значением свойства Вид формируется исключение.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При попытке из встроенного языка создать группу управляемой формы с некорректным значением свойства Вид поведение системы было неопределено (включая возможность аварийного завершения работы).Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Реализована возможность устанавливать одновременно выражения для детальных и итоговых записей пользовательских полей системы компоновки данных. Аналогичная возможность реализована для представлений пользовательских полей в детальных и итоговых записях системы компоновки данных.

Для объекта ПользовательскоеПолеВыражениеКомпоновкиДанных реализованы методы УстановитьВыражения() и УстановитьПредставлениеВыражений().

Методы УстановитьВыражениеДетальныхЗаписей(), УстановитьВыражениеИтоговыхЗаписей(), УстановитьПредставлениеВыраженияДетальныхЗаписей() и УстановитьПредставлениеВыраженияИтоговыхЗаписей() являются устаревшими, поддерживаются для совместимости и не рекомендуются к использованию.

Установка выражений пользовательских полей системы компоновки данных для детальных и итоговых записей устанавливались различными методами. Так же различными методами выполнялась установка представлений пользовательских полей системы компоновки данных для детальных и итоговых записей.Устранено некорректное поведение системы.

Стало возможно редактировать пользовательское поле системы компоновки данных, в обоих выражениях которого используется удаленное или переименованное поле запроса.

Система компоновки данных.
При автоматическом заполнении доступных полей набора данных-запроса, для виртуальных таблиц регистров сведений, поля измерений становятся доступными для отбора через параметры виртуальной таблицы.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При автоматическом заполнении доступных полей набора данных-запроса, для виртуальных таблиц регистра сведений, поля измерений не становились доступными для отбора через параметры виртуальной таблицы.Повышена эффективность получения данных из регистров сведений с помощью системы компоновки данных в случае использования виртуальных таблиц регистров сведений.
В документации данное изменение описано здесь.
Работа с запросами.
В том случае, если условие отбора добавляется в запрос с помощью конструктора объекта ВыражениеСхемыЗапроса, выражение отбора добавляется без преобразований.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В том случае, если условие отбора добавлялось в запрос с помощью конструктора объекта ВыражениеСхемыЗапроса, выражение отбора добавлялось в некорректном виде.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Хранилище конфигурации.
Новое хранилище конфигурации создается в формате версии 8.3.8 со страницей, равной 8192 байта.

Преобразование хранилища между форматами 8.3.8 и 8.2.14 (в обе стороны) можно осуществить с помощью утилиты cnvdbfl.

База данных хранилища конфигурации создавалось в формате версии 8.2.14.Стало возможно для хранилища установить формат версии 8.3.8. За счет этого появляется возможность хранить историю хранилища большего размера.
В документации данное изменение описано здесь, здесь и здесь.
Регистры бухгалтерии.
Если значение ресурса регистра бухгалтерии связано с признаком учета плана счетов, то значение такого ресурса в виртуальных таблицах Остатки, Обороты, ОстаткиИОбороты и ОборотыДтКт зависит от состояния этого признака учета для каждого счета. Если признак учета установлен, то ресурс имеет значение типа Число, если признак учета сброшен - ресурс имеет значение NULL.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Виртуальные таблицы регистра бухгалтерии (Остатки, Обороты, ОстаткиИОбороты и ОборотыДтКт), могли возвращать значение не равное NULL в качестве значения ресурса регистра бухгалтерии, связанного с признаком учета, по счету, в котором этот признак учета был отключен.Устранено некорректное поведение системы.
Веб-клиент.
Клиентское приложение.
Интерфейс.
Управляемая форма.
Прикладные объекты.
Прекращена поддержка модальных окон при работе в веб-клиенте с использованием любого веб-браузера. В том случае, если в прикладном решении используется вызов модального метода - генерируется исключение.

При работе в тонком клиенте и веб-клиенте прекращена поддержка проведения документа с запросом режима проведения у пользователя. При использовании документов с таким режимом проведения будет генерироваться исключение. Значение системного перечисления ИспользованиеРежимаПроведения.Запрашивать не поддерживается для использования в тонком и веб-клиентах.

Игнорируется указание варианта открытия окна (параметр Окно) при использовании методов ОткрытьФорму(), ПолучитьФорму(), а также в значении свойства структуры ПараметрыВыполненияКоманды.Окно с помощью системного перечисления ВариантОткрытияОкна. В тонком клиенте параметр Окно игнорируется при отключенном режиме совместимости. Системное перечисление ВариантОткрытияОкна исключено из синтакс-помощника.

В тонком и веб-клиентах стало невозможно открыть форму в отдельном окне при работе в режиме интерфейса В закладках.

В веб-клиенте прекращена поддержка режима интерфейса В отдельных окнах. В тонком клиенте невозможно установить режим работы интерфейса В отдельных окнах с помощью диалога параметров клиентского приложения. Для веб-клиента прекращена поддержка параметра командной строки запуска веб-клиента isdi.

При запуске веб-клиента не анализируется наличие блокировки всплывающих окон.

Поддерживалась работа с блокирующими окнами в веб-клиенте.

Поддерживалась возможность указывать режим проведения документа интерактивно, непосредственно во время проведения документа.

При работе в режиме интерфейса В закладках было возможно открыть форму в отдельном окне при работе в тонком и веб-клиентах.

При работе в веб-клиенте поддерживалась работа с интерфейсом В отдельных окнах.

Отключена поддержка режима интерфейса, который не поддерживается современными веб-браузерами.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Интерфейс.
Отображение информации.
Для метода глобального контекста ПоказатьОповещениеПользователя() реализованы параметры СтатусОповещенияПользователя, КлючУникальности. Параметр метода НавигационнаяСсылка переименован в ДействиеПриНажатии. +Для оповещений со статусом Информация незначительно изменяется внешний вид. Для оповещений со статусом Важное переработан механизм оповещений пользователя при работе в интерфейсе Такси. Данный механизм позволяет:
  • отображать одновременно несколько оповещений;
  • отображать оповещения даже если основное окно приложения свернуто;
  • обновлять информацию в окне оповещения, пока это окно не закрыто пользователем;
  • реализовать реакцию системы при нажатии на окно оповещения.

Реализована возможность работы с оповещениями через центр оповещений. Возможность перетаскивания окна оповещения не поддерживается.

Особенности использования оповещений в зависимости от используемой операционной системы и клиентского приложения описаны в документации.

Данные возможности не предоставлялись.

Возможности метода глобального контекста ПоказатьОповещениеПользователя() были ограничены.

Реализована возможность использования оповещений со статусом Важное, которые отображаются всегда, даже, когда окно приложения неактивно.
В документации данное изменение описано здесь и здесь.
Диаграммы.
Табличный документ.
Реализована возможность выполнять расшифровку в диаграмме Ганта, которая расположена в табличном документе. Последовательность действий аналогична таковой в случае, если диаграмма Ганта расположена на управляемой форме.

Для обработчиков событий табличного документа ОбработкаРасшифровки и ОбработкаДополнительнойРасшифровки реализован параметр ДополнительныеПараметры. В данном параметре передается дата, на которой инициирована расшифровка. В режиме совместимости с версией 8.3.9 поведение не изменилось.

Контекстное меню диаграммы Ганта, расположенной в табличном документе, открывается при отпускании правой кнопки мыши. В режиме совместимости с версией 8.3.9 поведение не изменилось.

При попытке вызвать расшифровку диаграммы Ганта, расположенной в табличном документе, открывалось окно со списком расшифровок, в котором было невозможно выполнить никаких действий.

Обработчики событий табличного документа ОбработкаРасшифровки и ОбработкаДополнительнойРасшифровки содержат только два параметра (отсутствует параметр ДополнительныеПараметры).

Контекстное меню диаграммы Ганта, расположенной в табличном документе, открывалось при нажатии правой кнопки мыши.

Устранено некорректное поведение системы.

Поведение расшифровки диаграммы Ганта, расположенной в табличном документе, приведено к единому поведению, принятому в платформе в таких случаях.

В документации данное изменение описано здесь.
Диаграммы.
Если у диаграммы выключены флажки Настройка серий и Настройка точек, то в тонком клиенте цвета серий/точек берутся из установленной палитры. В веб-клиенте поведение не изменилось.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

+

Если у диаграммы выключены флажки Настройка серий и Настройка точек, то в тонком клиенте цвета серий/точек брались из палитры по умолчанию, а в веб-клиенте - из установленной палитры.Устранены различия в отображении диаграмм между тонким и веб-клиентами.
В документации данное изменение описано здесь.
Диаграммы.
При десериализации диаграммы, если свойства Настройка серий или Настройка точек установлены в значение Ложь, то установка цветов серий/точек выполняется после загрузки палитры цветов.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При десериализации диаграммы, если свойства Настройка серий или Настройка точек установлены в значение Ложь, то установка цветов серий/точек выполнялось из палитры по умолчанию.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Если при интерактивном редактировании диаграммы значение флажка Настройка серий или Настройка точек будет установлено в значение Ложь, то будут выполнены следующие операции:
  • оформительские параметры серий или точек будут установлены в значения по умолчанию;
  • диаграмма будет перерисована.

В режиме совместимости с версией 8.3.9 поведение не изменилось. +

При интерактивном редактировании диаграммы не выполнялась установка значений по умолчанию для оформительских параметров серий и точек, после того, как значение флажка Настройка серий или Настройка точек устанавливалось в значение Ложь.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Диаграммы.
Если у диаграммы установлены в значение Ложь свойства Настройка серий или Настройка точек, то попытка изменить какие-либо свойства серии или точки с помощью встроенного языка будет приводить к генерации исключения.

В режиме совместимости с версией 8.3.9 поведение не изменилось. +

Попытка изменить какие-либо свойства серии или точки, с помощью встроенного языка, не приводило к генерации исключения, если у диаграммы установлены в значение Ложь флажки Настройка серий или Настройка точек. В этом случае свойства устанавливались в серию или точку.Некорректное использование диаграммы стало невозможно.
В документации данное изменение описано здесь.
Общие объекты.
В таблице значений, полученной в результате использования метода Выгрузить() от табличной части какого-либо объекта, имена предопределенных колонок создаются на языке, указанном в свойстве конфигурации Вариант встроенного языка.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В таблице значений, полученной в результате использования метода Выгрузить() от табличной части какого-либо объекта, обращение к именам предопределенных колонок было доступно на следующих языках:
  • если получившаяся таблица значений не передавалась между клиентом и сервером - на русском и английском языках;
  • если получившаяся таблица значений передавалась между клиентом и сервером - только на английском языке.
Устранено некорректное поведение системы.
Фоновые и регламентные задания.
Общие реквизиты / Разделение данных.
При запуске фонового задания с указанным ключом уникальности, уникальность указанного ключа проверяется в рамках текущего набора установленных разделителей. В рамках уникального набора разделителей, по прежнему, имеется возможность запуска не более одного фонового задания с указанным ключом уникальности.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

При запуске фонового задания с указанным ключом уникальности, уникальность указанного ключа проверяется в рамках информационной базы, без учета значений разделителей.Стало возможно реализовать запуск фонового задания для каждой уникальной области данных. Данная возможность, например, реализовать какой-либо долговременный расчет, в рамках разделенной информационной базы и при этом такие расчеты, запущенные в разных областях, не будут конфликтовать из одинакового ключа уникальности.
В документации данное изменение описано здесь.
Управляемая форма.
Если в обработчике ПриОткрытии управляемой формы установить параметр Отказ в значение Истина, то после окончания выполнения обработчика форма будет выгружена из памяти, будут освобождены все связанные с ней ресурсы (временное хранилище, блокировки и т.д.) и перестанут работать установленные обработчики ожидания.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Если в обработчике ПриОткрытии управляемой формы установить параметр Отказ в значение Истина, то после окончания выполнения обработчика, в некоторых сценариях, форма могла не выгружаться из памяти. Как следствие, сохранялись все связанные с ней ресурсы (временное хранилище, блокировки и т.д.) и работали установленные обработчики ожидания.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь, здесь и здесь.
Управляемая форма.
Реализована возможность управлять сквозным выравниванием для групп управляемой формы (свойство Сквозное выравнивание), у которых свойство Объединенная группа установлено в значение Ложь.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Для групп управляемой формы, у которых свойство Объединенная группа установлено в значение Ложь, игнорировалось значение свойства группы Сквозное выравнивание.Устранено некорректное поведение системы.
Работа в ОС Linux.
Системные требования.
Изменены системные требования для платформы, работающей под управлением ОС Linux. Библиотека freetype включена в состав платформы и исключена из списка библиотек, наличие которых проверяется при запуске платформы.Библиотека freetype не входила в состав платформы и ее наличие проверялось при старте платформы.Упрощены требования к программному окружению при запуске системы под управлением ОС Linux.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
В том случае, если у группы колонок таблицы управляемой формы свойство ФиксацияВТаблице установлено в значение Лево или Право, то фиксируются все колонки такой группы, а также все прочие колонки и группы таблицы, для которых указана фиксация.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

В том случае, если у группы колонок таблицы управляемой формы свойство ФиксацияВТаблице установлено в значение Лево или Право, то фиксировались только те колонки, которые находились левее (для значения Лево) или правее (для значения Право) такой группы. Колонки, входящие в такую группу, не фиксировались.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Если для группы управляемой формы вида «командная панель» свойство ВертикальноеПоложениеВГруппе установлено в значение Авто, и эта командная панель расположена в группе или форме, для которой свойство ВертикальноеПоложениеПодчиненных установлено в значение Авто, то такая командная панель будет располагаться вверху родительской группы, ниже последнего элемента.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Если для группы управляемой формы вида «командная панель» свойство ВертикальноеПоложениеВГруппе установлено в значение Авто, и эта командная панель расположена в группе или форме, для которой свойство ВертикальноеПоложениеПодчиненных установлено в значение Авто, то такая командная панель располагалась внизу родительской группы.Устранено некорректное поведение системы.
Динамический список.
Если в строку поиска динамического списка ввести значение, которое можно интерпретировать как число в экспоненциальной форме, то такое значение не будет интерпретироваться как число, а будет интерпретировано как строка. Поиск будет выполняться для строки.

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Если в строку поиска динамического списка ввести значение, которое можно интерпретировать как число в экспоненциальной форме, то такое значение интерпретировалось как число. Поиск выполнялся для числа.Устранено некорректное поведение системы.
Система компоновки данных.
Отключается свойство Использование для параметров данных, которые отключены функциональными опциями и были доступны для редактирования пользователем в следующих случаях:
  • при загрузке варианта отчета;
  • при вызове метода КомпоновщикНастроекКомпоновкиДанных.Восстановить().

В режиме совместимости с версией 8.3.9 поведение не изменилось.

Отключалось свойство Использование для параметров данных, которые отключены функциональными опциями в следующих случаях:
  • при загрузке варианта отчета;
  • при вызове метода КомпоновщикНастроекКомпоновкиДанных.Восстановить().
Повышена совместимость с запросами для системы компоновки данных, созданных в предыдущих версиях платформы.
В документации данное изменение описано здесь и здесь.
Встроенный язык.
Веб-клиент.
При работе в веб-клиенте функция ТРег() работает для строк, состоящих из специальных символов, цифр и букв только латинского алфавита.

При работе в других клиентских приложениях и на сервере поведение не изменилось - функция ТРег() работает в соответствии с алгоритмом, определенным стандартом Unicode.

При работе в веб-клиенте функция ТРег() всегда возвращала исходную строку.Уточнено поведение функции ТРег().
Системные требования.
Администрирование.
В дистрибутивах системы «1С:Предприятие» для ОС Windows и macOS поставляется HASP Device Driver версии 7.63.В дистрибутивах системы «1С:Предприятие» для ОС Windows и macOS поставлялся HASP Device Driver версии 6.60 или 7.60.Дистрибутив системы «1С:Предприятие» содержит более актуальную и безопасную версию HASP Device Driver.
Прикладные объекты.
После выполнения реструктуризации плана видов расчета происходит изменение порядка строк в табличных частях предопределенных видов расчета.Порядок строк в табличных частях предопределенных видов расчета был другим.Изменился порядок строк табличных частях предопределенных планов расчетов. Если прикладные решения, в каком-либо виде, зависели от порядка строк, то следует исключить такую зависимость.
Внешние компоненты.
Системные требования.
В технологии создания внешних компонент реализована поддержка Web Extensions API для веб-браузера Mozilla Firefox. Рекомендуется выполнить сборку нового установочного пакета для веб-браузера Mozilla Firefox с использованием нового шаблонного проекта. После выполнения сборки, внешние компоненты продолжат работу в тех же версиях системы «1С:Предприятие», что и до повторной сборки.

Обновлен шаблонный проект, входящий в состав технологии внешних компонент (см. здесь).

Технология создания внешних компонент не поддерживала Web Extensions API для веб-браузера Mozilla Firefox.Технология создания внешних компонент адаптирована под новые требования веб-браузера Mozilla Firefox. Начиная с 57 версии этого веб-браузера не поддерживается работа внешних компонент, которые для взаимодействия с веб-браузером используют интерфейсы, отличные от Web Extensions API.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Английское наименование метода СтрНачинаетсяС(). Старое наименование поддерживается для совместимости.
  • StrStartWith().
  • StrStartsWith().
Методы загрузки таблицы стилей XSL объекта ПреобразованиеXSL.

Старые наименования поддерживаются для совместимости.

  • ЗагрузитьИзСтроки(),
  • ЗагрузитьИзУзла(),
  • ЗагрузитьИзФайла(). +
  • ЗагрузитьТаблицуСтилейXSLИзСтроки(),
  • ЗагрузитьТаблицуСтилейXSLИзУзла(),
  • ЗагрузитьТаблицуСтилейXSLИзФайла().
Имена предметов отладки, используемые в файловом варианте информационной базы.
  • Для Web-сервиса: Сервер (файловый вариант);
  • Для HTTP-сервиса: Сервер (файловый вариант). +
  • Для Web-сервиса: Web-сервис;
  • Для HTTP-сервиса: HTTP-сервис.

+

+
Заголовки диалога настройки панели разделов.
  • Доступные разделы;
  • Выбранные команды.
  • Доступные разделы: (добавлен завершающий символ «:»);
  • Выбранные разделы.

+

+
Изменено представление команд меню табличного документа, управляющих отображением именованных областей.
  • Отображение именованных строк/колонок;
  • Отображать именованные ячейки.
  • Отображать имена строк/колонок;
  • Отображать имена ячеек.
Представления значений режима совместимости хранилища конфигурации.
  • Версия 8.3.2;
  • Версия 8.3.3.
  • Версии 8.3.2 и ниже;
  • Версии 8.3.3 - 8.3.5.
Английский вариант наименования свойства ПользовательИнформационнойБазы.ЗащитаОтОпасныхДействий. Старое наименование поддерживается для совместимости.
  • UnsafeActionProtection.
  • UnsafeOperationProtection.
Английский вариант наименования объекта ОписаниеЗащитыОтОпасныхДействий. Старое наименование поддерживается для совместимости.
  • UnsafeActionProtectionDescription.
  • UnsafeOperationProtectionDescription.
Английский вариант наименования свойства ОписаниеЗащитыОтОпасныхДействий.ПредупреждатьОбОпасныхДействиях. Старое наименование поддерживается для совместимости.
  • WarnAboutUnsafeActions.
  • UnsafeOperationWarnings.
Изменено имя системного перечисления, позволяющего управлять высотой таблицы управляемой формы. Старое наименование поддерживается для совместимости.
  • ВариантУправленияВысотой.
  • ВариантУправленияВысотойЭлемента.

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Специальные возможности мобильного устройства.
Для работы со средствами геопозиционирования реализованы следующие возможности:
  • выбирать из всех провайдеров геопозиционирования или только доступных в данный момент;
  • проверять включено или нет определение местоположения;
  • работать с геозонами.

Реализован объект Геозона. Реализовано системное перечисление ПоложениеОтносительноГеозоны. Реализовано свойство ИнформацияПровайдераГеопозиционирования.Доступен. Реализован параметр ТолькоДоступных для следующих методов объекта СредстваГеопозиционирования: ПолучитьПровайдеров(), ПолучитьПровайдера(), ПолучитьСамогоТочногоПровайдера(), ПолучитьСамогоЭнергоЭкономичногоПровайдера(). Для объекта СредстваГеопозиционирования реализованы методы: ИспользованиеДанныхГеопозиционированияВключено(), ПодключитьОбработчикИзмененияДоступностиПровайдеров(), ОтключитьОбработчикИзмененияДоступностиПровайдеров(), ВключитьОтслеживаниеГеозон(), ПолучитьОтслеживаемыеГеозоны(), ПолучитьОтслеживаемуюГеозону(), ОтключитьОтслеживаниеГеозон(), ОтключитьОтслеживаниеВсехГеозон(), ПодключитьОбработчикПересеченияГраницОтслеживаемыхГеозон().

Данные возможности не предоставлялись.Расширены возможности работы со средствами геопозиционирования. В частности, стало возможно выполнять какие-либо действия при попадании мобильного устройства в заранее указанное место.
Двоичные данные.
В мобильной платформе реализованы средства работы с двоичными данными.Данная возможность не предоставлялась. Работа с двоичными данными была доступна только в платформе для персонального компьютера.В мобильной платформе стали доступны средства для работы с двоичными данными.
Работа с Интернет.
Реализована возможность определять, что мобильное устройство работает в роуминге. Обработчик изменения интернет-соединения вызывается, в том числе, при изменении состояния роуминга.

Реализован метод ИнформацияОбИнтернетСоединении.ПолучитьИспользованиеРоуминга().

Возможность определения работы в роуминге была недоступна.Стало возможно обнаружить и реализовать реакцию на то, что мобильное устройство находится в роуминге. В частности, ограничить или прекратить использование мобильного интернета, стоимость которого в роуминге может быть очень высокой.
В документации данное изменение описано здесь.
Работа с Интернет.
Для мобильной платформы, работающей под управлением ОС Windows, реализованы возможности работы с защищенным соединением.Возможности работы с защищенным соединением были недоступны для мобильной платформы, работающей под управлением ОС Windows.При работе под управлением ОС Windows стало возможно выполнять соединение с ресурсами, требующими защищенного соединения.
Работа с криптографией.
В мобильной платформе реализован механизм работы с криптографией. Поведение мобильной платформы аналогично поведению тонкого клиента. Особенности поведения механизма отражены в документации.

Реализован метод МенеджерКриптографии.ПоказатьСписокСертификатов(). Реализован объект КонтейнерКлючейКриптографии. В мобильной платформе изменено поведение следующих методов объекта ХранилищеСертификатовКриптографии: Добавить(), Удалить(), НачатьДобавление(), НачатьУдаление().

В мобильной платформе не поддерживался механизм работы с криптографией.При использовании мобильной платформы стало возможно обеспечить проверку, что тот или иной документ, хранящийся в системе, не был изменен. Стало возможно обеспечить передачу какой-либо подписанной информации или организовать утверждение какого-либо документа в рамках системы, а также обеспечить передачу информации по открытым каналам так, чтобы с ней было невозможно ознакомиться, перехватив передачу (зашифровать данные).
Специальные возможности мобильного устройства.
В мобильной платформе реализована проверка возможности выполнять изменение и добавление контактов и календарей.

Для объекта МенеджерКонтактов реализованы методы ПоддерживаетсяИзменениеКонтакта() и ПоддерживаетсяДобавлениеКонтактов().

Для объекта МенеджерКалендарей реализованы методы ПоддерживаетсяИзменениеКалендаря() и ПоддерживаетсяДобавлениеКалендаирей().

Свойство МенеджерКалендарей.ПоддерживаетсяИзменениеКалендарей не поддерживается и оставлено для совместимости.

При работе под управлением ОС Windows метод МенеджерКалендарей.ПоддерживаетсяИзменениеСобытий() всегда возвращает значение Ложь.

Не поддерживалась проверка возможности изменения и добавления контактов.

Проверка возможности изменения и добавления календарей выполнялась другим образом.

Унифицирована работа с контактами и календарями в части проверки возможности добавления и изменения объектов.
Специальные возможности мобильного устройства.
Реализовано разрешение конфигурации Реклама. Разрешение используется только сборщиком мобильных приложений для выбора соответствующей версии мобильной платформы для ОС iOS, которая будет использована при сборке. Если в файле выгрузки конфигурации используется разрешение Реклама, то в форме мобильной конфигурации сборщика мобильных приложений недоступен флажок Приложение использует рекламу.У конфигурации отсутствовало разрешение, позволяющее указать, что мобильное приложение использует рекламу. Для такого указания использовался флажок Приложение использует рекламу в сборщике мобильных приложений.Стало возможным указывать сборщику мобильных приложений, что для сборки следует использовать особую версию мобильной платформы для iOS (с включенной рекламой).
В документации данное изменение описано здесь.
Работа с файлами.
В мобильной платформе реализована возможность получения картинки представления (уменьшенный вариант изображения для предварительного просмотра) для картинки и видео-файла, расположенных в соответствующих библиотеках мобильного устройства. Для выполнения этой операции путь к файлу должен начинаться со схемы content:.

Для объекта Файл реализованы методы ПолучитьКартинкуПредставленияФайлаБиблиотекиМобильногоУстройства() и НачатьПолучениеКартинкиПредставленияФайлаБиблиотекиМобильногоУстройства().

Данная возможность не предоставлялась.

Можно было загрузить картинку или видео-файл в целиком в оперативную память, несмотря на то, что картинка для предварительного просмотра может быть существенно уменьшена.

Оптимизировано использование памяти мобильного устройства при работе с картинками и видео-файлами из соответствующих библиотек мобильного устройства. Снижена вероятность получения ошибки нехватки памяти при работе с мобильным приложением, которое активно использует картинки или видео-файлы из библиотек мобильного устройства.
В документации данное изменение описано здесь.
Управляемые блокировки.
Реализована работа с управляемыми блокировками в мобильной платформе.

Реализованы методы глобального контекста ЗаблокироватьДанныеДляРедактирования(), РазблокироватьДанныеДляРедактирования(), УстановитьВремяОжиданияБлокировкиДанных(), ПолучитьВремяОжиданияБлокировкиДанных().

Реализованы методы Заблокирован(), Заблокировать() и Разблокировать() для объектов СправочникОбъект, ДокументОбъект, ПланОбменаОбъект.

Реализован метод РегистрНакопленияНаборЗаписей.БлокироватьДляИзменения().

Реализован метод УправляемаяФорма.ЗаблокироватьДанныеФормыДляРедактирования().

Реализованы объекты БлокировкаДанных, ЭлементБлокировкиДанных.

Для элементов конфигурации Документ, Справочник, ПланОбмена реализовано свойство ПоляБлокировкиДанных. Для элементов конфигурации Конфигурация, Документ, Справочник, ПланОбмена, Константа, Последовательность, РегистрНакопления, РегистрСведений реализовано свойство РежимУправленияБлокировкойДанных.

Управляемые блокировки не поддерживались в мобильной платформе.Стало возможно управлять блокировками объектов при работе фоновых заданий в мобильной платформе.
В документации данное изменение описано здесь.
Работа с файлами.
Реализована возможность получения файловой маски, описывающей все файлы, а также символа разделителя частей пути, вне зависимости от мобильной операционной системы, под управлением которой работает мобильная платформа «1С:Предприятие».

Реализованы методы ПолучитьМаскуВсеФайлы(), ПолучитьМаскуВсеФайлыКлиента(), ПолучитьМаскуВсеФайлыСервера(), ПолучитьРазделительПути(), ПолучитьРазделительПутиКлиента(), ПолучитьРазделительПутиСервера().

Реализован метод НачатьПолучениеКаталогаБиблиотекиМобильногоУстройства().

Отсутствовала возможность получить маску, описывающую все файлы и символ разделителя пути, вне зависимости от используемой мобильной операционной системы.

+

В мобильном приложении стало возможно реализовать работу с файлами, которая минимально зависит от используемой мобильной операционной системы.
В документации данное изменение описано здесь.
Системные требования.
Реализована поддержка ОС Android 7.0. Реализована поддержка многооконного режима при работе под управлением ОС Android 7.0.

При работе под управлением ОС Android 6.0 и старше:

  • используется новый программный интерфейс для работы с камерой мобильного устройства;
  • реализована работа с динамическими разрешениями.
Не поддерживался многооконный режим при работе под управлением ОС Android 7.0. Под управлением ОС Android 6.0 и старше, не поддерживалась работа с динамическими разрешениями. Не поддерживалось динамическое управление разрешениями при работе под управлением ОС Android 6.0 и старше.Улучшена поддержка операционной системы Android версии 6.0 и старше.
Специальные возможности мобильного устройства.
Реализована поддержка сканирования штрихкодов на мобильных устройствах, работающих под управлением ОС Windows 10. Сканирование штрихкодов на мобильных устройствах, работающих под управлением ОС Windows 8.1 и младше не поддерживается.

При работе под управлением ОС Windows 10 реализована доступность метода СредстваМультимедиа.ПоказатьСканированиеШтрихКодов(), метод СредстваМультимедиа.ПоддерживаетсяСканированиеШтрихКодов() возвращает реальную возможность сканирования штрихкодов.

Для работы сканирования необходимо, чтобы устройство поддерживало для основной камеры режим непрерывного авто-фокуса.

На мобильных устройствах, работающих под управлением ОС Windows, не поддерживалось сканирование штрихкодов.Расширены возможности мобильной платформы при работе на устройствах под управлением ОС Windows 10.
В документации данное изменение описано здесь.
Управляемая форма.
В мобильной платформе реализовано расширение поля формы для поля календаря. Расширение поля формы для поля календаря не поддерживает перетаскивание.Данная возможность не предоставлялась.Расширены возможности форм мобильной платформы по работе с данными типа Дата.
Средства печати.
При работе под управлением операционной системы Windows Phone 8.1 (архитектуры ARM и x86) и старше, а также сенсорных устройств под управление операционной системы Windows 8.1 (архитектуры x86 и x86-64) и старше, реализована поддержка печати на мобильном устройстве.При работе под управлением операционной системы Windows Phone 8.1 (архитектуры ARM и x86) и старше, а также сенсорных устройств под управление операционной системы Windows 8.1 (архитектуры x86 и x86-64) и старше, не поддерживалась печать на мобильном устройстве.Расширены возможности мобильного приложения при работе под управлением ОС Windows.
Мобильное приложение.
Реализована поддержка аппаратной отрисовки пользовательского интерфейса при работе под управлением ОС Android.Данная возможность не предоставлялась.Ускорена формирование пользовательского интерфейса мобильного приложения при работе под управлением ОС Android.
Сборщик мобильных приложений.
В сборщике мобильных приложений реализована возможность автоматической очистки информационной базы от «устаревших» данных. Под «устаревшими» понимаются собранные мобильные приложения и мобильные платформы, последнее изменение (или загрузка) которых выполнялась ранее определенной даты. Дата определяется как текущая дата минус указанное количество дней (размер «окна»). Для собранных мобильных приложений и мобильных платформ имеется возможность указать различные размеры «окна». Значения по умолчанию:
  • 90 дней для собранных мобильных приложений;
  • 180 дней для файлов мобильных платформ.

Если размер «окна» установлен в 0 - очистки «устаревших» объектов не происходит.

Если пользователь попробует воспользоваться «устаревшим» объектом, то ему будет предложено или пересобрать мобильное приложение или заново загрузить мобильную платформу.

В сборщике мобильных приложений не существовало инструментов по автоматической очистке «устаревших» объектов.Стало возможно поддерживать размер информационной базы сборщика мобильных приложений на комфортном уровне, не допуская того, чтобы эта база занимала существенный размер на диске.
Сборщик мобильных приложений.
Требования к версиям компонент Android SDK, используемым для сборки мобильных приложений, работающих под управлением ОС Android, определяются требованиями мобильной платформы, которую используют для сборки.

Для сборки будет использоваться Android API Level максимально доступной (на компьютере сборщика) версии, но не ниже, чем требует мобильная платформа. Требования к версиям остальных компонентов Android SDK определяются требованиями Android API Level.

Если мобильная платформа была загружена в предыдущих версиях сборщика, для сборки будет требоваться Android API Level не ниже 24 версии.

Для сборки мобильного приложения под управлением ОС Android, требовались следующие версии компонентов Android SDK:
  • Android API Level - 23 и выше;
  • Android Tools - 20.0.3 и выше;
  • Android Platform Tools - 14 и выше;
  • Android Build Tools - 19.0.0 и выше.

Указанные версии не зависели от используемых при сборке мобильного приложения версий мобильных платформ и были явно указаны в коде сборщика мобильных приложений. +

Требования к инфраструктуре сборки мобильного приложения для работы под управлением ОС Android определяются используемой мобильной платформой, а не теми требованиями, которые указаны в исходном коде сборщика мобильных приложений.
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
Для сборщика мобильных приложений реализована возможность собирать мобильные приложения с использованием технологии Gradle. Использование Android SDK версии 26 и старше позволяет собирать мобильные приложения только с использованием технологии Gradle.

В настройках сборщика предоставляется возможность одновременно указать путь к Android SDK версии 25 или младше и версии 26 или старше. Таким образом появляется возможность собирать мобильные приложения, требующие любую версию Android SDK.

Для сборки с использованием технологии Gradle требуется Java 8, установленная на компьютере, который выполняет процесс сборки.

Для сборки мобильных приложений с использованием технологии Gradle не требуется установка программного пакета Apache Ant.

Сборщик мобильных приложений не поддерживал сборку мобильных приложений с использованием технологии Gradle.Стало возможно выполнять сборку мобильных приложений, использующих новые версии Android SDK.
Мобильное приложение.
Начиная с мобильной платформы версии 8.3.10.71 сборка мобильных приложений возможна только с использованием технологии Gradle. Сборку мобильных приложений необходимо выполнять с помощью сборщика мобильных приложений, идущего в комплекте с мобильной платформой.

Программный пакет Apache Ant более не требуется для сборки мобильных приложений при использовании мобильной платформы версии 8.3.10.71 и старше.

Мобильная платформа версии младше 8.3.10.71 не использовала технологию Gradle и собиралась с применением Apache Ant.Технология сборки мобильных приложений адаптирована к изменению рекомендованного процесса сборки мобильных приложений для ОС Android.
Системные требования.
Сборщик мобильных приложений.
Реализована поддержка работы под управлением ОС iOS 11.

Расширен состав графической информации для мобильных приложений, работающих под управлением ОС iOS.

В сборщике мобильных приложений реализована поддержка нового набора графической информации и возможность сборки для работы под управлением ОС iOS 11.

Мобильная платформа не поддерживала работу в ОС iOS 11.Реализована поддержка актуальной версии операционной системы для мобильных устройств фирмы Apple.
Обработка ошибок.
Если при работе мобильного приложения под управлением ОС Android произошло аварийное завершение работы, то перед окончательным закрытием приложения пользователю отображается диалог, содержащий подробную информацию об ошибке (с возможностью скопировать текст в буфер обмена).Если при работе мобильного приложения под управлением ОС Android происходило аварийное завершение работы, то пользователь не получал никакой информации о причинах такого завершения.Упрощена диагностика причин аварийного завершения, т.к. теперь пользователь может отправить разработчикам информацию связанную с аварийным завершением работы мобильного приложения.
Интерфейс.
Мобильная платформа.
В табличном документе, отображаемом на мобильном устройстве, реализована поддержка права Вывод. Если право Вывод отключено - не поддерживается копирование в буфер обмена, печать и запись отображаемой информации.В табличном документе, отображаемом на мобильном устройстве, игнорировалось право Вывод. Копирование в буфер обмена, печать и запись отображаемой информации были доступны всегда.Устранено некорректное поведение системы.

Оглавление

Обновление используемых библиотек

Оглавление

Переход с предыдущей версии на версию 8.3.10

Оглавление

Версия 8.3.9

Версия 8.3.9 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v839doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.8. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, 8.3.6 и 8.3.7. +Возможность запуска конфигураций, разработанных в версии 8.3.8 и более младших, в версии 8.3.9, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.9 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.9, при необходимости, использовать для работы с информационной базой и версию 8.3.8. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Расширение конфигурации.
Встроенный язык.
В расширении конфигурации реализована возможность заимствования следующих объектов:
  • общих модулей;
  • модулей объектов для всех типов объектов;
  • модулей менеджеров для всех типов объектов;
  • модуля сеанса;
  • модуля управляемого приложения;
  • модуля внешнего соединения;
  • модулей команд.

Не поддерживается возможность заимствования модулей обычных форм и модуля обычного приложения. Таким образом, поддерживается возможность заимствования для всех модулей, кроме тех, которые используются только в обычном приложении.

Реализована возможность:

  • вызывать любые методы расширяемого модуля из расширяющего модуля;
  • добавлять обработчики событий в вышеперечисленных заимствованных модулях.

Экспортируемые методы и переменные расширяемого модуля формируют единый контекст расширяемого модуля.

Изменена схема работы с заимствованным модулем формы.

Предоставляется способ разрешить или запретить расширение либо всех вышеуказанных модулей (свойство профиля безопасности к расширению всех модулей), либо установить список модулей, для которых разрешено (свойство профиля безопасности Доступные для расширения модули) или запрещено расширение (свойство профиля безопасности Недоступные для расширения модули).

В расширении конфигурации реализована возможность создавать общие модули.

Для объекта ISecurityProfile реализованы свойства AllModulesExtension, ModulesAvailableForExtension, ModulesNotAvailableForExtension (технология программного администрирования кластера серверов с помощью COM-объектов).

Для интерфейса ISecurityProfile реализованы методы getAllModulesExtension(), setAllModulesExtension(), getModulesAvailableForExtension(), setModulesAvailableForExtension(), getModulesNotAvailableForExtension(), setModulesNotAvailableForExtension() (интерфейс работы с сервером администрирования из языка Java).

Для утилиты командной строки (rac) кластера серверов реализованы параметры all-modules-extension, modules-available-for-extension и modules-not-available-for-extension команды profile.

Отсутствовала возможность заимствования любых модулей, кроме модуля формы. Отсутствовала возможность создавать в расширении конфигурации общие модули.

Схема работы с заимствованным модулем формы была другой.

Управление возможностью расширения модулей было недоступно.

С помощью механизма расширения конфигурации стало возможно расширять работу всех модулей встроенного языка, кроме тех, которые используются только в обычном приложении.

Расширены возможности профилей безопасности для поддержки работы с расширениями конфигурации.

В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Web-сервисы и HTTP-сервисы.
Интерфейс OData.
Расширение конфигурации.
Кластер серверов.
Реализована возможность управлять временем жизни сеансов при использовании Интернет-сервисов и стандартного интерфейса OData:
  • Повторное использование текущего сеанса при исполнении запроса от имени одного и того же пользователя (выполняется автоматически);
  • Управление временем жизни сеанса с помощью заголовка HTTP-запроса.

Для Web-сервиса и HTTP-сервиса реализованы свойства ПовторноеИспользованиеСеансов и ВремяЖизниСеанса. Данные свойства недоступны для редактирования, если Web-сервис и HTTP-сервис являются собственными объектами расширения.

В файле default.vrd реализовано:

  • элемент <standardOData>, подчиненный элементу <point>.
  • атрибуты reuseSessions, sessionMaxAge, poolTimeout, poolSize для элементов <point>, <service>.

Атрибут enableStandardOData элемента <point> является устаревшим и не рекомендуется к использованию. +Если Web-сервис или HTTP-сервис является собственным объектом расширения, не опубликован в файле default.vrd или опубликован без указания на повторное использование сеанса, то повторное использование сеанса не используется при работе с этим Web-сервисом или HTTP-сервисом.

Реализован сервис кластера серверов, обеспечивающий работу автоматического пула повторно используемых сеансов. Сервис называется SessionReuseService (Сервис повторного использования сеансов).

Данная возможность не предоставлялась.

Сеанс создавался для каждого вызова Интернет-сервиса или одного запроса стандартного интерфейса OData.

Повышена производительность работы с Интернет-сервисами и стандартным интерфейсом OData.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Форматированный документ.
Изменено поведение при нажатии кнопки Tab:
  • нажатие кнопки увеличивает отступ текста, если имеется выделенный текст или курсор стоит в начале параграфа.
  • во всех остальных случаях добавляется символ горизонтальной табуляции.

Объект ЗакладкаФорматированногоДокумента имеет внутреннюю привязку не к позиции символа внутри параграфа, а к самому символу. При изменении текста, закладка более точно соответствует начальному положению.

При нажатии кнопки Tab всегда выполнялось увеличение отступа текста. Объект ЗакладкаФорматированногоДокумента имел внутреннюю привязку к позиции символа внутри параграфа.Поведение форматированного документа стало лучше соответствовать ожиданиям пользователя.
В документации данное изменение описано здесь.
Двоичные данные.
Реализованы средства работы с двоичными данными. Предоставляются следующие возможности:
  • Указание порядка следования байтов;
  • Работа с буфером двоичных данных в памяти;
  • Работа с файлами, как с двоичными данными;
  • Побайтовый доступ к двоичным данным;
  • Возможность считывать/записывать некоторые типы данных (строка, число).

Реализованы объекты БуферДвоичныхДанных, Поток, ФайловыйПоток, ПотокВПамяти, ЧтениеДанных, ЗаписьДанных, РезультатЧтенияДанных, МенеджерФайловыхПотоков. +Реализована доступность метода ДвоичныеДанные.Размер() на веб-клиенте.

Для метода ДвоичныеДанные.Записать() реализована возможность записывать данные в поток.

Реализован метод ДвоичныеДанные.ОткрытьПотокДляЧтения() открывающий поток для чтения двоичных данных, установленных для объекта ДвоичныеДанные.

Данные возможности не предоставлялись.

Предоставлялись возможности только чтения с диска и записи на диск произвольных файлов без выполнения каких-либо манипуляций с ними.

Расширены возможности системы для работы с двоичными данными.
В документации данное изменение описано здесь.
Картинки.
Реализована поддержка векторных картинок в формате SVG. Реализовано значение системного перечисления ФорматКартинки.SVG. Редактор картинок в конфигураторе не поддерживает редактирование картинок в формате SVG. Особенности поддержки формата SVG приведены в документации. Данная возможность не предоставлялась.Расширен список поддерживаемых форматов картинок. Стало возможно использование масштабируемых картинок, отображение которых не зависит от размера области, в которой отображается масштабируемая картинка.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Средства администрирования.
При запуске клиентского приложения с ключом /regserver (регистрация COM-объектов) реализованы необязательные параметры командной строки:
  • -AllUsers - выполняется регистрация для всех пользователей на данном компьютере.
  • -CurrentUser - выполняется регистрация для текущего пользователя.
  • -Auto - режим регистрации выбирается автоматически, в зависимости от наличия привилегий. Никаких интерактивных вопросов не формируется.

Если ключ /regserver используется без параметров - поведение не изменилось. +

При запуске клиентского приложения с ключом /regserver (регистрация COM-объектов) выполнялась попытка регистрации для всех пользователей, если обнаруживалась нехватка привилегий - пользователю задавался интерактивный вопрос о необходимости выполнить регистрацию для текущего пользователя.Упрощено использование ключа /regserver в пакетных режимах запуска системы «1С:Предприятие».
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Реализована поддержка спецификации Canonical XML 1.1.

Реализован объект ПреобразованиеККаноническомуXML. Для системного перечисления ТипКаноническогоXML реализованы значения КаноническийXML1_1, КаноническийXML1_1СКомментариями.

Объекты КаноническаяЗаписьXML, КаноническийDOM признаны устаревшими и не рекомендуются к применению. Данные объекты не поддерживают спецификацию Canonical XML 1.1.

Поддерживалась работа только со спецификацией Canonical XML 1.0.Расширены возможности по взаимодействию с различными внешними системами.
Работа с СУБД.
Средства администрирования.
Реализована возможность выполнения попытки восстановления структуры базы данных из командной строки пакетного режима запуска конфигуратора. Реализован параметр командной строки запуска конфигуратора /IBRestoreIntegrity.

Запуск конфигуратора с параметром /IBRestoreIntegrity рекомендуется, если предыдущее обновление конфигурации базы данных (в пакетном режиме или интерактивно) не выполнено до конца, например, из-за аварийного завершения работы конфигуратора или выключения компьютера.

Данная возможность не предоставлялась.Повышена устойчивость информационной базы к различным сбоям, которые могут происходить во время обновления конфигурации базы данных.
В документации данное изменение описано здесь.
Предопределенные данные.
Журнал регистрации.
Реализовано журналирование (в журнале регистрации) событий, возникающих в процессе работы с предопределенными данными:
  • Информационная база.Установка обновления предопределенных данных;
  • Информационная база.Обновление предопределенных данных;
  • Данные.Установка инициализации предопределенных данных;
  • Данные.Инициализация предопределенных данных;
  • Данные.Добавление предопределенных данных;
  • Данные.Изменение предопределенных данных;
  • Данные.Удаление предопределенных данных;
  • Данные.Инициализация предопределенных данных, данные не найдены.

+

Данная возможность не предоставлялась.Упрощена диагностика проблемных ситуаций при работе с предопределенными данными.
В документации данное изменение описано здесь.
Табличный документ.
При экспорте табличного документа в формат Microsoft Office OpenXML (Microsoft Word 2007- 2010) реализована выгрузка картинок в ячейках табличного документа.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При экспорте табличного документа в формат Microsoft Office OpenXML (Microsoft Word 2007- 2010) выгрузка картинок в ячейках табличного документа не выполнялась.Табличный документ, выгруженный в формате Microsoft Word, стал лучше соответствовать оригинальному табличному документу.
В документации данное изменение описано здесь.
Работа с Интернет.
При использовании протокола TLS реализована поддержка следующих алгоритмов: ГОСТ Р 34.10-2001, ГОСТ Р 34.10-94, ГОСТ Р 34.11-94, ГОСТ 28147-89.

Алгоритмы ГОСТ Р 34.10-2012 и ГОСТ Р 34.11-2012 не поддерживаются.

Данная возможность не предоставлялась.Стало возможно использовать интернет-сервисы, которые для работы по протоколу TLS используют алгоритмы ГОСТ.
В документации данное изменение описано здесь и здесь.
Интерфейс OData.
Для стандартного интерфейса OData реализована возможность получения:
  • Признака предопределенного и имени предопределенных данных.
  • Представления реквизита данных. Для получения представления используется суффикс имени поля ____Presentation. Поля представлений можно использовать только в операторе $select путем явного указания такого поля.
  • Конкретного реквизита табличной части или набора записей в операторе $select .
Данные возможности не предоставлялись.Расширены возможности стандартного интерфейса OData.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Интерфейс OData.
В запросах к стандартному интерфейсу OData реализована возможность использовать оператор $expand, позволяющий включать в тело ответа сущности, связанные с запрашиваемыми сущностями.Данная возможность не предоставлялась.Реализована возможность вместе с результатами основного запроса получать значения связанных сущностей, что позволяет не запрашивать каждую связанную сущность отдельно.
В документации данное изменение описано здесь и здесь.
Динамический список.
В конструкторе запросов динамического списка:
  • реализована возможность редактировать пакетный запрос (страница конструктора Пакет запросов).
  • не поддерживается установка количества выбираемых записей, но поддерживается отключение этой возможности запроса.
  • при закрытии конструктор запроса диагностирует наличие ключевого слова ПЕРВЫЕ и сообщается об этом.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

В конструкторе запросов динамического списка было невозможно редактировать пакетный запрос, была доступна возможность установки количества выбираемых записей без какой-либо диагностики этого факта.Реализована возможность редактирования пакетных запросов с помощью конструктора запросов динамического списка. Расширена диагностика ошибочных запросов динамического списка.
Расширение конфигурации.
Реализована возможность изменять права доступа (включая ограничения доступа к данным) в заимствованных ролях.

Реализована возможность создания собственных ролей в расширении конфигурации. Роли расширения могут быть назначены пользователю только с помощью встроенного языка. В конфигураторе доступно только удаление всех ролей расширения, назначенных пользователю.

Реализована возможность ограничения использования прав доступа, которые созданы в расширении конфигурации, в результирующей конфигурации с помощью профиля безопасности (свойство к расширению прав доступа).

Для объекта ISecurityProfile реализованы свойства RightExtension, RightExtensionDefinitionRoles (технология программного администрирования кластера серверов с помощью COM-объектов).

Для интерфейса ISecurityProfile реализованы методы RightExtension, RightExtensionDefinitionRoles (интерфейс работы с сервером администрирования из языка Java).

Для утилиты командной строки (rac) кластера серверов реализованы параметры right-extension и right-extension-definition-roles команды profile.

В расширении конфигурации имелась возможность устанавливать права доступа в заимствованных ролях только для собственных объектов расширения. Изменять права в заимствованных ролях было невозможно.В расширениях конфигурации получили существенное развитие возможности по управлению правами доступа.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Расширение конфигурации.
Средства разработки.
Реализована возможность проверить применимость расширения конфигурации до реального запуска прикладного решения с этим расширением:
  • С помощью команды Проверка возможности применения в окне Расширения конфигурации.
  • С помощью встроенного языка.
  • С помощью пакетного режима запуска конфигуратора.

При запуске клиентского приложения информация о проблемах совместимости более не выводится в окно сообщений, а добавляется в список информации для технической поддержки (открываемого из окна О программе). Также при обнаружении ошибок подключения выводится единственный диалог, из которого можно получить доступ к полному списку проблем совместимости расширения.

Для объекта РасширенияКонфигурации реализованы методы ПроверитьВозможностьПримененияВсех(), ПолучитьИнформациюОПроблемахПримененияВСеансе(). Для объекта РасширениеКонфигурации реализован метод ПроверитьВозможностьПрименения().

Для пакетного режима запуска конфигуратора реализован ключ командной строки /CheckCanApplyConfigurationExtensions.

Для стандартной функции Управление расширениями конфигурации реализован флажок Проверять применимость при добавлении и загрузке расширений.

Данные возможности не предоставлялись.

При подключении расширения диагностика выводилась в окно сообщений.

Улучшены возможности диагностики проблем подключения расширения к прикладному решению. Появилась возможность выполнять такие проверки в пакетном режиме запуска конфигурации (с целью автоматизации проверок).
В документации данное изменение описано здесь, здесь и здесь.
Журнал регистрации.
Реализована выгрузка состояния обновления предопределенных данных в качестве значения поля Данные события журнала регистрации, в том случае, когда журнал регистрации выгружается в формат XML.

Реализована доступность системного перечисления ОбновлениеПредопределенныхДанных на тонком и веб-клиентах.

Данная возможность не предоставлялась.Выгрузка журнала регистрации в формате XML приведена в соответствие с новыми событиями журнала регистрации. +
Локализация.
Реализована локализация интерфейса клиентского приложения для французского языка.Данная возможность не предоставлялась.Стало возможно использование системы «1С:Предприятие» франкоговорящими пользователями.
В документации данное изменение описано здесь.
Локализация.
Реализована локализация интерфейса клиентского приложения для венгерского языка.Данная возможность не предоставлялась.Реализован интерфейс платформы на венгерском языке. Стало возможным использование системы «1С:Предприятие» с венгерским интерфейсом.
В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Средства разработки.
Реализован метод МенеджерРасширенийКонфигурации.ВыполнитьФоновоеЗаданиеБезРасширений(), который позволяет выполнить фоновое задание без применения расширений, т.е. в сеансе запущенного фонового задания установленные в базе данных расширения конфигурации не будут действовать.

Для всех объектов метаданных реализован метод ЕстьИзмененияРасширениямиКонфигурации(), который позволяет определить, что объект конфигурации расширен в данном сеансе.

Данная возможность не предоставлялась.Упрощена работа с расширениями конфигурации из встроенного языка.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Работа с запросами.
В документации к системе, в описании функции ДОБАВИТЬКДАТЕ() системы компоновки данных и языка запросов уточнено, что под термином «декада» понимается ровно 10 дней, вне зависимости от месяца.В документации к системе отсутствовала информация о том, каким образом трактуется термин «декада» в функции ДОБАВИТЬКДАТЕ() системы компоновки данных и языка запросов.Улучшена документация к системе.
В документации данное изменение описано здесь и здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Microsoft SQL Server 2016 (в том числе версия для работы под управлением ОС Linux).СУБД Microsoft SQL Server 2016 не поддерживалась.Реализована поддержка СУБД Microsoft SQL Server 2016.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Клиентское приложение.
Системные требования.
Для ОС Windows реализовано 64-разрядное клиентское приложение: тонкий клиент (включая отдельный дистрибутив), толстый клиент, конфигуратор. 64-разрядное клиентское приложение находится в статусе бета-версии.

При запуске клиентского приложения приоритетной считается 32-разрядная версия, что позволит уменьшить количество проблем, связанных с тем, что внешние компоненты (в основном) отсутствуют для 64-разрядной версии платформы. При автоматической установке новой версии также будет устанавливаться 32-разрядная версия (если таковая присутствует в каталоге дистрибутивов).

Программа установки 64-разрядной системы не отличается от таковой для 32-разрядной системы.

Не рекомендуется одновременно устанавливать 64-разрядный сервер «1С:Предприятия» и приложения из 64-разрядного полного дистрибутива системы «1С:Предприятие».

Для ОС Windows существовали только 32-разрядные версии клиентских приложений (включая конфигуратор).

В 64-разрядной версии существовал только сервер системы «1С:Предприятие».

Реализована поддержка 64-разрядных операционных систем Windows. При работе с большими конфигурациями устранена проблема нехватки памяти для таких операций, как сравнение и объединение и т.д..
Регистры бухгалтерии.
Работа с базой данных.
Перед выполнением операции тестирования и исправления реализовано предупреждение о необходимости создания резервной копии информационной базы (при запуске в интерактивном режиме).

При выполнении реструктуризации информационной базы или операции тестирования и исправления информационной базы реализована проверка и исправление ситуации, когда в таблице значений субконто регистра бухгалтерии присутствуют записи, для которых нет соответствующих записей в основной таблице регистра бухгалтерии (потерянные субконто). При исправлении выполняется удаление потерянных субконто из таблицы значений субконто регистра бухгалтерии. Удаление потерянных субконто выполняется только при выполнении следующих условий:

  • выбран режим Тестирование и исправление;
  • выбран режим Проверка логической целостности информационной базы.

При реструктуризации проверка выполняется в следующих случаях:

  • Изменен признак разделения итогов;
  • Изменен состав регистраторов;
  • Изменено максимальное количество субконто;
  • Изменен тип значения характеристики плана видов характеристик, использующегося для указания видов субконто плана счетов.

Если при реструктуризации обнаруживаются потерянные субконто - процесс реструктуризации прерывается с предложением выполнить тестирование и исправление информационной базы.

Также реализована проверка того, что операция тестирования и исправления информационной базы не привела к возникновению потерянных субконто. Если такой случай обнаруживается, то рекомендуется восстановить информационную базу из резервной копии. Проверка выполняется в следующих случаях:

  • выбран режим Тестирование и исправление;
  • выбраны следующие режимы: Проверка логической целостности информационной базы, Проверка ссылочной целостности информационной базы, Пересчет итогов, Реструктуризация таблиц информационной базы.
Проблемы с нарушением хранения субконто недостаточно полно диагностировались системой.Реализована диагностика и исправление возможных ошибок в логической целостности регистра бухгалтерии, которые могут приводить к потере данных.
Средства администрирования.
Изменено наименование приложений (и ярлыков) размещаемых в стартовом меню ОС Windows. Общая схема формирования имени выглядит следующим образом: Имя приложения (полный номер версии).

В ОС Windows 8 и старше, в папке 1С Предприятие 8 будут присутствовать все установленные приложения (и ярлыки), различающиеся номером версии.

В ОС Windows 7 и младше, в папке 1С Предприятие 8 будут присутствовать папки с полным номером версии, а в этой папке все установленные приложения (и ярлыки) данной версии, сформированные по указанным выше правилам.

В именах установленных приложения (и ярлыков) не присутствовал полный номер версии системы.Упрощена навигация в стартовом меню для пользователей операционных систем Windows версии 8 и старше. Название приложения содержит полный номер версии.
Регистры бухгалтерии.
Реализована возможность создать такое движение по регистру бухгалтерии, которое оказывает влияние только на входящие остатки одного периода и не влияет на исходящие остатки смежного, более младшего, периода. Для этого введено понятие «уточнение периода». Уточнение периода представляет собой числовое значение, которое указывает, на сколько дополнительных интервалов следует разбить одну секунду. Секунда может быть разбита максимум на 1 000 интервалов. При указании движения в любом из уточнений периода, такое движение не будет учитываться в исходящих остатках одного периода, но будет учитываться во входящих остатках следующего, смежного, периода, не искажая обороты каждого из двух смежных периодов. Движения, сделанные в уточнениях периода, будут отражаться в оборотах в том случае, если период анализа целиком захватывает момент времени, в который выполнялись движения с указанием уточнения периода. Уточнение периода логически расположено между периодом и регистратором.

Для объекта конфигурации, описывающего регистр бухгалтерии, реализовано свойство Длина уточнения периода. Уточнение периода отсутствует, если значение этого свойства равно 0.

Реализовано свойство УточнениеПериода для объектов РегистрБухгалтерииЗапись, РегистрБухгалтерииВыборка. Данное свойство также доступно в основной таблице регистра бухгалтерии, таблице субконто и виртуальной таблице движений с субконто.

Для параметра Периодичность виртуальных таблиц запросов регистра бухгалтерии Обороты, ОборотыДтКт, ОстаткиИОбороты реализовано значение УточнениеПериода.

Реализован объект МоментВремениСУточнениемПериода.

Изменена версия выгрузки файлов в формат XML.

При наличии в конфигурации хотя-бы одного регистра бухгалтерии с включенным уточнением периода (значение свойства Длина уточнения периода отлично от 0), информационная база становится несовместимой c предыдущими версиями системы «1С:Предприятие» (в том числе и с более младшими версиями системы «1С:Предприятие» версии 8.3.9). При попытке открыть такую информационную базу с помощью системы «1С:Предприятие» версии 8.3.9.2015 и младше, будет выдано сообщение об ошибке Структура конфигурации несовместима с текущей версией программы без возможности продолжить работу.

Для того чтобы сделать информационную базу пригодной для работы с предыдущим версиями системы «1С:Предприятие», необходимо удалить все регистры бухгалтерии с уточнением периода или установить для таких регистров значение Длина уточнения периода в значение 0.

Данная возможность не предоставлялась.

Было невозможно создать такое движение по регистру бухгалтерии, которое оказывало влияние только на входящие остатки одного периода и не влияло на исходящие остатки смежного, более младшего, периода.

Стало возможно вводить в прикладных решениях некоторые операции, связанные с корректировкой входящих остатков на границах периодов.
В документации данное изменение описано здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД Oracle Database версии 11.2.0.4 (Windows).Данная версия СУБД Oracle Database не поддерживалась.Расширен список поддерживаемых версий СУБД Oracle Database.
В документации данное изменение описано здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Для любой общей формы отчета используется следующий приоритет при отображении справочной информации:
  • справка отчета;
  • справка формы;
  • справка формы отчета платформы.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Для общей формы отчета использовался следующий приоритет при отображении справочной информации:
  • справка формы;
  • справка отчета;
  • справка формы отчета платформы.

+

Обеспечивается более логичный порядок отображения справочной информации.
Интерфейс.
Клиентское приложение.
Для тонкого клиента, работающего под управлением ОС Windows, реализована поддержка управления с помощью сенсорного экрана.

Реализована поддержка прокрутки двумя пальцами для всех элементов управления, содержащих полосы прокрутки, во всех направлениях.

Жесты одним пальцем зависят от используемого элемента формы:

  • горизонтальный жест:
    • Прокрутка в табличном документе, таблице и форме.
    • Выделение в текстовом документе, многострочном поле ввода, форматированном документе, планировщике и поле HTML-документа.
    • Выделение или перетаскивание в графической и географической схемах.
  • вертикальный жест:
    • Выделение или перетаскивание в географической схеме.
    • Прокрутка во всех остальных элементах формы, поддерживающих вертикальную прокрутку.

Увеличена область нажатия при касании экрана для:

  • Флажков в таблице формы;
  • Значков открытия/закрытия узлов дерева в таблице формы;
  • Значков перехода по иерархическому списку в таблице формы;
  • Гиперссылок в командной панели;
  • Кнопок без отображения контура;
  • Ячеек в расширении поля ввода для периода.

Реализовано масштабирование в графической схеме при помощи жеста масштабирования.

Реализовано визуальное подтверждение нажатия для кнопки формы и кнопки командной панели при нажатии на них пальцем.

Работа с сенсорными экранами поддерживалась в ограниченно объеме.Повышена комфортность использования системы «1С:Предприятие» в случае использования сенсорных мониторов.
Табличный документ.
В табличном документе, при поиске числовых значений анализируется разрядность введенного числа, в том случае, если успешно выполнено преобразование к числу введенной строки поиска. В дальнейшем выполняется поиск именно указанного числа, без дополнительных упрощений и преобразований. Строки с ведущими нулями не игнорируются в процессе поиска.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При поиске числовых значений в табличном документе не выполнялся анализ разрядности введенного числа, при наличии ведущих нулей не выполнялась попытка преобразования введенной строки в число..Улучшен алгоритм поиска числовых данных в табличном документе.
Веб-клиент.
Восстановлена работоспособность расширений работы с файлами и криптографией при использовании веб-браузера Mozilla Firefox версии 51 и старше. При первом обращении к соответствующему расширению (после обновления платформы) будет автоматически выполнено обновление расширения.Расширения работы с файлами и криптографией были не работоспособны при использовании веб-браузера Mozilla Firefox версии 51 и старше.Устранено незапланированное поведение системы.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Средства разработки.
В конфигураторе ускорено исполнение следующих команд:
  • Проверка модулей;
  • Проверка конфигурации.
Проверка модулей и проверка конфигурации выполнялись недостаточно быстро.Повышена комфортность работы разработчика при работе с большими прикладными решениями.
Встроенный язык.
Незначительно ускорено выполнение кода на встроенном языке в тонком и толстом клиентском приложении.Код на встроенном языке в клиентском приложении выполнялся недостаточно быстро.Ускорено выполнение кода на встроенном языке в тонком и толстом клиентском приложении.
Общие объекты.
Ускорено изменение значения в ячейке таблицы значений, если колонка, в которой расположена модифицируемая ячейка, не является частью какого-либо индекса таблицы значений.Выполнялось избыточное перестроение индексов таблицы значений в том случае, если модифицировалась ячейка в колонке, которая не являлась частью какого-либо индекса таблицы значений.Повышена производительность при массовых изменениях значений в колонке, не являющиейся частью какого-либо индекса таблицы значений.
Обмен данными.
Кластер серверов.
Оптимизирована операция чтения наборов записей регистров накопления, сведений и расчета (без поддержки периода действия) при формировании начального образа информационной базы в клиент-серверном варианте.

Существенно уменьшено время создания начального образа информационной базы в клиент-серверном варианте.

Создание начального образа информационной базы в клиент-серверном варианте выполнялось недостаточно быстро.Ускорена подготовка информационной базы для нового узла распределенной информационной базы.
Командный интерфейс.
Средства разработки.
Ускорено открытие формы редактирования командного интерфейса конфигурации.Открытие формы редактирования командного интерфейса конфигурации выполнялась недостаточно быстро.Редактирование командного интерфейса конфигурации стало более комфортным.
Работа с СУБД.
Кластер серверов.
Изменен алгоритм работы кластера серверов «1С:Предприятия» с СУБД PostgreSQL. В результате снижено потребление памяти собственно СУБД PostgreSQL.

Соединение кластера серверов «1С:Предприятия» с СУБД PostgreSQL освобождается через 30 минут неиспользования.

Алгоритм работы кластера серверов «1С:Предприятия» с СУБД PostgreSQL приводил к повышенному расходу памяти собственно СУБД PostgreSQL.

Кластер серверов «1С:Предприятия» не освобождал неиспользуемые соединения с СУБД PostgreSQL.

Уменьшено использование памяти СУБД PostgreSQL при работе с кластером серверов «1С:Предприятия».
Средства разработки.
Оптимизирован процесс обновления конфигурации информационной базы, а также сравнение конфигураций в режиме установки соответствия объектов по именам.Процесс обновления конфигурации информационной базы выполнялся недостаточно быстро.Ускорено обновление конфигурации.
Работа с СУБД.
Оптимизирована работа с временными таблицами при работе с СУБД PostgreSQL.Работа с временными таблицами при работе с СУБД PostgreSQL выполнялась недостаточно эффективно.Ускорена работа в многопользовательском режиме при использовании СУБД PostgreSQL.
Web-сервисы и HTTP-сервисы.
Оптимизирована передача больших файлов (десятки и сотни мегабайт) при использовании HTTP-сервиса.При использовании HTTP-сервиса недостаточно быстро выполнялась передача больших файлов (десятки и сотни мегабайт).Ускорена работа с HTTP-сервисами при использовании больших файлов.
Работа с СУБД.
Оптимизирована работа с временными таблицами Microsoft SQL Server в сценариях высоконагруженной работы «1С:Предприятия» и активного использования временных таблиц. Исключены случаи временных задержек при закрытии соединений с СУБД.Работа с временными таблицами Microsoft SQL Server в сценариях высоконагруженной работы «1С:Предприятия» и активного использования временных таблиц выполнялась недостаточно эффективно.Ускорена работа в многопользовательском режиме при использовании СУБД Microsoft SQL Server.
Работа с СУБД.
Оптимизированы запросы в файловом варианте работы платформы, в том случае, если прикладное решение имеет разделители, но фактически содержит одну область данных.

Для того чтобы данная оптимизация начала использоваться на существующих информационных базах, требуется произвести тестирование и исправление информационной базы с включенным режимом Реиндексация таблиц информационной базы.

После реструктуризации информационной базы, для всех реструктуризируемых объектов также начинает работать данная оптимизация.

Запросы в файловом варианте работы платформы, в том случае, если прикладное решение имеет разделители, но фактически содержит одну область данных, выполнялись недостаточно оптимально.Ускорена работа файлового варианта информационной базы в случае использования прикладного решения с разделителем данных, но фактически содержащего одну область данных.
Средства разработки.
Командный интерфейс.
Уменьшено время реакции системы на отображение изменений объектов конфигурации, влияющих на командный интерфейс конфигурации. При изменении таких свойств изменяется отображение только активного редактора формы. Остальные редакторы форм обновляются по мере активизации.При изменении объектов конфигурации, влияющих на командный интерфейс конфигурации, осуществлялось обновление всех открытых редакторов форм.Ускорена работа конфигуратора при изменении свойств объектов конфигурации, влияющих на построение командного интерфейса.
Форматированный документ.
Ускорена работа форматированного документа.Форматированный документ работал недостаточно быстро.Ускорена работа с текстами большого размера.
Управляемые блокировки.
Реализована возможность поглощения управляемых блокировок. Блокировка, в которой указаны значения не всех пространств блокировки, поглотит блокировку, в которой указаны значения для большего количества пространств блокировки, при условии, что совпадают значения по совпадающим пространствам блокировок.

Если при эскалации блокировки возникает конфликт с уже наложенными блокировками, то эскалация не выполняется, а производится попытка установить запрошенную блокировку. В этом случае возможна ситуация, когда в системе будет существовать более 100 000 блокировок на одно пространство.

В случае, если используется транзакция с большим количеством управляемых блокировок, которые отличаются, например, значением одного измерения, рекомендуется вместо большого количества блокировок установить одну управляемую блокировку, для которой не будет установлено значение отличающегося измерения.

Поглощение управляемых блокировок не выполнялось.

Если при эскалации блокировки возникал конфликт с уже наложенными блокировками, то транзакция, которая пыталась эскалировать блокировку, отменялась.

Уменьшено количество реально устанавливаемых блокировок, снижен объем оперативной памяти, используемой менеджером кластера.

Повышена стабильность работы системы при большом количестве одновременно установленных блокировок.

В документации данное изменение описано здесь.
Работа с СУБД.
Регистры расчета.
При удалении записей фактического периода действия, запись набора записей регистра расчета с поддержкой периода действия выполняется несколькими запросами, что значительно снижает вероятность эскалации блокировки до уровня таблицы. При этом время выполнения записи набора записей не увеличивается.При удаление записей фактического периода действия, запись набора записей регистра расчета с поддержкой периода действия выполнялась одним запросом, что могло приводить к эскалации блокировки до уровня таблицы.Снижена вероятность возникновения табличной блокировки, что ведет к повышению параллельности работы системы.
Регистры расчета.
Для таблицы фактического периода действия регистра расчета индекс дополнен полями дата начала и дата окончания, индекс сделан кластерным. Это снижает вероятность эскалации блокировок на уровень таблицы при записи наборов записей регистров расчета с поддержкой периода действия.

Для таблицы порядковых номеров вытеснения видов расчета плана видов расчета с поддержкой периода действия реализован неуникальный индекс по номеру вытеснения. Это приведет к тому, что при использовании информационной базы в разделенном режиме, при одновременном редактировании плана видов расчета в разных областях данных не будет возникать ожидание снятия блокировки.

Для того чтобы данная оптимизация начала использоваться на существующих информационных базах, требуется произвести тестирование и исправление информационной базы с включенным режимом Реструктуризация таблиц информационной базы.

Для таблицы фактического периода действия регистра расчета в индексе отсутствовали поля даты начала и даты окончания, индекс не являлся кластерным.

Для таблицы порядковых номеров вытеснения видов расчета плана видов расчета с поддержкой периода действия отсутствовал неуникальный индекс по номеру вытеснения.

Повышена производительность работы регистра расчета при работе на больших и разделенных базах данных.

При работе на больших базах данных и в особенности при работе в разделенных базах данных уменьшено количество блокировок уровня таблицы для таблиц с вторичными данными: фактического периода действия регистра расчета и номеров вытеснения плана видов расчета.

+

Управляемая форма.
Средства разработки.
Ускорено первое открытие редактора управляемой формы в конфигураторе.Первое открытие управляемой формы в редакторе конфигуратора занимало продолжительное время.Уменьшено время ожидания при разработке управляемых форм.
Регистры сведений.
Ускорено выполнение записи наборов записей регистров сведений, для которых включено использование среза первых или среза последних.

Ускорено выполнение методов СрезПервых() и СрезПоследних() менеджера регистра сведений.

Запись наборов записей регистров сведений, для которых включено использование среза первых или среза последних, а также выполнение методов СрезПервых() и СрезПоследних() менеджера регистра сведений, выполнялись недостаточно быстро.Ускорена работа с регистрами сведений, для которых включено использование срезов первых или последних.
Интерфейс.
Управляемая форма.
Функциональные опции.
Ускорена работа методов ОбновитьИнтерфейс(), УстановитьПараметрыФункциональныхОпцийИнтерфейса(), УстановитьПараметрыФункциональныхОпцийФормы(). При многопользовательской работе в прикладном решении, использующем данные методы, ликвидированы задержки в работе интерфейса.Методы ОбновитьИнтерфейс(), УстановитьПараметрыФункциональныхОпцийИнтерфейса(), УстановитьПараметрыФункциональныхОпцийФормы() работали недостаточно быстро. При многопользовательской работе в прикладном решении, использующем данные методы, наблюдались задержки в работе интерфейса.Работа с прикладным решением, в котором используются функциональные опции, стала более комфортной и плавной.
Мобильное приложение.
В мобильной платформе ускорена работа табличного документа, отображающего большой объем данных.В мобильной платформе табличный документ, отображающий большой объем данных, работал недостаточно быстро.Ускорена работа с большими табличными документами на мобильных устройствах.
Работа с СУБД.
Исключено замедление работы СУБД Microsoft SQL Server 2014 при работе с сервером «1С:Предприятия». Для указанной СУБД сервер «1С:Предприятия» выполняет принудительную установку TRACE FLAG 4199 для каждого соединения с СУБД. В связи с этим в настройках соединения сервера «1С:Предприятие» с СУБД необходимо указывать пользователя, обладающего административными правами.

Сервер «1С:Предприятие» не будет выполнять установку TRACE FLAG 4199 в том случае, если этот TRACE FLAG уже установлен для всей базы данных.

В некоторых сценариях работы наблюдалось замедление работы СУБД Microsoft SQL Server 2014 при работе с сервером «1С:Предприятия». Сервер «1С:Предприятия» не выполнял принудительную установку TRACE FLAG 4199 и не проверял его установку для всей базы данных.В ряде случаев повышается скорость работы с СУБД Microsoft SQL Server 2014.
В документации данное изменение описано здесь.
Работа с СУБД.
При работе с СУБД PostgreSQL уменьшены накладные расходы на обслуживание временных таблиц.При работе с СУБД PostgreSQL на обслуживание временных таблиц тратилось большее количество времени.При работе с СУБД PostgreSQL ускорена работа при использовании транзакций с активным использованием временных таблиц.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Работа с Интернет.
Реализована возможность использования протокола FTPES при работе с FTP-сервером. Для конструктора объекта FTPСоединение реализован параметр УровеньИспользованияЗащищенногоСоединения, позволяющий управлять требованиями к FTP-серверу с точки зрения защищенного соединения.

Если параметры конструктора FTPСоединение не соответствуют требуемым типам - генерируется исключение. В режиме совместимости с версией 8.3.8 поведение не изменилось.

При работе с FTP-сервером поддерживалась работа только по протоколу FTPS.

Если параметры конструктора FTPСоединение не соответствовали требуемым типам - выполнялась попытка приведения параметров к нужным типам.

Расширены возможности работы с FTP-серверами при организации защищенного соединения.
Управляемая форма.
При нажатии левой кнопки мыши на ячейке таблицы управляемой формы, отображающей картинку с включенным режимом гиперссылки (свойство ГиперссылкаЯчейки установлено в значение Истина), у таблицы формы вызывается обработчик события Выбор.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При нажатии левой кнопки мыши на ячейке таблицы, отображающей картинку с включенным режимом гиперссылки(свойство ГиперссылкаЯчейки установлено в значение Истина), у таблицы формы не вызывался обработчик события Выбор.Устранено некорректное поведение системы.

Унифицировано поведение системы для разных видов объектов, отображаемых таблицей формы.

Средства печати.
При печати реализована возможность использовать настройки двусторонней печати, указанные у используемого принтера. Реализовано значение системного перечисления ТипДвустороннейПечати.ИспользоватьНастройкиПринтера.

Свойство ДвусторонняяПечать для табличного документа, графической схемы, пакета отображаемых документов, текстового документа по умолчанию содержит значение:

  • НеИспользовать - в режиме совместимости с версией 8.3.8.
  • ИспользоватьНастройкиПринтера - для отключенного режима совместимости и в режиме совместимости с версией 8.2.16 и ниже.

При печати табличного документа или пакета отображаемых документов из веб-клиента с использованием PDF и при сохранении табличного документа в PDF, используются свойства ДвусторонняяПечать и ЧередованиеРасположенияСтраниц для указания соответствующих свойств документа PDF. Если программа просмотра PDF поддерживает эти свойства, то печать такого документа будет выполняться с их учетом. Если программа просмотра не поддерживает эти свойства документа, то для двусторонней печати нужно использовать настройки самой программы печати или настройки принтера.

Настройки двусторонней печати, установленные на принтере, игнорировались при печати табличного документа, графической схемы, пакета отображаемых документов, текстового документа.Улучшены возможности печати документов системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При открытии конструктора схемы компоновки данных реализовано удаление поля набора данных, если поле с таким именем уже есть среди полей набора.При открытии конструктора схемы компоновки данных не выполнялось удаление дублирующегося поля набора данных.Устранено некорректное поведение системы.
Технологический журнал.
Реализовано журналирование исключительных ситуаций, возникающих в процессе запуска сервера отладки (dbgs), в технологическом журнале. Журналирование выполняется с помощью события <EXCP>.Журналирование исключительных ситуаций, возникающих при запуске сервера отладки (dbgs), не выполнялось.Улучшена диагностика проблемных ситуаций, возникающих при запуске сервера отладки (dbgs).
Предопределенные данные.
Средства разработки.
В случае если объединение конфигураций должно привести к возникновению нескольких предопределенных элементов с одинаковым именем, элементу из неприоритетного источника присваивается новое имя путем добавления числового суффикса.При объединении конфигураций допускалась ситуация, когда в результате объединения возникало несколько предопределенных элементов с одинаковыми именами.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Встроенный язык.
Для метода СтрШаблон() реализован специальный синтаксис указания маркера подстановки: %(N). Допускается указание номера подстановки в скобках, следующих сразу за символом процента. В результате стало возможным указывать число сразу после маркера подстановки в строке с шаблоном.Данная возможность не предоставлялась.Стало возможно оформлять шаблонные строки в тех случаях, когда сразу за маркером подстановки следует цифровой символ.
Средства разработки.
При выполнении проверки конфигурации и выполнении процедур рефакторинга, при поиске нерекомендуемых синхронных методов, не анализируются модули, которые не могут исполняться на стороне клиентского приложения, в прочих модулях исключаются клиентские участки кода, выделенные инструкциями препроцессора и директивами компиляции.Проверка конфигурации и процедуры рефакторинга, при поиске нерекомендуемых синхронных методов, игнорировали контекст исполнения модулей и методов.Снижено количество ложных срабатываний при выполнении проверки конфигурации и использовании механизмов рефакторинга, при поиске нерекомендуемых синхронных методов.
В документации данное изменение описано здесь и здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
В том случае, если попытка публикации на веб-сервер выполняется не от имени пользователя с административными правами:
  • В конфигураторе открывается диалог с предупреждением и возможностью продолжить операцию или отказаться от публикации.
  • При использовании утилиты webinst выполнение не прерывается, но выводится предупреждение о возможных проблемах.
В том случае, если попытка публикации на веб-сервер выполняется не от имени пользователя с административными правами, никакой диагностики не осуществлялось.Улучшена диагностика при публикации на веб-сервере.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
При удалении пакета XDTO выполняется проверка того, что пакет используется в Web-сервисах. Если удаляемый пакет используется в каких-либо Web-сервисах, то формируется предупреждение со списком этих Web-сервисов.При удалении пакета XDTO не выполнялась проверка использования пакета в Web-сервисах.Исключены ситуации, когда из-за удаленного XDTO-пакета, работа Web-сервиса становилась невозможной.
Управляемая форма.
Реализована возможность установки фокуса на командные панели, которые не содержат команд элементов формы или содержат команды от более чем одного источника команд, при помощи навигации по форме клавишами Tab/Shift+Tab.

В календаре поля ввода реализован выбор текущей даты при нажатии на гиперссылку Сегодня.

В тонком и толстом клиентах в календаре поля ввода выбор даты не из текущего месяца приводит к помещению указанной даты в поле ввода (выбор даты).

С помощью клавиш Tab/Shift+Tab было невозможно установить фокус ввода на на командные панели, которые не содержат команд элементов формы или содержат команды от более чем одного источника команд.

В календаре поля ввода при нажатии на гиперссылку Сегодня выполнялось позиционирование на выбранную дату с активизацией месяца, из которого выбрана дата.

В тонком и толстом клиентах в календаре поля ввода выбор даты не из текущего месяца приводил к активизации выбранного месяца в поле календаря. В веб-клиенте происходило помещение выбранной даты в поле ввода. +

Поведение интерфейса в некоторых ситуациях стало более ожидаемым. Унифицировано поведение системы в разных клиентских приложениях.
Хранилище конфигурации.
В сервере хранилища конфигурации реализована проверка целостности данных объекта, который помещается в хранилище конфигурации. Если фиксируется нарушение целостности помещаемого объекта - генерируется исключение и объект не помещается в хранилище.На сервере хранилища конфигурации не выполнялась проверка целостности данных объекта, который помещается в хранилище конфигурации.Снижена вероятность помещения в хранилище конфигурации испорченных данных, описывающих объект конфигурации.
Обновление конфигурации базы данных.
Во время динамического обновления корректно отрабатывается удаление объектов конфигурации, которые не препятствуют обновлению и отсутствуют в новой конфигурации. Такие объекты будут удалены только при монопольном обновлении.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Во время динамического обновления объекты конфигурации, которые не препятствуют обновлению и отсутствуют в новой конфигурации удалялись сразу, во время динамического обновления.Снижено количество проблем, возникающих в результате динамического обновления в том случае, если в новой конфигурации удалялись какие-либо объекты конфигурации.
Web-сервисы и HTTP-сервисы.
Работа с Интернет.
Данное изменение отменено.

При выполнении кодировании строки URI (как с помощью функции КодироватьСтроку() так и во внутренних механизмах платформы) символ % заменяется на %25.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При выполнении кодировании строки (как с помощью функции КодироватьСтроку() так и во внутренних механизмах платформы) символ % не заменялся на %25 и оставался «как есть».При кодировании строки URI применены рекомендации RFC 3986.
Локализация.
При формировании прописи числа на азербайджанском языке, исправлена орфографическая ошибка для чисел, начинающихся на «два» и «двадцать».При формировании прописи числа на азербайджанском языке, имелась орфографическая ошибка для чисел, начинающихся на «два» и «двадцать».Устранено некорректное поведение системы.
Средства разработки.
При просмотре в отладчике какой-либо коллекции (например, таблицы значений) в отдельном окне, колонки просматриваемой коллекции не упорядочиваются по алфавиту.При просмотре в отладчике какой-либо коллекции (например, таблицы значений) в отдельном окне, колонки просматриваемой коллекции упорядочивались по алфавиту. Данное поведение наблюдалось в системе «1С:Предприятие» версий 8.3.7 и 8.3.8.Устранено незапланированное поведение системы.
Общие реквизиты / Разделение данных.
Расширение конфигурации.
Метод УдалитьДанныеИнформационнойБазы() удаляет также и расширения конфигурации для всей информационной базы или для конкретной области, в зависимости от того, как выполнен вызов метода.Метод УдалитьДанныеИнформационнойБазы() не удалял расширения конфигурации.В методе УдалитьДанныеИнформационнойБазы() реализована более целостная очистка данных информационной базы.
В документации данное изменение описано здесь.
Динамический список.
При вводе в строку поиска динамического списка значения, похожего на дату, в которой год указан одной или двумя цифрами, год будет приведен к текущему веку. Данное поведение предотвращает ошибку поиска при использовании СУБД Microsoft SQL Server с установленным смещением дат равным 0.При вводе в строку поиска динамического списка значения, похожего на дату, в которой год указан одной или двумя цифрами, год не приводился к текущему веку. В этом случае поиск завершался ошибкой при использовании СУБД Microsoft SQL Server с установленным смещением дат равным 0.Исключены проблемы работы динамического списка при вводе даты в строку поиска при использовании СУБД Microsoft SQL Server с установленным смещением дат равным 0.
В документации данное изменение описано здесь.
Табличный документ.
При экспорте табличного документа в формат Microsoft Excel 97 и старше, для ячеек, содержащих многострочный текст, выровненный по центру ячейки и не умещающийся в ячейке целиком, добавляются дополнительные объединения ячеек. Объединение выполняется по горизонтали, в обе стороны от оригинальной ячейки, на равные расстояния, достаточные для размещения всего текста оригинальной ячейки. Колонки, в которые «попадают» левая и правая границы прямоугольника, занимаемого текстом, разбиваются на две.

В результате экспортированный документ в формате Microsoft Excel более точно соответствует оригинальному табличному документу.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При экспорте табличного документа в формат Microsoft Excel 97 и старше, для ячеек, содержащих многострочный текст, расположенный по центру ячейки, и не умещающийся в ячейке, не создавалось дополнительных объединений ячеек.При выгрузке табличного документа в формате Microsoft Excel реализовано более точное соответствие оригинальному табличному документу.
В документации данное изменение описано здесь и здесь.
Средства разработки.
Если программный доступ к буферу обмена интернет-браузера Microsoft Internet Explorer заблокирован параметром безопасности этого браузера Разрешить программный доступ к буферу обмена, то при попытке использовать команду Копировать контекстного меню Синтакс-помощника будет выводится предупреждение о такой блокировке и возможном пути обхода (использовать клавиатуру).

+

В том случае, если параметр безопасности Разрешить программный доступ к буферу обмена интернет-браузера Microsoft Internet Explorer установлен в значение Отключить, не работала команда Копировать контекстного меню Синтакс-помощника.Улучшена диагностика неочевидного поведения системы.
Управляемая форма.
Для групп, отображающих данные в заголовке, реализована поддержка свойства Формат во всех вариантах интерфейса (Такси и Версия 8.2) в тонком и веб-клиентах.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Для групп, отображающих данные в заголовке, свойство Формат поддерживалось не во всех вариантах интерфейса (Такси и Версия 8.2), а также имелись различия между тонким и веб-клиентами.Устранено различие в поведении между тонким и веб-клиентами. Устранено некорректное поведение системы.
Средства разработки.
Восстановлена возможность обновления конфигурации, содержащей формы констант, при помощи файла обновления (.cfu).

Стало возможно обновлять конфигурации с помощью файла обновления (.cfu) в тех случаях, когда изменялось только значение флага Использовать всегда в формах констант.

В некоторых случаях, когда в новой конфигурации изменялось значение флага Использовать всегда в формах констант, возникали проблемы с обновлением конфигураций, содержащих формы констант.Исключены имевшиеся в отдельных случаях проблемы, возникающие при обновлении конфигураций, содержащих формы констант, с помощью файла .cfu.
Средства разработки.
В том случае, если файл, содержащий измененные и новые объекты, создаваемый в процессе формирования файла обновления (.cfu), превышает размер 2 Гб, файл обновления формируется в новом формате. Информация об этом выводится в диалоговом окне при интерактивном формировании файла обновления или в файл с сообщениями (параметр командной строки /out) при формировании файла обновления в пакетном режиме.

Файл обновления, сформированный в новом формате, можно использовать для обновления только с помощью версии платформы 8.3.9.2033 и старше.

При попытке использовать для обновления файл, сформированный в новом формате, на версии «1С:Предприятия» младше указанной выше - будет выдаваться ошибка о неверном формате хранилища данных.

Система «1С:Предприятие» версии 8.3.9.2033 и старше может использовать для обновления файлы обновлений любого формата.

В том случае, если файл, содержащий измененные и новые объекты, создаваемый в процессе формирования файла обновления (.cfu), превышает размер 2 Гб, формирование файла обновления было невозможно.Стала возможна работа с очень большими файлами обновлений (.cfu).
Средства печати.
При использовании метода ПакетОтображаемыхДокументов.Напечатать() (кроме веб-клиента), пакет разбивается на несколько заданий. При этом для формирования заданий (и разбиения пакета документов) используются различные свойства пакета документов, которые задают принтер, на который будет отправляться печать, а также управляющие ориентацией страниц при печати, использованием двусторонней печати и т.д.При использовании метода ПакетОтображаемыхДокументов.Напечатать() (кроме веб-клиента), пакет документов печатался одним заданием. В результате могли возникать проблемы, если документы пакета должны были печататься на разные принтеры или различались свойствами печати, которые можно задать только один раз в одном задании печати.Устранены проблемы печати пакета документов, в том случае, когда различные документы в пакете должны печататься на различных принтерах, а также отличаются свойствами, управляющими ориентацией страниц, двусторонней печатью и т.д.
Работа с ОС.
Изменено поведение платформы «1С:Предприятие» при попытке перевести компьютер в спящий режим. Платформа «1С:Предприятие» препятствует переходу компьютера в спящий режим в том случае, если используется:
  • сетевой ключ защиты;
  • файловый вариант информационной базы, с файлом базы данных, который расположен на сетевом ресурсе.
Платформа «1С:Предприятие» препятствовала переходу компьютера в спящий режим в том случае, если используется:
  • сетевой ключ защиты;
  • файловый вариант информационной базы, с файлом базы данных, который расположен на сетевом ресурсе;
  • клиент-серверный вариант информационной базы.
Изменено использование энергосберегающих режимов операционной системы при работе системы «1С:Предприятие».
В документации данное изменение описано здесь.
Работа с информационными базами.
Выгрузка информационной базы в файл .dt не будет прервана при обнаружении проблем с внутренней структурой информационной базы.Выгрузка информационной базы в файл .dt прерывалась при обнаружении проблем с внутренней структурой информационной базы.Исключены проблемы, связанные с тем, что при наличии малозначимых проблем во внутренних структурах данных (не влияющих на работу системы) не работал механизм выгрузки информационной базы.
Работа с JSON.
Повышена стабильность при работе с JSON.При работе с JSON могло возникать аварийное завершение работы системы.Устранено некорректное поведение системы.
Кластер серверов.
При изменении значения свойства кластера Защищенное соединение новое значение начинает действовать только после перезапуска процессов кластера. В связи с этим после изменения значения свойства Защищенное соединение рекомендуется перезапустить кластер.При попытке изменить в консоли кластера значение свойства кластера Защищенное соединение формировалось сообщение об ошибке и изменение блокировалось.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Встроенный язык.
При компиляции текстов на встроенном языке генерируется ошибка, если используется отсутствующая директива компиляции.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При использовании неизвестной директивы компиляции не генерировалось ошибки при компиляции модуля.Повышен контроль за исходными текстами. Уменьшено количество сложно обнаруживаемых проблем (когда используемая директива компиляции незначительно отличается от настоящей).
Работа с запросами.
При откате транзакции из менеджера временных таблиц удаляются все временные таблицы, которые были созданы в рамках транзакции. В файловом варианте исключена возможность после отката транзакции в запросе использовать временные таблицы, которые были созданы этим запросом в рамках транзакции. При работе с другими СУБД использование временных таблиц после отката транзакции было недоступно.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Из менеджера таблиц автоматически не удалялись временные таблицы, созданные в рамках отмененной транзакции. В файловом варианте базы данных, в запросах можно было использовать временные таблицы, созданные в рамках транзакции и после отката транзакции. При работе с другими СУБД использование временных таблиц после отката транзакции было недоступно.Обеспечено единое поведение платформы «1С:Предприятие» при работе на различных СУБД.
В документации данное изменение описано здесь и здесь.
Навигационные ссылки.
При попытке выполнить метод ПолучитьНавигационнуюСсылку() для значения, от которого нельзя получить навигационную ссылку, генерируется исключение.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При попытке выполнить метод ПолучитьНавигационнуюСсылку() для значения, от которого нельзя получить навигационную ссылку:
  • в тонком-клиенте возвращалась пустая строка;
  • в веб-клиенте генерировалось исключение.
Унифицировано поведение системы при работе в различных клиентских приложениях.
В документации данное изменение описано здесь.
Оконная система.
Обработка ошибок.
Если для методов Вопрос(), ПоказатьВопрос(), Предупреждение(), ПоказатьПредупреждение() в параметре Таймаут передано отрицательное значение, то будет генерироваться исключение.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Если для методов Вопрос(), ПоказатьВопрос(), Предупреждение(), ПоказатьПредупреждение() в параметре Таймаут передано отрицательное значение, то:
  • в тонком клиенте таймаут отсчитывался от числа 4 294 967 295.
  • в веб-клиенте подстановки значения не происходило.
Устранено некорректное поведение системы. Унифицировано поведение системы при работе в различных клиентских приложениях.
Управляемая форма.
Во время исполнения прикладного решения, во время разработки, реализована возможность диагностировать использование контекстных серверных вызовов (в том числе неявных) в обработчиках событий формы, для которых запрещены такие вызовы. При включении такого режима, формируется диагностическое сообщение в окне сообщений.

Для управления такой диагностикой реализован ключ командной строки запуска клиентского приложения /EnableCheckServerCalls. Реализована настройка запуска клиентского приложения из конфигуратора, которая включает использование данного ключа при запуске клиентского приложения из конфигуратора. +

Отсутствовал инструмент, который позволял разработчику получать информацию об использовании контекстных серверных вызовов в обработчиках событий формы, для которых запрещены такие вызовы.Улучшена диагностики некорректного использования программных интерфейсов системы «1С:Предприятие» для разработчика.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Если в качестве параметра операции В языка запросов передать таблицу значений, в которой для колонки указан тип Строка с длиной более 1024 символов или ДвоичныеДанные размером более 2048 байт, то во время исполнения такого запроса будет сгенерировано исключение.Если в качестве параметра операции В языка запросов передать таблицу значений, в которой для колонки указан тип Строка с длиной более 1024 символов или ДвоичныеДанные размером более 2048 байт, то возможность исполнения такого запроса зависела от используемой СУБД.Повышена предсказуемость работы системы на различных СУБД. Повышена надежность работы системы.
В документации данное изменение описано здесь.
Клиентское приложение.
Управляемая форма.
При запуске толстого клиента игнорируется свойство конфигурации Режим использования синхронных вызовов расширений платформы и внешних компонент, при этом все синхронные методы работают без исключений и предупреждений.

При запуске толстого клиента из конфигуратора не передается параметр /EnableCheckExtensionsAndAddInsSyncCalls. Для тонкого и веб-клиента поведение не изменилось.

Механизм проверки конфигурации и механизм рефакторинга не меняют своего поведения: выдают ошибки для синхронных методов в программном коде прикладного решения и предлагают их преобразование в асинхронные.

При запуске толстого клиента учитывалось свойство конфигурации Режим использования синхронных вызовов расширений платформы и внешних компонент.

Параметр /EnableCheckExtensionsAndAddInsSyncCalls подставлялся при запуске толстого клиента из конфигуратора.

Исключены проверки использования синхронных методов при использовании прикладного решения, ориентированного на использование только толстого клиента.
В документации данное изменение описано здесь и здесь.
Работа с запросами.
Конструктор запроса (в конфигураторе и толстом клиенте) и объект СхемаЗапроса (в толстом клиенте), при генерации текста запроса формируют псевдонимы для всех полей первого запроса (среди объединений) для каждого запроса пакета.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Конструктор запроса (в конфигураторе и толстом клиенте) и объект СхемаЗапроса (в толстом клиенте), при генерации текста запроса формировали псевдонимы только для полей-выражений и полей, по которым выполнялось упорядочивание и рассчитывались итоги.Поведение конструктора запроса и объекта СхемаЗапроса унифицировано между различными клиентскими приложениями.
В документации данное изменение описано здесь.
Управляемая форма.
Хранение настроек.
Для хранения положения разделителей рабочего стола используются следующие ключи объектов:
  • HomePage/WindowSettings;
  • HomePage/Taxi/WindowSettings.

После отключения режима совместимости для существующих настроек выполняется переименование. При установке режима совместимости в значение Версия 8.3.8 выполняется обратное переименование.

Изменено имя файла выгрузки (в формате XML) содержащего свойство РабочаяОбластьНачальнойСтраницы.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Для хранения положения разделителей рабочего стола использовались следующие ключи объектов:
  • StartPage/WindowSettings;
  • StartPage/Taxi/WindowSettings.
Англоязычные термины приведены к общепринятым.
В документации данное изменение описано здесь.
Табличный документ.
При включенной автоматической группировке, создаваемой группировке проставляется видимость и имя группы от области, которая выводилась в области заголовка группировки.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При включенной автоматической группировке, создаваемой группировке проставлялась видимости и имя группы от области, которая выводилась внутри группировки.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Общие объекты.
В том случае, если в качестве параметра ИменаБазыДанных метода ПолучитьСтруктуруХраненияБазыДанных() передается значение, отличное от типа Булево, генерируется исключение.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В качестве параметра ИменаБазыДанных метода ПолучитьСтруктуруХраненияБазыДанных() допускалась передача значения любого типа.Устранено некорректное поведение системы.
Табличный документ.
При выводе в табличный документ текста под произвольным углом, текст выводится тем же размером шрифта, что и текст, выводимый без поворота.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При выводе в табличный документ текста под произвольным углом, текст выводился большим размером шрифта, чем текст, выводимый без поворота.Устранено некорректное поведение системы.
Работа с СУБД.
Изменение времени ожидания блокировки данных в диалоге конфигуратора Параметры информационной базы требует административных прав в неразделенном сеансе и устанавливает монопольный режим доступа к информационной базе. При невозможности установки монопольного доступа выдается сообщение об ошибке со списком «мешающих» сеансов и возможностью повторения.

Метод УстановитьВремяОжиданияБлокировкиДанных() требует административных прав в неразделенном сеансе и устанавливает режим монопольного доступа к базе данных, если он еще не был установлен, и завершается с исключением при невозможности установки монопольного доступа.

Изменение времени ожидания блокировки данных действует сразу после выполнения для всех СУБД, кроме IBM DB2. На IBM DB2 после изменения времени ожидания блокировки данных требуется рестарт СУБД.

Изменение времени ожидания блокировки данных в диалоге конфигуратора Параметры информационной базы и методом УстановитьВремяОжиданияБлокировкиДанных() из встроенного языка допускалось при совместном использовании информационной базы.В некоторых случаях ликвидирована причина возникновения ошибок при работе с базой данных.
В документации данное изменение описано здесь.
Работа с XML, XDTO.
Для метода ЗаписьXML.ОткрытьФайл() реализован параметр ДобавлятьBOM, позволяющий управлять наличием BOM в формируемом файле.Данная возможность не предоставлялась.Реализована возможность взаимодействия с системами, которые не ожидают BOM в обрабатываемых XML-файлах.
Средства администрирования.
При работе с файловой информационной базой реализована проверка версий клиентских приложений. Работа возможна только в случае полного совпадения версий клиентских приложений. При несовпадении версии выводится ошибка.При совместной работе «1С:Предприятие» версий от 8.2.19 до 8.3.4, а также версий 8.3.5 и 8.3.6 - формировалось сообщение об ошибке несоответствия версий.

В некоторых случаях была возможна одновременная работа системы «1С:Предприятие» версий 8.2.18 и младше совместно с версиями от 8.3.1 до 8.3.3.

Повышена стабильность файлового варианта информационной базы. Работа разных версий системы «1С:Предприятие» с файловым вариантом информационной базы стала невозможной.
В документации данное изменение описано здесь.
Работа с ZIP-архивами.
Разделитель пути для объекта ЭлементZipФайла зависит от используемой операционной системы.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Разделитель пути для объекта ЭлементZipФайла не зависел от используемой операционной системы и всегда был равен символу «/».Поведение механизмов работы с ZIP-файлами (в части работы с разделителями пути) приведено к общей схеме работы с разделителями пути.
В документации данное изменение описано здесь.
Система компоновки данных.
Компоновщик макета компоновки данных, при генерации имен параметров, не присваивает параметрам имена, которые уже существуют в схеме компоновки данных.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Компоновщик макета компоновки данных, при генерации имен параметров, мог присвоить параметрам имена, которые уже существуют в схеме компоновки данных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Средства администрирования.
При установке защищенного соединения (HTTPS) с Центром лицензирования автоматически используется хранилище корневых сертификатов текущей операционной системы.

В случае, если для выхода в интернет используется прокси-сервер дешифрующий трафик защищенного соединения (HTTPS), то администратору необходимо добавить сертификаты, которыми подписан сертификат прокси-сервера в хранилище доверенных корневых сертификатов ОС.

При установке защищенного соединения (HTTPS) с Центром лицензирования, сертификат для защищенного соединения искался в файле cacert.pem.Уменьшено количество проблем, возникающих при взаимодействии системы «1С:Предприятие» и Центра лицензирования.
Расширение конфигурации.
Во время выполнения некоторых обработчиков объектов конфигурации и подписок реализовано отключение безопасного режима. После выполнения обработчика (или подписки) безопасный режим и его профиль восстанавливаются.

Если разработчику необходимо самостоятельно отключить безопасный режим, то сделать это можно с помощью реализованных методов глобального контекста УстановитьОтключениеБезопасногоРежима() и ПолучитьОтключениеБезопасногоРежима(). Методы недоступны в расширении.

Обработчики, в которых выполняется автоматическое отключение безопасного режима, отмечены в синтакс-помощнике.

Отсутствовала возможность отключать безопасный режим в коде конфигурации.Реализована возможность работы с объектами, события модуля объекта которых выполняются в привилегированном режиме, из расширений и внешних обработок, исполняемых в безопасном режиме.
В документации данное изменение описано здесь.
Работа с Интернет.
При установке защищенного соединения используется протокол TLS 1.2 как более защищенный. При необходимости использовать протокол TLS 1.0 при подключении к веб-серверу можно использовать ключ командной строки запуска тонкого клиента /HttpsForceTLS1_0.

Объекты HTTPСоединение, FTPСоединение и WSПрокси автоматически используют протокол TLS 1.2 вне зависимости от указания источника клиентских сертификатов.

Для конфигурационного файла conf.cfg реализован параметр ForceTLS1_0.

Не поддерживается одновременное использование ключей командной строки запуска тонкого клиента /HttpsForceTLS1_0 и /HttpsForceSSLv3.

При установке защищенного соединения использовался протокол TLS 1.0.Повышена защищенность соединения, устанавливаемого клиентским приложением, при работе через Интернет.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
В том случае, если SMTP-сервер не смог отправить электронное сообщение одному или нескольким адресатам, то метод ИнтернетПочта.Послать() возвращает соответствие, где для каждого адресата (являющегося ключом соответствия) возвращается диагностика SMTP-сервера (значение соответствия).

В режиме совместимости с версией 8.3.8 поведение не изменилось.

В том случае, если SMTP-сервер не смог отправить электронное сообщение одному или нескольким адресатам, метод ИнтернетПочта.Послать() генерировал исключение.Стало возможно точно определять, какому из получателей не отправлена электронная почта и позволяет понять причины такого поведения SMTP-сервера.
В документации данное изменение описано здесь.
Средства разработки.
Свойства конфигурации.
Выгрузка/загрузка конфигурации в файлы.
При выгрузке конфигурации в файлы, изменена выгрузка свойства конфигурации Режим совместимости. При обратной загрузке не будет происходить потери информации о реальном режиме совместимости.При выгрузке конфигурации в файлы, свойство конфигурации Режим совместимости, если оно установлено в значение Не использовать, также выгружалось как значение Не используется. Если такую конфигурацию загрузить в старшей версии, то режим совместимости восстанавливался неверно.Предотвращена возможность потери информации о реальном режиме совместимости конфигурации после операции выгрузки/загрузки конфигурации.

Устранено некорректное поведение системы.

Табличный документ.
Метод ЗаполнитьЗначенияСвойств(), применяемый к табличному документу, копирует свойство Макет табличного документа.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Метод ЗаполнитьЗначенияСвойств(), применяемый к табличному документу, не копировал свойство Макет табличного документа.Исключено реализованное ранее поведение, предназначенное для удобства перехода на предыдущую версию.
Средства администрирования.
Работа с базой данных.
В файловом варианте работы, база данных по умолчанию создается в формате 8.3.8.В файловом варианте работы, база данных по умолчанию создавалась в формате 8.2.14.Реализованный в версии 8.3.8 оптимизированный формат файловой базы данных будет использоваться для новых информационных баз по умолчанию.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Свойство Порт объекта FTPСоединение и параметр Порт конструктора данного объекта, имеют тип Число.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Свойство Порт объекта FTPСоединение и параметр Порт конструктора данного объекта, имели тип Строка. Для параметра конструктора считались допустимыми любые данные, которые могли быть преобразованы к типу Число.Устранено незапланированное поведение системы.
Работа с базой данных.
В результате вызова метода ПолучитьСтруктуруХраненияБазыДанных(), для таблиц, не имеющих представления в терминах языка запросов, имена таблиц (свойство ИмяТаблицы) и полей этих таблиц (свойство ИмяПоля) равны пустой строке.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

В результате вызова метода ПолучитьСтруктуруХраненияБазыДанных(), для таблиц, не имеющих представления в терминах языка запросов, имена таблиц (свойство ИмяТаблицы) и полей этих таблиц (свойство ИмяПоля) были равны представлениям виртуальных таблиц.Устранено некорректное поведение системы.
Работа с HTML.
Запись или чтение HTML-документа, который содержит внутри себя строку <?xml, не приводит к сообщению об ошибке.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Запись или чтение HTML-документа, который содержит внутри себя строку <?xml, приводил к сообщению об ошибке.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с ZIP-архивами.
Имена файлов в zip-архиве записываются в кодировке UTF8.

Для конструктора объекта ЗаписьZipФайла и метода этого объекта Открыть() реализованы параметры позволяющие управлять кодировкой имен файлов в zip-архивах. Значения вышеуказанных параметров имеют приоритет над значением параметра FileNamesEncodingInZipFile файла conf.cfg.

Для параметра FileNamesEncodingInZipFile файла conf.cfg, значением по умолчанию является значение UTF8.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Имена файлов в zip-архиве записывались в кодировке UTF8 и текущей кодировке используемой ОС.

При работе с zip-архивом из встроенного языка было невозможно управлять кодировкой имен файлов в zip-архивах.

Для параметра FileNamesEncodingInZipFile файла conf.cfg, значением по умолчанию выступало значение OSEncodingWithUTF8.

И встроенного языка стало возможно управлять кодировкой имен файлов в архивах, формируемых системой «1С:Предприятие».
В документации данное изменение описано здесь.
Динамический список.
Данные полей динамического списка, задействованных в отборе элементов условного оформления формы, передаются на сторону клиента в независимости от значения свойства этого поля Использовать всегда или связанной видимой колонки.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Данные полей динамического списка, задействованных в отборе элементов условного оформления формы, автоматически не передавались на сторону клиента. Для того что бы такие элементы функционировали корректно, было необходимо для полей динамического списка, задействованных в отборе этих элементов, установить свойство Использовать всегда.Повышено удобство разработки.
Динамический список.
В документацию внесена рекомендация не использовать условное оформление формы для оформления динамических списков, если такое оформление можно получить за счет настройки условного оформления самого списка.

+

В документации отсутствовала рекомендация не использовать условное оформление формы для оформления динамических списков, если такое оформление можно получить за счет настройки условного оформления самого списка.Улучшена документация к системе.
В документации данное изменение описано здесь.
Система компоновки данных.
При компоновке макета системы компоновки данных, получение полей и применение отборов к полям, полученным «через точку» от полей, содержащих агрегатные функции, которые получаются из запроса, выполняется с помощью дополнительных наборов данных, автоматически генерируемых компоновщиком макета.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При компоновке макета системы компоновки данных, получение полей и применение отборов к полям, полученным «через точку» от полей, содержащих агрегатные функции, которые получаются из запроса, выполнялось в самом запросе. При этом мог быть получен некорректный результат или сформированный запрос мог выдавать ошибку при исполнении.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При генерации параметров в макете схемы компоновки данных, для параметров, имена которых могут быть на русском и английском языках, имена формируются на языке, который соответствует текущему варианту встроенного языка.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При генерации параметров в макете схемы компоновки данных, для параметров, которые могут иметь два имени, всегда формировался параметр с именем на английском языке.Стало возможно использовать русские имена параметров схемы компоновки данных, которые совпадают с именами параметров, автоматически получаемых из виртуальных таблиц.
В документации данное изменение описано здесь.
Управляемая форма.
Изменено поведение системы при выполнении следующего сценария: в поле ввода вводится какой-либо текст, не выходя из поля ввода нажимается гиперссылка, расположенная в декорации, в обработчике нажатия гиперссылки декорации выполняется контекстный серверный вызов:
  • для поля ввода вызывается обработчик события ПриИзменении;
  • для декорации вызывается обработчик события ОбработкаНавигационнойСсылки;
  • поле ввода отображает значение, соответствующее введенному тексту.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

При выполнении следующего сценария: в поле ввода вводится какой-либо текст, не выходя из поля ввода нажимается гиперссылка, расположенная в декорации, в обработчике нажатия гиперссылки декорации выполняется контекстный серверный вызов, наблюдалось следующее поведение системы:
  • в тонком и толстом клиентских приложениях:
    • для декорации вызывается обработчик события ОбработкаНавигационнойСсылки;
    • поле ввода отображает значение, которое было до ввода текста.
  • в веб-клиенте:
    • для декорации вызывается обработчик события ОбработкаНавигационнойСсылки;
    • поле ввода отображает введенный текст.
Устранено некорректное поведение системы.

Унифицировано поведение различных клиентских приложений.

В документации данное изменение описано здесь.
Клиентское приложение.
Установка клиентского приложения.
Веб-клиент.
В связи с тем, что ОС Windows версий 2008 R2 и старше, начиная с января 2017 года, прекращает доверять сертификатам, которые используют алгоритм SHA-1, реализованы следующие изменения:
  • Программы установки расширений работы с файлами и криптографией (для ОС Windows) при работе с веб-браузерами Google Chrome и Mozilla Firefox переведены в формат .exe и подписываются с использованием алгоритмов SHA-1 и SHA-256.
  • При формировании файла установки клиентского приложения 1CEClientSetup.exe рекомендуется подписывать получившийся файл с использованием алгоритмов SHA-1 и SHA-256. Соответствующая рекомендация внесена в статью на ИТС, описывающую использование утилиты 1CEClientSetupMake.exe (см. здесь).
Программы установки расширений работы с файлами и криптографией (для ОС Windows) при работе с веб-браузерами Google Chrome и Mozilla Firefox поставлялись в формате .msi и подписывались с использованием алгоритма SHA-1.

В статье на ИТС, которая описывает использование утилиты 1CEClientSetupMake.exe (см. здесь) содержалась только информация о необходимости подписывать получившийся файл 1CEClientSetup.exe, без уточнения используемых алгоритмов.

Исполняемые файлы платформы будут проходить проверку на всех поддерживаемых операционных системах семейства Windows.
Автоматизированное тестирование.
При вызове метода ТестируемаяКнопкаФормы.Нажать() будет генерироваться ошибка, если «нажимаемая» кнопка не отображается на тестируемой форме.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Вызов метода ТестируемаяКнопкаФормы.Нажать() не приводил к генерации ошибки, если «нажимаемая» кнопка не отображается на тестируемой форме.Устранено некорректное поведение системы.

Механизм автоматизированного тестирования может выполнять только те действия, которые может выполнить в интерактивном режиме обычный пользователь.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Английский вариант наименования объекта СоставФормНачальнойСтраницы. Старое наименование поддерживается для совместимости.
  • StartPageForms.
  • HomePageForms.
Английский вариант наименования объекта НастройкиНачальнойСтраницы. Старое наименование поддерживается для совместимости.
  • StartPageSettings.
  • HomePageSettings.
Английский вариант наименования объекта РабочаяОбластьНачальнойСтраницы. Старое наименование поддерживается для совместимости.
  • StartPageWorkingArea.
  • HomePageWorkingArea.
Английский вариант наименования свойства ОкноКлиентскогоПриложения.НачальнаяСтраница. Старое наименование поддерживается для совместимости.
  • StartPage.
  • HomePage.
Английский вариант наименования свойства ТестируемоеОкноКлиентскогоПриложения.НачальнаяСтраница. Старое наименование поддерживается для совместимости.
  • StartPage.
  • HomePage.
Наименование системного перечисления, содержащего варианты выравнивания элементов и их заголовков.
  • ВыравниваниеЭлементовИЗаголовков.
  • ВариантВыравниванияЭлементовИЗаголовков.
Значение колонки Назначение для таблицы ExtensionInfo в таблице значений, возвращаемой методом ПолучитьСтруктуруХраненияБазыДанных().

В режиме совместимости с версией 8.3.8 поведение не изменилось.

  • Основная (Main).
  • ИнформацияОРасширенияхКонфигурации (ConfigurationExtensionsInformation).
Значение колонки Назначение для таблицы ODataSettings в таблице значений, возвращаемой методом ПолучитьСтруктуруХраненияБазыДанных().

В режиме совместимости с версией 8.3.8 поведение не изменилось.

  • Основная (Main).
  • НастройкиСтандартногоИнтерфейсаOData (StandardODataInterfaceOptions).

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Работа с файлами.
Работа с мультимедиа.
На мобильной платформе реализована доступность объекта ДиалогВыбораФайла. Ограничения диалога для каждой мобильной операционной системы описаны в синтакс-помощнике. При работе на мобильном устройстве, реализована возможность интерактивного выбора файлов для методов ПолучитьФайл(), ПолучитьФайлы(), ПоместитьФайл(), ПоместитьФайлы().

Реализован метод Файл.ПолучитьПредставлениеФайлаБиблиотекиМобильногоУстройства(), который возвращает представление файла на мобильном устройстве для отображения пользователю.

Имя файла из библиотеки мобильного устройства (со схемой content:) можно использовать в конструкторах следующих объектов: Файл, ДвоичныеДанные, Картинка, ЗапускПриложенияМобильногоУстройства, в качестве параметров следующих методов глобального контекста ЗапуститьПриложение(), ПерейтиПоНавигационнойСсылке(), КопироватьФайл(), ПереместитьФайл(), УдалитьФайлы(), НайтиФайлы(), а также в качестве параметров методов ВоспроизвестиАудио() и ПолучитьПродолжительностьАудио() объекта СредстваМультимедиа (на платформах iOS и Android). Реализован метод глобального контекста КаталогБиблиотекиМобильногоУстройства(), возвращающий путь к требуемой библиотеке (аудио, видео или картинки) мобильного устройства.

Объект ДиалогВыбораФайла был недоступен на мобильной платформе.Для мобильной платформы реализована возможность интерактивной работы с файлами.
В документации данное изменение описано здесь.
Специальные возможности мобильного устройства.
Для ОС Android реализована возможность программной обработки информации о входящих звонках.

Для объекта СредстваТелефонии реализованы методы ПоддерживаетсяОбработкаЗвонков(), ПодключитьОбработчикЗвонков(), ОтключитьОбработчикЗвонков(). Метод СредстваТелефонии.ПоддерживаетсяОбработкаЗвонков() будет возвращать значение Истина только на ОС Android.

Данная функциональность не поддерживалась на мобильной платформе.Стало возможно обрабатывать информацию о входящих звонках в мобильном приложении, которое работает под управлением ОС Android.
В документации данное изменение описано здесь.
Специальные возможности мобильного устройства.
Расширены возможности работы с мультимедиа на мобильной платформе:
  • Реализована возможность воспроизведения звукового или вибро-сигнала. Реализован метод СредстваМультимедиа.ВоспроизвестиЗвуковоеОповещение().
  • Реализована возможность воспроизведения аудиоинформации различных типов. Воспроизведение выполняется с помощью программы воспроизведения, установленной в ОС по умолчанию. Реализована возможность останавливать воспроизведение. Для объекта СредстваМультимедиа реализованы методы ВоспроизвестиАудио(), ОстановитьВоспроизведениеАудио(), ПолучитьПродолжительностьАудио().
  • Реализована возможность воспроизведения текста с помощью встроенного в ОС синтезатора речи. Реализована возможность останавливать воспроизведение текста. Для объекта СредстваМультимедиа реализованы методы ВоспроизвестиТекст(), ОстановитьВоспроизведениеТекста(), ПоддерживаетсяВоспроизведениеТекста().
Данная функциональность не поддерживалась на мобильной платформе.Расширены возможности по работе с мультимедиа.
В документации данное изменение описано здесь.
Система компоновки данных.
На мобильной платформе реализована поддержка системы компоновки данных, за исключением объектов, допускающих интерактивное взаимодействие с пользователем. Таким образом, вся работа с системой компоновки данных выполняется средствами встроенного языка.

В конфигураторе реализована возможность создания схемы компоновки данных для отчетов, выполняющихся в мобильном приложении.

Данная функциональность не поддерживалась на мобильной платформе.Расширены возможности мобильной платформы для создания отчетов.
Внешние компоненты.
В мобильной платформе реализована возможность использования внешних компонент. Внешние компоненты реализуются по технологии Native API.

Выгрузка мобильной конфигурации из конфигуратора может выполняться в формате 1cema.zip, который включает в себя используемые внешние компоненты. При подключении мобильного устройства с помощью технологии Android Debug Bridge (ADB) внешние компоненты копируются на устройство.

В сборщике мобильных приложений реализована возможность сборки мобильного приложения с включением в его состав внешних компонент.

Доработаны примеры и документация по технологии внешних компонент (см. здесь).

Данная функциональность не поддерживалась на мобильной платформе.Реализована возможность расширять функциональность мобильного приложения в том случае, если недостаточно собственных возможностей мобильной платформы. +
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Управляемая форма.
Для мобильной платформы реализованы следующие возможности:
  • Отображать кнопку, расположенную на командной панели, в виде гиперссылки;
  • Управлять горизонтальным расположением картинки в кнопке управляемой формы;
  • Управлять расстоянием между кнопками, расположенными на командной панели;
  • Управлять формой кнопок командной панели (кроме расположенных в подменю);
  • Управлять внешним видом кнопки управляемой формы;
  • Для поля ввода реализована поддержка свойств КнопкаСоздания, ОтображениеКнопкиВыбора;
  • Для поля ввода реализована поддержка событий ИзменениеТекстаРедактирования и Создание.

Реализована поддержка свойств ЦветРамки, ЦветФона, ЦветТекстаЗаголовка, ШрифтЗаголовка для кнопок вида КнопкаКоманднойПанели, ГиперссылкаКоманднойПанели и для расширения группы формы для подменю. +

Данная функциональность не поддерживалась на мобильной платформе.Набор возможностей, доступный на мобильной платформе при работе с управляемой формой, стал меньше отличаться от набора возможностей платформы для персонального компьютера.
Работа с Интернет.
Специальные возможности мобильного устройства.
Реализована возможность анализировать доступность сети передачи данных в мобильном приложении.

Реализовано свойство глобального контекста ИнформацияОбИнтернетСоединении.

Данная функциональность не поддерживалась на мобильной платформе.Стало возможно выполнять анализ доступных способов передачи данных для выбора оптимальной стратегии работы с внешними данными.
В документации данное изменение описано здесь.
Работа с JSON.
Для мобильной платформы реализована возможность работы с данными в формате JSON. Не поддерживается XDTO-сериализация в формате JSON.Данная функциональность не поддерживалась на мобильной платформе.Упрощено взаимодействие с приложениями (в том числе и веб-приложениями), использующими для взаимодействия формат JSON.

Стало возможно хранить различные данные в формате JSON, например, вместо XML.

Работа с Интернет.
Поведение объекта ЗащищенноеСоединениеOpenSSL приведено в соответствие платформе на ПК:
  • Если параметр СертификатыУдостоверяющихЦентров конструктора объекта не задан - сертификат проверяться не будет;
  • Если параметр СертификатыУдостоверяющихЦентров конструктора объекта задан - для проверки используются корневые сертификаты, установленные на устройстве.

На мобильной платформе реализована доступность объекта СертификатыУдостоверяющихЦентровОС.

В режиме совместимости с версией 8.3.8 поведение не изменилось.

Сертификат всегда проверялся с использованием корневых сертификатов, установленных на мобильном устройстве. Параметр СертификатыУдостоверяющихЦентров конструктора объекта ЗащищенноеСоединениеOpenSSL игнорировался. Поведение платформы для мобильного устройства унифицировано с поведением платформы для ПК.

Устранено некорректное поведение системы.

Специальные возможности мобильного устройства.
Реализована возможность проверки фактической возможности работы с глобальными ключами контактов, календарей и событий календарей на различных мобильных операционных системах.

Для объекта МенеджерКонтактов реализован метод ПоддерживаютсяГлобальныеКлючиКонтактов().

Для объекта МенеджерКалендарей реализованы методы ПоддерживаютсяГлобальныеКлючиКалендарей() и ПоддерживаютсяГлобальныеКлючиСобытий().

У конструктора объекта ДанныеКонтактаУчетнойЗаписи прекращена поддержка параметра ГлобальныйКлючКонтакта. Значения свойств, описывающих глобальные ключи контактов, календарей и событий календарей, зависят от результата работы соответствующей функции проверки возможности работы с глобальными ключами. Если работа с глобальным ключом не поддерживается - соответствующее значение возвращает пустую строку.

Реализована доступность объектов ЛокальныйКлючКонтакта, ЛокальныйКлючКалендаря, ЛокальныйКлючСобытияКалендаря на сервере мобильного приложения.

Возможность работа с глобальными ключами контактов, календарей и событий календаря зависела от того, на какой платформе функционирует мобильное приложение. Разработчик не имел возможности проверить возможность работы с глобальными ключами из встроенного языка.

Объекты ЛокальныйКлючКонтакта, ЛокальныйКлючКалендаря, ЛокальныйКлючСобытияКалендаря были недоступны на сервере мобильного приложения.

Поведение приведено в соответствие с общей схемой работы с возможностями, доступными не на всех мобильных устройствах или операционных системах.
Предопределенные данные.
В мобильной платформе реализована поддержка методов глобального контекста ИнициализироватьПредопределенныеДанные(), УстановитьОбновлениеПредопределенныхДанныхИнформационнойБазы(), ПолучитьОбновлениеПредопределенныхДанныхИнформационнойБазы(). Данная функциональность не поддерживалась на мобильной платформе.Унифицированы возможности мобильной платформы и платформы для персонального компьютера в части работы с предопределенными данными.
Управляемая форма.
Реализованы следующие возможности интерфейса для управляемых форм в мобильной платформе:
  • Возможность создания сворачиваемых групп.
  • Управление отображением элемента управляемой формы Страницы в случае, когда отображаются либо закладки либо текущая страница. В этом случае реализована возможность из встроенного языка переключать режим отображения между отображением закладок или конкретной страницы. Реализовано свойство этого элемента ТекущееСостояниеСтраниц.
  • Возможность управления видимостью кнопок очистки и открытия значения поля ввода управляемой формы. Реализованы свойства поля ввода управляемой формы АвтоОтображениеКнопкиОчистки и АвтоОтображениеКнопкиОткрытия.
  • Возможность управления высотой многострочного поля ввода. Реализовано свойство этого элемента ВариантУправленияВысотой.
  • Возможность программного перехода в режим редактирования элемента управляемой формы. Реализован метод УправляемаяФорма.НачатьРедактированиеЭлемента().
  • Возможность управлять некоторыми сервисными возможностями для расширения поля управляемой формы для поля ввода:
    • Автоматическое исправление текста. Реализовано свойство АвтоИсправлениеПриВводеТекста.
    • Проверка правописания при вводе текста. Реализовано свойство ПроверкаПравописанияПриВводеТекста.
    • Автоматическое изменение регистра текста при вводе текста. Реализовано свойство АвтоИзменениеРегистраПриВводеТекста.
    • Управление видом клавиатуры, используемой для ввода данных. Реализовано свойство СпециальныйРежимВводаТекста.
    • Управление текстом на кнопке ввода экранной клавиатуры. Реализовано свойство ТекстКнопкиВводаЭкраннойКлавиатуры.
  • Возможность управления высотой таблицы управляемой формы, которая отображает данные, отличные от динамического списка. Реализовано свойство таблицы управляемой формы ВариантУправленияВысотой.
  • Возможность управлять положением строки поиска. Стало возможно явным образом указать расположение строки поиска в заголовке формы или отображение после жеста вниз на заголовке таблицы.

Команды, которые присутствуют в командной панели, отсутствуют в меню Еще.

Команды контекстного меню строки таблицы могут размещаться в меню Еще, если они (команды) не помещаются в отведенное для меню место экрана.

Изменено отображение фиксированных областей табличного документа.

Данные возможности не предоставлялись.

Команды, расположенные на командной панели, также дублировались в меню Еще.

Выполнялась попытка разместить все команды контекстного меню строки таблицы на экране.

Фиксированные области табличного документа отображались по-другому.

Интерфейс мобильной платформы стал лучше соответствовать подходам к разработке интерфейсов мобильных приложений.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Специальные возможности мобильного устройства.
Поведение при вызове метода Сигнал() реализовано аналогично вызову метода СредстваМультимедиа.ВоспроизвестиЗвуковоеОповещение(ЗвуковоеОповещение.ПоУмолчанию).Метод Сигнал() не выполнял никаких действий.Стало возможно использовать метод Сигнал() для воспроизведения стандартного звукового оповещения мобильного устройства.
В документации данное изменение описано здесь.
Средства администрирования.
Для мобильного приложения реализованы следующие возможности:
  • Выполнение тестирования и исправления информационной базы.
  • Выполнение резервного копирования информационной базы.
  • Возможность настройки автоматического резервного копирования (по умолчанию включено) перед обновлением приложения, что позволяет восстановить информационную базу, если во время обновления приложения произошли какие-либо проблемы.
  • Возможность настройки автоматического резервного копирования информационной базы.

Резервное копирование выполняется на накопитель мобильного устройства.

Доступа к данным возможностям выполняется через диалог редактирования свойств приложения (кнопка Администрирование в данном диалоге).

Данные возможности не предоставлялись.Расширены возможности администрирования мобильного приложения.
В документации данное изменение описано здесь и здесь.
Специальные возможности мобильного устройства.
Мобильная платформа более не поддерживает работу с сервисом Apple iAd в связи с закрытием последнего. На платформах iOS и Android поддерживается работа с рекламным сервисом Google AdMob. Сборщик мобильных приложений позволяет указать, что данная конфигурация использует рекламу. Это указание позволит сборщику мобильных приложений использовать для сборки соответствующий вариант мобильной платформы.

Не требуется переработка мобильного приложения, работающего под управлением ОС iOS, в том случае, если в нем была реализована поддержка обоих сервисов. Если была реализована поддержка только сервиса Apple iAd - необходимо доработка мобильного приложения.

Мобильная платформа поддерживала работу с сервисами Apple iAd и Google AdMob.Прекращена поддержка закрытого сервиса (Apple iAd).
В документации данное изменение описано здесь.
Сборщик мобильных приложений.
При сборке мобильного приложения для платформы iOS, реализована сборка версии для использования на эмуляторе.Сборщик мобильных приложений не выполнял сборку версии для эмулятора iOS.Расширены возможности разработки мобильного приложения при использовании платформы iOS.

Оглавление

Обновление используемых библиотек

Оглавление

Переход с предыдущей версии на версию 8.3.9

Оглавление

Версия 8.3.8

Версия 8.3.8 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v838doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.7. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5 и 8.3.6. +Возможность запуска конфигураций, разработанных в версии 8.3.7 и более младших, в версии 8.3.8, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.8 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.8, при необходимости, использовать для работы с информационной базой и версию 8.3.7. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Работа с Интернет.
Реализована поддержка работы с каталогом доверенных сертификатов операционной системы Linux (/etc/ssl/certs, /etc/pki/tls/certs). Реализован объект СертификатыУдостоверяющихЦентровОС, скрывающий используемую операционную систему при работе с сертификатами. Реализован объект СертификатыУдостоверяющихЦентровLinux, предназначенный для кеширования информации о сертификатах в ОС Linux. Рекомендуется использование объекта СертификатыУдостоверяющихЦентровОС.

В качестве значений параметра СертификатыУдостоверяющихЦентров конструктора объекта ЗащищенноеСоединениеOpenSSL могут передаваться объекты СертификатыУдостоверяющихЦентровLinux и СертификатыУдостоверяющихЦентровОС.

Сертификаты NSS более не поддерживаются системой.

Для работы с сертификатами в ОС Linux использовалось хранилище сертификатов NSS.Возможность работы в ОС Linux, с помощью тонкого клиента, с информационными базами, опубликованными на ресурсах, доступ к которым требует использования клиентских сертификатов.
В документации данное изменение описано здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
Системные требования.
Реализована поддержка веб-сервера Apache 2.4 для ОС Windows и Linux.

Для утилиты webinst реализован ключ -apache24. +

Данная возможность не предоставлялась.

Поддерживались только веб-сервера Apache 2.0 и 2.2.

Расширен список поддерживаемых веб-серверов.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Автоматизированное тестирование.
В диалоге О программе (и заголовке окна клиентского приложения) реализовано информирование о том, что клиентское приложение является клиентом или менеджером тестирования.

Реализован метод ТестируемоеПриложение.УстановитьРезультатДиалогаВыбораФайла() для установки результата работы диалога выбора файлов. Метод ТестируемоеПриложение.ПолучитьПодчиненныеОбъекты() включает в результирующую коллекцию окна, содержащие текстовые или табличные документы.

Реализован метод ТестируемаяФорма.ВыполнитьВыборИзСписка() для выполнения выбора из списка, открытого с помощью метода УправляемаяФорма.ВыбратьИзСписка().

Реализован метод ТестируемаяФорма.ВыполнитьВыборИзМеню() для выполнения выбора из меню, открытого с помощью метода УправляемаяФорма.ВыбратьИзМеню().

Для объекта ТестируемоеПолеФормы реализована поддержка расширения поля текстового документа.

Для объекта ТестируемоеПолеФормы реализована поддержка расширения поля форматированного документа. Для объекта ТестируемоеПолеФормы реализованы методы ПолучитьHTML() (возвращает содержимое форматированного документа) и ВвестиHTML() (имитирует ввод текста в форматированный документ).

Реализован метод ТестируемоеПолеФормы.ЗаписатьСодержимоеВФайл(), выполняющий запись документа в файл на диск, аналогично выполнению команды Сохранить. Метод доступен для расширений табличного документа, текстового документа и форматированного документа.

Данные возможности не предоставлялись.Расширены возможности механизма автоматизированного тестирования.
В документации данное изменение описано здесь, здесь и здесь.
Средства разработки.
Реализована возможность выполнять сохранение/восстановление настроек окна сравнения/объединения конфигураций. Реализован флажок, управляющий автоматическим сохранением настроек формы.

Переработана форма сравнения/объединения модулей: реализована командная панель, на которой располагаются команды работы с редактором.

В настройках фильтров просмотра реализован фильтр Показывать только дважды измененные свойства.

Данные возможности не предоставлялись.Повышен комфорт прикладного разработчика, часто выполняющего операции сравнения/объединения с настройками, отличающимися от стандартных.
В документации данное изменение описано здесь и здесь.
Средства разработки.
Реализованы возможности выполнения следующих операций с помощью команд пакетного запуска конфигуратора:
  • Сравнение конфигураций (/CompareCfg).
  • Объединение конфигураций (/MergeCfg).
  • Выполнение захвата объектов в хранилище конфигурации (/ConfigurationRepositoryLock).
  • Выполнение отмены захвата объектов в хранилище конфигурации (/ConfigurationRepositoryUnlock).
  • Помещение измененных объектов в хранилище конфигурации (/ConfigurationRepositoryCommit).
  • Установка метки на версию хранилища (/ConfigurationRepositorySetLabel).

Для ключа командной строки пакетного запуска конфигуратора /UpdateCfg реализованы параметры:

  • -DumpListOfTwiceChangedProperties - позволяющий сформировать список дважды измененных объектов.
  • -IncludeObjectsByUnresolvedRefs - если в настройках есть объекты, не включенные в список объединяемых и отсутствующие в основной конфигурации, но на которые есть ссылки из объектов, включенных в список, то такие объекты также помечаются для объединения, и выполняется попытка продолжить объединение.
  • -ClearUnresolvedRefs - ссылки на объекты, не включенные в список объединяемых - очищаются.
  • -Settings - указать имя файла с настройками объединения.
  • -force - определяет необходимость автоматически разрешать ряд проблем при объединении: поведение при наличии заблокированных объектов; поведение при предупреждение о наличии дважды измененных свойств, для которых не выбран режим объединения; поведение при предупреждении об удаляемых объектах, на которые есть ссылки в объектах, не участвующих в объединении.

Для ключа командной строки пакетного запуска конфигуратора /ConfigurationRepositoryUpdateCfg реализован параметр -objects, позволяющий выполнить операцию не со всей конфигурацией, а только с ограниченным набором объектов.

Данные возможности не предоставлялись.

При использовании ключа командной строки пакетного запуска конфигуратора /ConfigurationRepositoryUpdateCfg операция выполнялась только со всей конфигурацией.

Упрощен процесс автоматизированного обновления прикладных решений.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с запросами.
Во время отладки запросов реализована возможность работы с временными таблицами: просмотр списка временных таблиц, структуры временных таблиц и содержимого временных таблиц.

Реализован метод Запрос.ВыполнитьПакетСПромежуточнымиДанными(). Реализовано свойство МенеджерВременныхТаблиц.Таблицы.

Данная возможность не предоставлялась.Расширены возможности разработчика при отладке прикладного решения, особенно при отладке сложных пакетных запросов.
В документации данное изменение описано здесь и здесь.
Внешние источники данных.
Реализован метод ВнешнийИсточникДанныхМенеджер.ТранзакцияАктивна(), позволяющий понять, что внешний источник данных находится в состоянии транзакции Данная возможность не предоставлялась.Стало возможно определить, что внешний источник данных находится в состоянии транзакции.
В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Реализована работа с Web-сервисами, поддерживающими стандарт MTOM (см. здесь).Данная возможность не предоставлялась.

Работа с Web-сервисами, поддерживающими стандарт MTOM была невозможна.

Расширены возможности интеграции системы «1С:Предприятие» с различными внешними системами. Стало возможно использовать Web-сервисы, поддерживающие оптимизированную передачу двоичных данных, при этом уменьшается объем сетевого трафика и потребление оперативной памяти.
В документации данное изменение описано здесь.
Интерфейс OData.
Для стандартного интерфейса OData:
  • Реализован отбор по составным типам;
  • Реализованы лямбда-выражения;
  • Расширены возможности формирования отбора получаемых данных:
    • реализована опция запроса $skip, позволяющая пропустить несколько первых записей в результате запроса;
    • реализована опция запроса $inlinecount, позволяющая включить в результат запроса размер получившейся выборки;
    • реализована опция $orderby, позволяющая указать порядок записей в результате запроса;
    • реализована опция $count, позволяющая запросить, сколько записей вернет запрос.
  • Расширен состав функций, которые могут использоваться при выполнении запроса:
    • функции работы со строками;
    • функции работы с датой и временем;
    • функция проверки соответствия значения указанному типу;
    • функция приведения типа.
Стандартный интерфейс OData предоставлял более ограниченные возможности.Представление объектов «1С:Предприятия» стало более полно соответствовать стандарту OData.

+

В документации данное изменение описано здесь и здесь.
Расширение конфигурации.
Средства разработки.
Для объектов конфигурации реализован метод РасширениеКонфигурации(), позволяющий определить расширение конфигурации, в котором расположен интересующий объект конфигурации.

Для метода МенеджерРасширенийКонфигурации.Получить() реализован параметр ИсточникРасширенийКонфигурации, позволяющий указать, какой список расширений требуется получить (расширения только из базы данных; расширения, действующие в текущем сеансе или расширения, не прошедшие проверку при подключении или отключенные профилями безопасности).

Данные возможности не предоставлялись.Упрощена работа с расширениями конфигурации из встроенного языка.
Расширение конфигурации.
Реализовано свойство расширения конфигурации РежимСовместимостиРасширенияКонфигурации. Данное свойство позволяет ограничивать возможности расширения используемой версией платформы «1С:Предприятие», используя для редактирования расширения более старшие версии платформы, с большими возможностями расширений.

Реализована возможность создания в расширении конфигурации следующих объектов:

  • Общие макеты;
  • Общие команды;
  • Группы команд;
  • Общие картинки;
  • Реквизиты, табличные части и реквизиты заимствованных табличных частей:
    • Отчетов
    • Обработок.
  • Формы, макеты и команды заимствованных объектов:
    • Планы обмена;
    • Критерии отбора;
    • Хранилища настроек;
    • Справочники;
    • Документы;
    • Журналы документов;
    • Перечисления;
    • Отчеты;
    • Обработки;
    • Регистры бухгалтерии;
    • Регистры накопления;
    • Регистры расчета;
    • Регистры сведений;
    • Планы видов характеристик;
    • Планы счетов;
    • Планы видов расчетов;
    • Бизнес-процессы;
    • Задачи;
    • Внешние источники данных:
      • Таблицы;
      • Кубы;
      • Таблицы измерений.

Реализована возможность в расширении изменять свойства заимствованных объектов конфигурации, описывающих основные и вспомогательные формы.

Для заимствованного отчета реализована возможность изменять значение свойства Основная схема компоновки данных.

Для подсистем, групп команд, команд, общих команд в расширении возможно изменять значение свойства Картинка.

Контекстная подсказка в редакторе модулей выводится только для объектов входящих в текущее расширение.

Данные возможности не предоставлялись.

Контекстная подсказка в редакторе модулей выводилась по объединению расширяемой конфигурации и расширения.

Расширение конфигурации стало предоставлять больше возможностей.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Средства разработки.
Выгрузка/загрузка конфигурации в файлы.
Реализована возможность выгружать внешнюю обработку/отчет в файлы (в формате XML). Выгрузка возможна с помощью команд меню Файл конфигуратора (Сохранить, Сохранить как, Сохранить копию). При операции выгрузки невозможно изменить тип объекта (сделать внешнюю обработку внешним отчетом и наоборот). Загрузка возможна с помощью команды меню Файл - Открыть.

Реализована возможность выгрузки в файлы и обратной загрузки в диалоге редактирования внешней обработки/отчета. Команды доступны в меню Действия этого диалога.

Реализована возможность выполнить сравнение внешней обработки/отчета с внешней обработкой/отчетом, сохраненной на диске в виде файлов формата XML. Операция доступна с помощью команды Действия - Сравнить, объединить с внешней обработкой, отчетом диалога редактирования внешней обработки/отчета.

Реализована возможность выполнять выгрузку/загрузку внешней обработки/отчета в файлы с помощью ключей командной строки пакетного запуска конфигуратора. Реализованы ключи /DumpExternalDataProcessorOrReportsToFiles и /LoadExternalDataProcessorOrReportsFromFiles.

Выгрузка может выполнять в линейном или иерархическом форматах. Выгрузка выполняется только в версии 2.0 формата выгрузки. При загрузке формат загрузки определяется автоматически.

Данные возможности не предоставлялись.

Внешние обработки/отчеты можно было сохранять только в бинарном формате.

Расширены возможности работы с внешними обработками/отчетами с использованием внешних систем контроля версий. Стало возможно использовать внешние средства для модификации и создания внешних отчетов и обработок.
В документации данное изменение описано здесь и здесь.
Динамический список.
Для динамического списка реализована поддержка работы с пакетным запросом. Конструктор запроса динамического списка не поддерживает редактирование пакетного запроса.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Работа динамического списка с пакетным запросом не поддерживалась.Расширены возможности динамического списка.
В документации данное изменение описано здесь.
Средства разработки.
В синтакс-помощник добавлена информация о методе, который является обработчиком запроса HTTP-сервиса. Упрощен доступ разработчика к информации о типах параметра и возвращаемого значения.В синтакс-помощнике отсутствовала информация о методе, который является обработчиком запроса HTTP-сервиса. Разработчик не мог быстро получить информацию о типах параметра и возвращаемого значения.Упрощен доступ разработчика к важной для него информации.
Отображение информации.
Управляемая форма.
Для системного перечисления ЦветаСтиля реализованы следующие значения:
  • для оформления рамки кнопки формы и командой панели - ЦветРамкиКнопки;
  • для оформления фона шапки таблицы - ЦветФонаШапкиТаблицы;
  • для оформления текста шапки таблицы - ЦветТекстаШапкиТаблицы;
  • для оформления фона подвала таблицы - ЦветФонаПодвалаТаблицы;
  • для оформления текста подвала таблицы - ЦветТекстаПодвалаТаблицы.
Для оформления элементов формы использовались следующие значения системного перечисления ЦветаСтиля:
  • для оформления рамки кнопки формы и командой панели - ЦветРамки;
  • для оформления фона шапки таблицы - ЦветФонаКнопки;
  • для оформления текста шапки таблицы - ЦветТекстаКнопки;
  • для оформления фона подвала таблицы - ЦветФонаКнопки;
  • для оформления текста подвала таблицы - ЦветТекстаКнопки.
Расширены возможности использования стилевых элементов.
Отображение информации.
Управляемая форма.
Размеры кнопок формы и командной панели отличаются от аналогичных размеров в предыдущих версиях системы.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Размеры кнопок формы и командной панели имели другой размер. +Улучшено отображение кнопок. +
Технологический журнал.
Для события технологического журнала <CALL> реализовано свойство Usr, содержащее имя аутентифицированного пользователя информационной базы.У события технологического журнала <CALL> отсутствовало свойство Usr.Повышена информативность технологического журнала для события <CALL>.
Работа с ZIP-архивами.
Для конфигурационного файла conf.cfg реализован параметр FileNamesEncodingInZipFile, позволяющий управлять кодировкой, в которой будут записываться имена файлов в zip-архивах, сформированных с помощью системы «1С:Предприятие». Параметр может принимать значения UTF8 (кодировка только UTF8) или OSEncodingWithUTF8 (кодировка используемой ОС и UTF8, используется по умолчанию).

Если значение параметра установить в значение UTF8, то имена файлов, содержащие национальные символы, будут отображаться некорректно при помощи встроенного архиватора ОС Windows XP/2003/2008/7 и объекта ЧтениеZipФайла системы «1С:Предприятие» версии 8.3.6 и младше. При этом в OS X такие имена файлов будут отображаться корректно.

Если значение параметра установить в значение OSEncodingWithUTF8, то имена файлов, содержащие национальные символы, будут отображаться некорректно при помощи встроенного архиватора OS X, но в других случаях проблем не будет.

Имена файлов в zip-архивах, сформированных с помощью системы «1С:Предприятие», сохранялись в кодировке используемой ОС и UTF8 (без возможности настройки).Стало возможно управлять кодировкой имен файлов в архивах, формируемых системой «1С:Предприятие».
В документации данное изменение описано здесь.
Работа с СУБД.
Системные требования.
Реализована поддержка СУБД IBM DB2 11.1.СУБД IBM DB2 11.1 не поддерживалась.Реализована поддержка СУБД IBM DB2 11.1.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Средства администрирования.
Реализована утилита административной консоли (1cv8a). Утилита содержит в себе часть функций механизма тестирования и исправления, доступного в конфигураторе, и предназначена для ускорения проверки и исправления определенных проблем:
  • Тестирование и исправление для таблиц узлов планов обмена.
  • Тестирование и исправление хеш-полей таблиц информационной базы.

Утилита доступна для следующих операционных систем:

  • ОС Windows - устанавливается в составе компонента Дополнительные функции администрирования.
  • ОС Linux - устанавливается безусловно в составе пакета 1c_enterprise83-client-8.3.*. Зависит от пакета 1c_enterprise83-server-8.3.* одинаковой версии.
  • OS X - устанавливается безусловно при установке системы «1С:Предприятие».
Данная возможность не предоставлялась.

Часть возможностей была доступна при выполнении операции тестирования и исправления с помощью конфигуратора, но занимала значительно больше времени.

Стало возможно исправлять некоторые проблемы, возникающие с информационной базой, без запуска конфигуратора и за более короткое время. Это обусловлено тем, что утилита административной консоли выполняет обработку только проблемных объектов и при этом выполняет ограниченный набор исправлений.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Встроенный язык.
Расширение конфигурации.
Внешние отчеты и обработки.
Средства администрирования.
Реализован механизм защиты от опасных действий. При выполнении потенциально опасного действия система выдает предупреждение, содержащее информацию о выполняемом действии и потенциальной опасности этого действия. К потенциально опасным действиям относятся:
  • Загрузка внешнего отчета, обработки или расширения конфигурации.
  • Загрузка или обновление конфигурации/расширения.
  • Доступ из внешнего отчета/обработки или расширения к следующим возможностям:
    • Исполнение команды операционной системы.
    • Управление пользователями.
    • Загрузка внешней компоненты.

Пользователь имеет возможность разрешить или отклонить потенциально опасное действие. Если действие разрешено, в ряде случаев может потребоваться повторно выполнить разрешенное действие.

При загрузке конфигурации или обновлении конфигурации из файла .cfu предупреждение формируется в существующих диалогах конфигуратора.

В свойствах пользователя информационной базы реализовано свойство ПользовательИнформационнойБазы.ЗащитаОтОпасныхДействий. Реализовано свойство РасширениеКонфигурации.ЗащитаОтОпасныхДействий. Для метода Подключить() объектов ВнешниеОбработки и ВнешниеОтчеты реализован параметр ЗащитаОтОпасныхДействий. В диалоге управления расширениями конфигурации (в конфигураторе и в стандартных функциях) реализован флажок Защита от опасных действий.

Реализована возможность указать список информационных баз, при работе с которыми защита от опасных действий будет отключаться. Для файла conf.cfg реализован параметр DisableUnsafeActionProtection.

Отсутствовал механизм предупреждения о выполнении потенциально опасных действий. Предоставлялась возможность запретить запуск внешних обработок или отчетов с помощью прав доступа и настроек профилей безопасности.Повышена безопасность работы системы при использовании потенциально опасного кода.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Встроенный язык.
Расширение конфигурации.
Внешние отчеты и обработки.
Средства администрирования.
При срабатывании защиты от опасных действий на стороне тонкого или толстого клиентских приложений, выполнение продолжается после выполнения потенциально опасного действия так, как будто никаких остановок выполнения не происходило. Если пользователь отказался от выполнения потенциально опасного действия, то генерируется исключение, которое можно перехватить с помощью встроенного языка.

При работе в веб-клиенте и на стороне сервера «1С:Предприятие» поведение не изменилось.

В тонком и толстом клиентских приложениях, защита от опасных действий при исполнении клиентского кода, в котором находится потенциально опасное действие, прерывала работу кода и показывала сообщение пользователю для принятия решения о разрешении или запрещении действия. При этом независимо от принятого пользователем решения исполнение кода не возобновлялось и пользователь должен был заново перезапустить действие.Упрощено поведение системы при срабатывании защиты от потенциально опасных действий при работе на стороне тонкого или толстого клиентских приложений.
Системные требования.
Реализована поддержка работы «1С:Предприятия» под управлением ОС Microsoft Windows Server 2016 (x86-64).Не поддерживалась работа «1С:Предприятия» под управлением ОС Microsoft Windows Server 2016 (x86-64).Расширен список поддерживаемых операционных систем.
В документации данное изменение описано здесь, здесь и здесь.
Системные требования.
Реализована поддержка дистрибутива Astra Linux Special Edition 1.5.Данный дистрибутив не поддерживался.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь и здесь.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Интерфейс.
Изменен внешний вид полос прокрутки в интерфейсе Такси.Полосы прокрутки в интерфейсе Такси имели другой внешний вид.Полосы прокрутки в управляемых формах стали лучше заметны пользователю.
Интерфейс.
В диалоге поиска, который открывается в таблице управляемой формы, связанной с реквизитом типа ДанныеФормыКоллекция, изменен порядок полей: вначале идет поле Где искать, затем Что искать.В диалоге поиска, который открывается в таблице управляемой формы, связанной с реквизитом типа ДанныеФормыКоллекция, поля следовали в следующем порядке: вначале идет поле Что искать, затем Где искать.Унифицирован внешний вид диалогов поиска в таблицах управляемой формы, связанных с разными данными.
Управляемая форма.
Для панели навигации управляемой формы (в интерфейсе Такси) реализованы клавиатурные сокращения:
  • Переход к панели - Alt+4;
  • Переход на следующий/предыдущий элемент панели - Tab/Shift+Tab или <стрелка вправо>/<стрелка влево>. При достижении первого/последнего элемента панели перемещение на последний/первый элемент панели не выполняется;
  • Переход на первый элемент панели - Home;
  • Переход на последний элемент панели - End;
  • Выход из режима навигации по панели - Esc.
Работа с панелью навигации управляемой формы (в интерфейсе Такси) с клавиатуры был недоступна.Повышен комфорт использования клиентских приложений «1С:Предприятия» при использовании интерфейса Такси.
В документации данное изменение описано здесь.
Интерфейс.
В интерфейсе Такси изменено отображение вертикальной полосы прокрутки в динамическом списке. Собственно полоса прокрутки более не отображается. Для манипуляций списком служат несколько кнопок (в начало списка, в конец списка, на страницу вперед, на страницу назад), расположенные в правой нижней части таблицы формы, связанной с динамическим списком.В таблице, связанной с динамическим списком, присутствовала вертикальная полоса прокрутки, которая не предоставляла адекватной информации для навигации по списку.Улучшены способы навигации по динамическому списку.
Интерфейс.
Динамический список.
В контекстное меню таблицы, связанной с динамическим списком, у которого основной таблицей выступает список документов или журнал документов, добавлены команды Провести и Отменить проведение.Команды Провести и Отменить проведение были доступны только с помощью меню Еще таблицы, связанной с динамическим списком, у которого основной таблицей выступает список документов или журнал документов.Упрощено выполнение операций проведения и отмены проведения в динамическом списке.
Интерфейс.
Динамический список.
В контекстном меню таблицы управляемой формы, связанной с основным реквизитом управляемой формы списка, для которой есть команды Создать на основании, реализовано одноименное подменю со списком соответствующих команд.Команды ввода на основании были доступны только из командной панели таблицы управляемой формы, связанной с основным реквизитом управляемой формы списка.Упрощено выполнение операции ввода на основании в динамическом списке.

+

Интерфейс.
В тонком и толстом клиентских приложениях, в управляемом режиме работы, во всех вариантах интерфейса исключена возможность включения строки поиска в области системных команд.Имелась возможность включения строки поиска в области системных команд.Отключена возможность использования неработающего механизма.
Интерфейс.
В области системных команд реализовано отображение имени текущего пользователя. Имя пользователя является гиперссылкой, нажатие на которую отображает диалог с информацией о текущем пользователе. В этом диалоге также предоставляется возможность завершить работу с клиентским приложением, при этом одновременно будет выполняться отмена аутентификации OpenID, если аутентификация пользователя выполнялась с помощью этого протокола (т.е. одна команда и для завершения работы приложения и для отмены аутентификации OpenID). Если в информационной базе отсутствуют пользователи, то имя пользователя не отображается.

Реализована возможность задания в .vrd-файле (в том числе из диалога публикации в конфигураторе) URL для перехода после завершения работы веб-клиента. Реализован элемент <exitURL> для элемента <point> файла default.vrd.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Завершение работы было доступно с помощью команды меню Файл. Отмену аутентификации OpenID можно было выполнить с помощью команды меню Файл.Адаптация поведения клиентского приложения к привычному поведению веб-приложений.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Веб-клиент.
Управляемая форма.
В веб-клиенте улучшено выполнение операции отмены/возврата при работе в поле текстового документа и поле ввода.

При использовании веб-браузера Safari для Apple iPad, операция отмены выполняется сразу для целого слова, а не посимвольно, как в других веб-браузерах.

В веб-клиенте операции отмены/возврата работали с недостатками.Повышен комфорт работы с текстом в веб-клиенте.
Клиентское приложение.
Реализована поддержка списков переходов при работе на ОС Windows 7 и выше, а также на ОС Linux с оболочкой рабочего стола Unity. В список переходов автоматически попадают последние используемые информационные базы, которые в дальнейшем пользователь может использовать без открытия окна программы запуска.

Реализована возможность размещать кнопки (из встроенного языка) в окне предварительного просмотра приложения в панели задач при работе на ОС Windows 7 и выше (аналогично кнопкам управления воспроизведением Проигрывателя Windows Media).

Реализована возможность устанавливать картинку или число (из встроенного языка) , которые будут отображаться в правом нижнем углу картинки приложения на панели задач на ОС Windows 7 и выше, а также на ОС Linux с оболочкой рабочего стола Unity.

Реализована возможность осуществить мигание картинки приложения (из встроенного языка) на панели задач на ОС Windows XP и выше, а также на ОС Linux с оболочкой рабочего стола Unity.

Реализован объект МенеджерПанелиЗадачОС.

Данная возможность не предоставлялась.Повышено удобство работы с приложением в некоторых поддерживаемых операционных системах.
В документации данное изменение описано здесь, здесь и здесь.
Клиентское приложение.
Интерфейс.
Реализована невизуальная доступность интерфейса «1С:Предприятия» для пользователей с ограничениями по зрению. Данная возможность доступна при работе на ОС Windows XP и выше. Для работы используется программа экранного доступа NVDA (см. здесь).

Невизуальная доступность обеспечивается только для управляемых форм, в тонком и толстом клиентских приложениях в интерфейсе Такси.

Данная возможность не предоставлялась.Для пользователей с ограничениями по зрению использование «1С:Предприятия» стало более комфортным за счет озвучивания экранных элементов интерфейса.
В документации данное изменение описано здесь, здесь и здесь.
Динамический список.
В динамическом списке реализована возможность добавления дочерних полей для полей составного типа с помощью диалога пользовательской настройки формы (Еще - Изменить форму). Добавление доступно для полей, имеющих в составе своего типа хотя бы один ссылочный тип.

В динамическом списке, с помощью диалога пользовательской настройки формы (Еще - Изменить форму), было невозможно добавлять дочерние поля для полей составного типа. Расширены возможности отображения информации в динамическом списке.
Веб-клиент.
Работа с файлами.
В веб-клиенте, при использовании методов СоздатьКаталог() и НачатьСозданиеКаталога(), пользователю задается вопрос Создать каталог ИмяКаталога?

При использовании методов ЗапроситьРазрешениеПользователя() и НачатьЗапросРазрешенияПользователя(), вопрос о создании каталога (при необходимости запросить такое разрешение) будет добавлен в итоговый вопрос пользователю.

При создании каталогов в веб-клиенте не задавалось вопросов пользователю.Поведение системы приведено в соответствие с общей схемой безопасной работы с файловой системой в веб-клиенте.
В документации данное изменение описано здесь.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Кластер серверов.
Оптимизирована работа с сеансовыми данными. Исключены периодические замедления в работе пользователей при высокой нагрузке на хранилище сеансовых данных в клиент-серверном варианте работы.Работа с сеансовыми данными была недостаточно оптимальной. Периодически случались замедления работы пользователей в клиент-серверном варианте работы при высокой нагрузке на хранилище сеансовых данных.Работа системы стала более комфортной.
Интерфейс.
В тонком клиенте уменьшено влияние количества открытых форм на открытие новой формы.В тонком клиенте на открытие новой формы влияло общее количество открытых форм.Ускорено открытие новой формы в случае большого количества открытых форм.
Работа с запросами.
В языке запросов реализовано упрощение некоторых выражений вида <ВЫРАЖЕНИЕ> ИЛИ ИСТИНА.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В языке запросов не выполнялось дополнительных оптимизаций текстов запросов.В результате оптимизации может быть ускорена работа динамических списков и запросов ограничения доступа к данным за счет выбора СУБД более простого плана запроса.
Средства разработки.
Ускорены операции выгрузки/загрузки конфигурации в файлы в том случае, если конфигурация содержит большое количество управляемых форм.Операции выгрузки/загрузки конфигурации в файлы выполнялись недостаточно быстро.При хранении конфигурации во внешней системе, ускорены операции обмена между информационной базой и этой системой.
Работа с базой данных.
Ускорена работа с файловой информационной базой, при одновременном выполнении следующих условий:
  • с информационной базой работает одно клиентское приложение (в том числе конфигуратор);
  • клиентское приложение и база данных расположены на разных компьютерах;
  • на обоих компьютерах поддерживается протокол SMB 2.1 (используется ОС Windows 7 и выше);
  • при работе формируется значительное число транзакций записи в базу данных.
В указанных условиях работа с файловой информационной базой была недостаточной.Ускорено выполнение обновления конфигурации базы данных в файловом варианте, в том случае, когда конфигуратор и база данных расположены на разных компьютерах.
Обмен данными.
Ускорено создание начального образа информационной базы.

Ускорено чтение записей независимого непериодического регистра сведений при формировании начального образа информационной базы.

Создание начального образа информационной базы выполнялось недостаточно быстро.Ускорено формирование информационной базы для нового дочернего узла в распределенной информационной базе.
Работа с СУБД.
Оптимизированы операции удаления записей из временных таблиц при выполнении некоторых операций в СУБД PostgreSQL и IBM DB2.Операции удаления записей из временных таблиц при выполнении некоторых операций в СУБД PostgreSQL и IBM DB2 работали недостаточно быстро.Ускорена работа системы при работе с временными таблицами.
Работа с СУБД.
При работе в клиент-серверном варианте с использованием СУБД Oracle Database запросы, содержащие выражения … В (&СписокЗначений) исполняются по-другому, если количество значений в списке превышает 100 элементов.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

+

+

+

При работе в клиент-серверном варианте с использованием СУБД Oracle Database запросы, содержащие выражения … В (&СписокЗначений) исполнялись по-другому, если количество значений в списке превышает 1 000 элементов.При работе на СУБД Oracle Database может повысится производительность в некоторых сценариях использования.
Средства администрирования.
Технологический журнал.
Кластер серверов.
Работа с СУБД.
Оптимизировано получение информации о блокировках СУБД. Время получения этой информации не зависит от количества информационных баз в кластере серверов.

Реализован сервис кластера серверов, выполняющий сбор информации о блокировках СУБД. Сервис называется AuxiliaryService (Сервис вспомогательных функций кластера).

Реализована возможность управлять сбором информации о блокировках СУБД в технологическом журнале (элемент <DBMSLOCKS>). Включение сбора информации о блокировках ведет к повышенной нагрузке на СУБД.

Время получения информации о блокировках СУБД зависело от количества информационных баз в кластере серверов.

Отсутствовала возможность выполнять сбор информации о блокировках СУБД с помощью технологического журнала.

Расширены возможности диагностики работы с базой данных.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства администрирования.
Работа с базой данных.
Оптимизирована работа файлового варианта информационной базы, для чего доработан формат хранения данных в файловой базе данных (формат версии 8.3.8). Реализована возможность изменять размер страницы файла информационной базы (1Cv8.1CD). Размер страницы может быть 4096, 8192, 16384, 32768 и 65536 байт. При использовании версии 8.3.8 с размером страницы 8192 байта и выше, размер внутреннего файла в базе данных не может превышать 6 Гбайт (для любого размера страницы, большего 4096 байт).

Версия 8.3.8 может работать с информационными базами, созданными в предыдущих версиях (формат версии 8.2.14) без нарушения совместимости с предыдущими версиями.

По умолчанию новая информационная база создается в формате версии 8.2.14. Реализован параметр DBFormatVersion файла conf.cfg, с помощью которого можно управлять форматом создаваемой информационной базы в файловом варианте.

Для строки соединения с информационной базой реализованы параметры DBFormat и DBPageSize, позволяющие управлять форматом создаваемой информационной базы и размером страницы.

При необходимости выполнить перенос данных между различными форматами, можно воспользоваться либо переносом через файл .dt (при условии, что база-приемник имеет нужный вариант формата) либо конвертацией файла информационной базы с помощью утилиты cnvdbfl. Утилита cnvdbfl может выполнять конвертацию файла информационной базы с изменением размера страницы.

База данных имела только один формат: версии 8.2.14. Размер страницы файла информационной базы имел фиксированный размер в 4096 байт. Изменение этого размера не поддерживалось. Размер внутреннего файла в базе данных не мог превышать 4 Гбайта.При использовании информационной базы с большим размером страницы, будет наблюдаться уменьшение времени открытия информационной базы, а также ускорение выполнения некоторых запросов.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Кластер серверов.
Уменьшено место на диске, которое занимают сеансовые данные. Сеансовые данные хранятся в кластере серверов в сжатом виде.Сеансовые данные хранились кластером серверов в не сжатом виде.Уменьшено место, которое занимаю служебные данные кластера. Ускорены некоторые внутренние процессы кластера серверов.
Клиентское приложение.
Ускорился запуск тонкого клиента при использовании файлового варианта информационной базы.При использовании файлового варианта информационной базы запуск тонкого клиента выполнялся недостаточно быстро.Ускорен запуск тонкого клиента при работе в файловом варианте информационной базы.
Работа с базой данных.
Оптимизирована реструктуризация разделенных иерархических справочников.Реструктуризация разделенных иерархических справочников выполнялась недостаточно быстро.Ускорена реструктуризация информационной базы, содержащей разделенные иерархические справочники.
Работа с базой данных.
Уменьшено потребление оперативной памяти при реструктуризации базы данных в файловом варианте, содержащей значительное количество двоичных данных большого размера.Реструктуризация базы данных в файловом варианте, содержащей значительное количество двоичных данных большого размера, могло завершиться аварийно из-за нехватки оперативной памяти.Повышена стабильность системы при выполнении реструктуризации базы данных в файловом варианте.
Интерфейс.
Кластер серверов.
В том случае, если в качестве СУБД используется Microsoft SQL Server, ускорено открытие списка истории работы пользователя.

Для ускорение открытия списка необходимо установить свойство конфигурации Режим совместимости в значение Версия 8.3.8 и старше, а затем выполнить полную реструктуризацию информационной базы или выполнить выгрузку/загрузку информационной базы в формат .dt.

Открытие списка истории работы пользователя занимало больше времени в том случае, если информационная база в качестве СУБД использовала Microsoft SQL Server.Ускорено открытие списка истории работы пользователя.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Программное лицензирование.
Средства администрирования.
Реализована утилита командной строки, предназначенная для управления программными лицензиями (активация лицензии, получение информации о лицензии, получение списка лицензий и т.д.). Утилита поставляется в виде двух установочных пакетов и находится в подкаталоге ExtDst каталога конкретной версии (при выборе толстого клиента или сервера), при этом непосредственно установки не происходит. При необходимости использования утилиты, запуск ее установки требуется выполнить вручную. Утилита реализована для ОС Windows (обоих архитектур) и для ОС Linux (обоих архитектур, в виде .deb- и .rpm-пакетов).

Обращение к утилите выполняется с помощью команды ring license. Для работы утилиты требуется Java 8. Подробное описание утилиты приводится в документации. +

Активация программных лицензий была доступна только в интерактивном режиме. Других возможностей по управлению программными лицензиями не предоставлялось.Упрощено администрирование программных лицензий на компьютере пользователя.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
При автоматической генерации элементов управляемой формы, для команд СоздатьПоПараметру и ПоказатьВСписке, имена элементов формируются по следующему шаблону: <Форма><ИмяКоманды><ИмяОбъектаКонфигурации>.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При автоматической генерации элементов управляемой формы, для команд СоздатьПоПараметру и ПоказатьВСписке, имена элементов формировались по следующему шаблону: <Форма><ИмяКоманды><НомерПоПорядку>.

+

Повышен комфорт при разработке прикладных решений.
В документации данное изменение описано здесь.
Управляемая форма.
Выпадающий список поля ввода управляемой формы подстраивает свою ширину под ширину отображаемых в нем данных.

Клавиши Home и End с любым модификатором обрабатываются непосредственно в поле ввода.

Выпадающий список поля ввода управляемой формы не подстраивался под ширину отображаемых в нем данных и имел фиксированную ширину, заданную платформой и прикладным разработчиком.

Клавиши Home и End (в том числе с модификаторами) не работали непосредственно в поле ввода.

Повышен комфорт использования поля ввода с выпадающим списком.
В документации данное изменение описано здесь.
Средства разработки.
В окне сравнения/объединения модулей реализованы следующие возможности:
  • Отображение номеров строк в модулях.
  • Синхронизация окон сравнения и окна редактирования результирующего текста.
  • Возможности окна редактирования приближены к возможностям редактора текста на встроенном языке.
  • В окне редактирования реализована контекстная подсказка. Контекст образуют основная конфигурация (до объединения) и текущий модуль (после объединения).
  • В заголовок окна выводится название модуля.

В окне редактирования результата объединения внешней программой реализованы следующие возможности:

  • Возможности окна редактирования приближены к возможностям редактора текста на строенном языке.
  • В окне редактирования реализована контекстная подсказка. Контекст образуют основная конфигурация (до объединения) и текущий модуль (после объединения).

При обновлении конфигурации, находящейся на поддержке, в окне сравнения/объединения конфигураций реализован фильтр Показывать только свойства с конфликтами объединения, отображающий только те объекты, которые не были объединены с помощью внешней программы.

Данные возможности не предоставлялись.Повышен комфорт прикладного разработчика при выполнении задач по обновлению прикладных решений.
В документации данное изменение описано здесь.
Средства разработки.
В разделе Пояснение палитры свойств, русские имена свойств отображаются только в тех случаях, когда выбран русский вариант встроенного языка или русский интерфейс платформы. Английские имена свойств выводятся всегда.В разделе Пояснение палитры свойств всегда отображались русские и английские имена свойств.Упрощена работа с конфигуратором для англоязычных разработчиков прикладных решений.
Веб-клиент.
Табличный документ.
Реализована возможность отображения фоновой картинки и узора в ячейке табличного документа, отображаемого веб-клиентом.Не поддерживалось отображение фоновой картинки и узора в ячейке табличного документа, отображаемого в веб-клиенте.Расширены оформительские возможности для табличного документа, отображаемого веб-клиентом.
В документации данное изменение описано здесь.
Отображение информации.
Табличный документ.
Реализован подбор шрифта для символов, отсутствующих в текущем шрифте, при экспорте табличного документа в формат PDF.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Символы, отсутствующие в текущем шрифте, отображались потерянным символом («квадратиком») при экспорте табличного документа в формат PDF.Табличный документ, содержащий символы различных национальных алфавитов, стал экспортироваться в формате PDF с сохранением оригинального вида.
В документации данное изменение описано здесь и здесь.
Табличный документ.
При экспорте табличного документа в формате XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument) реализована возможность размещать картинки в ячейках табличного документа.

Данная возможность не поддерживается при экспорте табличного документа в формате XLS (Microsoft Excel 95).

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При экспорте табличного документа в формате XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument) не поддерживалась возможность размещать картинки в ячейках табличного документа.При экспорте табличного документа в Microsoft Excel и ODS обеспечивается максимальное сходство с оригинальным табличным документом.
В документации данное изменение описано здесь.
Расширение конфигурации.
При заимствовании реквизитов составного типа, не содержащем ссылок на объекты конфигурации, составной тип заимствуется полностью. При повторном заимствовании текущий тип в расширении дополняется набором типов из расширяемой конфигурации.

При заимствовании реквизитов составного типа, содержащим хотя бы одну ссылку на объекты конфигурации (не примитивные типы), тип заимствуется как ЛюбаяСсылка. При повторном заимствовании тип ЛюбаяСсылка добавляется только если тип уже не является составным и в его составе нет типов СправочникСсылка, ДокументСсылка и т.п.

Контроль типов при подключении расширения выполняется следующим образом:

  • наличие типа ЛюбаяСсылка в типе реквизита расширения требует наличие в соответствующем реквизите расширяемой конфигурации любого ссылочного типа.
  • Наличие в типе реквизите типа СправочникСсылка, ДокументСсылка и т.д. требует наличия в реквизите расширяемой конфигурации любого ссылочного типа соответствующих типов.

Если реквизит составного типа не может включать тип ЛюбаяСсылка, то любой составной тип для такого реквизита будет заимствован с единственным типом - Произвольный. Для таких реквизитов не может возникнуть ошибка применения расширения. +

При заимствовании составного типа примитивные типы заимствовались всегда, а из типов, ссылающихся на объекты конфигурации, случайным образом выбирался один тип.

Контроль типов при подключении расширения выполнялся следующим образом: наличие составных типов в типе реквизита требовало наличие точно таких же типов у соответствующего реквизита в расширяемой конфигурации.

Упрощено использования составных типов в расширениях.
В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Если при вызове Web-сервиса происходит внутренняя ошибка в инфраструктуре сервера, не связанная с протоколом SOAP, то сообщение об ошибке содержит корректную диагностику проблемы. Сообщение об ошибке вызова Web-сервиса стало более подробным и информативным и может включать в себя информацию из тегов faultfactor (Node) и Role ответа Web-сервиса.Если при вызове Web-сервиса происходила внутренняя ошибка в инфраструктуре сервера, не связанная с протоколом SOAP, то формировалось неверное сообщение об ошибке, при этом информация об истинных причинах ошибки терялась.

Сообщение об ошибке не включало дополнительной информации из ответа Web-сервиса.

Сообщение об ошибке вызова Web-сервиса стало более информативным и подробным, что облегчает диагностику проблем.
Фоновые и регламентные задания.
Регламентные задания начинают выполняться не ранее, чем через 2 минуты после старта клиентского приложения при работе в файловом варианте информационной базы.Регламентные задания (в файловом варианте информационной базы) начинали выполняться не ранее, чем через 1 минуту после запуска клиентского приложения.Уменьшены задержки при старте клиентского приложения при работе с файловым вариантом информационной базы.
В документации данное изменение описано здесь.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
При отключении публикации на веб-сервере из конфигуратора, пользователю предлагается выполнить перезапуск веб-сервера.При отключении публикации на веб-сервере из конфигуратора, пользователю не предлагалось выполнить перезапуск веб-сервера.Отключение публикации на веб-сервере стало более очевидным и корректным, т.к. фактическое отключение публикации выполнялось только при перезапуске веб-сервера.
В документации данное изменение описано здесь.
Средства разработки.
В конфигураторе реализована возможность настройки фона контекстной подсказки параметров методов.

Для отображения ссылок на синтакс-помощник в контекстной подсказке используется цвет Идентификаторы, для остального текста используется цвет Прочие.

Для отображения ссылок на синтакс-помощник в контекстной подсказке использовался цвет по-умолчанию цвета Идентификаторы, для остального текста использовался цвет по-умолчанию цвета Прочие.Стало возможно настроить читабельную подсказку параметров метода, если для редактора модулей выбрана цветовая схема с темным цветом фона.
Работа с XML, XDTO.
Web-сервисы и HTTP-сервисы.
В модели XDTO реализованы свойства, позволяющие корректно использовать XSD-схемы, содержащие любые комбинации значений атрибутов elementFormQualified (свойство пакета Квалифицированная форма элемента), attributeFormQualified (свойство пакета Квалифицированная форма атрибута) и form (свойство элемента Квалифицированное).

В редакторе XDTO-пакета реализована возможность просмотра и редактирования новых свойств пакетов. При установке режима совместимости в значение Версия 8.3.7 и ниже, новые свойства пакетов XDTO сбрасываются в значения по умолчанию.

При работе с XSD-схемами модель XDTO игнорировала фактические значения атрибутов схемы elementFormDefault и attributeFormDefault. Также игнорировался атрибут form элементов и атрибутов XSD-схемы. Вместо этого, независимо от фактических значений атрибутов всегда использовались следующие значения:
  • elementFormDefault считалось равным qualified;
  • attributeFormDefault считалось равным unqualified.

+

Расширен состав Web-сервисов, с которыми может работать «1С:Предприятие» без необходимости вручную дорабатывать описание этого сервиса.
Средства администрирования.
Переработаны диалоги добавления и изменения информационной базы в списке информационных баз. Уменьшено количество страниц в данных диалогах.

Реализовано автоматическое определение типа соединения с информационной базой по строке, которая запомнена в буфер обмена перед созданием новой информационной базы или при вводе строки в поле Укажите наименование информационной базы. Автоматически распознается путь к файловой информационной базе и URL, с помощью которого предоставляется доступ к информационной базе, расположенной на веб-сервере. При определении типа информационной базы автоматически заполняются соответствующие поля диалога.

Диалоги добавления и изменения информационной базы были более сложными и содержали большее количество страниц.Упрощен процесс добавления информационной базы в список.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Управляемая форма.
В том случае, когда поле ввода управляемой формы отображает данные типа СписокЗначений, форма списка значений, открываемая для редактирования данных, получает от поля ввода следующие свойства:
  • ПараметрыВыбора – реализовано дополнение значениями, в соответствии со свойством СвязиПараметровВыбора.
  • ФормаВыбора – реализовано для веб-клиента.
  • ВыборГруппИЭлементов – реализовано для веб-клиента.
  • Маска.
  • ФорматРедактирования.
  • БыстрыйВыбор.
  • СвязьПоТипу.
В том случае, когда поле ввода управляемой формы отображает данные типа СписокЗначений, форма списка значений, открываемая для редактирования данных, получала от поля ввода следующие свойства:
  • ПараметрыВыбора – без дополнения значениями, в соответствии со свойством СвязиПараметровВыбора.
  • ФормаВыбора – только для тонкого клиента.
  • ВыборГруппИЭлементов – только для тонкого клиента.
Устранено некорректное поведение системы.
Полнотекстовый поиск.
Ввод по строке.
Динамический список.
При вводе по строке и при использовании строки поиска динамического списка данные будут находиться, даже если они еще не попали в индекс полнотекстового поиска.При вводе по строке и при использовании строки поиска динамического списка данные, еще не попавшие в индекс полнотекстового поиска, не находились системой.Обеспечено попадание в результаты поиска при вводе по строке или поиска по строке в динамическом списке данных, которые еще не попали в индекс полнотекстового поиска.
Управляемая форма.
Изменен внешний вид кнопок управляемой формы и кнопок командной панели в интерфейсе Такси.

Для кнопок вида КнопкаКоманднойПанели, ГиперссылкаКоманднойПанели реализована поддержка свойств ЦветФона, ЦветТекста, Шрифт, ЦветРамки (кроме кнопок вида ГиперссылкаКоманднойПанели). Для расширения группы формы для подменю реализована поддержка свойств ЦветРамки, ЦветФона, ЦветТекстаЗаголовка, ШрифтЗаголовка. В режиме совместимости с версией 8.3.7 и в интерфейсе версии 8.2 поведение не изменилось.

Для стандартной команды Скопировать расширения таблицы для динамического списка:

  • Для свойства Отображение значение Авто означает Картинка.
  • Для свойства ТолькоВоВсехДействиях значение Авто означает Нет.

Для команд таблицы управляемой формы ПереместитьВверх и ПереместитьВниз для свойства ТолькоВоВсехДействиях значение Авто означает Нет. Также указанные команды размещаются в компактной группе кнопок.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В режиме совместимости с версией 8.3.7 и одновременно включенном компактном режиме интерфейса различается высота кнопок в тонком клиенте и веб-клиенте.

Внешний вид кнопок управляемой формы и кнопок командной панели в интерфейсе Такси имел другой вид.

Для кнопок вида КнопкаКоманднойПанели свойства ЦветФона, ЦветТекста, Шрифт, ЦветРамки присутствовали, но не использовались. Для расширения группы формы для подменю свойства ЦветРамки, ЦветФона, ЦветТекстаЗаголовка, ШрифтЗаголовка присутствовали, но не использовались.

Для стандартной команды Скопировать расширения таблицы для динамического списка:

  • Для свойства Отображение значение Авто означало Текст.
  • Для свойства ТолькоВоВсехДействиях значение Авто означало Да.

Для команд таблицы управляемой формы ПереместитьВверх и ПереместитьВниз для свойства ТолькоВоВсехДействиях значение Авто означало Да.

Расширены возможности создания форм в интерфейсе Такси.

Некоторые часто используемые пользователем кнопки (Скопировать в динамическом списке и команды перемещения строки для остальных таблиц) по умолчанию перестанут располагаться в меню Еще, а станут доступны сразу на командной панели.

Управляемая форма.
Реализована возможность отображать команду, расположенную на командной панели, в виде гиперссылки. В подменю отображение в виде гиперссылки не поддерживается. Для перечисления ВидКнопкиФормы реализовано значение ГиперссылкаКоманднойПанели. В режиме совместимости с версией 8.3.7 значение ВидКнопкиФормы.ГиперссылкаКоманднойПанели трактуется как ВидКнопкиФормы.КнопкаКоманднойПанели.

В интерфейсе Такси реализована возможность управлять горизонтальным расположением картинки в кнопке управляемой формы. Не поддерживается для команд, расположенных в подменю. Для кнопки управляемой формы реализовано свойство ПоложениеКартинки. В режиме совместимости с версией 8.3.7 и в интерфейсе версии 8.2 свойство игнорируется.

Реализована возможность управлять расстоянием между кнопками, расположенными на командной панели. Реализовано расширение группы управляемой формы для группы кнопок. Не поддерживается для команд, расположенных в подменю. Реализовано системное перечисление ОтображениеГруппыКнопок. В режиме совместимости с версией 8.3.7 и в интерфейсе версии 8.2 настройка расстояния между кнопками игнорируется.

Реализована возможность управлять формой кнопок командной панели (кроме расположенных в подменю). Для кнопки управляемой формы и расширения группы формы для подменю реализовано свойство Фигура. Не поддерживается для команд, расположенных в подменю. В режиме совместимости с версией 8.3.7 и в интерфейсе версии 8.2 свойство игнорируется.

Реализована возможность управлять внешним видом кнопки управляемой формы. Для кнопки управляемой формы и расширения группы формы для подменю реализовано свойство ОтображениеФигуры. Реализовано системное перечисление ОтображениеФигурыКнопки. Не поддерживается для команд, расположенных в подменю. В режиме совместимости с версией 8.3.7 и в интерфейсе версии 8.2 свойство игнорируется.

В командной панели команда не могла отображаться в виде гиперссылки.

Было невозможно управлять горизонтальным расположением картинки в кнопке управляемой формы.

Не поддерживалось управление расстоянием между кнопками, расположенными на командной панели.

Не поддерживалась возможность управления формой кнопок командной панели. +Не поддерживалась возможность управления внешним видом кнопок командной панели. +

Расширены возможности оформления управляемых форм в интерфейсе Такси.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
В документацию добавлены рекомендации по использованию сообщений пользователю, позволяющие снизить вероятность возникновения ситуаций, когда пользователь не может прочитать выведенные сообщения.Документация не содержала рекомендаций, направленных на снижение вероятности возникновения ситуаций, когда пользователь не может прочитать выведенные сообщения.Улучшена документация.
В документации данное изменение описано здесь.
Программное лицензирование.
Не происходит деактивации программных лицензий при обновлениях операционной системы Windows 10. +Система программного лицензирования была недостаточно совместима с операционной системой Windows 10: при обновлении операционной системы могла происходить деактивация программной лицензии.Улучшена совместимость системы программного лицензирования с операционной системой Windows 10.
В документации данное изменение описано здесь.
Локализация.
Не поддерживается интерфейс системы на казахском языке (код kk).Поддерживался интерфейс системы на казахском языке (код kk).Не поддерживается интерфейс системы на казахском языке.
Региональные установки.
Для Российской Федерации учитывается однократный сдвиг часовых зон на один час в связи с принятием законов №№ 453-ФЗ (Забайкальский край), 27-ФЗ (Астраханская область), 57-ФЗ (Алтайский край), 58-ФЗ (Республика Алтай), 59-ФЗ (Сахалинская область), 69-ФЗ (Ульяновская область), 87-ФЗ (Магаданская область), 109-ФЗ (Томская область), 271-ФЗ (Новосибирская область), 395-ФЗ (Саратовская область). Изменения касаются всех компонентов системы «1С:Предприятие», кроме веб-клиента. Веб-клиент пользуется информацией о временных зонах, которую предоставляет ОС и веб-браузер. +Изменения, внесенные законом №№ 453-ФЗ, 27-ФЗ, 57-ФЗ, 58-ФЗ, 59-ФЗ, 69-ФЗ, 87-ФЗ, 109-ФЗ, 271-ФЗ, 395-ФЗ, не учитывались платформой. +Учтены изменения законодательства об исчислении времени.
Табличный документ.
При копировании текста из ячеек Microsoft Excel, скопированный текст вставляется полностью, независимо от длины строки.При копировании текста из ячеек Microsoft Excel, скопированный текст ограничивался первыми 255 символами.Устранено некорректное поведение системы.
Табличный документ.
При импорте данных из документов Microsoft Excel улучшена обработка данных в формате дата и время:
  • Для стандартных форматов Microsoft Excel применяются соответствующие форматные строки «1С:Предприятия».
  • Учитывается явное указание кода локализации в форматной строке Microsoft Excel для определения форматной строки «1С:Предприятия»;
  • Для типа дата используется первый найденный разделитель из короткого формата даты, установленного для информационной базы.
  • Для даты, в которой месяц представлен первой буквой, в системе «1С:Предприятие» обеспечивается краткое представление месяца.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При импорте данных из документов Microsoft Excel обработка данных в формате дата и время выполнялась следующим образом:
  • Использовался фиксированный список стандартных форматов Microsoft Excel.
  • Игнорировалось явное указание кода локализации в форматной строке Microsoft Excel и использовались настройки текущей информационной базы системы «1С:Предприятие».
  • Для типа дата всегда использовался символ «/».
  • Дата, в которой месяц представлен первой буквой, в системе «1С:Предприятие» выводилась с полным представлением месяца.
Обеспечен более корректный импорт данных в формате даты и времени из документов Microsoft Excel.
Web-сервисы и HTTP-сервисы.
Для конфигураций, в которых используются HTTP-сервисы, разрешена установка режима совместимости Версия 8.3.4 и ниже.

При необходимости работать с конфигурацией, которая содержит HTTP-сервисы, на системе «1С:Предприятие» версии 8.3.8 и выше, но которая открывалась конфигуратором системы «1С:Предприятие» версии 8.3.4, необходимо выполнить следующие действия:

  • Создать любой объект конфигурации;
  • Выполнить сохранение конфигурации информационной базы;
  • Удалить созданный объект конфигурации;
  • Выполнить сохранение конфигурации информационной базы.
В «1С:Предприятии» версии 8.3.7 была запрещена установка режима совместимости Версия 8.3.4 и младше, если в конфигурации находились HTTP-сервисы.Возможность использования HTTP-сервисов в конфигурациях, требующих для работы режимы совместимости Версия 8.3.4 и ниже.
Клиентское приложение.
Работа с Интернет.
Реализована возможность указывать, к каким служебным ресурсам будет обращаться платформа. +Режим обращения задается через параметр ExternalResourcesMode конфигурационного файла conf.cfg. +В случае отсутствия параметра, режим автоматически определяется системой.Данная возможность не предоставлялась.У пользователей появилась дополнительная возможность указывать, к каким служебным ресурсам будет обращаться платформа.
В документации данное изменение описано здесь.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа с Интернет.
Объект ЗащищенноеСоединениеNSS недоступен для использования, сертификаты NSS недоступны для использования во встроенном языке.Система «1С:Предприятие» поддерживала работу с сертификатами NSS в режиме совместимости с версией 8.3.6.Прекращена поддержка сертификатов NSS.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с Интернет.
Реализована поддержка протоколов TLS 1.1 и 1.2 в тех случаях, когда в параметрах соединения не указан клиентский сертификат. Протокол SSL v3.0 будет использован только в том случае, если клиентское приложение запускается с параметром командной строки /HttpsForceSSLv3. Во всех остальных случаях протокол SSL v3.0 не используется.

Параметр AllowSSLv3 файла conf.cfg игнорируется.

Объект ИнтернетПочта не поддерживает протокол SSL v3.0.

Система поддерживала работу только с протоколом TLS 1.0.

Для конфигурационного файла conf.cfg было возможно использовать параметр AllowSSLv3.

Объект ИнтернетПочта поддерживал протокол SSL v3.0.

Повышена защищенность соединения, устанавливаемого клиентским приложением, при работе через Интернет.
В документации данное изменение описано здесь.
Работа с Интернет.
При создании HTTPS/FTPS соединения прекращена поддержка файла cacert.pem. При создании HTTPS/FTPS соединения будет использоваться хранилище корневых сертификатов используемой ОС.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При создании HTTP/FTPS соединения использовался файл cacert.pem в тех случаях, когда создание соединения выполнялось без явного указания на использование какого-либо хранилища сертификатов.Отказ от использования устаревшей технологии.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Управляемая форма.
Реализована возможность обновлять представление данных в управляемой форме только для указанного перечня элементов формы. Для метода ОбновитьОтображениеДанных() реализован параметр ОбновлятьЭлементы.

Для системного перечисления ОбновлениеТекстаРедактирования реализовано значение Всегда.

Было невозможно управлять списком элементов формы, которые должны обновить представление отображаемых данных при вызове метода ОбновитьОтображениеДанных().Стало возможно управлять изменением данных формы в обработчиках ожидания без потери редактируемого текста в текущем поле ввода.
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
Выгрузка в файлы свойства Источник объекта ДополнениеЭлементаФормы стала более читабельной.

Загрузка конфигурации из файлов возможна с обоими вариантами записи значения свойства.

Выгрузка в файлы свойства Источник объекта ДополнениеЭлементаФормы была менее читабельной.Формат выгрузки конфигурации в файлы стал более понятен для обычного (не машинного) чтения и анализа.
Работа с XML, XDTO.
Средства разработки.
При создании WS-ссылки (в конфигураторе или с помощью объекта WSОпределения) существенно расширена диагностика ошибочных ситуаций.

При создании объекта WSОпределения вызывается исключение в том случае, если в используемом WSDL имеются ошибки.

WSDL, используемый для создания объектов WSОпределения или WSСсылка должен:

  • Содержать тег <definitions> в качестве первого тега.
  • Содержать атрибут targetNamespace для элемента <xs:schema>.
  • При невыполнении вышеперечисленных условий генерируется исключение.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При создании WS-ссылки (в конфигураторе или с помощью объекта WSОпределения) диагностика ошибочных ситуаций была недостаточно подробной.

При создании объекта WSОпределения, если в используемом WSDL имелись ошибки, некорректные элементы игнорировались.

Если WSDL, используемый для создания объекта WSОпределения или WSСсылка, не содержал тег <definitions> в качестве первого тега - создавались пустые объекты, описывающие Web-сервис.

Если WSDL, используемый для создания объекта WSОпределения или WSСсылка, не содержал атрибут <targetNamespace> для элемента <xs:schema> - платформа устанавливала целевое пространство имен псевдослучайным образом.

Улучшена диагностика при работе с описаниями Web-сервисов.
В документации данное изменение описано здесь.
Работа с запросами.
В случае, если константа хранит значение следующих типов: ХранилищеЗначения, УникальныйИдентификатор, ВнешнийИсточникДанныхТаблицаСсылка, обращение к полю Значение таблицы константы, при обработке выборки из запроса к этой таблице, возвращает значение соответствующего типа.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В случае, если константа хранит значение следующих типов: ХранилищеЗначения, УникальныйИдентификатор, ВнешнийИсточникДанныхТаблицаСсылка, обращение к полю Значение таблицы константы, при обработке выборки из запроса к этой таблице, возвращало значение типа ДвоичныеДанные.Устранено некорректное поведение системы.
Средства печати.
Реализовано следующее поведение метода ПакетОтображаемыхДокументов.Напечатать():
  • Для ОС Windows:
    • создается одно задание на принтер;
    • весь пакет выводится в один файл, имя которого запрашивается перед выводом.
  • Для ОС Linux:
    • если параметры печати всех документов в пакете совпадают - поведение совпадает с поведением в ОС Windows;
    • если параметры различаются - каждый документ печатается в отдельном задании принтера.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Реализовано свойство ПакетОтображаемыхДокументов.Заголовок, предназначенное для формирования представления печатаемого пакета.

При использовании метода ПакетОтображаемыхДокументов.Напечатать(), каждый документ пакета печатался в отдельном задании.Улучшена печать пакетов документов.
В документации данное изменение описано здесь.
Система компоновки данных.
Элементы условного оформления Текст и Формат применяются к полям макета группировки диаграммы системы компоновки данных вне зависимости от ранее установленного оформления Формат (в т.ч. и взятого из схемы компоновки данных). При этом элемент условного оформления Текст имеет более высокий приоритет, чем элемент условного оформления Формат.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Элементы условного оформления Текст и Формат применялись к полям макета диаграммы системы компоновки данных только в случае, если ранее к этому полю не было применено условное оформление Формат.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Свойство условного оформления ВыделятьОтрицательные используется только в том случае, когда само свойство установлено в значение Истина и свойство условного оформления Использование также имеет значение Истина.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Свойство условного оформления ВыделятьОтрицательные использовалось в том случае, когда свойство условного оформления Использование имело значение Истина.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При определении типа результата операции языка запросов ВЫБОР, учитываются типы выражений из всех веток ТОГДА этого выражения.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При определении типа результата операции языка запросов ВЫБОР, игнорировались ветки ТОГДА, в которых находится константное выражение, принимающее значение NULL.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
Реализована возможность установки максимального размера данных, которые индексируются полнотекстовым поиском. По умолчанию установлен размер в 1 Мбайт.

Для объекта МенеджерПолнотекстовогоПоиска реализованы методы УстановитьМаксимальныйРазмерИндексируемыхДанных() и ПолучитьМаксимальныйРазмерИндексируемыхДанных().

Реализовано событие технологического журнала <FTEXTSKIP>.

В режиме совместимости с версией 8.3.7 поведение не изменилось. +

Отсутствовала возможность ограничить максимальный объем данных, индексируемых полнотекстовым поиском. Индексировались все данные, размещенные в информационной базе.Стало возможно ограничить объем данных, индексируемых полнотекстовым поиском, исключив из него очень большие данные, полнотекстовый поиск в которых не требуется. В результате стало возможно повысить скорость индексации и полнотекстового поиска, а также уменьшить размер индекса полнотекстового поиска.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Работа с Интернет.
Средства администрирования.
В механизме получения списка баз и обновлений платформы по HTTPS, исключено использование файла cacert.pem, поставляемого с платформой.

В ОС Linux задействован механизм получения сертификатов удостоверяющих центров, установленных в ОС, в ОС Windows используется системное хранилище корневых сертификатов ОС.

Для проверки HTTPS соединения в ОС Windows использовался файл cacert.pem и системное хранилище корневых сертификатов ОС.

В ОС Linux использовался только файл cacert.pem, поставляемый с платформой.

Упрощено администрирование процесса обновления платформы в случае использования протокола HTTPS.
Работа в ОС Linux.
Системные требования.
Доработан механизм формирования списка шрифтов для работы платформы в ОС Linux. Для получения списка шрифтов используется библиотека fontconfig, требование наличия которой включено в системные требования.

Из документации исключено перечисление каталогов, которые использовались для размещения шрифтов.

Для получения списка шрифтов в ОС Linux использовался фиксированный список каталогов (приведенный в документации).

Для поиска шрифтов не использовалась библиотека fontconfig.

Система «1С:Предприятие» стала использовать большее количество шрифтов при работе в ОС Linux. Упрощено администрирование системы.
В документации данное изменение описано здесь и здесь.
Системные требования.
Тип, указанный для параметра в схеме компоновки данных, влияет на тип поля запроса, в котором используется этот параметр.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Тип, указанный для параметра схемы компоновки данных, не влиял на тип поля запроса, в котором этот параметр используется.При формировании отчета выводимая информация более точно соответствует заданным параметрам.
В документации данное изменение описано здесь.
Динамический список.
Переработана реализация динамического списка. Расширен перечень виртуальных полей, которые в динамическом списке недоступны для использования в настройках упорядочивания, группировки и отбора.

Генерируется ошибка в том случае, если в таблице, указанной в качестве основной таблицы динамического списка, отсутствуют ключевые поля (с точки зрения объектной модели языка) и настроена группировка.

При установке из встроенного языка отбора, упорядочивания или группировки по полю, отсутствующего в тексте запроса, будет выдана ошибка о ненайденном поле.

Изменен список ограничений для запросов, использующихся при формировании динамического списка.

Описаны особенности упорядочивания динамического списка.

Изменено описание способов получения данных динамическим списком.

Стандартная картинка строк формируется на основе стандартных реквизитов. Если в тексте запроса списка есть поля, псевдонимы которых совпадают с именами стандартных реквизитов, но в них получаются другие данные - такие поля не будут использоваться для формирования стандартной картинки.

При невозможности преобразовать отбор динамического списка в конструкцию языка запросов, выдается ошибка.

На сторону клиента не передаются данные колонок динамического списка, которые не используются для отображения и не помечены свойством Использовать всегда. Доступ к данным таких колонок на стороне клиента невозможен.

На сторону клиента не передаются данные колонок динамического списка, которые помечены свойством Использовать всегда, но для которых у текущего пользователя отсутствует право Просмотр. Доступ к данным таких колонок (с помощью свойства ТекущиеДанные и метода ДанныеСтроки()) на стороне клиента невозможен.

Отборы, которые автоматически накладываются динамическим списком на стандартные поля Владелец, Родитель, Дата, Период и ЭтоГруппа, применяются средствами системы компоновки данных.

Отборы, которые автоматически накладываются динамическим списком на ключевые поля, могут применяться как средствами системы компоновки данных, так и путем непосредственного добавления в текст запроса условия на поля основной таблицы.

В результате применения отборов средствами системы компоновки данных, они могут примениться во вложенных запросах и параметрах виртуальных таблиц. При этом возможно существенное изменение результата выборки данных динамическим списком (относительно результата в режиме совместимости с версией 8.3.7).

Более подробное описание указанных особенностей приведено в документации.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Для использования в настройках упорядочивания, группировки динамического списка были недоступны виртуальные поля ВерсияДанных, ИмяПредопределенныхДанных, поля табличных частей и поля следующих типов: Тип, Строка (неограниченной длины), ДвоичныеДанные (неограниченной длины).

Список ограничений на настройки группировок и упорядочивания был другим и не являлся полным.

Если в таблице, указанной в качестве основной таблицы динамического списка, отсутствуют ключевые поля (с точки зрения объектной модели языка) и настроена группировка, то состав отображаемых данных был неопределен.

При установке из встроенного языка отбора на поле, отсутствующее в тексте запроса, отбор мог быть успешно применен или проигнорирован. При установке из встроенного языка упорядочивания или группировки по полю, отсутствующему в тексте запроса, такое поле игнорировалось.

Список ограничений для запросов, использующихся при формировании динамического списка, был другим.

Список особенностей упорядочивания динамического списка был не документирован.

Описание способов получения данных динамическим списком было другим.

Если в тексте запроса динамического списка есть поля с псевдонимами, совпадающими с именами стандартных реквизитов, используемые для формирования стандартной картинки, они использовались для формирования стандартной картинки (кроме реквизита ЭтоГруппа).

При невозможности преобразовать отбор динамического списка в конструкцию языка запросов, отбор применялся средствами процессора компоновки данных после получения данных, что могло приводить к уменьшению количества отображаемых данных, относительно их реального количества (с учетом отбора).

При наличии в настройках динамического списка недоступных (без учета прав и функциональных опций) полей сортировки или группировки, такие поля игнорировались.

В некоторых случаях на сторону клиента передавались данные колонок динамического списка, которые не использовались для отображения и не помечены свойством Использовать всегда.

На сторону клиента передавались данные колонок динамического списка, которые помечены свойством Использовать всегда, но для которых у текущего пользователя отсутствовало право Просмотр. В качестве значения таких колонок выступали значения по умолчанию для соответствующего типа.

Отборы, автоматически накладываемые динамическим списком на ключевые поля и стандартные поля Владелец, Родитель, Дата, Период, ЭтоГруппа, всегда применялись путем непосредственного добавления условия в текст запроса.

Повышено качество и предсказуемость работы динамического списка. В документации уточнены особенности работы динамического списка.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Фоновые и регламентные задания.
При попытке передать в качестве параметра запускаемого фонового задания (с помощью метода ФоновыеЗадания.Выполнить()) несериализуемое значение, запуск фонового задания не будет происходить и будет генерироваться исключение.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При попытке передать в качестве параметра запускаемого фонового задания (с помощью метода ФоновыеЗадания.Выполнить()) несериализуемое значение, фоновое задание запускалось, в качестве значения соответствующего параметра передавалось значение Неопределено, исключение не генерировалось.Запуск фонового задания приведен в соответствие с общей методикой диагностики ошибок.
Средства администрирования.
Реализовано формирование снимка экрана во время создания дампа аварийного завершения работы тонкого клиента (атрибут prntscrn элемента dump файла logcfg.xml).Формирование снимка экрана во время создания дампа аварийного завершения работы тонкого клиента не выполнялось.Устранено некорректное поведение системы.
Работа с запросами.
Результат операции деления, где делителем является NULL, трактуется как число произвольной разрядности. Результат такой операции не может выступать в качестве операнда в операции, где числовое значение недопустимо (например, операции AND, OR, NOT).

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Результат операции деления, где делителем является NULL, не трактовался как число и мог выступать в качестве операнда в операции, где числовое значение недопустимо (например, операции AND, OR, NOT).Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
Интерфейс.
Изменен подход, которому должен следовать прикладной разработчик при закрытии управляемых форм и приложения:
  • Реализован специальный режим завершения работы, который необходимо особым образом обрабатывать в обработчиках событий ПередЗакрытием и ПриЗакрытии управляемой формы.
  • В обработчиках событий управляемого приложения ПередЗавершениемРаботыСистемы, ПриЗавершенииРаботыСистемы, а также в обработчиках событий управляемой формы, находящейся в режиме закрытия, ПередЗакрытием, ПриЗакрытии, запрещено открывать окна и выполнять любые серверные вызовы.
  • Реализована возможность сформировать текстовое сообщение, в ответ на отображение которого платформой, пользователь может отказать от закрытия или подтвердить его (в веб-клиенте все сообщения будут объединены в один диалог).

Более подробно данный подход описан в документации.

Для обработчика события управляемой формы ПередЗакрытием реализованы параметры ЗавершениеРаботы и ТекстПредупреждения. Для обработчика события управляемой формы ПриЗакрытии реализован параметр ЗавершениеРаботы. Если в обработчиках событий ПередЗакрытием и ПриЗакрытии управляемой формы был добавлен параметр ЗавершениеРаботы, то в режиме совместимости с версией 8.3.7 данный параметра будет установлен в значение Неопределено. Для обработчика события модуля управляемого приложения ПередЗавершениемРаботыСистемы реализован параметр ТекстПредупреждения.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В зависимости от режима использования модальности, использовались разные подходы к закрытию управляемых форм и основного окна приложения.

В ряде случаев используемые подходы приводили к различным ошибкам (особенно в веб-клиенте), которые было сложно диагностировать и исправлять.

Реализован единый подход к закрытию форм и основного окна приложения, который одинаково работает во всех клиентских приложениях, обеспечивая приемлемые возможности по взаимодействию с пользователями.

Реализованное поведение стало соответствовать методике и техническим требованиям современных веб-браузеров.

В документации данное изменение описано здесь.
Средства администрирования.
Установка клиентского приложения.
При запуске информационной базы, с помощью приложений 1cv8, 1cv8c, 1cv8s, для которой в списке информационных баз (локальном или общем) указана конкретная версия платформы, подбор требуемой версии выполняется вне зависимости от того, указан в командной строке запуска ключ /AppAutoCheckVersion или нет. Если указана версия, отсутствующая на текущем компьютере, и эту версию невозможно установить, то происходит попытка запустить информационную базу с помощью самой свежей установленной версии «1С:Предприятия».

При обновлении клиентского приложения по протоколу HTTP отключена проверка привилегий пользователя операционной системы на выполнение операции. При недостаточности прав на установку клиентского приложения, пользователю будет выдан диалог UAC, с предложением подтвердить установку от имени пользователя с правами администратора. Улучшена диагностика ошибок при скачивании и установке дистрибутива клиентского приложения по HTTP.

Для ключа командной строки /AppAutoCheckVersion реализована возможность явного указания - выполнять автоматический подбор используемой версии «1С:Предприятие» или нет.

При запуске информационной базы, с помощью приложений 1cv8, 1cv8c, 1cv8s, подбор требуемой версии выполнялся только если в командной строке запуска был указан ключ /AppAutoCheckVersion.

При обновлении клиентского приложения по протоколу HTTP выполнялась проверка прав пользователя на выполнение операции.

+

Подбор и обновление клиентского приложения для получения доступа к конкретной информационной базе стал более простым и понятным.

Повышена стабильность автоматического обновления тонкого клиента при работе по протоколу HTTP.

В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Средства администрирования.
При установке тонкого клиента из специализированного дистрибутива, в папке «1С:Предприятие» присутствует только ярлык запуска приложения 1cestart.При установке тонкого клиента из специализированного дистрибутива, в папке «1С:Предприятие» присутствовал ярлык запуска приложения 1cestart, а также папка Дополнительно, которая содержала в себе подпапки с номерами конкретных установленных версий «1С:Предприятия».При установке тонкого клиента уменьшено количество различных вариантов запуска клиентского приложения.
Средства администрирования.
При разборе командной строки запуска клиентского приложения или конфигуратора изменены правила разбора обязательных параметров. Если для ключа параметр является обязательным, то в командной строке запуска он также должен присутствовать, либо ключ не должен указываться вовсе. Также допускается значение ключа, которое начинается с символа «/». +Правила разбора командной строки запуска клиентского приложения или конфигуратора были другими. Допускалось опускать значение параметра ключа даже в том случае, если параметр был обязательным. Параметр мог диагностироваться как ключ командной строки в том случае, если написание параметра начиналось с символа «/» (полное имя файла на ОС Linux).Устранено некорректное поведение системы.
Средства администрирования.
В документацию и справку конфигуратора внесено описание ключей /Out, /L, /VL и /O для режима запуска CREATEINFOBASE, которые ранее были не описаны.

Для режима запуска в режиме создания информационной базы (CREATEINFOBASE) реализован ключ командной строки /DumpResult, записывающий в файл результат работы. +При использовании в пакетном режиме запуска конфигуратора (в файловом варианте) ключей /RestoreIB и /LoadCfg вместе с ключом /DisableStartupDialogs, информационная база будет автоматически создана, если в каталоге отсутствует файл с базой данных.

В документации и справке конфигуратора отсутствовало описание ключей /Out, /L, /VL и /O для режима запуска CREATEINFOBASE.

При использовании в пакетном режиме запуска конфигуратора (в файловом варианте) ключей /RestoreIB и /LoadCfg вместе с ключом /DisableStartupDialogs, задавался вопрос в том случае, если в указанном каталоге отсутствовал файл базы данных.

Улучшена справка конфигуратора и документация к системе. Упрощено использование пакетного запуска конфигуратора в некоторых вариантах использования.
В документации данное изменение описано здесь.
Система компоновки данных.
Если у поля набора данных схемы компоновки данных указано выражение упорядочивания, и в настройках компоновки данных указано упорядочивание по этому полю с направлением упорядочивания По убыванию, то направление упорядочивания, указанное в выражении упорядочивания для данного поля заменяется на обратное.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Если у поля набора данных схемы компоновки данных указаны выражения упорядочивания, то при упорядочивании по данному полю направление упорядочивания всегда получается из выражения упорядочивания. Направление упорядочивания из настроек для этого поля игнорируется.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Управляемые блокировки.
Регистры бухгалтерии.
Управляемая блокировка, устанавливаемая при записи движений регистра бухгалтерии при использовании БлокироватьДляИзменения, будет установлена по значениям только не оборотных субконто.

Если блокировка устанавливается для дальнейшей работы с остатками, то не рекомендуется указывать значения оборотных субконто при наложении блокировки (возможно использование как свойства БлокироватьДляИзменения, так и явное использование управляемой блокировки). Если блокировка устанавливается для дальнейшей работы с оборотами - следует указывать все необходимые значения субконто, в том числе и значения оборотных субконто (возможно использование только явного вызова управляемой блокировки).

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Установка управляемой блокировки при записи движений регистра бухгалтерии при использовании БлокироватьДляИзменения устанавливала блокировку по значениям всех субконто. Поведение БлокироватьДляИзменения для регистра бухгалтерии стало лучше соответствовать типовым задачам. При использовании БлокироватьДляИзменения устанавливаемая блокировка не включает оборотные субконто, что соответствует наиболее часто встречающимся случаям, когда блокировка используется для проверки остатков, а не для проверки оборотов.
Работа с запросами.
Если в поле запроса получается одно системное перечисление, и не комбинируется с другими типами, то при использовании в запросе операции СГРУППИРОВАТЬ ПО значения этого поля группируются вне зависимости, от того, откуда получается значение перечисления.

Аналогичное поведение обеспечивается для уникальных идентификаторов и ссылок на таблицы внешних источников данных.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Если в поле запроса получается одно системное перечисление, и не комбинируется с другими типами, то при использовании в запросе операции СГРУППИРОВАТЬ ПО значения этого поля могли не группироваться, в зависимости, от того, откуда получались значение перечисления.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Работа с СУБД.
При работе с СУБД Microsoft SQL Server изменены типы полей таблиц, используемые для хранения некоторых типов реквизитов конфигурации (дата и время, строковые данные неограниченной длины и двоичные данные неограниченной длины). Новые типы полей используются при отключенном режиме совместимости и после выполнения реструктуризации соответствующего объекта конфигурации.

Для выполнения реструктуризации таблиц базы данных с изменением типов полей необходимо установить нужный режим режим совместимости и выполнить операцию реструктуризации информационной базы в конфигураторе (Главное меню - Администрирование - Тестирование и исправление).

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При работе с СУБД Microsoft SQL Server использовались другие типы полей таблиц, используемые для хранения некоторых типов реквизитов конфигурации (дата и время, строковые данные неограниченной длины и двоичные данные неограниченной длины). Реализовно более оптимальное соответствие хранимых типов и типов полей таблиц СУБД Microsoft SQL Server.
Работа с СУБД.
При работе со всеми СУБД изменена структура индексов по полям составного типа. В результате уменьшено количество индексов. Такое построение индексов осуществляется при отключенном режиме совместимости и после выполнения реструктуризации соответствующего объекта конфигурации.

Для выполнения реструктуризации таблиц базы данных с изменением индексов необходимо установить нужный режим режим совместимости и выполнить операцию реструктуризации информационной базы в конфигураторе (Главное меню - Администрирование - Тестирование и исправление).

В режиме совместимости с версией 8.3.7 поведение не изменилось.

При работе со всеми СУБД использовалась другая структура индексов по полям составного типа. Уменьшено количество индексов для таблиц, хранящих объекты с реквизитами составного типа, что ведет к повышению производительности при работе с такими объектами.
Расширение конфигурации.
При выполнении фонового задания, в сеансе фонового задания подключаются те же расширения, что и в сеансе, из которого это фоновое задание запущено. В режиме совместимости с версией 8.3.7 поведение не изменилось.

Для объекта МенеджерРасширенийКонфигурации реализован метод ВыполнитьФоновоеЗаданиеСРасширениямиБазыДанных(), который позволяет выполнить запуск фонового задания, аналогичного предыдущим версиям «1С:Предприятие».

При выполнении фонового задания, в сеансе фонового задания подключались все расширения, зарегистрированные для информационной базы.Запуск фоновых заданий более точно наследует окружение, в котором выполняется родительский сеанс.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
В тонком и толстом клиенте, при начале ввода в ячейке таблицы управляемой формы генерируется событие АвтоПодбор.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В тонком и толстом клиенте, при начале ввода в ячейке таблицы управляемой формы генерировалось событие НачалоВыбора.Устранено отличие в поведении поля ввода в случае начала ввода в ячейке таблицы от других случаев работы поля ввода.
Технологический журнал.
В документацию внесена рекомендация не создавать более 20 элементов <LOG> в файле logcfg.xml. Создание файла настройки технологического журнала с большим количеством элементов <LOG>, приведет к снижению производительности платформы.В документации отсутствовала рекомендация по количеству элементов <LOG> в файле logcfg.xml.Документирована рекомендация для исключения проблем неэффективного использования технологического журнала.
В документации данное изменение описано здесь.
Автоматизированное тестирование.
Панель разделов, которая не отображается в главном окне из-за того, что не содержит элементов, более не попадет в список подчиненных объектов, которые возвращает метод ТестируемыйКомандныйИнтерфейсОкна.ПолучитьПодчиненныеОбъекты().Панель разделов, которая не отображается в главном окне из-за того, что не содержит элементов, попадала в список подчиненных объектов, которые возвращает метод ТестируемыйКомандныйИнтерфейсОкна.ПолучитьПодчиненныеОбъекты(). Устранено незапланированное поведение системы.
Автоматизированное тестирование.
В документацию добавлена рекомендация по использованию методов НайтиОбъект() и НайтиОбъекты() для доступа к необходимому элементу списка подчиненных объектов (вместо доступа по индексу).Документация не содержала рекомендации по использованию методов НайтиОбъект() и НайтиОбъекты() для доступа к необходимому элементу списка подчиненных объектов.Улучшена документация к системе.
Управляемая форма.
Обработчик события ПриЗакрытии и оповещение, установленное в свойстве формы ОписаниеОповещенияОЗакрытии, не вызываются, если управляемая форма закрывается с помощью метода Закрыть(), вызванного в обработчике события ПриОткрытии.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Если управляемая форма закрывалась с помощью метода Закрыть(), вызванного в обработчике события ПриОткрытии, то:
  • в веб-клиенте не происходило вызова обработчика события ПриЗакрытии и оповещения, установленного в свойстве ОписаниеОповещенияОЗавершении.
  • в тонком клиенте происходил вызов обработчика события ПриЗакрытии и оповещения, установленного в свойстве ОписаниеОповещенияОЗавершении.
Унифицировано поведение различных клиентских приложений.
Управляемая форма.
В документации отражено следующее поведение системы - если выполняется присвоение значения необъявленной переменной, совпадающей по имени со свойством, доступном в текущем контексте, то может диагностироваться ошибка времени выполнения или во время проверки конфигурации. Чтобы избежать появления ошибок, рекомендуется явно объявлять переменные с такими именами с помощью оператора Перем.В документации отсутствовало явное описание такого поведения.В документации приведено явное описание существующего механизма и приведены рекомендации по исключению негативных последствий.
В документации данное изменение описано здесь.
Оконная система.
Изменился порядок следования элементов в коллекции, возвращаемой методом ПолучитьОкна(). В документации и синтакс-помощнике отражено, что порядок следования объектов в возвращаемой коллекции является неопределенным и в алгоритмах не следует ориентироваться на какой-либо порядок следования элементов.В документации не содержалась информация о том, что порядок следования элементов коллекции, возвращаемой методом ПолучитьОкна(), является неопределенным.В документации уточнено использование метода ПолучитьОкна().
Работа с XML, XDTO.
При попытке записать некорректное квалифицированное имя элемента генерируется исключение.

В режиме совместимости с версией 8.3.6 и 8.3.7 поведение не изменилось.

При попытке записать некорректное квалифицированное имя элемента исключение не генерировалось. В результате мог быть записан некорректный XML-файл.Устранено некорректное поведение системы, привнесенное в версии 8.3.6.
Динамический список.
Если у текущего пользователя отсутствует право Просмотр на ключевое поле динамического списка, получение данных этим динамическим списком приводит к ошибке нарушения прав доступа.

В информации для технической поддержки будет доступен список полей, на которые отсутствуют права доступа.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

Отсутствие права Просмотр на ключевые поля динамического списка не влияло на работоспособность этого списка. При наличии условного оформления формы, в котором задействованы ключевые поля вышеупомянутого динамического списка - форма не открывалась.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Обмен данными.
Устранено некорректное поведение системы при создании записи для объекта ЭтотУзел плана обмена, которое присутствовало в версиях системы «1С:Предприятие», между версиями 8.3.8.1606 и 8.3.8.1861 (включая обе граничные версии).

Если переход на текущую версию системы «1С:Предприятие» выполняется:

  • С версии 8.3.7 и младше - какие-либо действия предпринимать нет необходимости.
  • С версии из указанного выше интервала - рекомендуется воспользоваться утилитой административной консоли (1cv8a) или выполнить операцию тестирования и исправления с включенным флажком Проверка логической целостности (если любая из указанных операций еще не выполнялись после перехода).

В том случае, если в объектах информационной базе сохраняются ссылки на элементы планов обмена и сохраняемые ссылки могут указывать на элемент ЭтотУзел, рекомендуется скорректировать эти ссылки с помощью обработки Исправление ссылок на неправильную запись ЭтотУзел, размещенной на диске ИТС (см. здесь). Обработка может использовать для своей работы либо результат работы утилиты административной консоли (рекомендуется) либо состояние пометки удаления записей планов обмена.

Рекомендуется использовать утилиту административной консоли (1cv8a), запущенную в режиме тестирования и исправления с включенным режимом формирования отчета о результатах работы. Сформированный отчет следует использовать в качестве входных данных для работы обработки Исправление ссылок на неправильную запись ЭтотУзел.

Система «1С:Предприятие» в интервале версий между 8.3.8.1606 и 8.3.8.1861 (включая обе граничные версии), некорректно формировала запись плана обмена, описывающая элемент ЭтотУзел, что могло приводить к одному из следующих проявлений (список не полный):
  • Дублирование записей ЭтотУзел;
  • Отсутствие записи ЭтотУзел;
  • Аварийное завершение при открытии формы списка плана обмена;
  • И т.д.

Система «1С:Предприятие» версии 8.3.7 и младше не содержала указанных проблем.

Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Динамический список.
В источнике доступных настроек компоновки данных для динамического списка, недоступны для отбора, сортировки и группировки следующие поля:
  • Дочерние поля полей, являющихся агрегатными функциями языка запросов;
  • Дочерние поля полей из других (внешних) источников данных;
  • Дочерние поля–характеристики полей табличных частей.

Поиск через строку поиска по ссылочным полям, являющимся агрегатными функциями языка запросов, не выполняется.

В режиме совместимости с версией 8.3.7 поведение не изменилось.

В источнике доступных настроек компоновки данных для динамического списка, были доступны для отбора, сортировки и группировки следующие поля:
  • Дочерние поля полей, являющихся агрегатными функциями языка запросов;
  • Дочерние поля полей из других (внешних) источников данных;
  • Дочерние поля–характеристики полей табличных частей

При установке отбора на такие поля, динамический список мог работать неправильно – не отображать часть или все данные.

Поиск, через строку поиска, по ссылочным полям, являющимися агрегатными функциями языка запросов, пытался выполняться. При этом могли выдаваться ошибки, а в случае если ошибки не выдавались – динамический список мог работать неправильно: не отображать часть или все данные.

Улучшен поиск в динамическом списке с использованием строки поиска.

Уменьшено количество ошибочных ситуаций, непонятных пользователю и разработчику.

В документации данное изменение описано здесь.
Динамический список.
В режиме 1С:Предприятие, в динамическом списке с заданным произвольным запросом и указанной основной таблицей, доступность для отбора полей основной таблицы (и их дочерних полей) не зависит от присутствия этих полей в тексте запроса динамического списка. Поля основной таблицы неявно добавляются в текст запроса, если они отсутствуют в тексте запроса.

Если в тексте запроса, установленном для динамического списка, уже есть поле, псевдоним которого совпадает с псевдонимом поля основной таблицы – для отбора будет использоваться именно это поле, в независимости от того действительно оно является этим полем основной таблицы.

Поля, имеющие несколько вариантов пути (на разных вариантах встроенного языка), доступны только на текущем варианте встроенного языка.

В режиме совместимости с версией 8.3.7 и более ранними, поведение не изменилось.

Для отбора были доступны только поля присутствующие в тексте запроса и стандартные поля (Ссылка и т.п.) основной таблицы. Если поместить в отбор недоступные поля с именами, совпадающими с именами полей из основной таблицы – такой отбор мог примениться успешно.Для динамического списка, в котором указан произвольный запрос и основная таблица, стало возможно указывать в параметрах выбора и связях параметров выбора поля основной таблицы, которые отсутствуют в тексте запроса.
В документации данное изменение описано здесь.
Регистры накопления.
Регистры бухгалтерии.
Устранено некорректное поведение системы при расчете итогов регистров накопления и бухгалтерии в том случае, если в списке измерений есть хотя-бы одно измерение с типом Строка и в состав индекса по измерениям входит более 16 полей базы данных.

При переходе на систему «1С:Предприятие» версии 8.3.8 и старше, рекомендуется воспользоваться специальной обработкой, размещенной на диске ИТС (см. здесь). Результатом работы обработки является информация о том, нужно выполнять какие-то дополнительные действия или нет.

Если дополнительные действия нужны, рекомендуется однократно (после перехода на новую версию) выполнить операцию тестирования и исправления с включенными флажками Проверка логической целостности информационной базы и Пересчет итогов или воспользоваться утилитой административной консоли (1cv8a). В случае использования утилиты необходимые действия будут выполнены быстрее.

+

При работе с регистрами накопления и бухгалтерии был возможен некорректный расчет итогов в том случае, если среди измерений указанных регистров присутствовало измерение типа Строка и в состав индекса по измерениям входило более 16 полей базы данных.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Работа с Интернет.
Средства публикации веб-клиента, Web-сервисов и HTTP-сервисов.
Реализована возможность блокировки перенаправления на потенциально опасные сайты после окончания операции с провайдером OpenID. Для этого в файле default.vrd реализован элемент <returnto> (подчиненный элементу <provider>), с помощью которого можно указать список URL, на которые допускается переадресация после завершения операции.

Указание элементов <returnto> не поддерживается при публикации провайдера OpenID с помощью конфигуратора (существующие элементы удаляются, новые не формируются). Даные элементы необходимо указывать вручную.

При переходе на новую версию системы «1С:Предприятие», запросы к провайдеру OpenID с параметром openid.return_to будут возвращать ошибку HTTP 400.

Для восстановления работоспособности провайдера OpenID необходимо в соответствующем файле default.vrd внести необходимое количество элементов <returnto> с указанием URL, на которые допускается переадресация.

Отсутствовала возможность управлять перенаправлением после окончания операции с провайдером OpenID.Повышена безопасность работы провайдера OpenID.
В документации данное изменение описано здесь и здесь.
Системные требования.
Изменен список поддерживаемых операционных систем и веб-браузеров:
  • Тонкий клиент, толстый клиент, веб-клиент и сервер «1С:Предприятие», работающие под ОС Windows:
    • Windows XP Service Pack 3;
    • Windows Vista и выше со всеми установленными обновлениями;
    • Windows Server 2003 и выше со всеми установленными обновлениями.
  • Поддерживается Mozilla Firefox версии 38 и старше при работе под управлением ОС Windows и Linux.
Список поддерживаемых операционных систем и веб-браузеров был другим:
  • Тонкий клиент, толстый клиент, веб-клиент и сервер «1С:Предприятие», работающие под ОС Windows:
    • Windows XP без требования Service Pack 3;
    • Windows Vista и выше без требования установки всех обновлений;
    • Windows Server 2003 и выше без требования установки всех обновлений.
  • Поддерживался Mozilla Firefox версии 17 и старше при работе под управлением ОС Windows и Linux.
Для работы стали требоваться более безопасные версии операционных систем семейства Microsoft Windows.
Клиентское приложение.
Установка клиентского приложения.
Внешние компоненты.
В связи с тем, что ОС Windows версий 2008 R2 и старше, начиная с января 2017 года, прекращает доверять сертификатам, которые используют алгоритм SHA-1, реализованы следующие изменения:
  • Файлы .msi и .mst, входящие в состав дистрибутива платформы «1С:Предприятие», подписываются с использованием алгоритма SHA-256, остальные файлы подписываются с использованием алгоритмов SHA-1 и SHA-256.
  • В документацию по созданию внешних компонент (см. здесь) внесены рекомендации о необходимости подписывать файлы установщиков внешних компонент с использованием алгоритмов SHA-1 и SHA-256. Файлы .msi рекомендуется подписывать с использованием алгоритма SHA-256.

+

+

Все файлы, входящие в состав дистрибутива платформы «1С:Предприятие», подписывались с использованием алгоритма SHA-1.

В документации по созданию внешних компонент (см. здесь) отсутствовали рекомендации:

  • О необходимости подписывать файлы установщиков внешних компонент с использованием алгоритмов SHA-1 и SHA-256.
  • О необходимости подписывать файлы .msi с использованием алгоритма SHA-256.
Исполняемые файлы платформы будут проходить проверку на всех поддерживаемых операционных системах семейства Windows.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Представление команды ОтменаПроведения.
  • Отмена проведения
  • Отменить проведение
Имя свойства Режим использования синхронных вызовов расширений платформы и внешних компонент.
  • РежимИспользованияСинхронныхВызововРасширенийИВнешнихКомпонент.
  • РежимИспользованияСинхронныхВызововРасширенийПлатформыИВнешнихКомпонент.
Имя параметра, содержащего имя создаваемого каталога в методе НачатьСозданиеКаталога().
  • Каталог.
  • ИмяКаталога.
Кнопка начала обновления в диалоге обновления клиентского приложения по протоколу HTTP.
  • Обновить.
  • Обновить и запустить.

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Средства разработки.
Сборщик мобильных приложений.
Реализована возможность работать с сервисами покупок в приложениях на мобильной платформе. Для работы используются сервисы Apple In-App Purchase (для ОС iOS) и Google Play In-App Billing (для ОС Android). Использование встроенных покупок в ОС Windows не поддерживается. Реализовано разрешение мобильного приложения Встроенные покупки.

Реализованы объекты ВстроенныеПокупки, ВстроеннаяПокупка, КвитанцияВстроеннойПокупки, ПроверкаВстроенныхПокупок.

Для проверки механизмов работы с покупками, на платформе для персонального компьютера реализовано свойство глобального контекста ПроверкаВстроенныхПокупок.

Для отладки механизма работы с покупками на мобильной платформе разработчика под управлением ОС Android реализован специальный HTTP-сервис, предоставляющий программный интерфейс, аналогичный Google Play In-App Billing. Также реализована возможность провести полный цикл работы с покупками: создание покупки, имитация различных ситуаций при работе приложения и т.д. HTTP-сервис (имя сервиса PurchaseTest) и инструмент для тестирования предоставляется сборщиком мобильных приложений.

Сборщик мобильных приложений поддерживает сборку мобильных приложений, работающих со встроенными покупками.

Данная возможность не предоставлялась.Стало возможно организовывать в мобильном приложении различного рода подписки, покупки различных функциональностей и т.д. Стало возможно создавать приложения, часть возможностей которых доступна после оплаты.
В документации данное изменение описано здесь.
Средства разработки.
Сборщик мобильных приложений.
Реализована возможность показывать рекламу в приложениях на мобильной платформе. Для работы используются сервисы iAd (для ОС iOS) и AdMob (для ОС Android). Использование рекламы в ОС Windows не поддерживается.

Реализован объект ОтображениеРекламы.

Сборщик мобильных приложений поддерживает сборку мобильных приложений, работающих с рекламой.

Данная возможность не предоставлялась.Стало возможно создавать приложения, позволяющие разработчику мобильного приложения зарабатывать на рекламе.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность экспорта табличного документа в формат PDF.Данная возможность не предоставлялась.Расширены возможности мобильного приложения в части представления данных.
Отображение информации.
При работе в ОС Android версии 4.1 и выше, реализована возможность корректного представления чисел в том случае, если параметр форматирования ЧГ функции Формат() содержит две группы.При работе в ОС Android версии 4.1 и выше, число представлялось некорректно в том случае, если параметр форматирования ЧГ функции Формат() содержал две группы.Устранено некорректное поведение системы.
Работа с файлами.
В мобильной платформе реализована поддержка асинхронных методов работы c файлами (методы глобального контекста и объект Файл).Данная функциональность не поддерживалась на мобильной платформе.Повышена возможность совместного использования программного кода прикладных решений одновременно мобильной платформой и платформой для персонального компьютера.
Полнотекстовый поиск.
На мобильной платформе реализована поддержка метода МенеджерПолнотекстовогоПоиска.ПроверитьИндекс().

В синтакс-помощнике методы объекта МенеджерПолнотекстовогоПоиска отмечены как доступные на мобильной платформе.

Данная функциональность не поддерживалась на мобильной платформе.

Синтакс-помощник ошибочно не указывал на доступность методов объекта МенеджерПолнотекстовогоПоиска на мобильной платформе.

Расширены возможности мобильной платформы по работе с полнотекстовым поиском. Актуализирован синтакс-помощник.
Работа с Интернет.
На мобильной платформе реализована поддержка возможности управлять наличием BOM при установке тела запроса из строки для объектов HTTPЗапрос и HTTPСервисОтвет.

На мобильной платформе реализовано системное перечисление ИспользованиеByteOrderMark.

Данная функциональность не поддерживалась на мобильной платформе.Облегчено взаимодействие мобильного приложения с системами, которые не ожидают BOM в HTTP-запросах.
Общие объекты.
Реализована доступность объекта ЗапускПриложенияМобильногоУстройства на платформах iOS и Windows. Для определения фактической доступности данной возможности реализован метод ЗапускПриложенияМобильногоУстройства.ПоддерживаетсяЗапуск(). С помощью метода прикладной разработчик может определить возможность запускать внешние приложения на данном устройстве.Объект ЗапускПриложенияМобильногоУстройства был недоступен на платформах iOS и Windows.Поведение приведено в соответствие с общей схемой работы с возможностями, доступными не на всех мобильных устройствах или операционных системах.
Управляемая форма.
Расширена информация в синтакс-помощнике по свойствам элементов управляемой формы Активизировать по умолчанию и Кнопка по умолчанию.

Свойство поля ввода управляемой формы Режим выбора незаполненного стало доступным в формах, предназначенных для мобильной платформы.

Свойство таблицы управляемой формы Режим выделения строки стало недоступно в формах, предназначенных для мобильной платформы.

+

Информация в синтакс-помощнике была неактуальной.

Доступность некоторых свойств элементов управляемой формы не соответствовала возможностям мобильной платформы.

Синтакс-помощник и конфигуратор приведены в соответствие с возможностями мобильной платформы.
Сборщик мобильных приложений.
Изменена структура хранения данных в сборщике мобильных приложений. Конвертация данных при обновлении версии сборщика может выполняться существенное время.Структура хранения данных в сборщике мобильных приложений была другой.Структура хранения данных в сборщике мобильных приложений стала более эффективной.
Средства разработки.
При указании в мобильном приложении сервера отладки, который работает не по протоколу HTTP, сообщение об ошибке стало явно указывать на это: Отладка возможна только по протоколу HTTP.При указании в мобильном приложении сервера отладки, который работает не по протоколу HTTP, сообщение об ошибке не описывало суть проблемы.Улучшена диагностика проблемных ситуаций при разработке мобильного приложения.
Средства печати.
Изменен дизайн формы настроек параметров страницы для печати в мобильной платформе:
  • кнопка ОК перенесена в заголовок окна.
  • убрано дублирование заголовка Масштаб.
Дизайн формы настроек параметров страницы для печати мобильной платформы был другим:
  • кнопка ОК располагалась в самой форме.
  • заголовок Масштаб дублировался на форме.
Улучшен дизайн формы настроек параметров страницы.
Специальные возможности мобильного устройства.
Не поддерживается фоновое использование геопозиционирования на устройствах под управлением iOS.Возможность фонового использования геопозиционирования на устройствах под управлением iOS не документировалась.Уточнены особенности использования мобильного приложения при работе под управлением iOS.
В документации данное изменение описано здесь.

Оглавление

Обновление используемых библиотек

Оглавление

Переход с предыдущей версии на версию 8.3.8

Оглавление

Версия 8.3.7

Версия 8.3.7 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v837doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.6. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4 и 8.3.5. +Возможность запуска конфигураций, разработанных в версии 8.3.6 и более младших, в версии 8.3.7, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.7 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.7, при необходимости, использовать для работы с информационной базой и версию 8.3.6. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Работа с ZIP-архивами.
Переработаны объекты ЗаписьZIPФайла и ЧтениеZipФайла с целью повышения стабильности при интенсивной работе большого числа пользователей и устранения проблем при работе с национальными символами в именах файлов.

Работа с zip-архивами реализована с помощью библиотеки zipArchive. Реализовано значение системного перечисления МетодСжатияZIP.BZIP2.

+

При работе с объектами ЗаписьZipФайла и ЧтениеZipФайла наблюдались проблемы при интенсивной работе большого числа пользователей и при работе с национальными символами в именах файлов.

Для работы с zip-архивами использовалась библиотека Info-ZIP. Метод сжатия BZIP2 не поддерживался.

Улучшено поведение системы при работе с zip-архивами (в том числе при использовании национальных символов в именах файлов). При работе в ОС Linux стало возможно использовать более подходящий формат файлов-архивов.
В документации данное изменение описано здесь.
Средства разработки.
В режиме пакетного запуска конфигуратора реализована возможность управления настройками поддержки конфигурации.

Реализован параметр командной строки пакетного запуска конфигуратора /ManageCfgSupport.

Данная возможность не предоставлялась.

Управление настройками поддержки конфигурации было доступно только в интерактивном режиме.

Упрощен процесс автоматизированной сборки и тестирования прикладных решений.
В документации данное изменение описано здесь.
Работа с Интернет.
Web-сервисы и HTTP-сервисы.
Реализована возможность использовать аутентификацию ОС при работе с Интернет и Web-сервисами. При создании WS-cсылки из конфигуратора невозможно отключить использование аутентификации ОС.

При получении списка информационных баз с помощью Web-сервиса используется аутентификация ОС, если в URL не указаны данные аутентификации.

Под управлением ОС Linux использование аутентификации ОС не поддерживается.

При работе с объектом ИнтернетПрокси реализована возможность управлять возможностью использования аутентификации ОС для каждого протокола. В режиме совместимости с версией 8.3.6 поведение не изменилось.

Реализован параметр ИспользоватьАутентификациюОС в конструкторе HTTPСоединение, WSОпределения, WSПрокси.

Реализовано свойство ИспользоватьАутентификациюОС у объектов HTTPСоединение, WSПрокси.

Для метода WSСсылкаМенеджер.СоздатьWSПрокси() реализован параметр ИспользоватьАутентификациюОС.

Для метода ИнтернетПрокси.Установить() реализован параметр ИспользоватьАутентификациюОС.

Для объекта ИнтернетПрокси реализован метод ИспользоватьАутентификациюОС().

Возможность использования аутентификации ОС при работе с Интернет и Web-сервисами не предоставлялась.

При получении списка информационных баз с помощью Web-сервиса не использовалась аутентификация ОС.

При работе с объектом ИнтернетПрокси использовалась basic-аутентификация в том случае, если установлены имя пользователя и пароль.

Расширены возможности использования Web-сервисов, работы с Интернет и получения списка информационных баз в корпоративных средах.
В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Реализована возможность использования Web-сервиса, расположенного по адресу, отличного от указанного в wsdl-файле, который импортирован в прикладное решение (элемент конфигурации WS-ссылка).

Для конструктора объекта WSПрокси реализован параметр Местоположение. Для метода WSСсылкаМенеджер.СоздатьWSПрокси() реализован параметр Местоположение.

Данная возможность не предоставлялась.

Web-сервис можно было использовать только в том случае, если он располагался по адресу, указанному в wsdl-файле, который импортирован в прикладное решение (элемент конфигурации WS-ссылка).

Расширены возможности использования Web-сервисов в тех случаях, когда используемый Web-сервис обладает фиксированным интерфейсом, но может располагаться по различным адресам в сети Интернет. Например, используется Web-сервис какого-либо прикладного решения, которое может быть установлено у большого числа заказчиков.
В документации данное изменение описано здесь, здесь и здесь.
Работа с JSON.
Работа с XML, XDTO.
Реализована возможность JSON-сериализации объектов XDTO.Данная возможность не предоставлялась.

Была доступна только потоковая и объектная техники работы с JSON.

Упрощено использование формата JSON для обмена между различными системами на базе «1С:Предприятия». +

+

В документации данное изменение описано здесь, здесь и здесь.
Работа с JSON.
Реализована возможность управлять экранированием символа косой черты при записи данных в формате JSON.

Для конструктора объекта ПараметрыЗаписиJSON реализован параметр ЭкранироватьСлеш. Для объекта ПараметрыЗаписиJSON реализовано свойство ЭкранироватьСлеш.

Свойство ЭкранироватьСлеш используется при работе метода ЗаписьJSON.ЗаписатьЗначение().

При работе с JSON отсутствовала возможность управлять экранированием символа косой черты.Повышение совместимости при работе с различными внешними системами, использующими обмен в формате JSON.
В документации данное изменение описано здесь.
Локализация.
Реализована поддержка азербайджанского языка для методов глобального контекста ЧислоПрописью() и ПредставлениеПериода(). Код локализации: az. Особенности указания параметра ПараметрыПредметаИсчисления метода ЧислоПрописью() приведены в синтакс-помощнике.Методы глобального контекста ЧислоПрописью() и ПредставлениеПериода() не поддерживали работу с азербайджанским языком.Упростилось представление информации для пользователей, говорящих на азербайджанском языке.
Локализация.
Реализована поддержка турецкого языка для методов глобального контекста ЧислоПрописью() и ПредставлениеПериода(). Код локализации: tr. Особенности указания параметра ПараметрыПредметаИсчисления метода ЧислоПрописью() приведены в синтакс-помощнике.Методы глобального контекста ЧислоПрописью() и ПредставлениеПериода() не поддерживали работу с турецким языком.Упростилось представление информации для пользователей, говорящих на турецком языке.
Локализация.
Реализована поддержка венгерского языка для методов глобального контекста ЧислоПрописью() и ПредставлениеПериода(). Код локализации: hu. Особенности указания параметра ПараметрыПредметаИсчисления метода ЧислоПрописью() приведены в синтакс-помощнике.Методы глобального контекста ЧислоПрописью() и ПредставлениеПериода() не поддерживали работу с венгерским языком.Упростилось представление информации для пользователей, говорящих на венгерском языке.
Табличный документ.
При экспорте табличного документа в форматы XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument Spreadsheet) в получившийся файл экспортируются следующие настройки печати табличного документа:
  • Размеры полей страниц;
  • Размеры колонтитулов;
  • Ориентация страницы;
  • Размер страницы;
  • Масштаб печати;
  • Признак черно-белой печати;
  • Область печати;
  • Информация о повторяющихся на каждой странице строках и колонках;
  • Текст колонтитулов.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

При экспорте табличного документа в форматы XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument Spreadsheet) в получившийся файл настройки печати табличного документа не экспортировались.Повышена корректность экспорта табличного документа в популярные форматы табличных документов.
Расширение конфигурации.
В расширении конфигурации реализована возможность создавать WS-ссылки, XDTO-пакеты, Web-сервисы и HTTP-сервисы.

Реализована возможность публикации интернет-сервисов расширения на веб-сервере.

Для файла default.vrd реализован атрибут publishExtensionsByDefault для элементов ws и

httpServices.

Данная возможность не предоставлялась.Расширение конфигурации стало предоставлять больше возможностей.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Интерфейс OData.
Для стандартного интерфейса OData реализована возможность работы с независимым регистром сведений без измерений. Реализовано свойство SurrogateKey, описывающее суррогатный ключ.Данная возможность не предоставлялась.Реализация объектов «1С:Предприятия» стала более полно соответствовать стандарту OData.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Фоновые и регламентные задания.
Реализована возможность быстрого определения того, что текущий сеанс является сеансом фонового задания.

Реализован метод глобального контекста ПолучитьТекущийСеансИнформационнойБазы(). Реализован метод СеансИнформационнойБазы.ПолучитьФоновоеЗадание().

Данная возможность не предоставлялась.

Определение вида сеанса было возможно с помощью получения всех сеансов информационной базы и их последующего перебора.

Ускорено определение того, что сеанс является сеансом фонового задания, например, для разделения кода инициализации клиентского приложения и фонового задания.
В документации данное изменение описано здесь.
Работа с СУБД.
Выгрузка информационной базы в файл .dt будет прервана при обнаружении проблем с внутренней стуктурой информационной базы.При выгрузке информационной базы в файл .dt не анализировалось состояние внутренней структуры информационной базы.Снижена вероятность получения файла .dt, который нельзя будет загрузить.
Общие объекты.
Реализована возможность записи и чтения данных в случае запрета использования синхронных вызовов для объектов ТекстовыйДокумент, ТабличныйДокумент, ФорматированныйДокумент, ГрафическаяСхема, ПакетОтображаемыхДокументов (только запись).

Реализован метод НачатьЗапись() для объектов ТекстовыйДокумент, ТабличныйДокумент, ФорматированныйДокумент, ГрафическаяСхема.

Реализован метод НачатьЧтение() для объектов ТекстовыйДокумент, ГрафическаяСхема.

Реализован метод ПакетОтображаемыхДокументов.НачатьЗаписьФайлаДляПечати().

Данные возможности не предоставлялись.Реализована недостающая функциональность для поддержки работы системы в связи с изменениям в работе веб-браузера Google Chrome.
В документации данное изменение описано здесь.
Работа с криптографией.
Для свойств Издатель и Субъект объекта СертификатКриптографии реализована возможность получить доступ ко всем полям, описывающим издателя и субъекта, которые содержатся в сертификате.

Для свойств Издатель и Субъект объекта СертификатКриптографии реализовано свойство Street.

Все свойства структур Издатель и Субъект объекта СертификатКриптографии представлены два раза:

  • ключ представлен в виде мнемонического идентификатора (например, CN).
  • ключ представлен в виде универсального идентификатора (например, OID2_5_4_3 для поля CN).
С помощью свойств Издатель и Субъект объекта СертификатКриптографии не было возможности получить доступ ко всем полям, которые содержатся в сертификате.При работе с сертификатами стало возможно использовать все поля, включая поля, наличие которых обусловлено требованием регулятора.
Работа с СУБД.
При работе с СУБД Oracle Database табличное пространство V81C_INDEX_BIG создается платформой автоматически в том случае, когда происходит попытка построить индекс по более чем 3 строковым полям.При попытке построить индекс по более чем 3 строковым полям, при работе в СУБД Oracle Database, генерировалась ошибка, если отсутствовало табличное пространство V81C_INDEX_BIG. Табличное пространство можно было создать вручную.Исключена необходимость ручного изменения структуры базы данных.
В документации данное изменение описано здесь.
Расширение конфигурации.
Предопределенные данные.
Для расширения конфигурации реализована возможность заимствования предопределенных элементов. При этом становится возможным контролировать наличие необходимых предопределенных элементов, состав и правила регистрации объектов в плане обмена, использовать конструктор запросов.Данная возможность не предоставлялась.Расширения конфигурации стали более функциональными.
В документации данное изменение описано здесь и здесь.
Средства разработки.
Реализована возможность выгрузки и загрузки конфигурации в файлы в иерархическом формате.

Имя нового объекта конфигурации ограничено 80 символами. Существующие объекты конфигурации могут иметь имена длиннее 80 символов, но только до любой попытки редактирования такого имени.

Файл с модулем на встроенном языка имеет расширение .bsl.

В диалоге выгрузки конфигурации в файлы реализована возможность выбора формата выгрузки: линейный или иерархический.

Для ключа командной строки пакетного запуска конфигуратора /DumpConfigToFiles реализован параметр -Format для указания формата выгрузки.

По умолчанию выгрузка использует иерархический формат.

Выгрузка и загрузка конфигурации в файлы выполнялась с использованием только линейного формата.

На имя объекта конфигурации не накладывались ограничения по длине.

Файл с модулем на встроенном языке имел расширение .txt.

Стало возможно существенно снизить вероятность прерывания выгрузки конфигурации в файлы из-за того, что полное имя объекта конфигурации (которое используется в качестве имени файла), вместе с путем, по которому сохраняется этот файл, превысит ограничение на длину пути к файлу (или компонентов этого пути), действующее в той файловой системе, в которую выполняется выгрузка.
В документации данное изменение описано здесь, здесь и здесь.
Средства разработки.
Реализована возможность частичной загрузки конфигурации из файлов: добавление объекта конфигурации, изменение объекта конфигурации, удаление объекта конфигурации, переименование объекта конфигурации, изменение некоторых свойств объекта конфигурации (модули, справка). Реализована возможность одновременной загрузки конфигурации из файлов и обновления конфигурации базы данных.

Для ключа командной строки пакетного запуска конфигуратора /LoadConfigFromFiles реализованы параметр -files (для указания загружаемых файлов) и -listFile (для указания файла со списком загружаемых файлов).

Реализовано событие технологического журнала <CONFLOADFROMFILES>.

Данная возможность не предоставлялась.

Была доступна только полная загрузка конфигурации из файлов.

Стало возможно ускорить процесс обновления системы в том случае, если конфигурация хранится во внешней системе.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства разработки.
Реализован новый вариант механизма отладки прикладных решений. В настройках конфигуратора имеется возможность выбирать, какой вариант отладчика будет использоваться для отладки. Для работы отладчика используется протокол HTTP.

Переработан диалог автоматического подключения предметов отладки.

Реализован сервер отладки (dbgs), который может быть запущен из командной строки и как сервис операционной системы. Не поддерживается использование нового протокола отладки на сервере под управлением ОС Linux в том случае, если настроен автоматический запуск сервера «1С:Предприятия» при старте ОС.

Для агента сервера (ragent) реализованы ключи командной строки запуска /debug, /debugServerAddr, /debugServerPort, /debugServerPwd.

Для клиентского приложения реализован ключ командной строки запуска /debug.

Для элемента <debug>, файла default.vrd, реализован атрибут protocol.

Для элемента <config>, файла comcntrcfg.xml, реализован атрибут protocol.

Данная возможность включена в статусе бета-версии.

В системе был реализован только один вариант отладки.Возможность отлаживать прикладные решения, подключение к которым возможно только по протоколу HTTP. Новый механизм расширил возможности применения отладчика.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Локализация.
Реализована возможность создания локализации интерфейса платформы «1С:Предприятие», в той части, которая необходима для функционирования конкретного прикладного решения. Инструменты, необходимые для выполнения локализации, необходимо дополнительно запрашивать у фирмы «1С», по электронной почте int@1c.com. Такая локализация обладает следующими ограничениями:
  • Не поддерживается возможность локализации картинок;
  • Не предоставляется возможность сборки дистрибутива платформы.
Локализация выполнялась только полностью и поставлялась в дистрибутиве платформы.Реализована возможность выполнять перевод интерфейса платформы для конкретных прикладных решений и внедрений. Это востребовано в случаях, когда с прикладным решением будут работать пользователи, для родного языка которых не существует поставляемого с платформой варианта интерфейса.
Средства разработки.
В справке конфигуратора и документации перечислены имена исполняемых файлов предопределенных внешних программ сравнения/объединения модулей. Указанные имена следует указывать при настройке параметров запуска внешних программ сравнения/объединения модулей.В справке конфигуратора и в документации не были перечислены имена исполняемых файлов предопределенных внешних программ сравнения/объединения модулей.Улучшена справка конфигуратора и документация к системе.
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
Реализовано версионирование формата выгрузки конфигурации в файлы. Выгрузка, выполняемая системой «1С:Предприятие» версии 8.3.6 имеет номер 1.0. Выгрузка, выполняемая платформой «1С:Предприятие» версии 8.3.7 имеет номер 2.0.

Если в файлах выгрузки номер версии отсутствует - считается, что выгрузка создана в формате 1.0.

Выгрузка всегда выполняется в формате текущей версии платформы «1С:Предприятие».

Загрузка выполняется успешно только в том случае, если версия загружаемых файлов меньше или равна версии платформы «1С:Предприятие», с помощью которой загружаются файлы выгрузки.

Формат выгрузки конфигурации в файлы не версионировался.Уменьшено количество проблем, связанных с несовместимостью файлов выгрузки конфигурации различных версий «1С:Предприятия».
В документации данное изменение описано здесь.
Выгрузка/загрузка конфигурации в файлы.
Изменена выгрузка в файлы свойства Параметр элемента управляемой формы Кнопка. Если значение свойства Параметр ссылается на объект конфигурации, в файлы выгружается полное имя этого объекта конфигурации.При выгрузке конфигурации в файлы, свойство Параметр элемента управляемой формы Кнопка выгружалось в виде уникального идентификатора типа объекта конфигурации. Это происходило в том случае, если свойство Параметр ссылалось на объект конфигурации.Устранено несоответствие общепринятому подходу в конкретном элементе формата выгрузки конфигурации.
Средства администрирования.
Реализована проверка легальности использования прикладного решения на уровне платформы «1С:Предприятие». Проверка выполняется для прикладных решений, развернутых в файловом варианте или на сервере в версии МИНИ. При использовании прикладного решения, использующего базовую лицензию, проверка легальности использования не выполняется. Проверка выполняется при обращении платформы через Интернет в Центр защиты обновлений.

Информация о результатах проверки отображается в диалоге О программе.

В интерфейсе конфигуратора включены дополнительные команды для работы данного механизма. +

Реализованы методы глобального контекста: ПолучитьИдентификаторКонфигурации(), ПолучитьИмяКлиентаЛицензирования(), ПолучитьДополнительныйПараметрКлиентаЛицензирования(), УстановитьНастройкиКлиентаЛицензирования(), ПодключитьОбработчикЗапросаНастроекКлиентаЛицензирования(), ОтключитьОбработчикЗапросаНастроекКлиентаЛицензирования().

Для конфигурационного файла conf.cfg реализован параметр LicConfigDebugTimeouts, позволяющий уменьшать интервалы проверки.

Решения по порядку использования данного механизма публикуются отдельно.

Данная возможность не предоставлялась.Стало возможно выполнять проверку легальности использования прикладного решения.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
Реализована поддержка СУБД Oracle Database версии 12.1.0.2 (Linux).Данная версия СУБД Oracle Database не поддерживалась.Расширен список поддерживаемых версий СУБД Oracle Database.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Конфигуратор.
Клиентское приложение.
Кроссплатформенность.
Системные требования.
Доступно клиентское приложение, работающее под OS X 10.8 и старше (только в варианте 64-разрядного приложения). Поддерживается:
  • Работа тонкого клиента, толстого клиента и конфигуратора.
  • Файловый и клиент-серверный режим работы.

Под OS X не поддерживается работа сервера «1С:Предприятия». Ограничения клиентского приложения, работающего под ОС OS X, приведены в документации.

Поддерживается возможность одновременной установки и запуска различных версий «1С:Предприятия». +Данная возможность включена в статусе бета-версии.

Под OS X была доступна работа с информационной базой с помощью веб-клиента.Возможность разработки прикладных решений и работы клиентских приложений в OS X.

+

В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Системные требования.
Реализована поддержка дистрибутива Astra Linux Special Edition 1.4.Данный дистрибутив не поддерживался.Расширен список поддерживаемых дистрибутивов ОС Linux.
Внешние компоненты.
В технологию создания внешних компонент добавлено описание на английском языке в файле формата HTML. Описание технологии создания внешних компонент доступно на странице, предназначенной для скачивания файлов конкретной версии.Технология создания внешних компонент содержала описание только на русском языке.Создание внешних компонент стало доступно большему кругу разработчиков.
Работа с ZIP-архивами.
Имена файлов в zip-архивах, формируемых системой «1С:Предприятие», записываются в кодировке UTF-8 и текущей кодировке используемой ОС (если она отличается от UTF-8).

Zip-архивы, которые содержат файлы с национальными символами в именах, будут корректно читаться с помощью объекта ЧтениеZipФайла системы «1С:Предприятие» версии 8.3.6 и младше, а также встроенными архиваторами ОС Windows XP/2003/2008/7. При этом имена файлов в таких архивах будут некорректно отображаться встроенным архиватором OS X.

Имена файлов в zip-архивах записывались только в кодировке UTF-8. Имена файлов в zip-архивах, которые содержат файлы с национальными символами в именах, некорректно отображались с помощью объекта ЧтениеZipФайла системы «1С:Предприятие» версии 8.3.6 и младше, а также встроенными архиваторами ОС Windows XP/2003/2008/7.Zip-архивы, которые содержат файлы с национальными символами в именах, будут корректно читаться с помощью объекта ЧтениеZipФайла системы «1С:Предприятие» версии 8.3.6 и младше, а также встроенными архиваторами ОС Windows XP/2003/2008/7. При этом имена файлов в таких архивах будут некорректно отображаться встроенным архиватором OS X.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Интерфейс.
При работе в интерфейсе Такси удаление элемента из списка Избранное не сопровождается модальным диалогом-подтверждением. После удаления в панели Избранного появляется специальная гиперссылка для восстановления удаленного элемента.При работе в интерфейсе Такси удаление элемента из списка Избранное сопровождалось модальным диалогом-подтверждением.Стало возможно полноценно работать с панелью Избранное в веб-браузерах, которые не поддерживают модальные диалоги.
Интерфейс.
Для интерфейса Такси реализована возможность закрепления форм в рабочей области основного окна (форма постоянно доступна), а также возможность объединения двух форм таким образом, что объединенные формы всегда отображаются вместе при попытке переключения на любую из объединенных форм.

Для системного меню, контекстного меню панели открытых и контекстного меню заголовка формы реализованы соответствующие команды.

Данная возможность не предоставлялась.Использование системы стало более удобно в ряде случаев, например, при сравнении одинаковых отчетов за два разных периода.
В документации данное изменение описано здесь.
Отображение информации.
В случае ошибки аутентификации при работе с Web-сервисом, сообщение об ошибке больше не содержит текста html, который вернул веб-сервер.

Информативность самого сообщения не уменьшилась.

В случае ошибки аутентификации при работе с Web-сервисом, сообщение об ошибке содержало текст html, который вернул веб-сервер.Сообщение об ошибке аутентификации при работе с Web-сервисом, которое отображается пользователю, больше не содержит непонятной информации.
Интерфейс.
В некоторых сценариях исправлена подстановка реальных шрифтов и цветов вместо элементов стиля.В некоторых сценариях подстановка реальных шрифтов и цветов вместо элементов стиля выполнялась некорректно.Устранено некорректное поведение системы.
Клиентское приложение.
В справочную информацию клиентского приложения внесена информация о сочетании клавиш Ctrl+Shift+H, которое открывает историю.Информация о данном сочетании клавиш в справочной информации клиентского приложения отсутствовала.Актуализирована справочная информация клиентского приложения.
Веб-клиент.
Реализована работа с буфером обмена в веб-браузере Google Chrome с использованием команд контекстных меню, а не только клавиатуры.

Данная возможность доступна при установке специального расширения, доступ к которому автоматически предоставляет веб-клиент при попытке работы с буфером обмена с помощью меню. Если расширение не установлено, будет возможно работать с буфером обмена только с помощью клавиатуры.

Работа с буфером обмена в веб-браузере Google Chrome была возможна только с использованием клавиатуры. Работа с буфером обмена с помощью команд контекстного меню не поддерживалась.Использование веб-клиента с помощью веб-браузера Google Chrome стало более комфортным для пользователя.
Веб-клиент.
Реализована новая версия расширения для веб-браузера Mozilla Firefox. Расширение работает только в асинхронном режиме. Синхронные методы работы более недоступны.Для веб-браузера Mozilla Firefox существовала другая версия расширения браузера. Расширение позволяло работать в синхронном режиме.Реализована поддержка новых версий веб-браузера Mozilla Firefox (версия 40 и выше), которые не поддерживают синхронные методы работы (аналогично веб-браузеру Google Chrome 45 и выше).

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Средства разработки.
При работе в конфигураторе ускорено выполнение некоторых операций:
  • Открытие формы редактора подсистемы;
  • Включение объекта в подсистему;
  • Установка фильтра по подсистемам в окне с деревом конфигурации.
Некоторые операции в конфигураторе выполнялись недостаточно быстро.Уменьшено время выполнения некоторых операций при работе в конфигураторе.
Географическая схема.
При работе с географической схемой оптимизированы следующие операции:
  • Загрузка и отрисовка географической схемы;
  • Выбор объекта в поле географической схемы.
Работа с географической схемой выполнялась недостаточно быстро.Работа с географической схемой стала более комфортной.
Полнотекстовый поиск.
Оптимизирована работа полнотекстового поиска и построение индекса полнотекстового поиска.Построение индекса полнотекстового поиска и собственно полнотекстовый поиск работали недостаточно быстро.Ускорена работа полнотекстового поиска и построение индекса полнотекстового поиска. Ускорение особенно заметно в том случае, если информационная база содержит индексируемые объекты с большим количеством слов.
Полнотекстовый поиск.
Динамический список.
Ускорен поиск в динамическом списке с использованием строки поиска, в том случае, если для основной таблицы динамического списка используется полнотекстовый поиск и на поля основной таблицы динамического списка установлены отборы с видом сравнения Равно.Поиск в динамическом списке с использованием строки поиска работал недостаточно быстро.Ускорен поиск в динамическом списке с использованием полнотекстового поиска.
В документации данное изменение описано здесь.
Работа с запросами.
При выполнении запроса, обращающегося только к данным табличных частей, исключено соединение с таблицей родительского объекта.При выполнении запроса, обращающегося только к данным табличных частей, автоматически добавлялось соединение с таблицей родительского объекта.Устранено незапланированное поведение системы.
Работа с СУБД.
Оптимизировано чтение из СУБД объектов типа ДокументОбъект, СправочникОбъект, БизнесПроцессОбъект, ЗадачаОбъект, ПланВидовРасчетаОбъект, ПланВидовХарактеристикОбъект, ПланОбменаОбъект, ПланСчетовОбъект - чтение сопровождается неявным созданием транзакции только при наличии у объекта табличных частей и если СУБД используется «грязное» чтение вне транзакции.Чтение из СУБД объектов типа ДокументОбъект, СправочникОбъект, БизнесПроцессОбъект, ЗадачаОбъект, ПланВидовРасчетаОбъект, ПланВидовХарактеристикОбъект, ПланОбменаОбъект, ПланСчетовОбъект сопровождалось неявным созданием транзакции при наличии у объекта табличных частей.Уменьшено:
  • Количество ожиданий на блокировках для файловой СУБД.
  • Время загрузки объекта информационной базы из СУБД, при использовании сервера «1С:Предприятия».
  • Количество ожиданий на внутренних блокировках сервера «1С:Предприятие» при массовом чтении объектов информационной базы из СУБД.
  • Нагрузка на СУБД за счет значительного сокращения количества транзакций.
Управляемая форма.
Оптимизирована работа с условным оформлением в управляемой форме. Ускорено открытие управляемой формы с большим количеством элементов условного оформления.Работа с условным оформлением управляемой формы была недостаточно быстрой.Ускорено открытие управляемых форм, особенно а файловом варианте информационной базы и на медленных компьютерах.
Предопределенные данные.
Оптимизировано получение предопределенных данных с помощью метода ПредопределенноеЗначение(). Получение предопределенных данных с помощью метода ПредопределенноеЗначение() выполнялось недостаточно быстро. Ускорена работа с предопределенными данными.
Средства разработки.
Уменьшено время обновления конфигурации базы данных, не требующей реструктуризации таблиц базы данных и при наличии большого количества ролей.Обновление конфигурации базы данных, не требующей реструктуризации таблиц базы данных и при наличии большого количества ролей занимало много времени.Ускорено обновление конфигурации базы данных.
Управляемая форма.
Встроенный язык.
Ускорено открытие управляемой формы при работе в тонком и веб-клиентах.Открытие управляемой формы в тонком и веб-клиентах работал недостаточно быстро.Ускорена работа системы.
Работа системы.
Оптимизирована работа внутренних механизмов кеширования «1С:Предприятия». В результате ускорена работа большого числа механизмов системы, в числе которых:
  • Открытие форм;
  • Работа запросов;
  • Работа с функциональными опциями;
  • Работа с предопределенными данными;
  • Работа с повторно используемыми значениями;
  • Работа с данными «через точку»;
  • Другие механизмы.
Система работала не достаточно оптимально.Ускорена работа системы, особенно в файловом варианте и на компьютерах с небольшим количеством оперативной памяти (менее 4 Gb).
Ограничение доступа к данным.
Оптимизировано выполнение запросов для пользователей с неполными правами, с использованием ограничений доступа к данным, при большом количестве ролей. Время выполнения запроса не имеет существенной зависимости от количества ролей, назначенных пользователю.Запросы для пользователей с неполными правами, с использованием ограничения доступа к данным, выполнялись недостаточно быстро. Время выполнения запроса существенно зависело от количества ролей, назначенных пользователю.Ускорена работа конфигураций (включая открытие форм) с большим количеством ролей.
Динамический список.
Полнотекстовый поиск.
Если в динамическом списке выполняется поиск с использованием строки поиска, по полям, полученным не из основной таблицы динамического списка, то вначале используется полнотекстовый поиск по объектам, которые являются источниками этих полей. Поля тех объектов, по которым полнотекстовый поиск ничего не нашел, исключаются из дальнейшего поиска.Если в динамическом списке выполняется поиск с использованием строки поиска, дополнительные условия накладывались на все поля, отображаемые таблицей, связанной с динамическим списком.Ускорен поиск в динамическом списке в некоторых сценариях использования.
В документации данное изменение описано здесь.
Работа с запросами.
В языке запросов реализована оптимизация выражений, содержащих операции сравнения, в которых участвует константное значение и операция ВЫБОР, которая в качестве результата может принимать только константные значения. В результате оптимизации выражение или его часть может быть упрощено.В языке запросов отсутствовала оптимизация выражений, содержащих операции сравнения, в которых участвует константное значение и операция ВЫБОР, которая в качестве результата может принимать только константные значения.В ряде случаев может быть ускорено выполнение запросов.
Полнотекстовый поиск.
Ускорен ввод по строке при использовании полнотекстового поиска. Изменена структура данных индекса полнотекстового поиска. Новый формат используется при создании индекса полнотекстового поиска. Для того, чтобы задействовать новый формат индекса полнотекстового поиска, необходимо очистить индекс полнотекстового поиска и создать индекс заново. При этом следует установить значение свойства Режим совместимости в значение Не использовать.

Реализовано событие технологического журнала <INPUTBYSTRING> для отслеживания событий, связанных с вводом по строке.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Ввод по строке работал недостаточно быстро.

Индекс полнотекстового поиска хранился в другом формате.

Ускорен ввод по строке, что привело к повышению комфорта при работе с объектами системы, где используется этот механизм.
В документации данное изменение описано здесь и здесь.
Автоматизированное тестирование.
Ускорено выполнение команд сценария тестирования веб-клиентом, запущенным в режиме клиента тестирования.Выполнение команд сценария тестирования веб-клиентом, запущенным в режиме клиента тестирования, выполнялось недостаточно быстро.Ускорена работа автоматизированного тестирования при использовании веб-клиента.
Обмен данными.
Общие реквизиты / Разделение данных.
Ускорено создание начального образа информационной базы в том случае, если в состав плана обмена (по которому создается начальный образ) включен регистр, входящий в состав независимого разделителя, и в сеансе, из которого выполняется создание, этот разделитель не используется.Создание начального образа информационной базы в том случае, если в состав плана обмена (по которому создается начальный образ) включен регистр, входящий в состав независимого разделителя, и в сеансе, из которого выполняется создание, этот разделитель не используется, выполнялось недостаточно быстро.В некоторых случаях ускорено создание начального образа информационной базы.
Общие объекты.
Оптимизирована работа методов

ДоступныеТаблицыСхемыЗапроса.Найти(), ИсточникиСхемыЗапроса.Добавить() и ПараметрыТаблицыСхемыЗапроса.Количество().

Методы

ДоступныеТаблицыСхемыЗапроса.Найти(), ИсточникиСхемыЗапроса.Добавить() и ПараметрыТаблицыСхемыЗапроса.Количество() работали недостаточно быстро.

Ускорена работа со схемой запроса на встроенном языке.
Средства разработки.
Оптимизирована работа формы редактирования командного интерфейса конфигурации в случае наличия большого количества ролей. Увеличена производительность команд перемещения строк таблицы.Работа формы редактирования командного интерфейса конфигурации была недостаточно быстрой при большом количестве ролей.Повышен комфорт работы прикладного разработчика при редактировании командного интерфейса конфигурации с большим количеством ролей.
Работа с СУБД.
Регистры расчета.
При работе с СУБД PostgreSQL и IBM DB2 ускорено удаление записей о фактическом периоде действия регистра расчета при удалении больших наборов записей.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

При работе с СУБД PostgreSQL и IBM DB2 удаление записей о фактическом периоде действия регистра расчета при удалении больших наборов записей выполнялось недостаточно быстро.Оптимизировано удаление больших наборов записей из регистра расчета при работе с СУБД PostgreSQL и IBM DB2.
Табличный документ.
Ускорена установка размеров и положения рисунка табличного документа при работе на стороне сервера «1С:Предприятия».Установка размеров и положения рисунка табличного документа при работе на стороне сервера «1С:Предприятия» выполнялись недостаточно быстро.Повышена скорость формирование табличного документа в случае программного управления размером и положением рисунков табличного документа.
Управляемая форма.
Веб-клиент.
Кластер серверов.
Ускорено открытие управляемой формы при работе веб-клиента в клиент-серверном варианте, если кластер серверов развернут на компьютере под управлением ОС Linux.Открытие управляемой формы при работе веб-клиента в клиент-серверном варианте выполнялось недостаточно быстро, если кластер серверов развернут на компьютере под управлением ОС Linux.Ускорена работа веб-клиента, при работе с кластером серверов в ОС Linux.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Документация.
Начиная с «1С:Предприятия» версии 8.3.7, документация к платформе, на ИС ИТС (http://its.1c.ru/), будет соответствовать своей версии платформы. Документация к предыдущим версиям будет также доступна на ИС ИТС.

На диске ИТС будет доступна документация только к версии платформы «1С:Предприятие», актуальной на месяц, предыдущий месяцу выпуска диска.

Перевод документации к тестовой версии в статус актуальной будет выполняться одновременно с выходом финальной версии платформы.

Текущие ссылки на документацию (вида http://its.1c.ru/db/v83doc#bookmark:dev:TI000000167) всегда будут приводить в документацию к текущей актуальной (не тестовой) версии документации. Ссылки на разделы конкретной версии (например из файла V8Update) будут иметь другой вид (с указанием более полного номера версии в ссылке).

На ИС ИТС документация присутствовала в единственном экземпляре. Документация обновлялась в момент выхода тестовой версии платформы. После выхода ознакомительной версии получить доступ на ИС ИТС к документации текущей, актуальной, версии было невозможно.Улучшено структурирование документации. Появилась возможность четко разделять документацию к тестовой, текущей и предыдущим версиям платформы «1С:Предприятие».
Управляемая форма.
В меню Создать (в форме журнала документов) отсутствуют виды документов, отключенные функциональными опциями.

В меню Показать в списке (в форме документа) отсутствуют формы списков, отключенные функциональными опциями. +

В меню Создать (в форме журнала документов) присутствовали виды документов, отключенные функциональными опциями.

В меню Показать в списке (в форме документа) присутствовали формы списков, отключенные функциональными опциями. +

Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Динамическое обновление более не требует перезапуска конфигуратора при работе в клиент-серверном варианте.

Запуски и завершения регламентных задач в одной информационной базе не влияют на работу других информационных баз.

Повышена надежность системы в следующих случаях:

  • Обновление конфигурации базы данных;
  • Работа фоновых заданий;
  • Динамическое обновление.
При использовании динамического обновления требовался перезапуск конфигуратора при работе в клиент-серверном варианте.

Запуски и завершения регламентных задач в одной информационной базе влияли на работу других информационных баз.

Работа системы была недостаточно надежна в некоторых сценариях.

Повышена стабильность и надежность работы кластера серверов.
В документации данное изменение описано здесь.
Предопределенные данные.
При выполнении операции тестирования и исправления информационной базы реализована проверка того, что в основной таблице соответствующего объекта (справочник, план видов характеристик, план видов расчетов, план счетов) существует не более одной записи для каждого предопределенного элемента в каждой области. При обнаружении дублей у них снимается признак предопределенности и устанавливается пометка удаления.Данная возможность не предоставлялась.Улучшен механизм тестирования и исправления информационной базы.
В документации данное изменение описано здесь.
Внешние источники данных.
Поля таблиц и измерений таблиц кубов внешних источников данных могут содержать значение NULL только в тех случаях, когда в настройках соответствующего объекта установлен флажок Разрешить Null. Поля таблиц кубов внешних источников данных всегда считаются полями с разрешенным значением NULL.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Все поля таблиц внешних источников данных могли принимать значение NULL.Повысилась эффективность упорядочивания в динамических списках по полям, для которых корректно указана возможность содержать значения NULL.
Система компоновки данных.
При использовании в наборе данных схемы компоновки данных запроса, в котором есть вложенный запрос, поля из списка выборки вложенных запросов становятся доступными для отбора, если эти поля не используются в агрегатных функциях родительского запроса.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

При использовании в наборе данных схемы компоновки данных запроса, в котором есть вложенный запрос, поля из списка выборки вложенных запросов недоступны для отбора (кроме параметров виртуальных таблиц).Улучшено построение результирующего запроса в тех случаях, когда в схеме компоновки данных используются вложенные запросы с отборами по полям вложенных запросов.
В документации данное изменение описано здесь.
Тестирование и исправление информационной базы.
Общие реквизиты / Разделение данных.
Тестирование и исправление информационной базы позволяет обнаружить и исправить ситуацию, когда в информационной базе существуют строки в табличных частях, при этом отсутствуют записи об объектах, для которых формировались эти табличные части. Поиск и восстановление выполняется с учетом всех независимых разделителей, в состав которых входит объект.Данная возможность не предоставлялась.Улучшен механизм тестирования и исправления информационной базы.
Динамический список.
Поиск в динамическом списке по полям ссылочных типов с произвольным представлением выполняется по полям, которые используются для формирования представления. Поля, входящие в представление, получаются с учетом обработчика ОбработкаПолученияПолейПредставления() соответствующего объекта.Поиск в динамическом списке по полям ссылочных типов с произвольным представлением выполнялся только по полям, используемым для формирования представления по умолчанию.Повышено качество поиска в динамическом списке по полям ссылочных типов с произвольным представлением.
В документации данное изменение описано здесь.
Управляемая форма.
Командный интерфейс.
В тонком клиенте, при выполнении команды из панели навигации, в интерфейсе Такси и в режиме «Формы в закладках», параметр Уникальность обработчика команды устанавливается в значение типа Булево (Истина - при выполнении через команду контекстного меню Открыть новое и Ложь - в остальных случаях).

В тонком клиенте, при выполнении команды из панели навигации формы, в интерфейсе Такси и в режиме «Формы в закладках», не устанавливается уникальность открываемой формы.

В режиме совместимости с версией 8.3.6 и для режима «Формы в отдельных окнах» поведение не

изменилось.

В тонком клиенте, при выполнении команды из панели навигации, в интерфейсе Такси и в режиме «Формы в закладках», в качестве значения параметра Уникальность обработчика команды передавался идентификатор основного окна. В веб-клиенте, при выполнении команды из панели навигации, в интерфейсе Такси и в режиме «Формы в закладках», параметр Уникальность обработчика команды устанавливался в значение типа Булево.

В тонком клиенте и веб-клиенте, при выполнении команды из панели навигации формы, в интерфейсе Такси и в режиме «Формы в закладках», в качестве значения параметра Уникальность обработчика команды передавался идентификатор окна.

Для режима «Формы в отдельных окнах» при выполнении команды из панели навигации в качестве значения параметра Уникальность обработчика команды передавался идентификатор основного окна.

Для режима «Формы в отдельных окнах» при выполнении команды из панели навигации формы в качестве значения параметра Уникальность обработчика команды передавался идентификатор окна.

Унифицировано поведение в разных клиентских приложениях и сценариях использования.
Кластер серверов.
Реализован новый механизм отслеживания разрыва соединений между процессами одного кластера, который определяет разрывы соединений с большей скоростью и более эффективно.

Для командной строки запуска процессов кластера серверов ragent, rmngr и rphost реализованы ключи pingPeriod и pingTimeout.

Для элемента pool файла default.vrd реализованы атрибуты serverPingPeriod и serverPingTimeout. Для диалога публикации на веб-сервере реализованы свойства Период проверки и Таймаут проверки.

Для события CONN расширен состав регистрируемых событий, связанных с механизмом отслеживания разрыва соединений между процессами одного кластера.

Использовался другой механизм отслеживания разрыва соединений в кластере, который был менее эффективен.Работа кластер стала более надежной, повысилась скорость и эффективность определения разорванных соединений в рамках кластера.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Полнотекстовый поиск.
Динамический список.
Кластер серверов.
При закрытии формы, содержащей динамический список, кластер серверов оповещается об этом для отмены фонового задания, выполняющего поиск (если оно было инициировано ранее).При закрытии формы, содержащей динамический список, кластер серверов не оповещался об этом. В результате фоновое задание, выполняющее поиск (если оно было запущено в момент закрытия формы) завершалось не при закрытии формы, а по фактическому завершению.Устранено некорректное поведение системы.

Снижена нагрузка на кластер серверов в некоторых сценариях использования.

В документации данное изменение описано здесь.
Средства разработки.
Для команд Переместить вверх и Переместить вниз в конфигураторе убраны клавиши доступа (буква П для обоих команд). Функционирование команд и горячие клавиши остались неизменными.Для команд Переместить вверх и Переместить вниз использовалась одна клавиша доступа (буква П).Устранено некорректное поведение системы.
Система компоновки данных.
Изменено представление элемента отбора, выводимого в отчет.

Если в отчет включен элемент отбора, входящий в состав пользовательских настроек, и для этого элемента отбора установлено представление пользовательской настройки, то при выводе отбора в результат отчета будет использоваться заданное представление.

Поведение не изменилось, если в отчет включен элемент отбора, не входящий в состав пользовательских настроек, или для этого элемента отбора не установлено представление пользовательской настройки.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Если в отчет включен элемент отбора, для которого задано представление, то в отчет выводилось только это представление, в противном случае отбор выводился как <Левое Значение> <Вид сравнения> <Правое значение>.Повышена читабельность представления списка отборов в отчете.
Табличный документ.
Изменено поведение табличного документа при вставке/удалении прямоугольной области ячеек (как программной, так и интерактивной). Если смещаемая область пересекает область объединения ячеек, и объединение не полностью находится в перемещаемой области, то объединение ячеек убирается. При этом все ячейки, которые ранее принадлежали объединенной области сохраняют все свойства оформления, которые были у объединенной области.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

При вставке/удалении прямоугольной области ячеек, объединения ячеек, которые лишь частично попадали в перемещаемую область, оставались неизменными.Поведение табличного документа стало более ожидаемым.
Работа с СУБД.
При использовании СУБД Oracle Database, попытка создания индекса для временной таблицы, который включает более трех измерений с типом Строка (каждое из которых 60 или более символов), может привести к тому, что создаваемый индекс будет обрезан (по последним полям), если длина ключа индекса не помещается в размер блока.При использовании СУБД Oracle Database, попытка создания индекса для временной таблицы, который включает более трех измерений типа Строка, приводило к аварийному завершению работы системы в результате ошибки СУБД.Устранено некорректное поведение системы. Повышена надежность работы системы.
Средства администрирования.
В документации отражено следующее требование: файлы с расширением .mst, .msi, .cab, находящиеся в zip-архиве дистрибутива при обновлении по протоколам HTTP или HTTPS, должны быть подписаны цифровой подписью, которая проходит проверку на компьютере, где будет выполняться установка.В документации не было отражено требование к цифровой подписи файлов.Исправлена ошибка в документации.
В документации данное изменение описано здесь.
Средства разработки.
Для установки соответствия отладчика и предмета отладки более не требуется посимвольное совпадение строк соединения с информационной базой в отладчике и предмете отладки.

Реализована возможность изменять значение переменной в процессе отладки.

Реализована возможность просмотра всех локальных переменных в отлаживаемом методе (в специальном окне).

Реализовано сохранение раскрытых узлов в табло и окне локальных переменных между «шагами» отладки.

Прерывание работы отлаживаемого приложения (Shift+F5) не приводит к возникновению модального диалога в отлаживаемом приложении, возникающего перед завершением работы этого приложения.

Для установки соединения между отладчиком и предметом отладки требовалось посимвольное совпадение строк соединения с информационной базой в отладчике и предмете отладки.

В отладчике не поддерживалось изменение значения переменной.

Было невозможно просматривать локальные переменные отлаживаемого метода в отдельном окне. +Не сохранялось состояние раскрытых узлов в табло между «шагами» отладки.

Прерывание работы отлаживаемого приложения (Shift+F5) в ряде случаев приводило к возникновению модального диалога в отлаживаемом приложении, возникающего перед завершением работы этого приложения.

Улучшены возможности отладки прикладных решений.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Система компоновки данных.
В колонках общих итогов таблицы системы компоновки данных выводятся заголовки полей ресурсов, расположенных в группах, в случае если у колонок таблицы установлены макеты группировок.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

В шапке таблицы системы компоновки данных, в колонке итогов, не отображались заголовки полей ресурсов, расположенных в группах, в том случае если у колонок таблицы установлены макеты группировок.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Общие объекты.
Средства разработки.
Значение свойства Код языка, для объекта конфигурации Язык, не может включать в себя следующие символы: #, *, |, \, :, «, <, >, ?, /.Значение свойства Код языка, для объекта конфигурации Язык, не могло включать в себя символ #.В силу того, что код языка участвует в формировании имени файла для выгрузки конфигурации в файлы, снижена вероятность прерывания выгрузки из-за некорректного формирования имени файла.
В документации данное изменение описано здесь.
Установка клиентского приложения.
Средства администрирования.
Обновлена статья на ИТС по приложению Autorun (см. здесь).Информация по приложению Autorun была неактуальной.Описание приложения Autorun стало более полным.
Командный интерфейс.
В тонком клиенте (в режиме отдельных окон), если в обработчике навигационной команды выполняется метод глобального контекста ПерейтиПоНавигационнойСсылке(), в который в качестве параметра передана ссылка на точку навигации, то по окончании выполнения команды текущая точка навигации устанавливается на исполняемую навигационную команду.

+

В тонком клиенте (в режиме отдельных окон), если в обработчике навигационной команды выполняется метод глобального контекста ПерейтиПоНавигационнойСсылке(), в который в качестве параметра передана ссылка на точку навигации, то по окончании выполнения команды текущая точка навигации устанавливалась на ту, которая передана в параметре.Устранено некорректное поведение системы.
Управляемая форма.
В тонком клиенте свойство управляемой формы Окно стало доступно только для чтения. В веб-клиенте поведение не изменилось.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

В тонком клиенте свойство управляемой формы Окно было доступно для чтения и записи. В веб-клиенте свойство управляемой формы Окно было доступно только для чтения.Унифицировано поведение системы при работе в различных клиентских приложениях.
Регистры сведений.
Для периодического регистра сведений изменена структура индекса таблицы среза первых/последних, при наличии индексируемых ресурсов или реквизитов. Если периодичность регистра сведений установлена в По позиции регистратора, то в индекс добавляются измерения регистра. Если периодичность регистра сведений отличается от По позиции регистратора, то индекс является неуникальным.

Реструктуризация таблиц срезов выполняется при установке свойства конфигурации Режим совместимости в значение Не используется.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Для периодического регистра сведений с периодичность По позиции регистратора, измерения регистра не входили в состав индекса таблицы среза первых/последних. Для периодического регистра сведений с периодичность отличной от По позиции регистратора, индекс таблиц срезов являлся уникальным. +Устранена ошибка нарушения уникальности индекса.
Предопределенные данные.
При проверке конфигурации, которая выполняется перед каждым обновлением конфигурации базы данных, выполняется проверка уникальности имен предопределенных данных. Имя предопределенного элемента должно быть уникально в пределах одного объекта конфигурации. Если в конфигурации есть дубли предопределенных элементов, то информация о таких элементах выводится в окно сообщений и обновление конфигурации блокируется.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

При проверке конфигурации, которая выполняется перед каждым обновлением конфигурации базы данных, выполнялась проверка уникальности имен предопределенных данных, однако наличие дублей предопределенных элементов не мешало обновлению конфигурации базы данных.Повышена надежность обновления конфигурации, содержащей предопределенные данные.
Технологический журнал.
Реализовано журналирование исключительных ситуаций, возникающих в процессе работы отладчика, в технологическом журнале. Журналирование выполняется с помощью события <EXCP>.Журналирование исключительных ситуаций, возникающих при работе отладчика, не выполнялось.Улучшена диагностика проблемных ситуаций, возникающих при работе отладчика.
Средства администрирования.
При выполнении тестирования и исправления информационной базы исключена проверка того, что значения реквизитов типа Строка переменной длины завершаются пробелами.В версии 8.3.7 при выполнении тестирования и исправления информационной базы выполнялась проверка того, что значения реквизитов типа Строка переменной длины завершаются пробелами.Устранено некорректное поведение системы.
Региональные установки.
Для Российской Федерации учитывается однократный сдвиг часовых зон на один час в связи с принятием законов №№ 453-ФЗ, 27-ФЗ, 57-ФЗ, 58-ФЗ, 59-ФЗ, 69-ФЗ, 87-ФЗ. Изменения касаются всех компонентов системы «1С:Предприятие», кроме веб-клиента. Веб-клиент пользуется информацией о временных зонах, которую предоставляет ОС и веб-браузер. +Изменения, внесенные законом №№ 453-ФЗ, 27-ФЗ, 57-ФЗ, 58-ФЗ, 59-ФЗ, 69-ФЗ, 87-ФЗ, не учитывались платформой. +Учтены изменения законодательства об исчислении времени.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа с Интернет.
Объект ЗащищенноеСоединениеNSS недоступен для использования, сертификаты NSS недоступны для использования во встроенном языке.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Система «1С:Предприятие» поддерживала работу с сертификатами NSS.Будущие версии платформы не будут работать с сертификатами NSS.
Общие объекты.
Использование метода ХранилищеЗначения.Получить() в тонком клиенте приводит к генерации исключения.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Использование метода ХранилищеЗначения.Получить() в тонком клиенте не приводило к генерации исключения. В этом случае возвращалось значение Неопределено. Использование данного метода в веб-клиенте приводило к генерации исключения.Унифицировано поведение системы при работе в различных клиентских приложениях.
В документации данное изменение описано здесь.
Интерфейс.
Управляемая форма.
Изменены правила формирования истории выбора в поле ввода управляемой формы, в частности, при формировании истории выбора учитывается частота использования значения. История состоит из 7 элементов, в которые входят и часто используемые и последние использованные значения. Правила формирования подробно описаны в документации.

Системное хранилище истории выбора значений в поле ввода управляемой формы содержит значение типа НастройкиИсторииВыбора.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Правила формирования истории выбора в поле ввода управляемой формы были другими. История состояла только из 5 последних значений.

Системное хранилище истории выбора значений в поле ввода управляемой формы содержало значение типа Массив.

История выбора в поле ввода управляемой формы стала более удобна для использования.
В документации данное изменение описано здесь, здесь и здесь.
Управляемая форма.
Реализован новый механизм расстановки элементов управляемой формы. В результате реализации улучшено размещение элементов на форме, реализованы новые возможности размещения элементов на форме, изменение некоторых свойств элементов формы на клиенте больше не требует обращения к серверу (изменение состояния группы - свернута/не свернута, отображение или скрытие дополнения элемента формы Состояние просмотра), изменены правила автоматического формирования разделителей на форме и т.д. В существенной части случаев исключено обращение к серверу при управлении видимостью элементов формы. Подробное описание работы механизма приведено в документации.

В редакторе управляемой формы реализована возможность быстрого просмотра разрабатываемой формы в нужном разрешении и ориентации экрана.

Для системного перечисления ГруппировкаПодчиненныхЭлементовФормы реализовано значение ГоризонтальнаяЕслиВозможно. У расширений поля управляемой формы для поля надписи, поля ввода, поля картинки, поля табличного документа, поля текстового документа, поля форматированного документа, поля календаря, поля индикатора, поля полосы регулирования, поля диаграммы, поля диаграммы Гантта, поля дендрограммы, поля географической схемы, поля HTML-документа, поля графической схемы, поля периода и поля планировщика, элемента управляемой формы типа таблица, декорация и кнопка реализованы свойства: АвтоМаксимальнаяШирина, МаксимальнаяШирина, АвтоМаксимальнаяВысота, МаксимальнаяВысота. Для элементов управляемой формы типа форма, группа и страница реализованы свойства ГоризонтальныйИнтервал, ВертикальныйИнтервал, ВыравниваниеЭлементовИЗаголовков, ГоризонтальноеПоложениеПодчиненных, ВертикальноеПоложениеПодчиненных. Для полей управляемой формы типа поле, таблица, декорация, группа, кнопка и дополнение реализованы свойства ГоризонтальноеПоложениеВГруппе, ВертикальноеПоложениеВГруппе. Для расширения управляемой формы для дополнения элемента формы Отображение строки поиска, Отображение управления поиском и Отображение состояния просмотра реализованы свойства АвтоМаксимальнаяШирина и МаксимальнаяШирина. Для элемента управляемой формы типа группа реализовано свойство СквозноеВыравнивание. Для системного перечисления ВертикальнаяПрокруткаФормы реализовано значение ИспользоватьБезРастягивания. Для расширения управляемой формы для группы реализовано свойство Объединенная. Для расширения управляемой формы для страницы реализовано свойство ВертикальнаяПрокруткаПриСжатии.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Свойства РастягиватьПоГоризонтали и РастягиватьПоВертикали реализованы для следующих объектов: расширения управляемой формы для полей графической схемы и HTML-документа, элемент управляемой формы типа кнопка. Для расширения управляемой формы для дополнения элемента формы Отображение управления поиском реализовано свойство РастягиватьПоГоризонтали.

Свойство ШиринаПодчиненныхЭлементов для формы, страницы и обычной группы является устаревшим и поддерживается только в режиме совместимости с версией 8.3.6. Использование данного свойства с отключенным режимом совместимости игнорируется.

Использовался другой механизм расстановки элементов управляемой формы.Переработан механизм расстановки элементов на управляемой форме. Расширены возможности формирования формы. Устранен ряд известных проблем, возникающих при эксплуатации управляемых форм.
В документации данное изменение описано здесь, здесь и здесь.
Web-сервисы и HTTP-сервисы.
В том случае, если в конфигурации реализованы HTTP-сервисы, невозможно установить режим совместимости ниже, чем Версия 8.3.5 и выполнить сохранение конфигурации.При сохранении конфигурации не анализировалась связь между режимом совместимости и наличием HTTP-сервисов в конфигурации.Устранено некорректное поведение системы.
В документации данное изменение описано здесь.
Общие объекты.
Свойство конфигурации Режим использования синхронных вызовов расширений и внешних компонент анализируется при работе следующих методов:
  • Прочитать() объекта ТекстовыйДокумент.
  • Записать() объектов ТекстовыйДокумент, ТабличныйДокумент, ФорматированныйДокумент, ГрафическаяСхема.
  • ЗаписатьФайлДляПечати() объекта ПакетОтображаемыхДокументов.
При работе указанных методов игнорировалось свойство конфигурации Режим использования синхронных вызовов расширений и внешних компонент.Устранено незапланированное поведение системы.
Кластер серверов.
При настройке требований назначения функциональности используются следующие имена фоновых заданий:
  • Регламентное задание: BackgroundJob.ScheduledJob.<Имя объекта метаданных>.
  • Ввод по строке: BackgroundJob.InputByString.<Полное имя объекта метаданных>.
  • Отчет: BackgroundJob.GenerateReport.<Полное имя объекта метаданных отчета>.
  • Внешний отчет: BackgroundJob.GenerateReport.<Полное имя объекта метаданных отчета>.
  • Поиск в списке: BackgroundJob.DynamicListSearch.<Полное имя формы>.<Имя таблицы формы связанной со списком>.
  • Фоновая реструктуризация: SystemBackgroundJob.DBConfigUpdate.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Для целей требований назначения функциональности использовались следующие имена фоновых заданий:
  • Регламентное задание: BackgroundJob.CommonModule.<Имя модуля>.<Имя метода>.
  • Ввод по строке: BackgroundJob.SystemBackgroundJob.
  • Отчет: BackgroundJob.Report.
  • Внешний отчет: BackgroundJob.Report.
  • Поиск в списке: BackgroundJob.SystemBackgroundJob.
  • Фоновая реструктуризация: SystemBackgroundJob.

+

Имена фоновых заданий приведены в соответствие с внутренними требованиями системы. Имена фоновых заданий стали более четко описывать используемый предмет.
В документации данное изменение описано здесь.
Работа с запросами.
Функция языка запросов ТипЗначения() возвращает значение Неопределено в том случае, если параметром функции выступает значение Неопределено.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Функция языка запросов ТипЗначения() возвращает значение NULL в том случае, если параметров функции выступает значение Неопределено.Устранено некорректное поведение системы.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Работа с криптографией.
Реализована возможность ограничивать доступ к механизму криптографии с помощью механизма профилей безопасности.

Для объекта ISecurityProfile реализовано свойство CryptographyAllowed (технология программного администрирования кластера серверов с помощью COM-объектов).

Для интерфейса ISecurityProfile реализованы методы getCryptographyAllowed() и setCryptographyAllowed() (интерфейс работы с сервером администрирования из языка Java).

Для утилиты командной строки (rac) кластера серверов реализован параметр crypto команды profile.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Не предоставлялась возможность ограничивать доступ к механизму криптографии с помощью профилей безопасности.Расширены возможности профилей безопасности.
В документации данное изменение описано здесь, здесь и здесь.
Права доступа.
Проверка права доступа для реквизита графы журнала документов методом ПравоДоступа() с указанием параметра Пользователь/Роль осуществляется с учетом доступности всех объектов, входящих в состав графы журнала.

Результат вызова функции ПравоДоступа() кешируется системой аналогично кешу повторно используемых значений.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Проверка права доступа для реквизита графы журнала документов методом ПравоДоступа() с указанием параметра Пользователь/Роль не учитывала доступность всех объектов, входящих в состав графы журнала.

Результат вызова функции ПравоДоступа() не кешировался.

Устранено некорректное поведение системы.

Ускорена проверка прав доступа для прикладных решений с большим количество ролей, компьютерах с небольшой производительностью и файловой информационной базой. В результате оптимизации ускоряется открытие управляемых форм в указанных случаях.

В документации данное изменение описано здесь.
Локализация.
Реализована возможность указания первого дня недели. Данная установка выполняется с помощью диалога конфигуратора Администрирование - Региональные установки информационной базы. При создании новой информационной базы с помощью версии 8.3.7 (и старше) и отключенным режимом совместимости, первый день недели будет установлен в значение Авто и фактический первый день недели будет определяться на основании свойства Язык (Страна) региональных установок информационной базы.

Установка первого дня недели учитывается:

  • При работе методов встроенного языка НачалоНедели(), КонецНедели(), НеделяГода().
  • Работе функций языка запросов НачалоПериода(), КонецПериода(), Неделя().
  • Функций системы компоновки данных НачалоПериода(), КонецПериода(), Неделя(), а также вложенных полей для полей типа Дата: НачалоНедели, КонецНедели, НеделяГода.
  • Расписания регламентных заданий.
  • Виртуальные таблицы остатков и остатков и оборотов регистров накоплений.
  • Виртуальные таблицы остатков и остатков и оборотов регистров бухгалтерии.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Первым днем недели всегда являлся понедельник.Систему «1С:Предприятие» стало проще использовать в странах, где первый день недели отличается от понедельника.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Табличный документ.
Для табличного документа в управляемой форме реализована возможность редактирования на нескольких языках, если табличный документ является макетом. Состав языков получается непосредственно из макета.

В управляемой форме табличный документ редактируется и отображается на языке, указанном в свойстве табличного документа КодЯзыка. Строки на остальных языках остаются неизменными.

Реализовано свойство ТабличныйДокумент.Макет.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Метод ЗаполнитьЗначенияСвойств() не копирует свойство Макет (независимо от режима совместимости).

Табличный документ в управляемой форме всегда редактируется на текущем языке.

При отображении табличного документа:

  • В тонком клиенте свойство КодЯзыка не используется.
  • В веб-клиенте свойство КодЯзыка используется.

При программном редактировании текста табличного документа устанавливаются строки на текущем языке и теряются строки на других языках.

Стало возможно редактировать многоязычные табличные документы в режиме «1С:Предприятие».
В документации данное изменение описано здесь.
Прикладные объекты.
При формировании поля Представление виртуальной таблицы ЗадачиПоИсполнителю учитывается возможность переопределения представления соответствующего объекта Задача.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

При формировании поля Представление виртуальной таблицы ЗадачиПоИсполнителю не учитывалась возможность переопределения представления соответствующего объекта Задача и всегда использовалось стандартное представление.Устранено некорректное поведение системы.

+

Работа с запросами.
Доработана объектная модель запроса.

Реализован метод Найти() для объектов ВыраженияИндексаСхемыЗапроса, ВыраженияСхемыЗапроса, ВыраженияПорядкаСхемыЗапроса, ДоступныеПоляСхемыЗапроса, ПараметрыДоступнойТаблицыСхемыЗапроса, ПараметрыТаблицыСхемыЗапроса, ПоляСхемыЗапроса, КолонкиСхемыЗапроса, ТаблицыДляИзмененияСхемыЗапроса, ДоступныеТаблицыСхемыЗапроса. Реализованы методы НайтиПоИмени() и НайтиПоПсевдониму() для объектов СоединенияИсточникаЗапросаСхемыЗапроса, ИсточникиСхемыЗапроса. Реализован метод НайтиПоВыражению() для объектов КонтрольныеТочкиИтоговСхемыЗапроса и ВыраженияИтоговСхемыЗапроса. Реализован метод КонтрольныеТочкиИтоговСхемыЗапроса.НайтиПоИмениКолонки(). Реализован метод ВыраженияИтоговСхемыЗапроса.НайтиПоПолю(). Реализован метод ИсточникиСхемыЗапроса.ПолучитьКорневыеИсточники().

Реализован новый вариант метода Добавить() для объектов ВыражениеПорядкаСхемыЗапроса, СоединенияИсточникаЗапросаСхемыЗапроса, ТаблицыДляИзмененияСхемыЗапроса, ВыраженияИтоговСхемыЗапроса.

Для метода ПоляСхемыЗапроса.Добавить() реализован необязательный параметр Колонка.

Параметр Источник метода СоединенияИсточникаЗапросаСхемыЗапроса.Добавить() может принимать значение типа Строка и ИсточникСхемыЗапроса.

Параметр метода ВыраженияИтоговСхемыЗапроса.Добавить() может принимать значения типа Строка, КолонкаСхемыЗапроса и ВыражениеСхемыЗапроса.

Изменено поведение метода КонтрольныеТочкиИтоговСхемыЗапроса.Добавить() в случае, если параметр принимает значение типа Строка.

Значение свойства ВложеннаяТаблицаСхемыЗапроса.Поля имеет тип ПоляСхемыЗапроса. Если в метод ЗапросВыбораСхемыЗапроса.УстановитьТекстЗапроса() передан текст, содержащий пакетный запрос или запрос на уничтожение таблицы, выдается исключение. Вариант «для вложенной таблицы» метода ВыраженияСхемыЗапроса.Добавить() признан устаревшим. В режиме совместимости с версией 8.3.6 поведение не изменилось.

Данные возможности не предоставлялась.

Значение свойства ВложеннаяТаблицаСхемыЗапроса.Поля имело тип ВыраженияСхемыЗапроса.

Если в метод ЗапросВыбораСхемыЗапроса.УстановитьТекстЗапроса() передан текст, содержащий пакетный запрос или запрос на уничтожение таблицы, то использовался первый запрос пакета или создавался пустой запрос (для запроса уничтождения таблицы).

Доступен вариант «для вложенной таблицы» метода ВыраженияСхемыЗапроса.Добавить().

Работа с запросом с помощью объектной модели стала более удобной и наглядной.
В документации данное изменение описано здесь.
Система компоновки данных.
В системе компоновки данных тип связи наборов данных заменяется на внутреннюю в том случае, если применяется отбор, который содержит только поля набора данных, с которым выполняется связь. Условия, для которых не были сделаны внутренние связи, добавляются в свойство группировок ОтборЗаписей, в которых задействован хотя-бы один из наборов данных, поля которых используются в условиях.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

В системе компоновки данных тип связи наборов данных заменялся на внутреннюю при использовании в отборе поля набора данных, с которым выполняется связь.Устранено неожиданное поведение системы при использовании в отборах полей из нескольких наборов данных.
В документации данное изменение описано здесь.
Навигационные ссылки.
Значение, передаваемое в качестве параметра в метод ПерейтиПоНавигационнойСсылке(), перед передачей на выполнение операционной системе не декодируется (передается оригинальная ссылка).

В режиме совместимости с версией 8.3.6 поведение не изменилось.

Значение, передаваемое в качестве параметра в метод ПерейтиПоНавигационнойСсылке(), перед передачей на выполнение операционной системе:
  • в режиме совместимости с версией 8.3.4 и ниже - не декодировалось (передавалась оригинальная ссылка);
  • в режимах совместимости с версией 8.3.5 и 8.3.6 - декодировалось перед передачей.
Устранено некорректное поведение системы.
Расширение конфигурации.
Запись расширения в информационную базу возможен в том случае, если сеанс, из которого выполняется запись, работает в небезопасном режиме или если профиль безопасности, примененный для сеанса, допускает доступ к указанному расширению.

При подключении расширения не выполняется проверка соответствия расширения профилю безопасности сеанса.

Запись расширения в информационную базу была возможна только в том случае, если сеанс, из которого выполняется запись, работает в небезопасном режиме.

При подключении расширения проверялось, что профиль безопасности допускает доступ к указанному расширению.

Использование профилей безопасности при работе с расширением приведено в соответствие с аналогичным поведением для внешних отчетов и обработок.
В документации данное изменение описано здесь.
Прикладные объекты.
Если номер объекта (документа, элемента справочника, плана видов характеристик, бизнес-процесса или задачи) выделялся в транзакции, то он будет повторно использоваться даже в том случае, если установлен режим автонумерации Не освобождать автоматически, в том числе в ситуации, когда объект в транзакции не записывался.

Режим автонумерации Не освобождать автоматически действует только на номера, которые выданы вне транзакции. Т.е. если номер выдан вне транзакции и код не был использован (объект не был записан), то в режиме Не освобождать автоматически номер не будет переиспользован, а в режим Освобождать автоматически номер будет переиспользован.

Если номер объекта (документа, элемента справочника, плана видов характеристик, бизнес-процесса или задачи) выделялся в транзакции и объект не был записан, то выделенный номер не использовался повторно в том случае, если установлен режим автонумерации Не освобождать автоматически.

+

Уменьшено количество неиспользуемых номеров объектов в тех случаях, когда объекты, для которых номера назначаются в транзакции, фактически не записываются.
Клиентское приложение.
Отображение информации.
При использовании в прикладных решениях шрифтов, отличных от Авто, рекомендуется ограничиваться следующими шрифтами:
  • Стилевые шрифты системы «1С:Предприятия»:
    • Мелкий шрифт текста,
    • Обычный шрифт текста,
    • Крупный шрифт текста,
    • Очень крупный шрифт текста.
  • Векторные шрифты из состава «MS Core Fonts»:
    • Andale Mono,
    • Arial,
    • Arial Black,
    • Comic Sans MS,
    • Courier New,
    • Georgia,
    • Impact,
    • Times New Roman,
    • Trebuchet MS,
    • Verdana,
    • Webdings.

При использовании других шрифтов, корректное отображение элементов формы во всех режимах работы (и клиентских приложениях) не гарантируется.

Рекомендация по используемым шрифтам отсутствовала.Сформированы рекомендации по шрифтовому оформлению прикладных решений для устойчивой работы в различных окружениях.
Управляемая форма.
Исправлен алгоритм вычисления размера шрифта на основании заданных свойств шрифта элемента формы. В некоторых случаях может произойти изменение масштаба шрифта элемента формы у тех элементов, где свойство Масштаб свойства Шрифт было непреднамеренно установлено в значение, отличное от значения по умолчанию.

В режиме совместимости с версией 8.3.6 поведение не изменилось.

В некоторых случаях при отображении формы игнорировалось свойство Масштаб свойства Шрифт элемента формы. При этом текст в элементе отображался стандартного размера.Устранено некорректное поведение системы.

В некоторых случаях изменится размер шрифта элементов управления.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Свойство табличного документа, описывающего язык отображения и редактирования. Старое наименование поддерживается для совместимости.
  • КодЯзыкаМакета.
  • КодЯзыка.
Представления автоматически создаваемых групп команд поля графической схемы. Группы команд отображаются в диалоге настройки формы в режиме «1С:Предприятия».
  • Группа Выравнивание и размер (содержит команду Выровнять по левому краю);
  • Группа Выравнивание и размер (содержит команду Выровнять по верхнему краю);
  • Группа Группировка (содержит команду Распределить по горизонтали);
  • Группа Группировка (содержит команду На передний план);
  • Группа Группировка (содержит команду На задний план).
  • Выравнивание по горизонтали;
  • Выравнивание по вертикали;
  • Распределить;
  • Переместить вперед;
  • Переместить назад.

+

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Средства разработки.
Реализована возможность отладки конфигураций на мобильной платформе. Отладка возможна только при использовании отладки по протоколу HTTP (устанавливается в конфигураторе).Данная возможность не предоставлялась.Упрощена разработка прикладных решений для мобильной платформы.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства печати.
Реализовано разрешение мобильного приложения Печать, управляющее возможностью печати из мобильного приложения.

Сборщик мобильных приложений поддерживает сборку мобильных приложений, требующих данное разрешение.

Данная возможность не предоставлялась.Стало возможно уменьшить список требуемых мобильному приложению разрешений, если приложение не использует возможности печати.
Табличный документ.
Яркость зафиксированных областей табличного документа уменьшается на 2.5%.Яркость зафиксированных областей табличного документа уменьшалась на 10%.Улучшено восприятие табличного документа с зафиксированными областями.
Встроенный язык.
На мобильной платформе реализованы функции работы со строками, имеющиеся на платформе для персонального компьютера: СтрШаблон(), СтрСравнить(), СтрНачинаетсяС(), СтрЗаканчиваетсяНа(), СтрНайти(), СтрРазделить(), СтрСоединить().

Реализовано системное перечисление НаправлениеПоиска.

Данная возможность не предоставлялась.Унифицирована работа со строками между платформой для персонального компьютера и мобильной платформой.
Управляемая форма.
При отображении кнопки управляемой формы в командной панели управляемой формы, расположенной в заголовке формы, учитывается свойство Отображение этой кнопки. Свойства команды, связанной с этой кнопкой, игнорируются при определении режима отображения кнопки.При отображении кнопки управляемой формы в командной панели управляемой формы, расположенной в заголовке формы, не учитывалось свойство Отображение этой кнопки. Свойства команды, связанной с этой кнопкой, игнорировались при определении режима отображения кнопки.Стало возможно управлять отображением кнопки, расположенной в командной панели управляемой формы, расположенной в заголовке формы, с помощью свойств кнопки.
В документации данное изменение описано здесь.
Специальные возможности.
Для метода СредстваТелефонии.ПоддерживаетсяНаборНомера() реализован параметр ВызватьСразу. Параметр позволяет более точно определять возможность осуществления телефонных звонков.Для метода СредстваТелефонии.ПоддерживаетсяНаборНомера() было невозможно указать, какую возможность следует проверять.Унифицирована возможность проверки работы со специальными возможностями на мобильной платформе.
Системные требования.
Реализована поддержка операционной системы Windows Phone 8.1 (архитектуры ARM и x86) и старше, а также сенсорных устройств под управление операционной системы Windows 8.1 (архитектуры x86 и x86-64) и старше.

Возможности мобильной платформы для ОС Windows Phone аналогичны таковым для других мобильных ОС. Однако на ОС Windows Phone не поддерживается:

  • Возможность преобразовывать координаты в адрес и обратно, а также метод глобального контекста ПоказатьНаКарте();
  • Сканирование штрихкодов;
  • Журнал звонков;
  • Печать;
  • Прием SMS-сообщений;
  • Работа с уведомлениями;
  • Работа с контактами;
  • Работа с календарями.

Особенности мобильной платформы приведены в документации.

Расширен состав файла mobile.zip, в котором распространяется мобильная платформа.

Данная возможность включена в статусе бета-версии.

Данная возможность не предоставлялась.Расширена поддержка операционных систем для мобильных и сенсорных устройств.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Сборщик мобильных приложений.
Реализована возможность сборки мобильных приложений для ОС Windows Phone. Сборка может выполняться только на ОС Windows 8.1 и выше.

Расширен набор параметров для управления сборкой:

  • реализована возможность управлять сборкой для ОС Windows;
  • реализована поддержка графических ресурсов, требуемых для ОС Windows.

Не поддерживается публикация собранного мобильного приложения в магазин Windows Store.

При загрузке в сборщик мобильной платформы (из файла mobile.zip) реализована возможность загрузки файлов только тех мобильных ОС, которые присутствуют в загружаемом архиве.

Реализована возможность указывать индивидуальный идентификатор мобильного приложения для каждой из поддерживаемых мобильных операционных систем.

Реализована возможность выгрузки из базы сборщика мобильных приложений сертификатов разработчика.

Сборщик мобильных приложений не поддерживал возможность сборки для ОС Windows.

При попытке загрузить мобильную платформу (из файла mobile.zip) в сборщик мобильных приложений, загрузка выполнялась только в том случае, если в файле присутствовали версии для обоих операционных систем (iOS и Android).

Идентификатор мобильного приложения был общим для ОС iOS и Android.

Не поддерживалась выгрузка сертификатов разработчика из базы сборщика мобильных приложений.

Сборщик мобильных приложений стал поддерживать работу с приложениями для ОС Windows.

Использование сборщика стало более комфортным.

В документации данное изменение описано здесь.
Командный интерфейс.
Управляемая форма.
На мобильной платформе реализована команда Показать в списке, присутствующая в платформе для персонального компьютера.

Реализован метод УправляемаяФорма.ВыполнитьПереход(), реализовано событие управляемой формы ОбработкаПерехода.

Данная возможность не предоставлялась.Унифицирован интерфейс между мобильной платформой и платформой для персонального компьютера.
Web-сервисы и HTTP-сервисы.
На мобильной платформе реализована возможность использования Web-сервиса, расположенного по адресу, отличающемуся от указанного в wsdl-файле, который импортирован в прикладное решение (элемент конфигурации WS-ссылка).Данная возможность не предоставлялась.Работа с Web-сервисами унифицирована между мобильной платформой и платформой для персонального компьютера.
Управляемая форма.
На мобильной платформе реализована возможность использовать список выбора в полях ввода управляемой формы, отображающих данные типа дата и число.На мобильной платформе выпадающий список был недоступен.На мобильной платформе стало возможно использование выпадающих списков в полях ввода, отображающих данные типа число и дата.
Управляемая форма.
Реализована возможность перехода между полями ввода с помощью кнопки Enter виртуальной клавиатуры, возникающей на экране при необходимости ввести текст в поле ввода, без необходимости закрывать клавиатуру. Также реализована возможность перехода между полями ввода с помощью клавиш Tab/Shift+Tab, расположенной на физической клавиатуре, подключенной по Bluetooth.Возможность перехода между полями ввода управляемой формы без закрытия виртуальной клавиатуры была недоступна. Было необходимо закрыть клавиатуру в одном поле и заново открыть ее в другом поле ввода.Повышен комфорт использования мобильного приложения в случае использования нескольких полей ввода в форме.

Оглавление

Обновление используемых библиотек

Оглавление

Переход с предыдущей версии на версию 8.3.7

Оглавление

Версия 8.3.6

Версия 8.3.6 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v83doc) документации к текущей версии.

Для получения ссылки на элемент файла V8Update, следует дважды щелкнуть левой клавишей мыши по нужной строке. Необходимая ссылка будет доступна для копирования во всплывающем окне. Данная возможность недоступна при отключенном JavaScript.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.5. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3 и 8.3.4. +Возможность запуска конфигураций, разработанных в версии 8.3.5 и более младших, в версии 8.3.6, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.6 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.6, при необходимости, использовать для работы с информационной базой и версию 8.3.5. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Средства разработки.
В Конфигураторе реализована возможность сохранения закладок в текстах модулей между различными сеансами работы и редактирования модулей.

Для доступа к полному списку закладок реализована команда главного меню Правка - Список закладок.

Данная возможность не предоставлялась.Повышено удобство работы разработчика в конфигураторе.
В документации данное изменение описано здесь.
Средства разработки.
При переименовании объекта конфигурации реализована возможность выполнять операцию переименования также для всех вхождений имени используемого объекта в конфигурации.

При удалении объекта конфигурации реализована возможность проверки использования имени удаляемого объекта в конфигурации.

При изменении или удалении реквизита, параметра или элемента управляемой формы реализована проверка использования соответствующего имени в модуле формы. В случае переименования реализована возможность автоматического переименования найденных вхождений старого имени в модуле формы.

Для операции Поиск ссылок на объект реализована возможность искать в текстах модулей.

В диалоге параметров конфигуратора реализована возможность настраивать поведение системы при изменениях в метаданных и формах.

Данные возможности не предоставлялись.Снижена возможность совершения ошибок при переименовании или удалении какого-либо объекта конфигурации. Повышено удобство разработки.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Управляемая форма.
Реализован инструмент для визуализации данных планирования (планировщик). Для поля управляемой формы реализован вид поля формы - поле планировщика. Реализован объект Планировщик.

Для системного перечисления ПоложениеШкалыВремени реализованы значения Лево и Право, которые для диаграммы Ганта трактуются как значение Верх.

Данная возможность не предоставлялась.В прикладном решении упрощена работа с задачами, связанными с календарным планированием (встречи, календари и т.д.).
В документации данное изменение описано здесь и здесь.
Хранилище конфигурации.
Для пакетного режима запуска конфигуратора реализована возможность подключения ранее не подключенной информационной базы к хранилищу конфигурации (ключ командной строки запуска /ConfigurationRepositoryBindCfg).Данная возможность не предоставлялась.

Подключение неподключенной информационной базы к хранилищу конфигурации могло выполнять только в интерактивном режиме.

Расширены возможности автоматизированной работы с хранилищем конфигурации.
В документации данное изменение описано здесь.
Командный интерфейс.
Управляемая форма.
Реализована команда Показать в списке для расширений управляемой формы для объекта, справочника, документа, плана видов характеристик, бизнес-процесса, задачи, записи регистра сведений.

Для управляемой формы реализованы метод ВыполнитьПереход() и обработчик события ОбработкаПерехода.

Данная возможность не предоставлялась.Упрощено использование системы при необходимости открыть список объектов с автоматическим позиционированием на текущем объекте.
В документации данное изменение описано здесь.
Системные перечисления.
Клиентское приложение.
Для системного перечисления ОтображениеПанелиРазделов реализованы значения КартинкаСверхуИТекст и КартинкаСлеваИТекст.

В редакторе панели разделов клиентского приложения доступны следующие возможности для настройки отображения разделов:

  • В режиме совместимости интерфейса Версия 8.2:
    • Картинка;
    • Текст;
    • КартинкаИТекст.
  • В режиме совместимости интерфейса Такси:
    • Картинка;
    • Текст;
    • КартинкаИТекст;
    • КартинкаСверхуИТекст.
Для системного перечисления ОтображениеПанелиРазделов были доступны только значения Картинка, Текст, КартинкаИТекст. Расширены возможности отображения панели разделов в интерфейсе Такси.
Управляемая форма.
Реализована возможность указывать поле графической схемы в качестве источника команд для командной панели и кнопок управляемой формы.

В веб-клиенте для использования доступны только команды печати и предварительного просмотра.

Переименованы представления некоторых команд работы с графической схемой:

  • Выровнять по левому краю;
  • Выровнять по правому краю;
  • Выровнять по верхнему краю;
  • Выровнять по нижнему краю;
  • Переместить вперед;
  • Выровнять по центру;
  • Выровнять по середине.
Поле графической схемы было невозможно использовать в качестве источника команд для командной панели и кнопок управляемой формы.

Некоторые команды работы с графической схемой имели другое представление:

  • Выровнять влево;
  • Выровнять вправо;
  • Выровнять вверх;
  • Выровнять вниз;
  • Переместить вверх;
  • Выровнять по центру горизонтально;
  • Выровнять по центру вертикально.

+

+

Повышено удобство использования графической схемы.
Средства администрирования.
Реализована утилита контроля целостности, предназначенная для контроля состояния объектов файловой системы и базы данных, используемых при работе «1С:Предприятия», и обнаружения факта изменения этих объектов.

Утилита доступна в 32- и 64-разрядном виде для ОС Windows и Linux.

Данная возможность не предоставлялась.

Контроль неизменности файлов можно было выполнять с помощью сторонних утилит. Контроль неизменности объектов базы данных выполнить было невозможно.

Появилась возможность контроля целостности системы для защиты от несанкционированных модификаций.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с Интернет.
Для метода Выбрать() объекта ИнтернетПочта реализован параметр ОтмечатьКакПрочтенные. Имеет смысл только при работе с электронной почтой по протоколу IMAP.

Попытка использовать данный параметр, установленный в значение Ложь, при работе по протоколу POP3, приведет к возникновению исключения.

В режиме совместимости с версией 8.3.5 поведение не изменилось (если параметр установлен в значение Ложь).

Метод Выбрать() объекта ИнтернетПочта (при работе по протоколу IMAP) вел себя по-разному, в зависимости значения параметра МассивЗаголовковСообщенийИлиИдентификаторов:
  • Если параметр не был задан, то при выборке сообщений с почтового сервера сообщениям не проставлялся признак просмотренности;
  • Если параметр был задан, то признак проставлялся.

+

Устранено противоречивое поведение системы при работе с электронной почтой по протоколу IMAP.
Технологический журнал.
В технологическом журнале, в событиях SCALL и CALL, реализованы новые поля IName и MName , которые содержат дополнительную информацию о внутренних вызовах системы. Информация может использоваться специалистами фирмы «1С» при разборе обращений, направляемых в службу поддержки.Данная возможность не предоставлялась.Улучшены возможности технологического журнала для расследования сложных проблем.
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность получения данных, отображаемых динамическим списком, с учетом видимости колонок и использования поиска.

Для расширения таблицы управляемой формы для динамического списка реализованы следующие методы:

  • ПолучитьИсполняемуюСхемуКомпоновкиДанных();
  • ПолучитьИсполняемыеНастройкиКомпоновкиДанных().

+

Данная возможность не предоставлялась.Предоставлена возможность получить для последующей обработки данные динамического списка, которые видимы пользователю.
В документации данное изменение описано здесь.
Система компоновки данных.
Для полей системы компоновки данных, имеющих в составе типов тип Дата, реализованы следующие дочерние поля: НачалоДня, НачалоНедели, НачалоДекады, НачалоМесяца, НачалоКвартала, НачалоПолугодия, НачалоГода, КонецДня, КонецНедели, КонецДекады, КонецМесяца, КонецКвартала, КонецПолугодия, КонецГода, День, ДеньНедели, НазваниеДняНедели, ДеньГода, НеделяГода, Месяц, НазваниеМесяца, Квартал, Год, НачалоМинуты, НачалоЧаса, КонецМинуты, КонецЧаса, Минута, Час.Данная возможность не предоставлялась.

Получить необходимые данные можно было с помощью пользовательских полей-выражений.

Для пользователей упрощена работа с полями, включающими в свой состав дату и время.
В документации данное изменение описано здесь.
Встроенный язык.
Реализованы функции работы со строками:
  • СтрШаблон() - выполняет замену маркеров подстановки (вида %1) в шаблонной строке на реальные значения;
  • СтрСравнить() - выполняет лексикографическое сравнение строк без учета регистра;
  • СтрНачинаетсяС() - проверяет, что строка начинается на подстроку;
  • СтрЗаканчиваетсяНа() - проверяет, что строка оканчивается подстрокой;
  • СтрНайти() - выполняет поиск подстроки в различных направлениях и не только с начала строки;
  • СтрРазделить() - разделяет строку на части по указанному разделителю;
  • СтрСоединить() - соединяет строки из массива подстрок.

Реализовано системное перечисление НаправлениеПоиска.

Функция Найти() является устаревшей и поддерживается для совместимости.

В режиме совместимости с версией 8.3.5 поведение не изменилось. +

Данная возможность не предоставлялась.

Возможности новых функций можно было реализовать с помощью встроенного языка.

Упростилась реализация некоторых типовых алгоритмов работы со строками.
Веб-клиент.
Реализован механизм, позволяющий накапливать статистику использования веб-клиента. Механизм предназначен для использования специалистами фирмы «1С». Механизм включается параметром командной строки веб-клиента SYSTEMWEBCLIENTSTAT.Данная возможность не предоставлялась.Расширен состав инструментов, предназначенных для повышения качества работы платформы.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность импорта содержимого файлов в форматах XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument) в табличный документ. Данная возможность доступна как в интерактивном режиме, так и из встроенного языка.

Реализовано системное перечисление СпособЧтенияЗначенийТабличногоДокумента.

Для метода Прочитать() объекта ТабличныйДокумент реализован параметр СпособЧтенияЗначений.

Реализована поддержка вставки из буфера обмена областей, скопированных из Microsoft Excel и OpenOffice Calc.

Данная возможность не предоставлялась.Упрощен механизм загрузки данных из файлов электронных таблиц в форматах XLS (Microsoft Excel 97), Microsoft Office OpenXML (Microsoft Excel 2007- 2010) и ODS (OpenDocument).
Система компоновки данных.
Динамический список.
Для объекта КомпоновщикНастроекКомпоновкиДанных реализован метод ПолучитьИсточникДоступныхНастроек(). Данная возможность не предоставлялась.Упрощена процедура использования источника доступных настроек одного компоновщика настроек компоновки данных в другом. Например, для открытия отдельной формы редактирования настроек компоновки данных с тем же источником.
В документации данное изменение описано здесь.
Работа с Интернет.
Web-сервисы и HTTP-сервисы.
Реализована возможность работать с данными в формате JSON. Работа возможна в потоковой и объектной техниках.

Реализована сериализация и десериализация в JSON следующих объектов: примитивные типы, Массив, ФиксированныйМассив, Структура, ФиксированнаяСтруктура, Соответствие, ФиксированноеСоответствие.

Реализованы объекты ЧтениеJSON, ЗаписьJSON. Реализованы методы глобального контекста ЗаписатьJSON(), ПрочитатьJSON(), ЗаписатьДатуJSON(), ПрочитатьДатуJSON().

Данная возможность не предоставлялась.

Работу с данными в формате JSON можно было реализовывать на встроенном языке.

Упрощено взаимодействие с приложениями (в том числе и веб-приложениями), использующими для взаимодействия формат JSON.

Стало возможно хранить различные данные в формате JSON, например, вместо XML.

В документации данное изменение описано здесь.
Web-сервисы и HTTP-сервисы.
Для стандартного интерфейса OData реализована возможность получения ответа в формате JSON.Данная возможность не предоставлялась.

Для стандартного интерфейса OData ответ можно было получить только в формате atom.

Более полно поддерживается формат OData.

При использовании формата JSON уменьшается объем данных, передаваемых между клиентом и сервером.

В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с запросами.
Реализована возможность использования логических выражений в описании поля выборки и в выражениях фильтрации результатов запроса (предложение ГДЕ).Данная возможность не предоставлялась.

При необходимости использования логического выражения в описании поля выборки было необходимо использовать операцию выбора.

Логические выражения в предложении ГДЕ могли соединяться только логическими операторами И, ИЛИ и НЕ и не могли быть составными.

Упрощено написание и понимание сложных запросов.
В документации данное изменение описано здесь и здесь.
Кластер серверов.
Средства администрирования.
Реализован механизм мониторинга состояния кластера. Мониторинг анализирует некоторые параметры кластера и позволяет принудительно завершать проблемные процессы. Мониторинг выполняется агентом центрального сервера кластера. Результаты мониторинга записываются в технологический журнал.

Для кластера реализованы свойства Допустимое отклонение количества ошибок сервера и Принудительно завершать проблемные процессы.

Реализованы методы SetClusterRecyclingErrorsCountTheshold() и SetClusterRecyclingKillProblemProcesses() для объекта IServerAgentConnection.

Реализованы параметры командной строки --errors-count-threshold и --kill-problem-processes для утилиты rac.

Реализовано событие технологического журнала ATTN.

Механизм автоматического мониторинга состояния кластера не предоставлялся.Повышена надежность кластера путем своевременного обнаружения и завершения проблемных процессов.
В документации данное изменение описано здесь, здесь и здесь.
Автоматизированное тестирование.
В механизме автоматизированного тестирования реализована поддержка интерфейса Такси. Расширены возможности механизма автоматического тестирования:
  • Реализовано свойство НачальнаяСтраница объекта ТестируемоеОкноКлиентскогоПриложения.
  • Реализована возможность выполнять навигацию по окнам. Реализованы методы ПерейтиКНачальнойСтранице(), ПерейтиКСледующемуОкну(), ПерейтиКПредыдущемуОкну(), ЗакрытьПанельСообщенийПользователю() объекта ТестируемоеОкноКлиентскогоПриложения.
  • Расширены возможности работы с полем управляемой формы:
    • Реализована возможность создания нового элемента. Реализован метод Создать() для объекта ТестируемоеПолеФормы.
    • Реализована возможность отказа от редактирования данных в поле. Реализован метод ОтменитьРедактирование() для объекта ТестируемоеПолеФормы.
    • Реализована возможность открыть выпадающий список, ожидать окончание формирования выпадающего списка и выполнить выбор из него. Реализованы методы ОткрытьВыпадающийСписок(), ЗакрытьВыпадающийСписок(), ВыполнитьВыборИзВыпадающегоСписка(), ОжидатьФормированияВыпадающегоСписка(), ВыпадающийСписокОткрыт() для объекта ТестируемоеПолеФормы.
Интерфейс Такси не поддерживался механизмом автоматизированного тестирования.Механизм автоматизированного тестирования стало возможно использовать с интерфейсом Такси.
В документации данное изменение описано здесь.
Система компоновки данных.
Динамический список.
Реализована возможность связывать элементы пользовательских настроек отчета или динамического списка с таблицами управляемой формы.

Для объекта ПользовательскиеНастройкиКомпоновкиДанных реализованы колонки Отбор, Порядок, Выбор, УсловноеОформление, Структура.

Переработана форма пользовательских настроек отчета и динамического списка: вместо полей ввода для вызова редакторов (отбора, порядка и т.д.) реализованы закладки с таблицами (аналогично редактору схемы компоновки данных в конфигураторе).

Команда формы отчета Настройки отображается в основной командной панели формы.

Элементы пользовательских настроек отчета и динамического списка можно было связывать только с полями ввода управляемой формы.

Форма пользовательских настроек отчета и динамического списка выглядела по-другому.

Команда формы отчета Настройки находилась в меню Еще.

Улучшена стандартная форма редактирования пользовательских настроек отчета и динамического списка.
Управляемая форма.
Для объекта конфигурации Перечисление реализовано свойство ИсторияВыбораПриВводе. С помощью данного свойства реализовано управление отображением и сохранением истории ввода для поля ввода, связанного с реквизитом типа перечисление.

Для перечислений, выбор которых выполняется из формы, история ввода начнет отображаться и сохраняться автоматически.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Данная возможность не предоставлялась.

История выбора для полей ввода, связанных с реквизитом типа перечисление, не отображалась и не сохранялась.

Стало возможно управлять поведением истории выбора для полей ввода связанных с реквизитами типа перечисление.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Реализован конструктор для объекта ЗначенияПолейРасшифровкиКомпоновкиДанных. Для объекта ЗначенияПолейРасшифровкиКомпоновкиДанных отсутствовал конструктор.Стало возможно заполнение данных расшифровки из встроенного языка.
Web-сервисы и HTTP-сервисы.
Для объекта HTTPСоединение реализована возможность вызывать любые HTTP-методы (с указанием имени метода строкой). Для упрощения использования HTTP-методов PATCH и HEAD реализованы методы Изменить() и ПолучитьЗаголовки() (соответственно) для объекта HTTPСоединение.Данные возможности не предоставлялись.

С помощью объекта HTTPСоединение можно было выполнять только HTTP-методы GET, PUT, POST и DELETE.

Упрощено полноценное использование протокола HTTP из прикладных решений.
Кластер серверов.
Средства администрирования.
Расширены возможности внешнего управления сеансами. Реализованы методы, вызываемые при переходе сеанса в спящее состояние и выходе из этого состояния. Реализована возможность указывать тайм-аут ожидания ответа Web-сервиса внешнего управления сеансами.

Для Web-сервиса внешнего управления сеансами реализованы методы onHibernateSession() и onWakeupSession().

Для строки соединения с Web-сервисом внешнего управления сеансами реализованы необязательные параметры tout - задает величину тайм-аута ожидания ответа Web-сервиса внешнего управления сеансами и wsver - указывает версию интерфейса Web-сервиса внешнего управления сеансами. Новые возможности доступны только в том случае, если параметр wsver имеет значение 2.

Данные возможности не предоставлялись.Возможности Web-сервиса синхронизированы с возможностями платформы по работе с лицензиями.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с XML, XDTO.
Переработан механизм работы с FastInfoSet.Механизм работы с FastInfoSet имел другую реализацию.Повышена стабильность работы с FastInfoSet.
Полнотекстовый поиск.
Реализована возможность проверки целостности индекса полнотекстового поиска. Реализован метод ПроверитьИндекс() менеджера полнотекстового поиска.

Реализовано отражение в технологическом журнале операций обновления индекса полнотекстового поиска. Реализованы события технологического журнала FTEXTCheck и FTEXTUpd. Реализован элемент технологического журнала ftextupd.

Данные возможности не предоставлялись.Повышена стабильность работы с полнотекстовым поиском. Стало возможно выполнять перестроение индекса полнотекстового поиска в тех случаях, когда этот индекс стал некорректным.
В документации данное изменение описано здесь, здесь и здесь.
Работа с запросами.
Для объекта ОписаниеВременнойТаблицыСхемыЗапроса реализовано свойство ИмяТаблицы. В конструкторе запросов реализована возможность указать имя временной таблицы.

Для метода Добавить() объекта ИсточникиСхемыЗапроса реализован параметр Псевдоним.

Данные возможности не предоставлялись.Улучшена работа с программной моделью запроса.
Средства разработки.
Общие реквизиты / Разделение данных.
Расширение конфигурации.
Расширены возможности модификации прикладных решений без снятия с поддержки (в том числе и для облачных систем). Реализована возможность создания расширений конфигурации. С помощью механизма расширений предоставляется возможность выполнять некоторые модификации прикладного решения (не затрагивающие структур данных) так, что само решение не снимается с поддержки, а все доработки локализованы в специальном объекте (расширении), который достаточно легко подключается и отключается от прикладного решения.

В расширении реализована возможность модификации форм, создания отчетов и обработок, создания новых подсистем. Подключение расширений конфигурации возможно в режиме 1С:Предприятие и конфигуратора. Для каждой области разделенной информационной базы имеется возможность задавать свой набор расширений.

Данная возможность не предоставлялась.

Существовала возможность создания внешних отчетов и обработок, а также модификации конфигурации прикладного решения, что вело к необходимости снятия с поддержки и не позволяло реализовывать разные доработки для разных областей разделенной информационной базы.

Реализован новый механизм, позволяющий выполнять небольшие доработки конфигураций при внедрениях (в том числе в разделенных информационных базах и облачных решениях) более просто и с большим уровнем независимости от изменений конфигураций поставщиками.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Отображение информации.
В библиотеку картинок добавлены новые картинки: ПерейтиВперед, ПерейтиНазад, ПерейтиКНачалу, ПерейтиККонцу, Сегодня, ПоказатьВСписке.В библиотеке картинок отсутствовали добавленные картинки.Расширен состав библиотеки картинок.
Обновление конфигурации базы данных.
В документации описаны ключи командной строки режима пакетного запуска конфигуратора, позволяющие управлять фоновым и динамическим обновлением конфигурации базы данных.Описание ключей пакетного запуска конфигуратора для управления процессом фонового и динамического обновления конфигурации базы данных отсутствовали в документации.Устранена ошибка документации.
В документации данное изменение описано здесь.
Системные требования.
Веб-клиент.
Реализована поддержка операционной системы Microsoft Windows 10.

Реализована поддержка веб-сервера Microsoft Information Services 10.0.

Реализована поддержка веб-браузера Microsoft Edge со следующими ограничениями:

  • отсутствует поддержка внешних компонент;
  • отсутствует расширение работы с файлами;
  • отсутствует расширение работы с криптографией.
Операционная система Microsoft Windows 10 не поддерживалась.

Веб-сервер Microsoft Information Services 10.0 не поддерживался.

Веб-браузер Microsoft Edge не поддерживался.

Расширен список поддерживаемых операционных систем и веб-браузеров.
В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Работа с СУБД.
Реализована поддержка СУБД PostgreSQL версии 9.4.Данная версия СУБД PostgreSQL не поддерживалась.Расширен список поддерживаемых версий СУБД PostgreSQL.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Командный интерфейс.
В меню функций (в интерфейсе Такси) реализован поиск функции по представлению. Поиск выполняется по всем разделам, а не только по командам текущего раздела.

Команды настройки панели навигации и панели действий перенесены в специальное подменю справа от поля поиска.

В интерфейсе Такси нажатие клавиши F10 приводит к открытию меню функций.

Возможность найти команду по фрагменту ее представления не предоставлялась.

Команды настройки панели навигации и панели действий располагались в виде гиперссылок в правой части меню функций.

В интерфейсе Такси нажатие клавиши F10 приводило к открытию главного меню приложения.

Работа с меню функций стало более комфортной.
В документации данное изменение описано здесь.
Управляемая форма.
Если для всех кнопок командной панели управляемой формы свойство ТолькоВоВсехДействиях имеет значение Ложь, и не все кнопки могут быть размещены в командной панели по ширине, то на командной панели добавляется кнопка Еще с подменю, в котором размещаются все команды командной панели.Если для всех кнопок командной панели управляемой формы свойство ТолькоВоВсехДействиях имеет значение Ложь, и не все кнопки могли быть размещены в командной панели по ширине, то было невозможно использовать команды, которые не поместились на командной панели (команды отсутствовали в командной панели).При небольших размерах командной панели стало возможно использовать все команды, которые размещены на этой командной панели.
В документации данное изменение описано здесь.
Клиентское приложение.
Реализована возможность полностью заменять заставку, которая отображается при запуске тонкого клиента, толстого клиента и веб-клиента.

Для выполнения такой замены необходимо обратиться в фирму «1С».

Данная возможность не предоставлялась.Появилась возможность, в отдельных случаях, при согласовании с фирмой «1С», использовать заставку, полностью определяемую организацией, использующей программный продукт.
Веб-клиент.
При печати табличных документов больше не используются всплывающие окна веб-браузера.При печати табличных документов использовались всплывающие окна веб-браузера.Упрощен процесс печати табличного документа для конечного пользователя. +При использовании режима интерфейса Такси или В закладках и при отсутствии в прикладном решении модальных вызовов, исключена необходимость дополнительной настройки веб-браузера для работы с прикладным решением.
Управляемая форма.
Если для поля ввода управляемой формы доступна команда создания, то она отображается в контекстном меню этого поля.Команда создания никогда не отображалась в контекстном меню поля.Повышено удобство использования.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Полнотекстовый поиск.
Оптимизирован полнотекстовый поиск в случае повторного использования поискового запроса, например, при получении следующей порции результатов поиска.

Оптимизирован полнотекстовый поиск в том случае, если не на все объекты, соответствующие поисковому запросу, у текущего пользователя имеются права.

Скорость работы полнотекстового поиска была недостаточной.Ускорен полнотекстовый поиск для информационных баз, содержащих большое количество элементов, а также в том случае, если текущий пользователь не имеет прав на все объекты, соответствующие поисковому запросу.
Полнотекстовый поиск.
Уменьшено использование оперативной памяти при выполнении нечеткого поиска (поиск с применением оператора #). Оптимизирован поиск близких слов.При выполнении нечеткого поиска могло наступать переполнение оперативное памяти, что приводило к аварийному завершению работы.

Поиск близких слов выполнялся недостаточно быстро.

Повышена стабильность при использовании нечеткого поиска при больших объемах индекса полнотекстового поиска.
Веб-клиент.
Повышена производительность веб-клиента в следующих случаях:
  • Загрузка веб-клиента, в том числе на медленном соединении;
  • Открытие форм;
  • Общее ускорение работы в различных сценариях.

При работе веб-клиента используется Google Closure Compiler. +

Производительность веб-клиента была недостаточной.Повышена производительность работы веб-клиента.
В документации данное изменение описано здесь.
Встроенный язык.
Уменьшено (незначительно) время загрузки модулей на встроенном языке.Загрузка модулей на встроенном языке выполнялась недостаточно быстро.Уменьшено (незначительно) время запуска прикладных решений, содержащих большое количество модулей на встроенном языке.
Клиентское приложение.
Уменьшено (незначительно) время запуска клиентского приложения (до появления диалога аутентификации).Клиентское приложение запускалось недостаточно быстро.Уменьшено (незначительно) время запуска клиентского приложения.
Хранилище конфигурации.
Ускорено выполнение следующих операций:
  • Создание хранилища;
  • Первое подключение к хранилищу;
  • Помещение объектов в хранилище;
  • Обновление объектов из хранилища;
  • Обновление конфигурации из хранилища.

Ускорено выполнение операций смены режима совместимости.

Для хранилища конфигурации реализован режим совместимости с «1С:Предприятием» версии 8.3.3.

Ускорение работы с хранилищем конфигурации наблюдается в том случае, если режим совместимости хранилища установлен в значение Не использовать.

Работа с хранилищем конфигураций выполнялась недостаточно быстро.Ускорена работа с хранилищем конфигурации.
В документации данное изменение описано здесь.
Управляемая форма.
Оптимизирован алгоритм усиленного сжатия для больших объемов данных (свыше 64 Кбайт), передаваемых между клиентом и сервером (или расширением веб-сервера). В результате уменьшено (незначительно) время открытия управляемых форм при работе тонкого клиента через веб-сервер (для файлового и клиент-серверного вариантов работы), а также при прямом подключении в клиент-серверном варианте работы.Алгоритм усиленного сжатия работал недостаточно эффективно.Уменьшено (незначительно) время открытия управляемых форм при работе тонкого клиента через веб-сервер (для файлового и клиент-серверного вариантов работы), а также при прямом подключении в клиент-серверном варианте работы.
Web-сервисы и HTTP-сервисы.
Ускорена обработка запросов при обращении к стандартному интерфейсу OData.Обработка запросов при обращении к стандартному интерфейсу OData выполнялась недостаточно быстро.Ускорена работа со стандартным интерфейсом OData.
Управляемая форма.
Ускорено открытие управляемой формы в следующих случаях:
  • При большом количестве элементов формы;
  • При большом количестве реквизитов формы;
  • При значительных программных изменениях состава реквизитов и элементов формы;
  • При большом количестве пользователей, работающих с управляемыми формами.
В указанных случаях скорость открытия управляемых форм была недостаточной.Работа с управляемыми формами стала более комфортной.
Управляемая форма.
Оптимизирована работа условного оформления управляемой формы.Производительность работы условного оформления управляемой формы была недостаточной.Работа с управляемыми формами, содержащими условное оформление, стала более комфортной.
Средства разработки.
Ускорены операции, связанные с обновлением основной конфигурации (обновление конфигурации из файла, загрузка конфигурации из файла, получении версии из хранилища конфигурации).Обновление основной конфигурации выполнялось недостаточно быстро.Повышен комфорт работы прикладного разработчика.
Работа с СУБД.
Средства администрирования.
Для файлового варианта информационной базы реализована возможность реструктуризации служебной информации таким образом, что вся информация, необходимая для открытия информационной базы, располагается последовательно в начале файла 1Cv8.1CD. Это приводит к повышению скорости открытия информационной базы.

Данная оптимизация выполняется только при выполнении операции сжатия таблиц информационной базы (с помощью диалога конфигуратора или соответствующего параметра командной строки) и при выполнении тестирования утилитой chdfl с установленным флажком Исправлять обнаруженные ошибки.

Данную оптимизацию рекомендуется выполнять повторно после изменений конфигурации (и связанной реструктуризации информационной базы), приводящих к изменению структуры базы данных.

Служебная информация, необходимая для открытия информационной базы, равномерно распределялась по файлу информационной базы 1Cv8.1CD.Ускорено открытие файлового варианта информационной базы, особенно расположенной на сетевом ресурсе.
В документации данное изменение описано здесь, здесь и здесь.
Работа с СУБД.
При работе в клиент-серверном варианте с использованием СУБД PostgreSQL оптимизирован запрос, выполняющийся при удалении движений из таблицы субконто регистра бухгалтерии.При работе в клиент-серверном варианте с использованием СУБД PostgreSQL запрос, выполняющийся при удалении движений из таблицы субконто регистра бухгалтерии, работал не оптимально.Ускорено удаление записей из регистра бухгалтерии.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
При перезапуске клиентского приложения, в случае использования ключа /AppAutoCheckMode, учитываются права на запуск соответствующего клиентского приложения. При этом пользователь не получит доступ в информационную базу, если у пользователя установлен обычный режим запуска и нет возможности запустить толстый клиент. В остальных случаях будет подобрано клиентское приложение, максимально подходящее под режим запуска.При перезапуске клиентского приложения, в случае использования ключа /AppAutoCheckMode, права на запуск соответствующего клиентского приложения не учитывались.Подбор клиентского приложения стал более корректным.
В документации данное изменение описано здесь.
Управляемая форма.
Если для расширения поля формы для поля ввода управляемой формы запрещено редактирование текста (свойство РедактированиеТекста установлено в значение Ложь), то в выпадающем списке не отображается приглашение ввести текст для поиска.В выпадающем списке всегда отображалось приглашение ввести текст для поиска.Предложение выполнить недоступное действие больше не отображается на экране.
Средства разработки.
Реализована возможность вносить изменения в результат объединения модулей непосредственно в процессе объединения конфигураций. Реализована возможность использования внешних (относительно конфигуратора) программ для выполнения операций сравнения и объединения текстов модулей.

Настройка используемых внешних программ выполняется в диалоге настройки параметров конфигуратора.

Для следующих внешних программ существуют готовые настройки использования:

  • Для ОС Windows - Araxis Merge, KDiff3, TortoiseMerge, Perforce P4Merge, DiffMerge;
  • Для ОС Linux - KDiff3, Perforce P4Merge.

Возможно настроить использование внешних программ, не входящих в вышеуказанный список.

В процессе объединения конфигураций было невозможно вносить изменения в результат объединения.

Для операций сравнения и объединения текстов модулей использовались только встроенные возможности конфигуратора.

Разработчик может использовать для операций сравнения/объединения текстов модулей удобный для него инструмент. Стало возможно вносить изменения непосредственно в процессе объединения конфигураций (при использовании внешних программ).
В документации данное изменение описано здесь.
Средства разработки.
Упрощена настройка режима сравнения/объединения для управляемой формы. Правила для самой формы и ее модуля задаются непосредственно в диалоге сравнения/объединения.Правила настройки режима сравнения/объединения управляемой формы раздельно для модуля и самой формы настраивались в специальном диалоге.Упростилась настройка режима объединения для управляемой формы и ее модуля.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Средства разработки.
В редакторе управляемой формы реализованы следующие возможности:
  • Если свойство Заголовок управляемой формы не пустое - значение свойства отображается в заголовке окна в области предварительного просмотра;
  • Заголовок в области предварительного просмотра позволяет выделить всю форму, для заголовка реализовано контекстное меню, соответствующее всей форме.
Заголовок окна в области предварительного просмотра редактора управляемой формы никак не использовался для работы.Повышено удобство работы с областью предварительного просмотра формы в редакторе управляемой формы.
В документации данное изменение описано здесь.
Работа с Интернет.
Реализован автоматический подбор кодировки текста почтового сообщения, содержащего национальные символы. Подбор осуществляется только в том случае, если текст содержит национальные символы, но их кодировка, в нарушение стандарта, не указана. Подбор действует на текст:
  • В заголовках письма;
  • В теле письма;
  • Значение параметра заголовка, например, имя файла вложения.
Текст почтового сообщения, без указания кодировки, отображался нечитаемым.Почтовые сообщения, которые сформированы с отступлением от стандарта, стали обрабатываться корректно.
Фоновые и регламентные задания.
Ускорено первое обращение к менеджеру фоновых заданий (свойство глобального контекста ФоновыеЗадания) в файловом варианте информационной базы. Теперь время первого обращения существенно не отличается (по времени выполнения) от последующих обращений.Первое обращение к менеджеру фоновых заданий (свойство глобального контекста ФоновыеЗадания) в файловом варианте информационной базы могло приводить к блокировке работы пользовательского интерфейса до полной загрузки планировщика фоновых заданий.Ускорено обращение к менеджеру фоновых заданий при начале работы системы в файловом варианте информационной базы. Ускорен запуск клиентского приложения (в файловом варианте), в котором при начале работы системы выполняется обращение к менеджеру фоновых заданий.
Фоновые и регламентные задания.
Фоновые задания (при использовании файлового варианта информационной базы) принудительно завершаются через 30 секунд после завершения клиентского приложения, выполняющего фоновые задания. В случае принудительного завершения, в журнал регистрации записываются события _$Job$_.Terminate.Если системе не удавалось корректно завершить фоновые задания (при использовании файлового варианта информационной базы), то пользователю задавался вопрос с предложением подождать или принудительно завершить работу системы.Ликвидировано неожиданное и не очевидное (для пользователя) поведение системы.
В документации данное изменение описано здесь.
Обработка ошибок.
При обращении к свойствам и методам объектов ОбъектМетаданных, связанных с внешними обработками/отчетами, которые уже недоступны в момент обращения, генерируется исключение.При обращении к свойствам и методам объектов ОбъектМетаданных, связанных с внешними обработками/отчетами, которые уже недоступны в момент обращения, происходило аварийное завершение работы системы.Повышена стабильность работы системы.
Средства разработки.
Работа с Интернет.
В синтакс-помощнике выполнено уточнение информации:
  • Указано, что SSL поддерживается и для протоколов POP3 и SMTP;
  • Указано, что защищенное соединение не поддерживает проверку сертификатов сервера и клиента;
  • Указано, какие методы объекта ИнтернетПочта требуют IMAP-соединения.
  • Указано, какие именно поля заполняются в методе ПолучитьЗаголовки() объекта ИнтернетПочта.
Синтакс-помощник не содержал указанной информации.Улучшено качество синтакс-помощника.
Табличный документ.
При экспорте табличного документа в формате Microsoft Excel 2007 - 2010 примечания табличного документа сохраняются как примечания таблицы Excel.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При экспорте табличного документа в формате Microsoft Excel 2007 - 2010 примечания табличного документа сохранялись как рисунки таблицы Excel.Реализовано более точное преобразование элементов оформления табличного документа в элементы оформления Microsoft Excel.
В документации данное изменение описано здесь.
Фоновые и регламентные задания.
Регламентные задания начинают выполняться не ранее, чем через 1 минуту после старта клиентского приложения при работе в файловом варианте информационной базы.Регламентные задания (в файловом варианте информационной базы) начинали выполняться при запуске клиентского приложения.Уменьшены задержки при старте клиентского приложения при работе с файловым вариантом информационной базы.
В документации данное изменение описано здесь.
Определяемые типы.
При выполнении обновления конфигурации, находящейся на поддержке, реализована возможность объединения с приоритетами для свойства Тип объекта конфигурации ОпределяемыйТип и свойства Тип объекта конфигурации ПланВидовХарактеристик. Данная возможность не предоставлялась.Улучшен механизм сравнения и объединения определяемых типов, что упрощает использование таких типов в задачах разработки библиотек.
В документации данное изменение описано здесь.
Управляемая форма.
Представление элементов, найденных при вводе по строке, в случае использования полнотекстового поиска, совпадают с представлением элементов, найденных без использования полнотекстового поиска.

В выпадающем списке, сформированном с использованием полнотекстового поиска при вводе по строке, элементы располагаются в том порядке, в котором они возвращаются механизмом полнотекстового поиска.

Изменен алгоритм формирования представления объекта Задача при формировании выпадающего списка при вводе по строке.

Представление элементов, найденных при вводе по строке, в случае использования полнотекстового поиска, не совпадали с представлением элементов, найденных без использования полнотекстового поиска.

В выпадающем списке, сформированном с использованием полнотекстового поиска при вводе по строке, порядок расположения элементов был не определен.

Алгоритм формирования представления объекта Задача при формировании выпадающего списка при вводе по строке был другим.

Повышено удобство использования ввода по строке. Унифицировано формирование представления результатов поиска в разных случаях.
В документации данное изменение описано здесь.
Хранилище конфигурации.
В окне хранилища конфигурации для захваченных объектов отображается имя компьютера, с которого был выполнен захват объекта.В окне хранилища конфигурации для захваченных объектов отображалось имя компьютера, с которого текущий пользователь первый раз подключался к хранилищу.Устранено некорректное поведение системы.
Работа с Интернет.
Для объекта ИнтернетПочтовоеСообщение реализовано свойство СмещениеДатыОтправления.Данная возможность не предоставлялась.Стало возможно определить истинную дату отправления письма.
Динамический список.
Свойство расширения таблицы формы для динамического списка Период и свойство Отображение таблицы формы, связанной с динамическим списком, при открытии формы загружаются из настроек одновременно с загрузкой пользовательских настроек динамического списка.

Рекомендуется выполнять получение свойства Период в обработчике события управляемой формы ПриЗагрузкеПользовательскихНастроекНаСервере.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Свойство расширения таблицы формы для динамического списка Период получалось из пользовательских настроек до выполнения обработчика события управляемой формы ПриСозданииНаСервере.

Свойство Отображение таблицы формы, связанной с динамическим списком, получалось из настроек на клиенте при открытии формы.

Свойства Период и Отображение стали хранится в тех же разрезах, что и остальные настройки динамического списка, что упрощает работу с ними из встроенного языка.
В документации данное изменение описано здесь.
Табличный документ.
Веб-клиент.
При отображении непустых ячеек табличного документа свойство Размещение которых имеет значение Авто, не используется объединение ячеек до следующей заполненной ячейки, либо до конца табличного документа по горизонтали.При отображении непустых ячеек табличного документа свойство Размещение которых имеет значение Авто, ячейки объединялись до следующей заполненной ячейки, либо до конца табличного документа по горизонтали.Отображение табличного документа в веб-клиенте приближено к отображению табличного документа в тонком клиенте.
Работа с СУБД.
При работе в клиент-серверном варианте с использованием СУБД Oracle Database исполнение запроса, содержащего подзапрос в разделе ВЫБРАТЬ, а также агрегатную функцию, приводит к добавлению предложения GROUP BY с константой, если такого предложения нет в запросе.При работе в клиент-серверном варианте с использованием СУБД Oracle Database исполнение запроса, содержащего подзапрос в разделе ВЫБРАТЬ, а также агрегатную функцию, приводило к ошибке времени исполнения ORA-937.Повышена стабильность работы при использовании СУБД Oracle Database.
Управляемая форма.
Реализован механизм, препятствующий аварийному завершению рабочих процессов или клиентского приложения при обнаружении проблем в работе управляемой формы (рассинхронизация клиентской и серверной части данных формы). При обнаружении проблемы завершается только сеанс, в котором проблема возникла, не приводя к аварийному завершению работы рабочего процесса, обслуживающего данный сеанс. +Информация о таких проблемах фиксируется в технологическом журнале по умолчанию.Рассинхронизация клиентской и серверной части данных формы могло приводить к аварийному завершению работы рабочего процесса, обслуживающего данный сеанс или клиентского приложения.Повышена стабильность работы сервера «1С:Предприятия» при работе управляемой формы.
Работа с СУБД.
Снижена вероятность взаимоблокировок при использовании в запросах сравнений со значением Неопределено. Вероятность взаимоблокировок при использовании в запросах сравнений со значением Неопределено была выше.Повышена стабильность системы. Снижена вероятность возникновения взаимоблокировок с неочевидными причинами.
Клиентское приложение.
Управляемая форма.
Отображение информации.
Для клиентских приложений, работающих под управлением ОС Windows, реализована поддержка масштабирования Windows. При установке нестандартной величины DPI выполняется корректное изменение элементов интерфейса, кроме картинок, которые в этом случае могут выглядеть несколько «размытыми».Клиентские приложения, работающие под управлением ОС Windows, некорректно поддерживали масштабирование.Улучшено поведение системы в том случае, если пользователем установлено нестандартное значение DPI для используемого монитора.
Хранилище конфигурации.
При отказе от подключения к хранилищу конфигурации или при смене расположения информационной базы, подключенной к хранилищу, более не задается вопрос о необходимости выполнить отключение от хранилища.

Для отключения от хранилища следует использовать специальную команду конфигуратора.

При отказе от подключения к хранилищу конфигурации или при смене расположения информационной базы, подключенной к хранилищу, всегда задавался вопрос о необходимости выполнить отключение от хранилища.В ряде случаев работа с хранилищем конфигурации стала более комфортной.
Командный интерфейс.
Настройки видимости для команд в подчиненных подсистемах более не теряются при копировании настроек командного интерфейса подсистемы, содержащей подчиненные подсистемы, при помощи методов Загрузить() и Сохранить() объекта СтандартноеХранилищеНастроекМенеджер.При копировании настроек командного интерфейса подсистемы, содержащей подчиненные подсистемы, при помощи методов Загрузить() и Сохранить() объекта СтандартноеХранилищеНастроекМенеджер, терялись настройки видимости для команд в подчиненных подсистемах.Устранено некорректное поведение системы.
Веб-клиент.
Табличный документ.
В веб-клиенте реализована возможность выделения рисунков табличного документа с вызовом соответствующего события.

Доработано отображение рисунков в табличном документе, отображаемом в веб-клиенте:

  • Не происходит объединение ячеек, которые перекрывает рисунок;
  • Поддерживается наложение текста и рисунка в ячейке табличного документа;
  • Ликвидированы проблемы, возникающие в том случае, если границы рисунка располагаются вдоль границ ячеек.
Не поддерживалось выделение рисунков в табличном документе. Отображение рисунков могло приводить к возникновению некоторых проблем.Повышение качества отображения табличного документа, отображающего рисунки, в веб-клиенте.
Средства разработки.
Мобильное приложение.
Диалог редактирования картинок в конфигураторе поддерживает редактирование шаблонных картинок и нового формата картинок с вариантами (с использованием манифеста).

Шаблонные картинки используются при разработке прикладных решений для мобильной платформы.

Редактирование шаблонных картинок и нового формата картинок с вариантами (с использованием манифеста) не поддерживались.Реализована поддержка работы с шаблонными картинками.
В документации данное изменение описано здесь.
Работа с СУБД.
Упрощен запрос к СУБД, который формируется платформой при использовании в языке запросов функции ТИПЗНАЧЕНИЯ. При использовании в языке запросов функции ТИПЗНАЧЕНИЯ, запрос к СУБД был более сложный.Исключены проблемы, возникающие в том случае, когда СУБД не могла выполнить обработку сложного запроса.
Средства разработки.
При выполнении объединения конфигураций и операциях с хранилищем не используются механизмы рефакторинга, которые срабатывают при переименовании и удалении объектов конфигурации.При выполнении объединения конфигураций и операциях с хранилищем использовались механизмы рефакторинга, используемые при переименовании и удалении объектов конфигурации.Устранено некорректное поведение системы.

Исключено выполнение действий, результат которых игнорировался.

Встроенный язык.
При передаче методу (написанному на встроенном языке) некоторого объекта, обращение к свойствам этого объекта выполняется корректно при изменении (после начала вызова) состава свойств объекта с сохранением имени данного свойства. Например, при добавлении свойств. При изменении имени свойства обращение не может быть выполнено корректно.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При передаче методу (написанному на встроенном языке) некоторого объекта, обращение к свойствам этого метода выполнялось по номерам свойств, определенных на момент вызова метода. При изменении (после начала вызова) номера свойства (например, при вставке нового свойства) это не учитывалось и обращение выполнялось по старому номеру.Повышена надежность системы, в частности снижена вероятность возникновения ошибки в том случае, если состав свойств объекта изменялся во время работы метода.
В документации данное изменение описано здесь.
Управляемая форма.
В тонком клиенте форматированные строки, заданные при формировании выпадающего списка, отображаются в соответствии со своим оформлением в том случае, когда поле ввода связано с реквизитом составного типа и данный реквизит имеет значение Неопределено.В тонком клиенте форматированные строки, заданные при формировании выпадающего списка, отображались без заданного оформления в том случае, если поле ввода связано с реквизитом составного типа и данный реквизит имел значение Неопределено.Устранено некорректное поведение системы.
Веб-клиент.
Управляемая форма.
В веб-клиенте для оформления выпадающего списка используются те же цвета, что и в других клиентских приложениях.В веб-клиенте для оформления выпадающего списка использовались цвета, отличающиеся от цветов, используемых в других клиентских приложениях.Оформление выпадающего списка в веб-клиенте приведено в соответствие с другими клиентскими приложениями.
Веб-клиент.
В веб-клиенте максимально приближено к тонкому клиенту оформление следующих элементов интерфейса:
  • кнопка формы;
  • кнопка командной панели;
  • командная панель;
  • разделитель.

+

В веб-клиенте оформление следующих элементов интерфейса отличалось от оформления в тонком клиенте:
  • кнопка формы;
  • кнопка командной панели;
  • командная панель;
  • разделитель.

+

Унифицировано оформление клиентских приложений.
Командный интерфейс.
Стандартная команда, которая была размещена в удаленной пользовательской группе команд, автоматически размещается в той стандартной группе, в которой она размещается по умолчанию.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Стандартная команда, которая была размещена в удаленной пользовательской группе команд, переставала отображаться в командном интерфейсе.Устранено некорректное поведение системы.
Журнал регистрации.
При использовании метода ВыгрузитьЖурналРегистрации() время события усекается до секунд.

При использовании отбора по времени журнала регистрации (методы ВыгрузитьЖурналРегистрации(), СкопироватьЖурналРегистрации(), ОчиститьЖурналРегистрации()), событие считается соответствующим отбору также в том случае, если реальное время события больше установленного в отборе только на миллисекунды.

При использовании метода ВыгрузитьЖурналРегистрации() время события выдавалось с точностью до миллисекунд.

При использовании отбора по времени журнала регистрации (методы ВыгрузитьЖурналРегистрации(), СкопироватьЖурналРегистрации(), ОчиститьЖурналРегистрации()), событие считалось соответствующим отбору только при выполнении строго условия (включая миллисекунды).

Устранено некорректное поведение системы.

Поведение журнала формата .lgd приведено в соответствие с журналом формата .lgf (в части представления времени события и работы отборов).

Средства печати.
Табличный документ.
Изменен алгоритм расчета ширин колонок табличного документа при печати. Ширины колонок на экране и в печатном документе теперь больше соответствуют друг другу. Изменение алгоритма заметно в том случае, если в табличном документе присутствует фоновая картинка.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Ширины колонок табличного документа на экране и при печати не вполне соответствовали друг другу.Улучшено формирование табличного документа при печати.
Региональные установки.
Для Российской Федерации учитывается однократный сдвиг часовых зон на один час в связи с принятием законов №№ 453-ФЗ, 27-ФЗ, 57-ФЗ, 58-ФЗ, 59-ФЗ, 69-ФЗ. Изменения касаются всех компонентов системы «1С:Предприятие», кроме веб-клиента. Веб-клиент пользуется информацией о временных зонах, которую предоставляет ОС и веб-браузер. +Изменения, внесенные законом №№ 453-ФЗ, 27-ФЗ, 57-ФЗ, 58-ФЗ, 59-ФЗ, 69-ФЗ, не учитывались платформой. +Учтены изменения законодательства об исчислении времени.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Работа с Интернет.
В будущих версиях «1С:Предприятия» будет отключена возможность использования сертификатов NSS (и связанных объектов) независимо от режима совместимости.

Станет недоступен объект ЗащищенноеСоединениеNSS, сертификаты NSS станут недоступны для использования во встроенном языке и при настройке подключения тонкого клиента по протоколу HTTPS.

Система «1С:Предприятие» поддерживает работу с сертификатами NSS.Будущие версии платформы не будут работать с сертификатами NSS.
Автоматизированное тестирование.
Функция ТекущаяВидимость() объекта ТестируемаяГруппаФормы возвращает значение Ложь в том случае, если объект ссылается на группу формы являющейся неактивной страницей в группе страниц, расположенной в группе страниц без отображения закладок.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Функция ТекущаяВидимость() объекта ТестируемаяГруппаФормы возвращала значение Истина в том случае, если объект ссылался на группу формы являющейся неактивной страницей в группе страниц, расположенной в группе страниц без отображения закладок.Механизм автоматизированного тестирования более корректно имитирует работу системы и предоставляет информацию о статусе элементов формы.
Управляемая форма.
Для реквизитов управляемой формы типа табличный документ, графическая схема и текстовый документ, вызов метода Показать() приводит к исключению.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Поведение системы зависело от размещения реквизита на форме и вида клиентского приложения:
  • Реквизит связан с элементом управляемой формы:
    • Тонкий клиент:
      • табличный документ - выполняется активизация текущей формы;
      • графическая схема - открывается новая форма с копией схемы;
      • текстовый документ - открывается новая форма с копией документа.
    • Веб-клиент:
      • выполняется активизация текущей формы для любого типа реквизита (табличный документ, графическая схема, текстовый документ).
    • Реквизит не связан с элементом управляемой формы:
    • Тонкий клиент:
      • открывается новая форма с копией документа для любого типа реквизита (табличный документ, графическая схема, текстовый документ).
    • Веб-клиент:
      • табличный документ - открывается новая форма с копией документа;
      • графическая схема - выполняется активизация текущей формы;
      • текстовый документ - выполняется активизация текущей формы.
Приведено к единому поведение различных объектов в различных клиентах.
Управляемая форма.
В тонком и толстом клиентах кнопка (или гиперссылка), расположенная на управляемой форме (не в командной панели) отображается недоступной, если недоступной становится команда, связанная с этой кнопкой.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

В тонком и толстом клиентах кнопка (или гиперссылка), расположенная на управляемой форме (не в командной панели) отображалась доступной, даже если команда, связанная с этой кнопкой, была недоступной.Поведение системы стало более ожидаемым.

Обеспечено одинаковое поведение в различных клиентских приложениях.

В документации данное изменение описано здесь.
Управляемая форма.
При создании элемента из выпадающего списка, связанного с полем ввода, реализована возможность проверять созданный элемент на соответствие параметрам выбора, которые использовались при открытии формы нового элемента. Если элемент не соответствует параметрам выбора - будет выдано диагностическое сообщение и созданный элемент не будет помещен в поле ввода.

Проверка реализована для расширения управляемой формы для объектов, справочников, документов, планов видов характеристик, бизнес-процессов и задач.

Реализовано:

  • Стандартный параметр расширения управляемой формы ПараметрыВыбора;
  • Свойство расширения управляемой формы ПараметрыВыбора;
  • Свойство расширения управляемой формы ВыборДоступен;
  • Событие расширения управляемой формы ВыборЗначения.

В режиме совместимости с версией 8.3.5 недоступны свойства расширения управляемой формы ПараметрыВыбора и ВыборДоступен.

Имелась возможность создать новый элемент, который не соответствует параметрам выбора, заданным для поля ввода, и выбрать его в поле ввода.Уменьшена вероятность создания элемента (из списка выбора поля ввода), не соответствующего параметрам выбора, которые установлены для поля ввода.
В документации данное изменение описано здесь.
Управляемые блокировки.
Поле Период, установленное в отборе набора записей периодического регистра сведений, включается в набор полей, по которым устанавливается управляемая блокировка при чтении или записи набора записей.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При чтении или записи набора записей периодического регистра сведений, поле Период не включалось в управляемую блокировку, устанавливаемую при этой операции.Повышена параллельность работы системы при работе с периодическим регистром сведений, уменьшена вероятность получения взаимоблокировок.
Общие реквизиты / Разделение данных.
Регистры сведений.
При записи набора данных регистра сведений все значения по умолчанию для независимых и совместных разделителей, в состав которых входит регистр сведений, заменяются на значения разделителей, установленных в текущем сеансе.

Если значение разделителя не совпадает со значением по умолчанию для типа разделителя или не равно значению разделителя, установленного в текущем сеансе - генерируется ошибка.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При записи набора данных регистра сведений значения независимых и совместных разделителей, в состав которых входит регистр сведений, всегда заменялись на значения разделителей, установленных в текущем сеансе.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Работа с Интернет.
Если в качестве строкового значения критерия отбора (параметр Отбор) в методах ПолучитьЗаголовки() и ПолучитьИдентификаторы() объекта ИнтернетПочта (при работе с сервером Microsoft Exchange) используется строка, которая содержит только символы US-ASCII, то серверу будет дополнительно передаваться информация об этом. В противном случае будет использоваться строка в кодировке UTF-8.

Если в качестве значения критерия отбора передается строка, содержащая не только символы US-ASCII (например, символы кириллицы), то при обращении к серверу Microsoft Exchange будет диагностирована ошибка.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Методы ПолучитьЗаголовки() и ПолучитьИдентификаторы() объекта ИнтернетПочта всегда возвращали пустой массив при использовании строкового значения параметра Отбор при работе с Microsoft Exchange.Повышена совместимость с Microsoft Exchange при работе с объектом ИнтернетПочта. Стало возможно выполнять поиск в том случае, если значение строкового критерия отбора содержит только символы в кодировке US-ASCII.
Работа с Интернет.
Для работы с протоколами IMAP, SMTP, POP3 используется библиотека libetpan.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Для работы с протоколами IMAP, SMTP, POP3 использовалась библиотека UW IMAP toolkit.Повышена стабильность и быстродействие при работе с электронной почтой.
В документации данное изменение описано здесь.
Работа с Интернет.
При создании объекта ИнтернетПрокси (при работе под управлением ОС Linux) используются значения переменных окружения ОС http_proxy, https_proxy, ftp_proxy, ftps_proxy, all_proxy в тех случаях, если параметр конструктора ПроксиПоУмолчанию имеет значение Истина и система не может обнаружить файл inetcfg.xml.

Методы объектов HTTPСоединение и FTPСоединение не пытаются определить настройки прокси-сервера, а используются те настройки, которые находятся в свойстве Прокси соответствующего объекта.

Для метода Установить() объекта ИнтернетПрокси реализованы параметры Пользователь и Пароль. Для объекта ИнтернетПрокси реализованы методы Пользователь() и Пароль(). Свойства Пользователь и Пароль объекта ИнтернетПрокси являются устаревшими и поддерживаются для совместимости.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

+

Переменные среды не использовались при создании объекта ИнтернетПрокси при работе под управлением ОС Linux. Если при создании объектов HTTPСоединение и FTPСоединение не были указаны параметры прокси-сервера, при выполнении методов объектов производилась попытка определения параметров прокси-сервера из переменных окружения. Устранено различие в поведении при работе под ОС Windows и Linux. Устранено неочевидное поведение системы, проявлявшееся в том, что методы объектов HTTPСоединение и FTPСоединение пытались самостоятельно определить настройки используемого прокси-сервера.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Обработчики ожидания не вызываются во время блокировки клиентского приложения, установленной методом глобального контекста ЗаблокироватьРаботуПользователя() или командой Временная блокировка.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Установка блокировки клиентского приложения (с помощью метода глобального контекста ЗаблокироватьРаботуПользователя() или командой Временная блокировка) не оказывали влияния на выполнение обработчиков ожидания.Повышена безопасность системы.
В документации данное изменение описано здесь.
Работа с xBase.
При работе с dbf-файлами с помощью объекта XBase, в случае возникновения ошибки генерируется исключение.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При работе с dbf-файлами с помощью объекта XBase, в случае возникновения ошибки формировались диалоговые окна.Исключены ситуации, которые выглядят как «зависание» системы, например, ошибки при работе с dbf-файлами, которые происходят на стороне сервера «1С:Предприятия».
В документации данное изменение описано здесь.
Управляемая форма.
Для конструктора объекта СвязьПоТипу реализована возможность указывать первый параметр (ПутьКДанным) в виде пустой строки.Конструктор объекта СвязьПоТипу не мог получать пустую строку в качестве значения параметра ПутьКДанным.Стало возможно очищать свойство поля управляемой формы СвязьПоТипу путем присвоения нового объекта одноименного типа с неуказанным путем к данным.
Внешние источники данных.
Для объекта ВнешнийИсточникДанныхТаблицаОбъект реализованы методы ПолучитьИзменяемыеПоля() и УстановитьИзменяемыеПоля(). С помощью данных методов можно как ограничивать список записываемых полей таблицы внешнего источника данных, так и расширять его, относительно списка полей, возможность записи которых установлена в конфигурации (свойство ТолькоЧтение установлено в значение Ложь).

Методы ПолучитьЗаписываемыеПоля() и УстановитьЗаписываемыеПоля() являются устаревшими и поддерживаются для совместимости.

С помощью методов ПолучитьЗаписываемыеПоля() и УстановитьЗаписываемыеПоля() предоставлялась возможность только уменьшить количество полей, записываемых в таблицу внешнего источника данных. Не предоставлялась возможность выполнять запись в поля, помеченные в конфигураторе как доступные только для чтения.Стало возможно реализовывать специальные алгоритмы работы с внешними источниками данных, когда, например, необходимо выполнять запись в поля таблицы внешнего источника данных, которые в обычной работе не должны записываться.
В документации данное изменение описано здесь.
Средства администрирования.
При обновлении списка баз через Интернет и получении дистрибутива клиентского приложения реализовано получение корневых сертификатов удостоверяющих центров из хранилища сертификатов ОС Windows.При обновлении списка баз и получении дистрибутива клиентского приложения получение корневых сертификатов удостоверяющих центров выполнялось только из файла cacert.pem.Повышено удобство работы с самоподписанными сертификатами в корпоративной среде.
В документации данное изменение описано здесь, здесь и здесь.
Кластер серверов.
Реализована возможность указать пользователя, от имени которого будет запускаться менеджер кластера (rmngr), и который отличается от пользователя, от имени которого запускается агент кластера (ragent).

Реализована возможность указывать пользователей, от имени которых будут запускаться менеджер кластера (rmngr) и рабочий процесс (rphost) для каждого кластера на данном компьютере.

Реализована возможность указания своего каталога с реестром кластера для каждого менеджера кластера (rmngr) на данном компьютере.

Для файла swpuser.ini реализовано:

  • параметры rmngr_user и rmngr_pass;
  • параметр registry;
  • группа параметров НомерПорта:, которая может включать в себя все параметры файла swpuser.ini.
Для переопределения был доступен только пользователь, от имени которого должен запускаться рабочий процесс (rphost).Стало возможным повысить безопасность работы кластера серверов в том случае, когда, например, пользователи сервиса используют свои прикладные решения, внешние обработки и внешние компоненты, которым необходимо ограничить доступ к инфраструктуре компьютера, на котором работает кластер серверов.
В документации данное изменение описано здесь.
Ограничение доступа к данным.
Параметры шаблона ограничения доступа, указанные в комментариях, при подстановке не заменяются на фактические значения.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Параметры шаблона ограничения доступа, указанные в комментариях, при подстановке заменялись на фактические значения.Повышена стабильность системы ограничения доступа в некоторых ситуациях.
В документации данное изменение описано здесь.
Система компоновки данных.
Реализована возможность использования вложенных отчетов при выгрузке результата компоновки данных в коллекцию значений.

При выгрузке результата компоновки данных в коллекцию значений не создаются колонки с повторяющимися именами.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Использование вложенных отчетов при выгрузке результата компоновки данных в коллекцию значений было недоступно.

При выгрузке результата компоновки данных в коллекцию значений создавалось колонки без проверки на то, что колонка с таким именем уже присутствует в коллекции значений.

Расширены возможности применения системы компоновки данных.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
При выводе дополнительных данных для иерархических записей используются данные из иерархических записей.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При выводе дополнительных данных для иерархических записей использовались данные из детальных записей.В отчет стали выводиться более ожидаемые данные: при выводе в отчет таблицы с иерархическими группировками в строках, для иерархических строк группировки в колонках с дополнительной информацией выводятся данные, получаемые из иерархических записей, а не из детальных записей, как это было ранее.
В документации данное изменение описано здесь.
Система компоновки данных.
Значение, указанное у включенного параметра условного оформления Текст применяется к полям предопределенных макетов группировок и полей отчетов системы компоновки данных.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Значение, указанное у включенного параметра условного оформления Текст не применялось к полям предопределенных макетов группировок системы компоновки данных.Обеспечено совместное использование предопределенных макетов группировок и параметра условного оформления Текст системы компоновки данных.
В документации данное изменение описано здесь.
Система компоновки данных.
При оформлении ячейки, в которую выводится поле родительской группировки, используются выражения полей, полученные для текущей группировки.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При оформлении ячейки, в которую выводится поле родительской группировки, использовались выражения полей, полученные для родительской группировки.Оформление ячеек стало более ожидаемым.
В документации данное изменение описано здесь.
Динамический список.
При невозможности создать источник доступных настроек динамического списка генерируется исключение и создание формы не происходит.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При невозможности создать источник доступных настроек компоновки данных для динамического списка, никаких ошибок не генерировалось и работа управляемой формы продолжалась так, как будто источник данных динамического списка не содержит ни каких доступных полей. В результате все элементы формы, связанные с данными динамического списка, удалялись с управляемой формы.Улучшена диагностика ошибочных ситуация при работе с динамическим списком.
В документации данное изменение описано здесь.
Система компоновки данных.
Для иерархических записей группировок компоновщик макета компоновки данных использует поля детального набора данных. Для получения внутри агрегатных функций значения иерархической записи можно использовать функцию ВычислитьВыражение().

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Для иерархических записей группировок компоновщик макета компоновки данных использовал поля иерархического набора данных, если в этом наборе данных доступны соответствующие поля.Обеспечена возможность использования всех полей детальных записей в агрегатных функциях, вычисляемых для иерархических записей.
В документации данное изменение описано здесь.
Встроенный язык.
Метод НайтиПомеченныеНаУдаление() работает только с данными, доступными текущему пользователю.

В синтакс-помощнике описание методов НайтиПоСсылкам() и УдалитьОбъекты() приведено в соответствие с реальным поведением.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Метод НайтиПомеченныеНаУдаление() не учитывал доступность данных. При отсутствии прав доступа формировалась ошибка времени выполнения.

В синтакс-помощнике описание методов НайтиПоСсылкам() и УдалитьОбъекты() не соответствовало реальному поведению.

Исключено возникновение ошибки времени исполнения при попытке выполнить поиск помеченных на удаление в случае, если пользователю доступны не все объекты, среди которых выполняется поиск.

Поведение системы приведено в соответствие с описанием.

Управляемая форма.
В тонком клиенте, если в обработчике события управляемой формы ПриОткрытии параметру Отказ установлено значение Истина, то не вызывается обработчик события ПриЗакрытии и оповещение, установленное в свойстве управляемой формы ОписаниеОповещенияОЗакрытии.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Если в обработчике события управляемой формы ПриОткрытии параметру Отказ установлено значение Истина, то обработчик события ПриЗакрытии и оповещение, указанное в свойстве управляемой формы ОписаниеОповещенияОЗакрытии:
  • В тонком клиенте вызываются;
  • В веб-клиенте не вызываются.
Унифицировано поведение системы в различных клиентских приложениях.
В документации данное изменение описано здесь.
Автоматизированное тестирование.
Расширены возможности механизма автоматического тестирования:
  • Реализована работа с показателями производительности. Реализованы методы ПолучитьНакопленныеПоказателиПроизводительности() и ОчиститьНакопленныеПоказателиПроизводительности() объекта ТестируемоеПриложение.
  • Реализована поддержка элементов управляемой формы: поле индикатора и поле полосы регулирования. Реализована поддержка поля переключателя вида Тумблер.
  • Расширены возможности работы с таблицей управляемой формы:
    • Реализована возможность управления пометкой удаления. Реализован метод ПереключитьПометкуУдаленияСтроки() для объекта ТестируемаяТаблицаФормы.
    • Реализована возможность установки выделения и получения выделенных строк. Реализованы методы ВыделитьВсеСтроки(), ПолучитьВыделенныеСтроки() объекта ТестируемаяТаблицаФормы. Для методов ПерейтиКСтроке(), ПерейтиКПервойСтроке(), ПерейтиКПоследнейСтроке(), ПерейтиКПредыдущейСтроке(), ПерейтиКСледующейСтроке() реализован параметр ПереключитьВыделение.
    • Реализована возможность управления сортировкой данных в таблице. Реализован метод УстановитьПорядок() для объекта ТестируемаяТаблицаФормы.
  • Реализована возможность сворачивать и разворачивать группу управляемой формы. Реализованы методы Свернуть(), Развернуть(), ПолучитьТекущуюСтраницу() для объекта ТестируемаяГруппаФормы.

Метод ПолучитьТекстТекущейОбласти() объекта ТестируемоеПолеФормы является устаревшим. Рекомендуется использовать метод ПолучитьТекстОбласти() объекта ТестируемоеПолеФормы.

Реализована возможность автоматической записи журнала действий пользователя (если запись журнала была включена) при аварийном завершении работы клиентского приложения. Запись выполняется в каталог записи дампов аварийного завершения.

Доработана обработка преобразования журнала действий пользователя в сценарий на встроенном языке (см. здесь).

Не поддерживалась работа с показателями производительности, некоторые действия при работе с таблицей управляемой формы и группой управляемой формы.

Не поддерживалась работа с полем индикатора, полосой регулирования и видом поля переключателя Тумблер.

При аварийном завершении клиентского приложения не выполнялась запись журнала действий пользователя и накопленный журнал действий терялся.

Расширены возможности механизма. Снижено количество ручных операций при выполнении операций тестирования.
В документации данное изменение описано здесь.
Отображение информации.
Методы КраткоеПредставлениеОшибки() и ПодробноеПредставлениеОшибки() в сеансах без пользовательского интерфейса (фоновые и регламентные задания, web-сервисы и т.д.) формируют результат, совпадающий с действием этим методов в клиентских сеансах управляемого приложения.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Методы КраткоеПредставлениеОшибки() и ПодробноеПредставлениеОшибки() в сеансах без пользовательского интерфейса (фоновые и регламентные задания, web-сервисы и т.д.) формировали результат, совпадающий с действием этим методов в клиентских сеансах обычного приложения.Устранено незапланированное поведение системы.
Общие объекты.
При сохранении конфигурации выполняется проверка существования элементов стиля, которые названы эквивалентно значениям соответствующих системных наборов значений:
  • Для элементов стиля типа Цвет - системный набор значений ЦветаСтиля;
  • Для элемента стиля типа Шрифт - системный набор значений ШрифтыСтиля;
  • Для элемента стиля типа Рамка - системный набор значений РамкиСтиля.

При наличии таких элементов диагностируется ошибка и конфигурация не сохраняется.

При сохранении конфигурации не выполнялась проверка соответствия имен элементов стиля значениям соответствующих системных наборов значений.Устранено некорректное поведение системы.

Невозможно создать ситуацию, когда в одном из системных наборов значений, связанных с элементами стиля, оказывались два значения, имеющих одинаковое название.

Работа с Интернет.
Реализована диагностика некорректных сообщений электронной почты при разборе сообщений. Диагностика доступна как для получения сообщений с сервера, так и при формировании исходящего письма с помощью метода УстановитьИсходныеДанные() объекта ИнтернетПочтовоеСообщение. Для объекта ИнтернетПочтовоеСообщение реализовано свойство СтатусРазбора.

Реализовано событие технологического журнала <MAILPARSEERR>.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Обнаружение некорректного почтового сообщения приводило к аварийному завершению работы системы.Повышена надежность работы системы при работе с электронной почтой в том случае, если обрабатываемые электронные письма содержат ошибки.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Для метода УстановитьТелоИзСтроки() объектов HTTPЗапрос и HTTPСервисОтвет реализован параметр ИспользоватьBOM, позволяющий управлять наличием BOM в устанавливаемом тексте.

В режиме совместимости с версией 8.3.5 признак BOM по умолчанию формируется.

Данная возможность не предоставлялась.Облегчено взаимодействие с системами, которые не ожидают BOM в HTTP-запросах.
Обычная форма.
Для элемента обычной формы свойство Имя доступно только для чтения.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Для элемента обычной формы свойство Имя было доступно для чтения и записи.Исключена возможность программного изменения имени элемента обычной формы.
Работа с OData.
Уточнен список функций, поддерживаемых стандартным интерфейсом OData. Из документации исключено описание функции mod.Функция mod упоминалась в документации как поддерживаемая при работе со стандартным интерфейсом OData.Документация приведена в соответствие с фактическим поведением системы.
В документации данное изменение описано здесь.
Работа с файлами.
Клиентское приложение.
В тонком и толстом клиентах, в том случае, если при интерактивном получении файла с помощью метода ПолучитьФайл() выбрано открытие файла, проверяется наличие ассоциированного приложения (по расширению файла). Если ассоциированное приложение есть - файл открывается с использованием данного приложения. Если приложения нет - выводится системный диалог выбора приложения для открытия файла. Если в системном диалоге выбран отказ - происходит отказ от операции получения файла.

В веб-клиенте поведение не изменилось - оно совпадает с реализованным поведением тонкого/толстого клиентских приложений.

В тонком и толстом клиентах, в том случае, если при интерактивном получении файла с помощью метода ПолучитьФайл() выбрано открытие файла, проверялось наличие ассоциированного приложения (по расширению файла). Если ассоциированное приложение найдено - файл открывался с использованием данного приложения. Если приложение не найдено - происходил отказ от операции получения файла.

В веб-клиенте при этом выводился системный диалог выбора приложения для открытия файла.

Устранено различие в поведении веб-клиента и тонкого/толстого клиентских приложений.
Работа с файлами.
Веб-клиент.
Конструктор объекта Файл, с указанием имени файла, доступен при любом значении свойства конфигурации Режим использования синхронных вызовов расширений и внешних компонент. Механизмы проверки конфигурации и рефакторинга более не считают использование конструктор объекта Файл, с указанием имени файла, нерекомендуемым синхронным вызовом. В режиме «1С:Предприятие» использование такого конструктора не приводит к возникновению исключения.

В веб-клиенте использование конструктора объекта Файл, с указанием имени файла, более не требует установки расширения работы с файлами.

Описание конструктора объекта Файл без параметров и метода Файл.НачатьИнициализацию() удалено из документации. Использование метода Файл.НачатьИнициализацию() поддерживается для совместимости.

+

Конструктор объекта Файл, с указанием имени файла, был доступен при установки свойства конфигурации Режим использования синхронных вызовов расширений и внешних компонент в значения Использовать или Использовать с предупреждением. Механизмы проверки конфигурации и рефакторинга считали использование конструктор объекта Файл, с указанием имени файла, нерекомендуемым синхронным вызовом. В режиме «1С:Предприятие» использование такого конструктора приводило к возникновению исключения если свойство конфигурации Режим использования синхронных вызовов расширений и внешних компонент было установлено в значение Не использовать.

В веб-клиенте использование конструктора объекта Файл, с указанием имени файла, требовало установки расширения работы с файлами.

+

Использование объекта Файл для операций, не требующих доступ к файловой системе (например, получение расширения файла), снова стало возможно без установки расширения работы с файлами.
В документации данное изменение описано здесь.
Работа с Интернет.
Значения идентификаторов почтовых сообщений, полученных по протоколу IMAP, не зависят от способа указания используемого ящика (по умолчанию или с указанием имени).

После отключения режима совместимости выполнять проверку соответствия почтовых сообщений можно будет с использованием свойства ИнтернетПочтовоеСообщение.ИдентификаторСообщения.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

Значения идентификаторов почтовых сообщений, полученных по протоколу IMAP, зависели от способа указания используемого ящика (по умолчанию или с указанием имени).Стало возможно однозначно идентифицировать почтовое сообщение, вне зависимости от того, как указывается почтовый ящик. В результате упростилась процедура определения, какие почтовые сообщения уже получены, а какие являются новыми.
Веб-клиент.
Системные требования.
В список поддерживаемых веб-браузеров включен Google Chrome для архитектуры x86-64. При работе веб-браузера будут использоваться 32-разрядные версии внешних компонент и расширений.Веб-браузер Google Chrome для архитектуры x86-64 отсутствовал в списке поддерживаемых веб-браузеров.Расширен список поддерживаемых веб-браузеров.
В документации данное изменение описано здесь.
Система компоновки данных.
При выводе колонок макетов отчетов системы компоновки данных в дерево или таблицу значений, из имен колонок удаляются недопустимые символы.

В режиме совместимости с версией 8.3.5 поведение не изменилось.

При выводе колонок макетов отчетов системы компоновки данных в дерево или таблицу значений имена колонок копировались из имен выводимых полей.Устранено некорректное поведение системы.
Внешние компоненты.
В технологии внешних компонент реализована поддержка веб-браузеров Mozilla Firefox и Google Chrome (для ОС Windows, Linux, MacOS X всех архитектур) по одной технологии. Для сборки внешних компонент не требуется xulrunner (исключен из поставки).

Рекомендуется выполнить сборку новых установочных пакетов (.msi и .sh) для веб-браузера Mozilla Firefox и собрать новый архив с указанием в манифесте версии 40.*. Для поддержки старых версий платформы в архив также должны быть добавлены старые пакеты (.xpi) с указанием в манифесте версии 31.0.

Доработаны примеры и документация по технологии внешних компонент (см. здесь).

Внешние компоненты для веб-браузеров Mozilla Firefox и Google Chrome различались. При сборке внешних компонент для веб-браузера Mozilla Firefox использовался xulrunner.Обеспечена поддержка внешних компонент для веб-браузеров, прекративших поддержку механизмов, которые ранее использовались при создании внешних компонент.
Предопределенные данные.
При проверке конфигурации, которая выполняется перед каждым обновлением конфигурации базы данных, выполняется проверка уникальности имен предопределенных данных. Имя предопределенного элемента должно быть уникально в пределах одного объекта конфигурации. Если в конфигурации есть дубли предопределенных элементов, то информация о таких элементах выводится в окно сообщений, что, однако, не препятствует обновлению конфигурации.При проверке конфигурации, которая выполняется перед каждым обновлением конфигурации базы данных, проверка уникальности имен предопределенных данных не выполнялась.Повышена надежность обновления конфигурации, содержащей предопределенные данные.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Имя параметра обработчика события ОбработкаНавигационнойСсылки у декорации формы, расширения поля формы для надписи, управляемой формы.
  • НавигационнаяСсылка (URL).
  • НавигационнаяСсылкаФорматированнойСтроки (FormattedStringURL).
Ключ отбора, передаваемого в параметре Отбор для методов ПолучитьИдентификаторы() и ПолучитьЗаголовки() объекта ИнтернетПочта. Старое имя используется для совместимости.
  • ПолученОтвет.
  • Недавние.
Параметр обработчиков событий расширения поля ввода для поля формы АвтоПодбор и ОкончаниеВводаТекста.
  • Параметры.
  • ПараметрыПолученияДанных.
Наименование метода получения самого точного провайдера геопозиционирования. Старое наименование используется для совместимости.
  • GetMostAcurateProvider().
  • GetMostAccurateProvider().

+

+
Английский вариант имени метода СертификатКриптографии.НачатьВыгрузку().

Старое наименование поддерживается для совместимости.

  • BeginUnload().
  • BeginUnloading().
Английский вариант имени метода Файл.НачатьПроверкуСуществования().

Старое наименование поддерживается для совместимости.

  • BeginCheckingExist().
  • BeginCheckingExistence().

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Ускорен запуск мобильного приложения.Мобильное приложение запускалось недостаточно быстро.Работать с мобильным приложением стало более комфортно.
Средства разработки.
Отображение информации.
Изменен набор данных, расположенных в архиве картинки с вариантами. Описание вариантов картинок выполняется с помощью специального файла манифеста manifest.xml, входящего в состав архива. Имена файлов с картинками для конкретного разрешения могут быть произвольными. Реализована поддержка шаблонных картинок - картинок, имеющих прозрачный фон и отображаемых текущим цветом текста. Шаблонные картинки рекомендуется выполнять в формате PNG.Варианты картинок описывались особыми именами файлов. Файл манифеста не использовался.

Шаблонные картинки не поддерживались.

Стало возможно более полно использовать оформительские возможности мобильных операционных систем.
В документации данное изменение описано здесь.
Полнотекстовый поиск.
В мобильной платформе реализована возможность использовать полнотекстовый поиск. Обновление индекса выполняется автоматически, при изменении данных.

Поиск выполняется без учета морфологии. Не поддерживаются дополнительные словари и механизм извлечения текста. Обновление индекса происходит в том случае, если мобильная платформа не выполняет серверный вызов или фоновое задание.

Полнотекстовый поиск не поддерживался в мобильной платформе.Стало возможно использовать полнотекстовый поиск в мобильной платформе.
В документации данное изменение описано здесь и здесь.
Системные требования.
С точки зрения Google Play, мобильное приложение больше не считается оптимизированным только под телефон. Мобильное приложение считается оптимизированным для использования как с телефонами, так и с планшетами.

Необходимо пересобрать мобильное приложение с использованием новой мобильной платформы и обновить публикацию приложения в Google Play.

Магазин Google Play считал мобильное приложение оптимизированным только для телефона.Пользователи планшетов могут увидеть мобильные приложения в магазине Google Play в обычном списке, без необходимости поиска по наименованию.
Работа с календарями.
При создании поля компоновки данных, при работе с данным календарей и контактов, стало возможно указывать только имя поля, без указания типа данных.

Создание поля компоновки данных с указанием типа данных используется для совместимости.

При создании поля компоновки данных, при работе с данным календарей и контактов, было необходимо указывать полное имя поля, с учетом типа данных.Поведение системы приведено к описанному в документации. В некоторых случаях упрощена работа с данными календарей и контактов.
Оконная система.
Реализована возможность реагировать на изменение параметров экрана мобильного устройства.

Реализован обработчик ПриИзмененииПараметровЭкрана. Событие вызывается при изменении параметров экрана клиентского приложения.

Свойства Ширина и Высота объекта ИнформацияЭкранаКлиента отражают реальные значения (в зависимости от ориентации экрана).

Данная возможность не предоставлялась.

Отследить изменение параметров экрана мобильного устройства было невозможно. Свойства Ширина и Высота объекта ИнформацияЭкранаКлиента всегда содержали постоянные (канонические) значения.

Стало возможно обрабатывать изменение ориентации мобильного устройства и подключение мобильного устройства к внешнему монитору. Стало возможно создавать приложения, более удобные для использования конечным пользователем.
В документации данное изменение описано здесь.
Работа с мультимедиа.
Реализована возможность управлять качеством фото- и видеосъемки (только для ОС Android).

Реализована возможность управлять используемой камерой для фото- и видеосъемки.

Для методов ПоддерживаетсяФотоснимок() и ПоддерживаетсяВидеозапись() объекта СредстваМультимедиа реализован параметр ТипКамеры. Для метода СделатьФотоснимок() объекта СредстваМультимедиа реализованы параметры ТипКамеры, Разрешение, Качество и ЧерноБелый. Для метода СделатьВидеозапись() объекта СредстваМультимедиа реализованы параметры ТипКамеры, Качество. Для объекта СредстваМультимедиа реализован метод ПолучитьПоддерживаемыеРазрешенияКамеры().

Данные возможности не предоставлялись.Расширены возможности использования камер мобильных устройств.
В документации данное изменение описано здесь.
Средства печати.
Реализована возможность печати табличного документа на мобильной платформе. Поддерживаются принтеры, использующие протоколы PCL3 и ZPL. Для соединения с принтером используются WiFi и Bluetooth (только на ОС Android).Данная возможность не предоставлялась.В мобильном приложении стало возможно выполнять печать табличных документов.
Свойства конфигурации.
В документацию внесено описание режима совместимости для мобильной платформы:
  • Не управляется из Конфигуратора;
  • Не изменяется при обновлении платформы для существующей информационной базы;
  • Устанавливается при создании новой информационной базы как версия используемой мобильной платформы;
  • Изменяется (на версию используемой мобильной платформы) в случае обновления конфигурации существующей информационной базы.

Также в документации приводится соответствие версий платформы для ПК и мобильной платформы. +

Режим совместимости мобильной платформы не был описан в документации.Документация стала более актуальной.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
Средства разработки.
При разработке для мобильной платформы стало возможно использовать асинхронную схему работы с диалоговыми окнами.

Выбор значения Мобильное устройство в свойстве конфигурации Назначения использования не приводит к изменению свойства конфигурации Режим использования модальности.

При разработке для мобильной платформы можно было использовать только синхронную схему работы с диалоговыми окнами.

При выборе значения Мобильное устройство в свойстве конфигурации Назначения использования, задавался вопрос о необходимости изменения свойства конфигурации Режим использования модальности (при необходимости выполнить такое изменение).

Упрощена разработка для мобильной платформы. Прикладному разработчику больше нет необходимости поддерживать две схемы работы с диалоговыми окнами: для мобильной платформы и платформы для персонального компьютера.
В документации данное изменение описано здесь.
Встроенный язык.
При формировании имен свойств структур, создаваемых платформой, при формировании имен компонентов (элементы, реквизиты, команды, параметры) автоматически генерируемых форм мобильная платформа использует свойство конфигурации Вариант встроенного языка для корректного определения языка формирования текста.При формировании имен свойств структур, создаваемых платформой, при формировании имен компонентов (элементы, реквизиты, команды, параметры) автоматически генерируемых форм мобильная платформа использовала английский язык только в том случае, если языком конфигурации по умолчанию был английский. В остальных случаях использовался русский язык.Устранено некорректное поведение системы.

Поведение мобильной платформы унифицировано с платформой для персонального компьютера.

Средства разработки.
Реализована возможность работы с push-уведомления и локальными уведомлениями. Для работы используются сервисы Apple push notification service и Google Cloud Messaging. Реализована возможность отображать количество необработанных оповещений: у иконки мобильного приложения (на iOS) или в панели уведомлений (на Android). На устройствах под управлением ОС Android 4.1 и выше, отображение оповещений отличается от отображения опровещений на более младших версиях ОС Android. Для облегчения разработки в прикладном решении для персонального компьютера механизмов работы с оповещениями реализован специальный сервис, предоставляемый фирмой «1С». Отправитель оповещений может использовать как данный сервис, так и сервисы Apple push notification service и Google Cloud Messaging.

Для мобильной платформы реализовано свойство глобального контекста ДоставляемыеУведомления и объекты МенеджерДоставляемыхУведомлений, ДоставляемоеУведомление.

Для платформы для персонального компьютера реализовано свойство глобального контекста ОтправкаДоставляемыхУведомлений и объекты МенеджерОтправкиДоставляемыхУведомлений, ДоставляемоеУведомление.

Реализованы разрешения мобильного приложения Push-уведомления и Локальные уведомления.

Сборщик мобильных приложений поддерживает сборку мобильных приложений, работающих с уведомлениями.

Данная возможность не предоставлялась.Стало возможно пользоваться штатными возможностями оповещения пользователей на мобильных устройствах. Оповещение может формировать как мобильное приложение непосредственно на устройстве (локальные уведомления), так и прикладное решение, функционирующее на персональном компьютере (push-уведомление).
В документации данное изменение описано здесь.
Динамический список.
Оптимизировано открытие динамического списка. Загрузка данных сопровождается индикацией процесса.Загрузка данных динамического списка не сопровождалось индикацией и занимала больше времени.Оптимизировано использование динамического списка.
Работа с Интернет.
На мобильной платформе реализована поддержка безопасного соединения (HTTPS) при использовании следующих механизмов:
  • Работа по протоколу HTTP;
  • Работа с электронной почтой по протоколам POP3 и SMTP.

Реализована работа с электронной почтой по протоколу IMAP (включая защищенное соединение).

Реализована работа с клиентскими сертификатами и сертификатами удостоверяющих центров, хранящихся в файлах.

В мобильной платформе реализованы объекты СертификатКлиентаФайл, СертификатыУдостоверяющихЦентровФайл, ЗащищенноеСоединениеOpenSSL, а также соответствующие свойства объектов HTTPСоединение, ИнтернетПочтовыйПрофиль, ИнтернетПочта.

В мобильной платформе отсутствовала поддержка:
  • Безопасного соединения при работе по протоколу HTTP, POP3 и SMTP;
  • Работы с почтой по протоколу IMAP;
  • Работы с клиентскими сертификатами и сертификатами удостоверяющих центров.
На мобильной платформе реализована возможность безопасной работы с электронной почтой и другими ресурсами.
Обработка ошибок.
Для мобильной платформы разработчика реализована возможность получать подробную информацию об ошибке (кнопка Подробно в диалоге с ошибкой) и информацию для технической поддержки в форме О программе.Подробная информация об ошибке и информация для технической поддержки были недоступны на мобильной платформе.Улучшена диагностика проблемных ситуаций на мобильной платформе разработчика.
Интерфейс.
Реализован новый интерфейс клиентского приложения мобильной платформы. Новый интерфейс включает в себя большое количество изменений, среди которых можно выделить:
  • Интерфейс выдержан в едином стиле с интерфейсом Такси, но максимально учитывает специфику мобильного приложения.
  • Изменено оформление интерфейса: изменен дизайн форм, изменены основные цвета и оформление элементов форм, интерфейс стал больше соответствовать мобильным устройствам.
  • Переработано главное меню приложения.
  • Переработан командный интерфейс основного раздела.
  • Изменена схема навигации в мобильном приложении.
  • На начальной странице возможно расположение одновременно формы и командного интерфейса основного раздела.
  • Изменены правила формирования командной панели в формах и ее положение.
  • Реализовано отображение панели навигации формы.
  • Существенно переработано поле ввода с целью максимального учета особенностей работы с сенсорными экранами.
  • Заголовок формы не дублируется в самой форме.
  • Реализована возможность создания элемента из выпадающего списка во время подбора значений.
  • Реализована поддержка контекстного меню для элементов формы.
  • Не отображается отметка незаполненного.
  • Реализованы новые способы отображения группы страниц.
  • Реализован поиск в динамических списках на основе полнотекстового поиска.
  • Реализована возможность сортировки динамического списка нажатием на заголовок колонки.
  • Существенно переработана работа с таблицей, в том числе, изменены возможности прокрутки, выделения и изменения порядка строк.
  • Реализована возможность множественного выбора в таблице управляемой формы.
  • Реализована возможность обновить список попыткой потянуть список вниз или вверх при достижении первой или последней (соответственно) строки отображаемых данных (pull to refresh).
  • Изменен подход к использованию текущей строки в таблице управляемой формы.
  • Таблица управляемой формы автоматически подстраивается под отображаемые данные (по высоте), если она не отображает данные динамического списка.
  • Реализовано масштабирование табличного документа с помощью жестов.
  • Переработано отображение сообщений пользователю.
  • Реализована поддержка подсистем (в том числе в интерфейсе).
  • Реализованы поле переключателя, поле полосы регулирования.
  • Реализовано событие таблицы управляемой формы ОбработкаЗапросаОбновления. Для системного перечисления ОтображениеСтраницФормы реализовано значение Пролистывание. Для таблицы управляемой формы реализовано свойство ЗапросОбновления.
  • Удалены стандартные команды таблицы Переместить вверх/Переместить вниз.
  • Для команды управляемой формы реализованы свойства Использование текущей строки и Используемая таблица (недоступны из встроенного языка). Для кнопки управляемой формы реализовано свойство Отображение в контекстном меню (недоступно из встроенного языка).
  • Реализовано много других изменений. Так как изменений достаточно много, рекомендуется прочитать главу про разработку мобильных приложений.
Использовался интерфейс мобильного приложения, аналогичный интерфейсу версии 8.2 для управляемого приложения.Интерфейс мобильного приложения стал лучше соответствовать требованиям к интерфейсам мобильных приложений. Повышен комфорт использования мобильного приложения. Новый интерфейс выдержан в едином стиле с интерфейсом Такси, при этом максимально учитывает специфику мобильного приложения.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Управляемая форма.
Для устройств, работающих под управлением ОС Android, реализовано использование предиктивного ввода текста (с возможностью автоматической коррекции введенных слов) для многострочных полей ввода. Данная возможность используется в том случае, если она включена в настройках используемой виртуальной клавиатуры.Данная возможность не предоставлялась.Повышен комфорт использования системы для ввода текста.
Сборщик мобильных приложений.
Для сборщика мобильных приложений реализована возможность публикации собранного приложения в магазинах Apple AppStore и Google Play непосредственно из интерфейса сборщика.

Порядок действий, необходимых для подключения к Google Play, описан в справке сборщика мобильных приложений.

Данная возможность не предоставлялась.

Публикацию мобильных приложений было необходимо выполнять вручную.

Упрощена публикация мобильных приложений в магазинах Apple AppStore и Google Play.
В документации данное изменение описано здесь.
Динамический список.
Реализована возможность программной настройки динамического списка.

На мобильной платформе стало доступно свойство ДинамическийСписок.КомпоновщикНастроек.

Реализованы объекты КомпоновщикНастроекКомпоновкиДанных, ПользовательскиеНастройкиКомпоновкиДанных, НастройкиКомпоновкиДанных. Для этих объектов реализованы конструкторы и свойства. Методы объектов не доступны на мобильной платформе.

Реализован объект КоллекцияЭлементовПользовательскихНастроекКомпоновкиДанных.

Данная возможность не предоставлялась.Работа с настройками динамического списка на мобильной платформе приближена к возможностям платформы для персонального компьютера.
Динамический список.
Интерфейс.
При включенном режиме выбора в динамическом списке отображаются стрелки влево на строках, описывающих родительские группы.При включенном режиме выбора в динамическом списке не отображались стрелки влево на строках, описывающих родительские группы.Улучшена навигация в иерархическом динамическом списке, находящемся в режиме выбора.

Оглавление

Обновление используемых библиотек

Оглавление

Переход с предыдущей версии на версию 8.3.6

Оглавление

Версия 8.3.5

Версия 8.3.5 включает исправления обнаруженных ошибок и изменения в функциональности. +

Ссылки на разделы документации, которые описывают сделанные изменения в элементах данного документа, рекомендуется использовать только после публикации на сайте ИТС (http://its.1c.ru/db/v83doc) документации к текущей версии.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.4. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2 и 8.3.3. +Возможность запуска конфигураций, разработанных в версии 8.3.4 и более младших, в версии 8.3.5, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.5 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.5, при необходимости, использовать для работы с информационной базой и версию 8.3.4. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
В документации данное изменение описано здесь.
Средства разработки.
В конфигураторе изменены картинки таблиц и кубов внешних источников данных.Картинки таблиц и кубов внешних источников данных были другими.Картинки приведены к общему стилю картинок в платформе.
Средства разработки.
В конфигураторе реализован отбор объектов по фрагменту имени, синонима, комментария или представления. Отбор выполняется в следующих окнах:
  • Конфигурации;
  • Диалоге выбора объекта конфигурации;
  • Диалоге редактирования типа;
  • В окне свойств объекта.

Для объекта конфигурации Подсистема реализована возможность быстрого отбора объектов подсистемы в дереве конфигурации с помощью пункта Объекты подсистемы контекстного меню объекта.

В окне конфигурации реализована команда быстрого отбора объектов, захваченных текущим пользователем в хранилище конфигурации.

Данная возможность не предоставлялась.

Отбор был возможен только по объектам, входящим в подсистемы.

Повышен комфорт работы прикладного разработчика.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Интерфейс.
Реализована возможность программного управления составом и расположением форм на начальной странице (рабочем столе) прикладного решения.

Реализован объект СоставФормНачальнойСтраницы. Для объекта НастройкиНачальнойСтраницы реализованы методы ПолучитьСоставФорм() и УстановитьСоставФорм(), а также конструктор по умолчанию.

Вызов метода глобального контекста ОбновитьИнтерфейс() перестраивает начальную страницу (рабочий стол) в соответствии с настройками из системного хранилища настроек.

Объект НастройкиНачальнойСтраницы позволял хранить изменения настроек начальной страницы (рабочего стола) клиентского приложения относительно настроек, выполненных в конфигураторе.

Программное управление составом и расположением форм не поддерживалось.

Стало возможно программно управлять составом и расположением форм на начальной странице (рабочем столе) клиентского приложения.
В документации данное изменение описано здесь.
Средства администрирования.
Для колонки Назначение таблицы значений, возвращаемой методом ПолучитьСтруктуруХраненияБазыДанных() указаны новые назначения. Полный состав назначений таблиц базы данных приведено в описании метода ПолучитьСтруктуруХраненияБазыДанных() в Синтакс-Помощнике.Состав назначений таблиц не полностью описывал существующую схему базы данных.Уточнены назначения таблиц схемы базы данных.
Обмен данными.
Для плана обмена реализован стандартный реквизит ЭтотУзел. Реквизит содержит признак того, что узел плана обмена описывает текущую информационную базу.

Для объекта ПланОбменаОбъект реализовано свойство ОбменДанными. Для использования в данном свойстве доступно только свойство Загрузка. Данное свойство используется для отключения проверки уникальности элемента ЭтотУзел при редактировании или удалении элементов плана обмена.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Стандартный реквизит ЭтотУзел отсутствовал. Поменять узел плана обмена, описывающий текущую информационную базу, было невозможно.

У объекта ПланОбменаОбъект отсутствовало свойство ОбменДанными.

Стало возможно определять элементы ЭтотУзел в разделенной информационной базе из сеанса, в котором не используются разделители.

Стало возможно указывать другой элемент данных, который описывает текущую информационную базу в плане обмена.

В документации данное изменение описано здесь и здесь.
Управляемая форма.
Для поля ввода управляемой формы реализовано событие ИзменениеТекстаРедактирования. Данное событие вызывается при изменении текста в поле ввода, которое вызвано одним из следующих действий:
  • Набор текста в поле ввода;
  • Работа с буфером обмена;
  • Использование команд Отменить/Вернуть;
  • Отмена ввода (нажатие клавиши ESC).

Событие вызывается перед событием АвтоПодбор. +

В системе отсутствовало событие, которое вызывалось при изменении текста в поле ввода. Действия, которые выполняются при таком изменении, можно было с ограничениями выполнять в обработчике АвтоПодбор.В управляемой форме стало возможным полноценно реализовать следующий сценарий: в поле ввода вводится какой-либо текст, который применяется для установки отбора в связанном динамическом списке.
Средства разработки.
В редакторе модулей реализованы следующие возможности:
  • Поиск во всей конфигурации мест использования экспортной переменной, процедуры или функции;
  • Преобразование выделенного фрагмента кода в отдельную процедуру или функцию;
  • Переименование локальной переменной, процедуры или функции;
  • Создание перед определением процедуры или функции блока комментариев с описанием назначения, параметров и возвращаемого значения;
  • Преобразование модального вызова в немодальный аналог в ограниченном наборе случаев;
  • Преобразование процедуры или функцию к виду, позволяющему участие в последовательности асинхронных вызовов;
  • Преобразование выделенного фрагмента кода в отдельную процедуру или функцию, которую можно использовать в последовательности асинхронных вызовов;
  • Поиск всех мест использования модальных методов в данном модуле;
  • Преобразование всех найденных модальных методов в их асинхронные аналоги;
  • Создание обработки оповещения для блокирующих методов.

Команды, выполняющие эти функции, сгруппированы в подменю Рефакторинг конктектного меню редактора текстов модуля и меню Конфигурация главного меню конфигуратора.

Данные возможности не предоставлялась.Повышение эффективности труда прикладных разработчиков при выполнении некоторых рутинных операций.
В документации данное изменение описано здесь и здесь.
Управляемая форма.
Для поля ввода, которое отображает значение типа СтандартнаяДатаНачала в режиме ввода даты, реализован вызов обработчиков событий АвтоПодбор (при вводе значения) и ОкончаниеВводаТекста (при формировании значения по введенной строке).

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Для поля ввода, которое отображает значение типа СтандартнаяДатаНачала в режиме ввода даты, не выполнялся вызов обработчиков событий АвтоПодбор и ОкончаниеВводаТекста.Поведение поля ввода, связанного со значением типа СтандартнаяДатаНачала в режиме ввода даты, приведено в соответствие с полем ввода, связанным со значением типа Дата.
Клиентское приложение.
Реализована возможность запуска клиентского приложения с последующим переходом по навигационной ссылке, переданной в качестве параметра. Данная возможность реализована для программы запуска, тонкого и толстого клиентских приложений, метода ПерейтиПоНавигационнойСсылке(), стандартной формы полнотекстового поиска и с помощью специальной команды (Перейти по ссылке) в интерактивной программе запуска. Переход осуществляется только по внешней навигационной ссылке (содержащей в себе параметры подключения к информационной базе). При переходе система пытается использовать запущенные экземпляры клиентских приложений, работающих с той же информационной базой, что и в передаваемой навигационной ссылке. В режиме совместимости с версией 8.3.4 поведение метода ПерейтиПоНавигационнойСсылке() не изменилось.

Реализован параметр запуска /url для программы запуска, тонкого и толстого клиентских приложений.

Данная возможность не предоставлялась.

Существовала возможность выполнить переход по внешней ссылке в том случае, если к информационной базе предоставлялся доступ с помощью веб-клиента.

Упрощен доступ к данным информационной базы в том случае, если ссылка на данные стала доступна с помощью сторонних средств, например, электронной почты.
В документации данное изменение описано здесь и здесь.
Работа с Интернет.
Для объекта ИнтернетПочтовоеСообщение реализованы методы ПолучитьИсходныеДанные(), УстановитьИсходныеДанные(), ПолучитьИсходныйТекст(). Данные методы позволяют получить оригинальное почтовое сообщение без перекодировок, а также работать с исходным текстом почтового сообщения в виде текста, преобразованного к одной кодировке.Данная возможность не предоставлялась.Стало возможно сохранять почтовые сообщения в файл и загружать их обратно, при условии, что загружаемое сообщение соответствует RFC 822 (см. здесь), а также произвольным образом обрабатывать исходный текст почтового сообщения.
Отображение информации.
Диаграммы.
Реализована возможность выводить анимированные диаграммы. Для объекта Диаграмма реализовано свойство Анимация. Реализован объект НастройкаОтображенияДиаграмм. Настройка отображения диаграмм сохраняется в хранилище системных настроек.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Данная возможность не предоставлялась.Повышены изобразительные возможности диаграмм.
Web-сервисы и HTTP-сервисы.
Обмен данными.
Работа с базой данных.
Средства публикации веб-клиента и Web-сервисов.
Реализована возможность получения и модификации данных информационной базы «1С:Предприятия» с помощью протокола OData (см. здесь) v3 (см. здесь). Поддерживается представление данных: atom-xml.

Включение данной возможности не требует модификации прикладного решения и выполняется с помощью специальной публикации на веб-сервере.

Реализован атрибут enableStandardOData для тега <point> файла default.vrd.

В режиме совместимости с версией 8.3.4 с помощью интерфейса OData доступны все объекты конфигурации, поддерживаемые данным механизмом. При отключенном режиме совместимости доступ к объектам регулируется с помощью метода УстановитьСоставСтандартногоИнтерфейсаOData().

Универсальный доступ к данным информационной базы «1С:Предприятия» был доступен только в ОС Windows с помощью механизмов COM/OLE. В ОС Linux данная возможность была недоступна.

Также имелась возможность получать доступ к данным с помощью Web-сервисов, которые требовалось реализовать в прикладном решении.

Расширены возможности интеграции с данными «1С:Предприятия», в том числе стало возможно получать доступ к данным, без изменения прикладного решения, из внешней системы на ОС Linux.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Хранилище конфигурации.
Оптимизировано выборочное сравнение форм, прав доступа и фрагментов командного интерфейса в тех случаях, когда хранилище конфигурации расположено на сетевом диске или при работе через сервер хранилища.

Реализован локальный кеш данных хранилища конфигурации. Реализована возможность управлять размещением и размером локального и глобального кеша данных хранилища конфигурации с помощью диалога администрирования хранилища конфигурации, а также с помощью конфигурационных файлов cfgrepo.conf, расположенных в папке cfgrepo каталога служебных файлов информационной базы (локальный кеш) или в каталоге хранилища конфигурации (глобальный кеш).

Для пакетного режима запуска конфигуратора реализованы следующие возможности:

  • Очистка глобального кеша данных хранилища конфигурации (ключ командной строки запуска /ConfigurationRepositoryClearGlobalCache);
  • Очистка локального кеша данных хранилища конфигурации (ключ командной строки запуска /ConfigurationRepositoryClearLocalCache).
Выборочное сравнение форм, прав доступа и фрагментов командного интерфейса выполнялось недостаточно быстро в тех случаях, когда хранилище конфигурации расположено на сетевом диске или при работе через сервер хранилища.

Было невозможно управлять расположением и размером глобального кеша данных хранилища конфигурации. Локальный кеш данных хранилища конфигурации отсутствовал.

Ускорены операции выборочного сравнения и некоторые другие операции при работе с хранилищем конфигурации.

Стало возможно управлять расположением и объемом кеша данных хранилища конфигурации.

В документации данное изменение описано здесь, здесь и здесь.
Динамический список.
Расширены возможности поиска в таблице, отображающей динамический список. Реализован полнотекстовый поиск при помощи «строки поиска». Реализована возможность искать по текущему значению ячейки. Реализована история поиска. Реализовано наглядное представление текущего состояния поиска в таблице. Результаты поиска по разным колонкам складываются. В одной колонке поддерживается поиск только одного значения (не поддерживается флажок Искать в найденном).

Для автоматически созданных форм, в которых присутствует таблица, связанная с динамическим списком, изменен набор элементов (и их внешний вид) отвечающий за поиск данных в динамическом списке. Изменен внешний вид диалога поиска.

Реализован элемент управляемой формы ДополнениеЭлементаФормы, предназначенный для отображения дополнительных свойств элементов форм.

Реализованы расширения дополнения элемента формы для отображения строки поиска, состояния просмотра, управления поиском.

Для элемента управляемой формы ТаблицаФормы реализованы предопределенные элементы СтрокаПоиска, СостояниеПросмотра, УправлениеПоиском, а также свойства ПоложениеСтрокиПоиска, ПоложениеСостоянияПросмотра, ПоложениеУправленияПоиском.

История поиска хранится в хранилище системных настроек с ключом Общее/ИсторияПоискаТаблицы/<Имя формы>.<Имя таблицы>.

В библиотеке картинок реализована картинка УправлениеПоиском.

Поиск в таблице осуществляется с использованием диалога поиска. Имелась возможность выполнять поиск в одной колонке более чем по одному значению (флажок Искать в найденном). Диалог поиска имел другой внешний вид. Отсутствовал простой способ определения того, что в таблице используется поиск (только с помощью доступности кнопки Отмена поиска, если она присутствует в командной панели).Улучшен поиск в таблицах управляемых форм, включая наглядное представление того, что в таблице используется поиск.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Web-сервисы и HTTP-сервисы.
Реализована возможность прикладному разработчику создавать HTTP-сервисы в прикладном решении. Прикладной разработчик получает доступ к телу, заголовкам и строке HTTP-запроса.

Публикация HTTP-сервиса выполняется аналогично публикации Web-сервисов.

Для доступа к HTTP-сервису используется URL следующего вида: http://<имя хоста>/<имя базы>/hs/<идентификатор ресурса>. +Создание HTTP-сервисов возможно в ветке Общие - HTTP-сервисы дерева объектов конфигурации.

Реализованы объекты HTTPСервисы, HTTPСервис, HTTPСервисЗапрос, HTTPСервисОтвет.

Данная возможность не предоставлялась.

Предоставлялась только возможность обращения к Web-сервисам, которые реализованы в прикладном решении.

Стало возможно реализовывать сервисы, которые, по сравнению с Web-сервисами:
  • Более просты в реализации;
  • Обладают меньшим объемом передаваемых данных;
  • При разборе ответа требуется меньшая вычислительная мощность;
  • Предлагают другую модель использования (RESTful-сервисы).

+

В документации данное изменение описано здесь, здесь, здесь, здесь и здесь.
Клиентское приложение.
Работа с базой данных.
Для сеанса реализовано состояние Спящий, что позволяет сохранять сеанс при нештатном разрыве соединения с клиентским компьютером. В этом состоянии сеанс освобождает занятую лицензию (если таковая была получена). При назначении спящему сеансу соединения - сеанс автоматически лишается статуса Спящий. При «пробуждении» происходит попытка получения лицензии (если она требуется). При невозможности получения лицензии сеанс завершается аварийно. Реализована возможность автоматического завершения «спящего» сеанса при превышении временного порога. При разрыве клиентского соединения на сервере «1С:Предприятия» сеанс не завершается, а переходит в «спящее» состояние.

Для объекта ISessionInfo реализованы свойства Hibernate, PassiveSessionHibernateTime, HibernateSessionTerminateTime. Реализованы методы глобального контекста УстановитьВремяЗасыпанияПассивногоСеанса(), ПолучитьВремяЗасыпанияПассивногоСеанса(), УстановитьВремяЗавершенияСпящегоСеанса(), ПолучитьВремяЗавершенияСпящегоСеанса().

Настройки времени засыпания сеанса и времени завершения спящего сеанса доступны с помощью диалога настройки параметров информационной базы в конфигураторе.

Данная возможность не предоставлялась.

Если клиентское приложение не проявляло активности в течении 20 минут, сеанс завершался.

В некоторых случаях стало возможно продолжение работы клиентского приложения после перехода клиентского компьютера в «спящий» режим на продолжительное время.

+

В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Для выполнения операции сравнения строковых значений в системе компоновки данных реализованы новые виды сравнений: НачинаетсяС, НеНачинаетсяС, Подобно, НеПодобно. Виды сравнения Подобно и НеПодобно имеют следующие представления:
  • Подобно - Соответствует шаблону;
  • НеПодобно - Не соответствует шаблону.
Данная возможность не предоставлялась.Расширены возможности отбора по строковым выражениям в отчетах (построенных с помощью системы компоновки данных) и динамических списках.
В документации данное изменение описано здесь.
Объекты конфигурации.
Для объектов конфигурации справочник, план видов характеристик, план счетов, план видов расчетов реализован метод ПолучитьИменаПредопределенных().Данная возможность не предоставлялась.Стало возможно получать признак наличия у объекта конфигурации предопределенных элементов и полный список имен этих элементов. С помощью такого списка можно проверять, что для всех предопределенных элементов есть элементы данных.
В документации данное изменение описано здесь.
Внешние источники данных.
Реализована возможность записи данных в таблицы внешних источников данных.

Данная возможность реализована для решения задач интеграции с другими приложениями и не должна использоваться для замены хранения данных прикладного решения.

Данная возможность не предоставлялась.

Можно было выполнять только операции чтения данных из таблиц внешнего источника данных.

Расширены возможности интеграции с существующими системами и базами данных.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Работа с запросами.
Реализован конструктор запросов для работы в управляемом режиме. Для объекта КонструкторЗапроса реализован метод Показать().

В библиотеку картинок добавлены картинки

Переименовать, Реквизит, Измерение, Ресурс, ВложеннаяТаблица, КонструкторЗапросаОтображатьТаблицыИзменений, КонструкторЗапросаСоздатьВложенныйЗапрос, КонструкторЗапросаСоздатьОписаниеВременнойТаблицы, КонструкторЗапросаЗаменитьТаблицу, КонструкторЗапросаПараметрыТаблицы, КонструкторЗапросаСоздатьЗапросУничтоженияВременнойТаблицы

КонструкторЗапросаОписаниеВременнойТаблицы, КонструкторЗапросаГруппаВременныхТаблиц, КонструкторЗапросаВременнаяТаблица, КонструкторЗапросаВложенныйЗапрос, ПроизвольноеВыражение.

Данная возможность не предоставлялась.Расширены возможности при работе с запросами в управляемом приложении.
В документации данное изменение описано здесь.
Работа с запросами.
Реализована объектная модель для работы с текстом запроса. Реализован объект СхемаЗапроса.Данная возможность не предоставлялась.Стало возможно модернизировать запрос из встроенного языка без анализа текста запроса.
В документации данное изменение описано здесь.
Табличный документ.
Реализована возможность размещать в ячейках табличного документа картинки. Реализована возможность управлять относительным расположением текста относительно картинки в ячейке (области ячеек) табличного документа. Картинка «привязана» к ячейке, в которую она вставлена.

Для объекта ОбластьЯчеекТабличногоДокумента реализованы свойства Картинка, РазмерКартинки, ГоризонтальноеПоложениеКартинки, ВертикальноеПоложениеКартинки, ПоложениеТекстаОтносительноКартинки, ПараметрКартинки.

Картинку можно было вставить в табличный документ только как рисунок, не привязанный к конкретной ячейке (области ячеек).Работать с картинками в табличном документе стало более удобно.
Системные требования.
Реализована поддержка дистрибутива Alt Linux СПТ 6.0.Данный дистрибутив не поддерживался.Расширен список поддерживаемых дистрибутивов ОС Linux.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Для объекта ОтборКомпоновкиДанных реализован конструктор по умолчанию.Данная возможность не предоставлялась.В мобильном приложении данная возможность используется для установки отбора в списке контактов.
Журнал регистрации.
Реализовано событие _$Data$_.TotalsMaxPeriodUpdate, имеющее представление Данные. Изменение максимального периода рассчитанных итогов. Событие регистрируется при вызове методов УстановитьМаксимальныйПериодРассчитанныхИтогов() и УстановитьМинимальныйИМаксимальныйПериодыРассчитанныхИтогов().

Событие _$Data$_.TotalsPeriodUpdate используется для совместимости.

При установке максимального периода рассчитанных итогов регистрировалось событие _$Data$_.TotalsPeriodUpdate.Журнал регистрации стал более корректно отображать действия по изменению периода рассчитанных итогов.
Работа в ОС Linux.
Клиентское приложение.
Реализован поиск библиотеки ImageMagick по имени libMagickWand-6.Q16.Поиск библиотека ImageMagick по имени libMagickWand-6.Q16 не выполнялся.При запуске «1С:Предприятия» не происходит аварийного завершения работы системы, если в системе установлена библиотека ImageMagick после переименования библиотеки.
В документации данное изменение описано здесь и здесь.
Работа с СУБД.
Реализована возможность работы с СУБД Microsoft SQL Server 2014.СУБД Microsoft SQL Server 2014 не поддерживалась.Реализована поддержка новой версии СУБД компании Microsoft.
В документации данное изменение описано здесь, здесь, здесь, здесь, здесь и здесь.
Инструменты разработчика.
Для внешних обработок (поставляются на ИТС) редактирования файла настройки технологического журнала (см. здесь) и преобразования журнала действий пользователя (см. здесь) реализован английский интерфейс. Указанные обработки переписаны на английском варианте встроенного языка.Обработки редактирования файла настройки технологического журнала и преобразования журнала действий пользователя обладали только русским интерфейсом. Указанные обработки были написаны на русском варианте встроенного языка.Упрощено использование и доработка обработок редактирования файла настройки технологического журнала и преобразования журнала действий пользователя для не русскоговорящих прикладных разработчиков.
Средства разработки.
При выгрузке файлов конфигурации изменен подход к выгрузке информации о стандартных реквизитах. Выгружаются только те реквизиты, свойства которых отличаются от значений по умолчанию (для данного реквизита). Изменение свойств одного стандартного реквизита приводит к выгрузке всех стандартных реквизитов объекта конфигурации. При загрузке поведение не изменяется: если в xml-файле присутствует описание стандартного реквизита - эта информация загружается в конфигурацию, даже если описание стандартного реквизита полностью соответствует значениям по умолчанию.

Реализована внешняя обработка, предназначенная для удаления из xml-файлов, сформированных с помощью механизма выгрузки файлов конфигурации, информации о стандартных реквизитах объектов, которые не изменялись относительно значений по умолчанию. Обработка может использоваться только с файлами, выгруженными версией 8.3.5 и должна применяться один раз, перед обратной загрузкой файлов выгрузки конфигурации.

При выгрузке файлов конфигурации информация о стандартных реквизитах выгружалась всегда, вне зависимости от того, отличаются свойства стандартных реквизитов от значений по умолчанию или нет.Уменьшается размер файла конфигурации и уменьшается количество «разных» объектов при операции сравнения конфигураций после выполнения пары операций выгрузки/загрузки файлов конфигурации.
Предопределенные данные.
Прикладные объекты.
Общие реквизиты / Разделение данных.
Реализована возможность управления признаком инициализированности предопределенных данных в информационной базе/области данных. Реализованы методы УстановитьИнициализациюПредопределенныхДанных() и ПолучитьИнициализациюПредопределенныхДанных() для менеджеров справочников, планов видов характеристик, планов счетов и планов видов расчетов.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Отсутствовала возможность управления признаком инициализированности предопределенных данных в информационной базе/области данных.Расширены возможности работы с предопределенными данными. Стало возможно в любой момент времени указать системе, что предопределенные данные в информационной базе/области данных инициализированы или нет, при отключении информационной базы от распределенной информационной базы стало возможно указать, что в отключаемой базе все предопределенные данные созданы.
Системные требования.
Реализована поддержка работы «1С:Предприятия» под управлением ОС Microsoft Windows Server 2012 R2 (x86-64).Не поддерживалась работа «1С:Предприятия» под управлением ОС Microsoft Windows Server 2012 R2 (x86-64).Реализована поддержка новой версии ОС компании Microsoft.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Кластер серверов.
Средства администрирования.
Реализована возможность использовать для формирования дампов аварийного завершения внешнюю утилиту.

Реализован атрибут externaldump элемента dump файла logcfg.xml. Реализована утилита dumper.exe, входящая в комплект поставки платформы.

Дамп аварийного завершения всегда формировался тем процессом, который завершается аварийно.Исключены случаи зависания системы при формировании дампа аварийного завершения.
В документации данное изменение описано здесь.
Обмен данными.
В документации приведены инструкции по отключению информационной базы от центрального узла и по восстановлению конфигурации в узле распределенной информационной базы, учитывающие особенности использования предопределенных данных.Данная информация отсутствовала в документации.В документации отражена рекомендации по совместному использования распределенной информационной базы и предопределенных данных.
В документации данное изменение описано здесь.
Клиентское приложение.
Управляемая форма.
В тонком и толстом клиентских приложениях изменена реакция системы на свойство конфигурации Режим использования модальности. Реализован параметр запуска тонкого и толстого клиентского приложения EnableCheckModal.

Без использования параметра EnableCheckModal модальные методы исполняются штатным образом, без выдачи предупреждений и исключений.

С использованием параметра EnableCheckModal при использовании модальных методов формируется предупреждение или исключение (в зависимости от значения свойства конфигурации Режим использования модальности).

При запуске прикладного решения из конфигуратора параметр EnableCheckModal автоматически добавляется в строку запуска прикладного решения (без возможности отключить данное поведение).

В веб-клиенте поведение не меняется, параметр командной строки запуска не используется. Веб-клиент всегда формирует предупреждение или исключение (в зависимости от значения свойства конфигурации Режим использования модальности) при использовании модальных методов.

Поведение модальных методов зависело только от значения свойства конфигурации Режим использования модальности. В зависимости от значения этого свойства модальные методы исполнялись штатным образом, при их использовании формировались предупреждения или исключения. Изменить поведение с помощью параметра командной строки запуска было невозможно.Для прикладных решений, реализованных без использования модальности, реализована возможность использования внешних обработок, которые написаны с применением модальных методов.
В документации данное изменение описано здесь и здесь.
Системные требования.
Реализована поддержка операционной системы Microsoft Windows 8.x.Операционная система Microsoft Windows 8.x не поддерживалась.Расширен список поддерживаемых операционных систем.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Установка клиентского приложения.
При обновлении клиентского приложения через Интернет выводится диалог, отображающий процесс скачивания дистрибутива с соответствующего сервера. Во время скачивания имеется возможность отказаться от скачивания.При скачивании дистрибутива клиентского приложения не выполнялось отображение процесса скачивания.Обновлении дистрибутива клиентского приложения с помощью интернет-сервисов стало более комфортным: нет ощущения зависания системы, можно отказаться от скачивания.
Клиентское приложение.
Окно Справка открывается аналогично любой другой форме:
  • В режиме В отдельных окнах - в отдельном окне;
  • В режиме В закладках - в закладке;
  • В режиме Такси - в рабочей области основного окна;
  • Открытие справки из формы, блокирующей весь интерфейс, осуществляется поверх всех окон, блокируя весь интерфейс;
  • Открытие справки из формы, открытой модально, осуществляется в модальной форме.

Изменена командная панель справки.

Поиск запускается или при сходе с поля ввода поискового запроса или при нажатии на кнопку Найти. +

Окно Справка всегда открывалось отдельным окном, вне зависимости от настроек внешнего вида основного окна приложения.

Командная панель справки имела другой состав.

Поиск начинался во время набора поискового выражения (во время тайм-аута в наборе).

Поведение окна Справка приведено в соответствие с остальными формами системы.
Установка прикладного решения.
Программа установки прикладных решений использует новый вариант заставки.Программа установки прикладных решений использовала старый вариант заставки.Программы установки прикладного решения и платформы приведены к единому внешнему виду.
Клиентское приложение.
Если для информационной базы настроена OpenID-аутентификация, то после запуска тонкого клиента и выбора этой информационной базы, в диалоге аутентификации отображается имя пользователя, который был успешно аутентифицирован в этой базе при предыдущем запуске.В диалоге OpenID-аутентификации поле, предназначенное для ввода имени пользователя, всегда было пустым.Унифицированы различные способы аутентификации в части запоминания имени пользователя.
Предопределенные данные.
При интерактивной пометке на удаление, снятии пометки удаления и удалении группы в справочнике, плане видов характеристик и плане счетов, реализована проверка прав доступа для подчиненных предопределенных объектов.При интерактивной пометке на удаление, снятии пометки удаления и удалении группы в справочнике, плане видов характеристик и плане счетов, не выполнялась проверка проверка прав доступа для подчиненных предопределенных объектов.Стало невозможно удалить группу (для справочника, плана видов характеристик и плана счетов), если в состав группы входит предопределенный элемент, для которого у текущего пользователя отсутствует право на интерактивное действие.
Веб-клиент.
При запуске веб-клиента с помощью веб-браузера Google Chrome под управлением операционной системы MacOS X, отключена выдача сообщения о том, что веб-браузер не поддерживается.При запуске веб-клиента с помощью веб-браузера Google Chrome под управлением операционной системы MacOS X выдавалось предупреждение о неподдерживаемом веб-браузере.Для пользователей, которые работают с системой «1С:Предприятие» на MacOS X в веб-браузере Google Chrome, предоставлена возможность более удобного входа (без сообщения). Вопрос о поддержке данного варианта будет решаться отдельно.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Общие реквизиты / Разделение данных.
Файловый вариант.
Оптимизировано выполнение запросов при работе в файловом варианте разделенной информационной базы.Выполнение запросов при работе в файловом варианте разделенной информационной базы было недостаточно эффективным.Повышена производительность при работе с разделенной информационной базой в файловом варианте.
Управляемая форма.
Ускорено открытие форм в некоторых ситуациях.Формы открывались недостаточно быстро.Повышена скорость работы системы в некоторых случаях.
Работа с базой данных.
Увеличилась скорость подключения к файловому варианту информационной базы, расположенной на сетевом ресурсе.Скорость подключения к файловому варианту информационной базы, расположенной на сетевом ресурсе, была не достаточной.Ускорилось подключение к файловому варианту информационной базы, расположенной на сетевом ресурсе, для второго и последующих пользователей.
Встроенный язык.
Повышена скорость выполнения методов встроенного языка и получения свойств объектов конфигурации.Скорость выполнения методов встроенного языка и получения свойств объектов конфигурации была недостаточно высокой.Повышена скорость выполнения методов встроенного языка и получения свойств объектов конфигурации.
Регистры бухгалтерии.
Ускорена запись в регистр бухгалтерии, если в наборе записей содержится не более 10 записей.При записи в регистр бухгалтерии наборов записей, с количеством записей не более 10, скорость записи была недостаточной.Ускорена работа с регистром бухгалтерии.
Работа с СУБД.
Регистры бухгалтерии.
Общие реквизиты / Разделение данных.
При работе в клиент-серверном варианте, с использованием СУБД IBM DB2 или Oracle Database, ускорена запись в регистр бухгалтерии, если регистр входит в состав общего реквизита, являющегося разделителем.Запись в регистр бухгалтерии, входящего в состав разделителя, выполнялась недостаточно быстро при работе в клиент-серверном варианте, с использованием СУБД IBM DB2 или Oracle Database.Ускорена работа с регистром бухгалтерии при работе в клиент-серверном варианте (с использованием СУБД IDB DB2 или Oracle Database).

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Определяемые типы.
Существенно расширен набор типов, которые могу входить в состав определяемого типа.

Использование определяемых типов стало возможно в следующих объектах: общие команды, регистры расчета, подписки на события, внешние источники данных, общие реквизиты, являющиеся разделителями.

Изменен алгоритм проверки конфигурации на корректность использования определяемых типов: определяемый тип считается допустимым (в каждом конкретном месте), если допустимы все типы входящие в состав определяемого типа в момент проверки. В режиме совместимости с версией 8.3.4 режим проверки конфигурации не изменился.

Набор типов, который мог входить в состав определяемого типа, был существенно меньше.

При проверке конфигурации выполнялась проверка того, что в состав определяемого типа входил допустимый набор типов, и что определяемый тип не входит в состав следующих объектов: общие команды, регистры расчета, подписки на события, внешние источники данных, общие реквизиты, являющиеся разделителями.

Расширены возможности использования определяемых типов в прикладных решениях. В частности, стала более простой интеграция прикладных решений со сторонними подсистемами.
В документации данное изменение описано здесь.
Средства разработки.
Изменен порядок следования стандартных реквизитов в окне отображения стандартных реквизитов и в настройках ролей.

Конструктор формы предоставляет возможность размещения на форме поля, отображающего имя предопределенных данных.

Порядок следования стандартных реквизитов в окне отображения стандартных реквизитов и в настройках ролей был произвольным.

Конструктор форм не предоставлял возможности размещения на форме поля, отображающего имя предопределенных данных.

Отображение стандартных реквизитов приведено в соответствие с аналогичными механизмами системы.
Клиентское приложение.
Выполнение команды Сохранить как для текстового документа сохраняет кодировку, в которой открыт текстовый документ, если при открытии указана одна из 4 кодировок: ANSI, OEM, UTF-8, UTF-16. В противном случае устанавливается кодировка UTF-8.

Выход из диалога Сохранить как с отказом от выполняемого действия не меняет кодировку открытого текстового документа.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

При попытке выполнить команду Сохранить как, система всегда подставляла в качестве кодировки создаваемого документа UTF-8, вне зависимости от того, какая кодировка была установлена при открытии документа.

Выход из диалога Сохранить как с отказом от выполняемого действия приводил к установке для текстового документа кодировки UTF-8.

Устранено незапланированное поведение системы.
Управляемая форма.
В диалоге Настройка формы невозможно добавить на форму поле ВерсияДанных.В диалоге Настройка формы имелась возможность добавления на форму поля ВерсияДанных.Устранено незапланированное поведение системы.
Фоновые и регламентные задания.
При запуске фонового задания вызов обработчика события УстановкаПараметровСеанса выполняется после выполнения служебных действий (запись в журнал регистрации, установка параметров соединения с внешними источниками данных и т.д.).При запуске фонового задания вызов обработчика события УстановкаПараметровСеанса выполнялся до выполнения служебных действий (запись в журнал регистрации, установка параметров соединения с внешними источниками данных и т.д.). Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Общие реквизиты / Разделение данных.
Регистры сведений.
Регистры накопления.
Регистры бухгалтерии.
Регистры расчета.
При проверке конфигурации и при обновлении конфигурации выполняется проверка того, что регистры, влияющие на последовательность, входят в состав тех же разделителей, что и документы, входящие в последовательность.

Если влияющий на последовательность регистр включен в состав разделителя, а входящий в последовательность документ не включен в состав этого разделителя, то при обновлении границ последовательности, в режиме «1С:Предприятия», такие разделители игнорируются.

Не выполнялся контроль соответствия разделителей входящих в последовательность документов и регистров, влияющих на эту последовательность.Устранено незапланированное поведение системы.
Временное хранилище.
Объем данных, перемещаемых между клиентом и сервером, не должен превышать 4 Gb (в сериализованном виде) в следующих случаях:
  • Установка параметра сеанса;
  • Один вызов метода ПоместитьВоВременноеХранилище();
  • Один вызов метода ПоместитьФайл() или ПоместитьФайлы().

Попытка передать более 4 Gb приведет к возникновению невосстановимой ошибки.

Попытка помещения на сервер данных, объемом превышающих 4 Gb (в сериализованном виде), заканчивалась зависанием клиентского приложения.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с Интернет.
Библиотека сURL обновлена до версии 7.32. В результате стало возможно, в частности, получать файлы с кириллическими именами с ftp-серверов.Использовалась библиотека сURL версии 7.18.2.Решены некоторые проблемы, возникавшие при использовании старой версии библиотеки.
Работа с XML, XDTO.
При возникновении на стороне сервера ошибки, связанной с попыткой записи в XML недопустимого символа, на стороне клиентского приложения не будет генерироваться невосстановимой ошибки с предложением завершить работу клиентского приложения.

Данная ошибка может быть перехвачена конструкцией Попытка...Исключение.

При возникновении на сервере ошибки, связанной с попыткой записи в XML недопустимого символа, на стороне клиентского приложения генерировалась невосстановимая ошибка с предложением завершить работу клиентского приложения.Устранено незапланированное поведение системы.
Работа с XML, XDTO.
В случае обнаружения методом НайтиНедопустимыеСимволыXML() незавершенной суррогатной пары Unicode, возвращается позиция первого символа незавершенной суррогатной пары.В случае обнаружения методом НайтиНедопустимыеСимволыXML() незавершенной суррогатной пары Unicode, возвращалась позиция символа, следующего за первым символом незавершенной суррогатной пары.Устранено незапланированное поведение системы.
Управляемая форма.
Поле ввода, которое находится в режиме выбора из списка и отображает пустую ссылку, игнорирует нажатие кнопки Открыть.Поле ввода, которое находится в режиме выбора из списка и отображает пустую ссылку, при нажатии кнопки Открыть отображало диалог с текстом Неопределено.Устранено незапланированное поведение системы.
Навигационные ссылки.
При переходе по навигационной ссылке игнорируются пробельные символы (пробелы, переводы строки и т.д.) в начале и конце навигационной ссылки. Данное поведение реализовано для:
  • метода встроенного языка ПерейтиПоНавигационнойСсылке();
  • при переходе по навигационной ссылке из диалога перехода по навигационной ссылке (включая вставку текста из буфера обмена в данный диалог);
  • помещение в Избранное из диалога перехода по навигационной ссылке.
При переходе по навигационной ссылке пробельные символы (пробелы, переводы строки и т.д.) в начале и конце навигационной ссылки не игнорировались, а считались составной частью навигационной ссылки. Их было необходимо удалять вручную.Улучшена работа с навигационными ссылками.
Работа с XML, XDTO.
Web-сервисы.
При чтении строковых значений с помощью объекта ЧтениеXML или при получении с помощью Web-сервиса, символы перевода строк сохраняются в оригинальном виде и не конвертируются.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

При чтении строковых значений с помощью объекта ЧтениеXML или при получении с помощью Web-сервиса, происходила следующая замена:
  • Сочетания символов перевода строк 0x0D+0x0A (ВК+ПС) и 0x0D (ВК) заменялись на символ 0x0A (ПС);
  • Сочетание символов 0x0A+0x0D (ПС+ВК) заменялась на символы 0x0A+0x0A (ПС+ПС).

+

Устранено незапланированное поведение системы.
Табличный документ.
Работа с XML, XDTO.
Реализована XDTO-сериализация настроек поля ввода, расположенного в табличном документе. Благодаря этому табличный документ, десериализованный из XDTO, будет эквивалентен своему источнику.При XDTO-сериализации и последующей десериализации терялись настройки поля ввода, расположенного в табличном документе.После выполнения операции выгрузки/загрузки конфигурации в/из XML, сохраняются настройки полей ввода, которые располагаются в табличном документе.
Средства разработки.
В диалоге Вычислить выражение и в Табло не выполняется повторное вычисление выражения в следующих случаях:
  • Раскрытие значения, которое имеет свойства;
  • Просмотр какого-либо свойства как коллекции значений в отдельном окне;
  • Просмотр значения свойства из отдельного окна просмотра коллекции;
  • Просмотр строкового значения в отдельном окне.
В диалоге Вычислить выражение и в Табло выполнялось повторное вычисление выражения в следующих случаях:
  • Раскрытие значения, которое имеет свойства;
  • Просмотр какого-либо свойства как коллекции значений в отдельном окне;
  • Просмотр значения свойства из отдельного окна просмотра коллекции;
  • Просмотр строкового значения в отдельном окне.
Ликвидирована ситуация искажения результатов просмотра выражения в том случае, когда успешное вычисление выражения возможно (на текущем шаге отладки) только один раз.
Хранилище конфигурации.
Реализована возможность выборочного сравнения модулей форм без построения отчета по форме. Реализована команда Форма (модуль) для выпадающих меню Сравнить выборочно с объектом хранилища, Сравнить выборочно с объектом конфигурации и Сравнить выборочно версии объекта.При выборочном сравнении формы выполнялось два сравнения: модуля формы и самой формы. В результате выполнения команды выводилось два отчета.Механизм выборочного сравнения стал более удобным. Часто используемый механизм (сравнение модулей форм) выделен в отдельную команду.
В документации данное изменение описано здесь.
Система компоновки данных.
Автоматический заголовок поля системы компоновки данных, связанного с данными, получаемыми «через точку» от поля Ссылка табличной части, содержит только представление самого поля. Таким образом, заголовком поля, связанного с реквизитом ТабличнаяЧасть.Ссылка.Номер будет выступать текст Номер.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Автоматический заголовок поля системы компоновки данных, связанного с данными, получаемыми «через точку» от поля Ссылка табличной части, содержало слово Ссылка и представление реквизита данных «через точку».Улучшен внешний вид отчетов.
Управляемая форма.
Пессимистическая блокировка данных, описываемых основным реквизитом формы, выполняется в следующих случаях:
  • При нажатии кнопки открытия выпадающего списка в поле ввода;
  • При попытке создания нового элемента из выпадающего списка в поле ввода;
  • При попытке открыть список выбора из поля ввода;
  • При начале ввода текста в поле ввода.

Если блокировку установить не получилось - действие не выполняется.

Пессимистическая блокировка устанавливалась при выполнении в поле ввода следующих действий:
  • При попытке открыть список выбора из поля ввода;
  • При начале ввода текста в поле ввода.
Любые действия, направленные на изменение содержимого поля ввода, приводят к установке пессимистической блокировки данных.
Работа с XML, XDTO.
Средства разработки.
Изменен формат выгрузки в XML управляемых форм, настроек динамического списка, элементов графической схемы, географической схемы, состава функциональных опций и списка полей для операции выгрузки конфигурации в файлы. Имена тегов стали соответствовать именам встроенного языка, унифицировано написание имен элементов, формат выгрузки стал более компактным и читабельным, не выгружаются свойства, которые заполнены значениями по умолчанию. Настройки динамического списка стали выгружаться в одном элементе, в формате настроек системы компоновки данных.

Ранее выгруженные управляемые формы не могут быть загружены новой версией.

+

Формат выгрузки управляемых форм, настроек динамического списка, графических схем, географических схем, состава функциональных опций и списка полей в XML для операции выгрузки конфигурации в файлы был другим.XML-файлы выгрузки конфигурации стали более компактным, а их структура - более понятной.
План счетов.
Регистры бухгалтерии.
Обмен данными.
При записи элемента плана счетов со свойством ОбменДанными.Загрузка, установленным в значение Истина, новые виды субконто добавляются в таблицу значений субконто с контролем уникальности. При этом не уникальные записи не добавляются и не генерируется ошибка.При записи элемента плана счетов со свойством ОбменДанными.Загрузка, установленным в значение Истина, не выполнялась проверка уникальности при добавлении видов субконто в таблицу значений субконто, что могло приводить к ошибкам.Загрузка данных содержимого планов счетов и связанных регистров бухгалтерии может выполняться в любой последовательности.
Средства разработки.
Команда палитры свойств конфигуратора Сортировка по алфавиту выполняет сортировку по представлению свойств (если отключено отображение имен свойств) или по именам свойств (если такое отображение включено). Если у свойства нет имени, то сортировка всегда выполняется по текстовому представлению.Команда палитры свойств конфигуратора Сортировка по алфавиту всегда выполняла сортировку по представлению свойств.Поведение команды сортировки стало соответствовать установленному представлению свойств объекта.
В документации данное изменение описано здесь.
Система компоновки данных.
К области вертикального макета системы компоновки данных, содержащего имена выводимых полей, применяется условное оформление с областью использования В заголовке полей.

К области вертикального макета системы компоновки данных, содержащего значения выводимых полей, применяется условное оформление с областью использования В группировке.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Ко всем областям вертикального макета системы компоновки данных применялось условное оформление с областью использования В группировке.Применять условное оформление системы компоновки данных стало более удобно.
Толстый клиент.
Диагностируется ошибка в случае, если методу Вставить() объекта КолонкиТабличногоПоля передано более двух параметров.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Метод Вставить() объекта КолонкиТабличногоПоля мог принимать до пяти параметров, из которых использовались только первые два. Ошибки при этом не диагностировалось.Устранено незапланированное поведение системы.
Журнал регистрации.
Изменен формат хранения журнала регистрации. Журнал регистрации хранится в базе данных формата SQLite. Файл журнала имеет расширение .lgd. Месторасположение журнала не изменилось. Журнал регистрации в формате SQLite используется по умолчанию для вновь создаваемых информационных баз. Повышена скорость обращения к данным журнала регистрации.

Предоставляется возможность конвертации существующего журнала в новый формат. Обратная конвертация не предусмотрена.

Реализованы методы СкопироватьЖурналРегистрации() и ОчиститьЖурналРегистрации().

Время в журнале регистрации хранится в UTC.

Стандартная функция просмотра журнала регистрации позволяет просматривать файлы журнала регистрации нового формата (.lgd).

В стандартной форме просмотра журнала регистрации команда просмотра журнала регистрации из файла называется Еще - Просмотреть из файла.

Журнал регистрации имел текстовый формат.

В стандартной форме просмотра журнала регистрации команда просмотра журнала регистрации из файла называлась Еще - Загрузить из файла.

Увеличена скорость работы с данными журнала регистрации.

Повышена надежность работы журнала регистрации.

Представление команды просмотра файла журнала регистрации более точно соответствует выполняемому действию.

В документации данное изменение описано здесь, здесь, здесь и здесь.
Журнал регистрации.
Существенно ускорено удаление большого количества записей журнала регистрации (более 10 миллионов). +Реализована возможность прерывать сокращение журнала регистрации (в конфигураторе - с помощью Ctrl+Break или с помощью завершения сеанса административными средствами - в остальных случаях). Часть записей при этом будет удалена, а часть - нет.Скорость удаления записей журнала регистрации была недостаточной.

Прервать сокращение журнала регистрации было невозможно.

Стало возможным проводить сокращения больших журналов регистрации за приемлемое время.

Стало возможно прерывать процесс сокращения в случае необходимости.

В документации данное изменение описано здесь.
Табличный документ.
При сохранении табличного документа в PDF-файл сохраняется одна копия. Свойство табличного документа КоличествоЭкземпляров игнорируется.

Для того, чтобы поместить в PDF-файл несколько копий, следует использовать метод ЗаписатьФайлДляПечати() объекта ПакетОтображаемыхДокументов.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

При сохранении табличного документа в PDF-файл, в этот файл помещается столько копий, сколько указано в свойстве КоличествоЭкземпляров. Устранено незапланированное поведение системы.
Клиентское приложение.
Средства разработки.
В конфигураторе и толстом клиенте реализована возможность пользовательской настройки фона выделения результатов поиска.В конфигураторе и толстом клиенте результаты поиска выделялись фиксированным цветом фона, который нельзя было изменить.Пользователь может выбрать цвет фона выделения результатов поиска, максимально соответствующий используемым настройкам редактора текста.
В документации данное изменение описано здесь и здесь.
Обмен данными.
Общие реквизиты / Разделение данных.
Не требуется право Изменение на таблицу регистрируемого объекта для регистрации изменений в сеансе, где не используется ни один разделитель.

В сеансе, где используются разделители, реализованы следующие возможности:

  • Реализована возможность регистрации изменений для пустого набора записей, подчиненных регистратору. Если в сеансе не используются все разделители, необходимые для набора записей, получение значений разделителей выполняется из соответствующих полей регистратора.
  • При невозможности уточнить значения необходимых разделителей с помощью регистратора (существующего в памяти), генерируется ошибка и регистрация изменения прекращается.
Для регистрации изменений в сеансе, где не используется ни один разделитель, было необходимо наличие права Изменение на таблицу регистрируемого объекта.

В сеансе, где используются разделители, регистрации изменений для пустого набора записей, подчиненных регистратору была невозможна.

Устранение некорректного поведения механизма регистрации изменений в разделенном режиме работы.
Общие реквизиты / Разделение данных.
Работа с базой данных.
Реализованы новые возможности для методов НайтиПомеченныеНаУдаление(), НайтиПоСсылкам(), УдалитьОбъекты(): указать, в каких областях данных будет выполняться поиск ссылок или удаление объектов, включить или исключить из поиска/удаления некоторый перечень объектов конфигурации.

Для таблиц значений, которые возвращаются в результате работы методов НайтиПоСсылкам() и УдалитьОбъекты() реализована колонка, которая содержит значения разделителей, определяющие область данных, в которой находится найденный объект или объект, препятствующий удалению объекта.

Метод УдалитьОбъекты() возвращает значение типа Число, которое определяет количество удаленных объектов.

Поиск ссылок или помеченных на удаление объектов, удаление помеченных объектов выполнялись среди данных, которые доступны в текущем сеансе с текущими значениями разделителей. Также было невозможно принудительно включить или исключить из поиска/удаления перечень объектов конфигурации.

Таблица значений, которая возвращалась в результате работы методов НайтиПоСсылкам() и УдалитьОбъекты() не содержала колонки со значениями разделителей.

Метод УдалитьОбъекты() являлся процедурой.

Появилась возможность реализовать более гибкие алгоритмы удаления помеченных, особенно в разделенных информационных базах. Стало возможно более адекватно сообщать о результатах удаления помеченных (сколько объектов удалено, сколько не удалено и т.д.).
В документации данное изменение описано здесь.
Определяемые типы.
Состав свойств в палитре свойств конфигуратора для реквизита, тип которого является определяемым, формируется исходя из фактического типа, описывающего определяемый тип.Состав свойств в палитре свойств для реквизита, тип которого является определяемым, всегда отображался как для составного типа, вне зависимости от фактического типа.Возможности настройки реквизитов определяемого типа приведены в соответствие с возможностями настройки реквизитов с явным указанием типов.
Программное лицензирование.
В диалоге активации программной лицензии для ввода пинкода реализовано одно поле ввода с маской ввода (во всех случаях использования).

При вводе ответа центра лицензирования для каждой строки ответа используется одно поле ввода (с маской). С помощью клавиши Tab выполняется переход между строками ответа.

На странице регистрации комплекта реализована возможность получить информацию о различных вариантах активации комплекта на 5, 10 и 20 пользователей.

Расширена диагностика ошибок при активации лицензий.

В диалоге активации программной лицензии для ввода пинкода использовались 5 полей ввода (во всех случаях использования).

При вводе ответа центра лицензирования для каждой строки ответа использовались 5 полей ввода. С помощью клавиши Tab выполнялся переход между полями ввода и строками ответа.

При регистрации комплекта не было возможности получить информацию о разных способах активации комплекта.

При возникновении ошибки активации лицензии всегда выводилась технологические тексты ошибок, не всегда дающие возможность правильно понять причину ошибки.

Улучшен диалог активации программной лицензии. Стало возможно вставлять пинкод из буфера обмена.

Ввод ответа центра лицензирования стал более удобным.

Диагностика ошибок активации стала более понятной пользователю.

Общие реквизиты / Разделение данных.
После установки режима совместимости с версией 8.2.16 и ниже, при выполнении проверки конфигурации или обновлении конфигурации базы данных, анализируется вхождение журналов документов в состав хотя-бы одного общего реквизита и выдается соответствующая диагностика в случае такового вхождения. Обновление конфигурации базы данных в таком случае не выполняется.Проверка конфигурации, в которой в режиме совместимости с версией 8.2.16 и ниже, существовали журналы документов, входящие в состав общих реквизитов, не диагностировала ошибок и не препятствовала обновлению конфигурации базы данных.Устранена возможность приведения системы в не консистентное состояние, связанное с тем, что в версии 8.2.16 журналы документов не могли входить в состав общего реквизита.
Система компоновки данных.
Параметр вывода системы компоновки данных РасположениеГруппировки не влияет на вывод общих итогов.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Общий итог группировки не выводился, если параметр системы компоновки данных РасположениеГруппировки, для выбранной группировки, имел значение Конец или Нет.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Табличный документ.
Подсказка для ячейки высотой в одну строку выводится многострочной в том случае, если эта подсказка не помещается в одну строку.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Подсказка для ячейки высотой в одну строку также выводилась в одну строку. Если текст не помещался в одну строку - он завершался символом «...».Устранено незапланированное поведение системы.
Табличный документ.
В тонком клиенте, при получении табличного документа с сервера, сохраняются пустые строки, которые расположены в ячейках табличного документа.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

В тонком клиенте, при получении табличного документа с сервера, происходило удаление пустых строк, расположенных в ячейках табличного документа.Устранена потеря данных при передаче табличного клиента с сервера на сторону клиентского приложения.
Управляемая форма.
Нажатие клавиш Стрелка вниз или Стрелка вверх, которое выполнено в ячейке таблицы управляемой формы (с режимом редактирования Непосредственно) не будет приводить к тому, что выпадающий список (если настроен у ячеек таблицы) будет открываться во время навигации по строкам таблицы. Выпадающий список будет открыт только при добавлении новой строки.

Для открытия выпадающего списка следует воспользоваться комбинацией клавиш Ctrl+Стрелка вниз.

Нажатие клавиш Стрелка вниз или Стрелка вверх, которое выполнено в ячейке таблицы управляемой формы (с режимом редактирования Непосредственно) в некоторых случаях приводили к открытию выпадающего списка, что делало невозможным добавление новой строки нажатием клавиши Стрелка вниз.Устранено незапланированное поведение системы.
Система компоновки данных.
При генерации макета компоновки данных из предопределенных макетов удаляются выражения расшифровки, которые содержат поля, недоступные по функциональным опциям.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

При генерации макета компоновки данных из предопределенных макетов полностью копировались выражения расшифровки.При формировании отчета не возникают ошибки в том случае, если в макетах используются поля, отключенные функциональными опциями.
В документации данное изменение описано здесь и здесь.
Клиентское приложение.
Клиентское приложение в управляемом режиме при нарушении связи или проблемах на сервере в большинстве случаев позволяет повторить запрос, прервать операцию или завершить работу.При нарушении связи клиентского приложения и сервера, а также при возникновении проблем на сервере, не предоставлялась возможность повторения запроса. Чаще всего при возникновении таких проблем происходило аварийное завершение работы клиентского приложения.Повышена устойчивость работы клиентского приложения при нарушении связи или проблемах на стороне сервера «1С:Предприятия».
Мобильное приложение.
При установке свойства конфигурации Назначения использования в значения Персональный компьютер и Мобильное устройство, значение свойства Режим совместимости интерфейса устанавливается в значение Такси. Разрешить 8.2 в том случае, если до смены значения свойства Назначение использования режим совместимости интерфейса был установлен в значение Такси.

Если изменение свойства Назначения использования требует изменение значения свойств конфигурации Режим использования модальности и Режим совместимости интерфейса, то пользователю будет задан вопрос о необходимости такого изменения.

Выбор значения Мобильное устройство в свойстве конфигурации Назначения использования приводил к тому, что безусловно и без оповещения происходило изменение следующих свойств конфигурации:
  • Свойство Режим совместимости интерфейса устанавливалось в значение Версия 8.2;
  • Свойство Режим использования модальности устанавливалось в значение Использовать.
Поведение конфигуратора стало более понятным и предсказуемым.
В документации данное изменение описано здесь.
Программное лицензирование.
Реализована возможность активации программной лицензии для пользователя без административных прав. В этом случае активация лицензии будет выполняться «для текущего пользователя».Активация программной лицензии была возможна только для пользователя с административными правами.Стало возможно активировать программную лицензию в том случае, если пользователь без административных прав не обладает доступом на запись к каталогу, где расположены файлы лицензий, доступные всем пользователям компьютера.
В документации данное изменение описано здесь.
Предопределенные данные.
Обмен данными.
Общие реквизиты / Разделение данных.
При изменении предопределенных данных выполняется регистрация изменений только для реально измененных, добавленных или удаленных предопределенных элементов.

При смене режима совместимости со значения Версия 8.3.2 (и ниже) на значение Версия 8.3.3 (и выше), выполняется безусловная регистрация всех предопределенных элементов.

При смене режима совместимости со значения Версия 8.3.3 (и выше) на значение Версия 8.3.2 (и ниже), выполняется удаление регистрации изменений для всех предопределенных элементов.

При регистрации изменений предопределенных элементов:

  • если объект конфигурации, в котором выполняется изменение предопределенных элементов, и план обмена, в котором выполняется регистрация изменений, не имеют общих разделителей, то регистрация выполняется для всех узлов данного плана обмена;
  • если объект конфигурации, в котором выполняется изменение предопределенных элементов, и план обмена, в котором выполняется регистрация изменений, имеют общие разделители, то регистрация выполняется только для тех узлов плана обмена, для которых значения разделителей совпадают со значениями разделителей предопределенных элементов.
При изменении предопределенных данных выполнялась регистрация всех предопределенных элементов данного объекта.

Регистрация изменений предопределенных элементов выполнялась для всех узлов всех планов обмена, доступных из сеанса, в котором выполнялось изменение предопределенных элементов.

Не происходит сильного увеличения размера таблиц регистрации изменений объектов, для которых выполняется изменение предопределенных данных.
В документации данное изменение описано здесь.
Управляемая форма.
Веб-клиент.
В веб-клиенте, в ячейку таблицы управляемой формы выводятся только те строки многострочного текста, которые целиком помещаются в ячейку по высоте. Если строка отображается не полностью, в конце строки отображается символ «...». В веб-браузере Microsoft Internet Explorer 8 многоточие в конце строки не отображается.

В тонком клиенте улучшено заполнение текстом по вертикали ячейки таблицы управляемой формы.

В веб-клиенте, в ячейку таблицы управляемой формы выводились те строки многострочного текста, которые помещались по высоте ячейки любым своим фрагментом. Многоточие в конце последней строки в веб-клиенте не отображалось.

В тонком клиенте, в некоторых ситуациях, было возможно появление пустого места в нижней части ячейки таблицы управляемой формы.

Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
При загрузке пользовательских настроек отчетов и динамических списков (включая автоматическую загрузку при открытии форм) из настроек автоматически удаляются элементы, которые содержат ссылки на поля, отключенные функциональными опциями, недоступные в соответствии с правами доступами или связанные с более несуществующими полями схемы компоновки данных.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

При загрузке пользовательских настроек отчетов и динамических списков (включая автоматическую загрузку при открытии форм) из настроек автоматически удалялись элементы, которые содержали ссылки на поля, отключенные функциональными опциями или недоступные в соответствии с правами доступами.Повышена стабильность работы системы.
В документации данное изменение описано здесь.
Работа с базой данных.
Реализована возможность загрузки файла выгрузки информационной базы (*.dt), при формировании которого выполнялись следующие условия:
  • выгрузка выполнялась из файлового варианта;
  • при выгрузке использовалось «1С:Предприятие» версии 8.3.4;
  • в информационной базе существовали заполненные агрегаты оборотных регистров накопления.

В результате загрузки, в некоторых случаях, может происходить очистка агрегатов оборотных регистров накопления.

Загрузка файла выгрузки информационной базы (*.dt) не производилась, если при формировании файла выгрузки выполнялись следующие условия:
  • выгрузка выполнялась из файлового варианта;
  • при выгрузке использовалось «1С:Предприятие» версии 8.3.4;
  • в информационной базе существовали заполненные агрегаты оборотных регистров накопления.
Устранено незапланированное поведение системы.
Отображение информации.
Найденные фрагменты при поиске по подстроке оформляются единым образом (полужирным шрифтом и зеленым цветом) в следующих случаях:
  • выпадающий список поля ввода управляемой формы;
  • в избранном;
  • в истории;
  • в динамическом списке;
  • в форме полнотекстового поиска.
Найденные подстроки не имели единого оформления.Приведение дизайна различных механизмов к единому виду.
Работа с XML, XDTO.
Поле Предопределенное предопределенных табличных частей планов счетов и планов видов расчета доступно для записи. Предопределенные записи предопределенных табличных частей предопределенных элементов планов счетов и планов видов расчета могут содержать только предопределенные элементы.

При сериализации в XML (XDTO) элемента плана счетов или плана видов расчета записывается элемент Predefined, соответствующий свойству Предопределенное. При десериализации значение элемента Predefined будет записано в свойство Предопределенное только при отключенном режиме совместимости.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Поле Предопределенное предопределенных табличных частей планов счетов и планов видов расчета было доступно только для чтения.

При сериализации в XML (XDTO) элемента плана счетов или плана видов расчета элемент Predefined не формировался.

При обмене данными между конфигурациями перестали теряться признаки предопределенных данных в элементах планов счетов и планов вида расчета.
Управляемая форма.
Получение формы выбора в случае низкой скорости соединения реализовано аналогично другим случаям.Получение формы выбора в случае низкой скорости соединения выполнялось особым образом, при этом выполнялось кеширование самой формы.Повышена надежность получения формы выбора в случае низкой скорости соединения соединения.
Предопределенные данные.
Прикладные объекты.
При реструктуризации иерархических предопределенных данных элемент переносится на верхний уровень, если родитель элемента не обнаружен в момент обновления.

Если при реструктуризации или создании предопределенных данных в предопределенных табличных частях отсутствуют ссылки на зависимые элементы, то такие строки будут удалены (с выдачей диагностического сообщения или записи в журнал регистрации) и нормализацией номеров строк в таких табличных частях.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Некорректные ссылки на родительские элементы или зависимые элементы в предопределенных данных могли приводить к ошибкам в процессе выполнения реструктуризации информационной базы.Повышена стабильность работы системы при обнаружении некорректных ссылок на родительские элементы или зависимые элементы в предопределенных данных.
Командный интерфейс.
Определение размера картинок в панели разделов веб-клиента (в интерфейсе Такси) приведено к поведению тонкого клиенте. Высота картинок панели разделов определяется следующим образом:
  • Если есть хотя-бы одна картинка раздела, размер которой по вертикали более 48 точек, то все такие картинки пропорционально уменьшаются так, чтобы вертикальный размер был равен 48 точек;
  • Если все картинки панели разделов имеют вертикальный размер менее 48 точек, то высота панели разделов рассчитывается на основании максимального вертикального размера картинок, а картинки с меньшими размерами центрируются в областях, отведенных под картинки.
В веб-клиенте (в интерфейсе Такси) для картинки на панели разделов всегда резервировался квадрат 48x48 точек. Картинки большего размера пропорционально уменьшались, картинки меньшего размера центрировались внутри квадрата. Уменьшение высоты панели разделов не выполнялось.Поведение интерфейса Такси в веб-клиенте приведено к поведению тонкого клиента.
Табличный документ.
Работа с XML, XDTO.
При выполнении XDTO-десериализации табличного документа не важен порядок следования элементов в загружаемом XML-файле.При выполнении XDTO-десериализации табличного документа порядок следования элементов в загружаемом XML-файле был важен.Стало возможно без ошибок читать табличные документы, XDTO-сериализация которых была выполнена в «1С:Предприятии» версии 8.3.4 и ранее.
Используемые компоненты.
Библиотека OpenSSL обновлена до версии 1.0.0r.Использовалась библиотека OpenSSL версии 1.0.0m.Повышена безопасность использования платформы.
Веб-клиент.
Работа веб-клиента адаптирована к веб-браузеру Google Chrome 37. Исправлены недостатки отображения текста в управляемых формах (текст не помещался в отведенное под него место).В веб-браузере Google Chrome 37 наблюдались проблемы отображения текста.Улучшена поддержка веб-браузера Google Chrome 37.
Работа с СУБД.
Повышена надежность работы с СУБД PostgreSQL в некоторых случаях.Надежность работы с СУБД PostgreSQL в некоторых случаях была недостаточной.Повышена надежность работы с СУБД PostgreSQL.
Региональные установки.
Для России учитывается однократный сдвиг часовых зон на один час в связи с принятием закона № 248-ФЗ. Изменения касаются всех компонентов системы «1С:Предприятие», кроме веб-клиента. Веб-клиент пользуется информацией о временных зонах, которую предоставляет ОС и веб-браузер.Изменения, внесенные законом № 248-ФЗ, не учитывались платформой.Учтены изменения законодательства об исчислении времени.
Внешние компоненты.
В описание технологии создания внешних компонент (см. здесь) добавлен раздел с описанием ограничений в работе внешних компонент. Рекомендуется ознакомиться с этим разделом.Описание технологии создания внешних компонент не описывало ограничений при работе внешних компонент.Улучшено описание технологии создания внешних компонент.
Клиентское приложение.
Средства разработки.
При запуске толстого клиента (1cv8) в режиме обычного приложения не отображается окно показателей производительности.При запуске толстого клиента (1cv8) в режиме обычного приложения отображалось окно показателей производительности.Для обычного приложения отключено отображение показателей производительности, так как, в большинстве случаев, они в этом режиме не используются.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Динамический список.
Невозможно выполнять сортировку динамического списка по полям субконто регистра бухгалтерии. Попытка сортировки по таким полям (например, с помощью щелчка по заголовку колонки) не приводит к вызову сервера.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Попытка сортировки динамического списка по полям субконто регистра бухгалтерии приводила к формирования сообщения об ошибке и выполнению серверного вызова, не приводящего к получению каких-либо данных.Динамический список не позволяет выполнить недопустимую сортировку, что снижает вероятность неадекватной (по мнению пользователя) реакции системы на выполняемое действие.
В документации данное изменение описано здесь.
Прикладные объекты.
Попытка присвоить значение реквизиту ЭтотОбъект и ДополнительныеСвойства для объектов типа СправочникОбъект, ПланОбменаОбъект, ПланВидовХарактеристикОбъект приводит к возникновению исключительной ситуации.

Попытка присвоить значение реквизиту ОбменДанными для объектов типа СправочникОбъект, ПланВидовХарактеристикОбъект приводит к возникновению исключительной ситуации.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Попытка присвоить значение реквизиту ЭтотОбъект и ДополнительныеСвойства для объектов типа СправочникОбъект, ПланОбменаОбъект, ПланВидовХарактеристикОбъект не приводила к исключительной ситуации, однако присваивания значения также не происходило.

Попытка присвоить значение реквизиту ОбменДанными для объектов типа СправочникОбъект, ПланВидовХарактеристикОбъект не приводила к возникновению исключительной ситуации, однако присваивания значения также не происходило.

Работа с указанными свойствами приведена к единому виду: попытка присвоить значение реквизиту, доступному только для чтения, приводит к возникновению исключительной ситуации.
Клиентское приложение.
Кластер серверов.
При несовпадении версии клиентского и серверного приложений, поиск дистрибутива клиентского приложения выполняется в следующем порядке:
  • В каталоге, куда установлено «1С:Предприятие» (свойство InstalledLocation файлов 1cestart.cfg и 1cescmn.cfg);
  • В каталогах, указанных как место расположения дистрибутивных файлов новых версий (свойство DistributiveLocation файлов 1cestart.cfg и 1cescmn.cfg, а также свойство CommonCfgLocation файла 1cestart.cfg);
  • По URL, который возвращается в серверном исключении о несовпадении версий клиентского и серверного приложения (параметр PublishDistributiveLocation файла conf.cfg и атрибут pubdst элемента ws файла default.vrd);
  • С помощью интернет-сервисов получения дистрибутива клиентского приложения.

+

При несовпадении версии клиентского и серверного приложений, поиск дистрибутива клиентского приложения выполнялся в следующем порядке:
  • В каталоге, куда установлено «1С:Предприятие» (свойство InstalledLocation файлов 1cestart.cfg и 1cescmn.cfg);
  • По URL, который возвращается в серверном исключении о несовпадении версий клиентского и серверного приложения (параметр PublishDistributiveLocation файла conf.cfg и атрибут pubdst элемента ws файла default.vrd);
  • В каталогах, указанных как место расположения дистрибутивных файлов новых версий (свойство DistributiveLocation файлов 1cestart.cfg и 1cescmn.cfg, а также свойство CommonCfgLocation файла 1cestart.cfg);
  • С помощью интернет-сервисов получения дистрибутива клиентского приложения.
Поиск обновлений стал более логичным: вначале выполняется поиск обновлений в локальной сети и только после этого - с помощью интернет-сервисов.
В документации данное изменение описано здесь.
Общие реквизиты / Разделение данных.
Вызов методов УстановитьОбновлениеПредопределенныхДанных() и УстановитьОбновлениеПредопределенныхДанныхИнформационнойБазы() может выполняться только из сеанса, в котором не установлено использование ни одного разделителя (в дополнение к необходимости наличия права Администрирование).

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Вызов методов УстановитьОбновлениеПредопределенныхДанных() и УстановитьОбновлениеПредопределенныхДанныхИнформационнойБазы() можно было выполнять из любого сеанса при наличии права Администрирование.Снижена вероятность несанкционированного изменения режима обновления предопределенных данных информационной базы.
Навигационные ссылки.
Клиентское приложение.
Параметр МассивСсылок функции ПолучитьПредставленияНавигационныхСсылок() является обязательным. Возвращаемое значение этой функции всегда является массивом. Для тех значений входного массива, для которых невозможно получить представление, в выходном массиве возвращается значение Неопределено.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Параметр МассивСсылок функции ПолучитьПредставленияНавигационныхСсылок() не являлся обязательным. Поведение системы в том случае, когда для значения параметра нельзя было получить представление было различным для разных клиентских приложений.Функция ПолучитьПредставленияНавигационныхСсылок() работает одинаково в различных клиентских приложениях.
Веб-клиент.
Применение оператора Выполнить() в веб-клиенте приводит к возникновению исключительной ситуации.Применение оператора Выполнить() игнорировалось и не приводило к каким-либо диагностическим сообщениям.Реализована диагностика ошибок прикладных решений (использование оператора Выполнить() в веб-клиенте).
Табличный документ.
Для объекта ОбластьЯчеекТабличногоДокумента свойства ГраницаСверху, ГраницаСправа, ГраницаСнизу, ГраницаСлева содержат значение Неопределено в том случае, если в ячейках области соответствующая граница не является одинаковой у всех ячеек.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Для объекта ОбластьЯчеекТабличногоДокумента свойства ГраницаСверху, ГраницаСправа, ГраницаСнизу, ГраницаСлева содержали описание соответствующей границы первой попавшейся ячейки области.Устранено незапланированное поведение системы.
Система компоновки данных.
Если поля временной таблицы, создаваемой в запросе пакетного запроса системы компоновки данных, не используются последующими запросами пакетного запроса, а также если создаваемая временная таблица не находится в обязательных соединениях, то запрос, создающий временную таблицу, удаляется из пакетного запроса макета компоновки данных.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Временная таблица удалялась из пакетного запроса системы компоновки данных, если ее поля не использовались в последующих запросах пакетного запроса и создаваемая временная таблица не использовалась в других запросах пакетного запроса, которые также создают временные таблицы.Повышена адекватность при работе с временными таблицами в системе компоновки данных.
В документации данное изменение описано здесь.
Обмен данными.
Регистры сведений.
Корректно выполняется регистрация изменений для регистра сведений, у которого существует измерение типа УникальныйИдентификатор, входящее в основной отбор.

В таблице регистрации изменений для такого регистра сведений поле, описывающее измерение типа УникальныйИдентификатор, имеет тип УникальныйИдентификатор.

Регистрация изменений для регистра сведений, у которого существует измерение типа УникальныйИдентификатор выполнялась некорректно.

В таблице регистрации изменений регистра поле, описывающее измерение с типом УникальныйИдентификатор, имело тип ДвоичныеДанные.

Устранено незапланированное поведение системы. Для планов обмена, в состав которых входят регистры сведений с измерениями типа УникальныйИдентификатор, которые входят в основной отбор, необходимо выполнить регистрацию всех изменений.
Встроенный язык.
Общие объекты.
В тонком клиенте недоступны следующие типы: СтрокаТаблицыЗначений, КоллекцияКолонокТаблицыЗначений, КолонкаТаблицыЗначений, ИндексыКоллекции, ИндексКоллекции, КоллекцияСтрокДереваЗначений, СтрокаДереваЗначений, КоллекцияКолонокДереваЗначений, КолонкаДереваЗначений.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Следующие типы были доступны в тонком клиенте: СтрокаТаблицыЗначений, КоллекцияКолонокТаблицыЗначений, КолонкаТаблицыЗначений, ИндексыКоллекции, ИндексКоллекции, КоллекцияСтрокДереваЗначений, СтрокаДереваЗначений, КоллекцияКолонокДереваЗначений, КолонкаДереваЗначений.Устранено незапланированное поведение системы.
Управляемая форма.
Обработчик события ОкончаниеВводаТекста для поля ввода управляемой формы больше не вызывается при нажатии кнопок регулирования.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Обработчик события ОкончаниеВводаТекста для поля ввода управляемой формы вызывался при нажатии кнопок регулирования.Устранено незапланированное поведение системы.
Прикладные объекты.
Управляемая форма.
Для реквизитов объектов типа Дата реализовано заполнение из данных заполнения в том случае, если создание объекта выполняется из динамического списка и по этому реквизиту установлен отбор.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

У реквизитов типа Дата не устанавливались значения из данных заполнения, сформированных из отбора динамического списка, а в стандартном параметре ЗначенияЗаполнения формы нового элемента для таких реквизитов из отборов динамического списка передавались значения типа СтандартнаяДатаНачала.Устранено незапланированное поведение системы.
Управляемая форма.
 +

Если в результате редактирования строки с маской ввода, в поле ввода управляемой формы, получилась строка, соответствующая пустой маске ввода, то в реквизит формы, который отображается полем ввода, будет помещена пустая строка. Если длина строки установлена фиксированной - строка будет состоять из пробелов.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Если в результате редактирования строки с маской ввода, в поле ввода управляемой формы, получилась строка, соответствующая пустой маске ввода, то в реквизит формы, который отображается полем ввода, помещалась строка, включающая пробелы и фиксированные символы маски ввода.При очистке поля ввода, в связанный реквизит будет помещена пустая строка вне зависимости от того, установлена для поля маска ввода или нет. В результате корректно отображается автоматическая отметка незаполненного для полей ввода, связанных с реквизитом типа текст и с установленной маской ввода.
Управляемая форма.
Изменен алгоритм формирования выпадающего списка (при вводе по строке) для полей ввода управляемой формы. Алгоритм формирования приведен в документации.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

При формировании списка выбора (при вводе по строке) для поля ввода управляемой формы использовался следующий алгоритм:
  • Получаются 10 первых результатов поиска по началу строки;
  • Если список оказался меньше, чем 10 элементов, то список дополняется до 10 результатами поиска по подстроке;
  • Если в списке все равно менее 10 элементов, то список дополняется результатами поиска по другим полям, доступным для поиска при вводе по строке.
Устранение найденных недочетов в алгоритме формирования выпадающего списка поля ввода управляемой формы для ситуации, когда поиск делается и по началу строки и по подстроке.
В документации данное изменение описано здесь.
Управляемая форма.
Реализована возможность получения списка форм рабочего стола. Для режимов интерфейса Формы в закладках и Такси в коллекции ОкнаКлиентскогоПриложения присутствует отдельный элемент, описывающий начальную страницу (рабочий стол). Свойство Содержимое для этого элемента содержит перечень форм, присутствующих на начальной странице (рабочем столе).

Для режима интерфейса Формы в отдельных окнах коллекция ОкнаКлиентскогоПриложения содержит объекты ОкноКлиентскогоПриложения, которые описывают формы, расположенные на рабочем столе.

Для объекта ОкноКлиентскогоПриложения реализованы свойства НачальнаяСтраница, Содержимое.

Метод ПолучитьСодержимое() для объекта ОкноКлиентскогоПриложения поддерживается для совместимости.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Данная возможность не предоставлялась.

Для режимов интерфейса Формы в закладках и Такси в коллекции ОкнаКлиентскогоПриложения отсутствовали объекты, описывающие начальную страницу (рабочий стол).

Для режима интерфейса Формы в отдельных окнах коллекция ОкнаКлиентскогоПриложения не содержала объектов, описывающих формы, открытые на рабочем столе.

Прикладным разработчикам предоставлена возможность для программного доступа к формам, открытым на начальной странице (рабочем столе).
В документации данное изменение описано здесь.
Автоматизированное тестирование.
Для подчиненных объектов объекта ТестируемоеПриложение реализован объект ТестируемоеОкноКлиентскогоПриложения, описывающий начальную страницу (рабочий стол).

Формы (объекты типа ТестируемаяФорма), входящие в состав начальной страницы (рабочего стола) являются подчиненными объекту ТестируемоеОкноКлиентскогоПриложения, описывающему начальную страницу (рабочий стол).

Для объекта ТестируемоеОкноКлиентскогоПриложения реализовано свойство НачальнаяСтраница.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Среди подчиненных объектов объекта ТестируемоеПриложение отсутствовал объект ТестируемоеОкноКлиентскогоПриложения, описывающий начальную страницу (рабочий стол).

Формы, включенные в начальную страницу (рабочий стол) были подчинены объекту ТестируемоеОкноКлиентскогоПриложения с установленным, в значение Истина, свойством Основное.

Реализована возможность использовать возможности программного доступа к формам начальной страницы (рабочего стола) с помощью средств автоматизированного тестирования.
В документации данное изменение описано здесь.
Общие реквизиты / Разделение данных.
Обмен данными.
При регистрации предопределенных данных неразделенного объекта конфигурации в разделенном плане обмена из сеанса, в котором используются все разделители, вызывается исключение, которое не требует завершения работы приложения.При регистрации предопределенных данных неразделенного объекта конфигурации в разделенном плане обмена из сеанса, в котором используются все разделители, вызывалось исключение, которое требовало завершения работы приложения. Уменьшено количество ситуаций, приводящих к аварийному завершению работы приложения.
Общие реквизиты / Разделение данных.
Обмен данными.
Если для объекта конфигурации в сеансе используются не все разделители, в состав которых он (объект конфигурации) входит, то для него не выполняется инициализация предопределенных элементов при вызове метода ИнициализироватьПредопределенныеДанные().

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Если для объекта конфигурации в сеансе используются не все разделители, в состав которых он (объект конфигурации) входит, то в этом случае вызывается исключение при вызове метода ИнициализироватьПредопределенныеДанные().Стало возможно использовать метод ИнициализироватьПредопределенныеДанные() в любом сеансе, а не только в сеансе, в котором используются все разделители.
В документации данное изменение описано здесь.
Работа с СУБД.
Система компоновки данных.
Динамический список.
Длина шаблона поиска для операции языка запросов ПОДОБНО, а также при поиске в динамическом списке и при использовании отбора в системе компоновки данных, стала ограничена. Размер ограничения зависит от используемой СУБД. В случае превышения длины шаблона будет выдаваться ошибка, не приводящая к завершению работы системы.Использование шаблона поиска, длиной более 1024 символов, в операции языка запросов ПОДОБНО, а также при поиске в динамическом списке и отборе в системе компоновки данных, могло приводить к ошибке СУБД и аварийному завершению работы системы.Исключены аварийные завершения работы системы, возникающие из-за указания слишком длинного шаблона поиска.
В документации данное изменение описано здесь.
Прикладные объекты.
В обработчик ОбработкаПолученияПредставления передается правильное значение поля ЭтоГруппа.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

В обработчик ОбработкаПолученияПредставления передавалось инвертированное значение поля ЭтоГруппа.Устранено незапланированное поведение системы.
Управляемая форма.
Хранение настроек.
Настройка отображения управляемой формы сохраняется в хранилище системных настроек с учетом ключа назначения использования. Ключ объекта формируется следующим образом: <Полное имя формы>/<Ключ назначения использования>/НастройкиФормы.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Настройка отображения управляемой формы сохранялась в хранилище системных настроек без учета ключа назначения использования. Ключ объекта всегда имел следующий вид: <Полное имя формы>/НастройкиФормы.Стало возможно использовать одну и ту же форму для разных целей, причем для каждой цели используется свои настройки отображения.
В документации данное изменение описано здесь и здесь.
Система компоновки данных.
Во время вычисления выражений системы компоновки данных происходит переход в безопасный режим.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Во время вычисления выражений системы компоновки данных не выполнялся переход в безопасный режим.Повышена безопасность при выполнении отчетов, которые могут использовать небезопасные методы общих модулей.
В документации данное изменение описано здесь, здесь и здесь.
Управляемая форма.
В таблице управляемой формы начинать перетаскивание можно только с доступной ячейки таблицы.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

В таблице управляемой формы перетаскивание можно было начинать с любой ячейки таблицы. При этом если перетаскивать пытались недоступную ячейку - реально перетаскиваться начинала текущая ячейка (на момент начала перетаскивания).Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Параметр Текст условного оформления, которое задается для области использования в заголовке полей, применяется для заголовков полей группировки.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

К заголовкам полей группировки параметр условного оформления Текст никогда не применялся.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Система компоновки данных.
Генератор макета компоновки данных для вложенных отчетов всегда генерирует свойство ВертикальныйУровень. К значению данного свойства прибавляется уровень родительского отчета, в котором находится вложенный отчет.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Группировки родительского отчета не учитывались при выводе вложенных отчетов.Группировки родительского отчета распространяются на вложенные отчеты: визуально вложенные отчеты находятся на том же уровне группировки, что и родительский отчет.
В документации данное изменение описано здесь.
Управляемая форма.
Для поля управляемой формы реализован вид поля ПолеПериода, для упрощения выбора периода дат, кратных месяцу.

Для расширения поля управляемой формы для поля календаря реализовано свойство Рамка, с помощью которого можно задавать параметры рамки для поля календаря.

Изменен диалог установки интервала дат динамического списка, диалог стандартного периода для поля ввода, редактирующего значение типа СтандартныйПериод и для объекта ДиалогРедактированияСтандартногоПериода. В режиме совместимости с версией 8.3.4 поведение поля ввода не изменилось.

Для поля управляемой формы отсутствовал вид поля ПолеПериода.

У расширения поля управляемой формы для поля календаря отсутствовало свойство Рамка.

Для диалога установки интервала дат динамического списка, диалога стандартного периода для поля ввода, редактирующего значение типа СтандартныйПериод и для объекта ДиалогРедактированияСтандартногоПериода использовался другой диалог. В поле ввода открывается выпадающий список со списком вариантов, если установлен вариант периода, отличный от произвольного.

Улучшен диалог выбора интервала дат.
Управляемая форма.
Строка в таблице управляемой формы автоматически удаляется, если эта строка была добавлена при окончании редактирования предыдущей строки или при нажатии клавиши Стрелка вниз и в том случае, если после окончания добавления эта строка не изменялась ни программно, ни интерактивно.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Строка в таблице управляемой формы автоматически удалялась, если эта строка была добавлена при окончании редактирования предыдущей строки или при нажатии клавиши Стрелка вниз и в том случае, если после окончания добавления эта строка не изменялась интерактивно.Устранено незапланированное поведение системы.
В документации данное изменение описано здесь.
Управляемая форма.
При заполнении истории выбора поля ввода выполняется проверка на удаленные элементы. Представление значения будет удалено из списка истории, если данные удалены в этом сеансе или удаление было выполнено в другом сеансе, но в последствии представление удаленных данных получалось в этом сеансе. Если значение удалено после формирования истории выбора, то при попытке выбора такого значения формируется предупреждение, выбор не выполняется и элемент удаляется из списка истории.

Поведение реализовано для тонкого клиента и веб-клиента.

Удаленные значения отображались в истории выбора полей ввода в виде сообщения Объект не найден.Поведение системы стало более соответствовать ожиданиям пользователей. Из истории выбора удаляется информация об объектах, которые невозможно выбрать.
Управляемая форма.
Длина значения свойства управляемой формы КлючНазначенияИспользования ограничена 128 символами. Попытка присвоить свойству значение длиной более 128 символов или открыть форму со значением этого свойства более 128 символов приводит к исключению.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

Длина значения свойства управляемой формы КлючНазначенияИспользования не ограничивалась.Упрощена диагностика проблем, связанных со слишком длинным значением свойства КлючНазначенияИспользования.
В документации данное изменение описано здесь.
Ограничение доступа к данным.
Для объекта конфигурации, имеющего табличные части и входящего в состав разделителя, выполняется проверка ограничения доступа к данным (выполняемая после операции записи), в том случае, если в условии ограничения использовались реквизиты табличной части объекта.

В результате возможно появление сообщений о нехватке прав доступа в ситуациях, когда раньше таких сообщений не возникало.

Для объекта конфигурации, имеющего табличные части и входящего в состав разделителя, не выполнялась проверка ограничения доступа к данным (выполняемая после операции записи), в том случае, если в условии ограничения использовались реквизиты табличной части объекта.Устранено незапланированное поведение системы. +
Предопределенные данные.
План счетов.
План видов расчета.
При реструктуризации информационной базы:
  • Строка предопределенной табличной части плана счетов и плана видов расчета, добавленная в режиме «1С:Предприятие» и содержащая ссылку на предопределенный элемент, будет помечена предопределенной, если в режиме конфигуратора добавлена предопределенная строка содержащая ссылку на этот же элемент.
  • При удалении предопределенной строки из предопределенной табличной части плана счетов или плана видов расчета не происходит непосредственного удаления строки, а у нее сбрасывается признак предопределенности.

Также, при необходимости, будет изменен порядок следования строк в табличных частях так, чтобы предопределенные строки всегда следовали первыми.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

У плана счетов было невозможно добавить в конфигурации предопределенный вид субконто, который до этого был добавлен пользователем в режиме предприятия. При удалении предопределенной строки из предопределенной табличной части плана счетов происходило непосредственное удаление строки.

У плана видов расчета:

  • Для «1С:Предприятия» до версии 8.2.12 включительно, поведение соответствовало поведению в версии 8.3.5;
  • Для «1С:Предприятия» с версии 8.2.13 до версии 8.3.4 включительно, при добавлении в конфигурации вытесняющего, ведущего или базового вида расчета, который уже был добавлен пользователем в режиме «1С:Предприятие», происходило дублирование вида расчета. При удалении предопределенной строки из предопределенной табличной части плана видов расчета происходило непосредственное удаление строки.
После редактирования предопределенных табличных частей не происходит потери данных.

Возможна ситуация, когда редактирование списка видов субконто для предопределенных счетов в конфигураторе приведет к сообщению о превышении количества видов субконто у счета.

Регистры бухгалтерии.
Регистры накопления.
Регистры сведений.
Регистры расчета.
В таблице значений, получаемой с помощью метода Выгрузить() набора записей регистра бухгалтерии, накопления, расчета или регистра сведений, значение колонки НомерСтроки соответствует номеру строки выгружаемого набора записей.

В режиме совместимости с версией 8.3.4 поведение не изменилось.

В таблице значений, получаемой с помощью метода Выгрузить() набора записей регистра бухгалтерии, накопления, расчета или регистра сведений, значение колонки НомерСтроки соответствовало индексу строки выгружаемого набора записей.Устранено некорректное поведение системы.
Клиентское приложение.
Работа с Интернет.
При использовании защищенного соединения рекомендуется использовать протокол TLS как более защищенный. Использование протокола SSL v3.0 по умолчанию отключено.

В случае, если веб-сервер, который используется для подключения с помощью тонкого клиента, может использовать протокол SSL v3.0, то в этом случае можно использовать ключ командной строки запуска тонкого клиента /HttpsAllowSSLv3.

При подключении к хранилищу конфигурации, при использовании отладчика, а также при использовании объектов HTTPСоединение, FTPСоединение, ИнтернетПочта, WSПрокси, WSСсылка, WSОпределение использование протокола SSL v3.0 отключено по умолчанию. При необходимости использовать этот протокол следует использовать параметр AllowSSLv3 файла conf.cfg. Для файла conf.cfg реализован параметр AllowSSLv3.

Для объекта ИнтернетПочта в режиме совместимости с версией 8.3.5 и ниже, а также в более младших версиях «1С:Предприятия» включение использования протокола SSL v3.0 производится с помощью редактирования системного реестра (для ОС Windows). Возможности использования объектом ИнтернетПочта протокола SSL v3.0 (в ОС Linux) определяются используемой версией бибилиотеки OpenSSL.

При использовании защищенного соединения по умолчанию использовался протокол SSL v3.0.Повышена защищенность соединения, устанавливаемого клиентским приложением, при работе через Интернет.
В документации данное изменение описано здесь, здесь и здесь.
Веб-клиент.
Внешние компоненты.
Переработаны расширение работы с файлами и расширение работы с криптографией (для всех поддерживаемых веб-браузеров для ОС Windows). Переработка вызвана отказом от поддержки технологии NPAPI в веб-браузере Google Chrome.

Новые версии расширений работают исключительно асинхронно при любых операциях с файлами и криптографией (с использованием механизма оповещений). Для работы с расширениями и внешними компонентами необходимо установить специальное расширение, доступ к которому автоматически предоставляет веб-клиент при попытке выполнить подключение расширения.

Для работы на стороне клиентского приложения с внешними компонентами, расширениями работы с файлами и криптографией, реализована асинхронная техника. На стороне клиентского приложения синхронная техника работы с внешними компонентами и расширениями работы с файлами и криптографией оставлена для совместимости. Необходима переработка прикладных решений для поддержки этой техники, в том числе для работы с внешними компонентами:

  • вызовы методов заменяются на вызовы асинхронных методов НачатьВызов<ИмяМетода>();
  • чтение значений свойств заменяются на вызовы асинхронных методов НачатьПолучение<ИмяСвойства>();
  • установки значений свойств заменяются на вызовы асинхронных методов НачатьУстановку<ИмяСвойства>().

Внешние компоненты переписывать не требуется. Добавление префиксов и поддержка асинхронности добавляется системой автоматически. +Реализовано свойство конфигурации РежимИспользованияСинхронныхВызововРасширенийИВнешнихКомпонент. Если свойство установлено в значение Не использовать, то расширения, базирующиеся на NPAPI, в веб-клиенте вовсе не загружаются и, как следствие, синхронные методы не работают. В остальных случаях производится попытка загрузки расширения, реализованного на NPAPI. В случае успеха будут работать и синхронные и асинхронные методы. Более подробно поведение описано в документации.

Старые версии расширений можно удалить обычным образом.

Доработана технология создания внешних компонент (см. здесь).

Реализованы методы глобального контекста НачатьПодключениеРасширенияРаботыСКриптографией(), НачатьПодключениеРасширенияРаботыСФайлами(), НачатьПодключениеВнешнейКомпоненты(), НачатьКопированиеФайла(), НачатьПеремещениеФайла(), НачатьУдалениеФайлов(), НачатьПоискФайлов(), НачатьСозданиеКаталога(), НачатьПолучениеКаталогаВременныхФайлов(), НачатьПолучениеКаталогаДокументов(), НачатьПолучениеРабочегоКаталогаДанныхПользователя(), НачатьПолучениеФайлов(), НачатьПомещениеФайлов(), НачатьЗапросРазрешенияПользователя(), НачатьЗапускПриложения().

Для объекта МенеджерКриптографии реализованы конструктор без параметров, методы НачатьИнициализацию(), НачатьШифрование(), НачатьПодписывание(), НачатьПолучениеИнформацииМодуляКриптографии(), НачатьПолучениеСертификатовИзПодписи(), НачатьПолучениеХранилищаСертификатов(), НачатьПроверкуПодписи(), НачатьПроверкуСертификата(), НачатьРасшифровку().

Для объекта СертификатКриптографии реализован конструктор без параметров, методы НачатьИнициализацию(), НачатьВыгрузку().

Для объекта СредстваКриптографии реализован метод НачатьПолучениеИнформацииМодуляКриптографии().

Для объекта ХранилищеСертификатовКриптографии реализованы методы НачатьДобавление(), НачатьПоискПоОтпечатку(), НачатьПоискПоСерийномуНомеру(), НачатьПоискПоСубъекту(), НачатьПолучениеВсех(), НачатьУдаление().

Для объекта ДиалогВыбораФайла реализован метод Показать().

Для объекта Файл реализован конструктор без параметров, реализованы методы НачатьИнициализацию(), НачатьПолучениеВремениИзменения(), НачатьПолучениеНевидимости(), НачатьПолучениеТолькоЧтения(), НачатьПолучениеРазмера(), НачатьПолучениеУниверсальногоВремениИзменения(), НачатьПроверкуСуществования(), НачатьУстановкуВремениИзменения(), НачатьУстановкуНевидимости(),

НачатьУстановкуТолькоЧтения(), НачатьУстановкуУниверсальногоВремениИзменения(), НачатьПроверкуЭтоКаталог(), НачатьПроверкуЭтоФайл().

С помощью механизма рефакторинга стало возможно преобразовывать синхронные методы работы с расширениями и внешними компонентами в асинхронные аналоги. Расширены настройки механизма рефакторинга.

Расширения работы с файлами и криптографией были реализованы по технологии NPAPI. Работы с методами расширений была синхронной. В веб-браузере Google Chrome было возможно синхронно работать с программным интерфейсом внешних компонент.Реализована поддержка асинхронной работы с криптографией, внешними компонентами и расширенной работы с файлами в веб-клиенте, обеспечивающая возможность работы с веб-браузером Google Chrome.

Необходимо помнить, что поддержка синхронных вызовов в веб-браузере Google Chrome будет по умолчанию отключена в версии 42 (апрель 2015 года), а полностью удалена в версии 45 (сентябрь 2015 года). При этом синхронные методы во встроенном языке также перестанут работать, несмотря на то, что сама платформа поддерживает эти вызовы.

В документации данное изменение описано здесь, здесь, здесь, здесь, здесь, здесь, здесь и здесь.
Внешние компоненты.
Технология внешних компонент (см. здесь) перестала поддерживать разработку внешних компонент для веб-браузера Safari для ОС Windows.Технология внешних компонент поддерживала разработку внешних компонент для веб-браузера Safari для ОС Windows.Исключена поддержка неактуального веб-браузера. Выпуск веб-браузера Safari для ОС Windows прекращен компанией Apple. +
Внешние компоненты.
В технологии внешних компонент реализована поддержка веб-браузера Mozilla Firefox версии 31.0 и выше. Рекомендуется выполнить сборку нового установочного пакета для веб-браузера Mozilla Firefox с использованием нового адаптера. Рекомендуется удалить из архива с внешней компонентой установочные пакеты для веб-браузера Mozilla Firefox версии 30.0 и младше.

В технологии внешних компонент прекращена поддержка веб-браузера Mozilla Firefox версии 30.0 и младше. Удалены адаптеры для веб-браузера Mozilla Firefox версии 30.0 и младше.

Технология внешних компонент не поддерживала работу с веб-браузером Mozilla Firefox версий 31.0 и выше.

Технология внешних компонент поддерживала работу с веб-браузером Mozilla Firefox версии 30.0 и младше.

Технология внешних компонент стала поддерживать возможность работы с новыми версиями веб-браузера Mozilla Firefox (версии 31.0 и выше).

Технология внешних компонент перестала поддерживать работу с устаревшими версиями веб-браузера Mozilla Firefox (версии 30.0 и младше).

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Переименованы свойства объекта ДанныеАдреса. Старые имена используются для совместимости.
  • Улица;
  • Дом.
  • СтрокаАдресаОсновная;
  • СтрокаАдресаДополнительная.
Изменено представление событий журнала регистрации _$Data$_.TotalsMinPeriodUpdate и _$Data$_.TotalsPeriodUpdate.
  • _$Data$_.TotalsMinPeriodUpdate
  • Данные. Изменение периода рассчитанных итогов
  • Данные. Изменение минимального периода рассчитанных итогов
  • Данные. Изменение максимального периода рассчитанных итогов

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Динамический список.
Работа с запросами.
В мобильной платформе реализована возможность работы с произвольными запросами, в том числе и в динамических списках.Данная функциональность не поддерживалась на мобильной платформе.Стало возможно использовать в мобильном приложении динамические списки, построенные на основании произвольного запроса, а также использовать запросы к информационной базе для реализации различных механизмов, например для контроля остатков при проведении документов.
Управляемая форма.
Ускорено открытие формы и выполнение контекстных серверных вызовов.Открытие формы и контекстные серверные вызовы выполнялись недостаточно быстро.Работа с формами в мобильном приложении стала более комфортной.
Прикладные объекты.
Создание предопределенных элементов выполняется в момент первого обращения к соответствующей таблице. Вызов метода УстановитьОбновлениеПредопределенныхДанных() до первого обращения позволяет изменить признак создания предопределенных данных. Создание предопределенных элементов выполнялось только в момент обновления конфигурации мобильного приложения. Изменение режима создания предопределенных после вызова метода УстановитьОбновлениеПредопределенныхДанных() происходило только при следующем обновлении конфигурации мобильного приложения.Поведение мобильной платформы приведено в соответствие с платформой для персонального компьютера версии 8.3.3.
Фоновые и регламентные задания.
В мобильной платформе реализована возможность работы с фоновыми заданиями.Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно работать с фоновыми заданиями.
Права доступа.
Функциональные опции.
Для мобильной платформы реализованы следующие возможности:
  • Функциональные опции и параметры функциональных опций;
  • Роли (в ограниченном объеме). Доступен механизм ролевого управления видимостью и доступностью элементов формы и командного интерфейса;
  • Доступна ролевая настройка видимости форм на начальной странице. После применения функциональных опций и ролей используется первая, по порядку, форма из доступного списка форм.
  • Пользователи информационной базы (в ограниченном объеме).

Ограничения реализованных механизмов описаны в документации.

Данная функциональность не поддерживалась на мобильной платформе.Расширены возможности управления интерфейсом прикладного решения.
В документации данное изменение описано здесь, здесь, здесь и здесь.
Работа с базой данных.
Реализован метод глобального контекста УдалитьДанныеИнформационнойБазы().Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможным удалять все данные информационной базы.
Средства разработки.
Реализована возможность из конфигуратора взаимодействовать с Android Debug Bridge (adb). Стало возможно из конфигуратора запускать мобильное приложение на эмуляторе мобильного устройства или на подключенном к компьютеру физическом устройстве.Данная возможность не предоставлялась.Облегчена разработка и отладка мобильного приложения для ОС Android.
В документации данное изменение описано здесь, здесь и здесь.
Работа с Интернет.
Работа с телефонией.
Реализованы возможности:
  • Отправки и получения электронной почты с помощью встроенного почтового клиента мобильного устройства. Реализован объект СредстваПочты.
  • Отправки и получения SMS- и MMS-сообщений. Реализован объект SMSСообщение.
  • Набора телефонного номера. Реализован объект СредстваТелефонии.
  • Получения доступа к журналу звонков с возможностью установки отбора по виду звонков (исходящие, входящие, пропущенные). Реализован объект ЖурналЗвонков.

Ограничения работы со средствами телефонии на поддерживаемых мобильных операционных системах описаны в документации. +

Предоставлялась ограниченная возможность отправки SMS-сообщений и выполнения звонков с помощью специальных параметров методов ЗапуститьПриложение() или ПерейтиПоНавигационнойСсылке().

Доступ к журналу звонков и возможности получения и отправки электронной почты с помощью встроенного почтового клиента не предоставлялся. +

Стало возможно получить более удобный доступ к специфическим возможностям мобильных устройств: SMS/MMS, журнал звонков, осуществление звонков.
В документации данное изменение описано здесь, здесь и здесь.
Системные требования.
Реализовано свойство конфигурации ТребуемыеРазрешенияМобильногоПриложения, которое позволяет указывать, какие разрешения будут требоваться мобильным приложением на ОС Android:
  • Мультимедиа;
  • Геопозиционирование;
  • Работа с контактами;
  • Работа с календарем;
  • Доступ к телефонии.

Установленные разрешения используются сборщиком мобильных приложений.

Данная возможность не предоставлялась.Позволяет более четко описывать необходимые разрешения для мобильных приложений.
В документации данное изменение описано здесь.
Средства мультимедиа.
Реализована возможность получения штрихкода с помощью встроенной камеры мобильного устройства.

Для объекта СредстваМультимедиа реализованы методы ПоддерживаетсяСканированиеШтрихКодов(), ПоказатьСканированиеШтрихКодов(), ЗакрытьСканированиеШтрихКодов().

Данная возможность не предоставлялась.Расширены возможности мобильной платформы.
В документации данное изменение описано здесь.
Средства разработки.
Для конфигуратора реализована возможность редактировать картинки c вариантами. Реализована возможность конвертировать картинку в картинку с вариантами и обратно.Имелась возможность только загружать картинки с вариантами, без возможности редактирования.Упрощена работа с картинками, необходимыми для создания мобильных приложений.
В документации данное изменение описано здесь.
Доступ к возможностям мобильного устройства.
Реализован доступ к списку контактов мобильного устройства, как локального, так и связанного с конкретной учетной записью. Реализованы объекты МенеджерКонтактов, ДанныеКонтакта, ДанныеКонтактаУчетнойЗаписи, ЛокальныйКлючКонтакта, УчетнаяЗаписьКонтактов, ЭлементДанныхКонтакта, ЭлементДанныхКонтактаМгновенныеСообщения.Данная возможность не предоставлялась.Предоставлен доступ к списку контактов мобильного устройства.
В документации данное изменение описано здесь.
Доступ к возможностям мобильного устройства.
Реализован доступ к календарю мобильного устройства, связанного с конкретной учетной записью. Реализованы объекты МенеджерКалендарей, УчетнаяЗаписьКалендарей, ЛокальныйКлючКалендаря, ЛокальныйКлючСобытийКалендаря, ДанныеСобытияКалендаря, ДанныеСобытияКалендаряУчетнойЗаписи, ДанныеКалендаря, ДанныеКалендаряУчетнойЗаписи.Данная возможность не предоставлялась.Предоставлен доступ к данным календарей мобильного устройства.
В документации данное изменение описано здесь.
Геопозиционирование.
Для объекта ДанныеАдреса реализовано свойство СтрокаАдреса, содержащее фрагмент адреса, начиная с улицы.Данная возможность не предоставлялась.Объект ДанныеАдреса стал более универсальным и может использоваться не только для нужд геопозиционирования, но и для хранения различной контактной информации.
Средства разработки.
В список файлов архива mobile.zip, с помощью которого распространяется мобильная платформа, добавлен файл version.txt, который содержит номер версии мобильной платформы, расположенной в этом файле.Данная возможность не предоставлялась.Упрощено определение версии мобильной платформы, в том числе при использовании прикладного решения сборки мобильного приложения.
Сборщик мобильных приложений.
Доработан сборщик мобильных приложений, поставляемый в составе мобильной платформы:
  • Для сборки более не используется временный каталог пользователя. Для сборки используется явно задаваемый каталог, путь к которому должен включать только символы ASCII.
  • Запоминается (и отображается) дата сборки мобильного приложения.
  • Реализована возможность выгрузить на диск графическую информацию и мобильную конфигурацию.
  • При загрузке мобильной платформы версии 8.3.5 получение номера версии производится автоматически, из файла version.txt, входящего в состав дистрибутива мобильной платформы (файл mobile.zip).
  • Для сборки мобильного приложения для ОС Android требуется Android SDK версии 17 и выше.
  • Реализована проверка на полноту файла с графической информацией (в том числе и в момент загрузки).
  • Для файла с графической информацией реализована поддержка иконки для устройств с высокой плотностью точек экрана (размером 144 на 144 точки, имя файла Android\icon-144x144.png).
  • Реализованы другие доработки.
Сборщик мобильных приложений:
  • Использовал временный каталог пользователя для сборки мобильного приложения, что приводило к невозможности сборки мобильного приложения для ОС Android в том случае, если имя пользователя, от имени которого выполнялась сборка, содержало в себе не только символы ASCII.
  • Не фиксировалась дата сборки мобильного приложения.
  • Было невозможно выгрузить на диск графическую информацию и мобильную конфигурацию.
  • Для сборки мобильного приложения требовался установленный Android SDK строго 17 версии.
  • Мобильная платформа не поддерживала иконки для устройств с высокой плотностью точек экрана для ОС Android.
Повышено удобство работы со сборщиком мобильных приложений.
Клиентское приложение.
При запуске мобильной платформы надпись, отображаемая на заставке при запуске «1С:Предприятия», переведена на все языки локализации.При запуске мобильной платформы надпись «1С:Предприятие» на заставке выводилась только на русском языке.Устранено незапланированное поведение системы.
Общие объекты.
Реализована возможность запускать внешние приложения на мобильном устройстве и получать результат работы этих приложений. Возможность доступна только под управлением ОС Android.

Реализованы объекты ЗапускПриложенияМобильногоУстройства, ДополнительныеДанныеЗапускаПриложенияМобильногоУстройства.

Данная возможность не предоставлялась.Упрощена интеграция прикладного решения с различными приложениями на мобильном устройстве, в том числе с возможностью получать результат работы внешнего приложения.

Возможность доступна только под управлением ОС Android.

Средства разработки.
При сборке проекта Xcode реализована установка атрибута «исполняемый» для файла 1cem, входящего в состав проекта.При сборке проекта Xcode не изменялись атрибуты файла 1cem, входящего в состав проекта.Устранена проблема, возникающая в том случае, если файл проекта был переформирован на операционных системах семейства Windows, что приводило к очистке атрибута «исполняемый» у файла 1cem.
Отображение информации.
Сборщик мобильных приложений.
В мобильной платформе реализованы графические ресурсы для устройств iPhone 6 и iPhone 6 Plus:
  • заставки: 750x1334, 2208x1242, 1242x2208;
  • иконки: 87x87, 180x180.

Для сборщика мобильных приложений реализована поддержка графических ресурсов, используемых для устройств iPhone 6 и iPhone 6 Plus.

Мобильная платформа и сборщик мобильных приложений не поддерживали работу с графическими ресурсами, необходимыми для устройств iPhone 6 и iPhone 6 Plus.Реализована поддержка новых мобильных устройств компании Apple.

Оглавление

Переход с предыдущей версии на версию 8.3.5

Оглавление

Версия 8.3.4

Версия 8.3.4 включает исправления обнаруженных ошибок и изменения в функциональности. +

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.3. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16, 8.3.1 и 8.3.2. +Возможность запуска конфигураций, разработанных в версии 8.3.3 и более младших, в версии 8.3.4, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.4 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.4, при необходимости, использовать для работы с информационной базой и версию 8.3.3. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
Общие объекты.
Для методов Добавить() и Вставить() объекта ЭлементыПакетаОтображаемыхДокументов реализован необязательный параметр АдресДокумента, с помощью которого можно указать адрес временного хранилища, в котором расположен сохраняемый документ.Данная возможность не предоставлялась.Формировать пакет документов для сохранения или печати стало более удобно.
Табличный документ.
Реализовано сохранение табличного документа в формате HTML 5. При этом диаграммы и примитивные рисунки сохраняются в формате SVG, а также поддерживается вывод текста под углом.Данная возможность не предоставлялась.Стало возможно сохранять табличные документы в формате HTML 5.
Фоновые и регламентные задания.
При использовании параметра Параметры метода Выполнить() объекта ФоновыеЗадания (а также свойства Параметры объекта РегламентноеЗадание) реализована возможность не указывать завершающие параметры, для которых у метода, реализующего фоновое (или регламентное) задание, определены значения по умолчанию.В том случае, если при запуске фонового (или регламентного) задания не указывались завершающие параметры, для которых были определены значения по умолчанию, вызывалось исключение.Стало возможно добавлять в методы, реализующие фоновые (или регламентные) задания, завершающие параметры, если для добавленных параметров заданы значения по умолчанию. В этом случае не придется дорабатываться все места создания фоновых (или регламентных) заданий.
Средства разработки.
В редакторе модулей конфигуратора реализованы следующие возможности:
  • Выделение всех вхождений идентификатора, «внутри» которого находится курсор редактора текстов;
  • Выделение всех вхождений идентификатора, выделенного двойным щелчком мыши по идентификатору;
  • Выделение парных конструкций встроенного языка (включая скобки), например Процедура ... КонецПроцедуры, Если ... КонецЕсли и т.д.

Выделение идентификаторов по умолчанию отключено и требует отдельной настройки с помощью диалога параметров конфигуратора.

В конфигураторе, толстом и тонком клиентах, при поиске, реализовано выделение выражения поиска. +

Данные возможности не предоставлялись.Улучшены возможности редактора встроенного языка.
Внешние источники данных.
При работе с внешними источниками данных реализована поддержка всех возможностей языка запросов для СУБД MySQL.

Для свойства СУБД объекта ПараметрыСоединенияВнешнегоИсточникаДанных реализовано значение MySQL.

Для свойства DBMS события EDS технологического журнала реализовано свойство DBMySQL.

Внешние источники данных не поддерживали реализацию всех возможностей языка запросов при работе с СУБД MySQL.Стала возможной работа с динамическими списками, временными таблицами и другими возможностями в том случае, если внешний источник данных расположен на СУБД MySQL.
Интерфейс.
Реализована возможность управлять составом интерфейса клиентского приложения из встроенного языка.

Реализованы объекты НастройкиСоставаИнтерфейсаКлиентскогоПриложения, ГруппаНастройкиСоставаИнтерфейсаКлиентскогоПриложения, ЭлементНастройкиСоставаИнтерфейсаКлиентскогоПриложения. Вызов метода глобального контекста ОбновитьИнтерфейс() перестраивает панели интерфейса в соответствии с настройками из системного хранилища настроек.

Для объекта НастройкиИнтерфейсаКлиентскогоПриложения реализован конструктор и методы ПолучитьСостав(), УстановитьСостав(). +

Объект НастройкиИнтерфейсаКлиентскогоПриложения позволял хранить изменения настроек клиентского приложения относительно настроек, выполненных в конфигураторе.

Программное управление интерфейсом не поддерживалось.

Возможность программного управления составом и положением панелей интерфейса клиентского приложения.
Автоматизированное тестирование.
Для объекта ТестируемоеПолеФормы реализован метод ОжидатьФормированияВыпадающегоСписка().Данная возможность не предоставлялась.Появилась возможность ожидать формирование выпадающего списка в тех случаях, когда его формирование занимает существенное время.
Интерфейс.
Реализована возможность использования насыщенных форм в интерфейсе Такси без их (форм) существенной переработки.

Для управляемой формы реализовано свойство Вариант масштаба, которое недоступно, если свойство конфигурации Режим совместимости интерфейса установлен в значение Версия 8.2. Во встроенном языке свойство не доступно. Данное свойство позволяет изменить масштаб одной формы.

Для объекта НастройкиКлиентскогоПриложения реализовано свойство ВариантМасштабаФормКлиентскогоПриложения. Данное свойство предназначено для изменения масштаба сразу всех форм прикладного решения для конкретного пользователя.

Данная возможность не предоставлялась.

Не существовало простого способа быстро сделать форму более компактной.

Появилась возможность (на переходный период) управлять размером элементов управляемых форм при работе в интерфейсе Такси без переработки формы.

Существует возможность изменять как масштаб одной формы (которую пока не переработали для работы в интерфейс Такси), так и масштаб всего приложения в том случае, если, например, прикладное решение выполняется на мониторе с небольшим разрешением или размером.

Масштаб одной формы изменяется в конфигураторе, а масштаб приложения задается в настройках конкретного пользователя.

Управляемая форма.
Реализована возможность передачи дополнительных параметров (не являющихся отбором или стандартными параметрами) в форму создания нового объекта, при вызове создания из поля ввода управляемой формы. Форма выбора обеспечивает хранение и дальнейшую передачу этих дополнительных параметров в форму создания нового элемента. Дополнительные параметры задаются в параметрах выбора и связях параметров выбора с помощью особой формы именования параметра (имя параметра должно начинаться на префикс Дополнительно.). Такие параметры: при вызове создания в поле ввода непосредственно передаются в форму создания, а при вызове выбора из списка в поле ввода сначала передаются в форму списка, а при вызове в ней создания, передаются в форму создания.

Реализован стандартный параметр ДополнительныеПараметры (типа Структура) расширений управляемых форм для объектов, справочников, документов, планов видов характеристик, бизнес-процессов, задач и динамических списков.

Для расширения таблицы динамического списка реализовано свойство ДполнительныеПараметрыСоздания (типа ФиксированнаяСтруктура).

+

Обеспечивалась возможность передачи из поля ввода значений отбора, которые использовались в форме создания нового элемента в качестве значений заполнения. Возможность передачи дополнительных параметров отсутствовала.Стало возможно передавать дополнительные параметры (не параметры отбора) при вызове формы создания непосредственно из поля ввода.
Управляемая форма.
Реализована возможность управлять появлением истории у полей ввода, связанных с данными типа справочник, документ, бизнес-процесс, задача, план видов характеристик, план видов расчета, план счетов и план обмена.

Использование истории задается с помощью свойства ИсторияВыбораПриВводе у объекта конфигурации, реквизита объекта конфигурации и элемента формы.

Данная возможность не предоставлялась.Имеется возможность отключения истории у полей ввода, если эта возможность является излишней с точки зрения прикладной логики.
Управляемая форма.
Реализована возможность задавать минимальную ширину выпадающего списка для полей ввода управляемой формы с помощью свойства ШиринаВыпадающегоСписка. Итоговая ширина списка получается как минимальное значение между значением свойства и фиксированной шириной (40 символов).Выпадающий список для поля ввода имел фиксированную ширину в 40 символов.Появилась возможность увеличивать ширину выпадающего списка в тех случаях, если список содержит длинные строки.
Хранилище конфигурации.
Для пакетного режима запуска конфигуратора реализованы следующие возможности:
  • Создание хранилища конфигурации (ключ командной строки запуска /ConfigurationRepositoryCreate);
  • Создание пользователя хранилища конфигурации (ключ командной строки запуска /ConfigurationRepositoryAddUser);
  • Копирование пользователей из другого хранилища конфигурации (ключ командной строки запуска /ConfigurationRepositoryCopyUsers);
Данная возможность не предоставлялась.

Создание нового хранилища конфигурации и нового пользователя могло быть выполнено в интерактивном режиме администратором хранилища.

Появилась возможность автоматизировать административные операции при работе с хранилищем конфигурации, в том числе, возможность автоматического создания отдельных хранилищ для независимо разрабатываемых частей проекта.
Динамический список.
Журнал документов.
Для журналов документов реализована возможность размещения на форме команды создания, параметризуемой типом создаваемого документа. Для динамического списка, у которого в качестве основной таблицы установлена таблица журнала документов, возможно автоматическое формирование кнопки создания нового документа, содержащей подменю с перечнем доступных данному пользователю документов.

Для расширения таблицы формы для динамического списка реализована стандартная команда СоздатьПоПараметру.

Для элемента формы Кнопка реализовано свойство Параметр, доступный только в том случае, если кнопка связан с командой СоздатьПоПараметру.

Для обработчика события ПередНачаломДобавления таблицы формы реализован параметр Параметр, который служит для передачи в обработчик события значения типа создаваемого документа.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

В динамическом списке, для которого в качестве основной таблицы установлен журнал документов, была доступна только одна кнопка Создать (без подменю), после нажатия которой открывался диалог выбора вида создаваемого документа. При этом тип, описывающий создаваемый документ, не передавался в обработчик события ПередНачаломДобавления таблицы формы, связанной с динамическим списком.Для журналов документов, содержащих небольшое количество типов документов, стало возможным упростить создание нужного вида документа. Также стало возможным быстро и просто создавать на командной панели формы отдельные кнопки для создания конкретного документа.
Кластер серверов.
Для сервера «1С:Предприятия» реализованы лицензии с ограниченным количеством одновременно обслуживаемых сеансов клиентских приложений. Ограничение распространяется на следующие сеансы:
  • Конфигуратор (кроме случая создания информационной базы);
  • Тонкий клиент;
  • Веб-клиент;
  • Толстый клиент;
  • Внешнее соединение.

Лицензия может быть активирована как 32- так и 64-разрядной версией сервера. В кластере серверов, работающим с такой лицензией, не может быть создано более одного рабочего сервера.

Информация о выпуске содержится в информационном выпуске № 17577 от 05.12.2013 (см. здесь).

Данная возможность не предоставлялась.

Сервер «1С:Предприятия» не имел ограничений по количеству одновременно работающих пользователей.

Расширен спектр вариантов поставляемых лицензий сервера «1С:Предприятия». Появилась поставка, ориентированная на использование сервера на небольших предприятиях и в отдельных филиалах.
Работа с Интернет.
Для тонкого клиента включена поддержка протокола TLS начиная с «1С:Предприятие» версии 8.3.4.428.

Для тонкого клиента реализован ключ командной строки запуска /HttpsForceSSLv3, который «заставляет» систему не использовать протокол TLS (при подключении через веб-сервер), даже если веб-сервер поддерживает этот протокол.

Поддержка TLS в «1С:Предприятии» версии 8.3.4.408 (и ниже) и 8.2.19 была отключена.Стало возможно использовать протокол TLS в тех случаях, когда это необходимо или желательно.
Национальные установки.
Реализована поддержка следующих кодов локализации (монгольский язык):
  • mn - монгольский;
  • mn_Cyrl - монгольский (кириллица);
  • mn_MN - монгольский (Монголия);
  • mn_Mong - монгольский (Монгольская);
  • mn_Mong_CN - монгольский (Монгольская, Китая).
Не поддерживались коды локализации для монгольского языка.Не происходит аварийного завершения работы при попытке запуска «1С:Предприятия» на компьютере с монгольскими национальными настройками.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Веб-клиент.
Уточнены формулировки в диалоге установки расширения 1C:Enterprise Extension для веб-браузера Mozilla Firefox - пользователю предлагается установить расширение.В диалоге установки расширения пользователю предлагалось включить расширение.Более четко разделяется процесс установки собственно расширения и процесс разрешения работы установленного расширения веб-браузера.
Обработка ошибок.
Расширены возможности формирования дампа аварийного завершения работы системы. Дамп будет сформирован даже в том случае, если в процессе обработки исключения, перехваченного специальным механизмом платформы, произошло новое исключение.Если в процессе обработки исключения произошло другое исключение - дамп аварийного завершения работы не формировался.Уменьшено количество аварийных ситуаций, которые невозможно расследовать по дампу аварийного завершения работы системы.
Клиентское приложение.
В веб-клиенте доработаны следующие системные управляемые формы:
  • Диалог выбора шрифта;
  • Диалог поиска и замены в табличном документе;
  • Диалог показателей производительности.

Во всех управляемых системных формах кнопка Справка размещается на командной панели, а не в меню Еще (Все действия).

Системные управляемые формы выглядели по-другому.Исправлены недочеты в системных управляемых формах.
Работа с Интернет.
Клиентское приложение.
Реализована поддержка веб-браузера Microsoft Internet Explorer 11.Веб-браузер Microsoft Internet Explorer 11 не поддерживался.Реализована поддержка новой версии веб-браузера компании Microsoft.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Оптимизирована проверка измененности конфигурации.

Ускорено выполнение операций, которые в процессе своего выполнения проверяют измененность конфигурации:

  • Метод КонфигурацияИзменена();
  • Запуск клиентского приложения «1С:Предприятия»;
  • Чтение изменений с помощью метода ПрочитатьИзменения() менеджера плана обмена.
Проверка измененности конфигурации выполнялась недостаточно эффективно.

Повысилась скорость работы проверки измененности конфигурации. +

Веб-клиент.
Ускорена работа веб-клиента в интерфейсе Такси при большом количестве открытых форм.Скорость работы веб-клиента в интерфейсе Такси при большом количестве открытых форм была недостаточной.Повышена скорость работы веб-клиента при использовании интерфейса Такси.
Кластер серверов.
Прикладные объекты.
В клиент-серверном варианте снижено влияние сервиса нумерации на время начала и завершения транзакций, даже если в транзакции не используется сервис нумерации.

В клиент-серверном варианте оптимизирована работа сервиса нумерации при большом количестве префиксов.

В клиент-серверном варианте сервис нумерации оказывал негативное влияние на начало и завершение транзакций, даже если в транзакции не использовался этот сервис.

В клиент-серверном варианте сервис нумерации работал недостаточно быстро в случае использования большого количества префиксов.

Повышена эффективность работы клиент-серверного варианта при активном использовании сервиса нумерации с большим количеством префиксов, например в информационных базах с большим количеством областей.
Управляемая форма.
В тонком и толстом клиентских приложениях повышена производительность поля ввода со свойством Многострочный режим, установленным в значение Да, в случае работы с большим многострочным текстом.Производительность поля ввода при работе с большим многострочным текстом была недостаточной.Повышена реактивность работы системы при редактировании больших многострочных текстов в поле ввода.
Хранилище конфигурации.
Для хранилища конфигурации, не использующего режим совместимости:
  • Ускорено открытие конфгурации, подключенной к хранилищу;
  • Ускорено подключение к хранилищу;
  • Ускорено помещение объектов в хранилище;
  • Ускорено обновление конфигурации из хранилища, получение объектов, отмена захвата объекта в хранилище;
  • Увеличена параллельность помещения объектов в хранилище несколькими пользователями.
Указанные операции выполнялись недостаточно эффективно.Улучшена работа с хранилищем конфигурации.
Веб-клиент.
С целью повышения производительности, в веб-браузере Microsoft Internet Explorer 8, в элементах управления не выводятся скругленные рамки.В веб-браузере Microsoft Internet Explorer 8 в элементах управления выводятся скругленные рамки.Повышена производительность при работе в веб-браузере Microsoft Internet Explorer 8.
Работа в ОС Linux.
В некоторых сценариях оптимизирована работа Linux-клиента.В некоторых сценариях Linux-клиент работал недостаточно эффективно.Повышение эффективности работы Linux-клиента.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Прикладные объекты.
При реструктуризации информационной базы выполняется проверка наличия в планах обмена реквизитов объекта и табличных частей с зарезервированными именами: Ссылка, Код, Наименование, ПометкаУдаления, ЭтотОбъект, ВерсияДанных, ДополнительныеСвойства, НомерОтправленного, НомерПринятого, Ref, Code, Description, ThisObject, DataVersion, AdditionalProperties, SentNo, ReceivedNo. Выполнить реструктуризацию информационной базы будет невозможно, если у планов обмена будут существовать реквизиты с такими именами.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

При выполнении реструктуризации информационной базы не выполнялась проверка наличия у планов обмена реквизитов с зарезервированными именами.Устранено незапланированное поведение системы, приводящее к различным ошибкам.
Прикладные объекты.
При установке параметра Отказ обработчика ОбработкаПроверкиЗаполнения() в значение Истина, происходит прерывание исполнения подписок на событие ОбработкаПроверкиЗаполнения для следующих объектов: справочники, документы, наборы записей регистров (включая механизм перерасчетов), последовательности документов, планы видов характеристик, планы счетов, планы видов расчета, планы обмена, бизнес-процессы и задачи.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Выполнение подписок на событие ОбработкаПроверкиЗаполнения не прерывалось в том случае, если в модуле объекта параметр обработчика Отказ устанавливался в значение Истина.Устранено незапланированное поведение системы.
Общие реквизиты / Разделение данных.
Управляемые блокировки.
При записи и удалении данных в сеансе с неиспользуемыми разделителями, управляемая блокировка устанавливается не только по ссылке и явно указанным полям, но и по общим реквизитам, являющимися разделителями, в состав которых входит записываемый или удаляемый объект.

Реализована возможность использования общих реквизитов, не являющихся разделителями, в свойстве объекта конфигурации ПоляБлокировкиДанных.

Общие реквизиты, которые являются разделителями в режиме Независимо и совместно, не могут быть выбраны в список реквизитов ПоляБлокировкиДанных. Реализована возможность указывать такие реквизиты в качестве имени пространства блокировок объекта БлокировкаДанных. Система вызовет исключение в том случае, если в объекте БлокировкаДанных используется значение разделителя, отличное от значения, используемого в сеансе.

Изменения реализованы для следующих объектов:

  • Справочники;
  • Документы;
  • Планы видов характеристик;
  • Планы счетов;
  • Планы видов расчета;
  • Планы обмена;
  • Бизнес-процессы;
  • Задачи;
  • Константы.
При записи и удалении данных в сеансе с неиспользуемыми разделителями, управляемая блокировка устанавливается только по ссылке и явно указанным полям.

Использование общих реквизитов, не являющихся разделителями, в свойстве объекта конфигурации ПоляБлокировкиДанных было недоступно. Для таких общих реквизитов не поддерживалось использование их в качестве имен пространств блокировки объекта БлокировкаДанных.

Уменьшилось количество необоснованных конфликтов блокировок. Стало возможным из сеанса, в котором не используются разделители, изменять данные в произвольных областях данных в том случае, если в других областях установлены блокировки на пространство блокировок, к которому относятся изменяемые данные.

Например, в области О1 установлена блокировка на справочник Товары. Допустимо изменение данных для любых областей, где значение разделителя не равно значению О1.

Табличный документ.
При сохранении табличного документа в формат PDF, диаграммы (объекты Диаграмма, ДиаграммаГанта, Дендрограмма) сохраняются в векторном формате.При сохранении табличного документа в формате PDF, диаграммы сохранялись в виде растрового изображения.Уменьшен размер получающегося файла формата PDF, диаграмма масштабируется при изменении области отображения файла в программе просмотра файла PDF.
Хранилище конфигурации.
Реализовано хранение истории комментариев, которые вводят пользователи при помещении объектов в хранилище конфигурации. В истории хранится 20 последних комментариев. Комментарий может быть введен (и сохранен в истории) при захвате объекта в хранилище, а при помещении - выбран из истории.Комментарии, вводимые при помещении объекта(ов) в хранилище конфигурации, не сохранялись в истории.Упрощено многократное помещение объекта(ов) конфигурации в хранилище конфигурации, связанное с одной задачей, например, когда реализация какой-либо возможности прикладного решения помещается в хранилище в несколько приемов.
Права доступа.
Реализована возможность указывать несколько ролей, которые будут использоваться при определении прав доступа при пустом списке пользователей.

Реализовано свойство конфигурации ОсновныеРоли. Свойство ОсновнаяРоль поддерживается для совместимости. При отключенном режиме совместимости обращение к свойству ОсновнаяРоль вызывает исключение.

В режиме совместимости с версией 8.3.3 допускается указание только одной роли в свойстве ОсновныеРоли.

В качестве основной роли могла использоваться только одна роль.Позволяет упростить разработку прикладных решений, которые могут использовать как с указанием пользователей, так и с пустым список пользователей.
Прикладные объекты.
Для объектов конфигурации, которые могут содержать предопределенные данные, реализована возможность устанавливать свойство ИмяПредопределенныхДанных в значение специального вида, состоящее из символа # и текстового представления уникального идентификатора.Установка значения свойства ИмяПредопределенныхДанных была возможна только в режиме загрузки (свойство ОбменДанными.Загрузка установлено в значение Истина).Стало возможным загружать предопределенные данные из файлов произвольных форматов.
Автоматизированное тестирование.
Для элементов журнала действий пользователя, формируемых при работе с полями, кнопками, группами, таблицами и декорациями управляемой формы, реализован атрибут name, который содержит имя используемого элемента формы.

В обработке преобразования журнала действий пользователя в сценарий на встроенном языке (см. здесь) реализован переключатель, управляющий тем, как будет реализован поиск элемента формы: по представлению или по имени.

В журнал действий пользователя записывались представления элементов формы.

В обработке преобразования журнала действий пользователя в сценарий на встроенном языке выполнялся поиск элемента формы только по представлению элемента.

Поведение механизма автоматизированного тестирования стало более стабильным. При поиске элементов формы стало возможно опираться на имя элемента, что уменьшает зависимость работоспособности теста от языка локализации, ошибок в написании представления, уникальности представления элемента и т.д.
Табличный документ.
Печать табличного документа выполняется в масштабе, который указан в параметрах печати.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

На некоторых принтерах документ печатался с двукратным применением масштаба печати.Устранено незапланированное поведение системы при печати документов с масштабом, отличным от 100%.
Динамический список.
В отборах динамического списка реализована возможность использовать поля табличных частей объектов, используемых в запросе формирования динамического списка.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Поля табличных частей объектов было невозможно использовать в отборах динамических списков.Расширены возможности работы с динамическим списком.
Динамический список.
При получении данных динамического списка выполняется удаление настроек динамического списка, которые отключены функциональными опциями.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Настройки, отключенные функциональными опциями, не удалялись из списка настроек динамического списка.Устранено незапланированное поведение системы.
Интерфейс.
Изменен цвет панели разделов и панели команд текущего раздела в интерфейсе Такси.

Для панели команд текущего раздела в вертикальном расположении не отображается заголовок панели. Представление панели команд текущего раздела изменено на панель функций текущего раздела.

Панель разделов и панель команд текущего раздела в интерфейсе Такси имели другой цвет.

Для панели команд текущего раздела в вертикальном расположении отображался заголовок панели.

Повышен комфорт работы с интерфейсом Такси.
Средства разработки.
Хранилище конфигурации.
Реализована возможность быстрого просмотра выборочной истории изменения объектов конфигурации. Данная возможность доступна при работе с хранилищем и из окна сравнения и объединения конфигураций.

Просмотр выборочной истории реализовано для следующих объектов: модуль, макет, картинка, WS-ссылка, расписание, агрегаты регистра, состав плана обмена, стиль, рабочая область основного раздела, карта маршрута, форма, справочная информация, предопределенные элементы, фрагмент командного интерфейса, права роли.

Для вызова команды просмотра выборочной истории в контекстном меню диалогов работы с хранилищем и окна сравнения конфигураций реализована команда Выборочная история объекта.

Для диалога Отбор версий реализована возможность отбора по свойствам выбранных объектов конфигурации. +Просмотр выборочной истории объектов конфигурации возможно только для версий объектов, помещенных в хранилище конфигурации с помощью «1С:Предприятия» версии 8.2.9 и более старшей.

Данная возможность не предоставлялась.

Можно было получить только полную историю изменений объекта конфигурации.

Повышен комфорт работы с хранилищем конфигурации. Упрощен процесс просмотра истории какой-либо составной части объекта конфигурации.
Средства публикации веб-клиента и Web-сервисов.
Для диалога публикации веб-клиента и Web-сервисов (в конфигураторе) реализована:
  • Возможность управления исполнением фоновых заданий в файловом варианте (атрибут allowexecutescheduledjobs элемента ws);
  • Возможность управления доступностью Web-сервисов по умолчанию (атрибут pointEnableCommon элемента ws).
Управление возможностью исполнения фоновых заданий в файловом варианте и доступностью Web-сервисов по умолчанию было доступно только при публикации с помощью утилиты webinst по шаблону. Диалог публикации не давал доступа к управлению данными возможностями.Интерактивная публикация позволяет задавать все параметры файла default.vrd.
Табличный документ.
Для расширения поля формы для табличного документа реализовано свойство РежимМасштабированияПросмотра, позволяющее указывать, в каком виде будет отображаться табличный документ: как в версии 8.2 или в увеличенном виде.Данная возможность не предоставлялась.

При использовании нестандартных (увеличенных) размеров шрифтов, такие отчеты в интерфейсе Такси выглядели очень крупно.

+

Появилась возможность управлять масштабом отображения табличных документов, использующих нестандартные шрифты.
Динамический список.
В динамическом списке поля представлений недоступны для использования в отборе, группировке и сортировке. Также по полям представления невозможно выполнять поиск.В динамическом списке поля представлений можно было использовать для использования в отборе, группировке и сортировке. По полям представления можно было выполнять поиск.Устранено незапланированное поведение системы.
Внешние источники данных.
Система компоновки данных.
Работа с запросами.
При работе с внешними источниками данных реализована возможность использования функций, описанных во внешних источниках данных. Функция может возвращать одно значение, таблицу или не возвращать значений вовсе. Реализована возможность указывать вид таблицы внешнего источника данных - таблица или выражение (для описания функций, возвращающих таблицу).

Для обращения к функциям внешнего источника данных из языка запросов используется один из синтаксисов:

  • ВнешнийИсточникДанных.<Имя источника>.Таблица.<Имя табличной функции>(<Параметр 1>,...,<Параметр N>);
  • ВнешнийИсточникДанных.<Имя источника>.<Имя функции>(<Параметр 1>,...,<Параметр N>);

Обращение к функциям с помощью объектной модели возможно с помощью менеджера внешнего источника данных или менеджера таблицы внешнего источника данных.

В библиотеке картинок реализована картинка ВнешнийИсточникДанныхФункция (ExternalDataSourceFunction).

Использование функций при работе с внешними источниками данных было невозможно.Расширение возможностей при работе с внешними источниками данных.
Система компоновки данных.
При указании в качестве параметра ОтборЗаписей функций ВычислитьВыражениеСГруппировкойМассив(), ВычислитьВыражениеСГруппировкойТаблицаЗначений() агрегатной функции будет диагностироваться ошибка.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Использование агрегатной функции в параметре ОтборЗаписей функций ВычислитьВыражениеСГруппировкойМассив(), ВычислитьВыражениеСГруппировкойТаблицаЗначений() не диагностировалось как ошибка.Устранено незапланированное поведение системы.
Веб-клиент.
При работе в веб-браузере Microsoft Internet Explorer 10 удалена системная кнопка Очистка поля ввода в поле ввода управляемой формы.Системная кнопка Очистка поля ввода в веб-браузере Microsoft Internet Explorer 10 работала аналогично кнопке Очистка, формируемой платформой.Устранено различие во внешнем виде веб-клиента между веб-браузером Microsoft Internet Explorer 10 и другими веб-браузерами.
Хранилище конфигурации.
Команда Обновить конфигурацию из хранилища выполняется без формирования диалогового окна в случае обнаружения в хранилище новых объектов. Новые объекты создаются в целевой конфигурации автоматически.Команда Обновить конфигурацию из хранилища открывала диалоговое окно в случае обнаружения в хранилище новых объектов. При выполнении обновления с помощью пакетного режима запуска конфигуратора обновление не выполнялось при обнаружении в хранилище новых объектов.Стало возможно автоматически (например, из командного файла) обновлять конфигурацию прикладного решения из хранилища для выполнения различных регламентных задач, например, для выполнения автоматизированного тестирования. Теперь операция обновления конфигурации из хранилища не требует интерактивных действий, которые могут приводить к остановке исполнения командного файла.
Интерфейс.
Изменен внешний вид заставки для всех видов клиентов и конфигуратора: вместо тени реализована рамка.У заставки присутствовала тень.Исправлены проблемы с отрисовкой заставки в ряде случаев.
Общие объекты.
При выполнении проверки конфигурации и перед выполнением операции сохранения конфигурации выполняется проверка того, что состав определяемого типа допустим в каждом месте использования такого типа. Проверка выполняется в том случае, если свойство конфигурации Режим совместимости установлено в значение Версия 8.3.3 или Не использовать. Если установлен режим совместимости младше, чем Версия 8.3.3, то проверяется только невозможность указания в составе определяемого типа функций внешнего источника данных.

+

Проверка допустимости выбора определяемого типа выполнялась только при формировании диалога выбора типа реквизита объекта конфигурации. При сохранении конфигурации не выполнялась проверка того, что определяемый тип все еще остался допустимым в каждом месте использования определяемого типа.Уменьшено количество потенциально ошибочных ситуаций, возникающих при разработке прикладного решения, содержащего определяемые типы.
Управляемая форма.
Для полей ввода, у которых не указан режим выбора из списка, в режиме совместимости с версией 8.2.16, выпадающий список не содержит список выбора, который установлен для поля ввода.Для полей ввода в версии 8.3.3, выпадающий список всегда содержал список выбора, который был установлен для поля ввода.Не требуется переработка прикладного решения в случае использования его в режиме совместимости с версией 8.2.16.
Стандартные функции.
Общие реквизиты / Разделение данных.
Стандартная обработка удаления помеченных объектов пытается установить монопольный режим для удаления помеченных объектов в том случае, если в конфигурации установлен режим совместимости с версией 8.3.3 и старше (включая значение Не использовать для свойства Режим совместимости).

Если у конфигурации установлен режим совместимости с версией 8.3.2 и младше, монопольный режим устанавливается только в сеансе, где не используется ни один разделитель или в неразделенных конфигурациях.

Стандартная обработка удаления помеченных объектов выполняла установку монопольного режим для удаления помеченных объектов только в том случае, когда удаление выполнялось в сеансе, где не использовался ни один разделитель или для неразделенной конфигурации. Установленный режим совместимости не оказывал влияние на установку монопольного режима.Стало возможно удалять помеченные на удаление объекты в сеансе, где используются разделители.
Прикладные объекты.
Вне зависимости от значения свойства конфигурации Режим автонумерации объектов, реализовано повторное использование автоматически назначенного номера объекта, если произошел откат транзакции, в которой выполнялась запись этого объекта.Если свойство конфигурации Режим автонумерации объектов было установлено в значение Не освобождать автоматически, то не выполнялось повторное использование номера объекта, если произошел откат транзакции, в которой выполнялась запись этого объекта.Устранено незапланированное поведение системы.
Работа с XML, XDTO.
При десериализации информации из форматов XML- или XDTO-сериализации, игнорируются элементы Predefined для табличных частей планов счетов и планов видов расчета. При обнаружении такого элемента ошибки не происходит и данные успешно десериализуются.При попытке десериализации элементов плана счетов или плана видов расчета, наличие элемента Predefined в табличных частях приводило к возникновению исключения и невозможности выполнить десериализацию.Возможность загружать данные, сериализованные в следующих версиях «1С:Предприятия» (версии 8.3.5 и старше).
Используемые компоненты.
Библиотека OpenSSL обновлена до версии 1.0.0m.Использовалась библиотека OpenSSL версии 1.0.0l.Решение проблем с безопасностью в OpenSSL.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Регистры сведений.
Для регистров сведений, у которых включены свойства Разрешить итоги: срез первых или Разрешить итоги: срез последних, из списка полей таблиц среза первых или последних удалены поля Активность и НомерСтроки.

Если свойства Разрешить итоги: срез первых или Разрешить итоги: срез последних отключены, то поля Активность и НомерСтроки присутствуют в таблицах среза первых или последних.

Поля Активность и НомерСтроки всегда присутствовали в списке полей таблицы среза первых/последних регистра сведений.Исключена незапланированная функциональность.

В управляемых формах будут автоматически удалены элементы формы, связанные с полями Активность и НомерСтроки.

Управляемые блокировки.
Исключена возможность устанавливать управляемые транзакционные блокировки (свойство ПоляБлокировкиДанных) по реквизитам объектов следующих типов: строка неограниченной длины, хранилище значений, тип значения характеристики, составные типы, включающие в себя какие-либо из вышеперечисленных типов.

При проверке конфигурации выполняется контроль полей, указанных в списке полей блокировки данных и выдается ошибка, если какое-либо из полей не соответствует ограничениям.

Не рекомендовалось устанавливать управляемую блокировку по реквизитам следующих типов: строка неограниченной длины, хранилище значения, описание типов.

При проверке конфигурации не выполнялся контроль полей, указанных в списке полей блокировки данных.

Исключены ситуации, которые могли привести к потере производительности.

Улучшен контроль за разрабатываемой конфигурацией.

Права доступа.
Функция РольДоступна() генерирует исключение в следующих случаях:
  • В качестве параметра функции передана не строка и не объект конфигурации Роль;
  • Передано имя роли, которая отсутствует в конфигурации.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Функция РольДоступна() не анализировала корректность параметра и возвращала значение Истина даже в том случае, если переданная роль отсутствовала в конфигурации.Устранено неадекватное поведение системы.
Система компоновки данных.
При выполнении компоновки данных из встроенного языка учитывается включенный привилегированный режим при получении списка доступных полей.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

При выполнении компоновки данных из встроенного языка не учитывался факт включения привилегированного режима.При включенном привилегированном режиме появляется возможность использовать в компоновке данных поля, к которым у пользователя нет доступа.
Web-сервисы.
Изменилось соответствие элементов их именам для системного перечисления WSНаправлениеПараметра:
  • Элементу с именем ВходнойВыходной соответствует значение ВходнойВыходной;
  • Элементу с именем Выходной соответствует значение Выходной.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Для системного перечисления WSНаправлениеПараметра использовалось следующее соответствие имени и значения:
  • Элементу с именем ВходнойВыходной соответствует значение Выходной;
  • Элементу с именем Выходной соответствует значение ВходнойВыходной.

Устранено незапланированное и неадекватное поведение системы.
Обмен данными.
Предопределенные данные.
 +

Реализована возможность указывать признак обновления предопределенных данных в целом для информационной базы с помощью встроенного языка или ключей командной строки. В режиме «1С:Предприятие» режим обновления предопределенных данных дополнительно анализирует признак, установленный в целом для информационной базы (дополнительно к признаку, установленному для объектов конфигурации и признаку, установленному в данных и вида информационной базы: центральная/не распределенная информационная база или периферийная информационная база).

Реализованы методы глобального контекста УстановитьОбновлениеПредопределенныхДанныхИнформационнойБазы() и ПолучитьОбновлениеПредопределенныхДанныхИнформационнойБазы().

Реализованы параметр командной строки пакетного режима запуска конфигуратора /SetPredefinedDataUpdate.

В режиме совместимости с версией 8.3.3 поведение не изменилось.

Необходимость обновления предопределенных данных анализировалась на основании признаков, установленных в метаданных и в данных, а также на основании вида информационной базы.Стало возможно корректно и просто задавать признак обновления предопределенных данных в тех случаях, когда информационная база отключается от распределенной системы для проведения восстановительных или регламентных работ. Также стало возможно работать в том случае, если с помощью обмена (не распределенной информационной базы)взаимодействуют два похожих прикладных решения, где предопределенные данные задаются в одной базе, а в другой они должны быть скопированы с помощью обмена.
Прикладные объекты.
При работе в тонком и толстом клиентах для обработчика ПослеЗаписи расширения управляемых форм констант, записи регистра сведений и наборов записей регистров реализован параметр ПараметрыЗаписи. В режиме совместимости с версией 8.3.3 и ниже, данный параметр всегда содержит значение Неопределено.

Для обработчика ПередЗаписью в синтакс-помощник внесена информация о параметре ПараметрыЗаписи.

Для обработчика ПослеЗаписи расширения управляемых форм констант, записи регистра сведений и наборов записей регистров отсутствовал параметр ПараметрыЗаписи.

Для обработчика ПередЗаписью в синтакс-помощнике отсутствовала информация о параметре ПараметрыЗаписи.

Устранение незапланированного поведения.
Динамический список.
Функциональные опции.
Основной реквизит управляемой формы типа Объект (СправочникОбъект, ДокументОбъект и т.д.) будет отключен в том случае, если функциональной опцией отключен соответствующий объект конфигурации.

Основной реквизит управляемой формы типа ДинамическийСписок будет отключен в том случае, если функциональной опцией отключен объект конфигурации, который указан в качестве основной таблицы динамического списка.

В обоих случаях анализируются только те функциональные опции, которые не имеют параметров.

В версии 8.2 основной реквизит формы типа Объект не отключался даже если функциональной опцией (любой) был отключен соответствующий объект конфигурации.

В версии 8.3 основной реквизит формы типа Объект отключался, если функциональной опцией был отключен соответствующий объект конфигурации. При этом анализировались все функциональные опции.

В предыдущих версиях «1С:Предприятия» основной реквизит типа ДинамическийСписок отключался в том случае, если функциональной опцией был отключен объект конфигурации, который указан в качестве основной таблицы динамического списка. При этом анализировались все функциональные опции.

Поведение системы стало более единообразным и корректным. В частности, теперь невозможна следующая ситуация:
  • При редактировании формы изменяется (прямо или косвенно) значение параметра функциональной опции;
  • Новое значение параметра приводит к тому, что функциональная опция отключает объект конфигурации, который являлся основным реквизитом формы;
  • Отключенный объект конфигурации приводил к очистке формы этого объекта.
Управляемая форма.
Если в системе установлен режим совместимости интерфейса в значение Версия 8.2, то работа поля ввода имеет следующие особенности:
  • При активизации поля ввода не открывается выпадающий список;
  • Для свойства КнопкаВыпадающегоСписка расширения управляемой формы для поля ввода значение Авто интерпретируется как Ложь;
  • Для свойства ОтображениеКнопкиВыбора расширения управляемой формы для поля ввода значение Авто интерпретируется как ОтображатьВПолеВвода;
  • Для свойства КнопкаВыбора расширения управляемой формы для поля ввода значение Авто интерпретируется аналогично «1С:Предприятию» версии 8.3.2;
  • Нажатие клавиши Стрелка вниз приводит к открытию формы выбора, а не выпадающего списка.
Поведение поля ввода не отличалось в режиме совместимости интерфейса Такси и Версия 8.2.Для пользователей, переходящих на «1С:Предприятие» версии 8.3, в режиме совместимости интерфейса Версия 8.2, минимизировано количество изменений в поведении.
Системные требования.
Прекращена поддержка ОС Microsoft Windows 2000.ОС Microsoft Windows 2000 поддерживалась системой.Прекращена поддержка устаревшей операционной системы.
Клиентское приложение.
На клиентском компьютере (в ОС Windows) должен быть установлен Microsoft Internet Explorer версии не ниже 7.0. Работа тонкого и толстого клиентов версии 8.3.4 и выше на компьютере, на котором установлен Microsoft Internet Explorer версии 6.0 и ниже, может приводить к ошибкам в различных механизмах.На клиентском компьютере (в ОС Windows) требовался Microsoft Internet Explorer версии не ниже 6.0.Прекращена работа с устаревшим веб-браузером. Требования к различным механизмам платформы приведены в соответствие с системными требованиями.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Свойство расширения управляемой формы для поля ввода. Старое наименование используется для совместимости.
  • ШиринаСпискаВыбора
  • ШиринаВыпадающегоСписка
Изменено английское имя для метода Выбрать() объектов РезультатЗапроса и ВыборкаИзРезультатаЗапроса. Старое наименование используется для совместимости.
  • Choose()
  • Select()
Переименована кнопка, связанная с командой Отмена, в форме расширения управляемой формы отчета, форме настроек и форме варианта отчета.

В режиме совместимости с версией 8.3.3 используется старое наименование.

  • FormCancel
  • FormCancelEdit

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Системные требования.
Для мобильной платформы реализована поддержка процессоров с архитектурой x86 (Intel), работающих под управлением ОС Android. Мобильная платформа для архитектуры x86 поставляется отдельным файлом.

В поставку мобильной платформы входят следующие файлы:

  • 1cem-arm.apk - мобильная платформа разработчика для архитектуры ARM;
  • 1cem-x86.apk - мобильная платформа разработчика для архитектуры x86;
  • prjandroid-arm.zip - мобильная платформа, предназначенная для сборки мобильных приложений (для архитектуры ARM);
  • prjandroid-x86.zip - мобильная платформа, предназначенная для сборки мобильных приложений (для архитектуры x86).
Мобильная платформа не поддерживала процессоры с архитектурой x86 (Intel).Расширена номенклатура поддерживаемых устройств.
Средства разработки.
Для сборки мобильных приложений реализовано прикладное решение - сборщик мобильных приложений, который позволяет:
  • Хранить мобильные конфигурации;
  • Хранить мобильные платформы (начиная с версии 8.3.4);
  • Хранить графическую информацию;
  • Выполнять сборку мобильных приложений;
  • Хранить собранные мобильные приложения.

Сборщик мобильных приложений позволяет собирать мобильные приложения для ОС Android с архитектурой x86. Также реализована возможность выполнять полную сборку мобильного приложения для iOS с помощью компьютера Apple, на котором установлена система Xcode.

Конфигурация поставляется вместе с дистрибутивом мобильной платформы. Обработка для сборки мобильных приложений удалена из дистрибутива мобильной платформы.

Сборка может выполняться с любой версией Android SDK.

Для сборки мобильных приложений использовалась обработка, которая входила в состав дистрибутива мобильной платформы.Процесс сборки мобильных приложений стал более простым. Более не требуется дополнительных действий для сборки мобильного приложения для iOS. +
Системные требования.
Прекращена поддержка операционной системы Android версии 2.2.Поддерживалась операционная система Android версии 2.2.Исключение поддержки устаревшей версии операционной системы Android.

Оглавление

Переход с предыдущей версии на версию 8.3.4

Оглавление

Версия 8.3.3

Версия 8.3.3 включает исправления обнаруженных ошибок и изменения в функциональности. +

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.2. +Использовался режим совместимости с версиями 8.1, 8.2.13, 8.2.16 и 8.3.1. +Возможность запуска конфигураций, разработанных в версии 8.3.2 и более младших, в версии 8.3.3, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.3 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.3, при необходимости, использовать для работы с информационной базой и версию 8.3.2. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости). +
Управляемая форма.
Для управляемой формы реализована возможность управления вертикальным сжатием элементов формы. Реализована возможность указать форме, что вертикальный размер элементов не должен быть меньше размера, указанного в конфигураторе при разработке формы. Для этого у формы реализовано свойство ВертикальнаяПрокрутка.

Если у формы появляется вертикальная полоса прокрутки, то командная панель не попадает в область прокрутки, если командная панель расположена выше или ниже всех элементов формы и занимает всю ширину формы.

Элементы управляемой формы уменьшались до своего минимального вертикального размера при уменьшении высоты формы. +Если на управляемой форме появлялись вертикальные полосы прокрутки, в область прокрутки попадали все элементы, расположенные на форме.Для прокручиваемых форм элементы будут иметь достаточный для удобной работы размер. Командная панель с основными командами формы, такими как Записать и закрыть, будет доступна всегда и не будет прокручиваться.
Управляемая форма.
Веб-клиент.
Если для управляемой формы свойство ВертикальнаяПрокрутка установлено в значение ИспользоватьПриНеобходимости, в веб-клиенте не допускается уменьшение вертикального размера элементов формы до неработоспособного состояния (при вертикальном сжатии формы).Вертикальный размер элементов управляемой формы в веб-клиенте мог уменьшаться до состояния, когда элемент оказывался неработоспособным (при вертикальном сжатии формы).При уменьшении вертикального размера формы не будут возникать ситуации, когда элемент на форме становится непригодным для использования.
Средства разработки.
В редакторе текста на встроенном языке реализована возможность группировки произвольного количества строк, аналогично другим конструкциям встроенного языка (условия, циклы).

Реализованы инструкции препроцессора #Область и #КонецОбласти. Во время исполнения встроенного языка данные инструкции игнорируются.

В стандартные шаблоны добавлен шаблон создания области.

Данная возможность не предоставлялась. Группировались только некоторые синтаксические конструкции встроенного языка.Работа с исходным текстом стала более комфортной. Появилась возможность группировать фрагменты исходного текста по логическому принципу и при редактировании скрывать не используемый в данный момент текст.
Внешние источники данных.
В механизме внешних источников данных реализована возможность использования данных из OLAP-источников.

Поддерживаются следующие OLAP-источники:

  • Microsoft SQL Server Analysis Services;
  • IBM InfoSphere Warehouse;
  • Oracle Essbase.

Обращения к OLAP-источникам (и ошибки, возникающие при этих обращениях) фиксируются в событии EDS технологического журнала.

В библиотеку картинок добавлены картинки ВнешнийИсточникДанныхКуб, ВнешнийИсточникДанныхТаблицаИзмерения.

С помощью внешних источников данных имелась возможность обращения только к реляционным таблицам.При построении отчетов по данным других систем (внешним источникам) появилась возможность, работать не только с реляционными данными, но и с OLAP-источниками.
Интерфейс.
Реализована возможность получения информации о характеристиках мониторов (разрешение и DPI), подключенных к компьютеру, в клиентском приложении (тонкий клиент, толстый клиент, веб-клиент) и на стороне сервера. Во внешнем соединении вызов метода ПолучитьИнформациюЭкрановКлиента() возвращает значение Неопределено. +На сервер информация о характеристиках мониторов клиентского компьютера передается при начале сеанса и при вызове метода ОбновитьИнтерфейс().Возможность получения информации о характеристиках мониторов, подключенных к компьютеру, была доступна только при работе на мобильной платформе. +Позволяет определять характеристики и количество мониторов, подключенных к компьютеру, на котором исполняется приложение. +
Система компоновки данных.
Для элементов условного оформления реализована возможность указания областей, для которых будет применяться данный элемент условного оформления.

В динамическом списке данная возможность не используется.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Условное оформление применялось и к области данных и к заголовку области. Управлять этим было нельзя.Расширение оформительских возможностей для сложных отчетов. +
Средства публикации веб-клиента и Web-сервисов.
Реализована возможность публикации информационной базы, Web-сервисов и мобильного приложения из конфигуратора, работающего под управлением ОС Linux. Публикация возможна только для веб-сервера Apache. Для выполнения публикации необходим запуск конфигуратора от имени пользователя, обладающего административными правами (root).При использовании ОС Linux, публикация информационной базы и Web-сервисов была возможна только с помощью утилиты командной строки webinst. Возможность публикации мобильного приложения не предоставлялась.Устранены недостатки конфигуратора, работающего под управлением ОС Linux.
Работа в ОС Linux.
В конфигураторе, работающим под управлением ОС Linux, реализована возможность подготовки комплектов поставки. К файлам поставки добавляется установочная программа, предназначенная для установки шаблонов и обновлений прикладных решений под ОС Linux. Приложение работает как в 32-разрядном, так и в 64-разрядном варианте ОС Linux. Приложение работает под управлением того же перечня ОС Linux, что и клиентское приложение.В ОС Linux отсутствовала возможность подготовки комплектов поставки.Появилась возможность устанавливать шаблоны и обновления прикладных решений в ОС Linux.
Приложение Autorun.
Приложение Autorun поддерживает работу в ОС Linux. Приложение работает как в 32-разрядном, так и в 64-разрядном варианте ОС Linux. Приложение работает под управлением того же перечня ОС Linux, что и клиентское приложение.

Для конфигурационного файла autorun.lst реализованы новые свойства для элемента конфигурационного файла Element: CommandWindows, CommandLinux, RunAsRoot. Свойства используются для указания, каким образом данный элемент должен выполняться в различных ОС.

В ОС Linux отсутствовала возможность запуска приложения Autorun.

Конфигурационный файл autorun.lst не содержал свойств CommandWindows, CommandLinux, RunAsRoot для элемента конфигурационного файла Element.

Появилась возможность создания дистрибутивов прикладных решений, использующих программу Autorun и поставляемых на внешних носителях, которые могут использоваться и под управлением ОС Windows и под управлением ОС Linux.
Прикладные объекты.
Управляемая форма.
Реализована возможность создания объекта ссылочного типа непосредственно в процессе ввода данных в форме. Для управления этой возможностью реализовано свойство объекта конфигурации и элемента формы. Свойство элемента формы управляет видимостью специальной команды создания нового элемента в списке выбора. Возможность реализована для справочников, документов, планов видов характеристик, планов счетов, планов видов расчетов, бизнес-процессов, задач, планов обмена.

Команда создания нового элемента в списке выбора недоступна в режиме совместимости с версией 8.3.2.

Данная возможность не предоставлялась.

Имелась возможность открыть форму выбора и в ней создать новый объект с последующим его выбором.

Повышена скорость и комфортность работы при необходимости создания нового объекта в процессе ввода данных.
Управляемая форма.
Средства разработки.
В редакторе управляемой формы реализована возможность выбрать в списке добавляемых элементов обычную группу без отображения заголовка.Чтобы создать в редакторе управляемой формы обычную группу без отображения заголовка, было необходимо добавить обычную группу и затем изменить значения свойств, отвечающих за отображение заголовка группы.Повышено удобство редактирования управляемой формы в тех случаях, когда группы используются для управления расположением элементов на форме.
Управляемая форма.
Средства разработки.
При создании клиентских обработчиков событий элементов формы и команд реализована возможность указать перечень создаваемых процедур:
  • Только клиентский обработчик;
  • Клиентский обработчик и внеконтекстная серверная процедура с вызовом из обработчика;
  • Клиентский обработчик и контекстная серверная процедура с вызовом из обработчика.

Создание контекстной серверной процедуры недоступно для тех клиентских обработчиков, в которых вызов контекстных серверных процедур не рекомендуется. +

При создании клиентского обработчика создавался только сам обработчик. Сопутствующие процедуры не создавались.Упрощена разработка формы в тех случаях, когда обработка действия, вызываемого на клиенте, выполняется на сервере. Разработчику более не требуется вручную создавать серверный метод и ставить его вызов в тело клиентского обработчика.
Хранилище конфигурации.
Изменен способ хранения информации в хранилище конфигурации. Объекты хранилища хранятся в файловой системе. Файл 1cv8ddb.1CD используется как хранилище информации об измененных объектах. Реализован режим совместимости работы хранилища конфигурации. Новый способ хранения возможен только при отключенном режиме совместимости хранилища конфигурации.

Реализована возможность выполнять оптимизацию хранения данных хранилища конфигурации. Эта операция возможна как с помощью диалога администрирования хранилища, так и с помощью ключа командной строки ConfigurationRepositoryOptimizeData пакетного запуска конфигуратора.

Формат файлов хранилища конфигурации не предполагает чтения или модификации какими-либо средствами, кроме «1С:Предприятия».

Вся информация хранилища конфигурации хранилась в файле 1cv8ddb.1CD. Возможность оптимизации хранилища конфигурации не предоставлялась.Существенно увеличено количество изменений (версий), которые могут храниться в хранилище конфигураций.
Средства разработки.
Клиентское приложение.
Реализована возможность отключать диалоги выбора информационной базы и аутентификации (в информационной базе и хранилище конфигурации) при запуске клиентского приложения или конфигуратора. Для этого следует использовать ключ DisableStartupDialogs командной строки запуска файла 1cv8.exe/1cv8.

Если в командной строке запуска обнаруживаются ошибки, которые ранее приводили к возникновению диалогов, то диалоги не появляются, а вместо этого формируется соответствующее диагностическое сообщение, которое выводится только в файл для вывода служебных сообщений (ключ Out командной строки запуска).

Если во время запуска клиентского приложения или конфигуратора в пакетном режиме обнаруживались ошибки в параметрах информационной базы или параметрах аутентификации, то система выдавала модальные диалоги для уточнения некорректных параметров. При этом выполнение запрошенных действий останавливалось.При пакетном запуске конфигуратора, особенно если запуск выполняется из другого приложения или службы, появилась возможность исключить появление сложно обнаруживаемых «зависаний»: когда конфигуратор формировал диалог выбора параметра, который был недоступен для интерактивного управления.
Локализация.
Реализована поддержка французского языка для методов глобального контекста ЧислоПрописью() и ПредставлениеПериода(). Код локализации: fr, fr_CA. Значения параметра ПараметрыПредметаИсчисления метода ЧислоПрописью() задаются аналогично английскому, финскому или казахскому языкам.Методы глобального контекста ЧислоПрописью() и ПредставлениеПериода() не поддерживали работу с французским языком.Упростилось представление информации для франкоговорящих пользователей.
Полнотекстовый поиск.
Для объекта СписокПолнотекстовогоПоиска реализована возможность отключать поиск по представлениям объектов конфигурации. Эта возможность управляется с помощью свойства ИспользованиеМетаданных этого объекта.Поиск по представлениям объектов конфигурации было невозможно отключить.Возможность выполнять поиск только по данным, без указания представлений объектов конфигурации.
Встроенный язык.
Для коллекций Массив, Структура и Соответствие реализованы конструкторы, создающие эти объекты на основании соответствующих фиксированных коллекций (ФиксированныйМассив, ФиксированнаяСтруктура, ФиксированноеСоответствие). Для массивов выполняется рекурсивное преобразование, т.е. элемент фиксированного массива, являющийся фиксированным массивом, будет помещен в обычный массив.Преобразование фиксированных коллекций в обычные аналоги было возможно только с использованием циклов.Упрощено изменение значений, расположенных в фиксированных коллекциях.
Общие реквизиты / Разделение данных.
Реализован механизм установки монопольного доступа к области данных. Монопольный доступ к области не совместим с любой блокировкой данных в этой области другими сеансами. Монопольный режим области данных должен явно устанавливаться и сниматься с помощью метода встроенного языка УстановитьМонопольныйРежим(). Фоновое задание, запущенное из сеанса, установившего монопольный режим области, до своего завершения получает монопольный доступ родительского сеанса, при этом родительский сеанс «лишается» монопольного доступа. Изменение данных из родительского сеанса становится невозможным. Монопольный доступ «возвращается» родительскому сеансу после завершения фонового задания. Переход сеанса в другую область не влияет на список областей, к которым сеанс имеет монопольный доступ.

Монопольный режим области запрещает:

  • Создание новых сеансов с таким же набором разделителей;
  • Доступ к данным области из объемлющих областей;
  • Установку монопольного доступа в объемлющих областях.

Установка разделяемых управляемых блокировок для области игнорируется, если для этой области установлена монопольная блокировка данным сеансом. +

Установить монопольный доступ к области данных было невозможно. Существовала возможность наложить исключительную транзакционную управляемую блокировку на все данные области.Возможность выполнять согласованные изменения области данных, которые нет возможности заключать в транзакцию.
Общие объекты.
Для объекта ХешированиеДанных реализована возможность вычисления хеш-функций SHA1 и SHA256.Объект ХешированиеДанных позволял вычислять хеш-функции MD5 и CRC32.Расширение набора поддерживаемых хеш-функций.
Прикладные объекты.
Реализована возможность создавать определяемые типы данных - типы данных с уникальным именем и типом, состоящим из одного или нескольких допустимых типов. Определяемый тип данных может выступать в качестве типа реквизита объекта конфигурации. Определяемый тип не может входить в составной тип и не может выступать типом данных плана вида характеристик.

Если необходимо использовать прикладное решение с помощью предыдущих версий платформы - из прикладного решения необходимо удалить все определяемые типы.

Данная возможность не предоставлялась.Реализована возможность определять в конфигурации тип, на который можно ссылаться при описании типов конкретных реквизитов. Например, это позволяет описать в некотором универсальном фрагменте конфигурации реквизиты, ссылающиеся на данные, которые будут определены при встраивании фрагмента в конкретную конфигурацию.
Мобильное приложение.
Реализована возможность в качестве картинки, задаваемой файлом, указывать zip-архив, содержащий картинки разных размеров. Это позволяет указывать для мобильных приложений картинки, которые будут использоваться в устройствах с разным разрешением экрана. Поддерживаются следующие варианты экранов мобильных устройств:
  • устройства с разрешением менее 140 dpi;
  • устройства с разрешением от 140 до 180 dpi и устройства Apple с обычными экранами;
  • устройства с разрешением от 180 до 270 dpi;
  • устройства с разрешением более 270 dpi и устройства Apple с экранами Retina.

Каждая картинка соответствует определенным характеристикам экрана целевого устройства. Картинки, входящие в состав архива, рекомендуется делать в формате .png. Архив рекомендуется создавать без сжатия.

Для объекта Картинка реализовано свойство НаборВариантов. +

Данная возможность не предоставлялась. На мобильной платформе разработчик должен был устанавливать различные картинки из встроенного языка.Упрощено создание приложений, которые должны работать и на персональном компьютере и на мобильном устройстве. Теперь прикладной разработчик должен обеспечить только наличие картинок для различных разрешений и не должен выполнять программную установку картинок в режиме 1С:Предприятия.
Регистры накопления.
Регистры бухгалтерии.
Реализована возможность устанавливать границы интервала хранения итогов по периодам для регистров накопления остатков и регистров бухгалтерии. Задавать можно как нижнюю так и верхнюю границу интервала. Итоги, попадающие в этот интервал, будут автоматически пересчитываться при изменении итогов за границами интервала (при необходимости). За границами установленного интервала итоги по периодам не хранятся, а при необходимости получения остатков выполняется их расчет по таблицам движений.

Для менеджеров регистров накопления и бухгалтерии реализованы методы УстановитьМинимальныйПериодРассчитанныхИтогов(), ПолучитьМинимальныйПериодРассчитанныхИтогов(), УстановитьМинимальныйИМаксимальныйПериодРассчитанныхИтогов().

При изменении плана счетов, создании движений, пересчете итогов и получении остатков по остаточным регистрам накопления и регистрам бухгалтерии учитываются границы хранения итогов.

При включении использования итогов, выполняется пересчет только тех периодов, в которых были реальные изменения.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Итоги хранились по всем периодам, которые расположены младше периода рассчитанных итогов для регистра. При изменении движений задним числом выполнялся пересчет всех итогов, которые расположены позднее измененной даты.

При включении использования итогов также выполнялся пересчет всех итогов регистра.

Уменьшает объем данных, хранимых в базе данных, а также уменьшает время выполнения административных операций.

Позволяет снизить нагрузку на систему в тех случаях, когда база данных хранит данные за большие периоды (несколько лет), регулярно выполняются изменения задним числом, но регулярное получение данных (с использованием итогов) осуществляется в пределах ограниченного интервала времени относительно текущей даты.

Внешние компоненты.
В технологии создания внешних компонент реализована возможность организации простого диалога с пользователем, а также возможность сохранять значения между сеансами в локальном хранилище веб-браузера.

Изменена документация по технологии создания внешних компонент (http://its.1c.ru/db/metod81#content:3221:1), дополнены примеры, представлены новые версии адаптеров для веб-браузеров.

В технологии создания внешних компонент были недоступны возможности организации диалога с пользователем и сохранения значений в локальном хранилище веб-браузера.Доступ внешней компоненты, работающей в веб-браузере, к локальным ресурсам может сопровождаться соответствующими предупреждениями, так, как это реализовано во встроенных механизмах платформы.
Веб-клиент.
Табличный документ.
Печать документов.
Реализована возможность формировать пакеты документов, предназначенные для печати. Для печати всего пакета необходимо один раз вызвать печать.

Для пакета имеется возможность задавать параметры печати. Пакеты могут быть вложенными. Пакет может быть записан в один файл формата PDF, что упрощает его печать в веб-клиенте.

Реализован объект ПакетОтображаемыхДокументов.

В веб-клиенте было невозможно реализовать пакетную печать нескольких документов по нажатию одной кнопки. При выводе пакета документов в несколько табличных документов, пользователю было необходимо столько раз нажать кнопку печати, сколько документов входило в пакет.Улучшена печать нескольких документов (с различными настройкам параметров печати) в веб-клиенте. При печати с помощью пакета документов пользователю необходимо только один раз вызвать печать (вне зависимости от количества документов в пакете), при этом параметры печати для каждого документа (включая ориентацию страницы и количество печатаемых копий) будут установлены нужным образом.
Кластер серверов.
Для клиент-серверного варианта работы реализованы профили безопасности, позволяющие управлять доступом прикладных решений к различным внешним ресурсам на сервере «1С:Предприятия»: файловой системе, COM-объектам, внешним компонентам, приложениям операционной системы, ресурсам Интернета, привилегированному режиму, внешним отчетам и обработкам, методам глобального контекста Выполнить() и Вычислить(). Для каждой информационной базы в кластере может быть назначен свой профиль безопасности, а также назначен профиль безопасности для программного кода, исполняемого в безопасном режиме.

Для целей программного администрирования кластера:

  • Реализован объект ISecurityProfile;
  • Реализован объект ISecurityProfileVirtualDirectory;
  • Реализован объект ISecurityProfileCOMClass;
  • Реализован объект ISecurityProfileAddIn;
  • Реализован объект ISecurityProfileExternalModule;
  • Реализован объект ISecurityProfileApplication;
  • Реализован объект ISecurityProfileInternetResource;
  • Для объекта IServerAgentConnection реализованы методы GetSecurityProfiles(), RegSecurityProfile(), UregSecurityProfile(), CreateSecurityProfile(), GetSecurityProfileVirtualDirectories(), RegSecurityProfileVirtualDirectory(), UnregSecurityProfileVirtualDirectory(), CreateSecurityProfileVirtualDirectory(), GetSecurityProfileCOMClasses(), RegSecurityProfileCOMClass(), UnregSecurityProfileCOMClass(), CreateSecurityProfileCOMClass(), GetSecurityProfileAddIns(), RegSecurityProfileAddIn(), UnregSecurityProfileAddIn(), CreateSecurityProfileAddIn(), GetSecurityProfileUnSafeExternalModules(), RegSecurityProfileUnSafeExternalModule(), UnregSecurityProfileUnSafeExternalModule(), CreateSecurityProfileUnSafeExternalModule(), GetSecurityProfileApplications(), RegSecurityProfileApplication(), UnregSecurityProfileApplication(), CreateSecurityProfileApplication(), GetSecurityProfileInternetResources(), RegSecurityProfileInternetResource(), UnregSecurityProfileInternetResource(), CreateSecurityProfileInternetResource();
  • Для объекта IInfoBase реализованы свойства SecurityProfileName и SafeModeSecurityProfileName;
  • Изменен тип параметра БезопасныйРежим методов Создать() и Подключить() менеджеров внешних отчетов и обработок, а также метода глобального контекста УстановитьБезопасныйРежим() и тип возвращаемого значения метода глобального контекста БезопасныйРежим() с типа Булево на тип Строка. При использовании параметра (или возвращаемого значения) типа Строка, в качестве строкового значения используется имя профиля безопасности.

Аналогичные изменения внесены:

  • в утилиту администрирования кластера (rac) - реализован режим работы profile и внесены изменения в команду update режима infobase.
  • в интерфейс работы с сервером администрирования из языка Java.
Данная возможность не предоставлялась.Появилась возможность административно (без вмешательства в код прикладного решения) ограничивать доступ прикладных решений к различным ресурсам системы, в рамках которой они функционируют. Появилась возможность расширить доступную функциональность для программного кода, работающего в безопасном режиме (например, разрабатываемого пользователем), сохранив при этом необходимый уровень безопасности.

С помощью профилей безопасности, например, можно для каждой области данных организовывать персональный каталог временных файлов или описать список ресурсов Интернет, который доступен для использования в конкретной информационной базе.

Автоматизированное тестирование.
Реализованы объекты ТестируемаяКнопкаКомандногоИнтерфейса, ТестируемаяГруппаКомандногоИнтерфейса,

ТестируемыйКомандныйИнтерфейсОкна.

Для тестируемых объектов реализован метод ПолучитьОбъект(), по набору параметров аналогичный методам НайтиОбъект() и НайтиОбъекты(). В случае, если искомый объект не найден, метод ПолучитьОбъект() генерирует исключение.

Реализованы методы работы с сообщениями пользователя. +Расширен состав свойств и методов, позволяющих работать с объектами тестирования, например, получение имени формы, текущего окна, командного интерфейса и т.д. +Реализована возможность получить информацию о последней ошибке, произошедшей в тестируемом клиентском приложении.

Для объекта ТестируемоеПриложение реализованы методы ПолучитьАктивноеОкно(), ПолучитьТекущуюИнформациюОбОшибке(). Для объекта ТестируемоеОкноКлиентскогоПриложения реализованы методы ПолучитьКомандныйИнтерфейс(), ПолучитьТекстыСообщенийПользователю(), ВыбратьСообщениеПользователю(). Для объекта ТестируемаяФорма реализовано свойство ИмяФормы, методы НайтиКнопкуПоУмолчанию(), ТекущаяМодифицированность(), ПолучитьКоманднуюПанель(), метод Закрыть() перенесен в объект ТестируемоеОкноКлиентскогоПриложения. Для объекта ТестируемоеПолеФормы реализованы методы ТекущийРежимРедактирования(), ПолучитьТекстРедактирования() и изменены методы НачатьРедактированиеТекущейОбласти(), ЗакончитьРедактированиеТекущейОбласти(). Для объекта ТестируемаяТаблицаФормы реализован метод ТекущийРежимРедактирование() и изменены методы ИзменитьСтроку(), ЗакончитьРедактированиеСтроки(), ПерейтиКПредыдущейСтроке(), ПерейтиКСледующейСтроке(), Развернуть(), Свернуть(). Для объектов, описывающих тестируемые элементы формы, реализованы методы ПолучитьТекстПодсказки(), ТекущаяВидимость(), ТекущаяДоступность(), ТекущееТолькоПросмотр(), ПолучитьКонтекстноеМеню(), ПолучитьКоманднуюПанель().

Доработана обработка преобразования журнала действий пользователя в сценарий на встроенном языке (http://its.1c.ru/db/metod81#content:5014:1).

Командный интерфейс окна приложения был недоступен для использования средств автоматизированного тестирования. Возможность работы с сообщениями пользователю была недоступна.Появилась возможность работать с командным интерфейсом окна приложения.

Упростилась обработка ошибок при попытке получить несуществующий объект во время выполнения сценария тестирования.

Динамический список.
Для динамического списка реализована возможность автоматического сохранения настроек. Для управления этой возможностью для динамического списка реализовано свойство Автоматическое сохранение пользовательских настроек. Для хранения настроек предназначено особое хранилище: хранилище настроек динамического списка. Для таблицы управляемой формы, связанной с динамическим списком, реализованы команды сохранения/восстановления настроек, а также события, позволяющие реализовать нестандартную реакцию на сохранение, восстановление и редактирование настроек динамического списка. Режим просмотра динамического списка (список, дерево, иерархический список) сохраняется вместе с настройками элементов формы.

Реализована возможность редактировать пользовательские настройки динамического списка в отдельной группе формы, отображающей динамический список, для указания которой реализовано свойство таблицы формы Группа пользовательских настроек. Реализована возможность редактировать настройки динамического списка в отдельной общей форме, которая указывается с помощью свойства конфигурации Основная форма настроек динамического списка.

Для объекта ДинамическийСписок реализовано свойство КомпоновщикНастроек, аналогичное соответствующему свойству отчетов.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Для динамического списка автоматически сохранялись и восстанавливались отборы (восстанавливались с отключенным признаком использования) и условное оформление. Для сохранения и восстановления остальных настроек, прикладному разработчику было необходимо реализовывать нужные алгоритмы на встроенном языке.Повышен комфорт использования динамического списка пользователем. Для разработчика облегчено создание динамических списков с быстрыми отборами. Не требуется разработка специальных механизмов сохранения/восстановления настроек динамического списка.
Управляемая форма.
Для групп управляемой формы реализована возможность управлять сворачиванием группы (только по вертикали). Если установлена возможность сворачивания, пользователь может сворачивать группу, т.е. скрывать все элементы, входящие в состав группы. Для этого для группы управляемой формы реализованы свойства Поведение, ОтображениеУправления, ОтображатьОтступСлева и ЗаголовокСвернутогоОтображения.

Сворачивание доступно только для обычной группы с отображаемым заголовком.

Данная возможность не предоставлялась. Скрывать неиспользуемые элементы можно было управляя видимостью.Позволяет скрывать редко используемые элементы формы, уменьшая объем информации, воспринимаемый пользователем. Для доступа к скрытой информации пользователь может развернуть группу.
Средства разработки.
При попытке изменить объект конфигурации, изменение которого невозможно, сообщение о невозможности выполнить действие выводится в окно сообщений.При попытке изменить объект конфигурации, изменение которого невозможно, сообщение о невозможности выполнения действия выводилось с помощью модального диалогового окна.Прикладному разработчику больше не требуется многократно закрывать модальное диалоговое окно, если он попытался выполнить массовое изменение с заблокированными объектами (например, не захваченными в хранилище конфигурации).
Интерфейс.
Реализован новый вариант интерфейса клиентского приложения: Такси. Интерфейс Такси включает в себя большое количество изменений, среди которых можно выделить:
  • Изменено оформление интерфейса: увеличен шрифт, увеличены отступы в формах, изменены основные цвета и оформление элементов форм, увеличен их размер.
  • Усовершенствована навигация по приложению: ориентация на работу с одним окном, наличие специальных панелей (истории, избранного и т.д.), переходы между открытыми окнами как вперед, так и назад и т.д.
  • Расширены возможности настройки главного окна: разработчик может задать состав и местоположение панелей, соответствующих прикладному решению, при этом пользователь может перекомпоновать эти панели так, как удобно ему.
  • Использовать полнотекстовый поиск можно с помощью системной формы.
  • Панель навигации формы размещена в верхней части формы.
  • Окно сообщений расположено в нижней части формы и отображается только тогда, когда есть сообщения для отображения.
  • Панель показателей производительности отображается не в виде отдельного окна, а в виде отдельной панели основного окна приложения.
  • В панели История записи группируются по дням, с указанием времени открытия. Также реализована возможность поиска и добавления в Избранное.
  • В панели Избранное реализована возможность поиска, переименования и закрепления очень важных элементов вверху списка.

Для принудительного включения этого интерфейса (если он разрешен в прикладном решении) реализован ключ командной строки запуска клиентского приложения iTaxi. Также переключение интерфейса можно выполнять с помощью диалога настройки параметров клиентского приложения.

Реализованы свойства конфигурации:

  • РежимСовместимостиИнтерфейса - позволяет указать, с каким интерфейсом можно использовать прикладное решение.
  • ИнтерфейсКлиентскогоПриложения - содержит состав и положение панелей, используемых в клиентском приложении по умолчанию.
  • ОсновнаяФормаПоиска - содержит указание на форму поиска, которая будет использоваться для полнотекстового поиска в данных. Если форма не задана - используется системная форма полнотекстового поиска.

Реализован новый внешний вид календаря. Для поля календаря управляемой формы реализованы свойства, позволяющие управлять новыми возможностями: ВысотаВМесяцах, ШиринаВМесяцах, ОтображатьПанельМесяцев, которые используются только в интерфейсе Такси.

Для объекта НастройкиКлиентскогоПриложения реализовано свойство ВариантИнтерфейсаКлиентскогоПриложения, которое позволяет получить режим интерфейса, а также метод глобального контекста ТекущийВариантИнтерфейсаКлиентскогоПриложения(). Реализован метод глобального контекста, позволяющий получать размер основного шрифта клиентского приложения: ТекущийВариантОсновногоШрифтаКлиентскогоПриложения().

Для объекта ЭлементИзбранногоРаботыПользователя реализованы свойства Важное и Представление.

Рабочий стол в интерфейсе Такси переименован в Начальная страница (с соответствующим переименованием связанных команд), командный интерфейс рабочего стола переименован в командный интерфейс основного раздела, для доступа к командному интерфейсу основного раздела используется раздел Главное панели разделов.

В интерфейсе Такси:

  • Меню Все действия переименовано в Еще.
  • Изменено представление в формах стандартных команд по умолчанию, а также отображение команд в командой панели или в меню Еще;
  • Изменилось отображение групп элементов.

Навигационная ссылка на начальную страницу (рабочий стол) прикладного решения имеет вид e1cib/navigationpoint/startpage. Настройки начальной страницы (рабочего стола) сохраняются в настройках с ключом НачальнаяСтраница/НастройкиОкна (для интерфейса Такси - НачальнаяСтраница/Такси/НастройкиОкна).

В редакторе управляемой формы реализована возможность переключения окна предварительного просмотра между интерфейсом 8.2 и интерфейсом Такси.

Использовался интерфейс, реализованный в версии 8.2 для управляемого приложения.Улучшение навигации по прикладному решению, повышение комфорта использования, развитие в соответствии с современными тенденциями построения интерфейсов.
Интерфейс.
Реализован стилевой шрифт ОбычныйШрифтТекста, который является основой для расчета размера других стилевых шрифтов, кроме ШрифтТекста. Фактически используемый шрифт зависит от режима интерфейса прикладного решения (Такси или интерфейс 8.2).Данная возможность не предоставлялась.Использование данного шрифта (и основанных на нем) обеспечивает сохранение пропорций размеров шрифтов элементов управляемых форм в различных режимах интерфейса.
Интерфейс.
Реализовано свойство конфигурации КартинкаОсновногоРаздела, позволяющее указать картинку, которая будет использоваться в качестве картинки для основного раздела (рабочего стола) в панели разделов.У рабочего стола использовалась фиксированная картинка, которую было невозможно заменить.Данная возможность позволяет оформлять все прикладное решение в едином графическом стиле и отображать рабочий стол в виде, максимально понятном для основной категории пользователей данного решения.
Средства разработки.
Реализована возможность отображения контекстной подсказки по параметрам процедуры или функции, которая в данный момент редактируется в редакторе текстов модулей. Если метод имеет несколько вариантов синтаксиса - существует возможность выбрать нужный вариант.

Реализован автоматический разбор комментариев к процедурам и функциям прикладного решения для отображения в контекстной подсказке. Формат комментариев описан в документации и соответствует стандартам разработки прикладных решений. Шаблоны создания процедур и функций, входящие в состав поставки, соответствуют требуемому формату.

Реализован параметр настройки конфигуратора, который управляет отображением контекстной подсказки параметров процедур и функций. В редакторе исходного текста контекстная подсказка по параметрам процедур и функций вызывается с помощью горячей клавиши Ctrl+Shift+Пробел.

В конфигураторе отсутствовала контекстная подсказка по параметрам процедур и функций. В контекстной подсказке отображались только имена процедур и функций прикладного решения. Комментарии к процедурам и функция не использовались для получения информации о параметрах.Повышен комфорт разработчика при наборе исходных текстов прикладного решения. Нет необходимости использовать синтакс-помощник для быстрого просмотра порядка следования и типов параметров используемой процедуры или функции.
Средства разработки.
В синтакс-помощнике реализована возможность быстрого перехода к различным методическим материалам, связанными с изучаемой статьей. Переход осуществляется с помощью гиперссылки Методические материалы в нижней части статьи. Данные для перехода получаются с помощью специального веб-сервиса.

Список методических материалов открывается в ОС Windows с помощью веб-браузера Microsoft Internet Explorer, в ОС Linux используемый веб-браузер зависит от настроек системы.

Данная возможность не предоставлялась.С помощью данной возможности разработчик получает простой и быстрый доступ к материалам, расположенным на различных веб-ресурсах фирмы «1С». Однако, для доступа к некоторым материалам может потребоваться имя и пароль пользователя этого ресурса.
Средства администрирования.
В документацию включено описание возможностей по настройке и обслуживанию СУБД, которые могут использоваться при администрировании «1С:Предприятия».Документация не содержала описание инструментов администрирования, которые могут использоваться без нарушения лицензионного соглашения.Допустимо использовать возможности СУБД, которые не затрагивают представление структуры данных, используемых для работы «1С:Предприятием» (сделанные изменения не повлияют на процесс реструктуризации и будут сохранены после выполнения реструктуризации).
Управляемая форма.
Для полей вида поле флажка и поле переключателя, реализована возможность отображения в виде тумблера (нескольких кнопок, расположенных рядом, где цветом выделяется активное значение). Для этого реализованы свойства ВидФлажка и ВидПереключателя для соответствующих видов полей управляемой формы.Данная возможность не предоставлялась.Расширение презентационных возможностей системы. Повышено удобство работы при наличии сенсорного интерфейса.
Обновление конфигурации базы данных.
Кластер серверов.
Изменения плана видов характеристик, а также изменение плана счетов, в котором план видов характеристик выступает в качестве типа субконто, требует выполнение реструктуризации информационной базы.

В процесс фоновой реструктуризации внесены некоторые изменения:

  • С планом обмена невозможно выполнять операции создания, редактирования и удаления элементов в тех случаях, когда требуется выполнить операцию реструктуризации этого плана обмена. Реструктуризация выполняется в фазе обработки.
  • Невозможно выполнять операции создания, редактирования и удаления элементов плана видов характеристик в тех случаях, когда план видов характеристик указан в качестве типа субконто у плана счетов и требуется реструктуризация этого плана счетов. В этом случае реструктуризация плана видов характеристик выполняется в фазе обработки.
  • Во время фоновой реструктуризации невозможно использовать метод УстановитьОбновлениеПредопределенныхДанных().
Реструктуризация плана видов характеристик выполнялась при изменении самого плана видов характеристик.

Реструктуризация всех планов видов характеристик и планов обмена выполнялась в фазе принятия изменений (при выполнении фоновой реструктуризации).

В фоновом обновлении конфигурации базы данных, для некоторых случаев, учтены особенности изменения конкретных структур данных для исключения рассогласования данных различных объектов.
Системные требования.
Реализована поддержка работы «1С:Предприятия» под управлением ОС Microsoft Windows Server 2012 (x86-64).Не поддерживалась работа «1С:Предприятия» под управлением ОС Microsoft Windows Server 2012 (x86-64).Реализована поддержка новой версии ОС компании Microsoft.
Отображение информации.
 +

При установке свойства конфигурации Режим совместимости интерфейса в значения Такси или Такси. Разрешить Версия 8.2, картинка библиотеки картинок Справка будет иметь внешний вид, соответствующий интерфейсу Такси.

Внешний вид картинки Справка (из библиотеки картинок) не зависела от значений свойств конфигурации.В библиотеке картинок учтена особенность разного отображения кнопки Справка в разных режимах интерфейса.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Печать документов.
Изменено поведение формы состояния печати в управляемом приложении в тонком и толстом клиентах:
  • В режиме открытия форм в закладках форма состояния печати открывается в отдельном окне;
  • Форма открывается в модальном окне, что препятствует работе с интерфейсом во время печати;
  • Форму невозможно закрыть с помощью «крестика»;
  • Невозможно изменить размер формы.

+

Форма состояния печати имела другое поведение.Повышение комфорта пользователя, выполняющего печать документа.
Работа в ОС Linux.
Реализована работа с буфером обмена Primary Selection (данные попадают в этот буфер сразу, после выделения какого-либо фрагмента текста, без дополнительного нажатия каких-либо кнопок). Копирование в буфер Primary Selection поддерживается для следующих элементов формы:
  • Поле ввода;
  • Поле текстового документа;
  • Поле форматированного документа;
  • Поле табличного документа.

Вставка из буфера Primary Selection (нажатием средней кнопки мыши) поддерживается для поля ввода.

Данная возможность не предоставлялась.Повышена комфортность работы с клиентским приложением для пользователей, обладающих опытом работы в ОС Linux.
Управляемая форма.
Функциональные опции.
Если поле ввода связано с реквизитом составного типа, в котором правами доступа или функциональными опциями отключены все типы, кроме одного, то при попытке выбрать значение в поле ввода, сразу открывается форма выбора значения.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Если поле ввода связано с реквизитом составного типа, то при попытке выбрать значение в поле ввода, вначале открывался диалог выбора типа, даже если список типов состоял из одного значения.Нет необходимости выбирать единственное значение в диалоге выбора типа.
Автоматизированное тестирование.
При закрытии приложения реализован запрос на сохранение журнала действий пользователя, если на этот момент активна запись журнала.При закрытии приложения незавершенный журнал действий пользователя терялся.Снижена вероятность потери незавершенного журнала при закрытии окна приложения, в котором записывается журнал действий пользователя.
Веб-клиент.
Проверка блокировки всплывающих окон при запуске веб-клиента выполняется только если используется интерфейс в отдельных окнах или разрешено использование модальных окон. Проверка блокировки всплывающих окон выполняется после проведения аутентификации пользователя.

+

Проверка блокировки всплывающих окон выполнялась при каждом старте веб-клиента.Пользователю не будет предлагаться выполнить настройку блокировки всплывающих окон веб-браузера в тех случаях, когда это не требуется.
Интерфейс.
При смене режима интерфейса предлагается выполнить перезапуск клиентского приложения.Смена режима интерфейса не сопровождалось предложением выполнить перезапуск клиентского приложения.Смена режима интерфейса стала выполняться более логично: система сразу сообщает, что надо сделать для того, чтобы изменился режим интерфейса.
Стандартные функции.
Изменены некоторые стандартные функции:
  • Журнал регистрации:
    • Изменен состав и представление команд командной панели формы;
    • Переработана установка и отключение отбора;
    • Реализован просмотр данных записи журнала с помощью гиперссылки в соответствующей колонке журнала;
    • Реализована возможность отбора записей по дате и времени.
  • Поиск ссылок на объект:
    • Реализована возможность поиска ссылок на найденную ссылку (с помощью контекстного меню).
  • Управление полнотекстовым поиском:
    • Переработана форма;
    • Включение и выключение полнотекстового поиска выполняется без открытия дополнительной формы.
  • Проведение документов:
    • Переработана форма.
  • Список активных пользователей:
    • Реализовано открытие журнала регистрации, с отбором по пользователю, с помощью гиперссылки в колонке Пользователь.
Стандартные функции были менее удобными.Повышено удобство использования стандартных функций.
Веб-клиент.
В документацию включена рекомендация по выбору веб-браузера для работы на недостаточно производительных компьютерах.Рекомендация по выбору веб-браузера отсутствовала в документации.Сформулирована рекомендация по выбору веб-браузера.
Веб-клиент.
В веб-браузере Microsoft Internet Explorer отключено постепенное затухание окна оповещения при автоматическом закрытии.В веб-браузере Microsoft Internet Explorer окно оповещения постепенное затухало при автоматическом закрытии.Повышена скорость работы с окнами оповещений при работе веб-браузере Microsoft Internet Explorer.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
Регистры накопления.
Работа с запросами.
Оптимизирована работа виртуальных таблиц регистров накопления в случае, если для получения остатков по регистру указаны отборы не по всем измерениям. +Недостаточная эффективность работы виртуальных таблиц регистров накопления в случае, если для получения остатков по регистру указаны отборы не по всем измерениям. +Повышена скорость работы виртуальных таблиц регистров накопления. +
Кластер серверов.
Оптимизирован процесс создания нового сеанса.Создание нового сеанса выполнялось недостаточно эффективно.Уменьшено время подключения к серверу «1С:Предприятия» в следующих случаях:
  • Одновременное подключение большого количества клиентских приложений;
  • Подключение нового клиентского приложения к кластеру, обслуживающему большое количество сеансов.
Регистры сведений.
Оптимизирована работа независимого, не периодического регистра сведений с количеством измерений больше 1.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Работа с регистром выполнялась недостаточно эффективно. +Повышена скорость записи в регистр, особенно в условиях одновременной работы большого числа пользователей. +
Прикладные объекты.
Для некоторых сценариев оптимизированы выборки из справочников и планов видов характеристик. +В некоторых сценариях выборки из справочников и планов видов характеристик выполнялись недостаточно эффективно. +Для некоторых сценариев ускорены выборки из справочников и планов видов характеристик. +
Динамический список.
Оптимизирована работа динамического списка в клиент-серверном варианте при одновременной работе большого количества пользователей. +В некоторых сценариях динамический список работал недостаточно эффективно. +Для некоторых сценариев повышена скорость работы динамического списка. +
Кластер серверов.
Для некоторых сценариев оптимизирован механизм работы с сеансовыми данными.В некоторых сценариях работа с сеансовыми данными выполнялась недостаточно эффективно. +Повышена производительность и масштабируемость сервера «1С:Предприятия». +
Регистры накопления.
Оптимизировано выполнение запросов к оборотным регистрам с большим числом измерений в случае использования агрегатов (для некоторых сценариев использования).

В режиме совместимости с версией 8.3.2 поведение не изменилось.

В некоторых случаях выполнение запросов к оборотным регистрам с большим числом измерений в случае использования агрегатов выполнялось недостаточно эффективно. +Возможность использовать режим агрегатов в большем количестве случаев. +
Работа с СУБД.
Для ускорения работы некоторых запросов при работе с СУБД IBM DB2, в документацию включена рекомендация (а также способы идентификации проблемных ситуаций) по выполнению команды db2set DB2_OVERRIDE_BPF=5000 и перезапуск СУБД.Для некоторых запросов наблюдалась недостаточная производительность при работе с СУБД IBM DB2.Повышена производительность при работе с СУБД IBM DB2 при выполнении некоторых запросов.
Регистры сведений.
Для периодических регистров сведений, подчиненных регистратору, поле Активность включено в состав следующих индексов:
  • По периоду;
  • По измерениям;
  • По измерению.

Для указанных индексов поле Активность добавляется последним полем.

После переключения режима совместимости необходимо выполнить полную реструктуризацию информационной базы для перестроения индексов. +В режиме совместимости с версией 8.3.2 поведение не изменилось.

Поле Активность не входило в состав индексов периодического регистра сведений, подчиненного регистратору.Повышена производительность при получении срезов первых или последних.
Кластер серверов.
Выполнена оптимизация сервера «1С:Предприятия» с целью уменьшения потребления памяти и уменьшения фрагментации оперативной памяти.Сервер «1С:Предприятия» в некоторых сценариях неоптимально использовал память, что приводило к ее фрагментации и повышенному использованию.Уменьшено использование памяти во время работы сервера «1С:Предприятия», а также уменьшена фрагментация памяти. Это позволяет уменьшить количество плановых перезапусков сервера «1С:Предприятия» и повысить стабильность работы системы.
Работа с СУБД.
Индексы реквизитов с дополнительным упорядочиванием включают в себя (в конце индекса) пометку удаления и все поля, индексируемые с дополнительным упорядочиванием.Индексы реквизитов с дополнительным упорядочиванием не включали в себя пометку удаления и все поля, индексируемые с дополнительным упорядочиванием.Ускорена работа динамических списков с отборами по нескольким реквизитам (включая пометку удаления).
Управляемая форма.
Ускорено отображение управляемой формы после серверных вызовов (явных или неявных), связанных с изменением внешнего вида формы.При программном изменении внешнего вида формы, отображение формы выполнялось недостаточно быстро.Ускорено отображение форм, например при изменении отображаемого заголовка элемента формы.
Общие реквизиты / Разделение данных.
При отключении режима совместимости с версией 8.3.2 выполняется оптимизация структуры хранения информации о разделителях для таблиц, связанных с объектами, входящими в состав разделителей. При установке режима совместимости с версией 8.3.2 выполняется обратная реструктуризация таблиц базы данных.Структура хранения информации о разделителях была недостаточно оптимальна.

+

Увеличение производительности за счет изменения структуры хранения информации о разделителях.
Кластер серверов.
Оптимизирован алгоритм балансировки нагрузки рабочих процессов в кластере серверов. Для определения доступной производительности сервера (в дополнение к ранее используемым параметрам) используется также размер очереди к процессору, текущая загрузка процессора и количество ядер процессора.

Информация о значениях, участвующих в определении доступной производительности сервера, отображаются в свойстве TXT события технологического журнала CLSTR.

Для получения параметров производительности, пользователь, от имени которого исполняется сервер «1С:Предприятия», должен дополнительно входить в группу Performance Log Users.

Алгоритм балансировки нагрузки рабочих процессов в кластере серверов обладал недостаточной реактивностью.Повышена реактивность работы алгоритма балансировки нагрузки. Алгоритм более эффективно определяет перегруженный процессор и перестает его нагружать дополнительными задачами.
Управляемая форма.
Оптимизировано открытие управляемой формы в том случае, если на форме присутствуют многострочные поля ввода, которые отображают текст с большим количеством переносов строк.Открытие формы выполнялось недостаточно быстро, если в управляемой форме присутствовали многострочные поля ввода, отображающие текст с большим количеством переносов строк.Ускорено открытие управляемой формы, отображающей многострочные поля ввода с большим количеством переносов строк.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Программное лицензирование.
Реализовано получение лицензий для базовых версий в ОС Linux. +Получение лицензий для базовых версий в ОС Linux было невозможно. +Возможность использования базовых версий в ОС Linux. +
Прикладные объекты.
Переработан механизм автоматической нумерации объектов информационной базы. Контроль уникальности номера или кода (в том числе и полученного в результате автоматической генерации номера или кода) всегда производится во время записи объекта.

В текст сообщения о нарушении уникальности номера или кода добавлено указание, какой номер или код не уникален.

Изменилось использование освободившегося номера или кода. Новый номер или код назначается без использования освободившихся номеров или кодов, если есть уже выданные номера или коды с большим (по порядку) префиксом номера или кода.

Контроль уникальности не выполнялся, если номер или код создавались автоматически при записи объекта.

В тексте сообщения о нарушении уникальности номера или кода не отображалось значение, оказавшееся неуникальным.

Новый номер или код назначался из освободившихся номеров, если подходил префикс, вне зависимости от того, были или нет уже полученные номера с большим (по порядку) префиксом.

Повышена стабильность и надежность работы механизма автоматической нумерации объектов информационной базы. +Повышена информативность сообщений, возникающих при неуникальном значении номера или кода.

Механизм автонумерации стал более логичным: каждый новый объект имеет максимальный номер или код по порядку возрастания номера.

Прикладные объекты.
При невозможности вычисления текстового представления значения во время работы отладчика, в качестве текстового представления будет возвращена строка Ошибка получения представления значения.Невозможность вычисления текстового представления значения могло привести к зависанию конфигуратора. +Повышена стабильность работы системы во время отладки. +
Управляемая форма.
Видимость команды перехода к регистру расчета (в форме регистратора) по умолчанию устанавливается в значение Истина.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Видимость команды перехода к регистру расчета (в форме регистратора) по умолчанию устанавливается в значение Ложь. +Приведение видимости по умолчанию для команд перехода к регистрам к единому виду.
Управляемая форма.
При интерактивной очистке реквизита типа Число, для которого установлены минимальное или максимальное значение, значение реквизита после очистки не может выходить за установленные границы.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При интерактивной очистке реквизита типа Число, установленные для реквизита минимальное или максимальное значение игнорировались. +Исключен случай, когда пользователь мог ввести данные, не соответствующие ограничениям, которые установил разработчик. +
Прикладные объекты.
При сохранении табличного документа в формате .docx, рамки рисунков выгружаются так, как они заданы в табличном документе.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При сохранении табличного документа в формате .docx, рисунки всегда заключались в рамку. +Повышена корректность экспорта табличного документа в формат .docx. +
Прикладные объекты.
При сохранении табличного документа в формат .docx сохраняются следующие параметры печати табличного документа:
  • размер страницы;
  • ориентация страницы;
  • масштаб печати;
  • разбивка по страницам;
  • настройка полей;
  • колонтитулы;
  • признак отображения шапки на каждой странице;
  • признак отображения колонтитулов на первой странице.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При сохранении табличного документа в формат .docx параметры печати не сохранялись. +Повышено удобство дальнейшей работы с документом, сохраненным в формат .docx. +
Система компоновки данных.
При добавлении пользовательского поля в настройки системы компоновки данных с неустановленным источником доступных настроек, имя поля формируется на языке текущего варианта встроенного языка.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При добавлении пользовательского поля в настройки системы компоновки данных с неустановленным источником доступных настроек, имя поля формировалось на английском языке. +Поведение системы компоновки данных приведено в соответствие с аналогичными механизмами системы.
Работа с файлами.
Внешний вид и поведение диалога выбора файлов (включая объект ДиалогВыбораФайла), в ОС Windows Vista и выше, приведен к виду, принятому в этих операционных системах. В ОС Windows XP и ниже, а также в веб-клиенте, вид диалогов не изменился.В ОС Windows Vista и выше использовался устаревший диалог выбора файлов.Внешний вид диалога выбора файлов соответствует используемой операционной системе. +
Работа с файлами.
Если для объекта ДиалогВыбораФайла одновременно заданы свойства Каталог и ПолноеИмяФайла, диалог открывается в указанном каталоге и с указанным именем файла. +Если для объекта ДиалогВыбораФайла были одновременно заданы свойства Каталог и ПолноеИмяФайла, диалог игнорировал указанный каталог и использовал каталог, который был получен из полного имени файла.Работа с диалогом выбора файлов стала более комфортной.
Автоматизированное тестирование.
Для метода ВвестиТекст() объекта ТестируемоеПолеФормы реализована возможность работы с полями ввода, содержащими маску ввода. +Механизмы тестирования не поддерживали работу с полями ввода, содержащими маску ввода.Расширены возможности системы автоматизированного тестирования. +
Выгрузка/загрузка конфигурации в файлы.
В файлах выгрузки конфигурации в формат XML стандартные команды объектов метаданных получили имена вида Catalog.ИмяСправочника.StandardCommand.ИмяСтандартнойКоманды. Ранее выгруженные конфигурации не будут загружены. +В файлах выгрузки конфигурации в формат XML стандартные команды объектов метаданных имели имя Catalog.ИмяСправочника.ИмяСтандартнойКоманды. +Имена команд приведены к общему виду, по имени команды можно однозначно определить ее назначение. +
Выгрузка/загрузка конфигурации в файлы.
В файлах выгрузки конфигурации в формат XML команды объектов метаданных получили имена вида Catalog.ИмяСправочника.Command.ИмяКоманды. Ранее выгруженные конфигурации не будут загружены.В файлах выгрузки конфигурации в формат XML команды объектов метаданных обладали именами вида Catalog.ИмяСправочника.ИмяКоманды.Имена команд приведены к общему виду, по имени команды можно однозначно определить ее назначение. +
Выгрузка/загрузка конфигурации в файлы.
В файлах выгрузки конфигурации в формат XML стандартные команды управляемых форм получили имена вида Form.StandardCommand.ИмяКоманды. Ранее выгруженные конфигурации не будут загружены.В файлах выгрузки конфигурации в формат XML стандартные команды управляемых форм обладали именами вида FormStdCommand.ИмяКоманды. +Имена команд приведены к общему виду, по имени команды можно однозначно определить ее назначение. +
Выгрузка/загрузка конфигурации в файлы.
В файлах выгрузки конфигурации в формат XML команды управляемых форм получили имена вида Form.Command.ИмяКомандыФормы. Ранее выгруженные конфигурации не будут загружены. +В файлах выгрузки конфигурации в формат XML команды управляемых форм обладали именами вида FormCommand.ИмяКомандыФормы. +Имена команд приведены к общему виду, по имени команды можно однозначно определить ее назначение. +
Выгрузка/загрузка конфигурации в файлы.
В файлах выгрузки конфигурации в формат XML стандартные команды элементов управляемых форм получили имена вида Form.Item.ИмяЭлемента.StandardCommand.ИмяСтандартнойКоманды. Ранее выгруженные конфигурации не будут загружены.В файлах выгрузки конфигурации в формат XML стандартные команды элементов управляемых форм обладали именами вида Form<ТипЭлемента>.ИмяЭлемента.ИмяСтандартнойКоманды.Имена команд приведены к общему виду, по имени команды можно однозначно определить ее назначение. + +
Выгрузка/загрузка конфигурации в файлы.
При выгрузке конфигурации в файлы:
  • Ссылки на отсутствующие объекты конфигурации выгружаются в виде текстового представления идентификатора отсутствующего объекта конфигурации;
  • Свойства элемента управляемой формы УправляемаяФорма, имеющие смысл только в режиме «1С:Предприятие», не выгружаются;
  • Для реквизитов и элементов управляемой формы выгружаются внутренние идентификаторы, необходимые для сохранения настроек;
  • Для элементов диаграммы бизнес-процессов выгружаются идентификаторы элементов.
При выгрузке конфигурации в файлы:
  • Ссылки на отсутствующие объекты конфигурации игнорировались;
  • Выгружались свойства элемента управляемой формы УправляемаяФорма, имеющие смысл только в режиме «1С:Предприятие»;
  • Для реквизитов и элементов управляемой формы не выгружались внутренние идентификаторы, необходимые для сохранения настроек;
  • Для элементов диаграммы бизнес-процессов не выгружались идентификаторы элементов.
При выгрузке/загрузке конфигурации улучшено:
  • Обеспечение сохранения настроек пользователя, работающего с информационной базой (после загрузки конфигурации);
  • Точность анализа изменений при сравнении конфигураций (после загрузки конфигурации).
Управляемые формы.
При нажатии клавиши Esc в полях ввода (кроме многострочных полей ввода) выполняются следующие действия:
  • Если в поле ввода введен какой-либо текст, то в поле ввода возвращается представление значения, которое было там до начала ввода текста;
  • Если текст не изменялся - поле ввода не обрабатывает нажатие кнопки Esc и передает обработку кнопки форме.
Нажатие клавиши Esc всегда обрабатывалось формой. Поле ввода не выполняло никаких действий, если при редактировании текста нажать клавишу Esc.Появилась удобная возможность отказаться от изменения значения в поле ввода.
Управляемые блокировки.
Количество установленных управляемых блокировок, превышение которого приводит к установке блокировки на все пространство блокировки, равно 100 000. +Количество установленных управляемых блокировок, превышение которого приводило к установке блокировки на все пространство блокировки, было равно 20 000. + +Повышена параллельность работы при использовании транзакций с большим количеством (более 20 000) установленных блокировок в одном пространстве блокировок. +
Регистры сведений.
Обмен данными.
При передаче набора записей регистра сведений в качестве значения отбора метода ВыбратьИзменения() плана обмена, поведение системы зависит от установленного режима совместимости:
  • В случае, если установлен режим совместимости с версией 8.2.16 и младше, выборка содержит данные, не соответствующие отбору, определенному набором записей;
  • В случае, если установлен режим совместимости с версией 8.3.1 и старше (а также, если не используется режим совместимости), выборка содержит данные, полностью соответствующие отбору.
При передаче набора записей регистра сведений в качестве значения отбора метода ВыбратьИзменения() плана обмена, поведение системы не зависело от установленного режима совместимости:
  • Для версии 8.2.16 и младше, выборка содержала данные, не соответствующие отбору, определенному набором записей;
  • Для версии 8.3.1 и старше, выборка содержала данные, полностью соответствующие отбору.

Улучшена совместимость с предыдущими версиями системы. +
Динамический список.
Конструкции системы компоновки данных или построителя запросов, заключенные в фигурные скобки {}, не приводят к ошибкам при работе динамического списка. +Конструкции системы компоновки данных или построителя запросов, заключенные в фигурные скобки {}, в некоторых случаях могли приводить к ошибкам при работе динамического списка. +Повышена стабильность работы динамического списка. +
Криптография.
Значение параметра ИмяМодуляКриптографии в конструкторе объекта МенеджерКриптографии является регистро-независимым.Значение параметра ИмяМодуляКриптографии в конструкторе объекта МенеджерКриптографии было регистро-зависимым. +Поведение системы приведено в соответствие с общепринятыми стандартами. +
Управляемая форма.
Обычная форма.
Для управляемой и обычной формы изменилось место отображения меню, открываемого с помощью метода ВыбратьИзМеню() в том случае, если значением второго параметра метода (ЭлементФормы) выступает таблица управляемой формы, управляемая форма, табличное поле или обычная форма:
  • Для табличного поля или таблицы управляемой формы меню будет отображено в левом верхнем углу текущей ячейки или в левом верхнем углу табличного поля или таблицы управляемой формы, если текущую ячейку определить невозможно.
  • Для формы меню будет отображаться в левом верхнем углу.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Если значением второго параметра (ЭлементФормы) метода ВыбратьИзМеню() выступала таблица управляемой формы, управляемая форма, табличное поле или обычная форма, то меню открывалось следующим образом:
  • Для табличного поля или таблицы управляемой формы меню отображалось в левом нижнем углу элемента, переданного в качестве значения параметра.
  • Для формы меню отображалось в левом нижнем углу текущего элемента формы. Если текущий элемент определить нельзя, то меню отображалось в левом нижнем углу формы. В веб-клиенте меню отображалось в центре экрана.
Унифицировано поведение системы при открытии однотипных меню системой (например, контекстное меню в таблице управляемой формы) и прикладным решением (метод ВыбратьИзМеню()). +
Управляемая форма.
Обычная форма.
Для управляемой и обычной формы изменилось место отображения списка, открываемого с помощью метода ВыбратьИзСписка() в том случае, если значением второго параметра метода (ЭлементФормы) выступает таблица управляемой формы, управляемая форма, табличное поле или обычная форма:
  • Для табличного поля или таблицы управляемой формы список будет отображен в левом верхнем углу текущей ячейки или в левом верхнем углу табличного поля или таблицы управляемой формы, если текущую ячейку определить невозможно;
  • Для формы список будет отображаться в левом верхнем углу.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Если значением второго параметра (ЭлементФормы) метода ВыбратьИзСписка() выступала таблица управляемой формы, управляемая форма, табличное поле или обычная форма, то список открывался следующим образом:
  • Для табличного поля или таблицы управляемой формы список отображался в левом нижнем углу элемента, переданного в качестве значения параметра;
  • Для формы список отображался в левом нижнем углу текущего элемента формы. Если текущий элемент определить нельзя, то список отображался в левом нижнем углу формы.
  • В веб-клиенте список отображался в соответствии с настройками форм, в связи с тем, что список отображался с помощью системной формы.
Унифицировано поведение системы при выполнении аналогичных действий (методы ВыбратьИзМеню() и ВыбратьИзСписка()). +
Средства разработки.
Реализован поиск и замена для свойства объектов конфигурации ПараметрыВыбора. Для свойств объектов конфигурации СписокВыбора, СвязиПараметровВыбора изменен принцип поиска и замены.

Поиск и замена выполняется:

  • Для свойства ПараметрыВыбора - в колонках Имя и Значение (в том числе и среди элементов фиксированных массивов). Поиск выполняется среди значений типа Строка;
  • Для свойства СписокВыбора - в колонке Представление и в колонке Значение, если значение имеет тип Строка;
  • Для свойства СвязиПараметровВыбора - в колонке Имя;
  • Запрос на продолжение поиска или замены выдается после нахождения каждого вхождения искомой строки.

Поиск в свойстве объектов конфигурации СвязьПоТипу более не выполняется. +

Поиск и замена в свойствах объектов конфигурации СвязиПараметровВыбора выполнялся только по колонке Имя.

Поиск и замена в свойствах объектов конфигурации СписокВыбора выполнялся только по полю Представление.

Не выполнялся поиск и замена в свойствах объектов конфигурации ПараметрыВыбора.

Выполнялся поиск в свойствах объектов конфигурации СвязьПоТипу. +

Поиск и замена в свойствах объектов конфигурации приведен в соответствие с аналогичными операциями для текстов. +
Средства разработки.
Для свойства объектов конфигурации ПараметрыВыбора изменено представление в окне свойств объекта. В том случае, когда значением какого-либо элемента свойства является фиксированный массив, в качестве представления используются представления значений массива.

Для свойства объектов конфигурации СписокВыбора изменено представление в окне свойств объекта. В качестве представления выступают и значения элементов списка и его представления (если они заданы).

Если значением какого-либо элемента свойства ПараметрыВыбора выступал фиксированный массив, то представлением такого значения была строка ФиксированныйМассив.

Для свойства объектов конфигурации СписокВыбора представление в окне свойств объекта формировалось только из представлений значений списка.

В конфигураторе повышена комфортность работы со свойствами ПараметрыВыбора и СписокВыбора.
Управляемая форма.
Изменен внешний вид выпадающего списка для поля формы, отображающего данные ссылочного типа, перечисления или системные перечисления:
  • Надпись Нажмите показать все ... отображается в списке в том случае, если поле отображает данные ссылочного типа или перечисления и у поля ввода присутствует кнопка выбора;
  • Если список выбора открыт и в нем есть выбранная строка, то нажатие клавиш Tab, Shift+Tab и Enter, приводит к выбору текущего значения в списке. Выбор мышью другого элемента формы, не приводит к выбору выбранной строки, а приводит только к закрытию списка (аналогично кнопке Esc). При этом выбранный мышью элемент формы не активизируется;
  • Если список выбора закрыт и в нем есть выбранная строка (не из истории или списка выбора), то нажатие клавиш Tab, Shift+Tab и Enter, а также выбор мышью другого элемента формы, приводит к выбору значения.
  • Если список выбора закрыт и в нем нет выбранной строки, то нажатие клавиш Tab, Shift+Tab и Enter, а также выбор мышью другого элемента формы, приводит к открытию списка.
Выпадающий список имел другой внешний вид. +Повышение удобства работы с полем ввода, отображающим данные ссылочного типа, перечисления или системные перечисления. +
Регистры накопления.
Режим агрегатов можно включать для любого оборотного регистра накопления, вне зависимости от наличия агрегатов, заданных в метаданных.

В клиент-серверном варианте возможно создание новых оптимальных агрегатов (и удаление устаревших) при выполнении операции перестроения агрегатов в режиме «1С:Предприятие».

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Для поддержания актуального списка оптимальных агрегатов было необходимо добавлять агрегаты в конфигураторе. +Упрощена поддержка списка оптимальных агрегатов - для этого достаточно регулярно выполнять операцию перестроения агрегатов. +
Управляемая форма.
Для полей ввода, отображающих данные ссылочного типа, при активизации элемента цветом выделяется только текстовое представление отображаемого значения.При активизации поля ввода, отображающего данные ссылочного типа, цветом выделялось все внутреннее пространство поля. +Повышен комфорт использования поля ввода. Стало возможным отображать подсказку, расположенную в поле ввода, в том случае, если поле ввода, связанное с данными ссылочного типа, стоит первым в порядке обхода на форме. +
Хранилище конфигурации.
Реализована возможность быстрого выборочного сравнения объектов конфигурации. Данная возможность доступна при работе с хранилищем и из окна сравнения и объединения конфигураций.

Выборочное сравнение реализовано для следующих объектов: модуль, макет, картинка, WS-ссылка, расписание, агрегаты регистра, состав плана обмена, стиль, рабочая область рабочего стола, карта маршрута, форма, справочная информация, предопределенные элементы, фрагмент командного интерфейса, права роли.

Для вызова команды выборочного сравнения в контекстном меню диалогов работы с хранилищем и окна сравнения конфигураций реализована команда Сравнить выборочно с объектом конфигурации. +Выборочное сравнение объектов конфигурации возможно только для версий объектов, помещенных в хранилище конфигурации с помощью «1С:Предприятия» версии 8.2.9 и более старшей.

Данная возможность не предоставлялась.

При сравнении конкретного объекта выполнялось сравнение двух конфигураций целиком, с позиционированием в окне сравнения на используемом объекте.

Повышен комфорт работы с хранилищем конфигурации. Ускорен процесс сравнения в том случае, когда требуется сравнить конкретный объект конфигурации.
Работа с СУБД.
Кластер, созданный стандартной версией PostgreSQL (без исправлений от фирмы «1С»), может быть использован версией PostgreSQL с исправлениями от фирмы «1С», начиная с версии 9.2.1-2.1С.

Все необходимые настройки для корректной работы выполняются программой установки PostgreSQL (с исправлениями от фирмы «1С») автоматически в том случае, если на компьютере отсутствует кластер, созданный стандартными версиями PostgreSQL. +

Кластер, создаваемый стандартными версиями PostgreSQL, было невозможно использовать с помощью версии PostgreSQL, содержащей исправления фирмы «1С».Теперь «1С:Предприятие» может работать с кластером, созданными с использованием следующих версий СУБД PostgreSQL:
  • PostgreSQL 8.1.5-X.1C - 9.1.2-1.1C;
  • PostgreSQL 9.2.1-2.1C;
  • Стандартной версией PostgreSQL при условии совпадения национальных установок (locale) кластера и создаваемой информационной базы.

Изменение версии «1С:Предприятия» (как увеличение, так и уменьшение версии), без смены версии PostgreSQL, не приводит к необходимости выполнять какие-либо действия.

Следует иметь ввиду, что переход на новую версию PostgreSQL приводит к невозможности использовать более старые версии «1С:Предприятия» (8.3.2 и ранее). Это относится только к новым информационным базам, созданным с использованием PostgreSQL версии 9.2.1-2.1С. Не следует создавать информационные базы с использованием PostgreSQL версии 9.2.1-2.1С, если есть необходимость работы с такой информационной базой с помощью более ранних версий платформы.

Управляемая форма.
Если обработчик события ОбработкаПолученияДанныхВыбора менеджера перечисления возвращает пустой список и при возврате из этого обработчика значение формального параметра СтандартнаяОбработка установлено в значение Ложь, то для выбора будет использован полученный список.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Если обработчик события ОбработкаПолученияДанныхВыбора менеджера перечисления возвращает пустой список и при возврате из этого обработчика значение формального параметра СтандартнаяОбработка установлено в значение Ложь, то клиентское приложение заполняло список выбора всеми значениями перечисления.Поведение системы стало более ожидаемым в том случае, если прикладной разработчик принимает решение в каком-то случае полностью заблокировать возможность выбора значений перечисления.
Стандартные функции.
Представление отбора в стандартной форме просмотра журнала регистрации осуществляется в локализованном виде.Представление отбора в стандартной форме просмотра журнала регистрации всегда осуществлялось в виде русскоязычных имен колонок журнала регистрации.Представление отбора приведено в соответствие с аналогичными механизмами системы.
Хранилище конфигурации.
При работе с хранилищем конфигурации оптимизирован алгоритм контроля ссылочной целостности во время операций помещения в хранилище или получения из хранилища удаляемых объектов или объектов, ссылающихся на удаленные.

При удалении объектов, в некоторых случаях, нет необходимости захватывать объекты, содержащие ссылки на удаляемые объекты.

Алгоритм контроля ссылочной целостности при удалении объекта из хранилища конфигурации приведен в соответствие с алгоритмом контроля ссылочной целостности при удалении объекта из конфигурации, не подключенной к хранилищу конфигурации.

В режиме совместимости с версией 8.3.2 поведение хранилища конфигурации не изменилось.

Алгоритм контроля ссылочной целостности при операциях с хранилищем работал без оптимизации.

При удалении объектов из хранилища конфигурации, алгоритм контроля ссылочной целостности отличался от алгоритма контроля ссылочной целостности при удалении объектов из конфигурации, не подключенной к хранилищу.

Ликвидированы проблемы при удалении объектов из конфигурации из-за разных алгоритмов контроля ссылочной целостности. Помещение в хранилище конфигурации удаленных объектов стало происходить быстрее.
Управляемая форма.
Если для объекта конфигурации выбран режим редактирования В списке и прикладное решение исполняется в управляемом режиме толстого клиента, то при использовании метода ОткрытьЗначение() или кнопки Открыть в поле ввода, будет открыта обычная форма списка при выполнении всех условий:
  • Выбран способ редактирования В списке;
  • Существует обычная форма списка, выбранная в качестве основной или дополнительной;
  • В прикладном решении разрешено использование обычных форм в управляемом приложении;
  • Отсутствует управляемая форма списка или объекта, выбранная в качестве основной или дополнительной.

Во всех остальных случаях будет открываться форма объекта.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Если для объекта конфигурации выбран режим редактирования В списке и прикладное решение исполняется в управляемом режиме толстого клиента, то при использовании метода ОткрытьЗначение() или кнопки Открыть в поле ввода, открывалась управляемая форма списка.Система более корректно выбирает обычную форму списка для отображения или редактирования элемента для объектов конфигурации, для которых установлен режим редактирования В списке.
Средства разработки.
В процессе сравнения конфигураций реализованы следующие изменения:
  • Из операции сравнения исключен узел, которому подчинены элементы предопределенных данных;
  • Отсутствие справочной информации и пустая справочная информация считаются одинаковыми;
  • Дополнительные свойства элемента управляемой формы УправляемаяФорма, которые имеют смысл только в режиме «1С:Предприятие», исключены из процесса сравнения.
В процессе сравнения конфигураций:
  • В операцию сравнения входил узел, которому подчинены элементы предопределенных данных;
  • Отсутствие справочной информации и пустая справочная информация отмечались как различные;
  • Дополнительные свойства элемента управляемой формы УправляемаяФорма, которые имеют смысл только в режиме «1С:Предприятие», участвовали в процессе сравнения.
Поведение операции сравнения конфигураций стало более логичным.
Управляемая форма.
При формировании списка выбора для полей формы, связанных с данными типа ПеречислениеСсылка, используются параметры выбора и связи параметров выбора, заданные для элемента формы.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При формировании списка выбора для полей формы, связанных с данными типа ПеречислениеСсылка, параметры выбора и связи параметров выбора не использовались.Формирование списка выбора для перечислений приведено в соответствие с аналогичными механизмами системы.
Работа с Интернет.
Для свойства АутентификацияSMTP (устаревшее) объекта ИнтернетПочтовыйПрофиль по умолчанию устанавливается значение СпособSMTPАутентификации.ПоУмолчанию.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Для свойства АутентификацияSMTP (устаревшее) объекта ИнтернетПочтовыйПрофиль по умолчанию устанавливалось значение СпособSMTPАутентификации.БезАутентификации.Установки по умолчанию обеспечивают выбор максимально безопасного способа аутентификации из поддерживаемых почтовым сервером, с которым устанавливается соединение.
Работа с Интернет.
Если свойство ТолькоЗащищеннаяАутентификацияSMTP объекта ИнтернетПочтовыйПрофиль установлено в значение Истина, то попытка аутентификации пользователя выполняется независимо от прочих настроек.

Аутентификация пользователя SMTP-сервера не выполняется в следующих случаях:

  • Значением свойства ПользовательSMTP объекта ИнтернетПочтовыйПрофиль является пустая строка;
  • Свойство АутентификацияSMTP объекта ИнтернетПочтовыйПрофиль установлено в значение СпособSMTPАутентификации.БезАутентификации;
  • Свойство POP3ПередSMTP объекта ИнтернетПочтовыйПрофиль установлено в значение Истина.

Аутентификация пользователя SMTP-сервера не осуществлялась, если не было указано имя пользователя SMTP-сервера (свойство ПользовательSMTP объекта ИнтернетПочтовыйПрофиль).

Реализована возможность выполнять аутентификацию на SMTP-сервере с помощью POP3-сервера, в том случае, если не установлено свойство ТолькоЗащищеннаяАутентификацияSMTP и вне зависимости от значения свойства ПользовательSMTP объекта ИнтернетПочтовыйПрофиль. При этом аутентификация не будет выполнена, если почтовый сервер не поддерживает безопасные способы аутентификации.

Появилась возможность требовать наличие только безопасных способов аутентификации при осуществлении соединения с почтовым сервером.

Программное лицензирование.
Если диалог активации лицензии открывается при запуске клиентского приложения, то на первой странице уточняется, какая лицензия не обнаружена: серверная или клиентская.

На страницах регистрации лицензии и странице, открывающейся в случае отказа в активации лицензии, находится гиперссылка на контактные данные центра лицензирования. Реализован диалог с контактной информацией центра лицензирования.

При вводе пинкода (или резервного пинкода), а также в форме ввода ответа оператора центра лицензирования реализован автоматический переход между группами символов во вводимой информации.

Когда диалог активации лицензии открывается при запуске клиентского приложения, на первой странице не было информации о том, какая лицензия не найдена.

На страницах регистрации лицензии и странице, открывающейся в случае отказа в активации лицензии, находилась информация только о том, в каком печатном документе можно найти контактную информацию центра лицензирования.

При вводе пинкода (или резервного пинкода), а также в форме ввода ответа оператора центра лицензирования отсутствовал автоматический переход между группами символов.

Работа с диалогом активации лицензии стала более удобной.
Табличный документ.
Веб-клиент.
При работе в веб-клиенте реализована поддержка ориентации текста в ячейке табличного документа.При работе в веб-клиенте не поддерживалась ориентация текста в ячейке табличного документа.Расширены возможности оформления табличных документов при работе в веб-клиенте.
Кластер серверов.
При выполнении переназначения сервиса кластера из одного менеджера кластера в другой, выполняется перенос состояния сервиса, а также происходит завершение работы сервиса на исходном менеджере кластера и выполняется освобождение занимаемых ресурсов.

Реализована репликация состояния для сервисов: объектных блокировок, нумерации и фоновой реструктуризации.

В технологический журнал добавлено событие <SRVC>, отражающее операции с сервисами кластера: запуск, остановка и различные оповещения. Описание выполняемых операций формируется в свойстве Descr.

Каждый менеджер кластера хранит «свои» сеансовые данные в персональной директории. +Реализована возможность выбирать, по какому критерию будет выбираться рабочий процесс при создании нового соединения: по доступной производительности или по доступной памяти. В случае выбора по доступной памяти, выбирается тот рабочий прочесс, который уже обслуживает соединения с данной информационной базой или тот, который запущен на сервере с максимальным количеством свободной оперативной памяти.

В свойствах кластера реализовано свойство Режим распределения нагрузки. Для объекта IClusterInfo реализовано свойство LoadBalancingMode.

Для запуска фонового задания приоритетно выбирается рабочий процесс, обслуживающий сеанс, инициировавший запускаемое фоновое задание (если выбран режим выбора по доступной памяти - данное правило будет игнорироваться).

Для требования назначения реализована возможность задавать приоритет требования. Если в результате подбора требований будет выбрано несколько одинаковых требований, то, при прочих равных условиях, будет применено требование с максимальным значением приоритета. В свойствах требования назначения функциональности реализовано свойство Приоритет. Для объекта IAssignmentRule реализовано свойство Priority. Реализован параметр load-balancing-mode для команд create и update режима cluster утилиты администрирования кластера серверов (rac). Аналогичные изменения внесены в интерфейс работы с сервером администрирования из языка Java.

При определении доступной производительности рабочего процесса дополнительно учитывается загруженность процессоров, обслуживающих рабочий сервер и количество потоков, находящихся в очереди на исполнение.

Переназначение сервисов в некоторых случаях могло не выполнять освобождение занимаемых ресурсов.

Не выполнялась репликация состояния для сервисов: объектных блокировок, нумерации и фоновой реструктуризации.

Не предоставлялось событий, отражающих операции с сервисами кластера.

Сеансовые данные хранились в одном каталоге, что в некоторых случаях могло приводить к конфликтам доступа к ним.

Рабочий процесс при создании фонового задания всегда выбирался по критерию доступной производительности.

Если в результате подбора требований было выбрано несколько одинаковых требований, то, в общем случае, было невозможно однозначно определить примененное требование.

При определении доступной производительности рабочего процесса не учитывалась загруженность процессора и количество потоков, находящихся в очереди на исполнение.

Повышена отказоустойчивость кластера. Повышено качество (и управляемость) процесса распределения нагрузки по серверам кластера. С помощью специальной настройки обеспечивается эффективное использование памяти в том случае, если кластер обслуживает большое количество информационных баз с небольшим количеством сеансов на каждой информационной базе.
Управляемая форма.
Изменен цвет заголовка и рамки (линии) недоступной группы.Заголовок и рамка (линия) недоступной группы имели другой цвет.Отображение недоступной группы приведено в соответствие с отображением других недоступных элементов системы.
Прикладные объекты.
Общие реквизиты / Разделение данных.
Права доступа.
Обмен данными.
Мобильное приложение.
Реализована возможность использовать предопределенные данные для объектов конфигурации, входящих в состав разделителя в режиме Независимо и совместно.

Реализована возможность связывать предопределенные элементы с любыми элементами данных соответствующего типа (в том числе и не выполнять такое связывание - «удалять» предопределенные данные). Для объектов конфигурации, которые могут содержать предопределенные данные, реализовано свойство ИмяПредопределенныхДанных. Реализована поддержка работы с предопределенными элементами в данных, которые ссылаются на удаленные из метаданных предопределенные элементы.

Ссылки на предопределенные элементы более не являются одинаковыми, в том числе и в различных областях (даже для объектов, входящих в состав разделителя в режиме Независимо). Метод ПолучитьИмяПредопределенного() является устаревшими и поддерживается для совместимости.

Предопределенные данные регистрируются в планах обмена как и остальные данные.

Реализована возможность управлять созданием и обновлением предопределенных данных в информационной базе: свойство объекта конфигурации ОбновлениеПредопределенныхДанных и методы ПолучитьОбновлениеПредопределенныхДанных()/УстановитьОбновлениеПредопределенныхДанных().

Реализован метод глобального контекста ИнициализироватьПредопределенныеДанные(), с помощью которого можно создать отсутствующие объекты данных для предопределенных элементов (в рамках текущей области данных).

Права доступа и ограничения доступа к данным синхронно назначаются на поля Предопределенный и ИмяПредопределенныхДанных.

Данные возможности реализованы также для мобильной платформы.

Реализованы права доступа ИнтерактивноеУдалениеПредопределенныхДанных, ИнтерактивнаяПометкаУдаленияПредопределенныхДанных, ИнтерактивноеСнятиеПометкиУдаленияПредопределенныхДанных, ИнтерактивноеУдалениеПомеченныхПредопределенныхДанных, которые влияют на возможность редактирования предопределенных данных.

Исключены ограничения на редактирование предопределенных данных в планах счетов и планах видов расчетов, разрешено помечать предопределенные данные на удаление и полное удаление предопределенных данных.

План счетов должен входить в состав всех разделителей, в состав которых входят все субконто, в нем используемые.

Изменен процесс реструктуризации информационной базы.

В режиме совместимости с версией 8.3.2 поведение не изменилось. +

Было невозможно использовать предопределенные данные для объектов конфигурации, входящих в состав разделителя в режиме Независимо и совместно. Было невозможно связать с предопределенными данными любой существующий объект данных. Один предопределенный элемент имел одинаковую ссылку во всех областях данных. При обмене данными (распределенная информационная база), предопределенные данные передавались только с изменениями конфигурации прикладного решения. Управлять созданием и обновлением предопределенных данных было невозможно.Стало возможно использовать предопределенные данные для любых режимов разделения. Работа с предопределенными данными стала более гибкой.
Интерфейс.
Ссылки на внешние ресурсы в главах справки открываются с помощью веб-браузера используемой ОС.Ссылки на внешние ресурсы в главах справки открывались встроенным веб-браузером системы «1С:Предприятие».Повышено удобство просмотра ресурсов, ссылки на которые представлены в справке.
Интерфейс.
Для новых пользователей устанавливается режим интерфейса Формы в закладках в том случае, если не используется режим совместимости и режим совместимости интерфейса установлен в значение Версия82 или Версия82РазрешитьТакси.Для новых пользователей режим интерфейса устанавливался в значение Формы в отдельных окнах.Интерфейс Формы в закладках устанавливается в качестве интерфейса по умолчанию для новых пользователей. Этот режим интерфейса более эргономичен.
Интерфейс.
Для поля ввода, расположенного в таблице управляемой формы, выпадающий список всегда появляется при начале редактирования.Для поля ввода, расположенного в таблице управляемой формы, выпадающий список появлялся только при начале редактирования мышью.Реализован быстрый доступ к выпадающему списку для полей ввода, расположенных в таблицах управляемых форм.
Общие реквизиты / Разделение данных.
Встроенный язык.
После удаления данных области данных (или информационной базы) с помощью метода УдалитьДанныеИнформационнойБазы() (или ключа командной строки запуска /EraseData), состояние области данных соответствует таковому при первом входе в область данных после ее создания. В частности:
  • Таблицы перечислений не изменяются;
  • При установленном режиме совместимости с версией 8.3.2 или младше, предопределенные данные получают значения, определенные в конфигураторе или значения по умолчанию. При отключенном режиме совместимости предопределенные данные будут созданы при первом обращении к ним;
  • Значения реквизитов элемента ЭтотУзел планов обмена будут установлены в значения по умолчанию;
  • Значения неразделенных констант получают значения по умолчанию, а значения разделенных констант удаляются.
После удаления данных области данных (или информационной базы) с помощью метода УдалитьДанныеИнформационнойБазы() (или ключа командной строки запуска /EraseData), состояние области данных не соответствовало состоянию области, которое она получала при первом входе в область после ее создания:
  • Удалялись таблицы перечислений;
  • Сохранялись значения предопределенных данных неразделенных объектов;
  • Сохранялись значения реквизитов элемента ЭтотУзел планов обмена;
  • Значения констант сохраняли свои значения.
При удалении данных с помощью метода УдалитьДанныеИнформационнойБазы() (или ключа командной строки запуска /EraseData) поведение в большей степени отражает начальное состояние данных.
Внешний вид приложения.
Реализована новая заставка для конфигуратора, клиентского приложения, программы Autorun и программы установки системы.

Размер области вывода заставки (и картинки для создания заставки прикладного решения) равен 600 на 255 точек.

Картинка стандартной заставки размещена на диске ИТС.

Для различных приложений системы использовались другие заставки. Размер картинки для создания заставки прикладного решения был 305 на 110 точек.Новая заставка лучше соответствует новому внешнему виду системы.
Управляемая форма.
При установке значения в поле ввода, устанавливаемое значение приводится к значению, которое редактируется полем ввода и затем поле ввода отображает представление получившегося значения.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При установке значения в поле ввода, текст, который отображается полем ввода, мог не соответствовать значению, которое помещалось в поле ввода после установки нового значения.Поведение системы стало более логичным. Исключено ошибочное поведение системы.
Клиентское приложение.
Уточнено сообщение, возникающее при попытке обновления клиентского приложения через небезопасное соединение.Сообщение было недостаточно понятным.Сообщение более четко описывает ситуацию.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Выгрузка/загрузка конфигурации в файлы.
В файлы выгрузки попадают только те права доступа, значения которых отличаются от значений по умолчанию. +При определении значений по умолчанию, для каждой роли учитываются значения флажков Устанавливать права для новых объектов и Устанавливать права для реквизитов и табличных частей по умолчанию. Значения этих флажков являются значениями по умолчанию для прав на объект метаданных и прав на реквизиты и табличные части соответственно.В файлы выгрузки попадали все права доступа, в том числе и те, значения которых были равны значениям по умолчанию. +Ускорена выгрузка конфигурации в файлы, уменьшен объем файлов выгрузки. +
Прикладные объекты.
Англоязычное имя типа выборки из журнала документов получило имя вида DocumentJournalSelection.ИмяЖурналаДокументов. +Англоязычное имя типа выборки из журнала документов имело вид DocumentJournalsManager.ИмяЖурналаДокументов.Имена типов приведены к общему виду. +
Работа с файлами.
При получении файла (файлов) из информационной базы с помощью метода ПолучитьФайл() (ПолучитьФайлы()) выполняется проверка права Просмотр на реквизит, в котором хранятся данные файла.

Если используется метод ПолучитьФайлы(), то отсутствие доступа хотя-бы к одному файлу, из списка получаемых, приводит к отказу выполнения всей операции.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При выполнении операции получения файла (файлов) из информационной базы с помощью метода ПолучитьФайл() (ПолучитьФайлы()) не выполнялась проверка прав на реквизит, в котором хранятся данные файла.Унификация поведения с другими механизмами системы.
Средства разработки.
Проверка наличия реквизита Ссылка (Ref) в табличных частях справочников, планов видов характеристик, планов счетов, планов видов расчета, планов обмена, бизнес-процессов и задач выполняется перед обновлением конфигурации базы данных. Наличие такого реквизита ведет к невозможности реструктуризации.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Не происходила проверка наличия реквизита Ссылка (Ref) в табличных частях справочников, планов видов характеристик, планов счетов, планов видов расчета, планов обмена, бизнес-процессов и задач перед выполнением операции обновления конфигурации.Недопущение ошибок в прикладных решениях.
Кластер серверов.
Для утилиты администрирования кластера серверов (rac) исключены параметры name и cluster-port команды server update. В интерфейсе работы с сервером администрирования из языка Java у интерфейса IWorkingServerInfo удалены методы setName() и setClusterMainPort().

Для утилиты администрирования кластера серверов (rac) исключен параметр security-level команды infobase update. В интерфейсе работы с сервером администрирования из языка Java у интерфейса IInfoBaseInfo удален метод setSecurityLevel().

Для команды server update утилиты администрирования кластера серверов (rac) существовали параметры name и cluster-port. Параметры не использовались и ошибка при их использовании не выдавалась. В интерфейсе работы с сервером администрирования из языка Java у интерфейса IWorkingServerInfo существовали методы setName() и setClusterMainPort(). Выполнение методов не приводило к ошибке и не выполняло никаких действий.

Для команды infobase update утилиты администрирования кластера серверов (rac) существовал параметр security-level. Параметр не использовался и ошибка при его использовании не выдавалась. В интерфейсе работы с сервером администрирования из языка Java у интерфейса IInfoBaseInfo существовал метод метод setSecurityLevel(). Выполнение метода не приводило к ошибке и не выполняло никаких действий.

Параметры команд утилиты администрирования (rac) и набор методов интерфейсов для работы с сервером администрирования на языке Java приведены в соответствие с реальным функционированием системы.

Параметры рабочего сервера могут быть установлены при регистрации рабочего сервера в кластере.

Уровень безопасности информационной базы может быть задан при добавлении информационной базы в кластер.

Средства администрирования.
Кластер серверов.
Стало невозможным подключение утилиты администрирования кластера серверов (rac) предыдущих версий (8.3.1 и 8.3.2) к текущей версии сервера администрирования (ras).

Стало невозможным подключение утилиты администрирования кластера серверов (rac) текущей версии к предыдущим версиям (8.3.1 и 8.3.2) сервера администрирования (ras).

Утилита администрирования кластера серверов (rac) могла подключаться к любой версии сервера администрирования (ras).Исключена возможность работы несовместимых версий сервера администрирования кластера серверов (ras) и утилиты администрирования кластера серверов (rac).
Работа с файлами.
Работа в ОС Linux.
Реализована возможность получения файловой маски, описывающей все файлы, в зависимости от операционной системы, под управлением которой работает «1С:Предприятие». Для этого реализованы методы ПолучитьМаскуВсеФайлы(), ПолучитьМаскуВсеФайлыКлиента() и ПолучитьМаскуВсеФайлыСервера().Данная возможность не предоставлялась.Появилась возможность реализации программного кода, работающего с файлами, функционирование которого не зависит от ОС, под управлением которой исполняется «1С:Предприятие».
Работа с файлами.
Работа в ОС Linux.
Реализована возможность получения разделителя пути к файлу, в зависимости от операционной системы, под управлением которой работает «1С:Предприятие». Для этого реализованы методы ПолучитьРазделительПути(), ПолучитьРазделительПутиКлиента() и ПолучитьРазделительПутиСервера().Данная возможность не предоставлялась.Появилась возможность реализации программного кода работающего с файлами, работа которого не зависит от ОС, под управлением которой исполняется «1С:Предприятие».
Работа с ZIP-архивами.
Изменено поведение объекта ЗаписьZipФайла. Если у пользователя, от имени которого работает система, отсутствует право на просмотр списка файлов для каталога, откуда добавляются файлы, то:
  • Файл будет успешно добавлен в архив, если в имени файла нет символов подстановки (? или *);
  • Будет сформировано исключение, если имя файла содержит символы подстановки (? или *).

Изменено поведение объекта ЧтениеZipФайла. В том случае, когда у пользователя, от имени которого работает система, отсутствуют права на просмотр списка файлов в каталоге, где расположен архив, архив будет открыт только для чтения. +В режиме совместимости с версией 8.3.2 поведение не изменилось.

Если у пользователя, от имени которого работает система, отсутствует право на просмотр списка файлов для каталога, откуда добавляются файлы в архив с помощью объекта ЗаписьZipФайла, то файл(ы) в архив не добавлялся и архив создавался некорректно.

Архив не мог быть открыт с помощью объекта ЧтениеZipФайла в том случае, если у пользователя, от имени которого работает система, не было прав на просмотр содержимого каталога, содержащего архивный файл.

Поведение объектов ЗаписьZipФайла и ЧтениеZipФайла стало более логичным. При формировании архивного файла уменьшена вероятность создания некорректного архивного файла.
Хранилище конфигурации.
Для хранилища конфигурации реализован режим совместимости с «1С:Предприятием» версии 8.3.2 и более младших версий. Если режим совместимости для хранилища не используется, то:
  • Используется новая структура базы данных хранилища конфигурации;
  • Используется оптимизированный способ взаимодействия с сервером хранилища конфигурации.

При отключенном режиме совместимости работать с хранилищем можно только с помощью «1С:Предприятия» версии 8.3.3 и старше.

Реализован ключ командной строки запуска конфигуратора ConfigurationRepositoryClearCache, предназначенный для очистки локального кеша хранилища конфигурации.

Реализована возможность прерывания выполнения операции с хранилищем с помощью сочетания клавиш Ctrl+Break (не зависит от режима совместимости хранилища).

Использовалась старая структура базы данных хранилища конфигурации. Некоторые операции при работе с хранилищем выполнялись недостаточно эффективно.

Отсутствовал ключ командной строки запуска конфигуратора ConfigurationRepositoryClearCache.

Сочетание клавиш Ctrl+Break не приводило к прерыванию выполнения операции работы с хранилищем.

Повышена скорость работы с хранилищем конфигурации, в том случае, если работа с ним выполняется через сервер хранилища.
Прикладные объекты.
Свойство Отбор структуры параметров, которая передается в формальный параметр Параметр метода ПолучитьДанныеВыбора() и обработчика ОбработкаПолученияДанныхВыбора, может содержать элементы со значениями типа СписокЗначений и Массив. Для таких значений система применяет вид сравнения В списке, аналогично значению типа ФиксированныйМассив.Свойство Отбор структуры параметров, которая передается в формальный параметр Параметр метода ПолучитьДанныеВыбора() и обработчика ОбработкаПолученияДанныхВыбора, не могло содержать элементы со значениями типа СписокЗначений и Массив.Расширены возможности передачи значений отбора при получении данных выбора. Уменьшено количество преобразований данных, которые реально не требуются.
Фоновые и регламентные задания.
Реализована работа фоновых и регламентных заданий в файловом варианте информационной базы, без использования метода глобального контекста ВыполнитьОбработкуЗаданий(). Метод ВыполнитьОбработкуЗаданий() не выполняет никаких действий. Фоновые и регламентные задания выполняются в одном из клиентских приложений, подключенных к информационной базе. Поведение фоновых и регламентных заданий обладает некоторыми особенностями (полный перечень отражен в документации):
  • Регламентное задание выполняется тем клиентским приложением, которому назначена обработка регламентных заданий (по умолчанию - первым запущенным сеансом);
  • Фоновое задание, инициированное сеансом, выполняется тем же клиентским приложением, которое его инициировало;
  • В рамках клиентского приложения, в один момент времени, всегда выполняется одно фоновое задание (в том числе и регламентное).

Для определения клиентского приложения, которое будет выполнять регламентные задания, реализован ключ командной строки запуска клиентского приложения AllowExecuteScheduledJobs.

В диалоге автоматического подключения предметов отладки, в конфигураторе, установка флажка Фоновые задания влияет на подключение к фоновым заданиям не только на сервере, но и на клиенте.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

В файловом варианте информационной базы работа фоновых и регламентных заданий была возможна только с использованием метода глобального контекста ВыполнитьОбработкуЗаданий().

В диалоге автоматического подключения предметов отладки, в конфигураторе, установка флажка Фоновые задания влияло на подключение к фоновым заданиям только на сервере.

Разработчикам прикладных решений более не требуется прикладывать дополнительных усилий для того, чтобы в файловом варианте информационной базы выполнялись фоновые и регламентные задания, используемые прикладным решением.
Прикладные объекты.
Общие реквизиты / Разделение данных.
Для успешного выполнения чтения или записи разделенной константы, выполняемого с помощью свойства Константы глобального контекста, необходимо, чтобы были установлены значения всех совместных разделителей, в состав которых входит константа. В противном случае будет сгенерировано исключение.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Чтение или запись разделенной константы, выполняемое с помощью свойства Константы глобального контекста, выполнялось успешно даже в том случае, если были не заданы значения совместных разделителей, в состав которых входит константа.Унификация поведения с другими, аналогичными, механизмами системы.
Работа в ОС Linux.
Утилита конфигурирования для работы в ОС Linux config_system удалена из состава поставки. Поиск шрифтов из состава MS Core Fonts, необходимых для работы системы, выполняется системой автоматически в следующих каталогах:
  • /usr/share/fonts/truetype/msttfcorefonts;
  • /usr/share/fonts/msttfcorefonts;
  • $HOME/.fonts.

Система пытается автоматически найти необходимые динамические библиотеки в том случае, если используются функции, расположенные в этих динамических библиотеках.

При отсутствии необходимого шрифта или динамической библиотеки выдается сообщение об ошибке.

Необходимая информация о настройке ОС Linux отражена в документации. +

Утилита конфигурирования для работы в ОС Linux config_system входила в состав поставки. Отсутствие необходимых шрифтов или динамических библиотек не диагностировалось явным образом, а могло приводить к различным ошибкам и неожиданному поведению.

Информация, необходимая для настройки ОС Linux для работы системы «1С:Предприятие», не отражалась в документации.

Упрощена настройка ОС Linux для запуска «1С:Предприятия». Улучшена диагностика проблемных ситуаций.
Права доступа.
Работа с запросами.
Регистры накопления.
Регистры бухгалтерии.
Права доступа на автоматические поля периодичности (ПериодГод, ПериодПолугодие, ПериодКвартал, ПериодМесяц, ПериодДекада, ПериодДень, ПериодЧас, ПериодСекунда) виртуальных таблиц регистров накопления и бухгалтерии получаются из соответствующих прав доступа стандартного реквизита Период.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Права доступа на автоматические поля периодичности виртуальных таблиц регистров накопления и бухгалтерии зависили от состояния флажка Устанавливать права для реквизитов и табличных частей по умолчанию. Если флажок установлен, то считалось, что право есть.Работа с правами доступа стала более логичной.
Методики разработки.
В документацию включен раздел, содержащий рекомендации по разработке кросс-платформенных прикладных решений.В документации отсутствовал раздел, содержащий рекомендации по разработке кросс-платформенных прикладных решений.Прикладные разработчики получили рекомендации по созданию кроссплатформенных прикладных решений с минимальными затратами.
Управляемые блокировки.
Реализована возможность устанавливать управляемые транзакционные блокировки по реквизитам объектов. Для указания реквизитов, по которым возможна блокировка, реализовано свойство ПоляБлокировкиДанных для следующих объектов конфигурации:
  • Справочник;
  • Документ;
  • План видов характеристик;
  • План видов расчета;
  • Бизнес-процесс;
  • Задача;
  • План счетов;
  • План обмена.

При записи или удалении объекта выполняется блокировка по всем реквизитам, указанным в свойстве ПоляБлокировкиДанных (по значениям до выполнения операции и из текущего состояния объекта), а также по полю Ссылка.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Для объектов справочник, документ, план видов характеристик, план видов расчета, бизнес-процесс, задача, план счетов, план обмена управляемая блокировка могла быть установлена только по стандартному реквизиту Ссылка.Расширены возможности использования управляемых блокировок. В тех случаях, когда требуется выполнение согласованного действия над некоторым множеством объектов, определяемых значением реквизита, и при этом не допускается появление новых объектов с таким значением реквизита, появилась возможность устанавливать соответствующую блокировку, а не выполнять блокировку всего множества объектов данного типа.
Управляемые блокировки.
Использование объекта БлокировкаДанных, вне транзакции или в автоматическом режиме управления блокировками, приводит к возникновению исключения.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Использование объекта БлокировкаДанных вне транзакции или в автоматическом режиме управления блокировками не приводило к ошибке и не приводило к каким-либо блокировкам.Исключены неоднозначные ситуации, когда создавалось ощущение работающей системы, в то время как действий не выполнялось.
Установка клиентского приложения.
Средства администрирования.
Реализована возможность управлять автоматической установкой последней версии «1С:Предприятия». Для этого реализован ключ командной строки неинтерактивной программы запуска AppAutoInstallLastVersion, а также параметр AppAutoInstallLastVersion конфигурационных файлов 1CEStart.cfg и 1CESCmn.cfg.

При обнаружении несоответствия версии клиентского приложения и сервера «1С:Предприятия», или при указании для информационной базы полной версии «1С:Предприятия», установка новой версии выполняется всегда, если требуемая версия не установлена на компьютере пользователя.

В диалоге настройки окна выбора информационной базы реализован флажок Устанавливать автоматически новую версию.

Неинтерактивная программа запуска, как правило, начинала установку последней версии «1С:Предприятия». Не выполнять этой действие можно было:
  • Указав в списке версий диалога настройки программы запуска конкретную версию для использования со всеми информационными базами;
  • С помощью запуска клиентского приложения или интерактивной программы запуска конкретной версии.
При использовании неинтерактивной программы запуска реализована возможность отключать поиск и установку новой версии «1С:Предприятия» в тех случаях, когда требуемая для работы версия уже установлена на компьютер пользователя, но существуют более свежие, не установленные версии. При этом сохраняется возможность установить любую, необходимую версию системы.
Средства разработки.
При обновлении конфигурации базы данных выполняется проверка совпадения имен общих картинок с именами картинок из библиотеки картинок. При нахождении совпадений генерируется сообщение о неуникальности имени и обновление конфигурации базы данных не происходит.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При обновлении конфигурации базы данных не выполнялась проверка совпадения имен общих картинок с именами картинок из библиотеки картинок.Исключено поведение прикладного решения, когда в случае совпадения имен общих картинок и картинок из библиотеки картинок, в режиме «1С:Предприятие» отображались картинки из библиотеки картинок.
Управляемая форма.
Метод Закрыть(), вызванный для вспомогательной формы, приводит к закрытию этой формы. Если в момент закрытия данная форма является активной - произойдет активация основной формы, в противном случае никаких дополнительных действий выполнено не будет.

Метод Открыта(), вызванный для открытой вспомогательной формы, возвращает значение Истина. Если после открытия вспомогательной формы произошло переключение на другую вспомогательную или основную форму, метод Открыта() также вернет значение Истина.

Метод Закрыть(), вызванный для вспомогательной формы, приводил к возникновению ошибки. При этом закрытие формы не выполнялось.

Метод Открыта(), вызванный для открытой вспомогательной формы, возвращал значение Ложь.

Поведение системы стало более логичным и ожидаемым.
Работа с XML, XDTO.
При генерации модели данных конфигурации, для всех свойств модели данных конфигурации, имеющих в описании типов более одного типа, устанавливается свойство Возможно пустое (атрибут nillable схемы XSD) со значением Истина, в противном случае данное свойство не устанавливается.

Если в режиме Конфигуратора в качестве типа реквизита (ресурса, измерения и т.д.) был выбран тип Любая ссылка,то в модели данных конфигурации он будет преобразован:

  • в тип {http://v8.1c.ru/8.1/data/enterprise}AnyRef в случае наличия в конфигурации нескольких объектов метаданных, образующих тип Любая ссылка;
  • в тип, соответствующий ссылочному типу данных в том случае, если в конфигурации присутствует только один объект метаданных, образующий тип Любая ссылка.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При генерации модели данных конфигурации, для всех свойств модели данных конфигурации, имеющих в описании типов более одного типа, свойство Возможно пустое (атрибут nillable схемы XSD) не устанавливалось в любом случае.

Если в режиме Конфигуратора в качестве типа реквизита (ресурса, измерения и т.д.) был выбран тип Любая ссылка,то в модели данных конфигурации он всегда преобразовывался в тип {http://v8.1c.ru/8.1/data/enterprise}AnyRef.

Для типа Любая ссылка формирование модели данных в XML унифицировано с другими типами.
Полнотекстовый поиск.
Индексы полнотекстового поиска содержат номер версии, с помощью которой выполнялось создание индексов. В случае, если индекс полнотекстового поиска построен в версии 8.3.3 и выше и с отключенным режимом совместимости, то не будет выполняться поиск по представлениям объектов конфигурации в том случае, если с информационной базой работают с помощью версии 8.3.2 и более младшей.Индексы полнотекстового поиска не содержали номер версии, с помощью которой выполнялось построение индекса.Для индекса полнотекстового поиска реализован механизм, обеспечивающий возможность обратной совместимости (перехода на более младшую версию) при изменении формата индекса.
Web-сервисы.
Web-ссылки.
Для конструкторов объектов WSПрокси, WSОпределения и при вызове метода СоздатьWSПрокси() реализована возможность указания параметров proxy-сервера.

Прежний синтаксис конструкторов и метода поддерживается для совместимости.

При создании объектов WSПрокси, WSОпределения и при вызове метода СоздатьWSПрокси() не поддерживалась возможность указания параметров proxy-сервера. Настройки proxy-сервера были возможны только с помощью конфигурационного файла inetcfg.xml.Расширение возможности работы с Web-сервисами - появилась возможность указывать настройки proxy-севера в настройках конфигурации, а не с помощью служебного файла.
Функциональные опции.
При получении значения функциональной опции, для которой задан привилегированный режим при получении, не выполняется проверка прав доступа в том случае, если получение значения выполняется в безопасном режиме.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

При получении значения функциональной опции, для которой задан привилегированный режим при получении, выполнялась проверка прав доступа в том случае, если получение значения выполняется в безопасном режиме.Исключены проблемы, связанные с обращением к функциональным опциям в безопасном режиме. Считается, что информация, предоставляемая функциональной опцией с включенным привилегированным режимом, достаточно безопасна и может использоваться в безопасном режиме.
Автоматизированное тестирование.
Если во время выполнения теста, тестируемый объект не может выполнить какое-либо действие - генерируется исключение (кроме методов поиска объекта, где исключение не генерируется).Во время выполнения теста было невозможно определить, что тестируемый объект не может выполнить требуемое действие.Упрощена обработка ошибок, возникающих при выполнении тестирования.
Автоматизированное тестирование.
Методы, выполняющие какие-либо действия с тестируемыми объектами, не выполняют ожидание завершения действия. Методы, которые ранее возвращали результат выполнения действия - больше не возвращают результат, а в случае неудачного завершения - генерируют исключение.Методы, выполняющие какие-либо действия с тестируемыми объектами, ожидали завершения действия. В ряде случаев методы, выполняющие действия, возвращали результат своей работы в качестве кода возврата.Упрощена обработка ошибок, возникающих при выполнении тестирования.
Управляемая форма.
Для поля управляемой формы реализовано свойство КнопкаВыпадающегоСписка, которое управляет отображением у поля кнопки, открывающей выпадающий список. Этот список может содержать, в зависимости от типа реквизита, с которым связано поле ввода, следующую информацию:
  • Список выбора - из соответствующего свойства поля формы;
  • Список быстрого выбора - для соответствующих объектов конфигурации;
  • Значения выбора - значения, которые соответствуют тексту, введенному пользователем;
  • Историю выбора - для ссылочных полей и полей перечислений. История не ведется для полей, отображающих объекты конфигурации с установленным признаком быстрого выбора.

При вводе текста в поле ввода, система будет показывать уникальную информацию из всех указанных списков (в случае их наличия у поля ввода).

Для поля управляемой формы реализовано свойство ОтображениеКнопкиВыбора, которое управляет отображением кнопки открытия формы выбора.

Свойство поля управляемой формы КнопкаСпискаВыбора более не доступно и оставлено для совместимости. Событие поля ввода НачалоВыбораИзСписка более не вызывается.

В режиме совместимости с версией 8.3.2 поведение не изменилось.

Для поля управляемой формы было доступно свойство КнопкаСпискаВыбора. При начале выбора из списка формировалось событие НачалоВыбораИзСписка. Возможность открытия формы выбора из списка выбора не управлялась.Концепция списка выбора направлена на то, чтобы дать возможность пользователю быстро выбрать необходимое значение, по возможности не прибегая к форме выбора. Для этого список выбора содержит информацию, которая помогает в выборе значения для заполнения поля:
  • Историю выбора в поле данного типа (с данными параметрами);
  • Значения выбора;
  • Список быстрого выбора и т.д.
Веб-клиент.
При работе веб-клиента на iPad поддерживается только режим работы в закладках и без использования модальных окон, а также интерфейс Такси. Параметр командной строки webclientmode более не поддерживается. Реализована поддержка стандартных жестов увеличения и уменьшения масштаба.

Элементы формы, содержимое которых можно прокручивать, содержат полосы прокрутки.

При работе веб-клиента на iPad ограниченно поддерживалась работа с модальными окнами и не поддерживался режим работы в закладках. Поддерживался параметр командной строки запуска webclientmode. Не поддерживались стандартные жесты увеличения и уменьшения масштаба. В элементах формы не отображались полосы прокрутки.Теперь, для работы в iPad может использоваться конфигурация без специфических доработок и без ограничений (после перевода на режим, не использующий модальные окна). Ранее, необходимо было для работы в iPad исключать часть функциональности из-за ограниченной поддержки модальных вызовов.
Управляемая форма.
Командный интерфейс.
Доработана технология блокирующих окон. В рамках этой технологии меняется подход к модальности. Вместо модальных окон теперь используются блокирующие окна, а модальные окна поддерживаются для совместимости.

В прикладном решении все модальные окна рекомендуется заменить на блокирующие, а вместо методов платформы, использующих модальные окна, следует использовать новые методы, работающие без модальных окон.

Вызов модальной формы разбивается минимум на два вызова: отдельно выполняется открытие блокирующей формы (вместо модальной) и отдельно описывается процедура обратного вызова, которая будет вызвана платформой после завершения работы формы (в том числе для получения значения возврата).

Прикладное решение, которое должно работать на iPad - обязано поддерживать технологию блокирующих окон.

Реализовано свойство конфигурации РежимИспользованияМодальности, которое определяет, каким образом в прикладном решении используются модальные окна. При расширенной проверке конфигурации реализован режим поиска методов, связанных с модальностью. В командной строке эта проверка выполняется с помощью параметра -CheckUseModality ключа командной строки запуска ExtendedModulesCheck.

Реализован объект ОписаниеОповещения, предназначенный для передачи описания процедуры обратного вызова в методы платформы, открывающие блокирующие окна. Реализован метод глобального контекста ВыполнитьОбработкуОповещения().

Для системного перечисления РежимОткрытияОкнаФормы реализовано значение БлокироватьВесьИнтерфейс.

Для управляемой формы, команды командного интерфейса и общего модуля реализовано свойство ЭтотОбъект. Данное свойство не поддерживается в режиме совместимости с версией 8.3.2.

Изменен метод глобального контекста ОткрытьФорму().

Реализованы методы глобального контекста ПоказатьВопрос(), ПоказатьЗначение(), ПоказатьПредупреждение(), ПоказатьВводДаты(), ПоказатьВводЗначения(), ПоказатьВводСтроки(), ПоказатьВводЧисла(), НачатьУстановкуВнешнейКомпоненты(), НачатьУстановкуРасширенияРаботыСФайлами(), НачатьУстановкуРасширенияРаботыСКриптографией(), НачатьПомещениеФайла().

Для объектов ДиалогРедактированияСтандартногоПериода, КонструкторФорматнойСтроки, ДиалогВыбораШрифта, ДиалогВыбораЦвета, ДиалогРасписанияРегламентногоЗадания реализован метод Показать(). +Для объекта ОбработкаРасшифровкиКомпоновкиДанных реализован метод ПоказатьВыборДействия().

Для объекта СписокЗначений реализованы методы ПоказатьОтметкуЭлементов(), ПоказатьВыборЭлемента().

Для объекта УправляемаяФорма изменен метод Открыть() и реализованы методы ПоказатьВыборИзМеню(), ПоказатьВыборИзСписка().

Для объекта УправляемаяФорма реализовано свойство ОписаниеОповещенияОЗакрытии.

Свойство ЭтаФорма объекта УправляемаяФорма удалено и поддерживается для совместимости.

Значение системного перечисления ИспользованиеРежимаПроведения.Запрашивать поддерживается для управляемой формы только в режиме совместимости с версией 8.3.2.

В веб-клиенте, работающем на устройствах iPad, модальные окна поддерживались в ограниченном режиме. В прикладных решениях и системной части интерфейса активно использовались модальные окна.Веб-клиент стал лучше соответствовать современным веб-технологиям. Сняты ограничения на использование модальных окон при работе в веб-клиенте на устройствах iPad.

Требуется переработка конфигурации для обеспечения работы прикладного решения в веб-клиенте на устройствах iPad.

Технологический журнал.
Дискретность вывода времени событий в технологический журнал увеличена до 1 микросекунды. Количество микросекунд времени события технологического журнала выводится в шести позициях.

Реализовано свойство Durationus, которое содержит длительность события, выраженное в микросекундах. Отборы по свойствам Duration поддерживаются для совместимости.

Дискретность вывода времени событий в технологический журнал равнялась 100 микросекундам. Количество микросекунд времени события технологического журнала выводилось в четырех позициях.

В технологическом журнале существовало только свойство Duration, которое содержало длительность события, выраженного в сотнях микросекунд.

Уменьшена вероятность переполнения счетчика времени из-за того, что количество событий технологического журнала превышало 10 000 событий в секунду. Теперь в одной секунде может находится до 1 000 000 событий технологического журнала.

Свойство Durationus рекомендуется к использованию вместо свойства Duration.

Веб-клиент.
Системные требования.
Прекращена поддержка веб-браузеров:
  • Microsoft Internet Explorer версии 7.0;
  • Safari для ОС Windows;
  • Mozilla Firefox версии 16 и ниже (Windows, Linux).
Следующие веб-браузеры поддерживались системой:
  • Microsoft Internet Explorer версии 7.0;
  • Safari для ОС Windows;
  • Mozilla Firefox версии 16 и ниже (Windows, Linux).
Повышение стабильности веб-клиента, связанное с исключением поддержки веб-браузеров, имеющих ошибки и поведение, отличающееся от стандартного, а также низкую распространенность.
Работа в ОС Linux.
Реализована поддержка работы с объектом XBase при функционировании под управлением 64-разрядной ОС Linux.Не поддерживалась работа с объектом XBase при функционировании под управлением 64-разрядной ОС Linux.Появилась возможность работы с файлами .dbf на всех поддерживаемых архитектурах (кроме мобильной платформы).
Динамический список.
Поле ВерсияДанных убрано из состава доступных полей настроек динамического списка.Поле ВерсияДанных присутствовало в составе доступных настроек динамического списка.Исключено использование в динамическом списке поля, работа с которым не предполагалась и была реализована вследствии ошибки.
Права доступа.
Для того, чтобы управляемая форма отображала данные через точку, у пользователя должны быть права на все составляющие полного пути к данным. Если права отсутствуют - элемент, связанный с этими данными, не отображается на форме.В том случае, когда у пользователя были права не на все составляющие полного пути к данным (при обращении через точку), элемент, связанный с данными, отображался на форме, но не содержал данных.При доступе к данным через точку, элемент формы, связанный с такими данными, не будет отображаться на форме, если у пользователя отсутствуют права доступа на любую составляющую полного пути к отображаемым данным.
Средства администрирования.
Значения свойства RuleType объекта AssignmentRuleInfo интерфейса работы с сервером администрирования из языка Java приведены в соответствие значениям свойства RuleType объекта IAssignmentRule средств администрирования кластера серверов с помощью COM-соединения.Значения свойств RuleType различалось при работе через интерфейс работы с сервером администрирования из языка Java и при администрировании с помощью COM-соединения.Устранены незапланированные расхождения в различных механизмах администрирования кластера серверов.
Работа с Интернет.
Переработана реализация протокола сквозной аутентификации OpenID. Реализация соответствует режиму Direct Identity версии 2.0 протокола OpenID.

Изменен формат адреса OpenID-провайдера в файле default.vrd (атрибут url элемента rely): httрs://<адрес информационной базы OpenID-провайдера>/e1cib/oid2op. Время действия аутентификации по умолчанию равно 24 часам. Максимальное время действия аутентификации равно 168 часам.

Изменился протокол взаимодействия зависимой стороны и провайдера OpenID.

Реализована возможность запрета запоминания аутентификации в диалоге аутентификации.

Реализована форма ввода имени пользователя и пароля на стороне провайдера OpenID для использования в веб-клиенте.

Реализация протокола не полностью соответствовала режиму Direct Identity версии 2.0 протокола OpenID. Адрес OpenID-провайдера в файле default.vrd имел вид: httрs://<адрес информационной базы OpenID-провайдера>/e1cib/oida. Время действия аутентификации по умолчанию было равно 1 неделе. Максимальное время действия аутентификации не ограничивалось. Отсутствовала форма ввода имени пользователя и пароля на стороне провайдера OpenID для использования в веб-клиенте.Реализация протокола OpenID приведена в соответствие спецификации.
Внешние компоненты.
Веб-клиент.
В технологии внешних компонент реализована поддержка веб-браузера Mozilla Firefox версии 22.0 и выше. Адаптеры внешних компонент для веб-браузера Mozilla Firefox версии 22.0 будут работать с более новыми версиями веб-браузера без перекомпиляции. Для внешних компонент, которые должны работать во всех поддерживаемых версиях веб-браузера Mozilla Firefox, необходимо размещать в архиве несколько версий компоненты:
  • Для версий веб-браузера Mozilla Firefox до версии 18.0 включительно;
  • Для версий веб-браузера Mozilla Firefox с 19.0 по 21.0 включительно;
  • Для версии веб-браузера Mozilla Firefox версии 22.0 и выше.

В файле манифеста внешних компонент, работающих в веб-браузере Mozilla Firefox, рекомендуется указывать только минимальную версию веб-браузера.

Изменена документация по технологии создания внешних компонент (см. здесь), дополнены примеры, представлены новые версии адаптеров для веб-браузеров.

Удалены адаптеры для неподдерживаемых производителем версий веб-браузера Mozilla Firefox (версии 3.6, 4.0 и 5.0).

Технология внешних компонент не поддерживала работу с веб-браузером Mozilla Firefox версий 21.0 и выше.Технология внешних компонент стала поддерживать возможность работы с новыми версиями веб-браузера Mozilla Firefox (версии 22.0 и выше).
Управляемая форма.
Полнотекстовый поиск.
При формировании списка выбора при вводе по строке (для ссылочных объектов конфигурации) можно использовать следующие возможности:
  • Полнотекстовый поиск;
  • Поиск по вхождению подстроки или по началу строки;
  • Выполнение поиска непосредственно или в фоновом режиме.

Использование каждой из вышеперечисленных возможностей можно настроить с помощью конфигуратора, в свойствах объекта конфигурации.

Полнотекстовый поиск выполняется только по тому объекту конфигурации, для которого выполняется ввод по строке. Если при выполнении ввода по строке указан отбор, то этот отбор (при необходимости и возможности) конвертируется в запрос полнотекстового поиска с целью повышения скорости работы поиска.

Для таблиц внешнего источника данных допустимо выбирать только способ поиска строки и режим получения данных (непосредственно или фоновый).

В файловом режиме поиск в фоновом режиме выполняется только в том случае, если в этот момент не выполняется другое фоновое или регламентное задание.

Для обработчиков событий АвтоПодбор и ОкончаниеВводаТекста реализован формальный параметр Параметры. Данный параметр содержит настройки получения данных выбора и позволяет управлять этим процессом, изменяя соответствующие свойства структуры, передаваемой в этом параметре.

Объекты конфигурации не позволяли для ввода по строке настроить использование полнотекстового поиска, поиска по вхождению строки, а также выполнение поиска в фоновом режиме.

Можно было использовать полнотекстовый поиск и поиск по вхождению строки в обработчиках ОбработкаПолученияДанныхВыбора.

Появились новые стандартные возможности при вводе по строке в поле ввода:
  • Использовать полнотекстовый поиск.
  • Искать по вхождению строки, а не только по началу.
  • Выполнять поиск в фоне (пока пользователь вводит строку поиска).

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Переименовано имя типа менеджера перерасчетов регистра расчета.

Прежнее имя используется в режиме совместимости с версией 8.3.2.

РегистрРасчетаПерерасчеты.<Имя регистра расчета> +ПерерасчетыМенеджер.<Имя регистра расчета> +
Изменены английские имена для следующих объектов встроенного языка:
  • Запись таблицы внешнего источника данных (ВнешнийИсточникДанныхТаблицаЗапись);
  • Набор записей внешнего источника данных (ВнешнийИсточникДанныхНаборЗаписей).

В режиме совместимости с версией 8.3.2 поведение не изменилось.

  • ExternalDataSourceRecord;
  • ExternalDataSourceRecordSet.

  • ExternalDataSourceTableRecord;
  • ExternalDataSourceTableRecordSet.

Для менеджеров регистра накопления остатков и регистра бухгалтерии переименованы методы установки и получения рассчитанных итогов. Старые имена оставлены для совместимости.
  • ПолучитьПериодРассчитанныхИтогов();
  • УстановитьПериодРассчитанныхИтогов().
  • ПолучитьМаксимальныйПериодРассчитанныхИтогов();
  • УстановитьМаксимальныйПериодРассчитанныхИтогов().

+

+

Для объектов, описывающих тестируемые элементы формы, изменено имя свойства, содержащее заголовок элемента.Заголовок (Title)ТекстЗаголовка (TitleText)
Изменены имена элементов системного перечисления ОтображениеОбычнойГруппы. Старые имена используются для совместимости.
  • Линия (Line);
  • Отступ (Margin);
  • РамкаГруппы (GroupBox). +
  • СлабоеВыделение (WeakSeparation);
  • ОбычноеВыделение (NormalSeparation);
  • СильноеВыделение (StrongSeparation).
Переименованы методы получения и установки заголовка окна клиентского приложения. Старые имена оставлены для совместимости.
  • ПолучитьЗаголовокПриложения (GetApplicationCaption).
  • УстановитьЗаголовокПриложения (SetApplicationCaprion).
  • ПолучитьЗаголовокКлиентскогоПриложения (GetClientApplicationCaption),
  • УстановитьЗаголовокКлиентскогоПриложения (SetClientApplicationCaption).
Переименовано свойство конфигурации, хранящее командный интерфейс рабочего стола.КомандныйИнтерфейсРабочегоСтола (DesktopCommandInterface)КомандныйИнтерфейсОсновногоРаздела (MainSectionCommandInterface)
Переименовано свойство конфигурации, хранящее рабочую область рабочего стола (начальной страницы).РабочаяОбластьРабочегоСтола (DesktopWorkingArea)РабочаяОбластьНачальнойСтраницы (StartPageWorkingArea)
Переименованы настройки, предназначенные для сохранения параметров начальной страницы (рабочего стола).

В режиме совместимости с версией 8.3.2 используется старое имя. При смене режима совместимости выполняется соответствующее изменение ключей сохраненных настроек.

  • Общее/НастройкиРабочегоСтола,
  • РабочийСтол/ПанельНавигации/НастройкиКомандногоИнтерфейса,
  • РабочийСтол/ПанельДействий/НастройкиКомандногоИнтерфейса.
  • Общее/НастройкиНачальнойСтраницы,
  • ОсновнойРаздел/ПанельНавигации/НастройкиКомандногоИнтерфейса,
  • ОсновнойРаздел/ПанельДействий/НастройкиКомандногоИнтерфейса.
Переименован тип, описывающий объект хранения настроек начальной страницы (рабочего стола). Прежнее имя используется для совместимости.
  • НастройкиРабочегоСтола (DesktopSettings).
  • НастройкиНачальнойСтраницы (StartPageSettings).
Переименован русскоязычный вариант метода объекта ТестируемоеПолеФормы, вызывающего завершение редактирования текущей области.
  • ЗавершитьРедактированиеТекущейОбласти().
  • ЗакончитьРедактированиеТекущейОбласти().

Оглавление

Мобильная платформа

ФункциональностьКак сталоКак былоРезультат изменения
Системные требования.
Для устройств на базе операционной системы iOS прекращена поддержка версии 4.x. Минимальная версия iOS - 5.1.

Для устройств на базе операционной системы Android минимальный объем оперативной памяти составляет 256 МБайт.

Поддерживалась версия 4.x операционной системы iOS.

Для устройств на базе операционной системы Android было необходимо 100 МБайт оперативной памяти.

Уточнены системные требования для обеспечения эффективной работы мобильной платформы.
Управляемая форма.
Реализована возможность использования расширенной подсказки (кроме варианта Всплывающая) в мобильном приложении.Расширенная подсказка была недоступна в мобильном приложении.В мобильной платформе появилась возможность штатными средствами реализовывать подсказки к элементам формы с широкими оформительскими возможностями.
Общие объекты.
Реализована возможность работы с функциями геопозиционирования и мультимедийными возможностями мобильного устройства (фотография, аудио- и видеозаписи).

Для работы с функциями геопозиционирования реализованы объекты ДанныеМестоположения, ИнформацияПровайдераГеопозиционирования, СредстваГеопозиционирования, ДанныеАдреса. Для объекта ГеографическиеКоординаты реализовано свойство Высота. Реализовано свойство глобального контекст СредстваГеопозиционирования. Реализованы методы глобального контекста ПолучитьАдресПоМестоположению(), ПолучитьМестоположениеПоАдресу(), ПоказатьНаКарте(). Тип КоординатыГеографическойСхемы переименован в ГеографическиеКоординаты и используется в функциях геопозиционирования. Имя типа КоординатыГеографическойСхемы поддерживается для совместимости. Рекомендуется использовать имя типа ГеографическиеКоординаты.

Для работы с мультимедийными возможностями реализованы объекты ДанныеМультимедиа, СредстваМультимедиа. Реализовано свойство глобального контекста СредстваМультимедиа.

Данные возможности не предоставлялись.Стало доступно использование возможностей операционных систем мобильных устройств в части работы с механизмами геопозиционирования и мультимедиа. В частности, можно реализовать возможность определения текущего местоположения, выполнить снимок приходуемого товара и т.д.
Средства разработки.
Проверка конфигурации диагностирует несоответствие кода языка конфигурации стандарту ISO. При разработке мобильного приложения рекомендуется использовать коды языков, соответствующие ISO.Не проверялось соответствие кодов языков конфигурации стандартам ISO.Уменьшена вероятность некорректной установки языка мобильного приложения в зависимости от языка мобильного устройства.
Встроенный язык.
Реализована поддержка общих модулей с повторным использованием возвращаемых значений.Данная возможность не предоставлялась.В мобильной платформе реализована возможность оптимизации многократного получения некоторых данных в течении сеанса или вызова сервера.
Предопределенные данные.
При обновлении мобильного приложения объекты метаданных сопоставляются по внутренним идентификаторам.

При обновлении мобильного приложения на версию 8.3.3 будет выполнена соответствующая реструктуризация.

При обновлении мобильного приложения объекты метаданных сопоставлялись по именам.Стало возможно выполнять переименование объектов метаданных с сохранением информации в базе данных.
Отображение информации.
Все картинки мобильной платформы заменены на специальный формат, поддерживающий несколько разрешений экранов мобильных устройств.Картинки мобильной платформы были выполнены в одном разрешении.Системные картинки отображаются на экранах мобильных устройств в размерах, соответствующим разрешению экрана устройства.
Резервное копирование.
При создании информационной базы на устройствах под управлением iOS, папка с данными приложения помечается как не резервируемая. После того, как изменяются данные информационной базы (выполняется запись данных расширениями форм объектов и регистров), папка с данными приложения помечается как резервируемая и начинается ее резервное копирование с помощью системных средств.Папка с информационной базой, созданной на устройствах под управлением iOS, помечалась как резервируемая в момент создания.Поведение стало соответствовать требованиям компании Apple к резервному копированию пользовательских данных.
Табличный документ.
Исключены проблемы при отображении на мобильной платформе табличного документа с большим количеством строк и колонок.В некоторых случаях происходило аварийное завершение работы при отображении на мобильной платформе табличного документа с большим количеством строк и колонок.Повышена стабильность работы мобильной платформы при работе с большими табличными документами.
Работа с Интернет.
Для мобильной платформы реализовано поле HTML-документа. Поле HTML-документа обладает следующими особенностями:
  • Не поддерживаются свойства Документ и Вывод.
  • Событие ПриНажатии срабатывает только при попытке перехода на другую страницу. При этом все свойства параметра ДанныеСобытия, кроме Href, содержат значение Неопределено. Свойство Href содержит адрес, по которому выполняется попытка перехода.
Поле HTML-документа не поддерживалось для мобильной платформы.В мобильном приложении реализована возможность отображать HTML-страницы в формах, например, реализовать путеводитель по конфигурации.
Интерфейс.
Реализована возможность изменять порядок следования элементов в списке приложений на мобильном устройстве под управлением ОС Android.Порядок следования элементов в списке приложений было невозможно изменить на мобильном устройстве, работающем под управлением ОС Android.Повышено удобство работы со списком приложений. Пользователь может расположить приложения в нужном ему порядке.
Система компоновки данных.
Реализована возможность обработки расшифровки системы компоновки данных на мобильной платформе (открытие значения и удаленная обработка расшифровки). Для мобильной платформы реализован объект ИдентификаторРасшифровкиКомпоновкиДанных.На мобильной платформе было невозможно открыть отчет, содержащий расшифровку системы компоновки данных.Стало возможно формировать отчеты для мобильной платформы с помощью системы компоновки данных. Отчет с расшифровкой стал открываться на мобильной платформе.
Создание мобильного приложения.
Для обработки Помощник создания мобильного приложения реализована возможность указания ключа для работы с Google Maps.

Также в этой обработке реализована возможность указания логотипа с разрешением 950*1136 точек (экран телефона iPhone 5). +

Данные возможности не предоставлялись.С помощью Помощника создания мобильного приложения стало возможно создавать мобильные приложения, которые могут использовать новые возможности мобильной платформы (работа с геокодированием). Также улучшена поддержка устройств на базе iOS.
Работа с Интернет.
Для объектов HTTPСоединение, WSПрокси, WSОпределения, ИнтернетПочтовыйПрофиль и при вызове метода СоздатьWSПрокси() реализована возможность установки тайм-аута выполнения операции взаимодействия с сетевым ресурсом.

Имена пользователей и пароли, передаваемые объектам WSПрокси, WSОпределения и HTTPСоединение, могут содержать спец.символы URL, кроме символа «:».

Реализована возможность кодирования (метод КодироватьСтроку()) и раскодирования (метод РаскодироватьСтроку()) произвольных текстовых строк для использования в URL. Кодирование выполняется для соответствия стандарту RFC 1738 (http://www.ietf.org/rfc/rfc1738.txt).

Реализована возможность работы с заголовками HTTP-запросов, обработки кодов возврата, получения и установки тела запроса в виде строки или двоичных данных. Реализованы объекты HTTPЗапрос, HTTPОтвет.

Функциональность аналогична платформе для персонального компьютера.

+

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Устанавливать тайм-аут при взаимодействии с сетевыми ресурсами;
  • Указывать в именах пользователей или паролях не только символы ASCII;
  • Формировать URL (и получать значения из него) в соответствии со стандартом RFC 1738 (http://www.ietf.org/rfc/rfc1738.txt) в том случае, если в URL добавляется произвольный текст;
  • Программно формировать HTTP-запрос и обрабатывать ответ, взаимодействовать с REST-сервисами.
Встроенный язык.
Реализована возможность получения числа миллисекунд, прошедших с 1 января 0001 года, 0:00:00 UTC с помощью функции ТекущаяУниверсальнаяДатаВМиллисекундах().

Попытка присвоения значения элементу фиксированной структуры вызывает исключение.

Реализована сериализация описания индексов таблицы значений. Содержимое индексов не сериализуется, а восстанавливается при десериализации.

Доступна возможность вычисления значения хеш-функции по алгоритмам MD5 и CRC32 с помощью объекта ХешированиеДанных.

Функциональность аналогична платформе для персонального компьютера.

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Более точно измерять продолжительность интервала времени в системе, например, для получения времени выполнения какого-либо действия;
  • Использование фиксированной структуры аналогично другим фиксированным коллекциям;
  • Более полное восстановление состояния таблицы значений при десериализации;
  • Быстро определять неизменность большого объема данных или выполнять идентификацию данных из встроенного языка без привлечения сторонних средств.
Управляемая форма.
Реализована возможность указывать в качестве данных полей и таблиц управляемой формы данные, расположенные в конкретной строке реквизита формы, являющегося таблицей (кроме динамического списка).

Во время работы управляемой формы не выполняется считывание данных для тех динамических списков, которые не видны на форме в настоящий момент.

Для реквизитов типа Строка фиксированной длины изменено отображение автоотметки незаполненного, если этот реквизит расположен в таблице управляемой формы, табличном поле или табличном документе.

Реализованы стилевые шрифты МелкийШрифтТекста, КрупныйШрифтТекста, ОченьКрупныйШрифтТекста. Для типа Шрифт реализовано свойство Масштаб, определяющее увеличение или уменьшение шрифта относительно исходного размера.

Управление цветом фона для расширения группы формы вида обычная группа и расширения группы формы вида страница доступно с помощью свойства ЦветФона.

Реализован обработчик ОбработкаНавигационнойСсылки для поля формы Надпись, поля формы Декорация вида Надпись и управляемой формы, если в указанных элементах формы помещена форматированная строка, содержащая гиперссылку.

Расширены оформительские возможности для элемента формы поле (вида поле надписи) и декорация (вида надпись).

Реализовано изменение размера кнопок управляемой формы при установленном ограничении ширины обычной группы, аналогично другим элементам.

Функциональность аналогична платформе для персонального компьютера.

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Редактировать в отдельных полях формы данные, хранящиеся в конкретных строках табличных данных формы;
  • Быстро открывать формы, содержащие динамические списки на разных страницах управляемой формы;
  • Одинаковое поведения отметки незаполненного для различных реквизитов;
  • Указывать размер шрифтового оформления формы относительно базового шрифта формы, а не в абсолютных значениях;
  • Повысить наглядность форм и упростить работу с ними за счет цветового выделения групп;
  • Реализовать особую обработку для каждой гиперссылки, представленной в форматированной строке;
  • Более широко использовать оформительские возможности управляемой формы.

Унифицирован алгоритм изменения размеров элементов при установке ограничения размера обычной группы.

Прикладные объекты.
Реализованы пользовательские представления для объектов базы данных следующих типов: Справочник, Документ, ПланОбмена.

В журнале документов реквизит, хранящий номер документа, формируется фиксированной длины, если все документы, входящие в журнал, имеют поле номера типа Строка фиксированной длины. В противном случае поле журнала будет обладать переменной длиной.

Значение, полученное из незаполненного реквизита таблицы значений, дерева значений и табличной части, соответствует значению по умолчанию для типа реквизита колонки, с учетом квалификатора типа.

Функциональность аналогична платформе для персонального компьютера.

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Получать нестандартное представление данных в различных случаях;
  • Получать номера документов единообразно, вне зависимости от того, откуда получается значение номера документа: из самого документа или из журнала документов;
  • Формировать значение по умолчанию аналогично платформе для персонального компьютера.
Командный интерфейс.
В форме записи регистра сведений изменено поведение системы для случая, когда свойство ТолькоВоВсехДействиях команды Скопировать имеет значение Авто. Данное значение означает размещение команды только в меню Еще (Все действия).

Функциональность аналогична платформе для персонального компьютера.

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Одинаково размещать, по умолчанию, команду Скопировать в формах наборов записей регистров сведений и формах элементов.
Диаграммы.
Реализованы новые виды диаграмм: воронка, воронка объемная, воронка нормированная, воронка нормированная, объемная.

Реализован режим сглаживания диаграмм.

Реализована возможность соединения серий диаграмм.

Реализован режим прозрачности диаграмм.

Реализована поддержка свойства Индикатор для диаграммы изометрическая лента.

Функциональность аналогична платформе для персонального компьютера.

+

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно более широко и разнообразно использовать диаграммы.
Регистры сведений.
Для периодических регистров сведений реализованы итоги, которые используются для получения срезов первых/последних.

Функциональность аналогична платформе для персонального компьютера.

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Получать срезы первых/последних на самый первый и самый последний (текущий) моменты времени с большей скоростью.
Табличный документ.
Табличный документ не использует фиксацию, если область фиксации превышает отображаемую область.

Изменен алгоритм вычисления положения ячеек по горизонтали в разных строках.

Функциональность аналогична платформе для персонального компьютера.

+

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе стало возможно:
  • Повысить комфорт работы с отчетами, в которых используется фиксация областей слева и сверху;
  • Повысить комфортность использования табличного документа.
Работа с XML, XDTO.
Формируется ошибка вида Текст XML содержит недопустимый символ в позиции X в том случае, если текст сообщения пользователю содержит недопустимый символ XML.

Функциональность аналогична платформе для персонального компьютера.

+

Данная функциональность не поддерживалась на мобильной платформе.Поведение мобильной платформе унифицировано в части обработки использования недопустимых символов XML.
Отображение информации.
Доступны строки с форматированием (тип ФорматированнаяСтрока). Форматированные строки можно использовать в следующих случаях:
  • В качестве данных для элементов формы поле надписи;
  • В качестве заголовка поля формы типа декорация;
  • В качестве параметра ТекстПредупреждения метода Предупреждение();
  • В качестве параметра ТекстВопроса метода Вопрос().

+

Данная функциональность не поддерживалась на мобильной платформе.На мобильной платформе улучшены возможности отображения информации.
Работа с XML, XDTO.
Если при импорте схемы XSD будет обнаружено отсутствие определения в схеме целевого пространства имен, после выполнения попытки импорта будет выдано диагностическое сообщение.При импорте схемы XSD не формировалась диагностики в случае обнаружения проблем при загрузке.Улучшение диагностики при импорте схем XSD.
Управляемая форма.
Командный интерфейс.
Общие объекты.
Реализована возможность указания типа Произвольный для подчиненного реквизита у реквизита управляемой формы (например, колонка таблицы значений, дерева значений и т.д.).

Для управляемой формы реализовано свойство НавигационнаяСсылка, используемое для получения ссылки на основную форму объекта, а также свойство АвтоНавигационнаяСсылка.

Для методов ПолучитьФорму(), ОткрытьФорму() и ОткрытьФормуМодально(), реализован параметр НавигационнаяСсылка, значение которого будет присвоено одноименному свойству получаемой/открываемой формы.

Реализованы навигационные ссылки на списки. Для формы, основным реквизитом которой является динамический список с указанной основной таблицей, будет получена навигационная ссылка на список объекта, заданного в качестве основной таблицы. Переход по ссылке открывает основную форму списка.

Стало возможным использовать навигационные ссылки на команды глобального командного интерфейса. Изменен формат навигационной ссылки на точку навигации, образованную стандартной командой.

Изменения таблицы настроек хранения итогов для регистров накопления выполняются в рамках транзакции.

При передаче табличного документа между клиентом и сервером, сохраняются значения свойств ТолькоПросмотр и Защита.

Для метода глобального контекста ЧислоПрописью() реализован параметр форматирования ИИ (AU).

Реализованы объекты ЧтениеТекста и ЗаписьТекста.

Функциональность аналогична платформе для персонального компьютера.

Данная функциональность не поддерживалась на мобильной платформе.Обеспечена унификация использования некоторых механизмов с платформой для персонального компьютера.
Мобильное приложение.
Для мобильной платформы реализована поддержка языков интерфейса, поддерживаемых платформой для персонального компьютера. Реализован вариант мобильной платформы, поддерживающий только два языка интерфейса: русский и английский.

Изменен состав поставки мобильной платформы.

Мобильная платформа поддерживала только русский и английский языки интерфейса.Системная часть интерфейса мобильного приложения стала поддерживать большее количество языков.
Средства разработки.
В том случае, когда свойство конфигурации Назначения использования устанавливается только в значение Мобильное устройство, происходит автоматическое изменение других свойств конфигурации:
  • Свойство Режим использования модальности устанавливается в значение Использовать;
  • Свойство Режим совместимости интерфейса устанавливается в значение Версия 8.2.
Установка свойства конфигурации Назначения использования только в значение Мобильное устройство не приводило к изменениям других свойств конфигурации.Устранена возможность сохранения некоторых свойств конфигурации в состояниях, которые несовместимы с ограничениями, накладываемые разработкой прикладного решения только для мобильной платформы.

Оглавление

Переход с версии 8.2 на версию 8.3.3

Оглавление

Переход с предыдущей версии на версию 8.3.3

Оглавление

Версия 8.3.2

Версия 8.3.2 включает исправления обнаруженных ошибок и изменения в функциональности.

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.3.1.Использовался режим совместимости с версиями 8.1, 8.2.13 и 8.2.16.Возможность запуска конфигураций, разработанных в версии 8.3.1 и более младших, в версии 8.3.2, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.2 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.2, при необходимости, использовать для работы с информационной базой и версию 8.3.1. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости).
Средства разработки.
Для управляемого приложения реализован механизм автоматизированного тестирования конфигурации. Тестирование реализуется в виде кода на встроенном языке «1С:Предприятия» (с использованием соответствующих объектов встроенного языка), который имитирует последовательность интерактивных действий и выполняет проверку результата их выполнения.

Автоматизированное тестирование поддерживается для тонкого, толстого и веб-клиентов, в файловом и клиент-серверном вариантах информационной базы.

Для выполнения теста не требуется вносить изменений в тестируемую конфигурацию.

Реализована возможность записи интерактивных действий пользователя в управляемом приложении. Реализована возможность преобразования записанных действий в сценарий на встроенном языке «1С:Предприятия», воспроизводящий записанные действия. Обработка для выполнения такого преобразования размещена на диске ИТС (http://its.1c.ru/db/metod81#content:5014:1).

Данная возможность не предоставлялась.Повышение качества разработки прикладных решений за счет реализации автоматизированного тестирования интерфейса создаваемого прикладного решения.
Средства разработки.
Прикладные объекты.
Для сводной диаграммы реализована сериализация в XDTO. Макеты табличных документов, включающих сводные диаграммы, стало возможно выгружать в XML.Данная возможность не предоставлялась.Обеспечение выгрузки всех объектов конфигурации в файлы.
Мобильное приложение.
Реализована технология создания мобильных приложений. Поддерживается создание приложений для ОС iOS и Android. Приложения работают на мобильных устройствах автономно, без необходимости постоянного подключения к Интернет. Обмен с приложением через Интернет реализуется с помощью стандартных технологий «1С:Предприятия». Разработка выполняется в среде конфигуратора. При этом используется модель разработки управляемого приложения. Поддерживается подмножество функциональности, используемой для разработки приложений для персонального компьютера.

Созданное приложение может работать как на мобильных устройствах, так и на персональном компьютере.

В состав поставки демонстрационной конфигурации «Управляемое приложение» включена демонстрационная конфигурация мобильного приложения «1С:Заказы».

Данная возможность не предоставлялась.

Для разработки приложений для мобильных устройств можно было использовать расширение для карманных компьютеров (для ОС Microsoft Windows Mobile и Microsoft Windows CE).

Появилась возможность разрабатывать приложения для устройств на базе ОС iOS и Android с помощью инструментов платформы «1С:Предприятие» с возможностью реализовывать обмен между мобильными приложениями и прикладными решениями для персональных компьютеров.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Клиентское приложение.
Если выдается ошибка, которая приводит к завершению работы системы, то в окне информации для технической поддержки отображается текст этой ошибки.В некоторых случаях, ошибка, приводящая к завершению работы системы, не отображалась в окне информации для технической поддержки.Повышение удобства использования информации для технической поддержки.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Прикладные объекты.
Ускорено тестирование и исправление для журналов документов.При большом размере журнала документов, тестирование и исправление могло занимать существенное время.Уменьшено время работы операции тестирования и исправления для журналов документов.
Средства разработки.
Оптимизировано использование оперативной памяти при операциях сравнения конфигураций и обновления измененной конфигурации.Для больших конфигураций имелись проблемы при сравнении и объединении из-за большого расхода памяти.Стало возможным сравнивать и объединять конфигурации большего размера без дополнительных настроек компьютера.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Командный интерфейс.
В форме записи регистра сведений изменено поведение системы для случая, когда свойство ТолькоВоВсехДействиях команды Скопировать имеет значение Авто. Данное значение означает размещение команды только в меню Все действия.

В режиме совместимости с версией 8.3.1 поведение не изменилось.

Значение Авто свойства ТолькоВоВсехДействиях команды Скопировать означало, что команда отображалась непосредственно в командной панели и в меню Все действия.

Унифицировано поведение команды Скопировать формы записи регистра сведений с аналогичными формами других объектов.
Оконная система.
Для тонкого и толстого клиента изменено расположение по умолчанию окон оповещения, состояния и окна отображения вызовов сервера.

Окна оповещения и состояния по умолчанию отображаются в правом нижнем углу рабочей области экрана.

Окно отображения серверных вызовов по умолчанию отображается в левом нижнем углу рабочей области экрана.

В ОС Windows расположение окон по умолчанию зависело от положения панели задач. В ОС Linux расположение окон по умолчанию было не определено.Унификация расположения по умолчанию окон оповещения, состояния и окна отображения вызовов сервера в разных операционных системах. Ликвидация неопределенного поведения в ОС Linux.
Веб-клиент.
Для веб-браузера Google Chrome, инструкция по настройке веб-браузера, которую можно получить при включенной блокировке всплывающих окон, открывается в отдельной закладке.Инструкция по настройке веб-браузера открывалась в отдельном окне (а не закладке) веб-браузера.Повышение удобства настройки веб-браузера.
Прикладные объекты.
Значение, полученное из незаполненного реквизита таблицы значений, дерева значений и табличной части, соответствует значению по умолчанию для типа реквизита колонки, с учетом квалификатора типа.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Значение, полученное из незаполненного реквизита таблицы значений (дерева значений и табличной части), соответствовало значению по умолчанию для типа реквизита колонки, без учета квалификатора типа.Формирование значения по умолчанию приведено к единому виду, принятому в системе.
Клиентское приложение.
Работа с СУБД.
Системные требования.
Хранилище конфигурации.
Переработан механизм совместной работы с файлами информационной базы и файлами хранилища конфигурации. Обеспечена многопользовательская работа с информационной базой (или хранилищем конфигурации) пользователей, работающих как на ОС Windows, так и на ОС Linux. Для файлов 1Cv8.1CD, 1Cv8tmp.1CD, 1Cv8.1CL, 1Cv8tmp.1CL и некоторых других, при работе системы создаются служебные файлы, с добавлением к имени расширения .cfl, например, 1Cv8.1CD.cfl. Данные файлы имеют нулевой размер и не удаляются после завершения работы клиентских приложений.

Совместная работа с файловой информационной базой возможна только клиентскими приложениями одной версии.

Количество одновременных подключений к файловой информационной базе не может быть больше 1024.

Механизм многопользовательской работы с файловой версией информационной базы (и хранилищем конфигурации) не учитывал некоторые особенности файловой системы ОС Linux.Обеспечена возможность одновременной многопользовательской работы с информационной базой и хранилищем конфигурации пользователей, работающих как на ОС Windows, так и на ОС Linux. Устранены недостатки многопользовательской работы с файловым вариантом информационной базы и с хранилищем конфигурации в ОС Linux.
Отображение информации.
При создании форматированной строки средствами конфигуратора (диалог редактирования форматированной строки) доступно оформление строки с использованием элементов стиля (для шрифта и цвета). Форматированные строки хранят ссылки на элементы стиля, если они (элементы стиля) использовались при создании форматированной строки. Преобразование элементов стиля (разыменование) к реальным шрифтам и цветам происходит при отображении форматированной строки.В диалоге редактирования форматированной строки конфигуратора для оформления было недоступно использование элементов стиля.

При программном формировании форматированной строки с использованием элементов стиля, получившаяся форматированная строка содержала не ссылки на элементы стиля, а конкретные значения шрифтов и цветов.

Повышено удобство формирования форматированных строк. Стало возможным централизованно изменять оформление фрагментов текста, оформленных одним элементом стиля.
Работа с Интернет.
При использовании объекта ИнтернетПочта с почтовым сервером, для которого защищенное StartTLS соединение настроено на использование тех же портов, что и незащищенное, будет устанавливаться StartTLS соединение.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При использовании объекта ИнтернетПочта с почтовым сервером, для которого защищенное StartTLS соединение настроено на использование тех же портов, что и незащищенное, StartTLS соединение не устанавливалось.Возможность установки безопасного StartTLS соединения с почтовым сервером.
Табличный документ.
При использовании метода табличного документа Присоединить(), свойства ВместеСоСледующим, НачалоСтраницы, КонецСтраницы области ячеек табличного документа копируются только в том случае, если присоединение выполняется для области, которая расположена за правой границей результирующего табличного документа.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При использовании метода табличного документа Присоединить(), свойства области ячеек табличного документа копировались всегда.Обеспечение возможности работы с разрывами страниц при выводе в табличный документ при помощи метода Присоединить().
Кластер серверов.
При удалении кластера серверов или рабочего сервера с помощью консоли кластера, задается вопрос, требующий подтверждение удаления объекта.Удаление кластера серверов или рабочего сервера с помощью консоли кластера выполнялось безусловно.Снижение вероятности случайного удаления кластера серверов или рабочего сервера с помощью консоли кластера.
Средства администрирования.
Для метода CheckInfoBases интернет-сервиса WebCommonInfoBases добавлен параметр URL. С помощью этого параметра реализована возможность выполнить «переадресацию» запроса на получение списка общих информационных баз на другой интернет-сервис (с таким же описанием методов). Для этого интернет-сервиса могут использоваться другие настройки аутентификации.«Переадресация» интернет-сервиса была недоступна. Для всех вызовов веб-сервиса использовалась единая аутентификация.При получении списка информационных баз через интернет-сервисы доступна возможность реализовать несколько сервисов с различными требованиями к аутентификации. Это позволяет, например, выполнять проверку изменения списка баз без аутентификации, а получение измененного списка с аутентификацией.
Прикладные объекты.
Регистры сведений.
Исключено неявное чтение ресурсов, реквизитов и общих реквизитов (не являющихся разделителями) при записи наборов записей регистров сведений.

При записи набора записей регистра сведений больше не требуется прав на чтение ресурсов, реквизитов и общих реквизитов регистра (не являющихся разделителями). +

При записи набора записей регистра сведений требовались права на чтение ресурсов, реквизитов и общих реквизитов регистра (не являющихся разделителями). +Устранены нежелательные срабатывания ограничений доступа к данным на чтение при выполнении операции записи набора записей регистра сведений.

+

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Отображение информации.
Формируется ошибка вида Текст XML содержит недопустимый символ в позиции X в том случае, если текст сообщения пользователю содержит недопустимый символ XML (в случае тонкого и толстого клиентов).

В режиме совместимости с версией 8.3.1 поведение не изменилось.

Текст сообщения пользователю, содержащий недопустимые символы XML, не отображался тонким и толстым клиентом.Унифицировано поведение системы в части обработки использования недопустимых символов XML.
Прикладные объекты.
Явное указание свойства Кодировка объекта ИнтернетПочтовоеВложение учитывается при формировании отправляемого письма: для вложения явно указывается установленная кодировка.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Свойство Кодировка объекта ИнтернетПочтовоеВложение игнорировалось при формировании отправляемого письма.Установка кодировки вложения позволяет принимающему почтовому клиенту корректно отобразить содержимое и имя вложения в случае, когда для почтового вложения задана кодировка, отличная от кодировки письма.
Табличный документ.
Изменен алгоритм вычисления положения ячеек по горизонтали в разных строках. Если сумма ширин колонок из различных строк совпадает, то колонки будут занимать одинаковое пространство и внешние границы таких колонок будут совпадать.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Если сумма ширин колонок из различных строк совпадает, колонки могли занимать разное пространство и внешние границы колонок могли не совпадать.Повышение удобства использования табличного документа.

Оглавление

Переход с предыдущей версии на версию 8.3.2

Оглавление

Версия 8.3.1

Версия 8.3.1 не включает изменения, выполненные в версии 8.2.17. +

Версия 8.3.1 включает исправления обнаруженных ошибок и изменения в функциональности.

Изменено представление списка изменений:

Новые возможности и изменения

ФункциональностьКак сталоКак былоРезультат изменения
Свойства конфигурации.
Для свойства конфигурации Режим совместимости реализовано значение Версия 8.2.16.Использовался режим совместимости с версиями 8.1 и 8.2.13.Возможность запуска конфигураций, разработанных в версии 8.2.16 и более младших, в версии 8.3.1, без внесения изменений в конфигурацию и без изменений структур данных. Это позволяет при переходе на версию 8.3.1 сначала выполнить переход без внесения изменений в конфигурацию, а потом, внести необходимые изменения и снять режим совместимости. Так же это позволяет иметь возможность после перехода на версию 8.3.1, при необходимости, использовать для работы с информационной базой и версию 8.2.16. Это можно делать, как до снятия режима совместимости, так и после (установив вновь режим совместимости).
Конфигуратор.
Кроссплатформенность.
Доступно клиентское приложение, работающее под ОС Linux. Поддерживается:
  • Работа тонкого клиента, толстого клиента и конфигуратора.
  • Файловый и клиент-серверный режим работы.
  • Соединение тонкого клиента с информационной базой через веб-сервер.

Ограничения клиентского приложения, работающего под ОС Linux, приведены в документации.

Возможность одновременной установки и запуска различных версий «1С:Предприятия» не поддерживаются.

В меню приложений среды рабочего стола ОС Linux добавлены ярлыки запуска неинтерактивной программы запуска, тонкого клиента и толстого клиента. Ярлыки относятся к подкатегории Finance категории Office.

Под ОС Linux была доступна работа с информационной базой с помощью веб-клиента. Под ОС Linux также был доступен сервер.Возможность разработки прикладных решений и работы клиентских приложений в ОС Linux.

+

Работа тонкого клиента через Интернет.
Работа тонкого клиента по протоколу https стала возможной с использованием клиентских сертификатов (из файла, из хранилища сертификатов Windows и из хранилища сертификатов NSS). Для задания параметров сертификатов служат ключи командной строки запуска HttpsCert, HttpsCA и HttpsNSS.

Работа с хранилищем сертификатов Windows и ключи командной строки запуска HttpsCert, HttpsCA не поддерживаются клиентскими приложениями, работающими под ОС Linux.

Не поддерживалась работа тонкого клиента по протоколу https с использованием клиентских сертификатов.Возможность работы с помощью тонкого клиента с информационными базами, опубликованными на ресурсах, доступ к которым требует использования клиентских сертификатов.
Web-ссылки.
Работа с Web-сервисами по протоколу https стала возможной с использованием клиентских сертификатов (из файла, из хранилища сертификатов Windows и из хранилища сертификатов NSS).Возможность работы Web-сервисов по протоколу https с использованием клиентских сертификатов не поддерживалась.Возможность работы с Web-сервисами в случаях, когда серверная сторона требует наличия клиентского сертификата для использования протокола https.
Работа с Интернет.
Работа http- и ftp-соединений по протоколу https стала возможной с использованием клиентских сертификатов (из файла, из хранилища сертификатов Windows и из хранилища сертификатов NSS).Возможность работы http- и ftp-соединений по протоколу https с использованием клиентских сертификатов не поддерживалась.Возможность работы http- и ftp-соединений в случаях, когда серверная сторона требует наличия клиентского сертификата для использования протокола https.
Встроенный язык.
Доступна возможность вычисления значения хеш-функции по алгоритмам MD5 и CRC32 с помощью объекта ХешированиеДанных.Для вычисления хеш-функции было необходимо прибегать к сторонним средствам (внешние компоненты и т.д.).Быстрое определение неизменности большого объема данных или идентификации данных из встроенного языка без привлечения сторонних средств.
Внешние источники данных.
Общие реквизиты / Разделение данных.
Внешний источник данных может входить в состав общего реквизита. Для таких внешних источников данных параметры соединения хранятся в разрезе значений разделителей. Если в сеансе не используется данный разделитель - это считается отдельным значением для хранения параметров соединений. Сами данные, расположенные в таблицах внешних источников данных, не разделяются по значениям разделителей.Внешние источники данных не могли входить в состав общего реквизита.Возможность задания параметров соединения для каждой области данных в информационной базе. Таким образом, для разных областей данных реализуется возможность доступа или к разным базам данных с одинаковой структурой или доступ к одной базе данных с разными параметрами соединения.
Управляемая форма.
Реализована возможность указывать в качестве данных полей и таблиц управляемой формы данные, расположенные в конкретной строке реквизита формы, являющегося таблицей (кроме динамического списка).Данная возможность не предоставлялась.Появилась возможность реализовывать такие интерфейсные решения, как отображение настроек отчетов в виде отдельных полей формы.
Внешние источники данных.
При работе с внешними источниками данных доступна аутентификация ОС. Реализовано право доступа ИзменениеАутентификацииОССеанса, регулирующее возможность изменять настройку аутентификации ОС в настройках пользователя и параметрах текущего сеанса.Данная возможность не предоставлялась.Возможность выполнять подключение к внешним источникам данных в том случае, если доступ к этим источникам возможен только с помощью аутентификации ОС.
Прикладные объекты.
Отображение информации.
Пользовательские представления для объектов базы данных следующих типов: Справочник, Документ, ПланСчетов, ПланВидовРасчета, ПланВидовХарактеристик, БизнесПроцесс, Задача, ПланОбмена, Таблица. Для модулей менеджеров объектов вышеуказанных типов реализованы обработчики событий ОбработкаПолученияПолейПредставления и ОбработкаПолученияПредставления.

В режиме совместимости с версией 8.2.16 данная возможность не предоставляется.

Представление объектов базы данных было невозможно изменить из встроенного языка.Возможность получения нестандартного представления. Возможность получения представления для таблиц внешних источников данных в тех случаях, когда не указано поле, обеспечивающее представление. Возможность получения представления объекта, включающего в себя локализованные данные.
Внешние источники данных.
Встроенный язык.
Доступен поиск ссылок на объекты таблиц внешних источников данных с помощью метода глобального контекста НайтиПоСсылкам() и с помощью стандартной функции Поиск ссылок на объекты. Поиск выполняется как в таблицах информационной базы, так и таблицах внешних источников данных.Ссылки на объекты таблиц внешних источников данных было невозможно найти с помощью метода НайтиПоСсылкам() и с помощью стандартной функции Поиск ссылок на объекты.Возможность поиска ссылок на объекты таблиц внешних источников данных.
Внешние источники данных.
Для объекта ВнешнийИсточникДанныхТаблицыМенеджер реализован метод ТипВсеСсылки().Такая возможность не предоставлялась.Реализация отсутствующих возможностей при работе с внешними источниками данных.
Внешние источники данных.
Для метода глобального контекста ОткрытьЗначение() реализована возможность открывать значения типа РегистрСведенийКлючЗаписи и ВнешнийИсточникДанныхТаблицаКлючЗаписи.Было невозможно открыть значения типа РегистрСведенийКлючЗаписи и ВнешнийИсточникДанныхТаблицаКлючЗаписи с помощью метода ОткрытьЗначение().Реализация отсутствующих возможностей при работе с регистрами сведений и внешними источниками данных.
Обновление конфигурации базы данных.
Кластер серверов.
Реализовано фоновое обновление конфигурации базы данных.

Поддерживается только в клиент-серверном варианте. Доступно при изменении структур данных. Выполняется без длительного монопольного доступа к информационной базе. Монопольный режим требуется на финальном этапе фонового обновления на небольшой период времени.

В кластере серверов реализован сервис обновления конфигурации базы данных.

Реализовано системное фоновое задание, использующееся для фонового обновления конфигурации базы данных.

Реализован метод глобального контекста ПолучитьОбновлениеКонфигурацииБазыДанных(), реализован объект ОбновлениеКонфигурацииБазыДанных.

Для параметра /UpdateDBCfg командной строки режима пакетного запуска конфигуратора реализованы ключи -Dynamic, -BackgroundStart, -BackgroundCancel, -BackgroundFinish, -BackgroundSuspend, -BackgroundResume.

Реализованы события журнала регистрации: _$InfoBase$_.DBConfigBackgroundUpdateStart, _$InfoBase$_.DBConfigBackgroundUpdateFinish, _$InfoBase$_.DBConfigBackgroundUpdateCancel, _$InfoBase$_.DBConfigBackgroundUpdateSuspend, _$InfoBase$_.DBConfigBackgroundUpdateResume.

Обновление конфигурации базы данных, связанное с изменением структуры данных, было возможно только в монопольном режиме.Реализована возможность обновления информационной базы с существенными изменениями структуры данных без длительной остановки работы пользователей.

При выполнении обновления конфигурации информационной базы с помощью пакетного запуска конфигуратора стало доступно управление возможностью проведения динамического обновления (как при фоновом, так и при обычном обновлении).

Встроенный язык.
Работа с файлами.
Веб-клиент.
Метод КаталогВременныхФайлов() реализован для веб-клиента. Метод доступен при подключении расширения работы с файлами.

Реализован метод РабочийКаталогДанныхПользователя(), предоставляющий доступ к каталогу пользователя информационной базы, создаваемому системой. Метод доступен для тонкого, толстого и веб-клиентов. В веб-клиенте метод доступен при подключении расширения работы с файлами.

Реализован метод КаталогДокументов(), предоставляющий доступ к стандартному каталогу документов операционной системы. Метод доступен для тонкого, толстого и веб-клиентов. В веб-клиенте метод доступен при подключении расширения работы с файлами.

Доступ к стандартным каталогам (рабочий каталог данных пользователя и каталог документов) штатными средствами был невозможен. В тонком и толстом клиентах имелась возможность реализации такого доступа с помощью внешних, по отношения к системе, средств, что снижало переносимость системы между различными операционными системами и видами клиентских приложений.Возможность доступа к некоторым стандартным каталогам на клиентском компьютере, которая позволит хранить файловые данные пользователя в местах, которые специально для этого предназначены, без использования внешних инструментов.
Отображение информации.
Доступны строки с форматированием (тип ФорматированнаяСтрока). Форматированные строки можно использовать в следующих случаях:
  • В качестве данных для элементов формы поле надписи
  • В качестве заголовка поля формы типа декорация;
  • В качестве параметра ТекстПредупреждения метода Предупреждение();
  • В качестве параметра ТекстВопроса метода Вопрос().
Вывод текста с различным форматированием был возможен только при использовании документа в формате HTML и форматированного документа.Улучшение презентационных возможностей и улучшение юзабилити.
Встроенный язык.
Управляемая форма.
Реализован обработчик ОбработкаНавигационнойСсылки для поля формы Надпись, поля формы Декорация вида Надпись и управляемой формы. Обработчик вызывается в том случае, если в указанных элементах формы помещена форматированная строка, содержащая гиперссылку, если свойство Гиперссылка у элемента формы установлено в значение Ложь.Существовала возможность реализовать представление в виде гиперссылки всего элемента формы, без возможности размещения в одном поле нескольких гиперссылок.Возможность реализации особой обработки для каждой гиперссылки, представленной в форматированной строке.
Командный интерфейс.
Стало возможным использовать навигационные ссылки на команды глобального командного интерфейса. Переход по ссылке выполняет команду.

Для метода глобального контекста ПерейтиПоНавигационнойСсылке() реализована поддержка навигационных ссылок на команды.

Данная возможность не предоставлялась.Возможность перехода по ссылке к выполнению команды, а также возможность использовать эту возможность во встроенном языке.
Управляемая форма.
Для управляемой формы реализовано свойство НавигационнаяСсылка, используемое для получения ссылки на основную форму объекта.

Для управляемой формы реализовано свойство АвтоНавигационнаяСсылка. Метод ПолучитьНавигационнуюСсылку() объекта ОкноКлиентскогоПриложения возвращает значение свойства НавигационнаяСсылка (если свойство АвтоНавигационнаяСсылка установлено в значение Ложь) или стандартную ссылку основной формы.

Данная возможность не предоставлялась.Реализована возможность управления тем, каким будет значение навигационной ссылки, полученной у окна клиентского приложения.

Встроенный язык.
Общие реквизиты / Разделение данных.
Прикладные объекты.
В состав общих реквизитов, не являющихся разделителями, могут входить журналы документов. Для сохранения совместимости в информационных базах, созданных в «1С:Предприятии» версии 8.2, значение свойства Использование элемента состава общего реквизита для журналов документов устанавливается в значение Не использовать.Отсутствовала возможность отображать общие реквизиты в журналах документов.Доступна возможность отображения общих реквизитов в журналах документов.
Отображение информации.
Управляемая форма.
Реализованы стилевые шрифты МелкийШрифтТекста, КрупныйШрифтТекста, ОченьКрупныйШрифтТекста.

Для типа Шрифт реализовано свойство Масштаб, определяющее увеличение или уменьшение шрифта относительно исходного размера.

Для указания размера шрифта в управляемой форме имелась возможность указания только непосредственного размера шрифта.Возможность указания размера шрифтового оформления формы относительно базового шрифта формы, а не в абсолютных значениях.
Кластер серверов.
Встроенный язык.
Реализовано свойство SafeCallMemoryLimit для объекта IWorkingProcessInfo. Определяет количество памяти (в байтах), которое может использовать приложение во время одного серверного вызова.

Реализовано свойство SafeWorkingProcessesMemoryLimit для объекта IWorkingServerInfo. Определяет максимальный объем памяти (в байтах), который доступен всем рабочим процессам на данном рабочем сервере.

Отсутствовала возможность ограничить использование памяти. Это приводило к проблемам, например, при настройке пользователями отчетов, выбирающих большой объем данных.Повышена стабильность сервера. Реализована возможность не допускать аварийного завершения работы всего кластера серверов из-за большого потребления памяти конкретным сеансом. Вместо этого будет аварийно завершаться клиентское приложение, вызвавшее такой расход памяти.
Кластер серверов.
Встроенный язык.
Реализовано отслеживание переполнения стека при исполнении встроенного языка рабочим процессом кластера серверов в клиент-серверном варианте использования информационной базы.Бесконечная рекурсия приводила к аварийному завершению рабочего процесса кластера серверов.Повышена стабильность работы кластера серверов.
Кластер серверов.
Встроенный язык.
Для объектов ISessionInfo, IInfoBaseConnectionInfo реализованы свойства:
  • MemoryCurrent - объем памяти в байтах, занятый с начала выполнения текущего вызова;
  • MemoryLast5Min - объем памяти в байтах, занятый в процессе вызовов за последние 5 минут;
  • MemoryAll - объем памяти в байтах, занятый в процессе вызовов с момента начала сеанса;
  • InBytesCurrent - количество данных в байтах, прочитанных с диска с начала выполнения текущего вызова;
  • InBytesLast5Min - количество данных в байтах, прочитанных с диска данным сеансом за последние 5 минут;
  • InBytesAll - количество данных в байтах, прочитанных с диска данным сеансом с момента начала сеанса;
  • OutBytesCurrent - количество данных в байтах, записанных на диск с начала выполнения текущего вызова;
  • OutBytesLast5Min - количество данных в байтах, записанных на диск данным сеансом за последние 5 минут;
  • OutBytesAll - количество данных в байтах, записанных на диск данным сеансом с момента начала сеанса.

Аналогичные свойства реализованы в консоли кластера для списка сеансов, списка соединений и диалога свойств соединения.

Данная возможность не предоставлялась.Средства мониторинга кластера серверов облегчают определение элементов прикладного решения, приводящих к неоправданному расходу оперативной и дисковой памяти.
Технологический журнал.
Кластер серверов.
Расширен состав свойств для события технологического журнала <call> в том случае, если событие генерируется для процесса rphost (свойство process равно rphost), а также в том случае, если процесс rphost выполняет обращение к виртуальным ресурсам системы.

Добавлены свойства, отображающие:

  • Report - имя объекта метаданных выполняемого отчета;
  • Method - имя вызванного метода;
  • SessionID - номер сеанса;
  • Memory - объем памяти в байтах, занятой, но не освобожденной за вызов;
  • MemoryPeak - объем памяти в байтах, занятой, но не освобожденной за вызов. Пиковое значение;
  • InBytes - количество прочитанных за вызов данных с диска, в байтах;
  • OutBytes - количество записанных за вызов данных с диска, в байтах;
  • Context - контекст события.
Указанные свойства отсутствовали при генерации события <call>.Средства технологического журнала облегчают определение элементов прикладного решения, приводящих к неоправданному расходу оперативной и дисковой памяти.
Общие реквизиты / Разделение данных.
Встроенный язык.
Стало возможным удаление данных области данных или всей информационной базы. Удаляются следующие данные:
  • Данные прикладных объектов;
  • Данные хранилищ настроек;
  • Истории;
  • Списка пользователей;
  • Настройки часового пояса.

Для удаления требуется право Администрирование. Удаление возможно:

  • с помощью ключа командной строки /EraseData режима пакетного запуска Конфигуратора.
  • с помощью метода глобального контекста УдалитьДанныеИнформационнойБазы().

Реализовано событие журнала регистрации _$InfoBase$_.EraseData.

Отсутствовала возможность удалить предопределенные данные области.Возможность удаления областей данных, которые стали не востребованы, например, абонент перестал пользоваться системой.
Кластер серверов.
Программное лицензирование.
Для кластера серверов реализован сервис лицензирования. Изменен алгоритм поиска лицензий.Данная возможность не предоставлялась.Появляется возможность привязывать программную лицензию к специальному компьютеру, на котором работает только сервис лицензирования и параметры которого не изменяются.
Средства разработки.
Реализована выгрузка конфигурации в файлы и загрузка конфигурации из файлов.

Выгрузка большинства объектов выполняется в формате XML, модули выгружаются в текстовых файлах, файлы картинок выгружаются в своем формате, справочная информация выгружается в файлах .html, конфигурации поставщика выгружаются в виде файлов конфигураций (.cf), обычные формы и интерфейсы выгружаются в двоичном виде.

Реализованы команды Выгрузить конфигурацию в файлы и Загрузить конфигурацию из файлов в меню Конфигурация. Команды Выгрузить файлы конфигурации и Загрузить файлы конфигурации убраны из меню Конфигурация, вернуть их можно с помощью диалога настройки главного меню.

Реализованы ключи командной строки DumpConfigToFiles и LoadConfigFromFiles.

Поддерживалась выгрузка и загрузка ограниченного набора данных: модули, справочная информация, макеты, права и картинки. Остальная информация о конфигурации не выгружалась.

Для выгрузки и загрузки использовались команды Выгрузить файлы конфигурации и Загрузить файлы конфигурации меню Конфигурация.

Возможность анализировать и модифицировать конфигурацию внешними (по отношению к «1С:Предприятию») средствами.
Отображение информации.
Управляемая форма.
Управление цветом фона для расширения группы формы вида обычная группа и расширения группы формы вида страница доступно с помощью свойства ЦветФона.

Если у группы указан цвет фона, отличный от значения Авто и отображение группы имеет значение Рамка группы, то рамка группы (вместе с заголовком) отображается установленным цветом фона.

Не предоставлялась возможность управлять цветом фона расширений групп формы.Возможность цветового выделения групп повышает наглядность форм и упрощает работу с ними.
Общие реквизиты / Разделение данных.
Программное управление безопасным режимом разделения данных для разделителя доступно из встроенного языка, с помощью методов глобального контекста УстановитьБезопасныйРежимРазделенияДанных() и БезопасныйРежимРазделенияДанных().

Возможность является аналогом атрибута safe элемента zone файла default.vrd.

Возможность включения безопасного режима разделения данных была доступна только с помощью файла default.vrd и только в случае подключения к информационной базе через веб-сервер (по протоколу http).Позволяет обеспечить безопасное выполнение фрагментов кода, которые вызываются из сеансов с неиспользуемыми значениями разделителей, но которые должны работать в конкретных областях данных и не иметь возможности «сменить» область данных (например, по ошибке).
Журнал регистрации.
Аутентификация OpenID.
В случае успешной или неуспешной аутентификации OpenID, в журнале регистрации формируются события Сеанс. Аутентификация и Сеанс. Ошибка аутентификации соответственно.События аутентификации, связанные с аутентификацией OpenID, не записывались в журнал регистрации.Реализована возможность получения информации об аутентифкации средствами OpenID.
Журнал регистрации.
Аутентификация OpenID.
Для информационной базы, являющейся провайдером OpenID реализовано событие Провайдер OpenID. Подтверждено, формирующееся в случае положительного ответа на запрос аутентификации. В случае отрицательного ответа на запрос аутентификации, реализовано формирование события Провайдер OpenID. Отклонено в журнале регистрации информационной базы, выступающей в качестве провайдера OpenID.Данная возможность не предоставлялась.Облегчение администрирования провайдера OpenID.
Средства разработки.
Реализована возможность просмотра значений свойств элементов формы Шрифт, ШрифтЗаголовка, ШрифтПодвала и СписокВыбора в отдельном окне, в тех случаях, когда запрещено редактирование этих свойств.Просмотр свойств был недоступен, если объект не захвачен в хранилище или находится на поддержке.Если элемент не захвачен в хранилище конфигурации или находится на поддержке, стало возможным просматривать характеристики шрифтового оформления и список выбора, не включая возможность изменения и не захватывая объект в хранилище.
Кластер серверов.
При начале и завершении сеанса работы с информационной базой, требующего клиентской лицензии, платформа может информировать внешнее приложение вызовами методов веб-сервиса. Внешнее приложение, получив вызов при начале сеанса, может разрешить или запретить начало сеанса. Данная возможность доступна только в клиент-серверном варианте информационной базы.

Для указания параметров Web-сервиса внешнего управления сеансами реализовано:

  • свойство Внешнее управление сеансами информационной базы в консоли кластера;
  • свойство ExternalSessionManagerConnectionString объекта IInfoBaseInfo.

Поведение системы при недоступности Web-сервиса внешнего управления сеансами определяется с помощью:

  • свойства Обязательное использование внешнего управления сеансами информационной базы в консоли кластера;
  • свойства ExternalSessionManagerRequired объекта IInfoBaseInfo.

Для сервера реализован сервис внешнего управления сеансами.

Параметры вызываемых Web-сервисов приведены в документации.

Ограничить количество одновременных сеансов для прикладного решения было возможно только путем модификации прикладного решения, без возможности централизованного управления механизмом.Возможность централизованно управлять количеством одновременно используемых лицензий для различных прикладных решений, без модификации самих прикладных решений.
Веб-клиент.
Внешние компоненты.
Стало возможным использование внешних компонент для веб-браузеров Google Chrome и Safari (для ОС Windows и MacOS X). Для системного перечисления ТипПлатформы реализовано значение MacOS.

Расширение работы с файлами доступно для этих веб-браузеров на ОС Windows и MacOS X.

Расширение работы с криптографией доступно для этих веб-браузеров только на ОС Windows.

Внешние компоненты, расширение работы с файлами и расширение работы с криптографией не поддерживались для веб-браузеров Google Chrome и Safari.На веб-браузерах Google Chrome и Safari стали доступны расширения работы с файлами и криптографией (только для ОС Windows).

Создание внешних компонент стало возможным для всех поддерживаемых веб-браузеров.

Картинки.
Доступна обработка картинок во встроенном языке с помощью объекта ОбработкаКартинок:
  • Выделение значимой части;
  • Поворот картинки.
Данная возможность не предоставлялась.Позволяет выполнять обработку картинок. Например, перед размещением картинки в табличном документе:
  • Выделить из фотографии печать;
  • Повернуть картинку на определенный угол для выравнивания подписи, находящейся в картинке.
Диаграммы.
Для реквизитов управляемых форм типа Диаграмма, ДиаграммаГанта, Дендрограмма, ТабличныйДокумент, ГрафическаяСхема и ГеографическаяСхема реализована возможность интерактивной настройки в редакторе управляемой формы. Диалог настройки вызывается из панели свойств реквизита.Объекты Диаграмма, ДиаграммаГанта, Дендрограмма, ТабличныйДокумент, ГрафическаяСхема и ГеографическаяСхема было возможно настраивать или средствами встроенного языка, или путем размещения настроенного объекта в макете и помещения объекта из макета в элемент формы при создании формы.Повышение удобства разработки.
Отображение информации.
Для метода глобального контекста ЧислоПрописью() реализован параметр форматирования ИИ (AU). Параметр используется только для англоязычной локализации (en, en_XX) и определяет классическую или упрощенную пропись числа.

При классическом формировании числа прописью на английском языке между сотнями (или тысячами и миллионами) и следующими за ними десятками (или единицами, если нет десятков) в любом разряде всегда ставится союз and. Например, 150 – «one hundred and fifty», но 100 – «one hundred» и 50 – «fifty». При упрощенной прописи союз and не используется.

При формировании числа прописью (для англоязычных локализаций) использовалась только упрощенная форма.Корректное формирование числа прописью в европейских странах.
План видов характеристик.
Получение списка характеристик, заданного с помощью ключевого слова расширения языка запросов ХАРАКТЕРИСТИКИ или с помощью диалога указания характеристик объекта, выполняется с указанием ключевого слова РАЗРЕШЕННЫЕ. Если получение списка характеристик выполняется с помощью запроса – реализована возможность указания в этом запросе ключевого слова РАЗРЕШЕННЫЕ.При получении списка характеристик не использовалось ключевое слово РАЗРЕШЕННЫЕ.Реализация возможности использовать ограничение доступа к данным для таблиц, хранящих списки свойств (например, планы видов характеристик).
Система компоновки данных.
В детальных записях реализована возможность вывода полей несвязанных наборов данных. Для объектов ЗаписиМакетаКомпоновкиДанных и ЗаписиТаблицыМакетаКомпоновкиДанных реализованы свойства НаборыДанных. Значением свойства является массив, содержащий имена наборов данных, по которым надо выводить детальные записи.

Свойство НаборДанных для объектов ЗаписиМакетаКомпоновкиДанных и ЗаписиТаблицыМакетаКомпоновкиДанных является устаревшим и поддерживается для совместимости, пользоваться этим свойством не рекомендуется. Обращение к свойству НаборДанных приводит к исключению, если свойство НаборыДанных содержит массив из более чем одного элемента.

Было невозможно выводить поля из несвязанных наборов данных.

Свойство НаборДанных объектов ЗаписиМакетаКомпоновкиДанных и ЗаписиТаблицыМакетаКомпоновкиДанных содержало имя набора данных, по которому выводились детальные записи.

Возможность создания сложных аналитических отчетов.

Внешние источники данных.
В модуле менеджера таблицы внешнего источника данных реализовано событие ОбработкаПолученияФормы.Данная возможность не предоставлялась.Реализация возможности переопределения стандартной формы внешнего источника данных при открытии или получении.
Внешние источники данных.
Для объектных таблиц внешних источников данных реализована возможность организации иерархических списков. Для объекта метаданных Таблица реализованы реквизиты ПолеРодителя, ЗначениеНезаполненногоРодителя. Иерархические объектные таблицы можно использовать в системе компоновки данных, запросах, динамических списках.Данная возможность не предоставлялась.Реализация возможности работы с иерархическими данными во внешних источниках данных.
Внешние источники данных.
Работа с запросами.
Система компоновки данных.
Реализована возможность работы с временными таблицами для внешних источников данных. Временная таблица создается непосредственно в базе данных внешнего источника данных. Для обращения к временной таблице используется синтаксис ВнешнийИсточникДанных.<Имя внешнего источника данных>.ВременнаяТаблица.<Имя временной таблицы>.Данная возможность не предоставлялась.Возможность построения сложных отчетов на основании таблиц внешних источников данных.
План видов характеристик.
Система компоновки данных.
При задании характеристик объекта с помощью диалога Дополнительные характеристики объекта метаданных, если список характеристик получается не из плана видов характеристик, то тип значения характеристики определяется типом реквизита, указанного в реквизите Поле значения данного диалога. Если этот реквизит не заполнен, то типом значения характеристики является тип Булево.

При задании характеристик объекта с помощью расширения языка запросов ХАРАКТЕРИСТИКИ системы компоновки данных, если не указано свойство ТИП, то тип значения характеристики определяется типом значения, получаемого в свойстве ЗНАЧЕНИЯХАРАКТЕРИСТИК. Если свойство ЗНАЧЕНИЯХАРАКТЕРИСТИК не указано, то типом значения характеристики является тип Булево.

При задании характеристик объекта с помощью диалога Дополнительные характеристики объекта метаданных или расширения языка запросов ХАРАКТЕРИСТИКИ, если список характеристик получался не из плана видов характеристик, то типом значения характеристики являлся тип Булево.

+

Реализация возможности хранения типов характеристик в справочниках, при этом регулируя тип характеристики с помощью составного типа реквизита, хранящего значение характеристики (например, типа ресурса регистра сведений).
Встроенный язык.
Реализована сериализация описания индексов таблицы значений. Содержимое индексов не сериализуется, а восстанавливается при десериализации.При сериализации/десериализации индексы таблицы значений терялись.Более полное восстановление состояния таблицы значений при десериализации.
Диаграммы.
Реализованы новые виды диаграмм:
  • Воронка;
  • Воронка объемная;
  • Воронка нормированная;
  • Воронка нормированная, объемная.

Для объекта Диаграмма реализованы свойства: ВысотаГорлаВоронки, ШиринаГорлаВоронки, ПробелыВоронки. Свойства имеют смысл только для новых типов диаграмм.

Данная возможность не предоставлялась.Расширение возможностей диаграмм.
Диаграммы.
Реализован режим сглаживания диаграмм. Для объекта Диаграмма реализованы свойства РежимСглаживания и НатяжениеСглаживания. Данные свойства имеют смысл для следующих типов диаграмм: график, график с накоплениями, график с областями, график с областями и накоплением, график с областями нормированный, изометрическая непрерывная, изометрическая лента, водопад, воронка, воронка объемная, а также для следующих типов диаграмм, у которых для серий установлен флажок Индикатор: гистограмма, гистограмма объемная, гистограмма горизонтальная, гистограмма горизонтальная объемная, гистограмма с накоплением, гистограмма с накоплением объемная, гистограмма с накоплением горизонтальная объемная, гистограмма нормированная, гистограмма нормированная объемная, гистограмма нормированная горизонтальная, гистограмма нормированная горизонтальная объемная.Данная возможность не предоставлялась.Расширение возможностей диаграмм.
Диаграммы.
Реализована возможность соединения серий диаграмм. Для объекта Диаграмма реализованы свойства СоединениеЗначенийПоСериям, ЛинииСоединенияЗначенийПоСериям, ЦветСоединенияЗначенийПоСериям. Свойства имеют смысл для следующих типов диаграмм: гистограмма с накоплениями, гистограмма с накоплениями объемная, гистограмма с накоплениями горизонтальная, гистограмма с накоплениями объемная горизонтальная, гистограмма нормированная, гистограмма нормированная объемная, гистограмма нормированная горизонтальная, гистограмма нормированная объемная горизонтальная.Данная возможность не предоставлялась.Расширение возможностей диаграмм.
Диаграммы.
Реализован режим прозрачности диаграмм. Для объекта Диаграмма реализованы свойства РежимПолупрозрачности, ПроцентПолупрозрачности. Свойства имеют смысл для следующих типов диаграмм: график с областями, изометрическая, изометрическая пирамида, изометрическая непрерывная, изометрическая лента, водопад, воронка объемная, воронка нормированная объемная.Данная возможность не предоставлялась.Расширение возможности диаграмм.
Диаграммы.
Система компоновки данных.
Для объектов ЗначенияПараметровВыводаКомпоновкиДанных, ЗначенияПараметровВыводаГруппировкиКомпоновкиДанных, ЗначенияПараметровВыводаДиаграммыКомпоновкиДанных, ОформлениеДиаграммыОбластиКомпоновкиДанных реализованы следующие свойства: ТипДиаграммы.СоединениеЗначенийПоСериям, ТипДиаграммы.ЛинииСоединенияЗначенийПоСериям, ТипДиаграммы.ЦветСоединенияЗначенийПоСериям, ТипДиаграммы.РежимСглаживания, ТипДиаграммы.НатяжениеСглаживания, ТипДиаграммы.РежимПолупрозрачности. Эти свойства используются для настройки параметров макета компоновки данных.Данная возможность не предоставлялась.Расширение возможностей работы с диаграммами в системе компоновки данных.
Система компоновки данных.
В языке выражений системы компоновки данных реализованы следующие агрегатные функции: Каждый(), Любой(), СтандартноеОтклонениеГенеральнойСовокупности(), СтандартноеОтклонениеВыборки(), ДисперсияВыборки(), ДисперсияГенеральнойСовокупности(), КовариацияГенеральнойСовокупности(), КовариацияВыборки(), Корреляция(), РегрессияНаклон(), РегрессияОтрезок(), РегрессияКоличество(), РегрессияR2(), РегрессияСреднееX(), РегрессияСреднееY(), РегрессияСреднееSXX(), РегрессияСреднееSYY(), РегрессияСреднееSXY().Данные агрегатные функции отсутствовали в языке выражений системы компоновки данных.Возможность создания сложных аналитических отчетов.
Система компоновки данных.
В языке выражений системы компоновки данных реализованы следующие функции: ACos(), ASin(), ATan(), Sin(), Cos(), Tan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Окр(), Цел(), ТипЗначения(),Тип().Данные функции отсутствовали в языке выражений системы компоновки данных.Возможность создания сложных аналитических отчетов.
Система компоновки данных.
В языке выражений системы компоновки данных реализована агрегатная функция МестоВПорядке(). Функция возвращает номер по порядку для текущей записи среди записей текущей группировки, если все записи текущей группировки будут упорядочены в указанном порядке.Данная агрегатная функция отсутствовала в языке выражений системы компоновки данных.Возможность создания сложных аналитических отчетов.
Система компоновки данных.
В языке выражений системы компоновки данных реализована агрегатная функция КлассификацияABC(). Функция возвращает номер класса: 1 – класс «А», 2 – класс «B», 3 – класс «C».Данная агрегатная функция отсутствовала в языке выражений системы компоновки данных.Возможность создания сложных аналитических отчетов.
Табличный документ.
Для команды табличного документа Объединить реализовано сочетание клавиш Ctrl+M. В контекстном меню табличного документа реализована команда Объединить.Объединение ячеек табличного документа было возможно только с помощью команды меню Таблица - Объединить или соответствующей кнопки командной панели.Повышено удобство работы с табличными документами, содержащими большое количество объединенных ячеек.
Диаграммы.
Реализована поддержка свойства Индикатор для диаграммы изометрическая лента: при отключенном режиме сглаживания, серия с установленным свойством Индикатор отображается полупрозрачно на всей области диаграммы, образуя пересечения с остальными сериями.Данная возможность не предоставлялась.Расширение возможности диаграмм.
Управляемая форма.
Реализована возможность указания типа Произвольный для подчиненного реквизита у реквизита управляемой формы (например, колонка таблицы значений, дерева значений и т.д.).Хранить некоторые данные в подчиненных реквизитах реквизита управляемой формы невозможно. К таким данным относится ссылка на таблицу внешнего источника данных.Реализация возможности хранения в подчиненных реквизитах реквизита управляемой формы ссылок на таблицы внешних источников данных.
Отображение информации.
Реализована возможность управления двусторонней печатью для табличного документа, графической схемы (из встроенного языка и интерактивно) и текстового документа (только интерактивно). Реализованы системные перечисления ТипДвустороннейПечати и ЧередованиеРасположенияСтраниц.Управлять данной возможностью было возможно только с помощью драйвера принтера.Реализация возможности явного указания двусторонней печати для некоторых вариантов использования.
Средства разработки.
Средства публикации веб-клиента и Web-сервисов.
В диалоге публикации на веб-сервере возможно редактировать все элементы, присутствующие в файле default.vrd. В диалоге публикации на веб-сервере стало возможным редактировать произвольные файлы default.vrd.

Параметр descriptor утилиты webinst позволяет выполнять публикацию по шаблону. В качестве шаблона указывается сформированный файл default.vrd.

С помощью диалога публикации на веб-сервере можно было редактировать ограниченный набор элементов, присутствующих в файле default.vrd. Возможность публикации по шаблону для утилиты webinst была недоступна, что ограничивало возможности автоматизированной публикации, например невозможна публикация Web-сервисов с помощью утилиты. Возможность интерактивно редактировать все элементы файла default.vrd, создавать шаблоны для последующей автоматизированной публикации. Использование шаблонов открывает возможность публикации Web-сервисов с помощью утилиты командной строки.
Установка клиентского приложения.
Возможно настроить обновление дистрибутива тонкого клиента и получение списка общих информационных баз при помощи http-соединения или Web-сервиса.

В случае несовпадения версии клиентского приложения и сервера, реализовано автоматическое получение и установка тонкого клиента.

Для конфигурационного файла 1cestart.cfg реализованы параметры:

  • InternetService - адрес веб-сервиса для обновления дистрибутива тонкого клиента и списка общих информационных баз;
  • WebCommonInfoBases - адрес веб-сервиса для получения списка общих информационных баз;
  • WebDistributiveLocation - адрес веб-сервиса для обновления дистрибутива тонкого клиента.

Реализована возможность указания ссылки на дистрибутив тонкого клиента для конфигурационных файлов:

  • Для файла default.vrd с помощью атрибута pubdst;
  • Для файла conf.cfg с помощью параметра PublishDistributiveLocation.
Автоматическое обновление тонкого клиента и получение списка общих информационных баз было доступно только при работе в локальной сети.Возможность обновления дистрибутива тонкого клиента и получения списка общих информационных баз без создания общих каталогов позволяет получить актуальную версию дистрибутива и текущий список информационных баз при удаленной работе.
Работа с СУБД.
Для создания информационной базы в СУБД Oracle Database не требуются права DBA. При отсутствии прав DBA невозможно выполнить:
  • создание базы данных (схемы данных);
  • удаление базы данных (схемы данных) с помощью консоли управления кластером.
Для создания информационной базы в СУБД Oracle Database всегда требовались права DBA.Повышение безопасности работы с СУБД. Появилась возможность создания информационной базы без использования прав DBA в том случае, если база данных (схема данных) уже существует.
Работа с Интернет.
Встроенный язык.
Реализовано кодирование произвольных текстовых строк (метод глобального контекста КодироватьСтроку()):
  • С целью сделать строку с текстом пригодной для использования в качестве части URL.
  • С целью преобразовать строку URL в формат, соответствующий RFC 1738.

Реализована операция раскодирования строки (метод глобального контекста РаскодироватьСтроку()).

Данная возможность не предоставлялась.Облегчено программное формирование URL, содержащего не латинские символы.
Средства администрирования.
Реализована возможность создания самораспаковывающегося архива (SFX-архива) клиентского приложения для размещения на веб-сайте. В состав архива можно поместить конфигурационный файл 1CEStart.cfg, содержащий настройки, необходимые для установки, запуска и обновления клиентского приложения. Созданный исполняемый файл предназначен для использования только в ОС Windows.

Для создания архива используется утилита 1CEClientSetupMake.exe, которая публикуется на диске ИТС (http://its.1c.ru/db/metod81#content:4914:1).

Данная возможность не предоставлялась.Упрощает установку клиентского приложения на компьютер клиента в тех случаях, когда для доступа к информационной базе (через Интернет) желательно использование клиентского приложения, а не веб-клиента.

Оглавление

Новые возможности и изменения в режиме «1С:Предприятие»

ФункциональностьКак сталоКак былоРезультат изменения
Стандартные функции.
Поиск ссылок на таблицы внешних источников данных доступен для стандартной функции Поиск ссылок на объекты, работающей в управляемом режиме.Поиск ссылок на объекты внешних источников данных с помощью стандартной функции Поиск ссылок на объекты был не возможен.Реализация возможности поиска ссылок на объекты внешних источников данных с помощью стандартной функции.
Табличный документ.
В табличном документе, находящемся в режиме защиты, группировки можно сворачивать и разворачивать не только с помощью мыши, но и с помощью сочетания клавиш и контекстного меню табличного документа.В табличном документе, находящемся в режиме защиты, группировки можно было сворачивать и разворачивать только с помощью мыши.Повышение удобства работы с табличным документом.
Навигационные ссылки.
Для режима открытия форм В закладках, форма, открытая по команде из панели навигации, при запросе навигационной ссылки, возвращает ссылку на объект, отображаемый формой, если свойство управляемой формы АвтоНавигационнаяСсылка установлено в значение Истина. В противном случае возвращается значение свойства НавигационнаяСсылка управляемой формы.Для режима открытия форм В закладках, формы, открытые по командам из панели навигации, возвращали ссылки на точки навигации.Появилась возможность открыть форму списка в отдельном окне с помощью контекстного меню на заголовке закладки.
Управляемая форма.
Если свойство ячейки таблицы управляемой формы РежимРедактирования установлено в значение Непосредственно, то нажатие Enter в этой ячейке приводит к переходу к следующей редактируемой ячейке этой строки. Если ячейка в строке последняя, выполняется переход к первой редактируемой ячейке следующей строки. Если следующей строки нет и у таблицы управляемой формы свойство Автоввод новой строки установлено в значение Истина, то выполняется добавление новой строки.В режиме редактирования строки нажатие Enter приводило к завершению редактирования ячейки таблицы и не приводило к переходу к следующей ячейке.Нажатие кнопки Enter реализовано аналогично для режима ввода строки и для режима редактирования строки. Это упрощает работу с системой и делает работу более эффективной при редактировании табличных данных с использованием клавиатуры.
Управляемая форма.
Если выполняется редактирование ячейки таблицы управляемой формы, для которой свойство РежимРедактирования установлено в значение Непосредственно, то:
  • Нажатие клавиши Ins приводит к добавлению новой строки;
  • Нажатие клавиш PgUp и PgDn выполняет постраничное листание таблицы;
  • Нажатие сочетания клавиш Ctrl+Home и Ctrl+End выполняет переход, соответственно, к первой и последней строкам таблицы.
Данные возможности не предоставлялись.Повышение удобства использования таблицы управляемой формы.
Управляемая форма.
Для удаления строки таблицы управляемой формы реализовано сочетание клавиш Alt+Shift+Del. Данное сочетание можно использовать даже в том случае, если идет редактирование строки таблицы. Для таблицы управляемой формы с режимом автоматического добавления строк реализованы следующие возможности:
  • Новая строка удаляется, если в ней нет введенных данных и выполняется нажатие левой кнопкой мыши в любом месте, за пределами новой строки.
  • Новая строка удаляется также в том случае, если в ней нет введенных данных и выполняется переход к существующей строке таблицы с помощью клавиатуры.
Данные возможности не предоставлялись.Повышение удобства использования таблицы управляемой формы.
Управляемая форма.
Нажатие клавиши Вниз, при нахождении на последней строке, в таблице управляемой формы приводит к созданию новой строки. Если нажать клавишу Вверх в новой строке, не вводя в этой строке никаких данных, новая строка будет удалена.

При перемещении сверху вниз, с помощью нажатия клавиши Вниз (не отпуская ее) приведет к позиционированию курсора в последнюю строку таблицы управляемой формы. Для добавления новой строки необходимо отпустить и еще раз нажать клавишу Вниз.

Нажатие клавиши Вниз не приводило к добавлению новой строки. Нажатие клавиши Вверх не приводило к отказу от ввода новой строки.Повышение удобства использования таблицы управляемой формы.
Управляемая форма.
Для реквизитов типа Строка фиксированной длины изменено отображение автоотметки незаполненного, если этот реквизит расположен в таблице управляемой формы, табличном поле или табличном документе. Проверка заполненности значения выполняется с помощью метода ЗначениеЗаполнено(), соответственно значение типа Строка считается незаполненным, если в нем нет непробельных символов.Реквизит считался незаполненным только в том случае, если в нем содержалась пустая строка.Обеспечение единообразного поведения отметки незаполненного.
Веб-клиент.
При запуске системы с помощью веб-браузера, отсутствующего в списке поддерживаемых, отображается предупреждение об этом с возможностью продолжить работу или перейти к списку поддерживаемых веб-браузеров. Предупреждение отображается не чаще, чем 1 раз в неделю.Не проверялся запуск системы с помощью не поддерживаемых веб-браузеров.Оповещение пользователя о том, что он использует неподдерживаемую версию веб-браузера или неподдерживаемый веб-браузер.
Веб-клиент.
При запуске системы с помощью устаревшей версии веб-браузера выводится предупреждение об этом, с возможностью продолжить работу или перейти к списку поддерживаемых веб-браузеров. Предупреждение отображается не чаще, чем 1 раз в месяц.Не проверялся запуск системы с помощью устаревшей версии веб-браузера.Оповещение пользователя о том, что выполняется работа в устаревшей версии веб-браузера с предложением продолжить работу или перейти к списку поддерживаемых веб-браузеров. Рекомендуется сменить версию используемого веб-браузера.
Веб-клиент.
При запуске системы на новой версии Microsoft Internet Explorer, которая была недоступна во время разработки версии платформы, выводится предупреждение об этом с возможностью продолжить работу или перейти к списку поддерживаемых веб-браузеров. Предупреждение отображается не чаще, чем 1 раз в месяц.Не проверялся запуск системы с помощью новой версии веб-браузера Microsoft Internet Explorer.Оповещение пользователя о том, что данная версия веб-браузера Microsoft Internet Explorer не тестировалась на совместимость с «1С:Предприятием».
Технологический журнал.
Возможность помещения в технологический журнал информации о работе с внешними источниками данных. Для этого в конфигурационный файл технологического журнала добавлено событие <EDS>.Работа с внешними источниками данных не отражалась в технологическом журнале системы.Возможность анализа проблем при работе с внешними источниками данных.
Технологический журнал.
Возможность помещения в технологический журнал информации о выполнении операций, изменяющих работу кластера серверов, например во время репликации данных между сервисами кластера. Для этого в конфигурационный файл технологического журнала добавлено событие <CLSTR>.Не предоставлялось событий, формируемых при выполнении операций, изменяющих работу кластера серверов.Возможность анализа проблем при работе кластера серверов.
Кластер серверов.
Средства администрирования.
Для администрирования кластера серверов реализован кроссплатформенный сервер администрирования (ras). Приложение может работать как в режиме отдельного приложения, так и в режиме сервиса (демона). Сервер администрирования устанавливается в составе компонент сервера «1С:Предприятия».

Для взаимодействия с сервером администрирования реализована кроссплатформенная утилита командной строки (rac). Утилита администрирования устанавливается в составе компонент сервера «1С:Предприятия». Версия утилиты администрирования может не совпадать с версией сервера администрирования, с которым она (утилита) работает. Утилита позволяет выполнять администрирование кластера серверов в объеме, который доступен с помощью средств программного администрирования кластера (COM-объект V82.ComConnector), кроме аутентификации администраторов (информационной базы, кластера, рабочего сервера) средствами ОС. Данная возможность утилитой не поддерживается.

Также реализован интерфейс работы с сервером администрирования из языка Java, который (вместе с описанием и примером использования) распространяется с помощью ИТС (http://its.1c.ru/db/metod81#content:4985:1).

Средства администрирования кластера серверов «1С:Предприятия» были доступны только для ОС Windows в виде консоли администрирования кластера, а также COM-объекта V82.ComConnector. Средств администрирования кластера серверов для ОС Linux не предоставлялось.Возможность администрировать кластер серверов «1С:Предприятия» из командной строки на различных операционных системах (Windows и Linux), а также из программ, написанных на языке Java.

Оглавление

Оптимизация

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
При работе с Oracle Database оптимизировано выполнение запросов, на которые накладываются сложные условия ограничения доступа к данным.Недостаточная эффективность работы при наличии сложных условий ограничения доступа к данным.Повышена скорость работы ограничений доступа к данным на СУБД Oracle Database.
Прикладные объекты.
Оптимизирована работа с памятью некоторых механизмов.Недостаточная эффективность работы при определенных сценариях.Повышена общая эффективность работы системы в некоторых сценариях.
Работа с запросами.
При исполнении запроса, для всех условий В ИЕРАРХИИ с одинаковым значением параметра, формируется одна временная таблица на один пакетный запрос.При исполнении запроса, для всех условий В ИЕРАРХИИ с одинаковым значением параметра, формировалось несколько временных таблиц.Повышена производительность запросов, содержащих одинаковые значения параметров в нескольких операциях В ИЕРАРХИИ.
Работа с запросами.
При исполнении запроса, для всех условий В с одинаковым списком значений, используется одна временная таблица (для хранения списка) на один пакетный запрос.При исполнении запроса, для условий В с одинаковым списком значений параметра, формировалось несколько временных таблиц (по числу условий).Повышена производительность запросов, содержащих одинаковые значения параметров в нескольких операциях В.
Работа с запросами.
Оптимизирована работа запроса, при использовании конструкции В ИЕРАРХИИ. Оптимизирована работа системы компоновки данных с источником данных в виде запроса, при использовании конструкций В ГРУППЕ и В ГРУППЕ ИЗ СПИСКА.Недостаточная эффективность работы при выборках в запросах и отчетах при использовании условий вхождения в иерархию в некоторых ситуациях.Повышение производительности работы при выборках в запросах и отчетах при использовании условий вхождения в иерархию.
Кластер серверов.
Клиентское приложение.
Существенно уменьшено потребление памяти рабочими процессами сервера. Ускорен запуск клиентского приложения.

Эффект особенно заметен для конфигураций, обладающих большим объемом метаданных.

Недостаточно эффективное использование памяти для конфигураций с большим объемом метаданных.Снижение требований к оперативной памяти серверов для конфигураций с большим объемом метаданных.
Работа с СУБД.
При использовании СУБД PostgreSQL и Oracle Database оптимизирована запись движений с обновлением итогов регистра бухгалтерии за счет реализации дополнительного индекса.

Увеличение скорости будет достигнуто после реструктуризации регистров бухгалтерии и отключения режима совместимости.

Текущая структура данных не позволяла полностью использовать существующий индекс, что приводило к недостаточно эффективной работе системы.Повышена скорость работы с регистром бухгалтерии на СУБД PostgreSQL и Oracle Database.
Работа с СУБД.
Повышена скорость выполнения запросов к основным таблицам при работе с СУБД Oracle Database.Использовалось недостаточно оптимальное получение результатов запросов к СУБД.Уменьшилось время выполнения запросов к базе данных, в том числе существенно увеличена скорость обновления конфигурации базы данных в том случае, если требуется реструктуризация информационной базы.
Работа с СУБД.
Оптимизировано выполнение некоторых запросов к СУБД для регистра бухгалтерии, в частности тех, в которых используются отборы по счетам.Недостаточно эффективно использовались возможности СУБД.Повышена скорость работы «тяжелых» запросов к регистру бухгалтерии, например в бухгалтерских отчетах и операциях закрытия месяца.
Работа с СУБД.
Оптимизирована работа с временными таблицами в Microsoft SQL Server, а также работа объектов, использующих временные таблицы: регистров накопления, регистров бухгалтерии, последовательностей и т.д.Недостаточно эффективная работа системы при интенсивном использовании временных таблиц.Повышение эффективности работа системы при работе с Microsoft SQL Server при интенсивном использовании временных таблиц.
Веб-клиент.
Ускорен запуск веб-клиента на медленных соединениях.При запуске веб-клиента выполнялось получение большого объема служебной информации.Ускорен запуск веб-клиента на медленных соединениях.
Работа с СУБД.
Ускорена работа системы при работе с СУБД Microsoft SQL Server в следующих случаях:
  • запись и чтение данных;
  • загрузка информационной базы из файла *.dt (если выбран режим восстановления Простой или С неполным протоколированием);
  • реструктуризация информационной базы (если выбран режим восстановления Простой или С неполным протоколированием).

+

Недостаточно эффективно использовались возможности СУБД.Увеличена скорость работы с информационной базой на СУБД Microsoft SQL Server.
Регистры бухгалтерии.
Оптимизирована работа регистра бухгалтерии в следующих случаях:
  • запись наборов записей с количеством записей до десяти и несколько сотен записей;
  • получение итогов на определенный момент времени;
  • формирование отчетов, использующих регистр бухгалтерии.

Требуется выполнение реструктуризации информационной базы для получения эффекта от оптимизации.

Недостаточная эффективность работы регистра бухгалтерии в некоторых сценариях.Повышение эффективности работы регистра бухгалтерии при большом объеме данных.
Работа с СУБД.
Ускорена работа при использовании СУБД PostgreSQL за счет изменения структуры индексов. Оптимизация действует для новых информационных баз и для существующих после выполнения реструктуризации базы данных.При работе с СУБД PostgreSQL кластерные индексы не использовались, вместо кластерных создавались обычные индексы.Уменьшение времени выполнения операций при работе с СУБД PostgreSQL.
Работа с СУБД.
Стало возможно использовать отдельные табличные пространства для индексов (пространство v81c_index) и данных (пространство v81c_data) в СУБД PostgreSQL.

Табличные пространства не создаются автоматически и должны быть созданы администратором базы данных. Если дополнительных табличных пространств не создано - используется табличное пространство по умолчанию (pg_default).

Использование одного табличного пространства могло снижать производительность системы за счет недостаточной производительности дискового накопителя или его перегрузки.Позволяет управлять производительностью системы, за счет разнесения табличных пространств по разным дисковым накопителям в СУБД PostgreSQL.
Веб-клиент.
В веб-клиенте ускорено открытие форм в закладках основного окна, а также форм, блокирующих окно владельца.Недостаточная эффективность работы при открытии форм.Ускорено открытие форм, повышена комфортность работы пользователя.
Работа с запросами.
Оптимизировано получение выборки по группировке (с большим количеством записей) из результата запроса, содержащего предложение ИТОГИ.Недостаточно эффективно выполнялось получение выборки по группировке из результата запроса, содержащего итоги.Повышена производительность работы с результатами запроса, содержащими итоги.
Кластер серверов.
Повышена производительность и масштабируемость работы сервера при работе со ссылочными типами данных.Недостаточно эффективная работа сервера при работе со ссылочными типами данных.Ускорена работа сервера при работе со ссылочными типами данных.
Работа с СУБД.
При использовании СУБД IBM DB2 версии 9.7 и выше, временные таблицы, содержащие данные неограниченной длины, являются временными.При работе с данными неограниченной длины создавались постоянные таблицы, которые удалялись после использования.Исключены блокировки системных таблиц, увеличена параллельность при работе большого количества пользователей.
Работа с СУБД.
Ускорена работа системы с СУБД IBM DB2 на некоторых операциях.Недостаточно эффективное использование возможностей СУБД IBM DB2.Повышена эффективность использования СУБД IBM DB2.
Работа с СУБД.
Регистры бухгалтерии.
Ускорена обработка регистра бухгалтерии в процессе обновления конфигурации базы данных в клиент-серверном варианте информационной базы.Недостаточно эффективное выполнение операции реструктуризации регистра бухгалтерии.Повышена скорость обработки регистра бухгалтерии при выполнении операции реструктуризации.
Регистры сведений.
Для периодических регистров сведений реализованы итоги, которые используются для получения срезов первых/последних при выполнении всех следующих условий:
  • Разрешено использование итогов (в метаданных);
  • Установлено использование итогов (в режиме «1С:Предприятия»);
  • Срез получается без указания даты;
  • В условиях получения среза используются только измерения и разделители;
  • В ограничениях доступа к данным для регистра используются только измерения и разделители.

Для объекта конфигурации регистр сведений реализованы свойства РазрешитьИтогиСрезПервых и РазрешитьИтогиСрезПоследних.

Для менеджера регистра сведений реализованы методы ПересчитатьИтоги(), УстановитьИспользованиеИтогов(), ПолучитьИспользованиеИтогов().

Для регистров сведений реализовано право доступа УправлениеИтогами.

Тестирование и исправление информационной базы в конфигураторе выполняет перестроение среза первых/последних в случае, если выбран пункт Пересчет итогов в списке проверок и для регистра разрешено использование итогов.

Каждое получение среза приводило к выполнению запроса к основной таблице регистра с расчетом значений ресурсов.Повышена скорость получения срезов первых/последних на самый первый и самый последний (текущий) моменты времени.
Средства разработки.
Оптимизировано использование памяти при работе с конфигурацией, находящейся на поддержке, а также для случаев загрузки и выгрузки файла 1cv8.dt.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

В ряде случае было невозможно работать с конфигурациями, стоящими на поддержке других конфигураций большого объема.Уменьшена потребность в оперативной памяти при работе с конфигурациями поставщика большого объема.

Оглавление

Изменения, влияющие на поведение системы

ФункциональностьКак сталоКак былоРезультат изменения
Работа с СУБД.
Если запрос к базе данных содержит более 400 уровней вложенности выражений, то генерируется исключение, не приводящее к завершению работы системы.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Если запрос к базе данных содержал более 400 уровней вложенности выражений, происходило аварийное завершение работы системы.Повышение стабильности системы, предотвращение аварийного завершения при выполнении сложного запроса.
Проверка заполнения реквизитов.
Функциональные опции.
Реквизиты, отключенные функциональной опцией, не включаются в список проверяемых реквизитов обработчика ОбработкаПроверкиЗаполненияНаСервере().

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При формировании списка проверяемых реквизитов не учитывалось действие функциональных опций.У прикладного разработчика отсутствует необходимость программно исключать из проверки реквизиты, отключенные функциональными опциями.
Работа с запросами.
При наличии в результате запроса списка итогов с общим итогом, выгрузка результата запроса с помощью метода Выгрузить(ОбходРезультатаЗапроса.ПоГруппировкам) объекта РезультатЗапроса, приведет к организации в результирующем дереве одного узла с общим итогом, элементами которого будут узлы для группировок, расположенных в запросе после общего итога.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При наличии в результате запроса списка итогов с общим итогом, выгрузка результата запроса с помощью метода Выгрузить(ОбходРезультатаЗапроса.ПоГруппировкам) объекта РезультатЗапроса, приводила к организации в результирующем дереве нескольких узлов на одном уровне: общий итог и группировки, расположенные в запросе после общего итога.Поведение запроса позволяет более удобно работать с итогами при выгрузке результата в дерево.
Система компоновки данных.
При выводе результата компоновки данных в коллекцию значений, для колонки, в которую выводится вычисляемое поле, устанавливается тип значения, указанный в вычисляемом поле. Если тип значения у вычисляемого поля не указан, то тип колонки определяется автоматически на основании выражения вычисляемого поля.

В режиме совместимости с версией 8.2.16 изменений нет.

При выводе результата компоновки данных в коллекцию значений, для колонки, в которую выводится вычисляемое поле, устанавливался тип значения, который всегда определялся автоматически, на основании выражения вычисляемого поля.Возможность явной типизации вычисляемого поля в тех случаях, когда затруднено или невозможно автоматическое определение типа.
Клиент-серверное взаимодействие.
При смене версии сервера не выполняется автоматическое удаление сеансов, существующих на момент старта менеджера кластера.

При завершении клиентского приложения, работающего через веб-сервер, по исключению о различии версии клиента и сервера происходит попытка удаления сеанса на сервере.

При смене версии сервера формировалось сообщение Сеанс отсутствует или удален. При этом пользователь не получал адекватной информации о проблеме.При смене версии платформы на сервере, пользователь получает сообщения о том, что различаются версии клиентского приложения и сервера, а не неинформативное сообщения о том, что сеанс отсутствует или удален.
Хранилище конфигурации.
При работе с сервером хранилища конфигурации выполняется проверка текущей версии сервера и конфигуратора. Работа с сервером возможна только при условии совпадения версий сервера хранилища конфигурации и конфигуратора.При работе с сервером хранилища конфигурации не проверялось совпадение версии сервера хранилища и конфигуратора.Предупреждение возникновения проблем совместимости в том случае, если сервер хранилища конфигурации и конфигуратор обладают разными версиями.
Хранилище конфигурации.
При работе конфигуратора в пакетном режиме в том случае, если обнаружено изменение расположения информационной базы, подключенной к хранилищу, выполняется повторное связывание информационной базы и хранилища и предупреждение не выводится.

При проверке расположения информационной базы, подключенной к хранилищу, игнорируется имя компьютера, с которого выполняется подключение к информационной базе, для клиент-серверных информационных баз и файловых информационных баз, расположенных на сетевом диске.

В пакетном режиме выдавалось предупреждение о изменении расположения информационной базы, подключенной к хранилищу конфигурации и ожидался ответ пользователя.

При проверке расположения информационной базы, подключенной к хранилищу, учитывалось имя компьютера, с которого выполняется подключение к информационной базе, для клиент-серверных информационных баз и файловых информационных баз, расположенных на сетевом диске.

Обращение в пакетном режиме к копии информационной базы, соединенной с хранилищем от имени того же пользователя хранилища, что и оригинальная информационная база, приведет к отключению оригинальной информационной базы от хранилища.

Не выдается предупреждение о смене местоположения информационной базы, подключенной к хранилищу, в том случае, если подключения отличаются только именем компьютера, с которого выполняется подключение при использовании клиент-серверного варианта или файлового варианта, расположенного на сетевом диске.

Работа с СУБД.
При использовании СУБД IBM DB2 создаются кластерные индексы:
  • для объектных таблиц - первичного ключа (ссылка);
  • таблицы итогов между счетами - по периоду;
  • регистры сведений - Измерения, Измерения+Период, Регистратор+Номер, Измерения+Период+Регистратор+Номер, Измерения+Период (в зависимости от типа регистра).
При использовании СУБД IBM DB2 использовались следующие индексы:
  • для объектных таблиц - индекс по первичному ключу не является кластерным;
  • таблицы итогов между счетами - кластерный индекс отсутствует;
  • регистры сведений - кластерный индекс использовался только в следующих случаях: Регистратор, Измерения, Измерения+Период (в зависимости от типа регистра).
Обеспечение единого подхода к реализации индексов у объектов на различных СУБД.
Экспорт в Microsoft Excel.
При экспорте табличного документа в форматы Microsoft Excel 97 или Microsoft Excel 2007, ячейки табличного документа, выровненные влево, экспортируются с установкой общего формата ячейки.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При экспорте табличного документа в форматы Microsoft Excel 97 или Microsoft Excel 2007, происходило преобразование ячеек в число в следующих случаях:
  • в содержимом строки удается распознать число и после числа нет текстовых данных,
  • в содержимом строки распознано число, после которого расположены текстовые данные, но ячейка выровнена вправо, или по центру.
Если ячейка табличного документа содержит числовое значение, которое используется как текст и значение прижато к левой границе ячейки, например, ячейка содержит код или артикул номенклатуры, то при экспорте в формат Microsoft Excel не происходит преобразования ячейки в число, что облегчает использование получившегося документа (включая редактирование и сравнение).
Встроенный язык.
Управляемая форма.
Для методов ПолучитьФорму(), ОткрытьФорму() и ОткрытьФормуМодально(), реализован параметр НавигационнаяСсылка, значение которого будет присвоено одноименному свойству получаемой/открываемой формы, если значение параметра не равно Неопределено, при этом свойство получаемой/открываемой управляемой формы АвтоНавигационнаяСсылка будет установлено в значение Ложь.

Для объекта ПараметрыВыполненияКоманды реализовано свойство НавигационнаяСсылка. В примере программного кода, который создается в модуле команды, реализовано использование данного свойства.

Данная возможность не предоставлялась.Возможность задания навигационной ссылки для открываемой формы для дальнейшего использования в интерактивном режиме (например, для запоминания в истории).
Список пользователей информационной базы.
При нажатии сочетания клавиш Shift+Del, в списке пользователей информационной базы, выдается предупреждение.Нажатие сочетания клавиш Shift+Del в списке пользователей информационной базы приводило к удалению пользователя без предупреждений.Предотвращение случайного удаления пользователя информационной базы.
Программное лицензирование.
Если при запуске приложения не найдена лицензия, необходимая для работы приложения, то в протокол поиска лицензии помещается информация о расхождениях между текущими параметрами оборудования и параметрами оборудования при получении лицензии. Эта информация помещается только для программных лицензий.Информация о расхождениях параметров оборудования не публиковалась в протоколе поиска лицензии.Упрощается диагностика проблем с программными лицензиями, если лицензия не выдается по причине расхождения параметров оборудования.
Работа с СУБД.
Управляемые блокировки.
При работе с Microsoft SQL Server версии 2005 и выше, в режиме совместимости с версией 8.2.16 и старше, используется режим управления версиями строк, если конфигурация использует режим управляемых блокировок. Используется уровень изоляции транзакций READ_COMMITTED_SNAPSHOT. При чтении данных вне транзакций используется согласованное чтение.Microsoft SQL Server 2005 и выше использовался в режиме блокировок. Использовался уровень изоляции транзакций READ_COMMITTED. При чтении вне транзакций использовалось «грязное» чтение.Реализованные изменения приводят:
  • К уменьшению блокировок и взаимоблокировок при выполнении запросов, работающих в транзакции;
  • Исчезновению ошибок при выполнении запросов вне транзакции над часто модифицируемыми прикладными объектами;
  • Получению согласованных результатов отчета вне транзакции на момент выполнения отчета.
Управляемая форма.
Система компоновки данных.
Реализована возможность формирования быстрых пользовательских настроек в виде набора полей формы в отдельной группе, расположением и другими параметрами которой прикладной разработчик может управлять. Реализовано свойство Группа пользовательских настроек расширения формы отчета управляемой формы.

Реализована возможность явно создать элементы пользовательских настроек с помощью метода СоздатьЭлементыФормыПользовательскихНастроек() расширения управляемой формы для отчета. Перед созданием элементов настроек выполняется очистка группы от существующих в ней элементов.

Автоматически создаваемые формы (отчета и пользовательских настроек) содержат специальные группы, в которых выполняется создание элементов, позволяющих редактировать настройки.

Для расширения формы отчета управляемой формы реализовано событие ПриОбновленииСоставаПользовательскихНастроекНаСервере. Данное событие вызывается в следующих случаях:

  • При создании формы отчета;
  • После загрузки варианта отчета;
  • После изменения варианта отчета;
  • После редактирования пользователем состава настроек.

Изменено представление автоматически генерируемой формы отчета: представление варианта отчета перенесено в заголовок отчета, кнопка выбора варианта перенесена в командную панель отчета и т.д.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Быстрые пользовательские настройки редактировались в специальной таблице, размещенной в форме. Форма редактирования пользовательских настроек содержала таблицу для редактирования всех пользовательских настроек.

В форме отчета располагалось поле с представлением текущего варианта и кнопкой выбора варианта отчета.

Повышено удобство работы с настройками отчета - они стали выглядеть аналогично другим элементам формы прикладного решения за счет использования обычных элементов формы (поле ввода, флажок и т. д.), вместо использования специальных таблиц редактирования настроек.
Журнал регистрации.
При чтении журнала регистрации не выполняется отбор событий по текущему значению разделителя, если разделитель в этом сеансе условно выключен.При чтении записей журнала регистрации выполнялся отбор по значению условно выключенного разделителя.Устранено различие в работе журнала регистрации между информационной базой без разделителей и информационной базой с условно отключенным разделителем.
Работа с СУБД.
Изменилась внутренняя реализация выполнения некоторых запросов при работе с СУБД PostgreSQL, IBM DB2 и Oracle Database.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Реализация в меньшей степени учитывала особенности СУБД.Улучшение внутренней реализации работы механизма запросов для конкретных СУБД.
Командный интерфейс.
Реализованы навигационные ссылки на списки. Для формы, основным реквизитом которой является динамический список с указанной основной таблицей, будет получена навигационная ссылка на список объекта, заданного в качестве основной таблицы. Переход по ссылке открывает основную форму списка.

Для метода глобального контекста ПерейтиПоНавигационнойСсылке() реализована поддержка навигационных ссылок на списки.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Навигационные ссылки на списки не предоставлялись.Возможность запоминать ссылки на списки в истории и избранном.
Отчет о сравнении объектов.
Изменен отчет о сравнении ролей. В отчет не выводится информация о добавленных и удаленных объектах, права на которые не отличаются от прав по умолчанию для таких объектов.

+

В отчет выводилась информация о добавленных и удаленных объектах, права на которые не отличаются от прав по умолчанию для таких объектов. Отказ от отображения «лишней» информации, которая не помогала в процессе объединения.
Используемые компоненты.
Выполнен переход с использования библиотеки OpenSSL версии 1.0.1 на использование библиотеки OpenSSL версии 1.0.0g.Использовалась библиотека OpenSSL версии 1.0.1.Устранение ошибки Ошибка HTTP при обращении к серверу при запуске тонкого клиента.
Прикладные объекты.
Свойствам Длина наименования и Длина порядка объекта План счетов установлено ограничение в 628 символов. Проверка текущих значений свойств будет выполняться только при попытке изменить их значения.Значения свойств Длина наименования и Длина порядка объекта План счетов были не ограничены.Повышение стабильности работы системы. Предотвращение возможности приведения информационной базы (в файловом варианте) в неработоспособное состояние. Предотвращение возможного падения производительности.
Работа с запросами.
В тексте на встроенном языке, генерируемом с помощью конструктора запроса с обработкой результата, для переменной, содержащей результат запроса, назначается имя РезультатЗапроса.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

В определенных случаях (например, при создании запроса с обработкой результата в форме отчета) возникал конфликт имен переменных: между именами, которые создавал конструктор, и именами реквизитов формы, в модуле которой этот код размещался. В результате сгенерированный код оказывался неработоспособным.Исключены конфликты имен переменных, создаваемых конструктором запроса с обработкой результата, и имен реквизитов формы отчета.
Система компоновки данных.
Поле запроса, участвующее в объединении, становится недоступным для участия в отборе, если во всех частях объединения значение поля имеет значение NULL.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Если значение поля запроса, участвующее в объединении, имеет значение NULL во всех частях объединения, то отбор применялся на уровне набора данных макета компоновки данных, а не в запросе.

При использовании в запросе набора данных системы компоновки данных с автоматическим заполнением доступных настроек конструкции ОБЪЕДИНИТЬ или ОБЪЕДИНИТЬ ВСЕ, и накладывании отбора на реквизит поля, отбор накладывается только в тех частях объединения, в которых данный реквизит существует. При применении отбора к полю отбор применяется только в тех частях, где выражение поля не равно NULL.
Журнал регистрации.
В списке Типы файлов, в диалоге открытия файла толстого клиента и конфигуратора, из списка расширений удалено расширение *.elf. Сохранена возможность открытия журнала регистрации формата elf. Для этого необходимо выбрать тип файлов Журнал регистрации (*.lgf) и вручную ввести имя файла с явным указанием расширения elf.В списке расширений диалога открытия файлов толстого клиента и конфигуратора присутствовали оба расширения: *.lgf и *.elf.Исключение устаревших возможностей из пользовательского интерфейса.
Журнал регистрации.
Отображение информации.
В обычной форме журнала регистрации события, относящиеся к отмененным транзакциям, отображается серым цветом, аналогично управляемой форме журнала регистрации.

В режиме совместимости с версией 8.1 поведение не изменилось.

В обычной форме журнала регистрации события, относящиеся к отмененным транзакциям, отображались черным цветом.Унификация отображения обычной и управляемой формы журнала регистрации.
Стандартные функции.
Отображение информации.
Изменено представление объектов в стандартных функциях Поиск ссылок на объекты и Удаление помеченных объектов. Из представления объектов удалены наименования видов объектов метаданных.В стандартных функциях Поиск ссылок на объекты и Удаление помеченных объектов представление объектов содержало наименование вида объекта метаданных.Представление объектов приведено к стандартному виду, принятому в системе.
Регистры накопления.
Регистры бухгалтерии.
Общие реквизиты / Разделение данных.
Кластер серверов.
Изменения таблицы настроек хранения итогов для регистров накопления и бухгалтерии выполняются в рамках транзакции. При работе с таблицами настроек хранения итогов накладываются управляемые блокировки на соответствующее пространство блокировок.

Для рабочих процессов реализован кеш настроек хранения итогов.

Работа с таблицами настроек хранения итогов регистров накопления и бухгалтерии выполнялись вне транзакции.

Каждое получение настроек хранения итогов выполнялось с помощью запроса к базе данных.

Ликвидация конфликтов модификации таблиц настроек хранения итогов из нескольких параллельных сеансов с одинаковыми значениями используемых разделителей.

Уменьшение количества запросов к базе данных и улучшение параллельности работы в сеансах с использованием разделителей.

Общие реквизиты / Разделение данных.
Регистры бухгалтерии.
Регистры накопления.
При удалении разделителей или модификации типов разделителей, во время обновления конфигурации базы данных, в таблицах настроек хранения итогов регистров накопления и бухгалтерии происходит объединение записей по новым комбинациям установленных разделителей.При удалении разделителя или модификации типов разделителей были возможны следующие ситуации:
  • Вставка записей с неуникальными значениями в таблицу настроек хранения итогов;
  • Ошибка обновления с диагностикой попытки вставки неуникальной записи.
Повышена стабильность работы системы при обновлении конфигурации базы данных, вызванной удалением разделителя или модификацией типа разделителя.
Работа с текстом.
Реализована запись маркера BOM в начало файла, формируемого с помощью объекта ЗаписьТекста в том случае, если записываемый файл не существует и параметр конструктора Дописывать имеет значение Истина и кодировка текста установлена в значение UTF-8.

В режиме совместимости с версией 8.2.16 изменений нет.

Файл, сформированный с помощью объекта ЗаписьТекста, записывался без маркера BOM в начале файла в том случае, если записываемый файл не существует и параметр конструктора Дописывать имеет значение Истина и кодировка текста установлена в значение UTF-8.Наличие маркера BOM обеспечивает однозначное определение кодировки текста в файле.
Работа с XML, XDTO.
Если при импорте схемы XSD будет обнаружено отсутствие определения в схеме целевого пространства имен, после выполнения попытки импорта будет выдано диагностическое сообщение.При импорте схемы XSD не формировалась диагностики в случае обнаружения проблем при загрузке.Улучшение диагностики при импорте схем XSD.
Работа с СУБД.
В документации уточнены особенности работы с СУБД Oracle Database и PostgreSQL.Документация недостаточно точно отражала особенности работы с СУБД Oracle Database и PostgreSQL.Уточнение документации позволяет разработчику лучше учитывать особенности работы платформы с СУБД при разработке конфигураций.
Табличный документ.
При изменении области выделения табличного документа, если в область выделения попадают строки с различными форматами строк, автоматически включается режим выделения строк. Если режим выделения строк был автоматически включен, из режима выделения ячеек, и при изменении выделения в выделении окажутся строки только с одним форматом строк, то режим выделения автоматически возвращается к режиму выделения ячеек.Выделить строки с разными форматами можно было или с помощью заголовков строк табличного документа или с помощью сочетания клавиш Alt+Shift+Стрелки.Упрощение копирование информации из табличных документов с разными форматами строк.
Веб-клиент.
Табличный документ.
В веб-клиенте доступно интерактивное изменение табличного документа. Изменено меню Таблица главного меню веб-клиента. Для табличного документа в веб-браузере Chrome реализована работа буфера обмена. Буфер обмена работает только в пределах одного экземпляра веб-браузера, работающего с одной информационной базой.Данная возможность не предоставлялась (кроме редактирования ячеек со значениями, изменения отображения группировок, изменения фиксации строк и колонок, а также изменения ширины колонок).Возможность интерактивной доработки табличных документов после их формирования в веб-клиенте.
Клиентское приложение.
Веб-клиент.
Конфигуратор.
Табличный документ.
В меню Таблица главного меню тонкого клиента, веб-клиента, толстого клиента и конфигуратора реализовано подменю Ячейки, в которое перенесены некоторые команды меню Таблица и добавлены новые команды.Подменю Ячейки отсутствовало в меню Таблица главного меню тонкого клиента, веб-клиента, толстого клиента и конфигуратора.Повышено удобство работы с табличным документом. Команды работы с ячейками табличного документа сгруппированы в одно меню.
Динамическое обновление.
Повышена надежность работы динамического обновления в различных ситуациях.В некоторых ситуациях динамическое обновление работало некорректно.Повышена надежность работы динамического обновления.
Управляемая форма.
Реализовано изменение размера кнопок управляемой формы при установленном ограничении ширины обычной группы, аналогично другим элементам.Установленное ограничение ширины обычной группы не всегда приводило к изменению размера кнопок.Унифицирован алгоритм изменения размеров элементов при установке ограничения размера обычной группы.
Отображение информации.
Управляемая форма.
Подсказка у элементов управляемой формы может быть нескольких видов: непосредственно в поле ввода, рядом с элементом формы и открывающаяся по кнопке (во всплывающем окне). Если для команды формы не задана подсказка, то подсказка не отображается для связанной с ней кнопки командной панели.

Для отображения подсказки непосредственно в поле ввода реализовано свойство ПодсказкаВвода, содержащее текст подсказки. Данный вид подсказки недоступен для полей ввода, связанных с данными типа Число и Дата.

Для управления отображением подсказки и ее оформлением реализованы свойства РасширеннаяПодсказка и ОтображениеПодсказки для следующих элементов управляемой формы: поле, таблица, группа, кнопка, декорация вида Текст.

Подсказка была доступна через всплывающую подсказку элемента формы.

Если для команды формы не задана подсказка, то для связанной с ней кнопкой командной панели в качестве подсказки отображался заголовок.

Появилась возможность гибкого управления расположением подсказок и оформительскими свойствами подсказок.

Оглавление

Изменения, требующие изменений в конфигурациях и административных установках

ФункциональностьКак сталоКак былоРезультат изменения
Система программ "1С:Предприятие".
Версия «1С:Предприятия» изменена на 8.3.

Изменены каталоги установки:

  • Для ОС Windows: C:\Program Files\1cv8;
  • Для ОС Linux: /opt/1С/v8.3.

Изменены имена файлов установки:

  • Для ОС Windows: 1CEnterprise 8*.msi;
  • Для ОС Linux: 1С_Enterprise83*.

Изменены имена COM-объектов: V83.Application, V83.ComConnector.

Служба сервера называется:

  • Для ОС Windows: Агент сервера 1С:Предприятия 8.3 (1C:Enterprise 8.3 Server Agent);
  • Для ОС Linux: srv1cv83.

Пользователь, от имени которого по умолчанию запускается служба сервера, называется usr1cv8.

Изменен каталог шаблонов по умолчанию: %APPDATA%\1C\1Cv8\tmplts.

Изменен каталог установки внешних компонент: %APPDATA%\1C\1Cv8\ExCompT.

«1С:Предприятие» имело номер версии 8.2.

Каталоги установки назывались:

  • Для ОС Windows: C:\Program Files\1cv82;
  • Для ОС Linux: /opt/1С/v8.2.

Файлы установки назывались:

  • Для ОС Windows: 1CEnterprise 8.2*.msi;
  • Для ОС Linux: 1С_Enterprise82*.

COM-объекты имели имена: V82.Application, V82.ComConnector.

Служба сервера называлась:

  • Для ОС Windows: Агент сервера 1С:Предприятия 8.2 (1C:Enterprise 8.2 Server Agent);
  • Для ОС Linux: srv1cv82.

Пользователь, от имени которого по умолчанию запускается служба сервера, назывался usr1cv82.

Каталог шаблонов по умолчанию располагался по адресу %APPDATA%\1C\1Cv82\tmplts.

Каталог установки внешних компонент располагался по адресу %APPDATA%\1C\1Cv82\ExCompT.

В связи с изменением номера версии, изменились имена и идентификаторы, использующие в своем составе номер версии.
Прикладные объекты.
В журнале документов реквизит, хранящий номер документа, формируется фиксированной длины, если все документы, входящие в журнал, имеют поле номера типа Строка фиксированной длины. В противном случае поле журнала будет обладать переменной длиной.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

В журнале документов, реквизит, отвечающий за номер документов, всегда формировался фиксированной длины.Получение номера документа выполняется единообразно, вне зависимости от того, откуда получается значение номера документа: из самого документа или из журнала документов.
Табличный документ.
При вызове, на стороне сервера или во внешнем соединении, методов табличного документа Показать(), Напечатать(), Скрыть(), а также метода Записать() с установленным параметром ТипФайлаТабличногоДокумента в значение XLS95, вызывается исключение.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Вызов указанных методов, на стороне сервера или во внешнем соединении, не приводил к ошибке, но и не выполнял каких-то действий.Упрощено обнаружение ошибок конфигурации, связанных с некорректным указанием типа файла при работе с табличным документом на сервере или во внешнем соединении.
Работа с запросами.
В языке запросов не допускается указание квалификаторов типов в функции языка запросов Тип().

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Для функции языка запросов Тип() допускалось указание квалификаторов типов, однако это не влияло на результат функции.Реализована проверка, исключающая неправильное использование синтаксиса языка запросов.
Табличный документ.
Масштаб печати табличного документа не оказывает влияния на размер полей страницы.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Установленный масштаб печати оказывал влияние на размеры полей страницы табличного документа.Возможность независимого управления полями и масштабом печати.
Система компоновки данных.
При выводе результатов компоновки данных в коллекцию значений, поля различных группировок, ссылающихся на одно поле компоновки данных, попадают в одну колонку коллекции.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При выводе результатов компоновки данных в коллекцию значений, поля различных группировок, ссылающихся на одно поле компоновки данных, попадали в разные колонки коллекции.Вывод результата в коллекцию приведен в соответствие с выводом в табличный документ.
Командный интерфейс.
Встроенный язык.
Формат навигационной ссылки на точку навигации, образованную стандартной командой, изменен на следующий: e1cib/navigationpoint/Закупки/Справочник.Товары.ОткрытьСписок. Навигационный ссылки предыдущего формата также могут использоваться.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Навигационная ссылка на точку навигации, образованная стандартной командой, имела следующий формат: e1cib/navigationpoint/Закупки/Справочник.Товары.Команда.ОткрытьСписокУнификация использования имен метаданных.
Работа с СУБД.
Внешние источники данных.
Если свойство Имя в источнике данных поля таблицы внешнего источника данных содержит значение, заключенное в одинарные кавычки, то при формировании запроса к СУБД это значение не будет дополнительно заключено в двойные кавычки, независимо от состава символов в этом поле. В других случаях, при наличии в значении поля спецсимволов, имя поля заключается в двойные кавычки.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Если свойство Имя в источнике данных поля таблицы внешнего источника данных содержало спецсимволы (включая одинарные кавычки), то при формировании запроса к СУБД это значение дополнительно заключалось в двойные кавычки.Обеспечение работоспособности системы с СУБД, которые используют различный синтаксис описания полей запроса/базы данных (например MySQL).
Программное лицензирование.
При поиске доступных лицензий используются файлы программных лицензий из всех каталогов, в которых эти файлы могут располагаться.Поиск запрошенной программной лицензии выполнялся только среди файлов *.lic, расположенных в первом каталоге (из перечня возможных каталогов), содержащем файлы лицензий. Каталоги, которые стоят в порядке поиска после каталога с найденными файлами программных лицензий, не использовались для поиска. На продолжение поиска не влиял факт успешности или не успешности получения лицензии из найденных файлов первого каталога.Повышение гибкости механизма программных лицензий. Исключение имеющихся проблем в случаях, когда доступные файлы программных лицензий расположены в нескольких доступных каталогах, например, серверная лицензия находится в каталоге, расположенном в порядке поиска раньше, чем каталог с многопользовательской лицензией.
Управляемая форма.
Во время работы управляемой формы не выполняется считывание данных для тех динамических списков, которые не видны на форме в настоящий момент.

При открытии формы значение реквизита таблицы управляемой формы ТекущаяСтрока, связанной с динамическим списком, будет равно значению Неопределено. Значение реквизита ТекущаяСтрока изменится в тот момент, когда эта таблица будет показана пользователю.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Во время работы управляемой формы выполнялось считывание данных для всех динамических списков, вне зависимости от того, отображались они на форме или нет.

+

Ускорено открытие форм, содержащих динамические списки на разных страницах управляемой формы.
Функциональные опции.
Управляемая форма.
Изменено поведение реквизитов и элементов формы, связанных с функциональными опциями:
  • Отключается реквизит формы ссылочного типа, если объект конфигурации, образующий тип, отключен функциональной опцией. Реквизит формы составного типа отключается в том случае, если функциональные опции отключают все составляющие типы.
  • Отключается реквизит формы типа <Вид>Объект (например, основной реквизит формы), если объект конфигурации, образующий тип, отключен функциональной опцией.
  • Таблица формы будет отключена, если она отображает данные реквизита, отключенного функциональной опцией.
  • В диалоге выбора типов (например, для полей ввода, связанных с реквизитами составного типа) отсутствуют типы, если объекты конфигурации, формирующие эти типы, отключены функциональной опцией. Информация о типах, отключенных функциональными опциями, кэшируется на стороне клиента и очищается через 20 минут или во время вызова метода ОбновитьИнтерфейс().

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Реквизиты и элементы формы вели себя следующим образом:
  • Реквизит формы ссылочного типа не отключался при отключении объекта конфигурации, образующего тип, с помощью функциональной опции.
  • Реквизит формы типа <Вид>Объект не отключался при отключении объекта конфигурации, образующего тип, с помощью функциональной опции.
  • Таблица формы не отключалась в том случае, если она отображала данные реквизита, отключенного функциональной опцией.
  • Диалог выбора типов содержал все типы, в том числе и те, которые отключены функциональными опциями.
Повышение уровня автоматического влияния функциональных опций на управляемые формы и унификация влияния функциональных опций на различные элементы приложения.
Функциональные опции.
Система компоновки данных.
Изменено влияние функциональных опций на систему компоновки данных:
  • Поле системы компоновки данных становится недоступным, если оно связано с реквизитами, типы которых отключены функциональными опциями.
  • Таблица запроса и реквизиты этой таблицы становятся недоступными, если функциональная опция отключает объект конфигурации, образующий эту таблицу.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Система компоновки данных не отключала доступность поля или таблицы запроса, связанного с данными, тип которых отключен функциональной опцией.Повышение уровня автоматического влияния функциональных опций на систему компоновки данных и унификация влияния функциональных опций на различные элементы приложения.
Функциональные опции.
Командный интерфейс.
Команда командного интерфейса становится недоступной в следующих случаях:
  • Реквизит, являющийся параметром команды, отключен функциональной опцией.
  • Тип параметра команды отключен функциональной опцией. Если тип параметра команды составной, то команда становится недоступной тогда, когда отключаются все типы параметра.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Доступность команды не менялась в том случае, если изменялась доступность реквизита, являющегося параметром команды или если тип параметра команды отключен функциональной опцией.Повышение уровня автоматического влияния функциональных опций на командный интерфейс приложения и унификация влияния функциональных опций на различные элементы приложения.
Система компоновки данных.
Табличный документ.
Управление фиксацией строк и столбцов выполняется с помощью параметров вывода ФиксацияСлева и ФиксацияСверху. Табличный документ не использует фиксацию, если область фиксации превышает отображаемую область.Система компоновки данных всегда использовала фиксацию строк и колонок в отчетах.

В табличном документе область фиксации могла быть больше, чем отображаемая область.

Повышено удобство работы с фиксацией в отчетах. Пользователь может отключать фиксацию в отчетах в тех случаях, когда она неудобна. Фиксация отключается автоматически в тех, случаях, когда она не позволяет просматривать табличный документ.
Управляемая форма.
Рекомендуется использовать методы УстановитьСоответствиеОбъектаИФормы() и ПолучитьСоответствиеОбъектаИФормы().

Методы УстановитьСоответствиеОбъектаИРеквизитаФормы() и ПолучитьСоответствиеОбъектаИРеквизитаФормы() являются устаревшими и поддерживаются для совместимости.

Методы УстановитьСоответствиеОбъектаИРеквизитаФормы() и ПолучитьСоответствиеОбъектаИРеквизитаФормы() не были объявлены устаревшими.Исключены из предлагаемых к использованию методы, вместо которых были реализованы новые, более функциональные, методы.
Менеджер блокировок.
При использовании конструктора объекта Диапазон генерируется исключение в том случае, если левая граница диапазона больше, чем правая.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Допускалось использование конструктора объекта Диапазон в тех случаях, когда левая граница диапазона больше, чем правая.Устранение неопределенности поведения менеджера управляемых блокировок. Исключение ошибок разработчика.
Управляемые блокировки.
При установке управляемой блокировки в файловом варианте информационной базы выполняется проверка правильности задания типов значений, находящихся в реквизите ИсточникДанных объекта ЭлементБлокировкиДанных.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При работе в файловом варианте информационной базы не выполнялась проверка правильности задания типов значений.Обеспечение единообразного поведения файлового и клиент-серверного варианта работы системы. Облегчение обнаружения ошибок прикладного решения.
Встроенный язык.
Попытка присвоения значения элементу фиксированной структуры вызывает исключение.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Попытка присвоения значения элементу фиксированной структуры не вызывала исключения и не приводила к присваиванию значения.Поведение фиксированной структуры приведено к поведению других фиксированных коллекций.
Веб-клиент.
Системные требования.
Прекращена поддержка веб-браузера Mozilla Firefox версий 3.0 и 3.5.Веб-браузер Mozilla Firefox версий 3.0 и 3.5 поддерживался системой.Повышение стабильности веб-клиента, связанное с исключением поддержки веб-браузеров, имеющих ошибки, поведение, отличающееся от стандартного, а также низкую распространенность.
Веб-клиент.
Системные требования.
Прекращена поддержка веб-браузера Microsoft Internet Explorer версии 6.0. Предупреждение, отображаемое при запуске веб-клиента в веб-браузере Microsoft Internet Explorer версии 6.0 изменено на предупреждение о неподдерживаемом веб-браузере.Поддерживался веб-браузер Microsoft Internet Explorer версии 6.0.Повышение стабильности веб-клиента, связанное с исключением поддержки веб-браузеров, имеющих ошибки, поведение, отличающееся от стандартного, а также низкую распространенность.
Табличный документ.
При передаче табличного документа между клиентом и сервером, сохраняются значения свойств ТолькоПросмотр и Защита.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При передаче табличного документа между клиентом и сервером, значения свойств ТолькоПросмотр и Защита устанавливались в значение Ложь.Обеспечивается единообразное сохранение свойств табличного документа при передаче между клиентом и сервером.
Форматированный документ.
Расширена объектная модель форматированного документа. Текст состоит из параграфов разного типа, входящих в коллекцию параграфов. Параграф состоит из коллекции элементов форматированного документа. Реализованы возможности манипулирования параграфами и элементами форматированного документа.

Методы ПолучитьЭлементы(), СформироватьЭлементы() позволяют получить массив элементов форматированного документа, расположенного между указанными закладками. Метод НайтиТекст() получает область форматированного документа (объект ОбластьФорматированногоДокумента), содержащую искомый текст.

Изменен тип параметра ТипЭлемента методов Добавить() и Вставить() объекта ФорматированныйДокумент.

Методы Добавить() и Вставить() объекта ФорматированныйДокумент возвращают добавленный/вставленный элемент.

Реализована возможность добавлять или вставлять картинку, указывая URL картинки в качестве текстового значения.

Не рекомендуется добавлять или вставлять картинку с помощью двоичных данных. Данная возможность поддерживается для совместимости. Рекомендуется для вставки картинки использовать объект Картинка.

Текст форматированного документа не был представлен в виде объектной модели.Возможность реализации различных алгоритмов обработки текстов, опирающихся на формальную структуру текста (параграфы, списки и т.д.).

Упрощение программного формирования текста.

Ограничение доступа к данным.
Если для объекта существует ограничение доступа к данным на право Изменение, и в этом ограничении участвуют условия на реквизиты табличных частей, то записать измененный объект можно только в том случае, если данные табличных частей удовлетворяют ограничениям доступа к данным как до, так и после изменения.

Наличие обращения к табличным частям из условий ограничений доступа к данным приводит к дополнительным временным затратам.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Если для объекта существовало ограничение доступа к данным на право Изменение, и в этом ограничении участвовали условия на реквизиты табличных частей, то состояние реквизитов табличных частей после изменения не контролировалось ограничением доступа к данным.Обеспечена одинаковая работы ограничений прав доступа на уровне записей в отношении данных объектов и их табличных частей.
Работа с СУБД.
При работе с СУБД Oracle Database для сложных запросах определенного вида изменено формирование запросов к СУБД и исключены случаи, приводящие к ошибкам СУБД. При большом количестве соединений может наблюдаться замедление выполнения запроса СУБД. Рекомендуется не использовать запросы с большим количеством соединений.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

При работе с СУБД Oracle Database были возможны ситуации, приводившие к ошибкам СУБД, при попытке исполнения сложных запросов определенного вида.Повышение стабильности работы при использовании СУБД Oracle Database.
Работа с Интернет.
Доступна работа с защищенными версиями протоколов SMTP/POP3.

Для объекта ИнтернетПочтовыйПрофиль реализованы свойства ИспользоватьSSLSMTP, ИспользоватьSSLPOP3, ТолькоЗащищеннаяАутентификацияIMAP, ТолькоЗащищеннаяАутентификацияSMTP, ТолькоЗащищеннаяАутентификацияPOP3.

Для протокола POP3 реализована поддержка метода ПолучитьКоличествоСообщений() объекта ИнтернетПочта.

Свойства АутентификацияSMTP и АутентификацияPOP3 объекта ИнтернетПочтовыйПрофиль, а также перечисления СпособSMTPАутентификации и СпособPOP3Аутентификации использовать не рекомендуется. Свойства АутентификацияSMTP, АутентификацияPOP3 и перечисления СпособSMTPАутентификации, CпособPOP3Аутентификации поддерживаются для совместимости. Рекомендуется использовать свойства ТолькоЗащищеннаяАутентификацияSMTP, ТолькоЗащищеннаяАутентификацияPOP3 объекта ИнтернетПочтовыйПрофиль.

Объект ИнтернетПочта не поддерживал работу с защищенными версиями протоколов SMTP/POP3.Возможность использовать защищенные версии протоколов SMTP/POP3.
Работа с Интернет.
Изменены значения по умолчанию для свойств, описывающие номера портов объекта ИнтернетПочтовыйПрофиль:
  • Для свойства ПортSMTP значение по умолчанию равно 0, что означает порт 25 для обычного соединения и порт 465 для защищенного соединения.
  • Для свойства ПортPOP3 значение по умолчанию равно 0, что означает порт 110 для обычного соединения и порт 995 для защищенного соединения.
  • Для свойства ПортIMAP значение по умолчанию равно 0, что означает порт 143 для обычного соединения и порт 993 для защищенного соединения.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Для объекта ИнтернетПочтовыйПрофиль использовались следующие значения по умолчанию для номеров портов:
  • Для свойства ПортSMTP использовалось значение 25.
  • Для свойства ПортPOP3 использовалось значение 110.
  • Для свойства ПортIMAP использовалось значение 143.
Упрощена установка портов для работы объекта ИнтернетПочтовыйПрофиль. В большинстве случаев достаточно указания портов по умолчанию.
Управляемая форма.
Изменено поведение выпадающего списка для полей формы, отображающих данные ссылочного типа, перечисления или системные перечисления. Изменен внешний вид и функционирование выпадающего списка. Реализована история выбранных значений, которая хранится в системном хранилище настроек (имя настройки - ИсторияВыбора).

При пользовательском формировании списка выбора, допускается использовать значение типа ФорматированнаяСтрока в качестве представления значения.

В режиме совместимости с версией 8.2.16 поведение не изменилось.

Выпадающий список имел другой внешний вид и поведение. Список выбора не отображался в выпадающем списке.Повышение удобства работы с полем ввода, отображающим данные ссылочного типа, перечисления или системные перечисления.
Работа в ОС Linux.
Утилита конфигурирования для работы в ОС Linux называется config_system.Утилита конфигурирования называлась config_server.Более полное отражение выполняемых утилитой функций - проверка окружения выполняется не только для сервере, но и для клиентского приложения.
Администрирование.
Конфигурационный файл location.cfg позволяет указать «1С:Предприятию», где выполнять поиск служебных данных.

Во время установки версии 8.3, выполняется поиск каталогов с данными (профили пользователей, конфигурационные файлы, файлы программных лицензий и т.д.) от версии 8.2 в каталогах, доступных данному пользователю. Если каталоги с данными от версии 8.2 найдены, то в каталогах с данными версии 8.3 формируется файл location.cfg с указанием на каталоги с данными версии 8.2. Таким образом, установка новой версии не ведет к необходимости полного переноса всех данных и настроек из каталогов версии 8.2 в каталоги версии 8.3.

Данная возможность не предоставлялась.После установки версии 8.3 будет возможно использовать единые настройки для версии 8.2.16 и 8.3.
Программное лицензирование.
Если активация программной лицензии выполняется «для всех пользователей» или через сервер «1С:Предприятия», то для сохранения файлов программных лицензий используется каталог:
  • Для ОС Windows: %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses - для ОС Windows Vista и старше);
  • Для ОС Linux: /var/1C/licenses.

Каталог (в зависимости от используемой ОС) создается во время установки «1С:Предприятия». Права на созданный каталог назначаются в зависимости от используемой ОС:

  • Для ОС Windows права чтения и записи на создаваемый каталог назначаются пользователю, от имени которого будет выполняться служба сервера. Если служба не устанавливается - права на каталог не изменяются.
  • Для ОС Linux создается группа пользователей grp1cv8, в которую должны входить все пользователи, от лица которых работает демон сервера «1С:Предприятия». При установке сервера в эту группу включается пользователь usr1cv8, от имени которого работает демон сервера. Для создаваемого каталога назначаются следующие права: владелец - root, права - чтение и запись; группа владельца - grp1cv8, права - чтение и запись; для остальных пользователей назначаются права только для чтения.

Получение клиентской лицензии «для всех пользователей» может выполнять только пользователь с административными правами.

Для сохранения файлов программных лицензий использовался каталог:
  • Для ОС Windows: %ALLUSERSPROFILE%\Application Data\1C\1Cv82\Conf (%ALLUSERSPROFILE%\1C\1Cv82\Conf для ОС Windows Vista и старше);
  • Для ОС Linux: ~/.1cv82/conf.

На ОС Windows каталог использовался при активации программной лицензии «для всех пользователей», а на ОС Linux - при активации программной лицензии через сервер «1С:Предприятия».

Упрощается администрирование файлов программных лицензий. «1С:Предприятие» версий 8.2.16 и 8.3 могут использовать один и тот же набор лицензий в том случае, если активация программных лицензий выполняется «для всех пользователей» или через сервер «1С:Предприятия».
Кластер серверов.
Средства администрирования.
Изменена схема администрирования кластера серверов. Управление процессами кластера и распределение между ними функциональных возможностей выполняется в автоматическом режиме и более недоступно для ручного управления. Создавая специальные правила назначения сервиса кластера или соединения на рабочий сервер, можно влиять на автоматическое распределение. Кластер серверов сохраняет свою работоспособность до тех пор, пока работоспособен хотя бы один рабочий сервер, отмеченный как Центральный сервер. Работоспособность кластера серверов определяет параметр Уровень отказоустойчивости, который определяет максимальное количество рабочих серверов, одновременный выход которых из строя не приведет к аварийному завершению работы пользователей.

Кластер серверов отображается в консоли кластера своим именем (свойство Имя кластера), а не портом.

Средства программного администрирования кластера сервером версии 8.3 несовместимы со средствами программного администрирования кластера серверов версии 8.2.

Для объекта IClusterInfo реализовано свойство SessionFaultToleranceLevel.

Для объекта IWorkingServerInfo реализованы свойства MainServer, ClusterMainPort, DedicatedManagers, InfoBasesPerWorkingProcessLimit, ConnectionsPerWorkingProcessLimit, WorkingProcessMemoryLimit.

Реализован объект IAssignmentRule, позволяющий управлять функциональностью рабочих серверов.

Список требований назначения функциональности доступен с помощью объекта IServerAgentConnection и консоли кластера.

Для объекта IServerAgentConnection реализованы методы RegAssignmentRule(), UnregAssignmentRule(), GetAssignmentRules(), CreateAssignmentRule(), ApplyAssignmentRules().

Свойства объектов IWorkingProcessInfo, IClusterManagerInfo, IClusterServiceInfo доступны только для чтения.

Для объекта IServerAgentConnection удалены методы: CreateWorkingProcessInfo(), RegWorkingProcess(), UnregWorkingProcess(), StartWorkingProcess(), StopWorkingProcess(), SetWorkingProcessUsage(), SetClusterMultiProcess(), SetWorkingProcessCapacity(), SetClusterDescription(), CreateClusterManagerInfo(), RegClusterManager(), UnregClusterManager(), RegClusterService(), UnregClusterService(), CreateStandbyClusterItem(), RegStandbyCluster(), UnregStandbyCluster(), GetStandbyClusterList().

Удален объект IStandbyClusterItem.

Удалено свойство SyncPort для следующих объектов: IWorkingProcessInfo, IClusterManagerInfo, IWorkingServerInfo, IClusterInfo.

Управление рабочими процессами кластера серверов и распределение между ними функциональных возможностей было доступно только в ручном режиме. Кластер серверов отображался в консоли кластера в виде номера используемого порта. Отсутствовала возможность указания уровня отказоустойчивости.Управление рабочими процессами выполняется автоматически, что качественно улучшает процесс распределения нагрузки в рамках кластера серверов. При этом администратор (с помощью специальных правил) имеет возможность указывать на каком рабочем сервере будут выполняться конкретные сервисы кластера или соединения. Например, имеется возможность вынести сервис управления лицензиями на отдельный рабочий сервер с минимальными изменениями в составе оборудования, или определенные фоновые задания выполнять на рабочем сервере, функционирующим под управлением ОС Windows.
Кластер серверов.
После установки сервера на ОС Linux, запуск установленного сервера автоматически не выполняется.После установки сервера на ОС Linux выполнялся автоматический запуск установленного сервера.Не выполняется запуск сервера с не полностью настроенным окружением. Для настройки окружения необходимо запустить утилиту config_system и только после этого запускать сервер.

Оглавление

Переименования

Что переименованоСтарое наименованиеНовое наименование
Переименованы группы колонок табличного поля пользовательских настроек системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок1.
  • <Имя табличного поля>ГруппаКолонокНастройки;
  • <Имя табличного поля>ГруппаКолонокЗначения.
Переименована группа колонок табличного поля настроек системы компоновки данных. В режиме совместимости с версией 8.2.16 имена не изменились.
  • <Имя табличного поля>ГруппаКолонок.

  • <Имя табличного поля>ГруппаКолонокСтруктура.
Переименованы группы колонок табличного поля параметров данных системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок1;
  • <Имя табличного поля>ГруппаКолонок2;
  • <Имя табличного поля>ГруппаКолонок3.
  • <Имя табличного поля>ГруппаКолонокПараметрИЗначениеПериода;
  • <Имя табличного поля>ГруппаКолонокПараметр;
  • <Имя табличного поля>ГруппаКолонокЗначениеПериода;
  • <Имя табличного поля>ГруппаКолонокЗначениеПараметра.
Переименована группа колонок табличного поля доступных полей системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок.
  • <Имя табличного поля>ГруппаКолонокДоступноеПоле.
Переименованы группы колонок табличного поля полей группировки системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок1;
  • <Имя табличного поля>ГруппаКолонок2;
  • <Имя табличного поля>ГруппаКолонок3;
  • <Имя табличного поля>ГруппаКолонок4;
  • <Имя табличного поля>ГруппаКолонок5.
  • <Имя табличного поля>ГруппаКолонокПолеГруппировки;
  • <Имя табличного поля>ГруппаКолонокПолеИТип;
  • <Имя табличного поля>ГруппаКолонокПериод;
  • <Имя табличного поля>ГруппаКолонокПоле;
  • <Имя табличного поля>ГруппаКолонокНачалоПериода;
  • <Имя табличного поля>ГруппаКолонокКонецПериода.
Переименованы группы колонок табличного поля выбранных полей системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок1;
  • <Имя табличного поля>ГруппаКолонок3;
  • <Имя табличного поля>ГруппаКолонок2.
  • <Имя табличного поля>ГруппаКолонокВыбранноеПоле;
  • <Имя табличного поля>ГруппаКолонокЗаголовокИРасположение;
  • <Имя табличного поля>ГруппаКолонокЗаголовок;
  • <Имя табличного поля>ГруппаКолонокПоле.
Переименованы группы колонок табличного поля отбора системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок2;
  • <Имя табличного поля>ГруппаКолонок3;
  • <Имя табличного поля>ГруппаКолонок4;
  • <Имя табличного поля>ГруппаКолонок1.
  • <Имя табличного поля>ГруппаКолонокОтбор;
  • <Имя табличного поля>ГруппаКолонокОсновныеЭлементыОтбора;
  • <Имя табличного поля>ГруппаКолонокЛевоеЗначение;
  • <Имя табличного поля>ГруппаКолонокПравоеЗначение;
  • <Имя табличного поля>ГруппаКолонокПрименение.
Переименована группа колонок табличного поля порядка системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок.
  • <Имя табличного поля>ГруппаКолонокПоле.

Переименованы группы колонок табличного поля параметров вывода системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок1;
  • <Имя табличного поля>ГруппаКолонок2;
  • <Имя табличного поля>ГруппаКолонок3.
  • <Имя табличного поля>ГруппаКолонокПараметрИЗначениеПериода;
  • <Имя табличного поля>ГруппаКолонокПараметр;
  • <Имя табличного поля>ГруппаКолонокЗначениеПериода;
  • <Имя табличного поля>ГруппаКолонокПараметра.
Переименована группа колонок табличного поля вариантов пользовательского поля выбора компоновки данных системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок.
  • <Имя табличного поля>ГруппаКолонокЗначение.
Переименована группа колонок табличного поля оформляемых полей компоновки данных системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок.
  • <Имя табличного поля>ГруппаКолонокПоле.
Переименована группа колонок табличного поля оформляемых полос измерительной диаграммы системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок.
  • <Имя табличного поля>ГруппаКолонокЦветФона.
Переименованы группы колонок табличного поля условий отбора системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • <Имя табличного поля>ГруппаКолонок;
  • <Имя табличного поля>ГруппаКолонок1.
  • <Имя табличного поля>ГруппаКолонокЗначениеИПериод;
  • <Имя табличного поля>ГруппаКолонокПериод.
Переименованы элементы формы варианта отчета системы компоновки данных.

В режиме совместимости с версией 8.2.16 имена не изменились.

  • ПереходКВыбраннымПолямОтчета1;
  • ПереходКОтборуОтчета1;
  • ПереходКПорядкуОтчета1;
  • ПереходКУсловномуОформлениюОтчета1;
  • ПереходКПараметрамВыводаОтчета1.
  • ПереходКВыбраннымПолямОтчетаОтНедоступныхВыбранныхПолей;
  • ПереходКОтборуОтчетаОтНедоступногоОтбора;
  • ПереходКПорядкуОтчетаОтНедоступногоПорядка;
  • ПереходКУсловномуОформлениюОтчетаОтНедоступногоУсловногоОформления;
  • ПереходКПараметрамВыводаОтчетаОтНедоступныхПараметровВывода.
Изменено представление команды НастройкиОтчета формы отчета.
  • Настройка ....
  • Настройки ....
Изменено представление команды ЗагрузитьНастройкиОтчета формы отчета.
  • Выбрать настройку ....
  • Выбрать настройки ....
Изменено представление команды СохранитьНастройкиОтчета формы отчета.
  • Сохранить настройку ....
  • Сохранить настройки ....
Изменено представление команды СтандартныеНастройки формы варианта отчета.
  • Стандартная настройка.
  • Стандартные настройки.
Изменен заголовок поля с именем сохраняемых настроек в диалоге сохранения настроек.
  • Имя сохраняемой настройки.
  • Имя сохраняемых настроек.

Оглавление

Переход с предыдущей версии на версию 8.3.1

Оглавление

\ No newline at end of file diff --git a/distr/installAsRoot b/distr/installAsRoot new file mode 100755 index 0000000..7662e1f Binary files /dev/null and b/distr/installAsRoot differ diff --git a/distr/license/1c-enterprise-installer-1.17.1+3-linux-x86_64.e1c.car b/distr/license/1c-enterprise-installer-1.17.1+3-linux-x86_64.e1c.car new file mode 100644 index 0000000..8018179 Binary files /dev/null and b/distr/license/1c-enterprise-installer-1.17.1+3-linux-x86_64.e1c.car differ diff --git a/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.car b/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.car new file mode 100644 index 0000000..5478691 Binary files /dev/null and b/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.car differ diff --git a/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.dar b/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.dar new file mode 100644 index 0000000..7fdfff7 Binary files /dev/null and b/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.dar differ diff --git a/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.par b/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.par new file mode 100644 index 0000000..d468724 Binary files /dev/null and b/distr/license/1c-enterprise-license-tools-0.15.2+8-linux-x86_64.e1c.par differ diff --git a/distr/license/1c-enterprise-ring-0.20.0+4-linux-x86_64.e1c.car b/distr/license/1c-enterprise-ring-0.20.0+4-linux-x86_64.e1c.car new file mode 100644 index 0000000..8691964 Binary files /dev/null and b/distr/license/1c-enterprise-ring-0.20.0+4-linux-x86_64.e1c.car differ diff --git a/distr/license/1ce-installer b/distr/license/1ce-installer new file mode 100755 index 0000000..1f69b59 Binary files /dev/null and b/distr/license/1ce-installer differ diff --git a/distr/license/1ce-installer-cli b/distr/license/1ce-installer-cli new file mode 100755 index 0000000..529c7c5 Binary files /dev/null and b/distr/license/1ce-installer-cli differ diff --git a/distr/license/lib/activation-1.1.1.jar b/distr/license/lib/activation-1.1.1.jar new file mode 100644 index 0000000..1b703ab Binary files /dev/null and b/distr/license/lib/activation-1.1.1.jar differ diff --git a/distr/license/lib/animal-sniffer-annotations-1.18.jar b/distr/license/lib/animal-sniffer-annotations-1.18.jar new file mode 100644 index 0000000..3925273 Binary files /dev/null and b/distr/license/lib/animal-sniffer-annotations-1.18.jar differ diff --git a/distr/license/lib/aopalliance-1.0.jar b/distr/license/lib/aopalliance-1.0.jar new file mode 100644 index 0000000..578b1a0 Binary files /dev/null and b/distr/license/lib/aopalliance-1.0.jar differ diff --git a/distr/license/lib/checker-qual-2.8.1.jar b/distr/license/lib/checker-qual-2.8.1.jar new file mode 100644 index 0000000..09269be Binary files /dev/null and b/distr/license/lib/checker-qual-2.8.1.jar differ diff --git a/distr/license/lib/com._1c.chassis.app.instance.operations-1.17.1-3.jar b/distr/license/lib/com._1c.chassis.app.instance.operations-1.17.1-3.jar new file mode 100644 index 0000000..2ed0217 Binary files /dev/null and b/distr/license/lib/com._1c.chassis.app.instance.operations-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.chassis.gears-0.14.5-13.jar b/distr/license/lib/com._1c.chassis.gears-0.14.5-13.jar new file mode 100644 index 0000000..d256d00 Binary files /dev/null and b/distr/license/lib/com._1c.chassis.gears-0.14.5-13.jar differ diff --git a/distr/license/lib/com._1c.chassis.gears.guice-0.14.5-13.jar b/distr/license/lib/com._1c.chassis.gears.guice-0.14.5-13.jar new file mode 100644 index 0000000..37785ad Binary files /dev/null and b/distr/license/lib/com._1c.chassis.gears.guice-0.14.5-13.jar differ diff --git a/distr/license/lib/com._1c.chassis.os.desktop-0.17.0-17.jar b/distr/license/lib/com._1c.chassis.os.desktop-0.17.0-17.jar new file mode 100644 index 0000000..5743d67 Binary files /dev/null and b/distr/license/lib/com._1c.chassis.os.desktop-0.17.0-17.jar differ diff --git a/distr/license/lib/com._1c.chassis.os.hw-0.11.0-99.jar b/distr/license/lib/com._1c.chassis.os.hw-0.11.0-99.jar new file mode 100644 index 0000000..1495ae7 Binary files /dev/null and b/distr/license/lib/com._1c.chassis.os.hw-0.11.0-99.jar differ diff --git a/distr/license/lib/com._1c.chassis.os.path-0.11.0-82.jar b/distr/license/lib/com._1c.chassis.os.path-0.11.0-82.jar new file mode 100644 index 0000000..e45b049 Binary files /dev/null and b/distr/license/lib/com._1c.chassis.os.path-0.11.0-82.jar differ diff --git a/distr/license/lib/com._1c.chassis.os.user-0.10.3-1.jar b/distr/license/lib/com._1c.chassis.os.user-0.10.3-1.jar new file mode 100644 index 0000000..83bd014 Binary files /dev/null and b/distr/license/lib/com._1c.chassis.os.user-0.10.3-1.jar differ diff --git a/distr/license/lib/com._1c.installer.app.params-1.17.1-3.jar b/distr/license/lib/com._1c.installer.app.params-1.17.1-3.jar new file mode 100644 index 0000000..d9fcf8a Binary files /dev/null and b/distr/license/lib/com._1c.installer.app.params-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.app.restart-1.17.1-3.jar b/distr/license/lib/com._1c.installer.app.restart-1.17.1-3.jar new file mode 100644 index 0000000..9ff83dc Binary files /dev/null and b/distr/license/lib/com._1c.installer.app.restart-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.chassis.app.support-1.17.1-3.jar b/distr/license/lib/com._1c.installer.chassis.app.support-1.17.1-3.jar new file mode 100644 index 0000000..6b7ae5f Binary files /dev/null and b/distr/license/lib/com._1c.installer.chassis.app.support-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.cli-1.17.1-3.jar b/distr/license/lib/com._1c.installer.cli-1.17.1-3.jar new file mode 100644 index 0000000..9d50110 Binary files /dev/null and b/distr/license/lib/com._1c.installer.cli-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.distro-1.17.1-3.jar b/distr/license/lib/com._1c.installer.distro-1.17.1-3.jar new file mode 100644 index 0000000..a396284 Binary files /dev/null and b/distr/license/lib/com._1c.installer.distro-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.exceptions-1.17.1-3.jar b/distr/license/lib/com._1c.installer.exceptions-1.17.1-3.jar new file mode 100644 index 0000000..ecec78c Binary files /dev/null and b/distr/license/lib/com._1c.installer.exceptions-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.glob-1.17.1-3.jar b/distr/license/lib/com._1c.installer.glob-1.17.1-3.jar new file mode 100644 index 0000000..d5ef516 Binary files /dev/null and b/distr/license/lib/com._1c.installer.glob-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.info-1.17.1-3.jar b/distr/license/lib/com._1c.installer.info-1.17.1-3.jar new file mode 100644 index 0000000..ac76b1d Binary files /dev/null and b/distr/license/lib/com._1c.installer.info-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.logging-1.17.1-3.jar b/distr/license/lib/com._1c.installer.logging-1.17.1-3.jar new file mode 100644 index 0000000..1a4ae7f Binary files /dev/null and b/distr/license/lib/com._1c.installer.logging-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.logic-1.17.1-3.jar b/distr/license/lib/com._1c.installer.logic-1.17.1-3.jar new file mode 100644 index 0000000..55d36f4 Binary files /dev/null and b/distr/license/lib/com._1c.installer.logic-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.model.distro-1.17.1-3.jar b/distr/license/lib/com._1c.installer.model.distro-1.17.1-3.jar new file mode 100644 index 0000000..9ef2ba5 Binary files /dev/null and b/distr/license/lib/com._1c.installer.model.distro-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.model.installed-1.17.1-3.jar b/distr/license/lib/com._1c.installer.model.installed-1.17.1-3.jar new file mode 100644 index 0000000..28fcdf2 Binary files /dev/null and b/distr/license/lib/com._1c.installer.model.installed-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.model.installer-1.17.1-3.jar b/distr/license/lib/com._1c.installer.model.installer-1.17.1-3.jar new file mode 100644 index 0000000..58303d4 Binary files /dev/null and b/distr/license/lib/com._1c.installer.model.installer-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.model.manifest-1.17.1-3.jar b/distr/license/lib/com._1c.installer.model.manifest-1.17.1-3.jar new file mode 100644 index 0000000..9337324 Binary files /dev/null and b/distr/license/lib/com._1c.installer.model.manifest-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.os-1.17.1-3.jar b/distr/license/lib/com._1c.installer.os-1.17.1-3.jar new file mode 100644 index 0000000..596a361 Binary files /dev/null and b/distr/license/lib/com._1c.installer.os-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.process-1.17.1-3.jar b/distr/license/lib/com._1c.installer.process-1.17.1-3.jar new file mode 100644 index 0000000..a3fbcc6 Binary files /dev/null and b/distr/license/lib/com._1c.installer.process-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.ring.support-1.17.1-3.jar b/distr/license/lib/com._1c.installer.ring.support-1.17.1-3.jar new file mode 100644 index 0000000..83d5ae9 Binary files /dev/null and b/distr/license/lib/com._1c.installer.ring.support-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.sign-1.17.1-3.jar b/distr/license/lib/com._1c.installer.sign-1.17.1-3.jar new file mode 100644 index 0000000..8c9e41e Binary files /dev/null and b/distr/license/lib/com._1c.installer.sign-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.installer.ui-1.17.1-3.jar b/distr/license/lib/com._1c.installer.ui-1.17.1-3.jar new file mode 100644 index 0000000..541f906 Binary files /dev/null and b/distr/license/lib/com._1c.installer.ui-1.17.1-3.jar differ diff --git a/distr/license/lib/com._1c.packaging.inventory-1.10.3-12.jar b/distr/license/lib/com._1c.packaging.inventory-1.10.3-12.jar new file mode 100644 index 0000000..527a741 Binary files /dev/null and b/distr/license/lib/com._1c.packaging.inventory-1.10.3-12.jar differ diff --git a/distr/license/lib/com._1c.packaging.model.shared-1.3.0-1.jar b/distr/license/lib/com._1c.packaging.model.shared-1.3.0-1.jar new file mode 100644 index 0000000..cbf9eba Binary files /dev/null and b/distr/license/lib/com._1c.packaging.model.shared-1.3.0-1.jar differ diff --git a/distr/license/lib/com._1c.ring.framework-0.10.9-1.jar b/distr/license/lib/com._1c.ring.framework-0.10.9-1.jar new file mode 100644 index 0000000..88852e1 Binary files /dev/null and b/distr/license/lib/com._1c.ring.framework-0.10.9-1.jar differ diff --git a/distr/license/lib/com._1c.ring.framework.impl.registry-0.10.9-1.jar b/distr/license/lib/com._1c.ring.framework.impl.registry-0.10.9-1.jar new file mode 100644 index 0000000..ac40c24 Binary files /dev/null and b/distr/license/lib/com._1c.ring.framework.impl.registry-0.10.9-1.jar differ diff --git a/distr/license/lib/com.e1c.annotations-1.2.1-java7.jar b/distr/license/lib/com.e1c.annotations-1.2.1-java7.jar new file mode 100644 index 0000000..b179b78 Binary files /dev/null and b/distr/license/lib/com.e1c.annotations-1.2.1-java7.jar differ diff --git a/distr/license/lib/com.e1c.g5.i18n-3.2.0-2.jar b/distr/license/lib/com.e1c.g5.i18n-3.2.0-2.jar new file mode 100644 index 0000000..41bf119 Binary files /dev/null and b/distr/license/lib/com.e1c.g5.i18n-3.2.0-2.jar differ diff --git a/distr/license/lib/com.e1c.jcip.annotations-1.2.1.jar b/distr/license/lib/com.e1c.jcip.annotations-1.2.1.jar new file mode 100644 index 0000000..e042502 Binary files /dev/null and b/distr/license/lib/com.e1c.jcip.annotations-1.2.1.jar differ diff --git a/distr/license/lib/commons-lang3-3.7.jar b/distr/license/lib/commons-lang3-3.7.jar new file mode 100644 index 0000000..f37ded6 Binary files /dev/null and b/distr/license/lib/commons-lang3-3.7.jar differ diff --git a/distr/license/lib/commons-text-1.3.jar b/distr/license/lib/commons-text-1.3.jar new file mode 100644 index 0000000..0ec9e48 Binary files /dev/null and b/distr/license/lib/commons-text-1.3.jar differ diff --git a/distr/license/lib/error_prone_annotations-2.3.2.jar b/distr/license/lib/error_prone_annotations-2.3.2.jar new file mode 100644 index 0000000..bc2584d Binary files /dev/null and b/distr/license/lib/error_prone_annotations-2.3.2.jar differ diff --git a/distr/license/lib/failureaccess-1.0.1.jar b/distr/license/lib/failureaccess-1.0.1.jar new file mode 100644 index 0000000..9b56dc7 Binary files /dev/null and b/distr/license/lib/failureaccess-1.0.1.jar differ diff --git a/distr/license/lib/guava-28.1-jre.jar b/distr/license/lib/guava-28.1-jre.jar new file mode 100644 index 0000000..081cd11 Binary files /dev/null and b/distr/license/lib/guava-28.1-jre.jar differ diff --git a/distr/license/lib/guice-4.2.2.jar b/distr/license/lib/guice-4.2.2.jar new file mode 100644 index 0000000..1424592 Binary files /dev/null and b/distr/license/lib/guice-4.2.2.jar differ diff --git a/distr/license/lib/j2objc-annotations-1.3.jar b/distr/license/lib/j2objc-annotations-1.3.jar new file mode 100644 index 0000000..a429c72 Binary files /dev/null and b/distr/license/lib/j2objc-annotations-1.3.jar differ diff --git a/distr/license/lib/javax.activation-api-1.2.0.jar b/distr/license/lib/javax.activation-api-1.2.0.jar new file mode 100644 index 0000000..986c365 Binary files /dev/null and b/distr/license/lib/javax.activation-api-1.2.0.jar differ diff --git a/distr/license/lib/javax.inject-1.jar b/distr/license/lib/javax.inject-1.jar new file mode 100644 index 0000000..b2a9d0b Binary files /dev/null and b/distr/license/lib/javax.inject-1.jar differ diff --git a/distr/license/lib/javax.mail-1.6.0.jar b/distr/license/lib/javax.mail-1.6.0.jar new file mode 100644 index 0000000..408f3d2 Binary files /dev/null and b/distr/license/lib/javax.mail-1.6.0.jar differ diff --git a/distr/license/lib/jaxb-api-2.3.1.jar b/distr/license/lib/jaxb-api-2.3.1.jar new file mode 100644 index 0000000..4565865 Binary files /dev/null and b/distr/license/lib/jaxb-api-2.3.1.jar differ diff --git a/distr/license/lib/jsr305-3.0.2.jar b/distr/license/lib/jsr305-3.0.2.jar new file mode 100644 index 0000000..59222d9 Binary files /dev/null and b/distr/license/lib/jsr305-3.0.2.jar differ diff --git a/distr/license/lib/jul-to-slf4j-1.8.0-beta4.jar b/distr/license/lib/jul-to-slf4j-1.8.0-beta4.jar new file mode 100644 index 0000000..ef475e0 Binary files /dev/null and b/distr/license/lib/jul-to-slf4j-1.8.0-beta4.jar differ diff --git a/distr/license/lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar b/distr/license/lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar new file mode 100644 index 0000000..45832c0 Binary files /dev/null and b/distr/license/lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar differ diff --git a/distr/license/lib/logback-classic-1.3.0-alpha4.jar b/distr/license/lib/logback-classic-1.3.0-alpha4.jar new file mode 100644 index 0000000..9d53620 Binary files /dev/null and b/distr/license/lib/logback-classic-1.3.0-alpha4.jar differ diff --git a/distr/license/lib/logback-core-1.3.0-alpha4.jar b/distr/license/lib/logback-core-1.3.0-alpha4.jar new file mode 100644 index 0000000..256f3de Binary files /dev/null and b/distr/license/lib/logback-core-1.3.0-alpha4.jar differ diff --git a/distr/license/lib/org.eclipse.persistence.asm-2.7.4.jar b/distr/license/lib/org.eclipse.persistence.asm-2.7.4.jar new file mode 100644 index 0000000..f31d43b Binary files /dev/null and b/distr/license/lib/org.eclipse.persistence.asm-2.7.4.jar differ diff --git a/distr/license/lib/org.eclipse.persistence.core-2.7.4.jar b/distr/license/lib/org.eclipse.persistence.core-2.7.4.jar new file mode 100644 index 0000000..3094d09 Binary files /dev/null and b/distr/license/lib/org.eclipse.persistence.core-2.7.4.jar differ diff --git a/distr/license/lib/org.eclipse.persistence.moxy-2.7.4.jar b/distr/license/lib/org.eclipse.persistence.moxy-2.7.4.jar new file mode 100644 index 0000000..6e65928 Binary files /dev/null and b/distr/license/lib/org.eclipse.persistence.moxy-2.7.4.jar differ diff --git a/distr/license/lib/slf4j-api-1.8.0-beta4.jar b/distr/license/lib/slf4j-api-1.8.0-beta4.jar new file mode 100644 index 0000000..c6458a7 Binary files /dev/null and b/distr/license/lib/slf4j-api-1.8.0-beta4.jar differ diff --git a/distr/license/lib/snakeyaml-1.25.jar b/distr/license/lib/snakeyaml-1.25.jar new file mode 100644 index 0000000..0004985 Binary files /dev/null and b/distr/license/lib/snakeyaml-1.25.jar differ diff --git a/distr/license/lib/x86_64/installer/libinstaller.so b/distr/license/lib/x86_64/installer/libinstaller.so new file mode 100644 index 0000000..7f768e8 Binary files /dev/null and b/distr/license/lib/x86_64/installer/libinstaller.so differ diff --git a/distr/license/lib/x86_64/inventory/libinventory.so b/distr/license/lib/x86_64/inventory/libinventory.so new file mode 100644 index 0000000..d3514ae Binary files /dev/null and b/distr/license/lib/x86_64/inventory/libinventory.so differ diff --git a/distr/licenses/1CEnterprise_en.htm b/distr/licenses/1CEnterprise_en.htm new file mode 100644 index 0000000..c5d052a --- /dev/null +++ b/distr/licenses/1CEnterprise_en.htm @@ -0,0 +1,222 @@ + + + + +License agreement for 1C:Enterprise 8.3 + + + + + + + + + + + + + + + + + + +
+

License agreement for 1C:Enterprise 8.3

+

This License Agreement is a document conditioning the terms of use of the above-mentioned 1C:Enterprise 8 SOFTWARE PRODUCT by the entity (hereinafter referred to as "Licensee"), either private or legal, in possession of a copy of the SOFTWARE PRODUCT that was lawfully produced and registered by 1C-Soft LLC.

+

SOFTWARE PRODUCT is a 1C:Enterprise 8 bundle containing 1C:Enterprise 8 installation package, at least one application or configuration (except for ad hoc 1C:Enterprise 8 deliveries), and the License Agreement regulating the terms of use of the SOFTWARE PRODUCT.

+

All exclusive proprietary rights for the SOFTWARE PRODUCT (the actual software recorded on digital data media, software updates and add-ons provided separately, and any accompanying materials in a hard-copy or electronic form) are owned by 1C-Soft LLC (hereinafter referred to as "the Copyright Owner") registered in Moscow, Russian Federation. By installing the SOFTWARE PRODUCT and saving it to a computer memory, the Licensee acknowledges being bound by this License Agreement.

+

According to this License Agreement, the Licensee is granted selected non-exclusive rights as described below. The Licensee is to keep the License Agreement included into the SOFTWARE PRODUCT bundle as a document confirming their right to use the SOFTWARE PRODUCT granted by the Copyright Owner. The Copyright Owner reserves the right to unilaterally change the technical support terms from time to time, including the terms for providing the Licensee with updates to the SOFTWARE PRODUCT, by publishing a corresponding information message on the Copyright Owner's website.

+
+
+

RIGHTS AND LIMITATIONS

+
    +
  1. +

    The Licensee is entitled to install and use the SOFTWARE PRODUCT in accordance with the software documentation, on one computer at a time. The Licensee is entitled to use the SOFTWARE PRODUCT on multiple computers only if the Licensee holds the 1C:Enterprise 8 Client License that allows to use the SOFTWARE PRODUCT on multiple computers and in accordance with the workstation licensing terms stated below. The Licensee is entitled to use the SOFTWARE PRODUCT in a client-server mode only if the Licensee holds the 1C:Enterprise 8 Server License and only in accordance with the 1C:Enterprise 8 server licensing terms stated below. The Licensee is entitled to use the applications (configurations) not included into the SOFTWARE PRODUCT bundle only if the Licensee holds a separate License for each application (configuration) used.

    +
    2. +
  2. +

    If the Licensee is using the software products or the computer devices designed to reduce the number of the users who have direct access to 1C:Enterprise 8 (sometimes referred to as "multiplexing" software or hardware), this does not reduce the number of the required 1C:Enterprise 8 Client Licenses. The required number of the 1C:Enterprise 8 Client Licenses must be equal to the number of the individual entry points to the multiplexing software or hardware in use.

    +
    3. +
  3. +

    According to this License Agreement, the transfer of rights for the SOFTWARE PRODUCT to a third party is only allowed if the complete SOFTWARE PRODUCT bundle (including this License Agreement) the Licensee holds the right for is transferred. In this case, the original Licensee shall uninstall all the copies of the SOFTWARE PRODUCT from the computer it was used on and notify the Copyright Owner about the transfer of rights.

    +
    4. +
  4. +

    The Licensee undertakes to prevent any violations of the Copyright Owner's exclusive rights for the SOFTWARE PRODUCT, in particular not to commit the following acts and to prevent third parties from committing the following acts without specific written permission of the Copyright Owner:

    +
    5. +
      +
    1. +

      to distribute the SOFTWARE PRODUCT or its components;

      +
      2. +
    2. +

      to modify the SOFTWARE PRODUCT's program code, the database contents, and other datasets in which the system stores information, except for the modifications made with the SOFTWARE PRODUCT's built-in tools that are described in the accompanying documentation;

      +
      3. +
    3. +

      to modify the behavior of the 1C:Enterprise 8 platform by any means, with the exception of the SOFTWARE PRODUCT's built-in tools that are described in the accompanying documentation;

      +
      4. +
    4. +

      to access the SOFTWARE PRODUCT's infobase and develop derivative systems based on the SOFTWARE PRODUCT using means and technological solutions not described in the accompanying documentation;

      +
      5. +
    5. +

      to take actions that disable or reduce the efficiency of technical copyright protection means introduced by the Copyright Owner, including the use of multiplexing software or hardware that change the algorithm of the SOFTWARE PRODUCT's software or hardware protection system; or to use the SOFTWARE PRODUCT with the copyright protection disabled or modified without the permission of the Copyright Owner;

      +
      6. +
    6. +

      to recover the source code, decompile, and/or disassemble the system's software components, except for the cases when such activity is explicitly permitted by the legislation of the country in which the product is used and only to the extent to which such activity is explicitly permitted by the legislation of the country in which the product is used.

      +
      7. +
    + +

  5. This License Agreement is valid for the entire lifetime of the SOFTWARE PRODUCT possessed by the Licensee and/or for the period the Licensee possesses copies of the SOFTWARE PRODUCT.

    6. +

  6. The SOFTWARE PRODUCT and its accompanying documentation are provided to the Licensee “AS IS” - in accordance with the principle generally accepted in international practice (AS IS), according to which the Copyright Owner does not provide any representations or warranties regarding the quality of the programs, the absence of errors or the uninterrupted operation of the software, as well as compliance of the software and information contained in the databases with all the requirements of the Licensee, regardless of whether they have been reported to the Copyright Owner and/or its partners.

    7. +

  7. The information that the Copyright Owner can obtain about the Licensee, including information provided during registration, when applying for updates or contacting the Copyright Owner's technical support service, can be used by the Copyright Owner to send letters related to the Copyright Owner's software to the email address provided by the Licensee, as well as via other telecommunication channels the Licensee hereby confirms his consent to receive advertising and service messages from the Copyright Owner and/or from his partners.

    8. +

  8. When receiving updates from the Copyright Owner's servers, the Licensee agrees to periodically provide the Copyright Owner with certain anonymized information, such as (including, but not limited to): type and version of the installed SOFTWARE PRODUCT, update identifier, current license number. The Copyright Owner is entitled to compare this information with previously signed and currently valid IT support agreements.

    9. +
+
+

Workstation licensing

+
    +
  1. +

    The SOFTWARE PRODUCTS at any single moment can be accessed from the number of workstations specified in the 1C:Enterprise 8 Client License, legally acquired by the Licensee. It is assumed that the SOFTWARE PRODUCTS are accessed from this computer and that they are used in cases where the SOFTWARE PRODUCTS or parts thereof are recorded in the computer’s memory, as well as in other cases when there is a direct or indirect connection between the SOFTWARE PRODUCTS and the computer, workstation, pocket PC, or other digital electronic device.

    +
    2. +
  2. +

    Client License for 1C:Enterprise 8 is valid while the following conditions are met:

    +
      +
    • +

      2.1. The Licensee possesses one or more lawfully acquired SOFTWARE PRODUCTS.

      +
      • +
    • +

      2.2. The SOFTWARE PRODUCTS were installed to the Licensee's computers from the distribution packages mentioned above.

      +
      • +
    • +

      2.3. Each workstation that is used, in accordance with this Client License, to access the SOFTWARE PRODUCTS and infobases of applications included in the SOFTWARE PRODUCTS belongs to one of the following categories:

      +
      • +
        +
      • +

        2.3.1. Computers that have 1C:Enterprise 8 software license files or hardware dongles installed.

        +
        • +
      • +

        2.3.2. Computers connected to the same local area network that has 1C:Enterprise 8 dongles installed.

        +
        • +
      • +

        2.3.3. Other computers that are not used to create infobases for applications included in the SOFTWARE PRODUCTS, but are used to access infobases of applications located on computers defined in 2.3.1 and 2.3.2 above.

        +
        • + +
      +
    +
    3. +
+
    +
  1. +

    Number of Client Licenses required for sessions with 1C:Enterprise 8 infobases (when multiple user sessions run on the same computer to access the infobases):

    +
      +
    • +

      3.1. If a workstation has a 1C:Enterprise 8 software license file or dongle installed, or a workstation is connected to a local area network in which 1C:Enterprise 8 dongles are installed, then one (1) Client License is required for all sessions with 1C:Enterprise 8 infobases running on this workstation.

      +
      • +
    • +

      3.2. If a workstation does not have a 1C:Enterprise 8 software license file or dongle installed, and a workstation is not connected to a local area network in which 1C:Enterprise 8 dongles are installed, then a separate Client License is required for each session with 1C:Enterprise 8 infobases running on this workstation.

      +
      • +
    +
    2. +
+
+

1C:Enterprise 8 server licensing

+
    +
  1. +

    1C:Enterprise 8 server is a specialized server application for accessing infobases using client-server technology. 1C:Enterprise 8 server serves as an intermediate software layer between the 1C:Enterprise 8 client applications and the database server.

    +
    2. +
  2. +

    The Licensee is entitled to install and use 1C:Enterprise 8 Server on one server computer.

    +
    3. +
  3. +

    For server clusters containing multiple computers, a separate license is required for each computer running 1C:Enterprise 8 Server.

    +
    4. +
  4. +

    Usage of 1C:Enterprise 8 Server is considered to be legal if all of the following conditions are met:

    +
      +
    • +

      The Licensee possesses one or more lawfully acquired SOFTWARE PRODUCTS;

      +
      • +
    • +

      1C:Enterprise 8 Server is installed on one server computer;

      +
      • +
    • +

      the Licensee possesses and lawfully uses 1C:Enterprise 8 Client licenses for all workstations that are to access 1C:Enterprise 8 Server.

      +
      • +
    +

  5. Certain functionality of 1C:Enterprise 8 Server, as highlighted in the accompanying documentation, is available only to those Licensees who purchased 1C:Enterprise 8 CORP. Server license as well as Client licenses for 1C:Enterprise 8 CORP. Such functionality is not legally available to users of 1C:Enterprise 8. Server license and Client licenses for 1C:Enterprise 8 PROF. 1C:Enterprise 8.3 CORP server has the following additional functionality compared to the 64-bit PROF server:

    +
      +

    • background database configuration updates;

      • +

    • extra management tools for distribution of the following loads between production servers in a cluster (broken down by infobase, by client application type, or by background job):

      • +
        +

      • cluster services;

        • +

      • infobase connections;

        • +
      +

    • flexible cluster load management:

      • +
        +

      • safe memory consumption per call;

        • +

      • number of infobases per process;

        • +

      • amount of working process memory up to which the server is considered productive;

        • +

      • maximum amount of working process memory;

        • +

      • balancing strategy (by memory, by performance);

        • +
      +

    • external session management;

      • +

    • security profiles;

      • +

    • updating thin client from server;

      • +

    • publishing thin client updates and infobase lists via http.

      • +
    +
    6. +
+

Thin client licensing

+

The thin client is a component of the 1C:Enterprise 8 system. It provides client access to infobases or Internet services created on the 1C:Enterprise 8 platform.

+

Thin client is included in the official distribution package of the 1C:Enterprise 8 platform. It is also available for download from official 1C website provided that the Licensee accepts the terms of the license agreement. Thin client can be used free of charge.

+

When accessing infobases or Internet services via 1C:Enterprise 8 thin client, the client license can be provided and paid for by the infobase owner, the Internet service supplier, or the user.

+ +

Base edition licensing

+

Base edition of 1C:Enterprise 8 (hereinafter referred to as "BASE EDITION") is a 1C:Enterprise 8 distribution package that includes, among others, the 1C:Enterprise 8 platform and a specialized application (configuration).

+

License agreements for base editions impose the following functionality and usage limitations:

+
    +

  • the software product supports single-user access, sequential access by multiple users, or simultaneous access by multiple users (as specified in the License Agreement for the software product);

    • +

  • 1C:Enterprise 8 server connection is not supported;

    • +

  • distributed infobase mode is not supported;

    • +

  • configuration development and modification tools are not available;

    • +

  • external connection mode is not supported;

    • +

  • web client is not supported;

    • +

  • thin client only operates with file-based infobases.

    • +
+

To access and use BASE EDITION for some software products, the Licensee may be required to obtain a software license for using a BASE EDITION copy limited to a Licensee's computer. BASE EDITION does not support hardware dongles.

+ + +

Training version licensing

+

Training version of 1C:Enterprise 8 (hereinafter referred to as "TRAINING VERSION") is a 1C:Enterprise 8 distribution package that includes, among others, a specialized (training) version of the 1C:Enterprise 8 platform and one or several training applications (configurations).

+
    +
  1. +

    The Licensee is entitled to install and use TRAINING VERSION on one computer. 1C:Enterprise Server licenses and Client licenses cannot be used with TRAINING VERSION. To use TRAINING VERSION on multiple computers, a separate copy of TRAINING VERSION per computer must be purchased or downloaded free of charge from the official 1C website.

    +
    2. +
  2. +

    TRAINING VERSION does not support hardware dongles or electronic licenses.

    +
    3. +
  3. +

    TRAINING VERSION cannot be used for real-life automation tasks of enterprises, organizations, or institutions, as well as for personal goals. TRAINING VERSION can be used for development of real-life applications in accordance with documentation included in the software product's distribution package. However, a commercial version of 1C:Enterprise 8 is required to use these developed application for real-life purposes.

    +
    4. +
+ +

1C:Enterprise mobile platform licensing

+ +

Mobile application development tools and 1C:Enterprise mobile platform for development are included in the commercial delivery of 1C:Enterprise platform. They are available to application developers who have purchased 1C:Enterprise platform distribution package without any extra payment.

+

When developers distribute free mobile applications created on 1C:Enterprise platform in app stores or other sources, they do not need to conclude a license agreement with 1C Company or undertake any financial obligations.

+

Any method of monetization requires concluding a license agreement with 1C company.

+

To enable employees to install and use mobile applications created on 1C:Enterprise platform on their mobile devices, a company must purchase client licenses for the required number of mobile workstations.

+

When installing several applications created on 1C:Enterprise platform on one device, a company needs to purchase client licenses for mobile workstations for each application.

+

Rules for distributing applications developed on 1C:Enterprise mobile platform can be found here.

+ +
+ + + + diff --git a/distr/licenses/1CEnterprise_ru.htm b/distr/licenses/1CEnterprise_ru.htm new file mode 100644 index 0000000..a123213 --- /dev/null +++ b/distr/licenses/1CEnterprise_ru.htm @@ -0,0 +1,233 @@ + + + + +Лицензионное соглашение на "1С:Предприятие 8.3" + + + + + + + + + + + + + + + + + + +
+

Лицензионное соглашение на "1С:Предприятие 8.3"

+

Настоящее Лицензионное соглашение является документом, регулирующим правила использования ПРОГРАММНОГО ПРОДУКТА системы "1С:Предприятие 8" физическим или юридическим лицом ("Лицензиатом"), обладающим правомерно изготовленным и зарегистрированным в ООО "1С-Софт" экземпляром данного продукта.

+

ПРОГРАММНЫЙ ПРОДУКТ – это комплект поставки "1С:Предприятия 8", в состав которого в числе прочего входят дистрибутив платформы "1С:Предприятие 8", дистрибутив по крайней мере одного прикладного решения, или конфигурации (кроме отдельных поставок "1С:Предприятия 8") и Лицензионное соглашение, регулирующее правила использования ПРОГРАММНОГО ПРОДУКТА.

+

Все исключительные имущественные права на обозначенный ПРОГРАММНЫЙ ПРОДУКТ (собственно программное обеспечение, записанное на машинных носителях, предоставляемые отдельно обновления и дополнения к программному обеспечению, а также любые сопроводительные материалы в печатном или электронном виде) принадлежат ООО "1С-Софт" (далее – "Правообладатель"), зарегистрированному в г. Москве. Устанавливая ПРОГРАММНЫЙ ПРОДУКТ, осуществляя его запись в память ЭВМ, Лицензиат признает себя связанным условиями настоящего Лицензионного соглашения.

+

По настоящему Лицензионному соглашению Лицензиату предоставляются отдельные неисключительные права, описанные ниже. Лицензиат обязан сохранять Лицензионное соглашение, входящее в комплект поставки ПРОГРАММНОГО ПРОДУКТА, в качестве документа, подтверждающего наличие у него прав, предоставленных Правообладателем, на использование ПРОГРАММНОГО ПРОДУКТА. Правообладатель оставляет за собой право в одностороннем порядке время от времени изменять условия технической поддержки, в том числе предоставления Лицензиату обновлений ПРОГРАММНОГО ПРОДУКТА, путем публикации соответствующего информационного сообщения на сайте Правообладателя.

+
+
+

ОПИСАНИЕ ПРАВ И ОГРАНИЧЕНИЙ

+
    +
  1. +

    Лицензиат имеет право установить и использовать в соответствии с сопроводительной документацией ПРОГРАММНЫЙ ПРОДУКТ на одном компьютере в один момент времени. Использование ПРОГРАММНОГО ПРОДУКТА на нескольких компьютерах допускается только при наличии у Лицензиата Клиентской лицензии "1С:Предприятия 8" на соответствующее количество рабочих мест и только в соответствии с правилами лицензирования рабочего места пользователя (см. далее). Использование ПРОГРАММНОГО ПРОДУКТА в варианте "клиент-сервер" допускается только при наличии у Лицензиата Лицензии на сервер "1С:Предприятия 8" и в соответствии с правилами лицензирования сервера "1С:Предприятия 8" (см. далее). Использование прикладных решений (конфигураций), не входящих в поставку ПРОГРАММНОГО ПРОДУКТА, допускается только при наличии у Лицензиата соответствующих Лицензий на эти прикладные решения (конфигурации).

    +
    2. +
  2. +

    Использование программных продуктов или компьютерного оборудования, позволяющего сократить количество пользователей, которые имеют непосредственный доступ к системе "1С:Предприятие 8" или используют ее (что иногда называют программными или техническими средствами "мультиплексирования"), не уменьшает количества требуемых Клиентских лицензий "1С:Предприятия 8" – требуемое количество Клиентских лицензий должно соответствовать числу отдельных вводов мультиплексирующих программных или аппаратных средств, с которыми осуществляется прямое взаимодействие.

    +
    3. +
  3. +

    Передача прав по настоящему Лицензионному соглашению третьим лицам возможна только при условии передачи им полного комплекта поставки ПРОГРАММНОГО ПРОДУКТА (включая настоящее Лицензионное соглашение), обладателем которого являлся Лицензиат; при этом первоначальный Лицензиат обязан удалить со своего компьютера имеющиеся копии ПРОГРАММНОГО ПРОДУКТА и уведомить о передаче прав Правообладателя.

    +
    4. +
  4. +

    Лицензиат обязуется не допускать нарушений исключительных прав Правообладателя на ПРОГРАММНЫЙ ПРОДУКТ, в частности, не совершать и не допускать совершения третьими лицами следующих действий без специального письменного разрешения Правообладателя:

    +
      +
    • +

      распространять ПРОГРАММНЫЙ ПРОДУКТ или отдельные его компоненты;

      +
      • +
    • +

      вносить какие-либо изменения в код ПРОГРАММНОГО ПРОДУКТА, содержимое баз данных и других наборов данных, в которых система хранит информацию, за исключением тех изменений, которые вносятся штатными средствами, входящими в состав ПРОГРАММНОГО ПРОДУКТА и описанными в сопроводительной документации;

      +
      • +
    • +

      модифицировать поведение платформы «1С:Предприятие» любыми средствами, за исключением входящих в состав ПРОГРАММНОГО ПРОДУКТА и описанных в сопроводительной документации;

      +
      • +
    • +

      осуществлять доступ к информационной базе ПРОГРАММНОГО ПРОДУКТА и построение систем на основе ПРОГРАММНОГО ПРОДУКТА с помощью средств и технологических решений, не предусмотренных в сопроводительной документации;

      +
      • +
    • +

      совершать действия, результатом которых является устранение или снижение эффективности технических средств защиты авторских прав, применяемых Правообладателем, включая применение программных и технических средств "мультиплексирования", средств, изменяющих алгоритм работы программных или аппаратных средств защиты ПРОГРАММНОГО ПРОДУКТА, а также использовать ПРОГРАММНЫЙ ПРОДУКТ с устраненными или измененными без разрешения Правообладателя средствами защиты;

      +
      • +
    • +

      восстанавливать исходный код, декомпилировать и/или деассемблировать программную часть системы, за исключением тех случаев и лишь в той степени, в какой такая деятельность специально разрешена действующим законодательством.

      +
      • +
    +
    5. +
  5. +

    Настоящее Лицензионное соглашение действует в течение всего срока эксплуатации Лицензиатом ПРОГРАММНОГО ПРОДУКТА и/или нахождения у него экземпляров ПРОГРАММНОГО ПРОДУКТА.

    +
    6. +
  6. +

    ПРОГРАММНЫЙ ПРОДУКТ и сопутствующая ему документация предоставляются Лицензиату «КАК ЕСТЬ» – в соответствии с общепринятым в международной практике принципом (AS IS), согласно которому Правообладатель не предоставляет никаких заверений и не дает гарантий в отношении качества программ, отсутствия ошибок или бесперебойной работы программного обеспечения, а также соответствия программного обеспечения и информации, содержащейся в базах данных, всем требованиям Лицензиата вне зависимости от того, сообщено ли о них Правообладателю и/или его партнерам.

    +
    7. +
  7. +

    Информация, которую Правообладатель может получить о Лицензиате, включая информацию, сообщенную при регистрации, при обращении за обновлениями, обращении в службу технической поддержки Правообладателя, может быть использована Правообладателем для отправки связанных с программным обеспечением Правообладателя писем на предоставленный Лицензиатом адрес электронной почты, а также по иным каналам электросвязи, при этом Лицензиат выражает свое согласие на получение рекламных и сервисных сообщений от Правообладателя или третьих лиц.

    +
    8. +
  8. +

    При получении обновлений с серверов Правообладателя Лицензиат соглашается периодически предоставлять Правообладателю определенную обезличенную информацию, такую как (включая, но не ограничиваясь): тип и версия установленного ПРОГРАММНОГО ПРОДУКТА, идентификатор обновления, номер действующей лицензии, – которую Правообладатель вправе сопоставлять с ранее заключенными и действующими договорами на информационно-технологическое сопровождение.

    +
    9. + +
+
+

Лицензирование рабочего места

+
    +
  1. +

    Доступ к ПРОГРАММНЫМ ПРОДУКТАМ осуществляется в один момент времени с такого количества рабочих мест, которое обозначено в Клиентской лицензии "1С:Предприятия 8", правомерно приобретенной Лицензиатом. При этом считается, что к ПРОГРАММНЫМ ПРОДУКТАМ получен доступ с данного компьютера и что они используются в тех случаях, когда осуществляется запись ПРОГРАММНЫХ ПРОДУКТОВ или их частей в память компьютера, а также в иных случаях, когда имеет место прямая или косвенная связь между компьютером, рабочей станцией, карманным персональным компьютером или иным цифровым электронным устройством и ПРОГРАММНЫМИ ПРОДУКТАМИ.

    +
    2. +
  2. +

    Клиентская лицензия "1С:Предприятия 8" действительна при выполнении следующих условий:

    +
      +
    • +

      2.1. У Лицензиата имеется один или несколько правомерно приобретенных ПРОГРАММНЫХ ПРОДУКТОВ.

      +
      • +
    • +

      2.2. С указанных выше дистрибутивов установка ПРОГРАММНЫХ ПРОДУКТОВ произведена на компьютеры Лицензиата.

      +
      • +
    • +

      2.3. Все рабочие места, с которых в соответствии с настоящей Клиентской лицензией организуется доступ к ПРОГРАММНЫМ ПРОДУКТАМ и информационным базам прикладных решений, входящих в ПРОГРАММНЫЕ ПРОДУКТЫ, представляют собой:

      +
        +
      • +

        2.3.1. Компьютеры, на которых установлены файлы программных лицензий или аппаратные ключи защиты "1С:Предприятия 8".

        +
        • +
      • +

        2.3.2. Компьютеры, подключенные к одной и той же локальной вычислительной сети, в которой установлены аппаратные ключи защиты "1С:Предприятия 8".

        +
        • +
      • +

        2.3.3. Другие компьютеры, на которых не создаются информационные базы прикладных решений, входящих в ПРОГРАММНЫЕ ПРОДУКТЫ, а осуществляется доступ к информационным базам прикладных решений, расположенным на компьютерах, указанных в пп. 2.3.1 и 2.3.2.

        +
        • +
      +
      • +
    +
  3. +

    Требуемое количество Клиентских лицензий на сеансы с информационными базами "1С:Предприятия 8" (при запуске на одном компьютере нескольких пользовательских сеансов для работы с базами данных):

    +
      +
    • +

      3.1. Если на данном рабочем месте установлен файл программной лицензии или аппаратный ключ защиты "1С:Предприятия 8" либо данное рабочее место подключено к локальной вычислительной сети, в которой установлены аппаратные ключи защиты "1С:Предприятия 8", то на все сеансы с информационными базами "1С:Предприятия 8", запущенные с данного рабочего места, достаточно одной Клиентской лицензии.

      +
      • +
    • +

      3.2. Если на данном рабочем месте не установлен файл программной лицензии или аппаратный ключ защиты "1С:Предприятия 8" и данное рабочее место не подключено к локальной вычислительной сети, в которой установлены аппаратные ключи защиты "1С:Предприятия 8", то на каждый сеанс с информационной базой "1С:Предприятия 8" требуется отдельная Клиентская лицензия.

      +
      • +
    +
    4. +
+
+

Лицензирование сервера "1С:Предприятия 8"

+
    +
  1. +

    Сервер "1С:Предприятия 8" представляет собой специализированное серверное приложение, через которое осуществляется доступ к информационной базе с использованием технологии "клиент-сервер". Сервер "1С:Предприятия 8" образует промежуточный программный слой между клиентскими приложениями системы программ "1С:Предприятие 8" и сервером баз данных.

    +
    2. +
  2. +

    Лицензиат имеет право установить и использовать Сервер "1С:Предприятия 8" на одном компьютере-сервере.

    +
    3. +
  3. +

    Если используется кластер серверов на нескольких компьютерах, то должна быть приобретена лицензия на каждый компьютер, на котором будет работать Сервер "1С:Предприятия 8".

    +
    4. +
  4. +

    Использование Сервера "1С:Предприятия 8" будет являться правомерным при одновременном выполнении следующих условий:

    +
      +
    • +

      у Лицензиата имеется один или несколько правомерно приобретенных ПРОГРАММНЫХ ПРОДУКТОВ;

      +
      • +
    • +

      установка Сервера "1С:Предприятия 8" произведена на один компьютер-сервер;

      +
      • +
    • +

      на соответствующее количество рабочих мест, с которых планируется организовать доступ к Серверу "1С:Предприятия 8", у Лицензиата имеются и правомерно используются Клиентские лицензии на "1С:Предприятие 8".

      +
      • +
    +
    5. +
  5. +

    Отдельные функциональные возможности Сервера "1С:Предприятия 8", выделенные в сопроводительной документации, доступны только тем Лицензиатам, которые приобрели "1С:Предприятие 8 КОРП. Лицензия на сервер" и Клиентские лицензии на "1С:Предприятие 8" уровня КОРП. Использование таких функциональных возможностей пользователями "1С:Предприятие 8. Лицензия на сервер" и Клиентские лицензии на "1С:Предприятие 8" уровня ПРОФ неправомерно. Ниже перечислены расширенные возможности сервера уровня КОРП "1С:Предприятия 8.3" по сравнению с 64-разрядным сервером уровня ПРОФ:

    +
      +

    • фоновое обновление конфигурации базы данных;

      • +

    • дополнительное управление распределением по рабочим серверам кластера в разрезе информационных баз, видов клиентских приложений и фоновых заданий:

      +
        +

      • сервисов кластера;

        • +

      • соединений с информационными базами;

        • +
      +
      • +

    • гибкое управление нагрузкой в кластере:

      +
        +

      • безопасный расход памяти за один вызов;

        • +

      • количество ИБ на процесс;

        • +

      • объем памяти рабочих процессов, до которого сервер считается производительным;

        • +

      • максимальный объем памяти рабочих процессов;

        • +

      • стратегия балансировки (по памяти, по производительности);

        • +
      +
      • +

    • внешнее управление сеансами;

      • +

    • профили безопасности;

      • +

    • возможность обновления тонкого клиента с сервера;

      • +

    • возможность публикации списка баз и обновлений тонкого клиента через http.

      • +
    +
    6. +
+

Лицензирование тонкого клиента

+

Тонкий клиент является частью системы "1С:Предприятие 8" и обеспечивает клиентский доступ к информационной базе или интернет-сервису, созданным на платформе "1С:Предприятие 8".

+

Дистрибутив тонкого клиента входит в официальную поставку платформы "1С:Предприятия 8", а также доступен на официальном сайте фирмы "1С" при принятии Лицензиатом условий лицензионного соглашения. Плата за использование тонкого клиента не взимается.

+

При осуществлении доступа к информационной базе или интернет-сервису с помощью тонкого клиента "1С:Предприятия 8" клиентскую лицензию обеспечивает и оплачивает владелец соответствующей информационной базы, поставщик интернет-сервиса или непосредственно пользователь.

+ +

Лицензирование базовой версии

+

Базовая версия системы "1С:Предприятие 8" (далее – БАЗОВАЯ ВЕРСИЯ) – это комплект поставки "1С:Предприятия 8", в состав которого в числе прочего входит платформа "1С:Предприятие 8" и специализированная поставка прикладного решения (конфигурации).

+ +

Лицензионные соглашения для базовых версий накладывают ограничения функциональности и использования:

+
    +

  • программный продукт поддерживает работу одного пользователя, последовательную работу нескольких пользователей или нескольких пользователей в один момент времени (оговаривается в Лицензионном соглашении на программный продукт);

    • +

  • не поддерживается работа с сервером "1С:Предприятия 8";

    • +

  • не поддерживается работа в режиме распределенной информационной базы;

    • +

  • недоступны средства разработки и изменения конфигурации;

    • +

  • не работает в режиме внешнего соединения;

    • +

  • не поддерживается работа в режиме веб-клиента;

    • +

  • работа в режиме тонкого клиента возможна только с файловой информационной базой.

    • +
+ + +

Для запуска и работы БАЗОВОЙ ВЕРСИИ Лицензиату в зависимости от конкретного продукта может требоваться получение программной лицензии на использование данного экземпляра БАЗОВОЙ ВЕРСИИ, обеспечивающей его привязку к компьютеру Лицензиата. Аппаратные ключи защиты в БАЗОВОЙ ВЕРСИИ не применяются.

+ +

Лицензирование учебной версии

+

Учебная версия системы программ "1С:Предприятия 8" (далее – УЧЕБНАЯ ВЕРСИЯ) – это комплект поставки "1С:Предприятия 8", в состав которого в числе прочего входит специализированная (учебная) версия платформы "1С:Предприятия 8" и одно либо несколько учебных прикладных решений (конфигураций).

+
    +
  1. +

    Лицензиат имеет право установить и использовать УЧЕБНУЮ ВЕРСИЮ на одном компьютере. Использование Клиентских лицензий, а также Лицензии на сервер "1С:Предприятия 8" с учебной версией не допускается. При необходимости использования УЧЕБНОЙ ВЕРСИИ на нескольких компьютерах следует для каждого компьютера приобрести или бесплатно получить на официальном сайте фирмы "1С" отдельный экземпляр УЧЕБНОЙ ВЕРСИИ.

    +
    2. +
  2. +

    Аппаратные ключи защиты или "электронные лицензии" в УЧЕБНОЙ ВЕРСИИ не применяются.

    +
    3. +
  3. +

    УЧЕБНАЯ ВЕРСИЯ не может использоваться для реальной автоматизации предприятий, организаций, учреждений, а также персональных задач. УЧЕБНУЮ ВЕРСИЮ допускается использовать для разработки реальных прикладных решений в соответствии с документацией, включенной в комплект поставки программного продукта. При этом реальная эксплуатация прикладных решений может осуществляться только на коммерческих версиях "1С:Предприятия 8".

    +
    4. +
+ +

Лицензирование мобильной платформы "1С:Предприятия 8"

+ +

Средства разработки мобильных приложений и мобильная платформа "1С:Предприятие 8" для целей разработки включены в коммерческую поставку платформы "1С:Предприятие" и без дополнительной оплаты доступны разработчикам прикладных решений, правомерно владеющим дистрибутивом платформы "1С:Предприятие 8.3".

+

При бесплатном распространении мобильного приложения, созданного на платформе «1С:Предприятие», среди третьих лиц через магазины приложений и любыми другими способами заключение лицензионного договора с фирмой «1С» не требуется, никаких финансовых обязательств перед «1С» у разработчика не возникает.

+

При любом способе монетизации требуется заключение лицензионного соглашения с фирмой «1С».

+

Для установки и использования мобильных приложений, созданных на платформе "1С:Предприятие", на мобильных устройствах своих сотрудников организация должна приобрести клиентские лицензии на соответствующее количество мобильных рабочих мест.

+

При установке на одно устройство нескольких приложений, созданных на мобильной платформе "1С:Предприятие 8", необходимо приобрести клиентские лицензии на мобильные рабочие места на каждое из таких приложений.

+

Правила распространения приложений, разработанных на мобильной платформе "1С:Предприятия 8", см. здесь

+ +
+ + + + diff --git a/distr/readme.htm b/distr/readme.htm new file mode 100644 index 0000000..4d6ac04 --- /dev/null +++ b/distr/readme.htm @@ -0,0 +1,111 @@ + + + + + + + + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
(AZ)fayl Readme - Azərbaycan dili ilə bağlı əlavə məlumat.
(AR)Readme الملف التمهيدي - معلومات إضافية باللغة العربية.
(BG)Readme Файл - Допълнителна информация на Български език.
(DE)Datei Readme - weitere Informationen auf Deutsch.
(EL)File ReadMe - Περισσότερες πληροφορίες στα ελληνικά.
(EN)File ReadMe - Additional information in English.
(ES)File ReadMe - Mas informacion en español.
(FR)File ReadMe - Information supplémentaire en français.
(HU)File ReadMe - További információ magyarul.
(HY)Ֆայլը ReadMe - Լրացուցիչ տեղեկություններ հայերեն լեզվով.
(IT)File Readme - Maggiori informazioni in italiano.
(KA)ფაილი Readme - დამატებითი ინფორმაცია ქართულ ენაზე.
(KK)Файл Readme - Қазақ тілінде қосымша ақпарат.
(LT)Failas Readme - Papildoma informacija lietuvių kalba.
(LV)Fails Readme - Papildinformācija latviešu valodā.
(PL)Plik Readme - Informacja dodatkowa w języku polskim.
(pt_BR)Arquivo Readme - Informações adicionais em português (Brasil).
(RO)Fişierul Readme - Informaţia suplimentară în limba romănă.
(RU)Файл Readme - Дополнительная информация на русском языке.
(TK)Faýl ReadMe - Türkmen dilinde goşmaça maglumat.
(TR)Dosyası Readme - Türkçe olarak ek bilgiler.
(UK)Файл Readme - Додаткова інформація українською мовою.
(VI)Tệp Readme - Thông tin bổ sung bằng tiếng Việt.
(ZH)文件 Readme - 对中国的其他信息.
+


+
+
+
+
+
+
+

+ + diff --git a/distr/readme/readme_ar.htm b/distr/readme/readme_ar.htm new file mode 100644 index 0000000..c3079c8 --- /dev/null +++ b/distr/readme/readme_ar.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

حقوق الطبع والنشر © 1C-Soft LLC ، 1996-2024. جميع الحقوق محفوظة.

+ +

اتفاقية الترخيص

+ +

يتم إعطاء اتفاقية الترخيص التي تحكم استخدام 1C:Enterprise 8 في الملف 1CEnterprise_en.htm.

+

الانتقال من الإصدارات السابقة

+

اختلافات الإصدار الحالي من الإصدارات السابقة وميزات الانتقال إلى الإصدار الجديد مبينة في ملف V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_az.htm b/distr/readme/readme_az.htm new file mode 100644 index 0000000..8d69db5 --- /dev/null +++ b/distr/readme/readme_az.htm @@ -0,0 +1,29 @@ + + + + + + + + +

+ 1C:Müəssisə 8.3

+

+ Copyright © "1C-Soft" MMC, 1996-2025. Bütün haqlar qorunur. +

+ +

Lisenziya razılaşması

+ +

Lisenziya razılaşması, hansı ki 1C:Müəssisə 8-in istifadəsi qaydasını tənzimləyir + , bu faylda göstərilir  1CEnterpise_ru.htm. +

+

Əvvəlki versiyadan keçid

+

Cari versiyanın  əvvəlki versiyadan  fərqi və yeni versiyaya keçidin xüsusiyyətləri + bu faylda göstərilir V8Update.htm. +

+

+

+ + diff --git a/distr/readme/readme_bg.htm b/distr/readme/readme_bg.htm new file mode 100644 index 0000000..3e42328 --- /dev/null +++ b/distr/readme/readme_bg.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1С:Предприятие 8.3

+

Copyright © "1С-Софт" ООД, 1996-2025. Всички права запазени.

+ +

Лицензионно споразумение

+ +

Лицензионно споразумение, регулиращо правилата за ползване на 1С:Предприятие 8, приведено във файл 1CEnterprise_en.htm.

+

Преход от предходна версия

+

Разликите на текущата версия от предходните версии и особеностите по преминаване към нова версия са приведени във файл V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_de.htm b/distr/readme/readme_de.htm new file mode 100644 index 0000000..f9ad6be --- /dev/null +++ b/distr/readme/readme_de.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © 1C-Soft GmbH, 1996-2025. Alle Rechte vorbehalten.

+ +

Lizenzvereinbarung

+ +

Die Lizenzvereinbarung, die die Verwendung von 1C:Enterprise 8 regelt, ist in der Datei 1CEnterprise_en.htm enthalten.

+

Übergang von früheren Versionen

+

Die Unterschiede der aktuellen Version zu den Vorgängerversionen und die Funktionen des Übergangs zur neuen Version sind in der Datei V8Update.htm angegeben.

+

+

+ + diff --git a/distr/readme/readme_el.htm b/distr/readme/readme_el.htm new file mode 100644 index 0000000..54a8ba5 --- /dev/null +++ b/distr/readme/readme_el.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © ΕΠΕ 1С-Soft, 1996-2025. Όλα τα δικαιώματα διατηρούνται.

+ +

Άδεια χρήσης

+ +

Η άδεια χρήσης, που ρυθμίζει τους κανόνες χρήσης του 1C:Enterprise 8, αναφέρεται στο αρχείο 1CEnterprise_en.htm.

+

Μετάβαση από τις προηγούμενες εκδόσεις

+

Οι διαφορές της τρέχουσας έκδοσης από τις προηγούμενες εκδόσεις και οι ιδιαιτερότητες της μετάβασης σε νέα έκδοση αναφέρονται στο αρχείο V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_en.htm b/distr/readme/readme_en.htm new file mode 100644 index 0000000..f424b6b --- /dev/null +++ b/distr/readme/readme_en.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © 1C-Soft LLC 1996–2025. All rights reserved.

+ +

License agreement

+ +

The 1C:Enterprise 8 license agreement can be found in the file 1CEnterprise_en.htm.

+

Switching from earlier versions

+

The version changelog and information on switching to the later version can be found in the file V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_es.htm b/distr/readme/readme_es.htm new file mode 100644 index 0000000..cd79067 --- /dev/null +++ b/distr/readme/readme_es.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1С:Enterprise 8.3

+

Copyright © S.L."1С-Softт", 1996-2025. Todos los derechos reservados.

+ +

Acuerdo de licencia

+ +

El acuerdo de licencia que controla las reglas del uso de 1C:Enterprise 8 se encuentra en el archivo 1CEnterprise_en.htm.

+

Traspaso de las versiones anteriores

+

Las diferencias de la versión actual de las versiones anteriores y peculiaridades de traspaso a la versión nueva se encuentran en el archivo V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_fr.htm b/distr/readme/readme_fr.htm new file mode 100644 index 0000000..f982939 --- /dev/null +++ b/distr/readme/readme_fr.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright ©1C-Soft LLC, 1996-2025. Tous droits réservés.

+ +

Contrat de licence

+ +

Le contrat de licence régissant l’utilisation de 1C:Enterprise 8 est indiqué dans le fichier 1CEnterprise_en.htm.

+

Transition des versions précédentes

+

Les différences entre la version actuelle et les versions précédentes et les fonctionnalités de la transition vers la nouvelle version sont indiquées dans le fichier V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_hu.htm b/distr/readme/readme_hu.htm new file mode 100644 index 0000000..c4ede0f --- /dev/null +++ b/distr/readme/readme_hu.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © LLC "1С-Soft", 1996-2025. Minden jog fenntartva.

+ +

Licensz szerződés

+ +

Az 1C:Enterprise 8 használatát szabályozó licensz szerződést az 1CEnterprise_en.htm fájl tartalmazza.

+

A korábbi verzióról történő áttérés

+

Az új verzióra való áttérés tulajdonságai és az aktuális verzió éltérősegei a korábbi verzióktól a V8Update.htm fájlban vannak megadva.

+

+

+ + diff --git a/distr/readme/readme_hy.htm b/distr/readme/readme_hy.htm new file mode 100644 index 0000000..7e96ced --- /dev/null +++ b/distr/readme/readme_hy.htm @@ -0,0 +1,39 @@ + + + + + + + + + + + + + +

+ 1С:Ձեռնարկություն 8.3

+ +

+ Copyright © ՍՊԸ "1С-Սոֆթ", 1996-2025. Բոլոր իրավունքները պաշտպանված են: +

+ +

Արտոնագրային համաձայնագիր

+ + +

Արտոնագրային համաձայնագիր, որը կարգավորում է 1С:Ձեռնարկություն 8 օգտագործման կանոնները, բերված է ֆայլում   1CEnterpise_ru.htm. +

+ +

Անցում նախորդ տարբերակներից

+ +

Ընթացիկ ֆայլի տարբերությունները նախորդ ֆայլից և նոր տարբերակին անցման առանձնահատկությունները բերված են + ֆայլում V8Update.htm. +

+ +

+

+ + + \ No newline at end of file diff --git a/distr/readme/readme_it.htm b/distr/readme/readme_it.htm new file mode 100644 index 0000000..048a13e --- /dev/null +++ b/distr/readme/readme_it.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © ООО "1С-Soft", 1996-2025. Tutti i diritti riservati.

+ +

Accordo di licenza

+ +

L'accordo di licenza che disciplina l'uso del software 1С:Enterprise 8, è riportato nel file 1CEnterprise_en.htm.

+

Transizione dalle versioni precedenti

+

Vengono fornite le differenze della versione corrente rispetto alle versioni precedenti e le caratteristiche della transizione alla nuova versione nel file V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_ka.htm b/distr/readme/readme_ka.htm new file mode 100644 index 0000000..6bcaf8f --- /dev/null +++ b/distr/readme/readme_ka.htm @@ -0,0 +1,40 @@ + + + + + + + + + + + + + +

+ 1C:საწარმო 8.3

+ +

+ Copyright © LLC "1C-Soft", 1996-2025. ყველა უფლება დაცულია. +

+ + +

სალიცენზიო შეთანხმება

+ + +

სალოცენზიო შეთანხმება, რომელიც არეგულირებს 1C:საწარმო 8-ის გამოყენების წესებს, მოცემულია ფაილში  1CEnterpise_ru.htm. +

+ +

გადასვლა წინა ვერსიებზე

+ + +

წინა და მიმდინარე ვერსიებს შორის განსხვავებები და ახალ ვერსიაზე გადასვლის თავისებურებები მოცემულია ფაილში V8Update.htm. +

+ +

+

+ + + \ No newline at end of file diff --git a/distr/readme/readme_kk.htm b/distr/readme/readme_kk.htm new file mode 100644 index 0000000..01c9338 --- /dev/null +++ b/distr/readme/readme_kk.htm @@ -0,0 +1,28 @@ + + + + + + + + +

+ 1С:Предприятие 8.3 (1С:Кәсіпорын 8.3)

+

+ Copyright © "1С-Софт" ЖШҚ, 1996-2025. Барлық құқықтар қорғалған. +

+

Лицензиялық келісім

+ +

1С:Предприятие + 8 (1С:Кәсіпорын 8-ді) пайдалану қағидаларын реттейтін лицензиялық келісім 1CEnterpise_ru.htm файлында келтірілген. +

+

Алдыңғы нұсқалардан ауысу

+

Жаңа нұсқаның алдыңғы нұсқалардан айырмашылықтары және жаңа нұсқаға + ауысу ерекшеліктері V8Update.htm файлында келтірілген. +

+

+

+ + diff --git a/distr/readme/readme_lt.htm b/distr/readme/readme_lt.htm new file mode 100644 index 0000000..ff8a811 --- /dev/null +++ b/distr/readme/readme_lt.htm @@ -0,0 +1,20 @@ + + + + + + + +

1C:Organizacija 8.3

+

Copyright © Ltd "1C-Soft", 1996-2025. Visos teisės saugomos.

+

Licencijos sutartis

+

Licencijos sutartis, reguliuojanti programos 1C:Organizacija 8 naudojimo taisykles, pateikta byloje   1CEnterprise_en.htm.

+

Perėjimas nuo senesnių versijų

+

Tai, kuo ši versija skiriasi nuo kitų versijų, ir perėjimo į naują versiją ypatumai pateikti byloje V8Update.htm.

+

\ No newline at end of file diff --git a/distr/readme/readme_lv.htm b/distr/readme/readme_lv.htm new file mode 100644 index 0000000..1236f4e --- /dev/null +++ b/distr/readme/readme_lv.htm @@ -0,0 +1,14 @@ + + + + + + +

1С:Uzņēmums 8.3

+

Copyright © SIA "1C-Soft", 1996.-2025. Visas tiesības aizsargātas.

+

Licences līgums

Licences līgums, kas regulē 1C:Uzņēmums 8 izmantošanas noteikumus, atrodas failā 1CEnterpise_en.htm. +

Pāreja no iepriekšējām versijām

+

Šīs versijas atšķirības no iepriekšējām versijām un īpatnības pārejai uz jauno versiju sniegtas failā V8Update.htm.

+

\ No newline at end of file diff --git a/distr/readme/readme_pl.htm b/distr/readme/readme_pl.htm new file mode 100644 index 0000000..1678971 --- /dev/null +++ b/distr/readme/readme_pl.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © Sp. z o.o., "1С-Soft", 1996-2025. Wszystkie prawa zastrzeżone.

+ +

Umowa licencyjna

+ +

Umowa licencyjna regulująca użytkowanie 1С:Enterprise 8, jest zamieszczona w pliku 1CEnterprise_en.htm.

+

Przejście z poprzednich wersji

+

Różnice aktualnej wersji i poprzednich wersji oraz szczegóły przejścia do nowej wersji podano w pliku V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_ro.htm b/distr/readme/readme_ro.htm new file mode 100644 index 0000000..7dc7867 --- /dev/null +++ b/distr/readme/readme_ro.htm @@ -0,0 +1,21 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © SRL "1C-Soft", 1996-2025. Toate drepturile sunt rezervate.

+

Acord de licență

+ +

Acordul de licență care reglementează drepturile de utilizare a programului 1C:Enterprise 8 este expus în fișierul 1CEnterprise_en.htm.

+

Salt de la versiunile precedente

+

Deosebirile versiunii curente de versiunile precedențe și particularitățile de trecere la versiunea nouă a programului sunt prezentate în fișierul V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_ru.htm b/distr/readme/readme_ru.htm new file mode 100644 index 0000000..9550764 --- /dev/null +++ b/distr/readme/readme_ru.htm @@ -0,0 +1,29 @@ + + + + + + + + +

+ 1С:Предприятие 8.3

+

+ Copyright © ООО "1С-Софт", 1996-2025. Все права защищены. +

+ +

Лицензионное соглашение

+ +

Лицензионное соглашение, регулирующее правила использования 1С:Предприятие + 8, приведено в файле  1CEnterprise_ru.htm. +

+

Переход с предыдущих версий

+

Отличия текущей версии от предыдущих версий и особенности перехода на + новую версию приведены в файле V8Update.htm. +

+

+

+ + diff --git a/distr/readme/readme_tk.htm b/distr/readme/readme_tk.htm new file mode 100644 index 0000000..bb594e6 --- /dev/null +++ b/distr/readme/readme_tk.htm @@ -0,0 +1,26 @@ + + + + + + + + +

+ 1C:Kärhana 8.3

+

+ Copyright © JÇB "1C-Soft", 1996-2025. Ähli hukuklar goralan. +

+

Ygtyýarnama ylalaşygy

+ +

1C:Kärhana 8 ulanyş düzgünlerini kadalaşdyrýan ygtyýarnama ylalaşygy  1CEnterpise_ru.htm faýlynda ýerleşýär . +

+

Öňki görnüşlerden geçmek

+

Häzirki görnüşiň  öňki görnüşlerden tapawudy hem-de täze görnüşe geçmekligiň aýratynlyklary V8Update.htm faýlynda görkezilendir. +

+

+

+ + diff --git a/distr/readme/readme_tr.htm b/distr/readme/readme_tr.htm new file mode 100644 index 0000000..85272f4 --- /dev/null +++ b/distr/readme/readme_tr.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © 1С-Soft Ltd. Şti. 1996-2025. Tüm haklar saklıdır.

+ +

Lisans anlaşması

+ +

1C:Enterprise 8 kullanım kurallarını düzenleyen lisans anlaşması, 1CEnterprise_en.htm dosyasında sunulmuştur.

+

Önceki sürümlerden geçiş

+

Mevcut sürümün önceki sürümlerden farkları ve yeni sürüme geçiş özellikleri V8Update.htm dosyasında sunulmuştur.

+

+

+ + diff --git a/distr/readme/readme_uk.htm b/distr/readme/readme_uk.htm new file mode 100644 index 0000000..16e52cf --- /dev/null +++ b/distr/readme/readme_uk.htm @@ -0,0 +1,29 @@ + + + + + + + + +

+ 1С:Підприємство 8.3

+

+ Всі права захищені. +

+ +

Користувацька угода

+ +

Користувацька угода, що регулює правила використання 1С:Підприємство 8, + наведена у файлі  1CEnterprise_en.htm. +

+

Перехід з попередніх версій

+

Відмінності поточної версії від попередніх версій та особливості переходу на + нову версію приведені у файлі V8Update.htm. +

+

+

+ + diff --git a/distr/readme/readme_vi.htm b/distr/readme/readme_vi.htm new file mode 100644 index 0000000..f6b12e6 --- /dev/null +++ b/distr/readme/readme_vi.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © LLC "1С-Soft", 1996-2025. Tất cả các quyền đều được bảo hộ.

+ +

Thỏa thuận cấp phép

+ +

Thỏa thuận cấp phép điều chỉnh quy tắc sử dụng 1C:Enterprise mà được đưa ra trong tệp 1CEnterprise_en.htm.

+

Chuyền từ các phiên bản trước đó

+

Sự khác nhau giữa phiên bản hiện tại với các phiên bản trước đó và điểm đặc biệt chuyển đến phiên bản mới được đưa ra trong tệp V8Update.htm.

+

+

+ + diff --git a/distr/readme/readme_zh.htm b/distr/readme/readme_zh.htm new file mode 100644 index 0000000..cafc2cd --- /dev/null +++ b/distr/readme/readme_zh.htm @@ -0,0 +1,22 @@ + + + + + + + + +

1C:Enterprise 8.3

+

Copyright © LLC "1C-Soft", 1996-2025.保留所有权.

+ +

许可协议

+ +

在 1CEnterprise_en.htm 许可协议管理使用 1С:Enterprise 8 规则.

+

从上版本转移

+

本版本比上本版本差别和转移新的版本是 V8Update.htm.

+

+

+ + diff --git a/distr/server64_with_all_clients_8_3_27_2342.zip b/distr/server64_with_all_clients_8_3_27_2342.zip new file mode 100644 index 0000000..3f46826 Binary files /dev/null and b/distr/server64_with_all_clients_8_3_27_2342.zip differ diff --git a/distr/setup-full-8.3.27.2342-x86_64.run b/distr/setup-full-8.3.27.2342-x86_64.run new file mode 100755 index 0000000..992a0c3 Binary files /dev/null and b/distr/setup-full-8.3.27.2342-x86_64.run differ diff --git a/entrypoint.sh b/entrypoint.sh new file mode 100644 index 0000000..0ccc74c --- /dev/null +++ b/entrypoint.sh @@ -0,0 +1,76 @@ +#!/bin/bash + +set -euo pipefail + +log() { + echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" +} + +publish() { + log "Публикация $base_name" + $WORKDIR/webinst \ + -publish \ + -apache24 \ + -wsdir $base_name \ + -dir /var/www/1c/$base_name \ + -connstr "File=/bases/$base_name;" \ + -confpath /etc/apache2/apache2.conf +} + +check() { + log "Подготовка модулей apache" + apache2ctl -V | grep -i mpm + a2dismod mpm_event + a2dismod mpm_prefork + a2enmod mpm_worker + sed -i '/StartServers/s/2/1/g' /etc/apache2/mods-available/mpm_worker.conf + sed -i '/MinSpareThreads/s/25/1/g' /etc/apache2/mods-available/mpm_worker.conf + sed -i '/MaxSpareThreads/s/75/1/g' /etc/apache2/mods-available/mpm_worker.conf + log "Проверка наличия платформы" + if [ ! -d "/opt/1cv8/x86_64/${SERVER_VERSION}/" ]; then + log "Нужная версия 1С $SERVER_VERSION не установленна в $WORKDIR " + return 1 + else + log "Платформа 1С $SERVER_VERSION уже установлена. Путь: $WORKDIR" + fi + log "Проверка установленного модуля поддержки веб сервисов" + if [ ! -e "/etc/apache2/mods-enabled/wsap24.load" ]; then + log "Подключаю модуль wsap24" + echo "LoadModule _1cws_module /opt/1cv8/x86_64/${SERVER_VERSION}/wsap24.so" > /etc/apache2/mods-available/wsap24.load + ln -s /etc/apache2/mods-available/wsap24.load /etc/apache2/mods-enabled/wsap24.load + else + log "Модуль уже wsap24.load подключен" + fi + log "Проверка баз в $BASES_DIR" + if [ -d $BASES_DIR ]; then + log "Каталог баз данных $BASES_DIR обнаружен" + for dir in "$BASES_DIR"/*; do + log "Обрабатываем $dir" + if [ -f $dir/1Cv8.1CD ]; then + log "$dir - каталог базы данных" + log "Назначаю права на каталог $dir " + chown -R www-data:www-data $dir + local base_name=$(basename "$dir") + publish "$base_name" + fi + done + fi + log "Перечисление лицензий:" + /opt/1C/1CE/components/1c-enterprise-ring-0.20.0+4-x86_64/ring license list +} + +start() { + exec /usr/sbin/apache2ctl -DFOREGROUND +} +main() { + log "=== Запуск Web Сервера ===" + check + log "=== Все готово, запускаем сервер ===" + start +} + +# Обработка сигналов +trap 'log "Получен сигнал остановки"; exit 0' SIGTERM SIGINT + +# Запуск основной функции +main "$@" diff --git a/run.sh b/run.sh new file mode 100755 index 0000000..46165b0 --- /dev/null +++ b/run.sh @@ -0,0 +1,16 @@ +#!/bin/sh + +docker run -d \ + --restart unless-stopped \ + -h srv1c-web \ + -p 1540-1545:1540-1545 \ + -p 1560-1591:1560-1591 \ + -p 888:80 \ + --name srv1c-web \ + -v /srv/fdata/srv1c/data:/home/usr1cv8 \ + -v /srv/fdata/srv1c/licenses:/var/1C/licenses \ + -v /srv/sdata/srv1c/backup:/backup \ + -v /etc/localtime:/etc/localtime:ro \ + -v /srv/bases:/bases \ +srv1c-web:8.3.27.2342 +