Mobile Application Templates

The boot screen displays image with application version number that appears on application startup.

The presentation displays a series of consequently displayed application key features and a button to go to login dialog box. Described features include title, image and text. The presentation is displayed at the first application startup, and it can be further disabled using the checkbox.

To connect to mobile platform server:

1. Open connection settings by tapping the gear wheel button in the login dialog box.

2. Specify mobile platform server URL, environment and project name.

3. Click the Save button.

Default connection settings are determined at the first application startup.

To set up connection on mobile platform side, see the Connecting Template Application to Mobile Platform Server section.

User authentication depends on the operating system:

• iOS. User authentication is executed using the Keychain Service service that saves login and password of the last authorized user.

To quickly access the application, the user can set PIN code, set access by TouchID or FaceID. On the first online authorization the user can set PIN code that is saved in Keychain. After the PIN code is set, the user is allowed to access using TouchID or FaceID if the device supports this functionality.

On the further authorization the user is asked to access using TouchID or FaceID or PIN code. If the data is successfully verified, the user gets access to the saved login and password and is authorized.

To change user settings, use application side menu. The settings allow for: enabling and disabling PIN code and access by TouchID or FaceID, changing PIN code.

• Android. User authentication is executed by login and password or by code.

To change application login method, click the Change Application Login Method button in the login dialog box. Set PIN code or graphic code specified in device system settings. If the code is successfully verified, the user is authorized.

Application settings are stored in the data resource at mobile platform server:

• Idle time. Cancel authorization and go to the login dialog box if the user after authorization does not make any actions during the specified time.

• Menu color. Application interface color.

NOTE. The parameter can be stored only for iOS.

• Role information. Link between roles and access to resource. The application displays roles in the side menu. Clicking the role name displays a screen with a list of all available resources.

• User avatar. The avatar is loaded from mobile platform server on the first use of the side menu and is stored in the application directory.

When the user actively uses the application, background check of server availability is executed using authorization request.

A data sources is requested after successful online authorization of the user before going to the application home screen. If authorization failed, errors are displayed in the tooltip containing error code and description obtained from mobile platform server.

If the user is successfully authorized, the home screen displays a list of data sources and resources. Clicking the resource opens a list of resource tables. Clicking the table opens a list of table data.

Offline authentication is set by the user at the first authorization on a specific device using database key of the following type:

<environment>_<project>_<username>:<password>:<databasePIN> databasePIN

Key is valid until the user removes the application. Key change is available only on the full reinstallation of application and creating a new local database on a device. If online authentication is not executed, the offline mode is available, at which the user must enter the databasePIN created on the first authentication.

It is available to send a message to technical support with previously generated text to a specific email.

When setting up connection to mobile platform server, it is available to toggle between specified environments and projects, that is, development, testing, and operation.

A local database name is created automatically as "hhfw_<environment>_<project>_<username>". If user names are unique, an individual database is created for each user.