This release is a pre-release and may not be stable for production use.
Odoo Agreement App does not provide an easy way to access field service orders related to an agreement. Some organizations needs to have a quick access to field service orders to track the performance of an agreement.
This module allows you to link a field service order to an agreement and adds a smart button on the agreement to look at the list of related field service orders.
Table of contents
Usage
To use this module:
Go to Field Service > Operations > Orders
Select or create a field service order and set the agreement
Go to Agreement > Agreements
Open the previous agreement
Click on the smart button “Service Orders” to see the list of related field service orders
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
Bhavesh Odedra <bodedra@opensourceintegrators.com>
Sandip Mangukiya <smangukiya@opensourceintegrators.com>
Other credits
The development of this module has been financially supported by:
Open Source Integrators
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 maintainers:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo11-addon-fieldservice-agreement 11.0.1.0.0.99.dev16
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 |
|---|---|---|---|---|
| odoo11_addon_fieldservice_agreement-11.0.1.0.0.99.dev16-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_fieldservice_agreement-11.0.1.0.0.99.dev16-py2.py3-none-any.whl |
Release files / odoo11_addon_fieldservice_agreement-11.0.1.0.0.99.dev16-py2.py3-none-any.whl
| Download URL | odoo11_addon_fieldservice_agreement-11.0.1.0.0.99.dev16-py2.py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
feb50f5566fdb43123cce29e76e9f675de50b31914ed32847cb643bf1041883c
|
|
BLAKE2b-256 checksum How to use checksums |
c3515d6459df2b2de74ac32854753861441c2244a15cb22a41ab4b9d37ca1e04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo11-addon-fieldservice-agreement 11.0.1.0.0.99.dev16
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.
