BlueFletch Enterprise
  • BlueFletch Enterprise
  • Product Guides
    • BlueFletch Launcher
      • Configurable Layouts
        • Layouts
        • Orientation Options
        • Criteria
        • Widgets
        • Implied Groups
        • Kiosk Mode
        • Persistent Foreground App
        • Password Protected Applications
        • Quick Start Applications Folder
        • Layout Custom Actions
        • Replacement Values
        • Assets Manager
      • Theming
        • Configure Theme
        • Site-Specific Theming
        • Custom Field Display
      • Site Information Service
      • Custom Intents
        • Standard Android Intents
        • Platform Actions
        • Filtering
        • Technical Guide
      • Security and Safety
        • Clear App Data on Logout
        • Application Enabler
        • Disable Packages
        • Key Management
        • NFC Enable/Disable
        • Secure Notifications
        • Wi-Fi UI Settings Enable/Disable
        • Motion Activated Device Lock
        • Unique Login
        • Local Admin Password
        • Device Remote Lock
      • Device Loss Prevention
        • Low Battery Mode
        • Luggage Tag Mode
        • Secure Device Mode
      • Launcher Provider SDK
      • Load Configurations via QR Code Scan
      • Getting Started
      • Technical Guide
      • Release Notes
    • Authentication and SSO
      • Features
        • Secondary Authentication
          • PIN
          • Face Recognition
          • NFC Tag
          • Barcode
          • Alternate Secondary Authentication
      • Technical Guide
        • LDAP
        • AppAuth/OIDC
        • Okta (Session)
        • MSAL
        • ADFS 3.0/2012 Using ADAL
      • Release Notes
    • Support Application
      • Features
        • Events to Splunk
        • Logs to Azure
        • External Configuration Support
        • Application Usage History
        • Generating RxLogger Log Files
      • Technical Guide
        • Event Information
        • Event Examples
      • Support Installer
      • Getting Started
      • Release Notes
    • Device Finder
      • Features
        • Device Details
        • Device Status
        • View Site Devices
      • Technical Guide
      • Getting Started
      • Release Notes
    • Browser
      • Features
        • Custom Scripts
        • FIDO2 / Webauthn Support
        • URL AllowList and BlockList
      • Technical Guide
        • Configuring Browser
        • All Configuration
        • Available Intents
        • APIs and Page Actions
      • Release Notes
    • Chat
      • Features
      • Technical Guide
      • Getting Started
      • Release Notes
    • Playbook Agent
      • Features
      • Getting Started
      • Release Notes
    • Portal
      • Login & Logout
      • Navigation & Account Settings
      • Support Agent
        • Home
        • Device Details
        • Dashboards
        • Cards
        • Event Explorer
        • Reports
      • Enterprise Launcher
        • Creating a Configuration
        • Sending a Notification
        • Managing Sites
      • Playbook MDM
        • Playbooks
        • Plays
        • Devices
        • Deployment Groups
        • Zebra StageNow
      • EMM Console
        • Overview
        • Setup
          • Enroll Org in EMM
          • Policy Management
          • Provisioning
          • Device Management
          • Installing Playbook in EMM
        • Troubleshooting
          • Device Issues
          • Policy Issues
      • Chat Manager
        • Overview
        • Chat Roles
        • Chat Channels
        • Chat Audio Transcription
        • Message Logs
      • Admin
        • Organization
        • Single Sign On
          • Azure Setup
          • Okta Setup
          • Google Workspace Setup
          • Portal Setup
        • Users
        • Roles
          • Overview
          • Predefined Roles
          • Permissions
          • Manage Roles
        • Downloads
        • Agents
        • Key Management
          • Overview
          • API Keys
          • Device Keys
          • Device Restrictions
          • Allowed IP Addresses
        • Enterprise
        • Audit Logs
      • Event Forwarding
      • Remote Control
      • Getting Started
      • Release Notes
    • Other Applications
      • Messaging
        • Features
        • Technical Guide
        • Release Notes
      • Keyboard
        • Features
        • Technical Guide
          • How to: Set Keyboard as default
        • Release Notes
      • Bluetooth
        • Features
        • Release Notes
      • Voice Chat
        • Features
        • Release Notes
      • Device Remote Control
        • Features
        • Technical Guide
        • Release Notes
      • Device ID
        • Features
        • Technical Guide
        • Release Notes
      • Suite Installer
        • Technical Guide
        • Release Notes
      • Accessibility Enabler
        • Release Notes
      • EPM Plugin
        • Features
        • Technical Guide
        • Release Notes
    • Workforce Identity
  • Technical Documentation
    • Updating License Key
    • Commonly Reported Issues
    • Deploying BlueFletch Enterprise
      • Android 10 and 11
      • MDMs
        • Workspace One (VMWare AirWatch)
        • SOTI
        • Microsoft Intune
          • Microsoft Intune + Playbook
      • From Portal to Playbook Agent
