For the complete documentation index, see llms.txt. This page is also available as Markdown.

Dashboard scanning

Category: General

Version: 1.0

Last updated: May 6, 2025

Author: Any2Info


Description

Dashboards support multiple methods for scanning and using values inside mobile dashboard workflows.

Scanning functionality can be used for:

  • Product identification

  • Asset lookup

  • Record filtering

  • Workflow automation

  • Mobile operational processes

Currently dashboard scanning is only supported inside the mobile viewer app and is not available in the web-based viewer.

There are currently two primary ways to use scanning in dashboards:

  1. On scanned value event

  2. Scanned tag in Navigational Flow

Both methods serve different purposes and use different scanning technologies.


Method 1 — On scanned value event

Overview

The On scanned value event allows dashboards to react to scanning input while the dashboard is already open and active.

This method is event-driven and primarily intended for:

  • Operational scanning workflows

  • Repeated scanning

  • Real-time scan processing

  • Continuous scan interactions

The event is triggered automatically whenever a supported scan is received.


Supported scanning methods

Scanning Method
Description

Zebra device scanner

Built-in barcode or QR scanners available on Zebra mobile devices

Bluetooth NFC scanner

External NFC scanning module connected through Bluetooth


How it works

When:

  • the dashboard is open

  • the dashboard is active

  • and a supported scan is received

the On scanned value event is triggered.

The scanned value itself is not directly returned by the event. Instead, the value becomes available inside supported actions executed by the event.

The dashboard does not need focus on a specific control or input field.


Supported actions

Examples of actions that can use the scanned value:

Action
Usage

Set value action

Set control values using the scanned result

Execute dataflow

Execute a dataflow using the scanned value

Execute agent

Execute an agent using the scanned value

The scanned value is only available inside actions that explicitly support scanned values.


Zebra device support

Zebra mobile devices contain built-in scanning hardware.

DataWedge profile

The mobile viewer app requires a Zebra DataWedge profile to receive scans.

The application attempts to configure this automatically during startup.

If scanning does not work:

  1. Open the app settings

  2. Navigate to the Zebra device section

  3. Verify the DataWedge profile configuration

Device feedback

Zebra devices usually provide:

  • Beep sounds

  • Visual scan feedback

This behavior is controlled by Zebra device settings.


Bluetooth NFC support

Bluetooth NFC scanners are also supported.

Configuration and pairing are done inside the mobile app settings.

When a dashboard is opened:

  • A toast notification indicates whether Bluetooth NFC setup succeeded or failed

Detailed NFC configuration is documented separately.


Typical use cases

  • Warehouse scanning

  • Production scanning

  • Repeated barcode processing

  • NFC-based workflows

  • Continuous operational scanning


Limitations

Limitation
Description

Mobile only

Not supported in the web viewer

Supported actions only

Scanned values are only available in compatible actions

Active dashboard required

Dashboard must remain open and active


Method 2 — Scanned tag in Navigational Flow

Overview

The Scanned tag feature allows scanned values to be used during dashboard navigation.

This method is navigation-driven and intended for:

  • Opening dashboards in a filtered state

  • Context-based dashboard initialization

  • Product detail dashboards

  • Record lookup scenarios

Unlike the On scanned value event, this method uses the mobile device camera and does not require Zebra hardware.


How it works

The Scanned tag option is configured inside a Set parameter action in a Navigational Flow.

  1. Dashboard navigation starts

  2. The flow detects a parameter configured with Scanned tag

  3. The mobile camera opens

  4. The user scans a barcode

  5. The scanned value is applied directly to the incoming parameter

  6. Dashboard initialization continues

  7. Dataclips and controls load filtered data using the scanned value

If the scan fails or is cancelled:

  • The dashboard will not open


Navigational flows currently occur when:

Trigger
Description

Dashboard opened from menu

Dashboard launched directly from application menu

Load dashboard action

Dashboard navigation initiated from another dashboard


Camera-based scanning

This scanning implementation uses the device camera.

Important differences compared to the On scanned value event:

Feature
Scanned tag

Uses camera

Yes

Requires Zebra device

No

Requires DataWedge

No

Works on standard mobile devices

Yes

This makes the feature suitable when dedicated scanning hardware is unavailable.


Allowed tags

The following allowed tags currently exist:

Tag Type
Status

Barcode

Supported

List

Reserved

Tree

Reserved

Clip list

Reserved

Clip tree

Reserved

Currently only Barcode is functionally usable.

The remaining tag types are intended for future database tag functionality.


Dataclip integration

The scanned value is applied directly to the incoming parameter.

Dataclips using that parameter can automatically filter their data based on the scanned result.

Typical flow

  1. Barcode is scanned

  2. Incoming parameter receives the scanned value

  3. Dataclip filtering occurs

  4. Matching records are loaded

  5. Controls display filtered data

In most implementations the scanned value filters the dataclip to a single record.


Example scenario

Example:

  • A product barcode contains a product number

  • The barcode is scanned during dashboard navigation

  • The scanned value becomes the incoming parameter

  • A dataclip filters products using that parameter

  • Dashboard labels display:

    • Product name

    • Price

    • Description

This creates a dynamically loaded product detail dashboard.


Typical use cases

  • Product detail dashboards

  • Asset lookup dashboards

  • Record identification

  • Context-sensitive dashboard loading

  • Mobile lookup applications


Limitations

Limitation
Description

Mobile only

Not supported in web viewer

Single scan only

One scan per navigational flow step

Camera required

Device camera must be available

Barcode only

Only barcode tags currently functional

Mandatory scan

Dashboard does not open when scan fails or is cancelled


Choosing the correct scanning method

Scenario
Recommended Method

Repeated operational scanning

On scanned value event

Zebra hardware workflows

On scanned value event

NFC workflows

On scanned value event

Open dashboard using scanned identifier

Scanned tag

Camera-based scanning without Zebra devices

Scanned tag

Product lookup dashboards

Scanned tag

Real-time scan actions inside open dashboard

On scanned value event


Tips & Best Practices

  • Use On scanned value for continuous operational scanning.

  • Use Scanned tag for dashboard initialization and filtered dashboard loading.

  • Use Zebra devices for high-performance industrial scanning workflows.

  • Use camera-based Scanned tag workflows when standard mobile devices are used.

  • Design dataclips around unique identifiers for optimal filtering behavior.


Changelog

Version
Date
Change

1.0

May 6, 2026

Initial documentation version added.

Last updated

Was this helpful?