Mobile platform




Functionality After Before Result of changes
File operations.
Multimedia support.
On the mobile platform, the FileDialog object is available. For the dialog limitations on specific mobile operating systems, see the Syntax Assistant. For mobile devices, the option to select files interactively is implemented for the following methods: GetFile(), GetFiles(), PutFile(), and PutFiles().

The File.GetMobileDeviceLibraryFilePresentation() method is implemented. It returns the file presentation for displaying on the mobile device.

You can use mobile device library file names (with the content: schema) in constructors of the following objects: File, BinaryData, Picture, and MobileDeviceApplicationRun. You can use them as parameters for the following global context methods: RunApp(), GotoURL(), FileCopy(), MoveFile(), DeleteFiles(), and FindFiles(). On iOS and Android, you can also use them as parameters for the following methods of the MultimediaTools object: PlayAudio() and GetAudioDuration().

The MobileDeviceLibraryDir() global context method is implemented. It returns a path to a mobile device library (a picture, audio, or video library).

The FileDialog object was not available on the mobile platform. Interactive file operations are implemented for the mobile platform.
Mobile device-specific features.
For Android operating system, the option to process incoming call data using 1C:Enterprise script tools is implemented.

For the TelephonyTools object, the CallsHandlingSupported(), AttachCallsHandler(), and DetachCallsHandler() methods are implemented. The TelephonyTools.CallsHandlingSupported() method returns True on Android only.

This feature was not provided on the mobile platform. The option to process incoming call data in mobile applications using 1C:Enterprise script tools is now available on Android operating system.
Mobile device-specific features.
Extended multimedia options for the mobile platform:
  • The option to play a sound or vibration alert is implemented. The MultimediaTools.PlaySoundAlert() method is implemented.
  • The option to play audio data of various types is implemented. Playing is performed using the default application provided with the operating system. The option to stop playing is implemented. For the MultimediaTools object, the PlayAudio(), StopAudioPlayback(), and GetAudioDuration() methods are implemented.
  • The option to read text using the screen reader provided with the operating system is implemented. The option to stop reading is implemented. For the MultimediaTools object, the PlayText(), StopTextPlayback(), and TextPlaybackSupported() methods are implemented.
These features were not provided on the mobile platform. Extended multimedia support.
Data composition system.
On the mobile platform, the support of data composition system is implemented, except for the objects that allow user interaction. Therefore, all data composition system operations are performed using 1C:Enterprise script tools.

In Designer, the option to create data composition schemas for reports that run in mobile applications is implemented.

This feature was not provided on the mobile platform. Extended report development capabilities on the mobile platform.
Add-ins.
On the mobile platform, add-in support is implemented. It uses the NativeAPI technology.

You can export a mobile configuration from Designer to 1cema.zip format, which includes the add-ins used in the configuration.

When you connect a mobile device using Android Debug Bridge (ADB), add-ins are copied to the device.

In the mobile application builder, the option to build applications with add-ins is implemented.

Add-in development technology documentation and examples are updated (read more).

The mobile platform did not support this feature. You have the option to expand mobile platform functionality when its standard features do not cover your needs.
Managed forms.
The following features are implemented for the mobile platform:
  • Display a command bar button as a hyperlink.
  • Set horizontal picture alignment on a managed form button.
  • Set gaps between command bar buttons.
  • Set command bar button shapes (except for buttons located in popups).
  • Set the view of managed form buttons.
  • For text boxes, support of CreateButton and ChoiceButtonRepresentation properties is implemented.
  • For text boxes, support of EditTextChange and Creating events is implemented.

Support of BorderColor, BackColor, TitleTextColor, and TitleFont properties is implemented for buttons of CommandBarButton and CommandBarHyperlink type and for form group extensions for popups.

This feature was not provided on the mobile platform. The set of features available on the mobile platform is closer to the set of features available on the desktop platform.
Internet-enabled functionality.
The option to check the availability of data transfer network in mobile applications is implemented.

The InternetConnectionInformation global context property is implemented.

This feature was not provided on the mobile platform. The option to analyze available data transfer methods and choose the optimal strategy for operations with external data is implemented.
JSON support.
The mobile platform now supports JSON operations. Serialization of XDTO documents to JSON objects is not supported. This feature was not provided on the mobile platform. Simplified integration with applications (including web applications) that use JSON data format. The option to store data in JSON format (for example, instead of XML format) is implemented.
Internet-enabled functionality.
The behavior of the OpenSSLSecureConnection object is unified with that of the PC platform.
  • If the CertificationAuthorityCertificates parameter of the object constructor is not specified, the certificate is not checked.
  • If the CertificationAuthorityCertificates parameter of the object constructor is specified, the check uses the root certificates installed on the device.

The OSCertificationAuthorityCertificates object is now available on the mobile platform.

This change is not implemented in 8.3.8 compatibility mode.

The certificate check always used the root certificates installed on the mobile device. The CertificationAuthorityCertificates parameter of the OpenSSLSecureConnection object constructor was ignored. Unified behavior of the mobile platform and the PC platform.

Eliminated unexpected system behavior.

Mobile device-specific features.
The option to check the availability of operations with global contact keys, calendars, and calendar events on different mobile operating systems is implemented.

For the ContactManager object, the GlobalContactsKeySupported() method is implemented.

For the CalendarsManager object, the GlobalCalendarsKeysSupported() and GlobalEventsKeysSupported() methods are implemented.

The GlobalContactKey parameter of the AccountContactData object constructor is no longer supported. The values of properties that describe global contact keys, calendars, and calendar events depend on the result of the function that checks the availability of global key operations. If global key operations are not supported, requests to these values return blank strings.

Availability of LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects on the mobile application server is implemented.

The availability of global contact keys, events, and calendar events depended on the platform where a mobile application was running. Developers had no means to check whether operations with global keys from 1C:Enterprise script were supported.

The LocalContactKey, LocalCalendarKey, and LocalCalendarEventKey objects were not available on the mobile application server.

The mobile platform behavior is unified with the general behavior of applications that have features that are not available on some mobile devices or operating systems.
Predefined data.
In the mobile platform, support of the following global context methods is implemented: InitializePredefinedData(), SetInfoBasePredefinedDataUpdate(), and GetInfoBasePredefinedData(). This feature was not provided on the mobile platform. Unified desktop and mobile platform features related to predefined data.
Mobile device-specific features.
The implementation of the Beep() method is now uniform with the implementation of the MultimediaTools.PlaySoundAlert(SoundAlert.Default). The Beep() method did not perform any actions. You can use the Beep() method to play the default sound alert of a mobile device.
Administration tools.
For mobile applications, the following features are implemented:
  • Infobase verification and repair.
  • Infobase backup.
  • The option to run an automated backup before the application update, so that you can restore the infobase if any issues occur during the update. This option is enabled by default.
  • The option to schedule automated infobase backups is implemented.

The backups are stored to the mobile device storage.

These options are available in the application settings dialog box (the Administration button in this dialog box).

This feature was not provided. Additional options for mobile application administrators.

Comments
0
Add comment