29.6.7. Standalone mobile application specifics

29.6.7.1. Mobile device configuration update

The mobile client with standalone mode cannot be initially started in standalone mode. For the first startup, you need to have an interrupted communication channel to connect to the main infobase. It is required to import the standalone configuration.

Further, upon each startup of the client application and establishment/reestablishment of connection between the mobile application and main server, the standalone configuration is checked for available updates. You can observe one of the following scenarios:

An update is found when the client application is started, before its actual use:
- The standalone configuration update file is automatically downloaded to the device.
- The standalone infobase configuration is updated using the downloaded configuration.
Before connection to the main server is established, the client operates in standalone mode and is able to connect to the main server:
- The user is prompted to confirm configuration update.
- If the user confirms the update, the standalone configuration update file is downloaded to the mobile device, and the client application is restarted. After that, the standalone infobase is updated using the downloaded configuration.
- If the user declines the update, the client application continues operation with the previous standalone configuration version with no ability to connect to the main server (in standalone mode).
If a configuration update is found upon another connection to the main server (with disabled standalone mode), the current session is closed, and the previous operation scenario is applied.

29.6.7.2. External references

External references are references to objects not included in the standalone configuration. However, such references are used in standalone objects. Any references to configuration objects can be used as external references, including references to objects unavailable on a mobile device. Any actions with standalone references (receiving attribute values, receiving objects, and so on) are not supported on mobile devices. In fact, external references are used to display real data in respective form fields. As a result, the user does not have to be worried about data "loss".

If data being an external reference is displayed in a form field:

In case of no connection to the main server:
- This field becomes inaccessible.
- Reference presentation is cached as soon as connection is reestablished.
- If no external reference presentation is saved on a mobile device, a message about data unavailability is displayed instead.
In case of connection to the main server:
- The reference is available for further use.
- The main server is called for that.

29.6.7.3. Command interface

If a command is not included in the standalone configuration, it will be unavailable in standalone mode. If a command is included in the standalone configuration, its availability in standalone mode will be defined by the Behavior in case the main server is not available command property. If the property is set to Auto, it is interpreted as Do not change behavior. If property editing is unavailable for the command, Do not change behavior is used.

29.6.7.4. Users

No user operations are supported by the mobile client with standalone mode. When the application is started, username and password are requested. Authentication is performed by the main server. If a user different from the one specified upon initial authentication (when the infobase is created) is specified upon following application startups, an error occurs. Therefore, if the mobile device is used to operate a single main infobase by two or more users, each of them needs to have a separate infobase (application) on the mobile device.

If a user that signed in to the main infobase changes their password, the standalone infobase is notified about it only after successful authentication on the main server.

29.6.7.5. History

History is stored both on the main and standalone infobase server. If a mobile device is granted access to the main server, history is saved in both infobases. If a mobile device is not granted access to the main server, history is saved in the standalone infobase only. As soon as access to the main server is granted, history versions are merged and saved in both infobases.

29.6.7.6. Favorites

Favorites are stored both on the main and standalone infobase server. If a mobile device is granted access to the main server, favorites are saved in both infobases. If a mobile device is not granted access to the main server, favorites are saved in the standalone infobase only. As soon as access to the main server is granted, favorites are merged and saved in both infobases.

<< Prev Next >>