Instructions for a Check In/Out Service
Check In/Out is a curated service designed specifically for instances that may require your users to verify the status of a given value. For example, this application may be used in attendance scenarios to account for those who have entered the room and those who have not. Similarly, another use case may be checking that an asset has been placed on a truck or deployed to a physical site or subsequently returned to the truck or warehouse. The Check In/Out service can incorporate a database to validate against or may simply be used to record attendance when there is no specific list known beforehand.
To configure this service follow the steps below:
1. On the Services page, click “Add a Service” and select “Check In/Out”
2. On this first page, you can name your service, as well as link a database to validate your service against. As well, you’ll need to choose a Mode.
Fast Mode: Prompts session info to be provided before scanning that determines whether scans will be verified for checking in or checking out. In this mode, “session” refers to a series of scans that will occur sequentially. In Fast Mode, the session is changed when the user switches between checking in and checking out.
Confirm Mode: Asks before each scan if the asset should be checked in or out.
If you’ll be scanning at designated times for both checking in and out, then you will likely want to use Fast Mode and change the session from checking in to checking out with the appropriate time window. If there’s only one checkpoint and/or no specific time for checking in vs. checking out, you’ll probably need to choose the Confirm Mode.
Next, you’ll be asked to choose a default for unscanned values. Logically, you’re being asked to define what a value is designated before being scanned. 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 item not scanned is checked in.
Finally, you have the option to show last user scanning and/or times for a given value to the current app user.
3. From here, your service can be finished. You’ll be given the option to add users, questions, or alter advanced settings as with any other service type. However, no questions or advanced settings are necessary for the service to work properly.
When your authorized mobile app user(s) choose this service on the mobile app they will be presented with this screen:
In this example, the session info is needed because we are using Fast Mode.
Once the action is chosen, scanning can proceed as usual. Checked IN valid scans appear like this:
All valid scans will appear this way until a new action is chosen:
With Check OUT selected, all valid scans will appear as so:
As with any service, the display of the response can be fully customized however you may desire. Shown in the above images is simply 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.
And it will appear like this:
On the mobile app, your app user(s) can view statuses by clicking on the “Lookup” tab. This in-app web view is auto-refreshed but you can also manually refresh by tapping the refresh icon.