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.

Comments
0
Add comment