Powered by GitBook
On this page
  • Overview
  • User Guide
  • Feature Configuration
  1. Product Guides
  2. BlueFletch Launcher
  3. Theming

Custom Field Display

Custom Field Display is a Launcher feature that enables the values retrieved from an external file to be displayed on the Launcher home screen.

PreviousSite-Specific ThemingNextSite Information Service

Last updated 10 months ago

Overview

Custom Field Display is a Launcher feature that enables values retrieved from an external file to be displayed on the Launcher home screen. Having this functionality ensures that device-specific content, message, or information can be quickly accessed which in turn can help users save time, stay organized, and improve productivity.

User Guide

  1. The ‘format’ field is a string that determines how the external values are displayed on the UI. For example, a file containing a specific placeholder should be enclosed in braces and must match the corresponding field in the file.

  2. The ‘source’ field is an array of objects that defines where the information is coming from and how it should be parsed. If there are multiple pieces of information to be parsed from the file, multiple instances of the 'source' object can be created with different regex patterns and field names.

  3. The ‘pathfile’ field is a string that specifies the full path and filename of the file to be parsed. This is the location where the information is retrieved from.

  4. The ‘regex’ field is a Java regular expression string that specifies how to extract the desired information from the file. The regular expression should return the information to the first match group.

  5. The 'name' field is a string that specifies the field name retrieved by the regular expression. It should correspond to the placeholder in the 'format' string, which is then used to display the information on the Launcher home screen.

Feature Configuration

The Launcher configuration allows you to define the external values that can be displayed on the Launcher home screen. Use the example below as a guide:

For example, if there is an ASCII formatted file on the device /sdcard/Download/extension_dept.txt that contains the following:

Ext=2311
Dept=Front Desk
JobCode=A300403

The following configuration will allow you to display "2311 - Front Desk" on the screen:

    ...
    "customField" : {
        "format" : "{Extension} - {Department}",
        "source" : [
            {
                "pathfile": "/sdcard/Download/extension_dept.txt",
                "regex": "Ext=(.*)",
                "name": "Extension"
            },
            {
                "pathfile": "/sdcard/Download/extension_dept.txt",
                "regex": "Dept=(.*)",
                "name": "Department"
            }
        ]
    },
    ...

The Launcher when in focus will go through the source pathfiles and extract the group value specified by the regex and assign it as a value for the field name. In the above example, the matching group for '"Ext=(.)"' from the file will yield 2311*, and is assigned to the field name 'Extension'.

The Launcher will then apply the values read into the placeholders (the name of the custom field included in braces) as defined in the format configuration field. In this example, the Launcher will replace {Extension} with the value 2311 on the display.

Since it uses Java regular expressions to parse the values from the file, this feature is not file format specific, e.g. you can use XML, JSON, or text files as long as it is ASCII formatted and the regex is correct.

To display the last four digits of the device serial number within the custom field, use the following example:

   "customField" : {
        "format" : "{TruncatedSerial}",
        "source" : [
            {
                "data": "${config.ex.deviceId}",
                "regex": "$4(.*)",
                "name": "TruncatedSerial"
            }
        ]
    }

Custom Field Display was introduced in Launcher 2.13.x.