Mobile version of 1C:Enterprise


Functionality After Before Result of changes
Mobile client.
The mobile client now supports authentication using OpenID Connect protocol. Authentication uses a system web browser of a mobile device.

Authentication using OpenID Connect is supported for iOS 9.0 or higher devices and Android devices that have Google Chrome installed.

This feature was not provided. The mobile client now supports authentication that was available in thin client and web client.
Mobile client.
A сonfiguration synonym is not checked for matches when you start the mobile client. The mobile client will be started if a сonfiguration name has not changed since mobile application build and a сonfiguration signature matches its digest. Once a сonfiguration synonym changed, it was impossible to use this configuration with the mobile client application that was built with another synonym (for example, which did not have a synonym in any language). You do not now need to rebuild a mobile application of the mobile client when only a сonfiguration synonym changes.
Mobile client.
Mobile application builder.
Implemented a mobile client with the operating offline feature. This client application allows you to use it both online (as a mobile client) and offline (as a standalone mobile application). Implemented option to switch from online to offline mode and back.

Implemented an offline configuration feature that will be available on the mobile device in offline mode. Offline configuration is a subset of the main configuration. The offline configuration may include all metadata that exists in the platform for a PC. Configuration objects may not be a part of an offline configuration. Configuration extensions cannot be included in an offline configuration.

Implemented the MainServer global context property. Implemented the MainServerAvailable() global context method. Implemented the OnMainServerAvailabilityChange() client application module event. The following is implemented for the ClientApplicationForm object:

  • ReopenFromAnotherServer() and FillWhenReopen() methods.
  • OnMainServerAvailabilityChange, BeforeReopening, and OnReopening events.

Implemented the BehaviorWhenMainServerIsUnavailable property for the input field, button, decoration, and table form elements.

Implemented the OfflineConfigurationContents, OfflineConfigurationRestrictionRoles properties for the Configuration object. Implemented the BehaviorWhenMainServerIsUnavailable property for the common command and common form.

Implemented the form preview in the mobile client mode in offline mode for the client application form editor. Implemented the display of elements and attributes that are not available offline on a mobile device in the client application form editor.

Implemented the feature to perform configuration verification in the offline mobile client mode.

Implemented the feature to specify in which mode the mobile client will be started in Designer settings.

Implemented new debugging items for the debugger.

The mobile application builder allows building a mobile client application with the offline mode feature.

This feature was not provided.

It was possible to create either a standalone mobile application or a mobile client that worked online.

Expanded the options to build mobile applications using 1C:Enterprise.
Mobile platform.
Mobile client.
Mobile application builder.
Mobile device-specific features.
Implemented the feature to automatically manage mobile application data backup using the mobile operating system. Implemented the Backup using OS tools mobile application permission. The backup is performed as follows:
  • Android - Google Drive service or manually using Android Debug Bridge.
  • iOS - Apple iCloud service.
  • Windows - Microsoft OneDrive service.

The mobile application builder uses this permission to correctly configure the mobile application being built.

This feature was not provided. Automatic mobile application data backup (without user interaction) is now possible.
Mobile platform.
Mobile client.
Mobile application builder.
Mobile device-specific features.
Implemented the mobile application permission, which allows you to manage the third-party applications installation. This feature is supported by the mobile application builder when building applications for Android.

Implemented ApplicationInstallation permission.

This feature was not provided.

The third-party applications installation has always been permitted.

If the third-party applications installation is not required for the application, you can reduce the total number of permissions that the mobile application requires when running on Android.

Next page: Transition from the previous version to the version 8.3.16