DataWedge Profiles
DataWedge functionality is based on Profiles. Each Profile contains options, also known as plug-ins, for determining how the data is acquired (input), processed (data formatting) and delivered to the app (output). A single Profile can be associated with one or more activities or apps. However, an activity or app can be associated only to a single Profile. In addition to the core functionality with Input, Processing, and Output, optional Profile specific configuration settings are categorized under Utilities, which can be associated with apps or controlled at runtime. Details about functionality and usage of each of the Input, Processing, Output and Utilities options can be found in the links below. By default, Profile0 is provided as a generic Profile that can take effect for foreground apps that have not yet been associated to any Profiles. This provides the ability to quickly acquire data prior to taking action on setting any configurations. For more information about how Profiles work, see the Architecture Overview page.
A DataWedge Profile and its contents. When the associated app/activity is in the foreground, DataWedge loads the Profile and performs actions to acquire (input), format (process) and deliver (output) the data based on the Profile configurations. Data Capture Plus and Enterprise Keyboard Configuration are separate utilities that perform specific functions to the app/activity. Data Capture Plus enables areas of the screen to behave as a scan trigger. Enterprise Keyboard Configuration enables a custom generated keyboard layout to be displayed in the associated app/activity.
An introduction to DataWedge profiles
Main configurations for plugins:
| Plugin | Type | Main Configurations (not all-inclusive) |
|---|---|---|
| Input | Barcode | ∙ Select scanner: camera, 1D or 2D imager, Bluetooth scanner, etc. ∙ Enable/disable hardware trigger ∙ Select decoders ∙ Set decoder params (options for each decoder) ∙ Set reader params (options for the scanner selected) ∙ Set scan params (scanner specific decoding feedback) |
| Magnetic Stripe Reader (MSR) | ∙ Data output is acquired through intents, which DataWedge automatically parses and places into specific tags to be handled by the app | |
| Radio-frequency Identification (RFID) | ∙ Enable/disable hardware trigger ∙ Configure reader settings |
|
| Serial | ∙ Set serial port configuration | |
| Voice | ∙ Data capture start option: start phrase or PTT button ∙ Specify data capture start phrase ∙ Specify data capture end phrase ∙ Set timeout for data capture ∙ Configure voice commands ∙ Configure data type returned: alpha, numeric, any ∙ Offline speech recognition ∙ Validation window (validate captured data allowing to edit if needed) |
|
| Process | Basic Data Formatting (BDF) | ∙ Add prefix ∙ Add suffix ∙ Send as hex ∙ Append TAB key ∙ Append ENTER key |
| Advanced Data Formatting (ADF) | ∙ Create custom rule with specific criteria and actions to process acquired data | |
| Output | Keystroke | ∙ Inject action key in place of the character: None, Tab, Line feed, Carriage return ∙ Send keystrokes as key events ∙ Send certain key events as a string ∙ Set key event delay |
| Intent | ∙ Set intent action ∙ Set intent category ∙ Set intent delivery |
|
| Internet Protocol | ∙ Enable/disable Remote Wedge ∙ Set protocol: TCP or UDP ∙ Set IP address ∙ Set Port number |
|
| Utilities (Options) | Data Capture Plus (DCP) | ∙ Set location of button to trigger scanning: left side, right side, either side ∙ Set mode to launch DCP: button only, full-screen only, button interchangeable to full screen ∙ Set highest/lowest button position ∙ Set wait time to trigger scanner action after a screen tap |
| Enterprise Keyboard Configuration | ∙ Select custom generated layout |