Mobile version of 1C:Enterprise




FunctionalityAfterBeforeResult of changes
Mobile device-specific features.
Push notifications on Android use Firebase Cloud Messaging service. It is recommended to transfer push notifications to this platform in current applications.

Implemented the DeliverableNotificationSubscriberType.FCM enumeration value.

The Google Cloud Messaging service is supported for compatibility purposes and is not recommended for use.

The DeliverableNotificationSubscriberType.GCM value is obsolete and supported for compatibility purposes. The GoogleCloudApplicationNumber parameter of the ReceiveNotificationSubscriberID() method is optional on Android.

Push notifications on Android used Google Cloud Messaging service.The legacy push notifications delivery service is no longer used. Transfered to the latest version of the service.
Mobile device-specific features.
Mobile platform.
Mobile client.
Implemented the capability of managing the camera backlight interactively (on Android and Windows Phone) and from the 1C:Enterprise script (on all mobile operating systems).

Implemented the DeviceTools global context property. Implemented the CameraBacklightType parameter of the MultimediaTools.MakePhoto() method.

You can now use a camera flash as a flashlight. Implemented the DeviceTools global context property. Implemented the FlashlightSupported() and TurnFlashlightOn() methods of the device tools manager.

Managing the camera backlight from the 1C:Enterprise script was not available.

Interactive managing of the camera backlight was available only on iOS.

There was no option to use a camera flash as a flashlight.

Extended the mobile device camera operations.
Spreadsheet documents.
Mobile platform.
A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.A PDF type document generated on the mobile platform was less similar to the same PDF type document generated on PC. A PDF type document generated on the mobile platform is now closer to the same PDF type document generated on PC.
Mobile device-specific features.
Mobile client.
Mobile platform.
Implemented acquiring purchase receipts feature in 1C:Enterprise mobile version. It is now available to validate the purchase receipt on a mobile device.

Implemented the following InAppPurchasesManager object methods:

  • PurchaseHistorySupported()
  • GetPurchaseHistory()
  • GetInAppPurchaseReceipts()
  • GetInAppPurchaseReceiptsData().

The InAppPurchasesManager object is now available in the mobile client and in the mobile platform client. Implemented the InAppPurchasesValidationManager.ValidateInAppPurchaseReceiptAtMobileDevice() method on the mobile client and on the mobile platform client.

The global context InAppPurchasesValidation property is now available on the mobile client and on the mobile platform client.

Acquiring the list of internal purchases is now available in the mobile application builder purchase emulator.

Acquiring purchase receipts feature was not available.

The InAppPurchasesValidationManager object and the InAppPurchasesValidation global context property were available only on the server of the PC platform.

Improved the internal purchases feature, provided by the appropriate application store.
Mobile platform.
Implemented the following form control properties:
  • DisplayImportance for all controls
  • CurrentRowUse and TableBehaviorOnHorizontalCompression for a form table.

Implemented input hints for multiline input fields.

These features were available in the mobile client only.Managed forms are now displayed the same way in different 1C:Enterprise mobile versions.

Comments
0
Add comment