|Functionality||After||Before||Result of changes|
|Dynamic list. Working with queries.||Custom queries, including queries that generate dynamic lists, are now available on the mobile platform.||This feature was not provided on the mobile platform.||In mobile applications, you can use dynamic lists generated based on custom queries, and use queries to the Infobase for implementing various features, such as checking balance while posting documents|
|Managed form.||Faster form opening and faster execution of context server calls.||Insufficient performance of form opening and execution of context server calls.||Improved user experience by improving the performance of form operations.|
|Applied objects.||Predefined items are created at the first call of the corresponding table. Calling the SetPredefinedDataUpdate() method before the first call modifies the flag that shows whether predefined data is created.||Predefined items were only created when the mobile application configuration was updated. After calling the SetPredefinedDataUpdate() method, predefined data was only modified during the next mobile application configuration update.||Mobile platform behavior is uniform with that of PC platform version 8.3.3.|
|Background and scheduled jobs.||Background jobs are now available on the mobile platform.||This feature was not provided on the mobile platform.||Background jobs are available in mobile applications.|
|Access rights. Functional options.||
In the mobile platform, the following features are available:
Limitations of the implemented features are described in the documentation.
|These features were not provided in the mobile platform.||Extended features for applied solution interface management.|
|Working with database.||The EraseInfoBaseData() global context method is implemented.||This feature was not provided on the mobile platform.||On the mobile platform, you can delete all Infobase data.|
|Development tools.||In Designer, support of Android Debug Bridge (adb) is added. Now you can start a mobile application from Designer on a mobile device emulator or on a physical device connected to a computer.||This feature was not provided.||Easier development and debugging of mobile applications for Android OS.|
The limitations of the telephony tools on supported operating systems are listed in the documentation.
Sending SMS messages and making calls was available with some limitations using parameters of the RunApp() and GotoURL() methods.
Access to the call history and sent email messages from the built-in email client was not available.
|Easy access to mobile device functionality: SMS and MMS, call history, and making calls.|
The configuration property RequiredMobileApplicationPermissions, specifies permissions that mobile application will require on Android:
The Mobile application builder uses the specified permissions.
|This feature was not provided.||You can specify permissions required for your mobile applications more clearly.|
Scanning barcodes using the mobile device camera is supported.
For the MultimediaTools object, the following methods are implemented: BarcodeScannerScanning(), ShowBarcodeScanning(), and CloseBarcodeScanning().
|This feature was not provided.||New mobile platform feature.|
|Development tools.||In Designer, you can edit pictures with variants. You can convert images to images with variants and back.||You could only load pictures with variants without editing them.||Creating images for mobile applications became easier.|
|Access to mobile device features.||Access to mobile device contact lists, both local and linked to specific accounts, is implemented. The following objects are implemented: ContactManager, ContactData, AccountContactData, LocalContactKey, ContactAccount, ContactDataItem, and ContactDataItemInstantMessaging.||This feature was not provided.||You can access mobile device contacts.|
|Access to mobile device features.||Access to mobile device calendars linked to specific accounts is implemented. The following objects are implemented: CalendarManager, CalendarAccount, LocalCalendarKey, LocalCalendarEventKey, CalendarEventData, AccountCalendarEventData, CalendarData, and AccountCalendarData.||This feature was not provided.||You can access mobile device calendars.|
|Geolocation.||For the AddressData object, the AddressString property is implemented. It stores an address fragment starting from the street.||This feature was not provided.||The AddressData object functionality is extended. It can be used not only for geolocation purposes, but also for storing various types of contact information.|
|Mobile application builder||
The mobile application builder, which is included in the mobile platform, is improved:
The mobile application builder had the following features:
||The usability of the mobile application builder is improved.|