This release is a pre-release and may not be stable for production use.
Employee Identification Numbers from Previous System
When switching from a legacy HR system to a new one. It may be necessary to have a record of the ID No. used in the previous system.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback here.
Credits
Contributors
Michael Telahun Makonnen <mmakonnen@gmail.com>
Adrien Peiffer (ACSONE) <adrien.peiffer@acsone.eu>
Maintainer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit http://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo8-addon-hr-employee-legacy-id 8.0.1.0.0.99.dev10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo8_addon_hr_employee_legacy_id-8.0.1.0.0.99.dev10-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_hr_employee_legacy_id-8.0.1.0.0.99.dev10-py2-none-any.whl |
Release files / odoo8_addon_hr_employee_legacy_id-8.0.1.0.0.99.dev10-py2-none-any.whl
| Download URL | odoo8_addon_hr_employee_legacy_id-8.0.1.0.0.99.dev10-py2-none-any.whl |
|---|---|
| Size | 26.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
fa43a5417a3b1410ae355732fbea200479388605539df783990b6c43bed2af83
|
|
BLAKE2b-256 checksum How to use checksums |
f45be710bbf3610459fb1b234e013e741ef4603206d32dcee54e96515103d072
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo8-addon-hr-employee-legacy-id 8.0.1.0.0.99.dev10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
