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 77 changed one line
*The user will be asked to identify themselves using the reader built into the clock being used. If permitted (ALLOW_KEYING), a prompt stating a badge code may be entered manually to identify the employee will be displayed. If this is set to false, all keying for all employees will be removed. If using a biometric reader, some employees may be unable to record a bio template successfully. If that is the case, the administrator may define specific employees who are allowed to key their badge. (VALID_KEYED_VALUES a comma separated list of badge numbers). All badge values will be validated for minimum and maximum length. (MIN_BADGE_LEN, MAX_BADGE_LEN)
*The user will be asked to identify themselves using the reader built into the clock being used. If permitted (ALLOW_KEYING), a prompt will be displayed, stating a badge code may be entered manually to identify the employee. If this is set to 'False', all keying for all employees will be removed. If using a biometric reader, some employees may be unable to record a bio template successfully. If that is the case, the administrator may define specific employees who are allowed to key their badge. (VALID_KEYED_VALUES a comma separated list of badge numbers). All badge values will be validated for minimum and maximum length. (MIN_BADGE_LEN, MAX_BADGE_LEN)
At line 83 changed 3 lines
*The Idle screen has a function button dedicated to initiate the employee verification. When pressed the user is given two choices. One to verify using the reader or to enter the employee number.
%%information: The employee number will be either the eP "Person code" (defined in IEID) or the employees defined "clock card code" (defined in ITCC). This is important to know depending on the reader type being used. The clock card code may only be a numeric value since both clocks (G1 and G2) only support numeric keying. The USE_BADGE in the configuration file defines this; A true value will validate against the HR IEID record. A false value will validate against the ITCC record.%%
*Validation using the reader will verify the badge number ( Please refer to USE_BADGE attribute. ) on the server. Biometric readers will verify that biometric templates exist in the clock memory first then check the server for validation.
*The Idle screen has a function button dedicated to initiate the employee verification. When pressed, the user is given two choices. One to verify using the reader and the other to enter the employee number.
%%information: The employee number will be either the "Person code" (defined in [IEID]) or the employees defined "clock card code" (defined in [ITCC]). This is important to know depending on the reader type being used. The clock card code may only be a numeric value since both clocks (G1 and G2) only support numeric keying. The USE_BADGE in the configuration file defines this, a true value will validate against the HR IEID record. A false value will validate against the ITCC record.%%
*Validation using the reader will verify the badge number (Please refer to USE_BADGE attribute.) on the server. Biometric readers will verify that biometric templates exist in the clock memory first then check the server for validation.
This page (revision-22) was last changed on 26-Nov-2021 10:22 by lurtanTop