Duplicate Checking

On the first step when creating a validation Service type you have the ability to make duplicate scans valid or invalid. Check ‘Invalid’ if you want the first scan to be Valid but all subsequent scans made for this Service to be Invalid Duplicate scans.

duplicate_checking

Advanced Option for Special Situations: Reset duplicate checking automatically

The app uses a status table for duplicate checking. This table is NOT stored within the Service’s associated database but instead stored within the Service itself. Once a value has been scanned for a Service, if you’ve checked duplicates to be invalid then all subsequent scans will be invalid duplicates.

To override that, you can also reset the status table for this Service on a periodic basis. What this means is when the new period starts, the first scan will again be valid once, and then all subsequent scans will again be invalid duplicate scans. This is required if you want to use the same Service over and over again.

When is the override used? It’s used for certain access control applications and also for “What’s Scanned and Not Scanned” when tracking assets, attendance, security patrols and maintenance crews.

Online services with reset option

No special action required by your app users.

Offline Services with the reset option

For the reset to take effect with on-device (offline) Services your app users must:

a) Upload their scans from the device; and

b) Refresh the app (or sign out and sign back in) with Internet connectivity after the new period begins.

Note: The reset does not change the associated validation database since the ‘scanned’ and ‘not scanned’ status of each barcode value is stored in a separate table for each Service, not in the validation database itself.

in Services