This page (revision-22) was last changed on 26-Nov-2021 10:22 by lurtan

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
22 26-Nov-2021 10:22 14 KB lurtan to previous
21 26-Nov-2021 10:22 14 KB rforbes to previous | to last

Page References

Incoming links Outgoing links
GENUS CLOCK APPLICATIONS
GENUS CLOCK APPLICATIONS

Version management

Difference between version and

At line 71 changed 4 lines
*The idle screen is the screen which all clocks revert back to when waiting for a user to punch. This screen may include such information as a main title(TITLE), welcome message (WELCOME_MESSAGE), punch IN and OUT(*) prompts(*), verification prompt(*), Software Version(G2 only), time stamp including date and time.
(*) - Located on function buttons only on the G1: F1-Punch IN, F2-Punch OUT F3-verify, F4-Enroll(**), F5-remove print(if applicable to clock reader) (**), F6-Edit punch(**), F11 - Turn Debug on and off, F12-Memory Capacity Test /Current queue size.
*The G2 provides access to the administrator's screen and functions using the F1 key(**).
(**) -These functions are restricted and requires an administrator to enter the admin pass code defined in the configuration file (PASSCODE) before access is granted.
*The idle screen is the screen which all clocks revert back to when waiting for a user to punch. This screen may include such information as a main title(TITLE), welcome message (WELCOME_MESSAGE), punch IN and OUT(*) prompts(*), verification prompt(*), software version(G2 only), time stamp including date and time.\\(*) - Located on function buttons only on the G1: F1-Punch IN, F2-Punch OUT F3-verify, F4-Enroll(**), F5-remove print(if applicable to clock reader) (**), F6-Edit punch(**), F11 - Turn Debug on and off, F12-Memory Capacity Test /Current queue size.
*The G2 provides access to the administrator's screen and functions using the F1 key(**).\\(**) -These functions are restricted and requires an administrator to enter the admin pass code defined in the configuration file (PASSCODE) before access is granted.
At line 78 changed one line
*A user may then be requested to enter a valid cost center code if defined in the configuration file (ENTER_COST_CENTER). The entered code is validated against a list provided in the configuration file (VALID_COST_CENTERS). An error sound and light will tell the user of an invalid entry and the punch attempt is stopped. If a valid cost center code is entered the user will then be allowed to continue the punch.
*A user may then be requested to enter a valid cost center code if defined in the configuration file (ENTER_COST_CENTER). The entered code is validated against a list provided in the configuration file (VALID_COST_CENTERS). An error sound and light will tell the user of an invalid entry and the punch attempt is stopped. If a valid cost center code is entered, the user will then be allowed to continue the punch.
At line 81 changed 2 lines
*Employees may be requested to punch into a specific job (ENTER_JOB). When this is true, the information collected identifying the employee is sent immediately to the server for validation and a list of jobs the employee may clock into is returned to the clock. If the employee has only one assignment the punch will be recorded and the clock will declare a successful punch recorded.
*If validation is not required the punch details will be stored into clock memory (the queue) for speed to allow the next user to punch. All details collected within the defined (QUEUE_SLEEP_TIME) are sent to the server. Once the details are stored in the queue a successful completion message is given and the clock is reset back to the welcome screen for the next user.
*Employees may be requested to punch into a specific job (ENTER_JOB). When this is true, the information collected identifying the employee is sent immediately to the server for validation and a list of jobs the employee may clock into is returned to the clock. If the employee has only one assignment, the punch will be recorded and the clock will declare a successful punch recorded.
*If validation is not required, the punch details will be stored into clock memory (the queue) for speed to allow the next user to punch. All details collected within the defined (QUEUE_SLEEP_TIME) are sent to the server. Once the details are stored in the queue a successful completion message is given and the clock is reset back to the welcome screen for the next user.
This page (revision-22) was last changed on 26-Nov-2021 10:22 by lurtanTop