Mobile platform




Functionality After Before Result of changes
Mobile device-specific features.
Implemented the following location features:
  • Selecting a location provider either from the global list of providers, or from the list of providers available now
  • Checking if location service is enabled
  • Geofence management

Implemented the Geofence object. Implemented LocationRelativeToGeofence system enumeration. Implemented LocationProviderInformation.Available property. Implemented AvailableOnly parameter for the following methods of LocationTools object: GetProviders(), GetProvider(), GetMostAccurateProvider(), and GetMostPowerSavingProvider(). For LocationTools object , implemented methods: LocationDataUseEnabled(), AttachProvidersAvailabilityChangeHandler(), DetachProvidersAvailabilityChangeHandler(), EnableGeofencesMonitoring(), GetMonitoredGeofences(), GetMonitoredGeofence(), DisableGeofencesMonitoring(), DisableAllGeofencesMonitoring(), and AttachMonitoredGeofencesBorderCrossingDetectionHandler().

These features were not provided. Location management capabilities are now expanded. For example, predefined actions can be performed when a mobile device reaches a specific location.
Binary data.
Implemented binary data management capabilities for the mobile platform. This feature was not provided. Binary data management capabilities were only available for the PC platform. Binary data management capabilities are now implemented for the mobile platform.
Internet-enabled functionality.
Implemented check whether a mobile device is in roaming mode. The Internet connection change handler is called when the roaming mode status is changed. Implemented method InternetConnectionInformation.GetRoamingUsage(). Check whether a mobile device is in roaming mode was not implemented. A variety of actions can be performed when roaming mode is enabled on a mobile device. For example, access to mobile Internet can be restricted or prohibited due to high Internet charges in roaming.
Internet-enabled functionality.
For mobile platforms running on Windows, implemented secured connection management capabilities. Secured connection management capabilities were not available for mobile platforms running on Windows. Mobile platforms running on Windows can now access resources that require secured connection.
Cryptography support.
Implemented encryption operations for the mobile platform. The mobile platform behavior is identical to that of the thin client. Details of the encryption operations are described in the documentation. Implemented CryptoManager.ShowCertificateList() method. Implemented CryptoKeysContainer object. Changed behavior of the following methods of CryptoCertificateStore object on the mobile platform: Add(), Delete(), BeginAdding(), and BeginDeleting(). Encryption operations were not implemented for the mobile platform. On the mobile platform, you can implement a check whether a document stored locally was modified. Sensitive data and documents can now be securely sent through open channels thanks to encryption capabilities.
Mobile device-specific features.
For the mobile platform, implemented a check whether contacts and calendars can be added or edited. For ContactManager object, implemented methods ContactEditingSupported() and ContactsAppendingSupported(). For CalendarsManager object, implemented methods CalendarEditingSupported() and CalendarsAddingSupported(). The CalendarManager.CalendarEditingSupported property is now deprecated and supported for compatibility purposes only. For 1C:Enterprise applications running on Windows, the CalendarManager.EventEditingSupported() method always returns False. The check whether contacts can be added or edited was not implemented. The check whether calendars can be added or edited was implemented in a different way. Unified contacts and calendar management as related to adding and editing objects.
Mobile device-specific features.
Implemented new configuration permission: Ads. This permission is only used by the mobile application builder when selecting a mobile platform version for iOS to be used in the builds. If the Ads permission is used in the configuration export file, The app uses ads check box is unavailable in the mobile configuration form of the mobile application builder. The permission specifying that ads are allowed for a mobile application was not implemented in the configuration. Instead, The app uses ads check box in the mobile application builder was used for this purpose. Now the mobile application builder can be forced to use an advertisement-enabled mobile platform version for iOS in the builds.
File operations.
For the mobile platform, implemented getting thumbnails for pictures and video files stored in the corresponding libraries of the mobile device. This feature requires the file path to start with content: schema. For File object , implemented methods GetMobileDeviceLibraryFileThumbnailPicture() and BeginGetMobileDeviceLibraryFileThumbnailPicture(). This feature was not provided.

It was possible to fully load a picture or video file into memory when a thumbnail could be used instead

Optimized mobile device memory use when loading pictures or video files from the corresponding libraries of the mobile device. Reduced risk of insufficient memory error for mobile applications that load a large number of pictures or video files from the corresponding libraries of the mobile device.
Managed locks.

Implemented data lock management for mobile platforms. Implemented global context methods LockDataForEdit(), UnlockDataForEdit(), SetLockWaitTime(), and GetLockWaitTime(). Implemented methods IsLocked(), Lock(), and Unlock() for objects CatalogObject, DocumentObject, and ExchangePlanObject. Implemented method AccumulationRegisterRecordSet.LockForUpdate(). Implemented method ManagedForm.LockFormDataForEdit(). Implemented DataLock and DataLockItem objects. For Document, Catalog, and ExchangePlan configuration objects, implemented the DataLockFields property. For Configuration, Document, Catalog, ExchangePlan, Constant, Sequence, AccumulationRegister, and InformationRegister configuration objects, implemented DataLockControlMode property.

