Our A/B Compare feature allows your app users to match two or three barcode or text values. First, the user scans the barcode on a list or asset. Secondly, the user scans the barcode on the target asset(s) to validate the match. If they all match, the app user will see a green valid screen. If they do not match, the app user will see a red invalid screen. If valid, the app user can optionally be prompted to collect associated data to be included in that formal scan record.
A primary scan refers to the scan initiated from the app’s Tap to Scan screen. A question-answer scan refers to a scan made when the app user is prompted to do so after the primary scan. A question prompt can be a standard question asked after every scan or a session question. A database refers to the database associated with a Validate Scans service type. It includes the barcode value and the intended response after each scan.
This technology works when using the built-in camera of iOS and Android OS devices. It also works with dedicated scanners, like those offered by Honeywell and Zebra. When using a dedicated scanner in the keyboard emulation mode with a CR/LF suffix, the app user doesn’t have to tap the screen to sequentially scan or to submit the record. That makes repetitive scanning faster.
The barcode matching script works online or offline. It uses our Custom On-Device Validation (COV) feature. You simply edit the script for your intended use. Then, paste it on the Advanced step when creating or editing your services.
This option compares the primary scan to a secondary scan made as a question-answer. If the initial scan (A) matches the question scan (B), the record will be valid.
This option first validates the primary scan against the associated database. It then compares the primary scan to a secondary scan made as a question-answer. If the initial scan (A) matches the question scan (B) and is in the associated database, the record will be valid.
This option first validates the primary scan against the associated database. Then, it compares the primary scan and/or a question-answer scan to the response text in the associated database. If the primary scan (A) and/or a question-answer scan (A) matches the corresponding response text (B), the record will be valid. Here, the database would be structured so that the primary scan value is in column 1 and the expected question-answer is in column 2 of your import. The matching of text in the response can either be an exact match or a match to a select string within the text.