Validate Scans Against a Database of Barcode Values
Step 1. Type
Duplicate Checking (optional)
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.
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 the 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.
c) After a) or b) above, the app-user will be prompted to download the database to the device; that download also includes a file that resets duplicates if so configured for the Service.
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.
Step 2. Name
Step 3. Users (app users)
Create at least one new app user. Convention is using email address or suffix + name.
Step 4. Questions (optional):
Prompts to your app users to collect data after each scan.
New: Sessions for auto-repeating data for every scan in a series
Step 5: Advanced
For a full overview of what each option entails, you can read more on our page about advanced settings.
- To restrict app-user access to the scans uploaded to our server, you should check the option to Enable custom web view for scan “History”.
- To restrict app-user access to the database associated with your service, you should check the option to Enable custom web view “Lookup”.
You don’t have to be a developer for those options – you can enter an existing URL there, such as your Privacy or Terms URL. Alternatively, you or your developer can create a custom web page specifically for these options and insert those URLs.