New functionality and changes
|Functionality||After||Before||Result of changes|
||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.|
||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.|
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.|
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.|
||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.|
||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.|
||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.|
||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.|
||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:
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.|
||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
|This feature was not provided.||New functionality introduced for configuration extensions.|
||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.|
||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.|
||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.|
||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:
|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.|
||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.|
|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.|
||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).|
||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.|
||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.|
||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:email@example.com. This option has the following limitations:
||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.|
||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.|
||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.|
||Support of Oracle Database version 126.96.36.199 (Linux) is implemented.||This Oracle Database version was not supported.||Extended list of supported Oracle Database versions.|
|The client application for OS X 10.8 or later is available (64-bit version only). It supports the following features:
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.|
||Astra Linux Special Edition 1.4 is supported.||This release was not supported.||New Linux release is supported.|
||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.|