Skip to main content

Setup Entrance Unit Application

This guide explains how to properly provision and configure the application on the Zebra Enterprise Browser.

Entrance Unit Configuration​

Create the app-config.json file by following these steps:

  1. Create the File: Open a text editor and create a new file named app-config.json in the Enterprise Browser's configuration directory: /storage/emulated/0/Android/data/com.zebra.mdna.enterprisebrowser/

  2. Add Key Configuration Settings: Define the necessary settings for the Entrance Unit application by adding the following JSON structure.

    Note: The softwareId (daeu) and softwareVersion (6.0.0) must correspond to the Entrance Unit global template. For detailed instructions on generating the softwareStatement, please refer to the Setup and Authentication section in the Device Management Service documentation.

{
    "softwareId": "daeu",
    "softwareVersion": "6.0.0",
    "softwareStatement": "software statement credential",
    "tenantId": "tenant-alias",
    "buid": "EU001",
    "name": "Sample Application",
    "releasePageLayout": "Simple",
    "employeeCardRegex": "^[0-9]{8}$",
    "employeePinHashed": "81dc9bdb52d04dc20036dbd8313ed055",
    "enableTermsAndConditions": false
}

Properties Definition​

  • softwareId: (string) Software identifier is used to uniquely identify a registration template.
  • softwareVersion: (string) Software version is used to uniquely identify a registration template.
  • softwareStatement: (string) Software statement (SS) is an optional credential that is created from Registration template and used by apps when they register themselves as OAuth clients.
  • tenantId: (string) The unique identifier for the tenant.
  • buid: (string) The unique identifier for the business unit. If the buid is omitted from the configuration file, you can enter it manually during the registration process in the registration form when setting up the Entrance Unit for the first time.
  • name: (string) Entrance unit friendly name. If the name is omitted from the configuration file, you can enter it manually during the registration process in the registration form when setting up the Entrance Unit for the first time.
  • releasePageLayout: (string) The layout type for the release page of a handheld scanner. Possible values are Simple, Grid.
    • Simple: When selected, only text is displayed on a handheld scanner release.
    • Grid: When selected, an image is displayed showing the actual position of the handheld scanner on the wall.
  • employeeCardRegex: (string|null) A regular expression for validating scanned employee card numbers. If this property is set to null or omitted, it will become impossible to access the administration area after the initial setup. Make sure to include a valid regular expression if administrative access is required.
  • employeePinHashed: (string|null) An MD5 hash of the employee PIN. If this property is set to null or omitted, the staff authentication process will rely only on card scans for login.
  • enableTermsAndConditions: (boolean) Flag that indicates whether the application's terms and conditions feature is enabled. By default, it is off.

Custom Terms and Conditions content​

  1. Locate the terms and conditions content file: This file needs to be created in the Enterprise Browser's configuration directory on the device at: /storage/emulated/0/Android/data/com.zebra.mdna.enterprisebrowser/terms-and-conditions.html
  2. Create or edit the terms and conditions content file: The file does not exist by default. It should contain valid HTML markup with inline CSS styles. This allows the application to display the terms and conditions content dynamically.

Enterprise Browser​

  1. Locate the Config.xml: This file is typically found in the Enterprise Browser's configuration directory on the device at: /storage/emulated/0/Android/data/com.zebra.mdna.enterprisebrowser/Config.xml
  2. Edit the Config.xml: Open the Config.xml file in a text editor and find the <StartPage> tag. It should look something like this: 
    <StartPage value="" name="Menu"/>
  3. Change the URL: Modify the URL inside the <StartPage> tag to the desired webpage, for example: 
    <StartPage value="https://scanngo-entrance-unit.retailsvc.com" />
  4. Save: Save the modified Config.xml file.
  5. Restart Enterprise Browser: Close and restart Enterprise Browser. The new start page will load when the app launches.