|Functionality||After||Before||Result of changes|
||The option to debug configurations on the mobile platform is implemented. The debugging can only be performed over HTTP (you can select this option in Designer).||This feature was not provided.||Streamlined development of applied solutions for the mobile platform.|
||The Print mobile application extension, which is used for printing from mobile applications, is implemented.
The mobile application builder supports building mobile applications that require this extension.
|This feature was not provided.||Reduced list of required permissions for mobile applications that do not require printing.|
||The brightness of frozen spreadsheet document areas is reduced by 2.5%.||The brightness of frozen spreadsheet document areas was reduced by 10%.||Better look and feel of spreadsheet documents with frozen areas.|
||The following string processing functions previously available for the personal computer platform are now implemented for the mobile platform: StrTemplate(), StrCompare(), StrStartWith(), StrEndsWith(), StrFind(), SrtSplit(), and StrConcat().
The SearchDirection system enumeration is implemented.
|This feature was not provided.||Unified string processing for the personal computer platform and the mobile platform.|
||The Representation property of a managed form button located in a form title command bar affects the button view. When the platform defines the button view, it ignores the properties of the command linked to the button.||The Representation property of a managed form button located in a form title command bar did not affect the button view. When the platform defined the button view, it ignored the properties of the command linked to the button.||You can manage the view of buttons located in form title command bars using the button properties.|
||For the TelephonyTools.NumberDialingSupported() method the DirectCall parameter is implemented. The parameter streamlines the check for number dialing support.||The TelephonyTools.NumberDialingSupported() method did not support any check options.||Унифицирована возможность проверки работы со специальными возможностями на мобильной платформе.|
||Support of Windows Phone operating system version 8.1 or later (ARM and x86 architectures) and touch devices that run Windows version 8.1 or later (ARM and x86) is implemented.
The mobile platform for Windows Phone supports all mobile platform features available on other operating systems, excluding:
The mobile platform specifics are described in the documentation.
The mobile platform distribution file mobile.zip is complemented with new data.
This option is implemented as beta version.
|This feature was not provided.||Extended support of operating systems for mobile and touch devices.|
|Mobile application builder.
||Mobile application builder for Windows Phone operating system is implemented. It supports Windows Phone 8.1 or later.
New builder parameters are added:
Publishing of built applications to Windows Store is not supported.
When loading mobile platform data from the mobile.zip file to mobile platform builder, you have the option to load only mobile operating systems that are present in the archive.
The option to specify different application IDs for different mobile operating systems is supported.
The option to export developer certificates from the mobile application builder database is implemented.
|Mobile application builder did not support Windows operating system.
Attempts to load the mobile platform from the mobile.zip file to mobile application builder were only successful if the file contained platform versions for both Android and iOS.
A single mobile application ID was assigned for Android and iOS builds.
Exporting developer cerificates from the mobile application builder database was not supported.
|Mobile application builder supports Windows operating system, and features other improvements.|
|On the mobile platform, the Show in list command, which was perviously available only on the personal computer platofrm, is implemented.
The ManagedForm.ExecuteNavigation() method and the NavigationProcessing managed form event are implemented.
|This feature was not provided.||The interfaces of the mobile and personal computer platforms are unified.|
|Web services and HTTP services.
||On the mobile platform, the option to use a web service whose address does not match the address specified in a WSDL file imported to the applied solution (WS-reference configuration object) is implemented.||This feature was not provided.||Web servfice operations on the mobile and personal computer platforms are unified.|
||On the mobile platform, the option to use a selection list to provide a value for a managed form input field that displays date and time is implemented.||On the mobile platform, drop-down lists were not available.||On the mobile platform, the option to use drop-down lists in the input fields that display date and time is now available.|
||The option to switch between the input fields using the Enter button of the virtual keyboard (i.e. without closing the keyboard) is implemented. The option to switch between the input fields using Tab/Shift+Tab keys of a physical keyboard connected via Bluetooth is also implemented.||The option to switch between the input fields without closing the virtual keyboard was not available. To switch between the fields, a mobile application user had to close the keyboard, then switch to another field, and then open the keyboard.||Improved mobile application usability is scenarios where multiple input fields are available in a single form.|