Clocks 7.0.0.2 resolved issues

Total: 9 issues

----------------

WFMC-1124

DbUpdate does not bring the change if reader's reader group is changed to another group of different clock server

If reader group is changed to another group belonging to different clock server, a change history record is created. Dbupdate does not bring the change. The reader is seen on the terminals with the old reader group ID. Tabledump is required to remove the reader.

Outcome

Fixed by WFMC-1125 and WFMC-4188.

----------------

WFMC-1125

DbUpdate does not remove the reader from terminals if it is deleted from WFM

If a Reader is deleted from the WBCS Standalone Clock Server, a change history record is created. dbupdate brings the change history ID, but there is no detailed logs and it does not remove the reader from the terminals.

Outcome

Fixed. Refactored the query of collecting delete change records.

----------------

WFMC-1441

DbUpdate brings tomorrow's schedule when wbsynch.schedules.days is set to 0(Clock side)

Changes to tomorrow's schedule is brought down through dbupdate and is displayed on the clock while Viewing Schedule, when wbsynch.schedules.days=0.

Outcome

Fixed. Added start day and end day to the request of schedule for dbupdate.

----------------

WFMC-1444

Approval records are not removed from database statistics in Admin Console when an employee becomes inactive

Number of approval records are not removed from the database statistics when an employee becomes inactive and when employee is removed from the reader group.

The records are removed and downloaded when employee's status and reader group is changed (can be seen in Employee Time Approval tab).

Outcome

Fixed. Added removing approvals.

----------------

WFMC-4135

Failed to delete finger print message is displayed in clock.log during unenrollment, badge removal, inactive status change, disabling biometric flag when the clock is in Verification mode

Clock displays "Failed to delete finger print" warning message is displayed for several use cases.

Outcome

Fixed. Should ignore user delete message if reader is in verification mode. When unenrolling an employee from a clock in verification mode, no need to delete template as it's not loaded in verification mode.

----------------

WFMC-4175

Employee Schedules are not downloaded if the clock goes offline during reader's reader group change

During reader's reader group change, dbupdate triggers tabledump in which EMPLOYEE_SCHEDULE table is included as part of the update.

When it resets the last change history id to 0 during the clock reboot or WFM going offline, table dump for EMPLOYEE_SCHEDULE is not part of the same dbupdate.

EMPLOYEE_SCHEDULE tabledump runs separately after the dbupdate and synchronizes the records if the clock is rebooted. When there is network failure, it does not follow after the dbupdate.

Outcome

Fixed. Include employee Bio data and employee schedule in the table dump triggered by DbUpdate.

----------------

WFMC-4176

Employee Biodata are not downloaded if the clock is rebooted/disconnected during reader's reader group change

During reader's reader group change, dbupdate triggers tabledump in which EMPLOYEE_BIO_DATA table is included as part of the update.

During initial dbupdate when the change history id is -1, Table dump for EMPLOYEE_BIO_DATA is performed.

When it resets the last change history id to 0 during the clock reboot or WFM going offline, table dump for EMPLOYEE_BIO_DATA is not part of the same dbupdate.

The templates are not downloaded until a tabledump is requested.

Outcome

Fixed. This is resolved by WFMC-4175.

----------------

WFMC-4181

DbUpdate brings tomorrow's schedule when wbsynch.schedules.days is set to 0 (WFM side)

Outcome

Fixed. Changed code to accept start day and end day in DB update.

----------------

WFMC-4189

Handle DBUpdate compatibility when 7.1.0.0 clock connect to WFM pre-7.0.0.1

The change done in WFMC-1441 introduced new properties in DbRequest which will break the communication when 7.1 clock connects to WFM pre-7.0.0.1. Handle this so that a 7.1 clock is compatible with WFM version before 7.0.0.1.

Outcome

Fixed. Send the compatible schedule update request based on the WFM version.

----------------