CRM LEAD PERSONAL FILE DATA
This module adds a lead data root directory related to the crm.lead model and a personal data root directory related to the res.partner model. It also adds listeners to move a lead’s personal data files (those under the category_personal_data category, e.g. the applicant’s own DNI) to their related partner, both when creating dms files on leads that already have a partner, or when assigning a partner to a lead that already has dms files under its lead data directory. Files of other categories (e.g. documentation tied to the requested service) stay on the lead.
It also extends crm_lead_dms_category’s _get_uploaded_document_categories on crm.lead so that documents uploaded on the lead’s partner (e.g. after being moved there by the listeners above) also count towards has_all_required_documentation, not just documents scoped to the lead itself.
The dms_directory_id and partner_dms_directory_id fields are shown on the lead form, inside the “documentation” tab.
Table of contents
Configuration
No specific configuration is required.
Usage
Listeners will act automatically moving dms files under the described conditions in the main module description.
Known issues / Roadmap
There are no issues for the moment.
Bug Tracker
Bugs are tracked on GitLab 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.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
José Robles <jose.robles@somit.coop>
Álvaro García <alvaro.garcia@somit.coop>
-
Gerard Funosas <gerard.funosas@somconnexio.coop>
Maintainers
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.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-crm-lead-personal-file-data 16.0.1.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| odoo_addon_crm_lead_personal_file_data-16.0.1.3.1.tar.gz | 29.5 kB | Without provenance | Details |
Release files / odoo_addon_crm_lead_personal_file_data-16.0.1.3.1.tar.gz
| Download URL | odoo_addon_crm_lead_personal_file_data-16.0.1.3.1.tar.gz |
|---|---|
| Size | 29.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
152495cdf25187c29ca61357b89afc52d9b796cbc250e72369426ccf7c349638
|
|
BLAKE2b-256 checksum How to use checksums |
3d9b044201c8876bd9539466a34d280853b31d798289d07260186e25f48f6842
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for odoo-addon-crm-lead-personal-file-data 16.0.1.3.1
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.
