Advanced Data Formatting
The switching back to normal rules can also be done in the “sale” rule. For example, the rule may look like this:
When scanning a bar code of length 15, send the next 2 characters, send the class key, send the next 8 characters, send the stock key, turn off rule set 1.
It is recommended that the Disable All Rule Sets bar code on page
In addition to enabling and disabling rule sets within the rules, it is possible to enable or disable them by scanning the appropriate bar codes on
Rules Hierarchy (in Bar Codes)
The order of programming individual rules is important.The most general rule should be programmed last.
All programmed rules are stored in a buffer. As they are programmed, they are stored at the “top” of a rules list. If three rules have been created, the list would be configured as follows:
Third Rule
Second Rule First Rule
When data is scanned, the rules list is checked from top to bottom to determine if the criteria matches (and therefore, if the actions should occur). Input is modified into the data format specified by the first matching set of criteria it finds. Be sure that the most general rule is the last one programmed.
For example, if the THIRD rule states:
When scanning a bar code of any length, send all data, then send the ENTER key. And the SECOND rule states:
When scanning a Code 128 bar code of length 12, send the first four characters, then send the ENTER key, then send all remaining data.
If a Code 128 bar code of length 12 were scanned, the THIRD rule would be in effect. The SECOND rule would appear to not function.
Note also that ADF rules are actually created when the standard data editing functions are used. Scan options are entered as ADF rules, and the hierarchy mentioned above also applies to them. For the scanner, this applies to prefix/suffix programming in the parameter Scan Data Transmission Format.
