Fingerprint Service Log - Revision history

Stage: /* Admin Log */

2020-04-13T22:52:30Z

‎Admin Log

2019-01-02T14:59:56Z

‎Time Log

2019-01-02T14:56:43Z

‎Admin Log

2019-01-02T14:55:01Z

‎Admin Log

2019-01-02T05:38:48Z

‎Admin Log

2019-01-02T04:43:25Z

‎Admin Log

2019-01-02T04:34:33Z

‎Admin Log

2019-01-02T04:32:05Z

‎Admin Log

2019-01-02T04:31:32Z

2019-01-02T04:24:57Z

@@ Line 19: / Line 19: @@
   <nowiki>{"access_control":false,"action":"Insert User","admin_id":"","log_id":29,"result":0,"time":"Jan 1, 2019 10:29:05 PM","timezone_offset":"GMT-05:00","user_id":"10000"}</nowiki>
-* Update User - when a time clock receives a user that is already in the time clock, the clock sends an "Update User" message.
+* Update User - when a time clock receives a user that is already in the time clock, the clock sends an "Update User" message. This log has been deprecated.
   <nowiki>{"access_control":false,"action":"Update User","admin_id":"","log_id":31,"result":0,"time":"Jan 1, 2019 10:32:50 PM","timezone_offset":"GMT-05:00","user_id":"10000"}</nowiki>
-* Enroll Backup Fp - sent when a fingerprint is enrolled. The actual fingerprint data will be sent in the message type New Fingerprint. The action is oddly named but implies that a fingerrpint was enrolled, and the service should "BackUp the Fingerprint".
+* Enroll Backup Fp - sent when a fingerprint is enrolled. The actual fingerprint data will be sent in the message type New Fingerprint.
   <nowiki>{"access_control":false,"action":"EnrollBackupFp","admin_id":"","log_id":30,"result":6,"time":"Jan 1, 2019 10:30:55 PM","timezone_offset":"GMT-05:00","user_id":"10000"}</nowiki>

← Older revision		Revision as of 14:59, 2 January 2019
Line 57:		Line 57:
	== Time Log ==		== Time Log ==

−	One record per punch is created even if the time logs are sent together in one ~~Json~~ payload.	+	One record per punch is created even if the time logs are sent together in one payload.

@@ Line 13: / Line 13: @@
 ''' Admin Log Received '''
-This message type represents multiple actions. The action can been seen in the JsonData column.
+This message type represents multiple actions. The action can been seen in the JsonData column. Multiple messages (of the same message type) can be sent in the same payload and will create a single Admin Log record.
 * Insert User - when a time clock receives a user that is not in the time clock, the clock sends an "Insert User" message.

@@ Line 27: / Line 27: @@
   <nowiki>{"access_control":false,"action":"EnrollBackupFp","admin_id":"","log_id":30,"result":6,"time":"Jan 1, 2019 10:30:55 PM","timezone_offset":"GMT-05:00","user_id":"10000"}</nowiki>
-* App Version - sent after Clean DB is done at the clock when the clock is starting.
+* App Version - sent after Clean DB is done at the clock, or a Reset Device is sent from the management software.
   <nowiki>{"access_control":false,"action":"App Version","admin_id":"","data":"eyJWZXJzaW9uTmFtZSI6IlNla3VyZUlEIEFwcCAyLjguMTArIiwiRGJWZXJzaW9uIjoiMS4zOCIs\nIlBsdWdpbnMiOlsiVGltZWNvIDMuNDkrIl19\n","log_id":1,"result":1,"time":"Jan 1, 2019 11:20:23 PM","timezone_offset":"GMT-05:00","user_id":""}</nowiki>

@@ Line 53: / Line 53: @@
   <nowiki>{"finger_number":6,"template":"(Fingerprint data sent from clock)","user_id":"10000"}</nowiki>
-  <nowiki>{"user_id":"STAGE","finger_number":6,"template":"(Fingerprint data sent to clock)"}</nowiki>
+  <nowiki>{"user_id":"10000","finger_number":6,"template":"(Fingerprint data sent to clock)"}</nowiki>
 == Time Log ==
 One record per punch is created even if the time logs are sent together in one Json payload.

@@ Line 49: / Line 49: @@
 ''' NewFingerprint'''
-This occurs when the user enrolls an employee at the time clock but also when a fingerprint is sent to the time clock. The Jsondata is similar but the serial number is "server" when the fingerprint is sent from the service to the time clock, and it is the serial number of the time clock when the clock sends the fingerprint.
+This occurs when the user enrolls an employee at the time clock. There is also a log when the service sends a fingerprint to the time clock but this log is created by the service and the serial number will be "server".  The Jsondata is similar but the serial number is "server" when the fingerprint is sent from the service to the time clock, and it is the serial number of the time clock when the clock sends the fingerprint.
-  <nowiki>[{"finger_number":6,"template":"(Fingerprint data...)","user_id":"10000"}]</nowiki>
+  <nowiki>{"finger_number":6,"template":"(Fingerprint data sent from clock)","user_id":"10000"}</nowiki>
 == Time Log ==
 One record per punch is created even if the time logs are sent together in one Json payload.

@@ Line 43: / Line 43: @@
   <nowiki>{"access_control":false,"action":"BatchSet_WiredNet","admin_id":"","log_id":36,"result":0,"time":"Jan 1, 2019 11:14:58 PM","timezone_offset":"GMT-05:00","user_id":"0"}</nowiki>
-'' DeviceConnectionChanged ''
+''' DeviceConnectionChanged '''
 This occurs when the clock connects or disconnects from the service. Also occurs when the service is restarted. JsonData will contain true or false.
-'' NewFingerprint''
+''' NewFingerprint'''
 This occurs when the user enrolls an employee at the time clock but also when a fingerprint is sent to the time clock. The Jsondata is similar but the serial number is "server" when the fingerprint is sent from the service to the time clock, and it is the serial number of the time clock when the clock sends the fingerprint.

@@ Line 3: / Line 3: @@
 There are 2 logs maintained. Time Log records all punches made at the time clock while Admin Log records all other logs sent from the time clock.
-''' Admin Log '''
+== Admin Log ==
 The AdminLog will contain the following Message Types:
@@ Line 11: / Line 11: @@
 * New Fingerprint
-'' Admin Log Received ''
+''' Admin Log Received '''
 This message type represents multiple actions. The action can been seen in the JsonData column.
@@ Line 52: / Line 52: @@
   <nowiki>[{"finger_number":6,"template":"(Fingerprint data...)","user_id":"10000"}]</nowiki>