The PosiEd EDC package includes a well-developed Kiosk application that can perform the following types of functions:
Student Sign In/Out
Student Check In/Out
Staff Member Sign In/Out
Visitor Sign In/Out (Future Release)
This Kiosk function is unmanaged meaning that either your own in-house developers or your Salesforce partner can extend the Kiosk's functionality to meet your organization's specific needs if required. However, it provides a range of functions out-of-the-box and those functions can be administered through the Kiosk Definition object.
...
In the Contact Search field, specify which of the Contact search options you want the Kiosk to support. Currently, only Student ID and Name are supported for student kiosks. The Staff ID and Name are supported in the Staff Kiosk. Barcode and Camera are not yet supported.
...
These Contact Search options specify what options are available to the Kiosk user to locate their record in the Kiosk. For example, if you specify Student ID and Name, then the user can either type in their Student ID or their Name to locate their Contact record for the Sign In or Check In process.
Certain Kiosk functions send notifications to staff, in particular, the Sign In/Out functions. The Kiosk will locate the Staff Members of any Sessions that the student should currently be in if the student is late or leaving early, and will send notifications to those staff members. The Notification Channel option allows you to specify the method of communication to send these notifications to the staff members. Currently, only Salesforce notification is supported.
...
The In and Out checkboxes allow you to specify which functions are available on the specific Kiosk. For example, if this is a Sign In Kiosk, then you can specify whether you want it to support both Signing In and Signing Out, or just Signing In, or just Signing Out.
...
You may personalize the Kiosk page with the help of prompt fields. There are pre-provided default texts if the field is left empty,
Welcome Page
This page uses the Welcome Prompt field, if empty the default text is “Welcome to {{School}} {{Location}}”
In/Out Page
This page uses the In/Out Prompt field, if empty the default text is “Hello {{Name}} {{School_ID}} {{Grade_Level}}”
The In and Out buttons use the In Button Label and Out Button Label fields and if empty the default text is “In“ and “Out“.
Thank You Check In and Out Page
This page uses the Thank You In Prompt and Thank You Out Prompt fields if empty the default text is:
For Check In; “Thank you {{Name}}, you have checked-in at {{Location}}“
For Check Out; “Thank you {{Name}}, you have checked-out of {{Location}}“
Sign In page Default
On the Reason page for Arrival, it uses the In Reason Prompt field, if empty the default text is “You were supposed to sign-in at {{Expected_Arrival}}. Reason:“
On the Reason page for Departure, it use the Out Reason Prompt field, if empty the default text is “You were supposed to sign-out at {{Expected_Departure}}. Reason:“
Thank You Sign-In/Out with Reason Page Default
The Arrival page uses the Thank You In with Reason Prompt field, if empty the default text is “Thank you {{Name}}, you have signed-in at {{Location}} with Reason: {{Reason_Code}} {{Absence _Reason}}“
The Departure page uses the Thank You Out with Reason Prompt field, if empty the default text is “Thank you {{Name}}, you have signed-out at {{Location}} with Reason: {{Reason_Code}} {{Absence _Reason}}“
...
Once you have saved your Kiosk Definition, the next step is to assign Kiosk Reason codes to the Kiosk definition, if the Kiosk is a Student Sign In/Out or Student Check In/Out Kiosk.
...