Version 8.3.17
Version 8.3.17 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 version of "1C:Enterprise"
- Library updates
- Transition from the previous version to the version 8.3.17
New functionality and changes
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.16 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.15 was available. | Configurations developed using 1C:Enterprise platform version 8.3.16 or earlier can now run on version 8.3.17 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.17 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.16 after the migration to version 8.3.17, even if you disable the compatibility mode (simply enable it again). |
| Data display. | New pictures were added to the picture library:
|
The listed pictures were not available in the picture library. | The picture library is upgraded. |
| Error handling. | The following features related to the application running error processing were implemented:
|
These features were not provided. Local processing of recoverable errors was available only. | You can now make error texts easier to understand by end users. Error processing in 1C:Enterprise language was improved. |
| Server clusters. Client application. | When in the client/server mode, you can by default delete temporary files created using GetTemporaryFileName() method on the side of the PC(s) running the server cluster in the following scenarios:
|
Temporary files were only deleted when the 1C:Enterprise processes were started. The system startup speed depended on the number of temporary files to be deleted. | 1C:Enterprise processes performance is improved, if there is a large number of temporary files generated by 1C:Enterprise itself. The risk of running out of space on the hard drivers where the temporary file directories are located is mitigated during prolonged operation without restarting and inaccurate application handling of the temporary files being created. The number of simultaneously existing temporary files with names that were obtained using GetTemporaryFileName() method was reduced. |
| Collaboration system. | Integration with external (with respect to the collaboration system) instant messaging systems was implemented for the collaboration system. Interaction with the following systems is now supported: Telegram, VKontakte. CollaborationSystemIntegration object is supported. CreateIntegration(), GetIntegration(), GetIntegrations(), GetExternalSystemTypes() and GetExternalSystemDescription() methods were implemented for CollaborationSystemManager object. CollaborationSystemUser.ExternalSystemType, CollaborationSystemUser.ExternalSystemUserID, CollaborationSystemConversion.Integration and CollaborationSystemConversationFilter.Integration properties were implemented. | This feature was not provided. | Expanded collaboration system capabilities. |
| Configuration extensions. | You can now borrow event subscriptions and create your own subscriptions in the extension. | This feature was not provided. | Extended configuration extension options. |
| Client application. Data display. System requirements. | You can save a spreadsheet document in Microsoft Excel 97 format in a client application running macOS. In Linux, to save in Microsoft Excel 97, use libgsf-v8 library. Thus, libgsf-1 and libglib-2.0 libraries are no longer required. You cannot save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS. | You could save a spreadsheet document in Microsoft Excel 97 format in Linux only. Nominally, you were able to save a spreadsheet document in Microsoft Excel 95 format in Linux and macOS. However, in practice this feature was unavailable. | Users of client applications running macOS can now save spreadsheet documents in Microsoft Excel 97 format. |
| Development tools. | A technical specialist mode is implemented for a managed client application. The following features are available in this mode for managed forms:
|
This feature was not provided. It was difficult to determine which form is currently used in the client application. | Technical specialists operations as part of application development or deployment process were made easier. |
| Common objects. | You now can identify IP-address of a PC, where an infobase user session was started. IP-address cannot be determined in every instance and in every mode of operation. ClientIPAddress property was implemented for AdministrationSession and InfobaseSession objects. Now, IP-address of a client application can be displayed in the cluster console and standard server management processor. ISessionInfo.getClientIPAddress() property is now available in the administration server interface in Java language. Client-ip field is now available in the command-line utility (rac) of a server cluster. It displays values returned by session info command.. SessionNumber and ClientIPAddress parameters are now available for the onStartSession() method of external session management Web-service. New features are only available, if wsver is assigned 3. | This feature was not provided. | You now can identify IP-address of a PC, where an infobase user session was started. |
| Analytics system. | 1C:Enterprise is now integrated with 1C:Analytics (analytics system). In the publishing settings on the Web server, you can enable analytics system publication. In the Service and Settings menu, Analytics System command is now supported, thus allowing you to open a tab with analytics system in the web browser for the current user. Standard Analytics System Management function is supported to integrate it with the infobase. So far as global context is concerned, AnalyticsSystem property is available. AnalyticsSystemClient access rights are supported. 1C:Analytics is not included in distribution package. Information on this functionality is published separately. | This feature was not provided. | 1C:Enterprise is now integrated with 1C:Analytics (analytics system). |
| Data composition system. | You can pass temporary tables manager to data composition system. In the data composition system, you can use tables that do not exist in the infobase similarly with temporary tables in the query language. The TempTablesManager parameter is now available for the DataCompositionProcessor.Initialize() method. | This feature was not provided. You were able to use temporary tables in the data composition system only as part of a batch query. | Now, you can use pre-defined temporary tables, when a query is executed by the data composition processor. |
| Spreadsheet documents. Charts. | Now, you can manage the way an image selection box is displayed in a spreadsheet document in a client application form. To expand the form field boundaries, DrawingsSelectionView property is supported for spreadsheet fields. This upgrade is ignored in 8.3.13 version compatibility mode. | This feature was not provided. When you selected a chart in a spreadsheet document available in the client application form, the said chart was always highlighted. | Now, it is much more easier to use charts in a spreadsheet document available in the form. |
| Data display. Сlient application form. | Nested dimension items can be created and text in background bands displayed in the Planner.
The PlannerDimensionItem object now supports Items, Parent, and ShowItemsAreaOnlyForSubordinateItems properties.
The PlannerDimensionItemsCollection.Find() method now supports IncludeSubordinates parameter.
To expand the form field, planner filed supports the following:
|
These features were not provided. | Now, you can implement a group of planner dimension items similarly to a group of spreadsheet or hierarchical catalog lines. |
| DBMS operations. System requirements. | Implemented support for the following versions of Oracle Database DBMS:
|
These Oracle Database versions were not supported. | Extended list of supported Oracle Database versions. |
| Integration service. | Integration service creating feature was implemented. Integration services allow to coordinate with the "External integration service" product. The IntegrationServices property of 1C:Enterprise language was implemented. Managing integration services was implemented in standard functions. "External Integration Service" is not included in distribution package. Information on this functionality is published separately. | This feature was not provided. | Interaction with "External Integration Service” was implemented. |
| Web client. | Language support with spelling from right to left is implemented for the web client. This mode is supported automatically in the entire client application interface, with the exception of the following form elements: planner, chart, Gantt chart, dendrogram, graphical schema field and graphical schema field. The requirement to change the interface is determined by the interface language or configuration language. The web client now supports Arabic formats for numbers and dates. When calculating the arrangement of form elements and other interface items, the default font is Almarai. The web client supports using specialized Arabic characters for writing arithmetic expressions. In such cases, the expressions are calculated correctly. | The web client did not support using of languages with right-to-left spelling. | It has become possible to use 1C: Enterprise (using a web client) in countries where the national language uses right-to-left spelling. |
New functionality and changes in the 1C:Enterprise mode
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. File operations. | As soon as you open an external report or data processor file on a web client (without a file system extension installed), there is no need to reopen the selected file after positive feedback to security warning. In a file opening dialog box on a web client, now you can select a filter to search files you need to open (if it is defined, when you open a dialog box). | As soon as you opened an external report or data processor file on a web client (without a file system extension installed), you needed to reopen the selected file after positive feedback to security warning. In a file opening dialog box on a web client, there was no option to define a filter to search files. | Now, you can open an external report or data processor on a web-client (without a file system extension installed) in a easier and user-friendly way. Moreover, it's much more easier to open other files on a web client now. |
| Data display. | Some platform images (including part of image library) now have different appearance (they were redrawn) and are now implemented in SVG format. In the Taxi interface windows appearance was modified. They are now generated by ShowUserNotification() and State() global context methods. | Some platform images (including part of image library) had different appearance, and they were implemented in PNG format. Appearance of windows generated in Taxi interface using ShowUserNotification() and State() global context methods was different. | Visual perception of 1C:Enterprise interface was improved. |
| Error handling. | As soon as you open a dialog box with information for technical support team, the entire text available in the input field is selected by default. | When you opened a dialog box with information for technical support team, text available in the input field was not selected. | Now, you can copy information for technical support team (if necessary) easier and without delay. |
| Global search. Client application. Web client. | The following global search commands are available:
|
Search Everywhere context menu command was available, only if there was a selected text block in the current form element. Search was made by the text block so selected. No text block so searched was added to Search Everywhere command presentation in the menu. | Global search usage was improved. |
| Web client. Spreadsheet documents. | The display of a spreadsheet document containing patterns in cells was optimized when using a web client in case of a slow connection. When saving a spreadsheet document containing patterns in cells in HTML format, the size of resulting HTML document was reduced. | Displaying a spreadsheet document containing patterns in cells took longer when using a web client in case of a slow connection. | Eliminated unexpected system behavior. |
| Full-text search. Standard functions. | So far as standard full-text search management function is concerned, you can check the current full-text search index for accuracy. Before you clear the current full-text search index, a warning is displayed notifying that you can abandon this procedure. | So far as standard full-text search management function was concerned, the current full-text search index was unavailable for accuracy verification. The current full-text search index was cleared with a prior warning on an unconditional basis. | Capabilities supported by the standard full-text search management function were expanded. Now, it is more difficult to clear full-text search index. |
| Web client. | The browser extension installation process was simplified (for Google Chrome and Mozilla Firefox browsers). The said extension is required to use file system, cryptography and add-in extensions. As soon as you install an extension for Google Chrome web browser, there is no need to restart your web client any more. | The browser extension installation process was complicated (for Google Chrome and Mozilla Firefox browsers). The said extension was required to use file system, cryptography and add-in extensions. As soon as you installed an extension for Google Chrome web browser, you needed to restart your web client. | Now, the web browser extension installation process is much more easier and user-friendly. |
| Collaboration system. | The collaboration system interface was modified as follows:
|
Previously, the collaboration system interface was different. | Now, it is much more easier to use the collaboration system. |
| Standard functions. | The button for accepting changes is always available, and not only after changing the parameters in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself is called OK. | The button for accepting the changes was only available after changing any parameter in the dialog box for configuring full-text search parameters of full-text search standard processing management. The button itself was called Set. | The interface of the parameter setting dialog box has been brought to the standard accepted in the platform. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Сlient application form. | Removal of rows from tables displayed in the client application form was optimized. | Previously, removal of rows from tables displayed in the client application form took more time. | Client application operation when rows are removed from the form table was improved. |
| Event log. | You can index event log files. Indexing is performed in the background. Indexes are stored in .lgx files in 1Cv8Log directory. Algorithms for sequential reading of event log files were optimized. No additional settings are required to enable indexing. Due to indexing, filtering of event log entries by indexed fields was significantly accelerated. When another infobase event log file is opened in Designer, indexing of this file is performed in the background and the index file is deleted after the work with the event log being viewed is finished. Separate Log Storage by Periods is set to Week for a new infobase. It is recommended to set separation for existing infobases, so that the size of a single log file is max 100 MB. Event logs created in the 1C:Enterprise of version 8.0 and 8.1 are no longer supported. | This feature was not provided. No event log files indexing was performed. Filtering of entries in event log files took a very long time, so far as large event log files were concerned. | Operations with event logs were accelerated. |
| Access rights. Server clusters. | When using the client/server mode, starting of the first session is accelerated to access the infobase, the configuration of which contains a large number of roles. | When using the client/server mode, starting of the first session to access the infobase, the configuration of which contained a large number of roles, took more time. | The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased. |
| Server clusters. | When using the client/server mode, starting of the first session to access the infobase is accelerated. Acceleration is especially noticeable for configurations containing a large amount of metadata. | When using the client/server mode, starting of the first session to access the infobase took more time. | The time for server cluster inaccessibility for users during the working processes restart is reduced, and the start time of the first session for each infobase in working process is also decreased. |
| Common objects. | Accelerated solution of some systems of linear algebraic equations is enabled. AllowGraphReduction parameter is implemented for SolvingLinearEquationSystems.SolveLinearEquationSystems() method, which allows to control the calculation algorithm. SolvingLinearEquationSystems.GetGraphDepth() method is implemented to allow making the decision on AllowGraphReduction parameter value. | 1C:Enterprise showed insufficient search speed for solutions of some linear algebraic equations systems. | A finer customization of behavior of a tool designed to solve linear algebraic equations systems was implemented. |
| Queries. | Comparison of composite type with non-composite type was improved, provided that the latter can be NULL and a query includes temporary tables.
The following operations were optimized:
|
Comparison of composite type with non-composite type, whenever the latter can be NULL and query had temporary tables, resulted in generation of complex queries which eventually can trigger runtime errors and generate non-optimal query plans. | In some scenarios, query performance was improved. |
| Queries. DBMS operations. Server clusters. | If comparison with an empty link returned as a parameter is made in a query, DBMS receives a query, where a parameter is replaced with a constant. Optimization is feasible, if a server cluster supports such DBMS as IBM DB2, Microsoft SQL Server or Oracle Database. | If comparison with an empty link returned as a parameter was made in a query, no replacement of a parameter with a constant was effected. | DBMS can select a more efficient query execution plan, whenever comparison with empty links returned as parameters is made in a query. |
| DBMS operations. | So far as use of infobase in file mode is concerned, execution of a query with several B conditions which use indexes was largely improved. However, in some scenarios insignificantly decelerated execution of such queries is possible. | So far as use of infobase in file mode is concerned, execution of a query with several B conditions which used indexes was non-optimal. | Execution of some queries in infobase file mode was accelerated. |
Changes that affect system behavior
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Data composition system. | When reading report, dynamic lists and conditional appearance settings, missing style elements do not cause an error, but are replaced with default values of the corresponding type. | When reading report, dynamic lists and conditional appearance settings, missing style elements caused an error and no application of such settings was possible. | If a style element is used as the appearance parameter value in any report, dynamic list, form conditional appearance settings, the entire settings object will not be lost and the remaining settings will be applied if this element is unavailable for reading as a result of deleting/renaming or applying settings on the previous platform version. Appearance options containing invalid values will also be applied, but using default values. |
| Web client. | Web client reliability is improved. | Web client operation was characterized by lower reliability. | Web client reliability is improved. |
| Development tools. | If halt on error during debugging is enabled, the error text is displayed both in the dialog box and in the message window. This also allows you to go to exception from the message window. | This feature was not provided. An error message was only displayed in a dialog box with error details. | It is now much more easier to use debugger when halt on error is enabled. |
| Development tools. | The following control features were implemented when a report on the configuration repository versions is generated:
|
These features were not provided. | A list of features designed to manage repository reports in Designer batch run mode was expanded. |
| Collaboration system. Linux. | After installing 1C:Enterprise - Notifications and Startup application (in Linux), a shortcut is created on the desktop to launch this application. The shortcut refers to the Finance subcategory of the Office category. | In Linux, you were able to start 1C:Enterprise - Notifications and Startup application from ~/bin/1cecla directory only. | Now, it became easier for Linux users to find and run 1C:Enterprise - Notifications and Startup application. |
| Web client. File operations. | Whenever you use BeginPutFileToServer() and BeginPutFilesToServer() methods on the web client (without a file system extension), PutFilesDialogParameters is used, and in the file opening dialog box you can now select one of the filters defined when you created PutFilesDialogParameters object. When you create PutFilesDialogParameters object, you can now define filter by default to be used when a file selection dialog box is opened. | Whenever you used BeginPutFileToServer() and BeginPutFilesToServer() methods on the web client (without a file system extension), PutFilesDialogParameters was used, and in the file opening dialog box you were unable to select a filter in the file opening dialog box. | If there is now file system extension on the web client, it's easier to select files for further processing by application. |
| Cryptography support. | Values of properties starting from OID prefix which are based on Subject and Publisher properties of CryptoCertificate have the maximum length of 2,048 bytes. | Values of properties starting from OID prefix which were based on Subject and Publisher properties of CryptoCertificate object had the maximum length of 128 bytes. | Eliminated unexpected system behavior . |
| Global search. | GlobalSearchResultItem object cannot be created on the basis of the following standard global search kinds: GlobalStandardCommands and FunctionsForTechnicalSpecialist. | You were able to create GlobalSearchResultItem object on the basis of the following standard global search kinds: GlobalStandardCommands and FunctionsforTechnicalSpecialist, so that eventually incorrect data upon global search result processing was returned. | Eliminated unexpected system behavior. |
| Dynamic lists. | If the dynamic list settings form contains changed settings, then when attempting to close this form, the user will be warned about the changed settings and will be prompted to save the changed settings. The UserSettingsModified and SettingsModified properties are implemented to expand the client application form for the settings composer. The standard processing of the settings composer form analyzes the flag of settings modification and prompts to save the settings, if necessary. | If the dynamic list settings form contains changed settings, when attempting to close this form, the form was closed without any warnings. | Likelihood of losing work results by changing dynamic list settings was reduced. |
| XML and XDTO support. | When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option is exported in the same way as it is for properties with an "Attribute" presentation option. This upgrade is ignored in 8.3.13 version compatibility mode. | When exporting an XDTO package to an XML schema, the default value (or fixed value) for properties with an "Element" presentation option was not exported. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | Whenever you convert a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contain tab characters or text starting with whitespace can now be created easier. | Whenever you converted a spreadsheet document into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format, cells which contained tab characters or text starting with whitespace were created in a way, when the resulting document was visually different from the original one. | Now you have less visual differences between the original spreadsheet document displayed in 1C:Enterprise and that created by way of conversion thereof into XLS (Microsoft Excel 94-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later versions, Microsoft Word 2007 and later versions) or ODS (OpenDocument Spreadsheet) format. |
| Queries. | If the temporary table is generated based on the table of values, a runtime error will be generated if a column with an unspecified type is present in the table of values and this column is included in the temporary table. An error will also occur if a non-typed column is involved in any expression (for example, SELECT or ISNULL). This upgrade is ignored in 8.3.13 version compatibility mode. | If a temporary table is formed based on a table of values where a column with an unspecified type is present and this column is included in a temporary table, no runtime errors were generated, but the query result could be incorrect. | Eliminated unexpected system behavior. |
| Collaboration system. Web client. | Screen translation in the collaboration system running on a web client:
|
Screen translation in the collaboration system running on a web client:
|
The screen translation tool is improved, so far as the collaboration system runs on the web client. |
| Administration tools. | In Version 8.3.10 and later compatibility mode, GetDataBaseStorageStructure() function returns a table of values where the Indexes column contains short index names. At the same time, the names of indexes are displayed identically for any DBMS. | In the Indexes column of the table of values returned by the GetDataBaseStorageStructure() method, long index names were indicated and the index names differed in different DBMSs. | The names of indexes in the database schema are refined. |
| Configuration extensions. | Tooltips for the check box, which controls the behavior of the object property in the extension, have become more clear and better describing the essence of the check box status. | Tooltips for the check box, which controls the behavior of the object property in the extension were poorly describing the check box status. | Improved tooltips for the check box describing the behavior of an object property in the extension. |
Changes that require modification of configuration and administrative settings
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Сlient application form. | If no table is displayed in the form or there are no rows in the table or a row which is unavailable in the table is transferred to FormTable object method:
|
So far as thin and thick client applications are concerned:
|
Now, the system operates in a similar way both on the thin and thick client. Unexpected system behavior was eliminated. |
| Client application. | To describe OpenID Connect provider in default.vrd file, you can specify the fields to compare users of 1C:Enterprise and OpenID Connect provider infobases. | This feature was not provided. Users were always compared by e-mail and infobase user name. | Now, you can use OpenID Connect with a great number of providers, for instance, Microsoft Azure. |
| Data composition system. | If a data composition system expression in query language contains curly brackets, whenever this query is processed, the said characters cannot be deleted. If there is no "}" character at the end of a data composition system expression in query language before that query is transmitted, an error is displayed. In 8.3.16 version compatibility mode behavior remained unchanged. | If a data composition system expression in query language contained curly brackets, whenever this query was processed, the said characters were deleted from the query. If there was no "}" character at the end of a data composition system expression in query language before that query was transmitted, no error was displayed. | Eliminated unexpected system behavior. |
| DBMS operations. Queries. | When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator IN, which meets all of the following criteria, always returns a Boolean value:
|
When using the file or client-server version (when using the Microsoft SQL Server DBMS), the query language operator IN, which meets all of the following criteria, returned a Boolean or NULL value:
|
Eliminated unexpected system behavior. |
| Data composition system. | If a query with merges is available in the data composition system query, whenever you use DataCompositionProcessor.Initialize() method with RestrictGettingFieldsByRefByViewRight set to True, View rights are applicable to all merging parts. In 8.3.16 version compatibility mode behavior remained unchanged. | If a query with merges was available in the data composition system query, whenever you used DataCompositionProcessor.Initialize() method with RestrictGettingFieldsByRefByViewRight set to True, View rights were applicable to the initial merging part only. | Eliminated unexpected system behavior. |
Renamed objects
Table of contentsMobile version of "1C:Enterprise"
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile client. | Images in SVG format can be displayed in the mobile client. No filters and effects are supported when you use images of this format. ImageFormat.SVG system enumeration property was implemented. | This feature was not provided. | 1C:Enterprise mobile client now supports display of images in SVG format. |
| Add-ins. Mobile platform. Mobile client. | So far as add-ins are concerned which are supported by mobile devices running iOS, you can connect dynamic system libraries to add-ins. The add-in technology documentation is updated. (read more) | This feature was not provided. So far as add-ins running iOS were concerned, you were able to specify required subsystem components only. | Functionality to develop add-ins running iOS was added. |
| Mobile client. | Dynamic add-in setting is no longer supported by mobile client application build (including mobile clients which can run in a standalone mode) running Android. DynamicAddInInstallationSupported() method always returns False value on a mobile device (except mobile versions for developers) | Whenever you were running Android, you were able to use dynamic add-in setting for mobile application application build (including mobile clients capable of running in a standalone mode). | Due to update of security policy by Google, always make sure that add-ins available on a mobile client are included in a mobile application build. |
| Formatted documents. | External appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was changed. Functionality offered by a tool bar remained unchanged. The formatting tool bar was made similar for mobile phones and tablets. | Previously, external appearance of a tool bar for formatted and HTML-documents in a mobile version of 1C:Enterprise was different. The formatting tool bar was dissimilar for mobile phones and tablets. | The formatting tool bar for formatted and HTML-documents became easier and more user-friendly. |
| Mobile platform. Mobile client. | Application usage statistics services can now be connected to the mobile application being built. The following statistics services are supported:
|
This feature was not provided. | Now, you can integrate mobile applications for a mobile version of 1C:Enterprise with various mobile application statistics services. |
| Mobile platform. Mobile client. | User interface was enhanced (photos, audio and video recording). Now, you can review the result of action you performed and (if deemed necessary) repeat it. | User interface was different (photos, audio and video recording). You were unable to preview and hear the results of your actions. Moreover, you were unable to repeat any of the actions. | Now, it is much more easier to use tools supported by a mobile version to record audios and videos and make photos in a convenient way. |
| Mobile platform. Development tools. | It has become possible to connect to the web server where the configuration of the mobile application is published using the HTTPS protocol in the developer's mobile platform. Opening the dialog box for configuring an HTTPS connection has been implemented in the infobase adding dialog box. | This feature was not provided. | Connecting a developer's mobile platform to a web server can be more secure (using the HTTPS protocol). |
Library updates
Table of contentsTransition from the previous version to the version 8.3.17
- 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.17.
- Some features that are added in version 8.3.17 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.