About SmartDocs

The "SmartDocs" bar can customize this page to show only the features present on a particular Zebra device.

Use drop-downs to select the OSX, MX and/or Android version on the device, and/or the device Model, which highlights features supported in the device. Unsupported features turn gray based on selection(s).

SmartDocs Nav works when viewing features of an individual CSP. To use, click on a CSP (i.e. "App Manager") and make at least one selection in the SmartDocs bar. Unsupported features turn grey. Click the forward and back SmartNav buttons to scroll to the next and previous supported feature of that CSP (SmartNav is not supported on the feature matrix).

To clear all selections press the SmartDocs button.

OSX, MX and Android version information for a device can be found in the Android Settings panel or by querying the device through ADB, EMDK or the MX CSP. More info.

The OSX layer provides extensions to the base operating system to implement functionality not offered by Android. The root OSX version number always matches the root number of the Android version that it extends. More info.

The MX Management System provides a uniform interface into privileged and unprivileged Android APIs on the device. Some features require a specific pairing of MX and OSX versions. More info.

The Android version is sometimes enough to determine a feature set. Others require a specific MX version plus a minimum version of Android.

The Device Model indicates which subset of MX features is present in the device.

Overview

The Batch setting is used to execute one Profile (which may contain any number of settings) from within another Profile. This can be viewed as sort of a subroutine call. In StageNow, a Batch setting is used internally (without explicit reference by the staging administrator) to generate bar codes and NFC tags and to implement execution of the Deployment Section read from a Deployment Server.

A Batch setting also can be used explicitly by a staging administrator to leverage the functionality of one Profile from within another Profile. This could be used to create reusable 'components' as Profiles that could then be used from other Profiles by embedding or referencing them from a Batch setting. For example, one staging administrator may create and test a Profile, demonstrate and prove that it provides some functionality. This Profile could then be exported as XML or saved as Binary (e.g. for programming into an NFG tag). The Profile (as XML or Binary) could then be embedded into a Batch setting. That Batch setting could then be used (via Re-use Saved Setting) by a staging administrator in another Profile to perform the entire functionality of the embedded Profile at the point in the created Profile where the Batch setting is placed. The staging administrator using the Batch setting would have no visibility to the Profile that is embedded in that Batch setting but would nonetheless be able to exploit the functionality of that embedded Profile.

A Batch setting also can refer to a file in the device file system that contains a Profile (as either XML or binary) instead of embedding the Profile into the Batch setting. Such usage would require the 'batch file' (the file containing the Profile) to be present in the device file system before the Batch setting that references it is executed in order for the proper result to occur. Such a 'batch file' might be transferred to the device using a File setting or through some other 'out of band' method. The Deployment Section functionality of StageNow is implemented internally and automatically using a combination of File and Batch settings without the need for the staging administrator to explicitly create either a File setting or a Batch setting. But a staging administrator COULD use such settings to construct more advanced or customized staging deployment scenarios.

Main Functionality

Process a file in the device file system that contains a Profile

Process a Profile that is embedded within the Batch setting

Process Profiles that are XML or binary

Process Profiles that are optionally encrypted

Batch File Type

Specify the type of file to be processed.

Parm Name: BatchFileType

Option

Name

Description

Note

Requires

1

XML File

The batch file is encoded as XML.

MX: +

2

Binary File

The batch file is encoded as binary.

MX: +

Batch File Access

Specify whether the batch file will be available on the device file system or embedded in the XML.

Parm Name: BatchFileAccessMethod

Option

Name

Description

Note

Requires

2

File in Device File System

When choosing **Device File System**, enter a path and file name on the device where the XML or binary file to be processed will be located.

MX: 4.3+

3

File Embedded in XML

When choosing **Embedded in XML**, select an XML or binary file in the workstation file system. This file is encoded and placed into the Batch setting.

MX: 4.3+

File Path

Enter a path and file name on the device where the XML or binary file to be processed will be located.