Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
From v. 1.8.1.
When performing planned registrations, the order line dictates which values are registered and checked for validity. This is a bit different in the unplanned scenarios, although validation is still performed.
A new form of validation has been introduced in v. 1.8.1 where values in a multi value barcode, like Gs1, can be verified even before it is processed, and without the value being needed for a registration. Validation is setup in start.cfg and works across the application. This means that if a barcode is scanned, and a value fails the warnOnScan functionality, the user will be presented with a warning. Whether the user is allowed to proceed or not is up to the configuration.
Code Block | ||
---|---|---|
| ||
<start ...>
<!-- SCANNER -->
<scanner>
<type>internal</type>
<gs1Support enabled="true">
<warnOnScan>
<expirationDate eanAI="12,15,17" warningType="Warn" addDays="5"/>
</warnOnScan>
...
</gs1Support>
</scanner>
</start> |
Expiration date
When scanning a multi value barcode that contains an expiration date the application can be setup to warn if the date is expired.
- eanAI: "12,15,17" - Defines which Gs1 AI's to look for
...
- .
- warningType: "Warn" - Decides which type of warning is displayed to the user.
- Block: Blocks the user from using the barcode, hence, the barcode will be ignored after dismissing the message.
- Warn: Warns the user about the date, but allows proceeding if the user selects to do so.
- None: Does not display any warnings, and is the same as having the functionality disabled.
- addDays: "0" - Can be a positive or a negative number, modifying the barcode date, to have the warning displayed earlier or later than the actually scanned date.
Image displays a Gs1 barcode scanned which contains both lot number and expiration date.
Even though the barcode is scanned to register the Lot number, the fact that the barcode contains an expired expiration date makes the warning appear.