Advanced Data Formatting allows you to manipulate collected data based on its content and/or custom rules configured to trigger (or prevent) actions based on specific criteria. For example, a simple rule might move the cursor four characters forward or from one text box to another. A complex rule can only be created to trigger an action if the first four digits of a purchased 16-digit number match those of a particular bank. An unlimited number of rules and interdependencies can be created, allowing DataWedge to meet virtually any data processing requirement. Containers for one or more processing actions and customizable criteria that trigger the action. All DataWedge output plug-ins can contain one or more ADF rules for processing collected data. Note: ADF rules do not support selecting which scanner to use to scan data when multiple scanners are configured. String to validate: Allows you to specify a string that, if present in the collected data, initiates the action(s) (that is, generates the captured string). If the specified string does not exist at the “Start Position” (see below), the action(s) will not be executed.

DataWedge can check alphanumeric or control characters. For example, data processing controls appear as Master Data Formatting and Advanced Data Formatting and are grouped in the settings pane of a profile with the output parameters: Sends the specified ASCII/Unicode character. The maximum value of the Unicode character is U-10FFFF (1114111 in decimal places). Sending control characters (character codes 1 through 31, except ENTER and TAB) with this option is not supported because they are not printable and therefore do not appear in the data output. If control characters are to be sent as key events, Zebra recommends enabling the Send control characters as an event option in the keystroke output. 3. Tap the new rule to access the settings. A screen is similar to the image in step 4.

7. On the rules screen, tap “Actions” as shown below. Then select New Action from the menu on the next screen. A drop-down list of actions appears, similar to the illustration in step 8. These steps are all performed in the Advanced Data Formatting Process plug-in, which is part of each DataWedge output plug-in. For more information, see DataWedge Profiles. Reduce spaces between words to one and remove all spaces at the beginning and end of data 1. In the profile that requires an automatic document feeder, tap Advanced Data Formatting, as shown below. A screen looks like the image in step 2.

A set of procedures to analyze, identify and process the collected data. 9. Repeat step 8 until all required actions appear in a list of actions similar to the screenshot below. Actions are performed from top to bottom. To rearrange an action, drag to the “hamburger” icon. See additional notes and example below. The DataWedge 6.2 AutoFeeder rules screen (with multiple actions configured). For example, if the collected data contains the group separator (GS) (x1D) and the data must be retrieved on both sides of the delimiter, the following ADF actions can be added to the ADF rule: String length: An optional parameter that allows a specified length (in characters) to exist before actions are called. For example, if you are scanning U.S. Social Security numbers, a string length of nine (9) can be used as the initial validation medium. String Position – The starting position (from 0) at which to find the string specified in the String to check parameter.

For example, the destination string “AB” with string position 3 would call action(s) when string “123ABC123” is retrieved, but would not call action if “AB” is elsewhere in the string (or was not present). Notice that the “AB” part of the string example starts at the fourth character from the left, which is position 3 if the number starts at 0. 8. In the Actions list, tap the desired action and scroll as needed. After you tap an action, the Rule screen reappears, with that action added to the end of the Actions list. For a description of each action, see the following table. Replaces a specified string with a new specified string. Both must be specified. When configuring an ADF data processing rule to find or replace control characters, extended ASCII characters, or other nonprinting characters, DataWedge supports using xNN notation to specify the hexadecimal value of the character and the uNNNN notation for Unicode values. Stops removing characters from subsequent send actions Configuring advanced data formatting is done in three basic steps: Sends the specified number of characters from the current cursor position (default=0) Advanced data formatting features are implemented through rules. criteria and actions.

Moves the cursor forward by the specified number of characters (default=1) 5. In the Criteria form, enter the criteria that enable the rule based on the following options. 2. Tap Rules. Then tap the “Hamburger” menu, select New Rule and enter a name for the rule. The new rule appears along with other rules in the output plug-in screen, similar to the image in step 3 below. The following is an example of the process of creating an advanced data formatting rule that might be typical of data processing scenarios. 6. Press the BACK button to save and return to the rules screen.

Triggers for a treatment action. Criteria can be based on input type (for example, only barcode reader data), symbology (i.e. only Code39 data), and a specified string in the data (at a specific location in the data string and/or length). Collected data that does not meet all the defined criteria does not trigger any action. Some or all supported barcode types can be selected or excluded. Source Criteria – An optional parameter that can trigger actions only when data is captured using a barcode scanner (which allows certain decoders to be selected or excluded) or SimulScan. The DataWedge 6.2 AutoFeeder rules screen (without any actions configured). 4. Tap Criteria as shown below to enter the criteria that activate the rule. Sends all remaining data from the current cursor position Pauses the specified number of milliseconds (default = 0; max.