Version 8.3.8
Version 8.3.8 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.8
New functionality and changes
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | Version 8.3.7 is added to the list of available values of the Compatibility mode property. | Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, and 8.3.6. | In version 8.3.8 you can run configurations created in version 8.3.7 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.8 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.7 for working with the infobase even after the transition to version 8.3.7. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on). |
| Internet-enabled functionality. | Support of Linux trusted certificate directory (/etc/ssl/certs) is implemented. The OSCertificationAuthorityCertificates object enabling cross-OS certificate operations is implemented. The LinuxCertificationAuthorityCertificates object caching certificate data on Linux operating system is implemented. It is recommended that you use the OSCertificationAuthorityCertificates object. The CertificationAuthorityCertificates parameter of OpenSSLSecureConnection object constructor accepts objects of OSCertificationAuthorityCertificates and LinuxCertificationAuthorityCertificates types. NSS certificates are no longer supported. | On Linux operating system, the platform used NSS certificate store. | On Linux operating system, in the thin client, the option to access infobases published on resources that require clent certificates is implemented. |
| Web client, web service, and HTTP service publishing tools. | Support of Apache 2.4 is implemented for Windows and Linux. For the webinst utility, the -apache24 key is implemented. | This feature was not provided. Apache versions 2.0 and 2.2 were supported. | Extended list of supported web servers. |
| Automated testing. | The About 1C:Enterprise window and the title of the client application window indicate whether the client application is a test manager or a test client. The TestedApplication.SetFileDialogResult() method is implemented, it provides the result of an operation performed in the file selection dialog box. The resulting collection of the TestedApplication.GetChildObjects() method now inlcudes windows that contain text or spreadsheet documents. The TestedForm.ExecuteChoiceFromList() method is implemented, it selects a value from the list opened using the ManagedForm.ChooseFromList() method. The TestedForm.ExecuteChoiceFromMenu() method is implemented, it selects a value from the menu opened using the ManagedForm.ChooseFromMenu() method. For the TestedFormField object, the support of form field extension for a text document is implemented. For the TestedFormField object, the support of form field extension for a formatted document is implemented. For the TestedFormField object, the following methods are implemented: GetHTML() (returns the formatted document content) and InputHTML() (emulates entering text to the formatted document). The TestedFormField.WriteContentToFile() method is implemented, it writes the document file to the hard disk (same as the Save command). The method is available for spreadsheet document, text document, and formatted document extensions. | These features were not provided. | Extended automated testing capabilities. |
| Development tools. | The option to save and restore the settings in the configuration comparison and merging window is implemented. A check box that manages automatic automatic saving of the form settings is implemented. The module comparison and merging form is refactored. Now it includes a command bar with the editor commands. The filter settings now include the Show only properties that were changed twice option. | These features were not provided. | Improved usability for applied solution developers who often perform comparison and merging of configurations with custom settings. |
| Development tools. | The following operations are now available as command-line options for batch Designer startup mode:
The following parameters are implemented for /UpdateCfg command-line option of batch Designer startup:
For /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup, the -objects parameter is implemented. This parameter specifies that the operation is performed for a specific set of configuration objects. | These features were not provided. The /ConfigurationRepositoryUpdateCfg command-line option of batch Designer startup was only applicable to the entire configuration. | Simplified automatic update of applied solutions. |
| Queries. | For the query debug, the following operations are inplemented: viewing the list of temporary tables, the structure of temporary tables, and the contents of temporary tables. The Query.ExecuteBatchWithIntermediateData() method is implemented. The TempTablesManager.Tables property is implemented. | This feature was not provided. | Extended applied solution debug capabilities, especially when debugging complex batch queries. |
| External data sources. | The ExternalDataSourceManager.TransactionActive() method is implemented. It determines whether an external data source has a transaction in progress. | This feature was not provided. | The option to determine whether an external data source has a transaction is progress is now available. |
| Web services and HTTP services. | Support of web services that support MTOM standard is implemented Read more.. | This feature was not provided. Web services that supported MTOM standard were not supported. | Extended capabilities for 1C:Enterprise integration with third-party systems. Integration with web services that support optimized transfer of binary data is available, which reduces the network traffic and RAM usage. |
| OData interface. | The following improvements to the standard OData interface are implemented:
| The standard OData interface provided more limited functionality | 1C:Enterprise object presentations better conform to the OData standard requirements. |
| Configuration extensions. Development tools. | The ConfigurationExtension() method is implemented for configuration objects. It is used to determine the configuration extension where the object belongs. For ConfigurationExtensionsManager.Get() method, the ConfigExtensionSource parameter is implemented. If specifies which list of extensions is retrieved (database extensions only; extensions available in the current session; or extensions that were disabled or did not pass the check at the attachment stage). | This feature was not provided. | Simplified configuration extension operations in 1C:Enterprise script. |
| Configuration extensions. | The ConfigurationExtensionCompatibilityMode property of configuration extensions is implemented. This property is used to limit the extension functionality to ensure its compatibility with a specific version of 1C:Enterprise platform, while leaving the option to edit the extension using a later 1C:Enterprise platform version, which provides more features for configuration extensions.The option to create the following objects in configuration extensions is implemented:
In configuration extensions, the option to change the properties of adopted configuration objects, which describe both main and auxiliary forms, is implemented. For adopted reports, the option to change the Main data composition schema property is implemented. In configuration extensions, changing the Picture property of subsystems, command groups, commands, and common commands is available. In the module editor, the context help is only displayed for objects included in the current extension. | These features were not provided. In the module editor, the context help was displayed for both the original configuration and the extension. | Extended configuration extension capabilities. |
| Development tools. Dumping/loading configurations to files. | The option to export external reports and data processors to XML files is implemented. In Designer, the following File menu commands provide this option: Save, Save as, and Save copy. After the export, changing the object type (external report to external data processor or vice versa) is not available. The import is available using the Open command of the File menu. In the external report or data processor editor dialog box, the options to export the report or data processor to files and import it from files are implemented. The export and import commands are available on the Actions menu of the dialog box. The option to compare an external report or data processor with an external report or data processor stored in XML files is implemented. In the external report or data processor editor dialog box, the following Actions menu command provides this option: Compare and merge with external report or data processor. The option to export and import external reports or data processors to or from XML files using the command-line options of Designer batch mode is implemented. The /DumpExternalDataProcessorOrReportsToFiles and /LoadExternalDataProcessorOrReportsFromFiles keys are implemented. Export to both flat and hierarchical file structures is supported. The export is only available in export format version 2.0. The import format is determined automatically during the import. | These features were not provided. External reports and data processors could only be saved in binary format. | Extended capabilities for external report and data processor operations in scenarios that use external version control systems. The option to use external tools for creating and editing external reports and data processors is implemented. |
| Dynamic lists. | For dynamic lists, support of batch queries is implemented. The dynamic list query builder does not support editing batch queries. This change is not implemented in 8.3.7 repository compatibility mode. | Dynamic lists did not support batch queries. | Extended dynamic list capabilities. |
| Development tools. | In the Syntax Assistant, more information is added to the description of the HTTP service request handler method. This includes the parameter type and the return value type. | In the Syntax Assistant, some information was missing from the description of the HTTP service request handler method. It did not provide the parameter type and the return value type. | Easier developer access to critical information. |
New functionality and changes in the 1C:Enterprise mode
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Interface. | In the Taxi interface, the appearance of scroll bars is changed. | In the Taxi interface, scroll bars had a different appearance. | Better visibility of scroll bars in managed forms. |
| Interface. | In the search dialog box that can be opened from a managed form table linked to a FormDataCollection attribute, the order of fields is changed: the Search in field comes before the Find field. | In the search dialog box that could be opened from a managed form table linked to a FormDataCollection attribute, the Find field came before the Search in field. | Unified look and feel of search dialog boxes in managed form fields linked to various data types. |
| Managed forms. | In the Taxi interface, the following keyboard shortcuts are implemented for the managed form navigation panel:
| In the Taxi interface, keyboard shortcuts for moving through navigation panel items were not available.
| Improved usability of 1C:Enterprise client applications that use the Taxi interface. |
| Interface. | In the Taxi interface, in dynamic lists, the vertical scrollbar is replaced with a set of buttons (go to beginning, go to end, page up, and page down) located at the right bottom part of the table linked to a dynamic list. | Tables linked to dynamic lists had vertical scroll bars that did not provide comfortable navigation. | Improved navigation in dynamic lists. |
| Interface. Dynamic lists. | The following commands are added to the context menu of a table linked to a dynamic list whose main table is a document list or a document journal: Post and Clear posting. | For a table linked to a dynamic list whose main table was a document list or a document journal, the Post and Clear posting commands were only available on the More menu.
| Simplified posting and clearing posting in dynamic lists. |
| Interface. Dynamic lists. | The context menu of a managed form table that is linked to the main attribute of a managed list form having the Generate command now includes a Generate submenu. | The generation commands were only available in the command bar of a managed form table linked to the main attribute of a managed list form. | Simplified document generation based on dynamic lists.
|
| Interface. | In the thick and thin clients, in the managed mode, the option to add a search string to the system command area is removed from all interface modes. | The option to add a search string to a system command area was available. | Removed a feature that was no longer in use. |
| Interface. | The system command area displays the current user name. It is a hyperlink that opens a dialog box with the user info. The dialog box includes the option to log out of the client application. If the user is authenticated using OpenID, this also cancels OpenID authentication (so that a single command both exits the application and cancels OpenID authentication). If the infobase does not have users, the user name is not displayed. The option to specify the URL that is opened after the exit from the web client in the .vrd file is implemented (you can also specify the URL in the publishing settings dialog box in Designer, and then the platform writes it to the .vrd file). The <exitURL> element of the <point> element of default.vrd file is implemented. This change is not implemented in 8.3.7 compatibility mode. | The exit command and the cancel OpenID authentication command were available on the File menu. | Client application behavior is closer to the standard behavior of web applications. |
| Web client. Managed forms. | In the web client, streamlined the undo operation in text document fields and input fields. In Safari web browser for Apple iPad, the undo operation is applied to an entire word (and not to each of its characters), just like it is implemented in other web browsers. | In the web client, the undo and redo operations were not optimal. | Improved usability of text operations in the web client. |
| Client application. | On Windows 7 and later and on Linux with Unity desktop shell, support of jump lists is implemented. The last used infobases are automatically added to a jump list, so that a user can open these infobases without opening the 1C:Enterprise start dialog box. On Windows 7 and later, the option to define buttons that are displayed in the application preview taskbar window (using 1C:Enterprise script) is implemented. This is similar to Windows Media Player buttons in its preview window. On Windows 7 and later and on Linux with Unity desktop shell, the option to define a picture or a number to be displayed at the bottom right corner of the application taskbar icon (using 1C:Enterprise script) is implemented. On Windows XP and later and on Linux with Unity desktop shell, the option to enable blinking of a taskbar application icon (using 1C:Enterprise script) is implemented. The OSTaskbarManager object is implemented. | This feature was not provided. | Inproved usability of 1C:Enterprise applications on some operating systems. |
| Client application. Interface. | 1C:Enterprise user interface now has screen reader support, which provides accessibility for blind and visually impaired people. This option is available on Windows XP or later. It uses the NVDA Read more. screen reader software. Screen reader support is only available for managed forms, in the thick and thin clients that use the Taxi interface. | This feature was not provided. | Improved 1C:Enterprise usability for blind and visually impaired people due to screen reader support. |
| Dynamic lists. | In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) is implemented. Adding subordinate fields is available for fields whose type includes at least one reference type. | In dynamic lists, the option to add subordinate fields to fields of composite type in the form customization dialog box (the Change form command on the More menu) was not available. | Improved data display capabilities in dynamic lists. |
| Web client. File operations. | In the web client, a CreateDirectory() or BeginCreatingDirectory() method call includes the question to the user: Do you want to create the DirectoryName directory? In the RequestUserPermission() method call, this confirmation is included in the final question to the user (provided that the confirmation is needed). | In the web client, directories were created without user confirmation. | The platform behavior conforms to the general security recommendations for file operations in the web client. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Server clusters. | Optimized operations with session data. The lags experienced by end users during the periods of high load on the session data storage in client/server mode are eliminated. | Operations with session data required optimization. End users experienced lags during the periods of high load on the session data storage in client/server mode. | Improved 1C:Enterprise usability. |
| Interface. | The impact on the total number of opened forms to the opening of new forms is reduced. | The impact on the total number of opened forms to the opening of new forms was significant. | Streamlined form opening when many other forms are open. |
| Queries. | In the query language, <EXPRESSION> OR TRUE expressions are optimized. This change is not implemented in 8.3.7 compatibility mode. | The query language did not feature additional optimization of query texts. | In some scenarios, the optimization increases the performance of dynamic lists and access restriction queries because the DMBS generates a simpler query plan. |
| Development tools. | The dump configuration to files and restore configuration from files operations are optimized for scenarios where the configuration includes a large number of managed forms. | The performance of dump configuration to files and restore configuration from files operations was insufficient. | In scenarios where the configuration is stored in an external system, improved performance of data exchange between the infobase and that system. |
| Database operations. | File infobase operations are optimized in the scenario where all of the following conditions are met:
| In the specified scenario, the file infobase performance was insufficient. | Improved performance of database configuration updates for file infobases in the scenario where Designer and the database are located on different computers. |
| Data exchange. | The performance of initial infobase image creation is improved. The performance or reading records from independent nonperiodic information registers during the initial image creation is improved. | The performance of initial infobase image creation was insufficient. | Faster creation of subordinate node infobases in distributed infobases. |
| DBMS operations. | Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized. | The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient. | Improved performance of temporary table operations. |
| DBMS operations. | In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) have a different execution algorithm when applied to lists containing more than 100 records. This change is not implemented in 8.3.7 compatibility mode.
| In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) had a different execution algorithm when applied to lists containing more than 1000 records. | Improved performance for some scenarios that include access to Oracle Database DBMS. |
| Administration tools. Technological log. Server clusters. DBMS operations. | Getting DBMS lock data is optimized. The time required for getting the data does not depend on the number of infobases in the cluster. The server cluster service that collects DBMS lock data is implemented. It is named AuxiliaryService (Utility cluster service). The option to manage the collection of DBMS lock data is implemented in the technological log (<DBMSLOCKS> element). Enabling the data collection increases the DBMS load. | The time required for getting DBMS lock data depended on the number of infobases in the cluster. The option to manage the collection of DBMS lock data using the technological log was not available.
| Extended database diagnostics. |
| Administration tools. Database operations. | In the file mode, infobase operations are optimized. The option to change the page size of the infobase file (1Cv8.1CD) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes. Infobases created using 1C:Enterprise version 8.3.8 ot later have page size 8192 bytes and cannot be opened by earlier 1C:Enterprise versions. 1C:Enterprise version 8.3.8 can open infobases created in the earlier versions without changing their compatibility modes. To migrate data between version 8.3.8 and an earlier version, you can use a .dt file or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion. | Pages of the infobase file had fixed size: 4096 bytes. The option to change the size was not available. | Reduced infobase opening time for infobases with large page sizes, and reduced query execution time. |
| Server clusters. | Reduced size of session data on the hard disk. Session data is stored in the server cluster in compressed form. | Session data was stored in the server cluster in uncompressed form. | The space occupied by internal cluster data is reduced. Some of the internal cluster operations are streamlined. |
| Managed forms. Development tools. | The first opening of a managed form in the Designer editor is now faster. | The first opening of a managed form in the Designer editor took more time. | Reduced waiting time for a managed form operation. |
| Client application. | Faster thin client startup in the file mode. | The performance of the thin client startup in the file mode was insufficient. | Faster thin client startup in the file mode. |
Changes that affect system behavior
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Software licensing. Administration tools. | The command-line utility for software license management (which includes license activation, getting license data, getting the list of licenses, and more) is implemented. The utility is delivered in two distribution packages, which are located in the ExtDst subdirectory of the platform version directory (provided that the thick client or 1C:Enterprise server is installed for this platform version). The utility is not installed automatically. In order to use it, you have to install it first. The utility is available for Windows operating system (both architectures) and for Linux operating system (both architectures, as .deb- and .rpm packages). To access the utility, use the ring license command. The utility requires Java version 8. The detailed utility description is available in 1C:Enterprise documentation. | Software license activation was only available in the interactive mode. No other software management options were available. | Simplified software license management on the end-user computer. |
| Managed forms. | During the automatic generation of managed form items, the names of items that match the CreateByParameter and ShowInList commands are generated according to the following template: <Form><CommandName><ConfigurationObjectName>. This change is not implemented in 8.3.7 compatibility mode. | During the automatic generation of managed form items, the names of items that matched the CreateByParameter and ShowInList commands were generated according to the following template: <Form><CommandName><SequentialNumber>.
| Better usability for applied solution developers. |
| Managed forms. | In a managed form, the width of a drop-down list of an input field is adjusted according to the width of data displayed in that list. Pressing the Home or End key (as a single key or with any modifier keys) is handled directly in the input field. | In a managed form, each drop-down list of an input field had a fixed width set by the platform or by a developer. Pressing the Home or End key (as a single key or with any modifier keys) in an input field had no effect. | Improved usability of input fields in drop-down lists. |
| Development tools. | The following features are implemented in the compare and merge modules window :
The following features are implemented in the window that displays the result of merging with a third-party tool:
When a supported configuration is being updated, the compare and merge configurations window has a new filter option: Show only properties with merge conflicts. The filter displays the objects that are not merged with a third-party tool. | This feature was not provided. | Improved usability for developers working on applied solution update functionality. |
| Development tools. | The Explanation field of the property palette displays Russian property names only when the Russian 1C:Enterprise script variant or the Russian platform interface is selected. | The Explanation field of the property palette always displayed both Russian and English property names.
| Improved Designer usability for English-speaking developers. |
| Web client. Spreadsheet documents. | In the web client, the option to display a background picture and a pattern in a spreadsheet document cell is implemented. | In the web client, displaying background pictures and patterns in spreadsheet document cells was not supported. | Extended spreadsheet document style options in the web client. |
| Data display. Spreadsheet documents. | In spreadsheet documents exported to PDF format, font substitution for characters that are not available in the current font is implemented. This change is not implemented in 8.3.7 compatibility mode.
| In spreadsheet documents exported to PDF format, characters that were not available in the current font were displayed as missing characters (squares). | In spreadsheet documents exported to PDF format, non-English characters are displayed correctly. |
| Spreadsheet documents. | When a spreadsheet document is exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells is implemented. This option is not available when exporting spreadsheet documents to XLS (Microsoft Excel 95) format. This change is not implemented in 8.3.7 compatibility mode. | When a spreadsheet document was exported to XLS (Microsoft Excel 97) format, Microsoft Office OpenXML (Microsoft Excel 2007-2010) format, or ODS (OpenDocument) format, the option to add pictures to spreadsheet document cells was not supported. | Better conversion of spreadsheet documents to Microsoft Excel and ODS formats. |
| Configuration extensions. | When an attribute of composite type that does not include references to configuration objects is adopted, the composite type is fully adopted. During the next adoption attempt, the composite type is supplemented with the set of types from the main configuration. When an attribute of composite type that includes references to configuration objects (nonprimitive types) is adopted, it is adopted as AnyRef. During the next adoption attempt, the AnyRef type is only added if the type is no longer composite and does not include CatalogRef, DocumentRef, and similar types. When a configuration extension is attached, the following rules apply:
If an attribute of composite type cannot include AnyRef type, any composite type adopted for this attribute is adopted with a single Arbitrary type. Such attributes cannot cause configuration extension attachment errors. | When a composite type was adopted, primitive types were always adopted, and a single type from the configuration object reference types was adopted. When a configuration extension was attached, the following rule applied: if an extension attribute type included composite types, this required the matching main configuration attribute to include exactly the same composite types. | Simplified usage of composite types in configuration extensions. |
| Web services and HTTP services. | During a web service call, if an internal server infrastructure error that is not related to SOAP occurs, the error message contains the correct diagnostics text. The web service call error message is more detailed and can include data from the faultfactor (Node) and Role tags of the web service response. | During a web service call, if an internal server infrastructure error that was not related to SOAP occurred, an incorrect error message was displayed, and the information about the actual error cause was lost. The web service call error message did not include additional details from the web service response.
| The web service call error message is more detailed, which simplifies error diagnostics. |
| Background and scheduled jobs. | When a client application is started with a file infobase, there is a 2-minute delay before starting the execution of scheduled jobs. | When a client application was started with a file infobase, there was a 1-minute delay before starting the execution of scheduled jobs. | Faster startup of client applications in file mode. |
| Web client, web service, and HTTP service publishing tools. | When a user disables publishing to a web server from Designer, they are prompted to restart the web server. | When a user disabled publishing to a web server from Designer, they were not prompted to restart the web server. | Users are given better understanding of the disable publishing operation, since the publishing is actually disabled when the server is restarted. |
| Development tools. | In Designer, the option to customize the background of the context method parameter help is implemented. In the context help, links to the Syntax Assistant have the Identifiers color and normal text has the Miscellaneous color. | In the context help, links to the Syntax Assistant had the default Identifiers color and normal text had the default Miscellaneous color. | You can customize the context help of method parameters to make it readable when the module editor color scheme has dark background. |
| XML and XDTO support. Web services and HTTP services. | In the XDTO model, new properties are implemented. They ensure correct processing of XSD schemas with any combinations of the following attribute values: elementFormQualified (Qualified element form package property), attributeFormQualified (Qualified attribute form package property), and form (property of the Qualified element). | When processing XSD schemas, the XDTO model ignored actual values of elementFormDefault and attributeFormDefault attributes. It also ignored the form attribute of XSD schema elements and attributes. Instead, it always used the following values:
| Extended list of web services that are compatible with 1C:Enteprise as they are, without any manual corrections to their descriptions. |
| Administration tools. | The wizards used to add and edit infobases are refactored, the number of wizard pages is reduced. Automatic detection of the infobase connection type is implemented, based on the string stored in the clipboard or the string entered in the Specify infobase name field. This includes the detection of the path to a file infobase or the URL for accessing an infobase running on a web server. Once the infobase type is detected, all of the related wizard fields are filled in. | The wizards used to add and edit infobases were more complex and had more pages. | Simplified adding of infobases to the list. |
| Managed forms. | If an input field of a managed form displays ValueList data, the value list form that is opened for editing the data gets the following properties from the input field:
| If an input field of a managed form displayed ValueList data, the value list form that was opened for editing the data received the following properties from the input field:
| Eliminated unexpected system behavior. |
| Full-text search. Input by string. Dynamic lists. | Input by string and full-text search in dynamic lists find data that is not yet indexed for the full-text search. | Input by string and full-text search in dynamic lists did not find data that was not yet indexed for the full-text search. | Data that is not yet indexed for the full-text search is included in full-text search results and input by string results. |
| Managed forms. | In the Taxi interface, the appearance of managed form buttons and command bar buttons is changed. For the CommandBarButton and CommandBarHyperlink buttons, support of the following properties is implemented: BackColor, TextColor, Font, BorderColor (except CommandBarHyperlink buttons). For form group extension submenus, support of the following properties is implemented: BorderColor, BackColor, TitleTextColor, and TitleFont. This change is not implemented in version 8.3.7 compatibility mode and in version 8.2 interface compatibility mode. For the standard Copy command of dynamic list table extension:
For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property is equivalent to No. These commands are included in a compact button group. This change is not implemented in version 8.3.7 compatibility mode. In version 8.3.7 compatibility mode with compact interface the button height in the thin client differs from the button height in the web client. | In the Taxi interface, the appearance of managed form buttons and command bar buttons was different. The CommandBarButton buttons had BackColor, TextColor, Font, and BorderColor properties, which were never used. Form group extension submenus had BorderColor, BackColor, TitleTextColor, and TitleFont properties, which were never used. For the standard Copy command of dynamic list table extension:
For MoveUp and MoveDown managed form table commands, the Auto value of the OnlyInAllActions property was equivalent to Yes. | Improved form creation capabilities in the Taxi interface. The default location of some frequently used buttons (Copy in dynamic lists and row movement commands in other tables) changed from the More menu to the command bar. |
| Managed forms. | The option to display command bar commands as hyperlinks is implemented. Pop-up menus do not support displaying commands as hyperlinks. For the FormButtonType enumeration, the CommandBarHyperlink value is implemented. In 8.3.7 compatibility mode, the FormButtonType.CommandBarHyperlink value is treated as FormButtonType.CommandBarButton. In the Taxi interface, the option to set horizontal picture alignment for managed form buttons is implemented. Pop-up menus do not support this feature. For managed form buttons, the PictureLocation property is implemented. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. The option to set command bar button spacing is implemeneted. Managed form group extension for a button group is implemented. Pop-up menus do not support this feature. The ButtonGroupRepresentation system enumeration is implemented. In 8.3.7 compatibility mode and version 8.2 interface compatibility mode, the button spacing value is ignored. The option to set button shape (except pop-up menu buttons) is implemented. For managed form buttons and form group extensions for popups, the Shape property is implemented. Pop-up menu commands do not support this property. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. The option to set managed form button shape is implemented. For managed form buttons and form group extensions for popups, the ShapeRepresentation property is implemented. The ButtonShapeRepresentation system enumeration is implemented. Pop-up menu commands do not support this feature. This property is ignored in 8.3.7 compatibility mode and version 8.2 interface compatibility mode. | Command bar commands could not be displayed as hyperlinks. The option to set horizontal picture alignment for managed form buttons was not available. The option to set command bar button spacing was not available. The option to set button shape was not available. The option to set command bar button appearance was not available. | More managed form appearance options in the Taxi interface. |
| Managed forms. | Recommendations about the usage of user messages are added to the documentation. The recommendations are aimed to reduce the chance of situations where users cannot read the displayed messages. | The documentation did not contain the recommendations aimed to reduce the chance of situations where users cannot read the displayed messages. | The documentation is improved. |
Changes that require modification of configuration and administrative settings
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Internet-enabled functionality. | The NSSSecureConnection object and NSS certificates are no longer available for use in 1C:Enterprise script. | 1C:Enterprise supported NSS certificates in 8.3.6 compatibility mode. | Support of NSS certificates is discontinued. |
| Internet-enabled functionality. | Support of TLS protocol versions 1.1 and 1.2 is implemented for scenarios where the client certificate is not specified in the connection settings. The SSL protocol version 3.0 is only used when the client application is started with /HttpsForceSSLv3 command-line option. In all other scenarios SSL version 3.0 is not used. 1C:Enterprise ignores the AllowSSLv3 parameter in conf.cfg file. The InternetMail object does not support SSL version 3.0. | 1C:Enterprise only supported TLS protocol version 1.0. The AllowSSLv3 parameter was available for use in conf.cfg file. The InternetMail object supported SSL version 3.0.
| Increased security of connections established by client applications for Internet operations. |
| Internet-enabled functionality. | The platform no longer uses cacert.pem file for creating HTTPS/FTPS connections. The platform uses the root certificate store of the operating system for creating HTTPS/FTPS connections. This change is not implemented in 8.3.7 compatibility mode. | The platform used cacert.pem file for creating HTTPS/FTPS connections in scenarios where no certificate stores were specified explicitly. | The outdated technology is no longer supported. |
| Managed forms. | For managed forms, the option to update data presentations only for the specified set of form items is implemented. For the RefreshDataRepresentation() method, the UpdateItems parameter is implemented. For the EditTextUpdate system enumeration, the Always value is implemented. | The option to specify a set of form items when updating data presentations using the RefreshDataRepresentation() method was not available. | Form data can be updated in idle handlers without losing the text being edited in a text box. |
| Dumping/loading configurations to files. | The dump of the Source property of the FormItemAddition object to a file is more human-readable. You can restore configuration from files having both property dump formats. | The dump of the Source property of the FormItemAddition object to a file was less human-readable. | Dumping configurations to files produces files that are more human-readable. |
| XML and XDTO support. Development tools. | Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) is much more detailed. During the creation of WSDefinitions object, exceptions are raised if the used WSDL description has errors. The WSDL description used to create WSDefinitions or WSReference objects must comply with the following rules:
This change is not implemented in 8.3.7 compatibility mode. | Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) was not sufficiently detailed. During the creation of WSDefinitions object, if the used WSDL description had errors, invalid elements were ignored. If the first tag of the WSDL description used to create WSDefinitions or WSReference objects was not <definitions>, empty web service description objects were created. If the WSDL description used to create WSDefinitions or WSReference objects did not include the targetNamespace attribute of the <xs:schema> element, the platform set a pseudorandom namespace. | Better diagnostics for WSDL description operations. |
| Queries. | If a constant stores a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that includes a request to the Value field returns a value of that type. This change is not implemented in 8.3.7 compatibility mode. | If a constant stored a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that included a request to the Value field returned a value of BinaryData type. | Eliminated unexpected system behavior. |
| Print tools. | The following behavior of the RepresentableDocumentBatch.Print() method is implemented:
This change is not implemented in 8.3.7 compatibility mode. The RepresentableDocumentBatch.Title, property is implemented. It is used for generating the batch presentation. | The RepresentableDocumentBatch.Print() method created a job for each document in a batch. | Improved printing of document batches. |
| Data composition system. | Text and Format conditional appearance items are applied to fields of chart grouping templates of data composition systems regardless of the previous Format value (even if the previous value is taken from the data composition system). Text conditional appearance item has higher priority than Format conditional appearance. This change is not implemented in 8.3.7 compatibility mode. | Text and Format conditional appearance items were applied to fields of chart grouping templates of data composition systems only if the Format conditional appearance was not applied to those fields earlier. | Eliminated unexpected system behavior. |
| Data composition system. | The MarkNegatives conditional appearance property is only used if this property is set to True and the Use conditional appearance property is also set to True. This change is not implemented in 8.3.7 compatibility mode. | The MarkNegatives conditional appearance property was only used if the Use conditional appearance property was set to True. | Eliminated unexpected system behavior. |
| Data composition system. | In the query language, the CASE operation result is based on all expression types from all THEN branches of that expression. This change is not implemented in 8.3.7 compatibility mode. | In the query language, the calculation of CASE operation result ignored all THEN branches that included constant expressions with NULL values. | Eliminated unexpected system behavior. |
| XML and XDTO support. | Serialization of a ValueList object using the XDTOFactory.WriteXML() method creates an XML document based on the schema used for serialization of this object with XDTOSerializer.WriteXML() method. This ensures that value lists serialized in platform version 8.3.7 can be read in version 8.3.6 (and vice versa), and also ensures the same behavior for versions 8.3.8 and 8.3.7 (in the compatibility mode). Value lists serialized in version 8.3.8 (no compatilibity mode) cannot be deserialized in earlier platform versions. This change is not implemented in 8.3.7 compatibility mode. | Serialization of a ValueList object using the XDTOFactory.WriteXML() method created an XML document that did not match the schema used for serialization of this object with XDTOSerializer.WriteXML() method. | This change is not implemented in 8.3.7 compatibility mode. |
| Full-text search. | The option to set a size limit for data indexed for the full-text search is implemented. The default size limit is 1 MB. For the FullTextSearchManager object, the SetMaxIndexedDataSize() and GetMaxIndexedDataSize() methods are implemented. The <FTEXTSKIP> technological log event is implemented. This change is not implemented in 8.3.7 compatibility mode. | The option to set a size limit for data indexed for the full-text search was not available. All infobase data was indexed. | You can limit the full-text search scope by excluding large blocks of data you do not need to search. This increases the performance of full-text search indexing and reduces the index size. |
| Client application. Internet-enabled functionality. Administration tools. | The algorithm that retrieves the list of infobases and platform updates over HTTPS no longer uses the cacert.pem file, which is included in the platform distribution kit. On Linux, the platform gets certificates from the certification centers specified in the operating system. On Windows, the platrorm uses the operating system root certificate store. | On Windows, the platform used the cacert.pem file and the operating system root certificate store in order to check an HTTPS connection. On Linux, the platform used the cacert.pem file only. | Simplified administration of platform update over HTTPS. |
| Linux. System requirements. | The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system is refactored. The fontconfig library is used to get the list of fonts. This library is included in the system requirements. The list of directories used for storing fonts is removed from 1C:Enterprise documentation. | The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system used a fixed directory list, which was described in 1C:Enterprise documentation. The fontconfig library was not used for getting the list of fonts. | Extended the list of fonts available to 1C:Enterprise on Linux operating system. Simplified 1C:Enterprise administration. |
| System requirements. | The type specified for a data composition schema parameter affects the type of query fields that use this parameter. This change is not implemented in 8.3.7 compatibility mode. | The type specified for a data composition schema parameter did not affect the type of query fields that used this parameter. | Data displayed in reports better matches the input parameters. |
| Dynamic lists. | The dynamic list implementation is refactored in order to increase its quality. The list of virtual dynamic list fields that are not available for use in filter, grouping, and order settings is extended. If the main dynamic list table does not have key fields (according to 1C:Enterprise script object model) and a grouping is set for this table, an error is generated. When a filter, sorting, or grouping by a field that is not included in the query is specified using 1C:Enterprise script, an error informing that the field is not found is displayed. The list of restrictions to queries used to generate dynamic lists is modified. Dynamic list sorting specifics are described in the documentation. The description of algorithms used by dynamic lists for getting data is changed. The standard row picture is generated based on the standard attributes. If a query includes fields whose aliases are identical to standard attribute names and these fields store other data, these fields are not used in standard picture generation. If a dynamic list filter cannot be converted to a query language clause, an error is generated. Dynamic list column data that is not displayed and does not have the Use always property set is not sent to the client. Client access to these columns is not available. The detailed description of all the changes listed above is included in the documentation. This change is not implemented in 8.3.7 compatibility mode. | The following virtual fields were not available in the dynamic list sorting and grouping settings: DataVersion, PredefinedDataName, tabular sections fields, and fields having the following types: Type, String (unlimited length), and BinaryData (unlimited length). The list of restrictions to the grouping and ordering settings was different and it was not full. If the main dynamic list table did not have key fields (according to 1C:Enterprise script object model) and a grouping was set for this table, the content of data to be displayed was undefined. When a filter by a field that was not included in the query text was set, the filter might be applied without displaying any errors, or ignored. If grouping or sorting by a field that was not included in the query was specified using 1C:Enterprise script, the field was ignored. The list of restrictions to queries used to generate dynamic lists was different. The list of dynamic list sorting specifics was not documented. The description of algorithms used by dynamic lists for getting data was different. If a dynamic list query had fields with aliases matching the names of standard attributes used to generate standard row pictures, they were used in the generation of standard pictures (except the IsFolder attribute). If a dynamic list filter could not be converted to a query language clause, the filter was applied by data composition schema processor after getting the data, and this might reduce the amount of displayed data. If dynamic list settings included grouping or sorting fields that were unavailable (before applying rights and functional options), these fields were ignored. In some scenarios dynamic list column data that was not displayed and did not have the Use always property set was sent to the client. | Improved quality and reliability of dynamic lists. More details about dynamic list specifics are added to the documentation. |
| Background and scheduled jobs. | When a nonserializable value is passed to BackgroundJobs.Execute() method as a background job parameter, the background job is not started and an exception is raised. This change is not implemented in 8.3.7 compatibility mode. | When a nonserializable value was passed to the BackgroundJobs.Execute() method as a background job parameter, the background job was started and the Undefined value was stored to that parameter. This did not raise any exceptions. | The start of background jobs complies with the global error diagnostic rules. |
| Administration tools. | During an unexpected shutdown of the thin client, the dump generation includes taking a screenshot (prntscrn attribute of dump element of logcfg.xml file).
| During an unexpected shutdown of the thin client, the dump generation did not include taking a screenshot. | Eliminated unexpected system behavior. |
| Queries. | The result of division by NULL is treated as a number of unspecified length . This number cannot be used in operations that do not accept numeric operands (such as AND, OR, NOT). This change is not implemented in 8.3.7 compatibility mode. | The result of division by NULL was not treated as a number and therefore could be used in operations that did not accept numeric operands (such as AND, OR, NOT). | Eliminated unexpected system behavior. |
| Managed forms. Interface. | The approach to processing the closing of applications and managed forms is changed:
This approach is described in detail in the documentation. For BeforeClose managed form event handler, the Exit and WarningText parameters are implemented. For OnClose managed form event handler, the Exit parameter is implemented. For BeforeExit managed application module event handler, the WarningText parameter is implemented. This change is not implemented in 8.3.7 compatibility mode. | Depending on the modality usage mode, different approaches to closing managed forms and the main application window were used. In some scenarios (especially in the web client) these approaches led to errors that were hard to detect and fix. | Unified approach to closing forms and the main application window, which provides acceptable user interaction capabilities in all client applications. The implemented platform behavior conforms to the methodology and technical requirements of modern web browsers. |
| Administration tools. Client application installation. | When an infobase that has a platform version specified in a local or global list of infobases is started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version is performed regardless of the presence of /AppAutoCheckVersion command-line option. If a version that is not available on the local computer is specified and this version cannot be installed, an attempt to run the infobase with the latest 1C:Enterprise version is made During the client application update over HTTP, the check for operating system user right to perform this operation is disabled. If the user does not have sufficient rights for installing the client application, the UAC dialog box prompting to confirm the installation on behalf of a user that has administrative rights is displayed. Error diagnostics during the download and installation of the client application distribution kit over HTTP is improved. In the /AppAutoCheckVersion command-line option, you can explicitly specify whether the search for a specific 1C:Enteprise version is performed. | When an infobase was started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version was only performed if the command line included the /AppAutoCheckVersion option. During the client application update over HTTP, the check for operating system user right to perform this operation was performed. | The usability of selection and update of the client application used to access a specific infobase is improved. Improved reliability of automatic thin client updates over HTTP. |
| Administration tools. | When the thin client is installed from a custom distribution kit, a single 1cestart shortcut is created in the 1C:Enterprise folder. | When the thin client was installed from a custom distribution kit, the 1C:Enterprise folder included 1cestart shortcut and the Advanced folder with subfolders for each installed 1C:Enterprise version. | Reduced number of 1C:Enterprise startup options available after the installation of the thin client. |
| Administration tools. | In the client application startup command line, the rules for parsing mandatory parameters are modified. If an option that has a mandatory parameter is specified, the parameter must be also specified (or the option must be omitted). Parameters beginning with slash marks "/" are allowed. | In the client application startup command line, the rules for parsing mandatory parameters were different. Mandatory option parameters could be omitted. Parameters beginning with slash marks "/" (full file name on Linux) could be treated as command-line options. | Eliminated unexpected system behavior. |
| Administration tools. | 1C:Enterprise documentation and Designer help include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode, which were previously missing. For the infobase creation mode (CREATEINFOBASE), new /DumpResult option is implemented. It enables writing the operation result to a file. In the file mode, batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option automatically creates an infobase if the database file is not available in the directory. | 1C:Enterprise documentation and Designer help did not include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode. In the file mode, during the batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option, if the dababase file was not found in the specified directory, the user was asked for the confirmation of further actions. | Improved 1C:Enterprise documentation and Designer help. Simplified batch Designer startup in some usage scenarios. |
| Data composition system. | If a data set field of a data composition schema has an ordering expression specified and the data composition settings include ordering by this field (Descending), the direction speficied in the ordering expression is reversed. This change is not implemented in 8.3.7 compatibility mode. | If a data set field of a data composition schema had an ordering expression specified, ordering for this field was always taken from the ordering expression, while the direction specified in the field settings was ignored. | Eliminated unexpected system behavior. |
| Managed locks. Accounting registers. | Managed locks that are set for writing accounting register records in the LockForUpdate mode are set by values of nonturnover extra dimensions only. When you set a lock for further operations with balances, it is recommended that you do not specify turnover extra dimension values (you can use the LockForUpdate property or explicitly use a managed lock). When you set a lock for further operations with turnovers, specify all the required extra dimenstion values, including the values of turnover extra dimensions (use the managed lock explicitly). This change is not implemented in version 8.3.7 compatibility mode. | Managed locks that were set for writing accounting register records in the LockForUpdate mode included locks by all extra dimension values. | The behavior of LockForUpdate property of accounting register object is better suited for solving typical tasks. In the LockForUpdate mode, the resulting lock does not inlcude turnover extra dimensions, which fits the frequently used scenarios where the lock is used to check the balances but not the turnovers. |
| Queries. | In a query, if a single system enumeration is retrieved and it is not combined with other types, the GROUP BY operation groups the values of this field regardless of the enumeration value source. A similar behavior is implemented for UUIDs and references to external data source tables. This change is not implemented in 8.3.7 compatibility mode. | In a query, if a single system enumeration was retrieved and it was not combined with other types, the GROUP BY operation might not group the values of this field (depending on the enumeration value source). | Eliminated unexpected system behavior. |
| DBMS operations. | For Microsoft SQL Server DMBS, types of table fields that store some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) are changed. New field types are used if no compatibility mode is selected and only after restructuring configuration objects. To perform database table restructuring with modification of field types, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair). This change is not implemented in 8.3.7 compatibility mode. | For Microsoft SQL Server DMBS, table fields that stored some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) had different types. | Better mapping between the stored types and Microsoft SQL Server table field types. |
| DBMS operations. | For all DBMS, the structure of indexes by fields of composite type is modified. This reduces the total number of indexes. Such indexes are built if no compatibility mode is selected and only after restructuring configuration objects. To perform database table restructuring with index update, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair). This change is not implemented in 8.3.7 compatibility mode. | For all DBMS, the structure of indexes by fields of composite type was different. | Reduced number of indexes for tables storing objects with fields of composite types. This increases the performance of operations with these object types. |
| Configuration extensions. | When a background job is executed, all the configuration extensions available in the session that startes the job are also attached in the background job session. This change is not implemented in 8.3.7 compatibility mode. For ConfigurationExtensionsManager object, the ExecuteBackgroundJobWithDatabaseExtensions method is implemented. It duplicates the background job execution procedure implemented in earlier 1C:Enterprise versions. | When a background job was executed, all the configuration extensions available in the infobase were attached in the background job session. | Background job execution environment is closer to the parent session environment. |
| Managed forms. | In the thick and thin clients, when a user starts typing in a cell of a managed form table, the AutoComplete event is fired. This change is not implemented in version 8.3.7 compatibility mode. | In the thick and thin clients, when a user starts typing in a cell of a managed form table, the StartChoice event is fired. | The behavior of the input field in the scenario where a user starts typing in a table cell is uniform with other input scenarios. |
Renamed objects
Mobile platform
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Development tools. Mobile application builder. | In the mobile platform, support of in-app billing services is added. This includes Apple In-App Purchase (for iOS) and Google Play In-App Billing (for Android). Support of in-app billing for Windows is not provided. The In-app purchases mobile application permission is implemented. The InAppPurchases, InAppPurchase, InAppPurchaseReceipt, and InAppPurchasesValidation objects are implemented. In the desktop platform, the InAppPurchasesValidation object is implemented. It is intended for testing in-app purchase algorithms. In the mobile platform for developers, a service providing an API similar to Google Play In-App Billing is implemented for Android operating system. It is intended for debugging in-app purchase algorithms. The option to test the full purchase cycle is implemented. This includes the purchase creation and the emulation of some related scenarios. The HTTP service (named PurchaseTest) and the testing tools are provided by the mobile application builder. The mobile application builder supports building mobile applications with in-app purchases. | This feature was not provided. | The option to implement purchases and subscriptions in mobile applications is available. You can create applications with paid features. |
| Development tools. Mobile application builder. | For mobile applications, the option to display ads is implemented. It uses iAd service (for iOS) and AdMob service (for Android). Displaying ads on Windows is not supported. The AdRepresentation object is implemented. Mobile application builder supports applications that display ads. | This feature was not provided. | The option to create mobile applications with advertising monetization model is available. |
| Spreadsheet documents. | Exporting spreadsheet documents fo PDF format is implemented. | This feature was not provided. | More options for data presentation in mobile applications. |
| Data display. | On Android version 4.1 or later, numbers are displayed correctly if the NG parameter of the Format function contains two groups. | On Android version 4.1 or later, numbers were displayed incorrectly if the NG parameter of the Format function contained two groups. | Eliminated unexpected system behavior. |
| File operations. | In the mobile platform, support of asynchronous file operation methods is implemented (this includes global context methods and the File object). | This feature was not supported by the mobile platform. | Improved parallel code implementation for both mobile and desktop platforms. |
| Full-text search. | On the mobile platform, support of FullTextSearchManager.CheckIndex() method is implemented. In the Syntax Assistant, methods of FullTextSearchManager object are marked as available on the mobile platform. | This feature was not supported by the mobile platform. The Syntax Assistant erroneously stated that methods of the FullTextSearchManager object were not available on the mobile platform. | Extended full-text search support on the mobile platform. The Syntax Assistant description is up-to-date. |
| Internet-enabled functionality. | On the mobile platform, when specifying request body as a string for an HTTPRequest or HTTPServiceResponse object, you have the option to include BOM characters to the request or exclude them. On the mobile platform, the ByteOrderMarkUsage system enumeration is implemented. | This feature was not supported by the mobile platform. | Simplified mobile application integration with systems that do not expect BOM characters in HTTP requests. |
| Common objects. | The MobileDeviceApplicationRun object is now available on iOS and Windows platforms. The MobileDeviceApplicationRun.RunningSupported method is implemented to test the availability of this feature. Developers can use this method to determine whether their mobile devices support running external applications. | The MobileDeviceApplicationRun object was not available on iOS and Windows platforms. | The platform behavior related to functionalities that are not available on some mobile devices or operating systems is unified across all platforms.
|
| Managed forms. | In the Syntax Assistant, more information is added to the descriptions of Activate by default and Default button managed form items. The Unfilled selection mode property of managed form input fields is available in mobile platform forms. The Row selection mode property of managed form tables is no longer available in mobile platform forms.
| The information in the Syntax Assistant was outdated. The availability of some properties of managed form input fields did not match the capabilities of the mobile platform. | Designer and Syntax Assistant now match the capabilities of the mobile platform. |
| Mobile application builder. | Data storage structure implemented in the mobile application builder is modified. When the mobile application builder is started for the first time after the update, the data conversion may take significant time. | Data storage structure implemented in the mobile application builder was different. | Data storage structure implemented in the mobile application builder is now more efficient. |
| Development tools. | When a debug server that does not support HTTP is specified in a mobile application, the error message clearly explains the problem: The mobile platform only supports debugging over HTTP. | When a debug server that did not support HTTP was specified in a mobile application, the error message did not clearly explain the problem. | Better problem diagnostics during mobile applicatiobn development. |
Library updates
Transition from the previous version to the version 8.3.8
- 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.8.
- Some features that are added in version 8.3.8 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.
- When the Compatibility mode is set to None, the minimum supported version of Microsoft SQL Server is Microsoft SQL Server 2005 (this includes scenarios that use the Native Client).