Version 8.3.7 includes known bug fixes and functionality modifications.
- New functionality and changes
- New functionality and changes in the 1C:Enterprise mode
- Optimization
- Changes that affect system behavior
- Changes that require modification of configuration and administrative settings
- Renamed objects
- Mobile platform
- Library updates
- Transition from the previous version to the version 8.3.7
New functionality and changes
| Functionality | After | Before | Result 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). |
| File 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:
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:
| 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. | 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:
| 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. | 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. | 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. |
New functionality and changes in the 1C:Enterprise mode
| Functionality | After | Before | Result 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. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. | The performance of the following Designer operations is improved:
| The performance of some Designer operations was insufficient. | Streamlined execution of some Designer operations. |
| Geographical schemas. | The following geographical schema operations are optimized:
| 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:
|
| 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:
| 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. |
Changes that affect system behavior
| Functionality | After | Before | Result 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:
| 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. |
Changes that require modification of configuration and administrative settings
| Functionality | After | Before | Result 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 toggling item visibility, 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. 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:
| 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:
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 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:
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. | In managed forms you can edit multilingual spreadsheet documents, 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 preserved. The SpreadsheetDocument.Template property is implemented. This change is not implemented in 8.3.6 compatibility mode. | In managed forms spreadsheet documents were always edited using the current language. When the platform displayed a spreadsheet document:
When spreadsheet document text was edited using 1C:Enterprise script, strings in the current language were written and strings in other | 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:
| 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:
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. |
Renamed objects
Mobile platform
| Functionality | After | Before | Result 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:
The mobile platform specifics are described in the documentation. The mobile platform distribution file mobile.zip is complemented with new data. | 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:
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. |
Library updates
Transition from the previous version to the version 8.3.7
- Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.7.
- Some features that are added in version 8.3.7 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
- In order to use the new format of full-text search index and improve the performance of the input by string feature, clearing the full-text search index and building a new index is required. The Compatibility mode property must be set to None during these operations.
- In the web client, the cryptography extension is required in order to access all certificate fields using the Issuer and Subject properties of the CryptoCertificate object.