This module implements a new dms directory structure under a root directories (unique by model and category). Each file can be created in a particular directory related to model instances and under a root directory, also model related.
Table of contents
Configuration
No specific configuration is required.
Usage
### Create root directories
To create root directories, follow this instructions:
Documents > Directories
Click create
Set “Is Root Directory”
Fill Model and category (which is optional but recommended under this module logic)
Save
Root directories with same model and category as existing ones cannot be created.
After, these directories can be used as parent directories.
### Create files
With this module we add a wizard to add documents (dms files) to model instances. By default, it is added to res.partner, but it can be added in other model form views as well. Once in this form views with our assitant to add modules:
Click on “Add documentation”
Upload file, and fill file name and file root directory.
Click on “Add”.
The file will be saved in a model related directory (same record name, linked to record) under the selected rood directory
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-dms-res-model-root-directory 16.0.1.1.0
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_dms_res_model_root_directory-16.0.1.1.0.tar.gz | 56.5 kB | Without provenance | Details |
Release files / odoo_addon_dms_res_model_root_directory-16.0.1.1.0.tar.gz
| Download URL | odoo_addon_dms_res_model_root_directory-16.0.1.1.0.tar.gz |
|---|---|
| Size | 56.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72e528cccff38498ce98d1aa81daad65e683739db1f76c2aa9290fe0e63772d4
|
|
BLAKE2b-256 checksum How to use checksums |
7e380eb87779d54e2e8712650feaffb2eb55af5b6696e243325f0f5e2ac7bcf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.2
|
Security for odoo-addon-dms-res-model-root-directory 16.0.1.1.0
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.
