Rollback HandPunch Templates - Revision history

Stage at 23:39, 12 November 2015

2015-11-12T23:39:13Z

Stage at 20:27, 28 September 2015

2015-09-28T20:27:19Z

Stage at 20:12, 9 May 2015

2015-05-09T20:12:29Z

Stage at 03:00, 7 May 2015

2015-05-07T03:00:28Z

Stage at 02:57, 7 May 2015

2015-05-07T02:57:17Z

Stage at 02:53, 7 May 2015

2015-05-07T02:53:42Z

Stage at 18:45, 6 May 2015

2015-05-06T18:45:22Z

Stage: Created page with "{{Advanced}} When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand tem..."

2015-05-06T16:08:21Z

Created page with "{{Advanced}} When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand tem..."

New page

{{Advanced}}

When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees it is easiest to remove and re-enroll the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch when the punches are polled from the clock.

@@ Line 70: / Line 70: @@
 	FkTimeClockID = 876861399)</nowiki>
-Note that we are using the templates from successful punches made on any time clock. The rollback procedure is best done for a range on one month, moving back a month at a time.
+Note that we are using the templates from successful punches made on any time clock. The rollback procedure is best done for a range of one month, moving back a month at a time.
 See also
 * [[HandPunch]]

@@ Line 3: / Line 3: @@
 {{Advanced}}
-When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment|re-enroll] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is polled from the clock. The rollback procedure needs to be performed in [[SQL Management Studio]].
+When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. A hand template that previously worked can now have a problem being used at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration every time an employee punches. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment|re-enroll]] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is made at the clock. The rollback procedure needs to be performed in [[SQL Management Studio]].
 It is best to rollback templates only for employees that were having biometric issues. An example of a query that selects TRY AGAIN or ID REFUSED clock punches is:

← Older revision		Revision as of 20:12, 9 May 2015
Line 1:		Line 1:
		+	[[image:HandPunch.png\|right]]
		+
	{{Advanced}}		{{Advanced}}

Line 69:		Line 71:

	Note that we are using the templates from successful punches made on any time clock. The rollback procedure is best done for a range on one month, moving back a month at a time.		Note that we are using the templates from successful punches made on any time clock. The rollback procedure is best done for a range on one month, moving back a month at a time.
		+
		+	See also
		+
		+	* [[HandPunch]]

@@ Line 3: / Line 3: @@
 When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment|re-enroll] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is polled from the clock. The rollback procedure needs to be performed in [[SQL Management Studio]].
-It is best to rollback templates only for employees that were having biometric issues. An example of a query that selects TRY AGAIN or ID REFUSED clock punches is:<nowiki>
+It is best to rollback templates only for employees that were having biometric issues. An example of a query that selects TRY AGAIN or ID REFUSED clock punches is:
   <nowiki>
@@ Line 12: / Line 12: @@
 WHERE
 	RawPunchType = 3 OR
-	RawPunchType = 6
+	RawPunchType = 6</nowiki>
 </nowiki>
 This is a more advanced query that limits the results to a date range and to a single time clock:
 SELECT
+	*
@@ Line 26: / Line 26: @@
 	RawPunchDateTime > '05/05/2015 22:00' AND
 	RawPunchDateTime < '05/06/2015 09:00' AND
-	FkTimeClockID = 876861399
+	FkTimeClockID = 876861399</nowiki>
 Once the subset of employees have been identified then the full query needs to update the Employee Clock ID (EmployeeClockID) table with the template information from the Raw Punch table (RawPunch), joining on the employee key (FkEmployeeID), and ensuring that we use only successful punches (RawPunchType = 7) from a given date range (RawPunchDateTime), and finally, filtering the scope of this query to the employees returned in the above query.
 UPDATE
 	EmployeeClockID
@@ Line 65: / Line 66: @@
 	RawPunchDateTime > '05/05/2015 22:00' AND
 	RawPunchDateTime < '05/06/2015 09:00' AND
-	FkTimeClockID = 876861399)
+	FkTimeClockID = 876861399)</nowiki>
 Note that we are using the templates from successful punches made on any time clock. The rollback procedure is best done for a range on one month, moving back a month at a time.

@@ Line 3: / Line 3: @@
 When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment|re-enroll] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is polled from the clock. The rollback procedure needs to be performed in [[SQL Management Studio]].
-It is best to rollback templates only for employees that were having biometric issues. An example of a query that selects TRY AGAIN or ID REFUSED clock punches is:
+It is best to rollback templates only for employees that were having biometric issues. An example of a query that selects TRY AGAIN or ID REFUSED clock punches is:<nowiki>
 SELECT
