In-App Lookup by Scanned Value or Response Text
For finding What’s Done, What’s Left to Do (Checklist)
The app’s Lookup feature is typically used when the barcode or NFC tag is not available, inaccessible or damaged.
However, it can also be used as the primary way to initiate scan records. Instead of scanning a barcode or NFC tag, app users simply tap the Lookup tab to view the database associated to the Service. They can search database values and response text by voice or manual entry. They can scroll to find the correct item, tap to select it and the immediately submit the ‘scan’ or first collect required data before submitting.
Advanced Search Options
A very valuable Lookup feature is the ability for your app users to view items in the validation database that have been scanned (What’s Done) and items that have not yet been scanned (What’s Left) – a simple checklist.
Typical checklist use cases:
Events: If you expected 100 people at a seminar or event, the app user(s) can see who has and who has not arrived.
Attendance: If you want to know who has not checked-in yet (i.e. they are late or absent), the app user can see who’s not there at any time.
Assets: If your app user needs to deliver 100 assets to a location, they can scan each item delivered and then check if anything hasn’t been scanned – and therefore not delivered. The same is true when picking up those assets or monitoring their assigned location.
Security: If a security guard needs to check 100 locations on their rounds, at the end of their round they can view a list of items that they’ve checked and, importantly, what they missed. Currently, for the advanced checklist, you have two options when you have multiple checklists.
Enabling your Checklist Service
For this advanced search option you need to create a Validate Scans service type; check the box to have duplicates invalid with reset (option); associate that service to a Database of the barcode values to be scanned; and optionally check the box on the Advanced step to allow app users to view other app user’s scans. Using reset option for duplicates is required when you want to repeat this special Lookup option hourly, daily, weekly, etc.
You should use online scanning if multiple devices are to be used for this Service since Internet connectivity is needed to sync the scans between devices. If you choose to scan offline you should select the Auto Sync feature on the Advanced step which will sync scans in the background when there’s Internet connectivity.
To filter the result the app user can search by all, search by barcode value, and search by the response. This is an important feature because they can search within the database for unscanned values filtered by a specific parameter. For example, if your response text looked like this “Order A, Route 1”, “Order B, Route 1″, Order C, Route 2”, “Order D, Route 2”, etc. you can use the filter to find out how many items still need to be delivered for Order A or for Route 1. Here are a few screenshots showing what the app-user needs to do.
a. One master database: When the app user uses the Lookup feature they can first use search to filter the results by either the barcode values or by anything in the response text, then show what’s been scanned and not yet scanned. So, for example, if there are many different locations in one database and the app user needs to check one location at a time, if the location is within the response text they can filter by location and then look for what’s scanned and what’s not yet scanned at that location.
b. Multiple databases: You can create a new Service for each checklist with the ‘Duplicate Service’ button (or the API) to duplicate the Service, rename it and associate a different checklist (database) for each list.