This section explains how to select, install and deploy a number of Android terminals for Reflex Web WMS.
Prerequisites
| Characteristics | |
OS |
|
SCREEN |
|
PERIPHERAL DEVICES |
|
Configuring the terminal
If using native Android keyboards (default option), you must deactivate the auto-complete and auto-correct features on the Android keyboard for the terminal (in particular, auto-changing a double space to a "full stop plus space" must be deactivated).
The scanner must be configured as follows:
- When reading a GS1 code, the first FCT1 character must not be sent.
- The scanner must replace the ASCII &x1D (Group Separator) character by the one specified in the "HF_EAN" program configuration.
We recommend you to use the '=" character as it is rarely used in bar codes. - Return the Enter key at the end of the scanned string.
For Zebra terminals, we recommend configuring the bar code reader so that it uses the Intent mechanism rather than keyboard input. This will make scanning more reliable and an error beep will be emitted if the application is not available.
The configuration steps are as follows:
- Deactivate keyboard input.
- Activate input via Intent.
- The Intent action must be: com.hardis.wagonandroid.INJECTDATA.
- The send mechanism via Intent must be: startService
- The key for "string"-type data must be: com.symbol.datawedge.data_string.
Selecting deployment method
You can choose between two deployment methods for the Reflex application on a terminal fleet.
If you have an MDM-type deployment tool, we recommend that you use it, because it will make deployment simpler.
Deployment without tool
Click here for the installation without tool step-by-step guide |
Deployment using an MDM tool
|
Note : The installed version of Reflex Apk can be viewed in the Version menu of the application.
Information regarding the Reflex Android application
Where can I download the application?
| Download source | Variant and limits |
|---|---|
From Google Play Store https://play.google.com/store/apps/details?id=hardis.com.wagonandroid&hl=en&gl=US EN | The application downloaded from the Play Store is the variant called "playstore". It has the following restrictions:
It is made to be deployed by an MDM-type tool or manually for personal use. |
On the Hardis server | The application downloaded from Reflex is the variant called "legacy". It has no restrictions. |
Which version is it?
The Android application is approved with Reflex when a major update is released.
The two variants are produced simultaneously and have the same version number.
The version number is displayed in the "About" section of the Play Store, in the Reflex updater and in the Android application parameters.
Which version of the Reflex server is it compatible with?
The Reflex Android application, regardless of its version, is compatible with all Reflex servers with a version greater than or equal to 9.14.
We recommend that you always use the latest version of Reflex Android.
When are Android versions approved?
Hardis approves its application according to manufacturer terminal availability and announces new Android version support as part of the release of a major Reflex update.
What is the change log?
Reflex Android Version | Changes |
|---|---|
| 14.8.0.6 | Network flow optimised Access permissions to certificates and environments menus |
| 14.8.0.3 | Configurable sound during data inject via intent |
| 14.8.0.1 | Allowed data to be exchanged via intents. |
| 14.5.0.1 | "playstore" and "legacy" variants created. Android Enterprise and managed configurations support. |
| 14.4.0.4 | Improved security |
| 14.4.0.5 | Made it possible to block sleep mode |
| 14.3.0.4 | Android 11 support |
| 14.3.0.1 | Desktop shortcut to access multiple Reflex environments. |
| 14.1.0.2 | Open-Id authentication handling. |
| 14.1.0.1 | Custom keystore for SSL certificate. |
Ajouter un commentaire