+	*
@@ Line 12: / Line 13: @@
 	RawPunchType = 3 OR
 	RawPunchType = 6
 This is a more advanced query that limits the results to a date range and to a single time clock:

← Older revision		Revision as of 02:53, 7 May 2015
Line 1:		Line 1:
	{{Advanced}}		{{Advanced}}

−	When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment\|re-enroll] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is polled from the clock.	+	When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment\|re-enroll] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is polled from the clock. The rollback procedure needs to be performed in [[SQL Management Studio]].
		+
		+	It is best to rollback templates only for employees that were having biometric issues. An example of a query that selects TRY AGAIN or ID REFUSED clock punches is:
		+
		+	SELECT
		+	*
		+	FROM
		+	RawPunch
		+	WHERE
		+	RawPunchType = 3 OR
		+	RawPunchType = 6
		+
		+	This is a more advanced query that limits the results to a date range and to a single time clock:
		+
		+	SELECT
		+	*
		+	FROM
		+	RawPunch
		+	WHERE
		+	(RawPunchType = 3 OR
		+	RawPunchType = 6) AND
		+	RawPunchDateTime > '05/05/2015 22:00' AND
		+	RawPunchDateTime < '05/06/2015 09:00' AND
		+	FkTimeClockID = 876861399
		+
		+	Once the subset of employees have been identified then the full query needs to update the Employee Clock ID (EmployeeClockID) table with the template information from the Raw Punch table (RawPunch), joining on the employee key (FkEmployeeID), and ensuring that we use only successful punches (RawPunchType = 7) from a given date range (RawPunchDateTime), and finally, filtering the scope of this query to the employees returned in the above query.
		+
		+	UPDATE
		+	EmployeeClockID
		+	SET
		+	HandPunchTemplate0 = RawPunch.HandPunchTemplate0,
		+	HandPunchTemplate1 = RawPunch.HandPunchTemplate1,
		+	HandPunchTemplate2 = RawPunch.HandPunchTemplate2,
		+	HandPunchTemplate3 = RawPunch.HandPunchTemplate3,
		+	HandPunchTemplate4 = RawPunch.HandPunchTemplate4,
		+	HandPunchTemplate5 = RawPunch.HandPunchTemplate5,
		+	HandPunchTemplate6 = RawPunch.HandPunchTemplate6,
		+	HandPunchTemplate7 = RawPunch.HandPunchTemplate7,
		+	HandPunchTemplate8 = RawPunch.HandPunchTemplate8
		+	FROM
		+	EmployeeClockID
		+	INNER JOIN
		+	RawPunch
		+	ON
		+	EmployeeClockID.FkEmployeeID = RawPunch.FkEmployeeID
		+	WHERE
		+	RawPunch.RawPunchType = 7 AND
		+	RawPunch.RawPunchDateTime > '02/01/2015' AND
		+	RawPunch.RawPunchDateTime < '03/01/2015' AND
		+	RawPunch.HandPunchTemplate0 <> 0 AND
		+	RawPunch.HandPunchTemplate0 <> 255 AND
		+	EmployeeClockID.FkEmployeeID IN
		+
		+	(SELECT
		+	FkEmployeeID
		+	FROM
		+	RawPunch
		+	WHERE
		+	(RawPunchType = 3 OR
		+	RawPunchType = 6) AND
		+	RawPunchDateTime > '05/05/2015 22:00' AND
		+	RawPunchDateTime < '05/06/2015 09:00' AND
		+	FkTimeClockID = 876861399)
		+
		+	Note that we are using the templates from successful punches made on any time clock. The rollback procedure is best done for a range on one month, moving back a month at a time.

← Older revision		Revision as of 18:45, 6 May 2015
Line 1:		Line 1:
	{{Advanced}}		{{Advanced}}

−	When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees it is easiest to remove and re-enroll the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch ~~when the punches are~~ polled from the clock.	+	When an existing HandPunch is replaced with a new HandPunch, there can be a difference in the calibration from the existing to the new clock. As such, a hand template that previously worked can now have a problem punching at the new clock. It is not the clock that is causing the issue, but the hand template. This occurs because the hand template adjusts to the clocks' gradual change in calibration. If a small number of employees are affected, it is easiest to remove and [[HandPunch Enrollment\|re-enroll] the employees. If a large number of employees are affected then the templates can be rolled back to an older template. This is possible because the hand template is retrieved from the HandPunch for every punch that is polled from the clock.