Repair Quality Control
This module allows to create quality control inspections from repair orders. One repair order can be linked to many different inspections.
The related inspections can be created either on the confirmation of the repair order, or when it is done. The creation can be executed manually or automatically. Both of these aspects are configurable at a company level.
Moreover, you can configure trigger lines at a Product, Product Template or Product Category level (using the ‘Repair’ trigger) to set the QC Test to use when creating the inspections.
Table of contents
Usage
To use this module, you need to:
Configure the QC repair behavior for the company:
Go to Settings > Repair.
Configure the two settings related to QC Inspections.
Configure the triggers:
Go to Products > Products.
Select a product (this product must then be used in a repair order).
Go to the ‘Inventory’ tab.
In the ‘Quality Control’ section, select the QC Test to use when creating the inspections, for the ‘Repair’ trigger.
You can also configure the triggers at the product template or product category level.
Create a repair order:
Go to Repairs > Repair Orders.
Create new repair order.
Set the repair order to ‘Done’ or ‘Confirmed’ state.
An inspection should be created automatically or a button should appear to allow creating it manually.
You can access from repair order to inspection directly with a smart button and the same backwards.
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
-
Antoni Marroig <amarroig@apsl.net>
-
Laura Cazorla <laura.cazorla@forgeflow.com>
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/repair project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-repair-quality-control 18.0.1.0.0.6
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 |
|---|---|---|---|---|
| odoo_addon_repair_quality_control-18.0.1.0.0.6-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_repair_quality_control-18.0.1.0.0.6-py3-none-any.whl |
Release files / odoo_addon_repair_quality_control-18.0.1.0.0.6-py3-none-any.whl
| Download URL | odoo_addon_repair_quality_control-18.0.1.0.0.6-py3-none-any.whl |
|---|---|
| Size | 57.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a17a8fabdd7d51b6e3f67e60a262b8a3dcea790c5aa5515a5139468847ccf84
|
|
BLAKE2b-256 checksum How to use checksums |
660a8a62f63ffd86636d6fef742d8fddf344d4304c4d394cb87b36d1c2dbec99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-repair-quality-control 18.0.1.0.0.6
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.