WEB config parameters

This parameter determines cookie accepting policies.

Possible values: do not accept – false, accept – true.

Rewrites the default ‘user-agent’ string with own value. User-Agent string is a part of the http-header.

Example: MY_USER_AGENT_STRING: ‘My EMC web browser’

Server response expectation time (in seconds). After the timer expires, a server unavailable error is displayed.

Example: 30

This option allows ignoring invalid SSL server certificates.

Possible values: true or false.

This parameter determines the cache clearing policy at session start.

Possible values: do not clear – false, clear – true.

This parameter determines cookie removal policies at session start.

Possible values: do not remove existing cookies – false, delete all existing cookies – true.

Use the SESSION_WEB parameter to create each new session.

Syntax:

SESSION_WEB: Host Name,

Host – ip-address or server name,

Name – session name (displayed in the list of available sessions and used to create an override *).

Example: Declare two Sessions GOOGLE and MY LOCAL HOST

SESSION_WEB: google.com GOOGLE
SESSION: 127.0.0.1 MY LOCAL HOST

*Override is a set of parameters that are executed exclusively for the specified session. It can be used if, for example, separate servers have different encodings or when you need to set different behavior of keystrokes. The example of a config file with override, where different font sizes will be used in two separate sessions:

SESSION_WEB: google.com GOOGLE
SESSION: 127.0.0.1 MY LOCAL HOST

[GOOGLE]
TEXT_SIZE: 20

[MY LOCAL HOST]
TEXT_SIZE: 40

URL of the page displayed if the server http error occurs.

Default value (changing is not recommended):

file:///storage/emulated/0/Android/data/com.enterprisemobilityclient.web/files/web/badlink.html

The path to the local CSS file.

Example:  file:///storage/emulated/0/Android/data/com.enterprisemobilityclient.web/files/web/my.css

This parameter controls the function of local CSS use. You can use it when you need to change html styles without making changes on the server.

Possible values: allow – true, deny – false.

This parameter that controls the function of local JavaScript scripts use.

Possible values: allow – true, deny – false.

Indicator background color.

Example: #00000000

Indicator fill color.

Example: #FF000000

The path to the local JS script file.

Example: file:///storage/emulated/0/Android/data/com.enterprisemobilityclient.web/files/web/my.js

This parameter sets the zoom factor for zooming in or zooming out the displayed page.

Example: 1.2

Fill color of the progress bar that is displayed while the page is loading.

Example: #FFD81B60

This parameter determines the screen data storage policy.

Possible values: do not store – false, store – true.

This parameter allows you setting the screen auto-rotate mode.

Possible values:
A – auto rotate,
Р – fix in portrait orientation,
L – fix in landscape orientation,
L2 – fix in inverted landscape orientation.

This parameter allows turning on and off the scrollbars on the displayed page.

Possible values: scrollbars is disabled, the page is fixed in the upper left corner – false, scrollbar is enabled – true.

The parameter allows displaying the button for switching the scanner into the hands-free mode.

Possible values: display – true, hide – false.

Timer in seconds. When the set time expires the scanner switches into the hands-free mode.

Default value: 5.

Example: 7

This parameter allows displaying the system virtual keyboard.

Possible values: allow – true, deny – false.

Keyboard reassignments (macros) allow increasing the operator’s ergonomics. Reassignments work only for the hardware buttons of the device.

A macro for any given key is a one-line entry in the following format:
keyName(my description): {command}

keyName(my description) – The system code and the assigned friendly name (my description). The system code can be found by running the KEY SCANCODES program from the menu. Also displays the keyName values ​​of the keys that are pressed.

Example: KEYCODE_F1 (F1 button)

{command} – a sequence of calls that are transmitted to the server.

Valid values:
null – empty (no suffix is ​​transmitted),
[CR] – emulation of Enter,
[ESC] – escape,
[TAB] – emulation of tabs,
[SN] – serial number,
[0xB] – a set of bytes, for example [0x01] [0x02] [0x03]
[PAUSEx] – delay in x (ms),
[KEYCODE] – key,
‘TEXT’ – string.

Examples:

By pressing F1, send the key code 3 to the server:
KEYCODE_F1(F1): [KEYCODE_3]

By pressing F1, send TAB to the server (corresponds to 09 in ASCII tables, see appendix A):
KEYCODE_F1 (F1): [0x09]

By pressing F1, send the TEXT line to the server:
KEYCODE_F1 (F1): ‘TEXT’

By pressing F1, send the TAB command to the server (pressing the TAB key is emulated):
KEYCODE_F1 (F1): [TAB]

Commands can also be transmitted as bytes, that is, the two entries below are equivalent:
KEYCODE_F1 (F1): [TAB]
KEYCODE_F1 (F1): [0x09]

Macros can be assembled in a sequence. Sequences should be separated by spaces in order to make input easier. Absence of spaces is not considered as error. The macro will not be executed if some element has an incorrect entry inside. The number of lines is unlimited.

By pressing F1, transfer login, tabulation, password, Enter (CR), wait 1 sec., Send CR LF:
KEYCODE_F1 (F1): ‘mylogin’ [TAB] ‘pass’ [CR] [PAUSE1000] [0x0D] [0x0].

The URL of the page displayed after performing a refresh (F5). This parameter can be empty.

Example: https://sapewm.exsample.com/zits_m480x854/