The Check-In/Out service is for instances that may require your users to verify the status of a given value. For example, you can use this application in attendance scenarios to record who entered or didn’t enter. Similarly, you can check if an asset is in a truck, a physical site, or a warehouse. The Check-In/Out service can incorporate a database to validate against. Also, you can simply use it to record attendance when there is no specific list.
1. First, you can name your service. Also, link a database to validate your service against. Then, choose Mode.
2. Next, you can choose a default for unscanned values. Logically, it asks you to define the value. For example, if you are using the service for attendance, anyone not scanned is checked out. Whereas, if you are using the service for tracking assets (e.g. equipment, vehicles, etc.) any unscanned item is checked in.
3. Then, you can show the last user scanning and/or times for a given value to the current app user. You are given the option to disallow check-ins/outs when the value is already checked in/out. This means, if a value is checked in and the user attempts to select check-in again, the answer will be recorded as invalid. However, you can choose to show the check-in/out question with each duplicate scan or not. This gives the user the option to select the opposite of what is the current status so that they may submit a valid scan. This is shown below for greater clarity.
4. Additionally, you may edit the question asked with each check in/out. You can select any question you’ve created for all services through the Question tab of your account. If you would like to input a new question, you will need to add it via the Questions tab. Leaving it as is or “create automatically” will retain the Check In and Check Out options as well as keep the question being asked as “Select the action.” However, you may want to change what this question says as shown in the example below.
5. Finally, you have the option to limit a maximum of checked in and/or checked out items. When you enter a limit, anything scanned beyond that number will be marked as invalid until a more values are checked out. For example, if the limit is 3 total checked in values, when a fourth value is scanned, it will return as invalid. All subsequent scans will remain invalid until a value is checked out and the total number is back under the limit.
You can find this feature on the tasks page by clicking “Add a Task.” This task is made specifically for Check In/Out services and has some special options to enhance your reporting.
At the top of the creation page, you’ll scheduling options. As with all tasks, you can choose to schedule your export periodically or just download the scans once. Using the custom schedule option allows you to create multiple tasks for different repetitions if need be.
The second of half of the page is where you’ll find the filtering options specific to Check In/Out. After selecting the service you’d like to see scans for you can choose whether you’d like to include only check ins, check outs, or both. Next, we have an option to include a check in or out for values not checked in or out when scanning. What this means is the spreadsheet will be modified to include a second timestamp for your values but the status of the values will not actually be changed on CodeREADr.
For example, let’s say you have employees that need to clock in and out each day. You can set the spreadsheet to automatically check everyone out at 5pm. This will not change any values in the app or on the website to be checked out but it will show in your report who stayed until the required time each day.
Additionally, you can filter the export to include only a specific range of dates as needed. A start date is required to create the task but the end date by default is the current day. Finally, you have three options for the template- what’s included- in the export.
The descriptions for each are noted below.
Regular: The default template includes only the most recent timestamp and status for each value.
Extended: This template includes the first status and timestamp for each value as well as the last status (if more than 1 scan record) for each value. It also includes a “duration” column showing the difference between the two times for each value, reported in milliseconds.
History: This template builds on the extended template, including all of the timestamps and statuses for every value.
From here, you can finish your services. You can add users, questions, and alter advanced settings. However, no questions or advanced settings are necessary for the service to work properly. Below, we walk through how to use the service in-app.
When your authorized mobile app user(s) choose this service on the mobile app, they will see this screen:
In this example, we need the session info because we are using Fast Mode.
Once you choose the action, you can proceed to scan. Checked IN valid scans appear like this:
All valid scans will appear this way until a new action is chosen:
When you select Check OUT, all valid scans will appear as so:
In Fast Mode with duplicate Check In/Out disallowed but the question not shown, invalid scans appear as so.
In Fast Mode with duplicates disallowed and the question asked again, invalid duplicates will be shown with the option to answer much like in Confirm Mode. Selecting an option here does NOT change the session info for subsequent scans.
As with any service, you can customize the display of the response. This image shows the default response. If you have selected Confirm Mode, there will be no session info to select on the app screen. Instead, with each scan, the default (either Checked IN or out based on what you designated on Step 2) will appear and the user can define the action for that scan:
On the CodeREADr website, you can view your Checked IN and Checked OUT statuses by clicking “View Items in Portal”. You should refresh this view as often as necessary.
On the lookup page, you will see you can also sort by a few different options. The dropdown includes the following:
ID – This orders the list numerically/alphabetically by the barcode value
Description – This orders the list alphabetically by the response value
Timestamp – This orders the list by the time the scan was taken
ASC/DESC – This refers to ascending and descending as a way of ordering the list
On the mobile app, your app user(s) can view statuses by clicking on the “Lookup” tab. It auto-refreshes the in-app web view. However, you can manually refresh by tapping the refresh icon.