This module uses checkins/checkouts from multiple remote biometric devices (using the SOAP service in the device) to fill the attendances list for employees.
PS: The Biometric Machine must be based on ZKTeco software, and have its webserver activated.
This Module Depends on the Attendance and HR Odoo modules, Odoo can resolve those Dependencies automatically.
How to use
This module once installed adds a menu to the Employees application as you can see in the picture below
Here you can create your first Biometric Machine via "Biometric Machines Management->Biometric Machines"
Machine IP: The IP address of the machine plus the port if it's not 80. Examples: 192.168.1.200, 22.214.171.124:8080, biometric.myserver.com:3333, etc...
Timezone: This is important because When Odoo saves times it considers them as UTC, and converts them when displayed to the client's timezone.
Last Download: A read-only attribute that will be updated every time the data is downloaded.
Once that done you should configure your employee Biometric Code. This is the code that associates an Odoo employee to a biometric device user.
Here our Employee Code is 14
After you finished associating Employees with their respective Biometric Code, you can run The Biometric Machine Data Download manually. This will download all attendances associated to your Odoo employees.
Now you can check the Downloaded Attendances from "Attendances->Manage Attendances->Attendances".
PS : Odoo default behaviour is to show only today's attendances so check the search filter.
In this Module you can configure the Odoo server to Periodically download Data from Biometric Machines, to do that you go to "Employee->Biometric Machines Management->Configuration".
By default, Odoo doesn't allow employees that never checked out of a session to check in the next time. This behaviour can be overrided by checking the "Allow checkins without checkouts" box. If you choose not to check it, Odoo will only download attendance sessions that ended by a checkout.
Attendances in Odoo will now have a new attribute called "Manually created". This field is true if the attendance session is created manually by a user. This helps the module detect days where attendances have been manually modified for a specific employee, and therefore it will not override those attendances on the next data download from the biometric device.
Any problems or unsuccessful data downloads will be reported in the "Attendance Exceptions" sub-menu.
To Access the Functionnalities of this Module you need to have Manager Level in Employee and Attendance Applications.
If you encounter any problem with this module please contact us on the following mail: email@example.com .
The Technical Support for installation is provided with the buy fee, any other request will be invoiced.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.