6.9. Mobile 1C:Enterprise version specifics

This section does not fully describe the features and limitations of the mobile version of 1C:Enterprise (both of the mobile platform and the mobile client). Features and changes implemented in the personal computer platform are not automatically transferred to the mobile version of 1C:Enterprise. The new features of the mobile version are reflected in the corresponding records in V8Update.htm file, in 1C:Enterprise mobile version section.

When developing a mobile application, the following configuration objects and system mechanisms are supported:

Subsystems
Constants
Catalogs
Documents
Document journals
Accumulation registers (except totals split and aggregate mode)
Information registers
Data processors
Enumerations
Access rights (with limitations), roles
Infobase users (with limitations)
Functional options
Session parameters
Exchange plans (except exchange plans with the Distributed infobase flag set)
Managed locks
Event subscriptions
Queries
Dynamic list (with limitations)
Web service usage (without creating a Web service in mobile applications)
Common pictures
Common commands and command groups
Common templates
Common modules
Common forms
Data composition system (including the setting dialog boxes)
Conditional appearance
XDTO tool (without creating an XDTO package)
Full-text search
Languages
Background jobs
Features for debugging applications

The following features and configuration objects are not supported:

Switch interfaces (and the interfaces compatibility mode)
Accounting features
Periodic calculation features
Features of business processes and tasks
Common attribute feature
Data access restrictions
Settings storages
Operations with external data sources
Automated testing
Dragging
Standard functions
Some managed form items
Extended editing in form items
User form settings
Save and restore form data in settings
Information panel, user activity history, and notifications (the ShowUserNotification() method)
Display the long-term process state (the State() method)
Help in the mobile platform
Scheduled job feature

When distributing a configuration for a mobile application without source texts, keep in mind the following 1C:Enterprise feature: a module distributed without a source text is compiled expecting that it will be executed only on a personal computer. If such a module (supplied without source texts) uses methods that have a different number of parameters for a mobile platform and a personal computer platform, then when checking such a module when exporting to a mobile application, an error will be generated.

Some configuration objects and mechanisms have certain operation features:

iOS does not support the Execute() operator and the Calculate() function.
iOS up to version 5.x (inclusively) only supports password input using the Latin alphabet letters and numbers. iOS 6 version supports the use of national alphabet characters in passwords. To ensure compatibility between different OS versions, it is recommended to set user passwords using numbers and letters of the Latin alphabet only.
When running a dynamic list, interactive control of dynamic list settings is not supported. Settings management is available only from 1C:Enterprise language.
On mobile devices running Android OS, the animation in a mobile application may be disabled if the platform evaluates this device as not sufficiently powerful.

When operating running Windows OS (both the phones version and touch devices version) the following is not supported:

Barcode scanning using the device camera (not supported only when running Windows OS for personal computers).
Operations with calendars.
Operations with contacts.
Access to the call log.
Print from the application.
Receive and interactively send text messages.
Dial a phone number non-interactively.
Operations with client application certificates.

You should also keep in mind, that supported objects do not have all the features that are available in applications for personal computers implemented. In this regard, you should pay attention to the Availability section of the syntax assistant to determine the availability of a method or property in the mobile platform.