Managed lock support was not provided on the mobile platform. Object lock management during background job execution on the mobile platform is now available.
File operations.
Implemented getting a file mask that describes all files, as well as getting a file path separator character, regardless of the mobile operating system where 1C:Enterprise is running. Implemented methods GetAllFilesMask(), GetClientAllFilesMask(), GetServerAllFilesMask(), GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator(). Implemented method BeginGetMobileDeviceLibraryDir(). Getting a file mask that describes all files and getting a file path separator character regardless of the mobile operating system used was not supported. File operations in mobile applications are nearly operating system-agnostic now.
System requirements.
Implemented Android 7.0 support. Implemented multiwindow mode for Android 7.0. For Android versions 6.0 or earlier:
  • Introduced a new API for operations with the mobile device camera
  • Implemented dynamic resolutions
Multiwindow mode was not supported for Android 7.0. Dynamic resolutions were not supported for Android versions 6.0 or earlier. Dynamic resolution management was not supported for Android versions 6.0 or earlier. Improved support of Android versions 6.0 and earlier.
Mobile device-specific features.
Implemented barcode scanning capability for mobile devices running Windows 10. Barcode scanning is not supported for mobile devices running Windows 8.1 or earlier. For devices running Windows 10, implemented availability of MultimediaTools.ShowBarcodeScanning() method, while MultimediaTools.BarcodeScanningSupported() method returns a value specifying whether barcode scanning functionality is available. For successful barcode scanning, continuous auto focus mode must be supported for the primary device camera. Barcode scanning was not supported for mobile devices running Windows. Expanded mobile platform capabilities for devices running Windows 10.
Managed forms.
For the mobile platform, implemented form field extension for the calendar field. The form field extension for the calendar field does not support dragging. This feature was not provided. Expanded Data type data management capabilities for mobile platform forms.
Mobile application builder.
In the mobile application builder, automatic deletion of obsolete data is implemented. Obsolete data is defined as mobile application builds and mobile platforms that were last changed (or imported) before a specific date. This date is calculated as follows: current date minus the specified number of days (the gap size). You can specify custom gaps for mobile application builds and mobile platforms.

Default values:

  • 90 days for mobile application builds
  • 180 days for mobile platform files

If you set the gap size to 0, obsolete objects are never deleted.

When you attempt to use an obsolete object, the mobile application builder prompts you to rebuild the mobile application or reimport the mobile platform.

The mobile application builder did not provide tools for automatic deletion of obsolete objects. You have the option to keep the size of the mobile application builder infobase within reasonable limits, avoiding significant growth of the disk space occupied by this infobase.
Print tools.
Printing is now supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64). Printing was not supported on devices that run Windows Phone 8.1 or later (ARM and x86) and touch devices that run Windows 8.1 or later (ARM and x86-64). Extended mobile application capabilities on Windows.
Mobile applications.
Hardware rendering support is implemented for user interface on Android devices. This feature was not provided. Improved performance of user interface generation on Android devices.
Mobile application builder.
In the mobile application builder, automatic deletion of obsolete data is implemented. Obsolete data is defined as mobile application builds and mobile platforms that were last changed (or imported) before a specific date. This date is calculated as follows: current date minus the specified number of days (the gap size). You can specify custom gaps for mobile application builds and mobile platforms.

Default values:

  • 90 days for mobile application builds
  • 180 days for mobile platform files

If you set the gap size to 0, obsolete objects are never deleted.

When you attempt to use an obsolete object, the mobile application builder prompts you to rebuild the mobile application or reimport the mobile platform.

The mobile application builder did not provide tools for automatic deletion of obsolete objects. You have the option to keep the size of the mobile application builder infobase within reasonable limits, avoiding significant growth of the disk space occupied by this infobase.
Mobile application builder.
The requirements to Android SDK components used to build mobile applications are defined by the requirements of the mobile platform version used to build the applications.

The builder uses the latest Android API Level available on the computer, provided that the API Level meets the mobile platform requirements. The requirements to other Android SDK components are defined by Android API Level requirements.

If the mobile platform was loaded in a previous builder version, the builder requires Android API Level version 24 or later.

The following Android SDK components were required to build mobile applications for Android:
  • Android API Level version 23 or later
  • Android Tools version 20.0.3 or later
  • Android Platform Tools version 14 or later
  • Android Build Tools version 19.0.0 or later

These requirements were applied regardless of the mobile platform versions used to build mobile applications. They were hardcoded in the mobile application builder.

The requirements to mobile application build infrastructure for Android are defined by the mobile platform version, instead of the requirements hardcoded in the mobile application builder.
Mobile application builder.
In mobile application builder, Gradle tool now can be used to build mobile applications. On Android SDK version 26 or later, you can build mobile applications using no other tools besides Gradle.

You can specify two Android SDK paths in the builder settings: one for version 25 or ealier and the other one for version 26 or later. Therefore, you can build mobile applications that require any specific Android SDK version.

Building with Gradle requires Java 8 on the computer that runs mobile application builder. It does not require Apache Ant.

Mobile application builder did not support building mobile applications with Gradle tool. Building mobile applications that use new Android SDK versions is now available.
Mobile applications.
Since mobile platform version 8.3.10.71, only building mobile applications with Gradle tool is supported. Use mobile application builder provided as a part of the mobile platform distribution package to build mobile applications.

Since mobile platform version 8.3.10.71, Apache Ant is not required for building mobile applications.

Mobile platform versions earlier that 8.3.10.71 did not support Gradle. Building the mobile platform required Apache Ant. The mobile application building procedure is modified to comply with the changes in the recommended application building procedure for Android.

Comments
0
Add comment