|Functionality||After||Before||Result of changes|
|Mobile device-specific features.||The following permissions are implemented for iOS mobile applications:||These features were not provided.||Expanded settings for iOS mobile applications.|
|Managed forms.||In the mobile platform, the object that visualizes planner data (the planner) is now available.|
For the object usage specifics, see the documentation.
|The planner was only available on the platform for personal computer.||Expanded data presentation options on mobile devices.|
|Mobile device-specific features.||Support of local and push notifications is added to the mobile platform for Windows. 1C:Enterprise uses Windows Notification Services for this purpose. The notification sending service provided by 1C Company does not support Windows Notification Services.|
The system enumeration value DeliverableNotificationSubscriberType.WNS is implemented.The DeliverableNotificationSendManager.GetAccessToken() method is implemented.
Notification sending errors are returned in the return value of DeliverableNotificationSendManager.Send() method.This change is not implemented in 8.3.10 compatibility mode.
The system enumeration DeliverableNotificationSendErrorType is implemented. The DeliverableNotificationSendIssueInformation object is implemented.
For DeliverableNotificationSendManager.Send() method, the DeliverableNotificationSendIssuesInformation parameter is implemented.
The option to get a local notification when a device is crossing a geofence border is implemented.
|Support of local and push notifications was only available for iOS and Android devices.|
Notification sending errors generated exceptions.
|Standard user notifications are now available on mobile Windows devices. Both mobile applications and desktop applications can generate notifications (local and push notifications, respectively).|
|System requirements.||Support for Android versions earlier than 4.0 is ended. The earliest supported API version is API 14 (Androuid 4.0).||Android versions with API 9 (Android 2.3) or later were supported.||Ended support for legacy Android versions.|
|In the mobile platform, support of batch printing is implemented.||This feature was not provided.||Batch printing is now available in the mobile platform.|
|File operations.||On the mobile platform, the file selection dialog box now supports multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method are now case-insensitive. The file selection dialog box and FindFiles() method now support iOS and Android wildcards.||The file selection dialog box did not support multiple file masks. The search by mask in the file selection dialog box and the search by mask with FindFiles() method were case-sensitive. The file selection dialog box and FindFiles() method did not support iOS and Android wildcards.||Expanded file operation tools in the mobile platform. These tools are unified with file operation tools available in the desktop platform.|
|Formatted documents.||The mobile platform now supports FormattedDocument object (and can display formatted documents in managed forms).||This feature was not provided.||Expanded support of formatted text in mobile applications.|
|Mobile device-specific features.||On the mobile platform for Windows (except Windows 8.1), support of map operations is implemented. The following methods are now available: ShowOnMap(), GetAddressByLocation(), and GetLocationByAddress().|
Global context method MapRepresentationSupported() is implemented.
|Map operations were not supported on Windows mobile devices.||Extended mobile platform capabilities on Windows. Determining whether map operations are available is standardized with other operations that might be unavailable on some devices or operating systems.|
|Mobile applications.||When a configuration that was saved using an earlier 1C:Enterprise version for personal computer is loaded to a mobile application, the mobile device displays a warning and provides the option to cancel the operation.||When a configuration was loaded on a mobile device, 1C:Enterprise did not check whether the configuration was saved using an earlier 1C:Enterprise version for personal computer.||Implemented diagnostics of potential compatibility issues between the mobile platform and the configuration to be loaded (in scenarios where the configuration was saved using an earlier 1C:Enterprise version for personal computer).|
|Mobile device-specific features.||On Android devices, the following operations with SMS messages are implemented:|
On Android devices, in method SMSLog.FindRecords(), ungrouped filter items are combined using AND operator.
|On Android devices, access to SMS message log was not provided.|
On Android devices, in method SMSLog.FindRecords(), ungrouped filter items were combined using OR operator.
|Introduced advanced SMS management tools on Android devices.|
The behavior of the filter used in a search in the SMS message log is unified with other filters.
|Database configuration update.||In built mobile applications, the message stating that unused data will be deleted is no longer displayed after configuration updates.|
The mobile platform for developers displays a message stating that the update changes metadata structure (only when it actually changes it).
The developers are now responsible for preventing data losses caused by configuration updates.
|If a configuration update changed metadata structure, a message stating that unused data will be deleted was displayed after the update.|
The message was displayed both in built mobile applications and in the mobile platform for developers.
|Configuration updates are now less distressing to end users. In patricular, end users do not get a message that their data will be lost (which was not always true). At the same time, developers must be more cautious when implementing configuration changes that might cause losses or user data.|