In-App Lookup by Scanned Value or Response Text
For finding What’s Done and What’s Left to Do (Checklist)
You can use the app’s Lookup feature when the barcode or NFC tag is not available, inaccessible or damaged.
Also, you can use it as the primary way to initiate scan records. Instead of scanning a barcode or NFC tag, users tap the Lookup tab to view the database associated with the Service. They can search database values and response text by voice or manual entry. They can scroll to find the correct item and tap to select it. Then, submit the ‘scan’ or first collect the required data before submitting it.
Advanced Search Options
Users can use the Lookup feature 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). Thus, it is perfect for a checklist use case.
Typical checklist use cases:
Events: If you expected 100 people at an event, the app user(s) can see who has and has not arrived.
Attendance: The app user can check checked-in yet at any time.
Assets: If your app user needs to deliver 100 assets to a location, they can scan each delivered item. They can also check if anything hasn’t been scanned.
Security: If security guards need to check 100 locations on their rounds, they can view a list of items that they’ve checked and 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. Use the reset option for duplicates to repeat this special Lookup option hourly, daily, weekly, etc.
Use online scanning if you are using multiple devices for this Service since you need Internet connectivity to sync the scans. If you choose to scan offline, select the Auto Sync feature on the Advanced step which will sync in the background when there’s 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 users use 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. For example, if there are multiple 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. 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. Then, you can rename it and associate a different checklist (database) for each list.