The first section on this page is for specifying your particular scanning use to improve the speed of scanning. Enable it by checking the box and configure by clicking on “add scanner customization.” This will take you to a pop-up where you can enter a few different selections.
Allow users to delete scans saved on-device
This feature allows users to delete scans that have been saved on the device but haven’t been uploaded yet. Once you upload the scans, you can delete them on the Scans page of CodeREADr.com.
Allow users to edit answers saved on-device
By enabling this feature, every app user can edit their own data collection answers. Once uploaded, this data cannot be edited.
Allow users to view other users’ scans
This feature allows app users to see all scans from this service in real-time. If enabled, this will display all scans in the online History tab of the CodeREADr app. This feature is useful for app-users who need to cross-reference scans made by other app users. By allowing other app users to see these scans, they can easily check the scan status with any device.
However, before enabling this feature, consider potential privacy issues. For instance, all scanned data for that service would be visible to all app-users. Also, if you enabled deleting or editing, all app users can delete or edit scan records even if they didn’t create the original record.
Allow users to edit online scan
You may want your users to be able to edit answers before they upload the scans. You can find the explanation above as allowing ‘users to edit answers saved on device’. Also, you may want them to edit scans even if they have been sent to the server by allowing ‘users to edit online scans’. You can editing scans this way by enabling on-device editing.
Forbid users from backing up scans on-device when connectivity fails
By enabling this feature, your app-users cannot save scans on the device if connectivity fails. Also, you must submit all scans online. This feature forces app users to keep trying to connect. However, if they cannot, it forces them to contact their manager.
This service should only be active for a limited duration
If you’re creating a service for an event, or you’re using CodeREADr for a project with a definite beginning and end date, you’ll want to keep people from scanning when the event is already over, or when it hasn’t yet begun. You can do this automatically by setting an active duration for the service. When a user signs in before or after the active duration, the app will not display this service. To enable this feature, click this checkbox. Then, click on the boxes to specify the date you’d like the service to begin and end.
Duplicate scans on-device are INVALID
This option allows you to decide if the device should also have its own duplicate checking when scanning. If you are relying upon internet connectivity for duplicate checking but you think the app-user may lose connectivity, you’ll want to check this box. However, please note that this duplicate checking option only applies to the device scanning, not all devices scanning. To apply for all devices scanning you’ll instead want to create an on-device (offline) service with auto-sync enabled and duplicates set to be invalid globally.
With Manual Sync, the user must upload the scans to the server themselves. Then, the device will auto-check for a new database after an upload.
With Auto Sync, the system will queue scans for on-device service for auto-uploading to our server every two seconds after the validation. Then, the system will auto-sync the validation databases to the device every 2 minutes. There must be the Internet to be able to sync. Also, the service must be open within the mobile app to sync. Learn more about Auto Sync here.
Email me when on-device scans are uploaded
By enabling this feature, scans uploaded from an on-device service will be immediately forwarded to the email address defined here by the account Administrator.
Postback each on-device scan uploaded to a specified URL
If you are a developer, you can choose here to enable postback to send each scan to your own server and/or validate against a database on your own server. Get more information on using Postback URL services here.
Alter Scan Value
This feature enables parsing the original data read when each barcode matching a specified pattern is scanned. It passes only the parsed data as the scan record, whether for recording or validation purposes. This feature is useful if you need to submit a portion of the scanned data. For example, driver’s licenses, trade show badges, student and member IDs, and asset tags.
Alter Response Value
This feature enables you to customize the display of the information to the app user after submitting a scan. When it detects a defined pattern within your original, default response text, the app will instead display custom, formatted text to the app users based on the replacement template you create.
Auto-Next will ensure that the user moves quickly through the scanning process by moving back to the scanning view. You can choose a delay time in seconds before the app reopens the camera for scanning. With Auto-Next, you can have the screen advance only when a scan is valid and halt when it is invalid. Moreover, you can always advance with the options to discard or save scans that return errors.
Using Auto-Next with the single-line option auto-advances the cursor to the next field and auto-submits the record when the “Enter” button is pressed. Thus, the data collection process will be very fast. In contrast, the multi-line option forces the app user to manually advance by tapping the next field. Tapping “Enter” on this section allows the user to enter multiple lines of data rather than moving to the next question the next field or submitting the entire record.
Do not automatically reopen camera after each scan
When your app-user is scanning, the camera will, by default, reopen to show the user the camera scanning view. If you want to bring the user back to the ‘Tap to Scan’ screen, disable the re-opening of the camera.
Disable Camera Scan, Manual Scan, and/or Lookup
If you’d like to remove the ability to scan with the device’s built-in camera and only use manual entry, or vice versa, you can disable the camera or manual scanning. This is useful when using a scanning accessory. If you’d prefer your users not be able to access the database by searching its values, disable the lookup feature to show scanned and unscanned data.
Enable Kiosk Mode
This mode locks the device into a particular service in the application. You will need to set a PIN so you can unlock and lock the device. Then, users cannot move from the service and may only use it to scan. We have more specifics on what you can include in your configuration to customize it. For example, there are custom branding and instructions to help users. Learn more about the Kiosk mode for barcode scanning here.
Barcode GPS Location Tracking
Collect or Track Device GPS Location without interruption as a property with each scan
Track GPS location with barcode scanning. First, you can record the GPS location of the device at the time of each scan in the background as a scan property. It’s another great way to increase accountability, allowing you to confirm each scan’s actual location. Alternatively, you can collect GPS locations in the foreground as a Question prompt. Learn more about collecting data with questions here.
While our Scans page offers a map view, to visualize each scan as pins on a map, including the associated data in each scan record, the ideal method is to use Google’s My Maps custom map builder. Learn more about importing scans to Google’s My Maps here.
Enable custom web view for lookup and history
In the advanced settings, you can make changes to what the lookup and history sections of the device display.
Enable custom display configuration
Here, you can add customization to the look of the response display screen. See how you can customize the scan response.
Enable on-device custom validation
Enable the PRINT option
You can also configure the integration of a printer using Mobi Print.