TMS Document
Generic, expiry-tracked document framework for the TMS.
Attach typed documents (license, insurance, inspection, …) to any TMS resource (drivers, vehicles). Document validity (valid / expiring / expired) is computed from the expiry date against a configurable horizon.
A document can be flagged critical: an expired critical document on a trip’s driver or vehicle blocks starting that trip.
Table of contents
Configuration
The expiry horizon is controlled by the configuration parameter tms.document.expiry_horizon_days (default: 30 days).
A document whose expiry date is within this many days is considered expiring; once the expiry date passes, it is expired.
To change the horizon, set the parameter under Settings > Technical > Parameters (or via ir.config_parameter.set_param). A smaller value makes documents switch to expiring later; a larger value warns earlier.
Usage
Creating a document
Documents can be created from the Documents menu under TMS > Documents, or directly from a driver or vehicle form using the Documents tab. Click Create and fill in:
Document type: e.g. driver license, vehicle insurance, inspection.
Number / reference: the reference printed on the document.
Holder: the TMS resource the document belongs to (a driver or a vehicle).
Expiry date: used to compute the validity state.
Critical: mark the document as critical to enforce it on trip start.
When uploading a file from the Documents tab of a holder form, the document is automatically linked to that holder and the file is attached to the holder’s chatter.
Once saved, the document appears read-only in the Documents tab of its holder’s form, so all documents of a driver or vehicle are visible in one place.
Validity states
The document state is computed from its expiry date and the configured horizon (see Configure):
Valid — the expiry date is further away than the horizon.
Expiring — the expiry date falls within the horizon.
Expired — the expiry date is in the past.
Blocking trip start
When a trip is started, all documents of its driver and vehicle are checked. If any critical document is expired, a user error is raised and the trip cannot be started until the document is renewed, its expiry date is corrected, or it is no longer flagged critical.
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 to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Volkan Taşçı me@volkantasci.com
Other credits
VSL
Odoo Community Association (OCA)
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.
Current maintainer:
This module is part of the OCA/stock-logistics-transport project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file odoo_addon_tms_document-19.0.1.0.4.4-py3-none-any.whl.
File metadata
- Download URL: odoo_addon_tms_document-19.0.1.0.4.4-py3-none-any.whl
- Upload date:
- Size: 35.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/6.2.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
1cca93f9b445273ee7403faa6220aa13fda5fc1ff7f4a8955133fb4088965536
|
|
| MD5 |
7f681a2ba195d05ee9a3b2a1e033d0ba
|
|
| BLAKE2b-256 |
3c3f4cc91b68a8518efce50c9222135ec1d4def51cef1e13ee8c5590815bfd9a
|
