Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
1 Odpowiedz
110 Widoki

Hi All,

We have a connected manufacturing process with multiple levels of BoMs:

A+B ->C

   ​C+D ->E

​      E+F->Finished Good.

Due to the nature of our industry, we create three separate Manufacturing Orders (MOs) to produce the finished good.

To reduce manual paperwork, we are building quality worksheet templates for each BoM item (C, E, and the Finished Good).

To be more specific,  We have two different semi-finished products, and each requires different quality thresholds for the same component. Our goal is to set separate thresholds and create automation rules to notify the responsible manager when a check fails.


In terms of technical perspective,  During creation of automation rules we enter the model name:

For Example:

Model Description Pre-op Inspection

Model  x_quality_check_worksheet_template_8


However, the technical name of a worksheet template (e.g., "Pre-op Inspection") changes if we create another version of "Pre-op Inspection" worksheet template for the second semi finished good to be able to set different threshold and trigger a warning.  


Our implementation partner has mention that any custom development related with specific work sheet template, should require another development if threshold has changed, because quality worksheet templates have been created dynamically after MO has been confirmed unless you use the same customized worksheet templates for second product but that is not aligning with the quality requirements.


My question:

Is this truly a limitation of Odoo? Does the approach described by our implementation partner sound correct?


Odoo version 17.0+e (Enterprise Edition)


Awatar
Odrzuć
Najlepsza odpowiedź

Hi,


Each Quality Worksheet Template is a record in quality.check.worksheet.template. When you duplicate or create a new template (even if it looks like “Pre-op Inspection v2”), it is technically a different record with a different XML/DB identifier.

→ This is why, when you create automations based on a specific template’s technical name (like x_quality_check_worksheet_template_8), that automation only applies to that one record. A second version will not automatically inherit the same rules.


The “new development” approach your partner mentioned is one way to handle it, but it’s not the only way. The core problem is that the automation is hard-linked to a template record, instead of to a more flexible configuration (like product, BoM level, or inspection type).


Alternative approaches that avoid custom dev per template version:


    Use Quality Points (quality.point model) to configure which product/BOM/operation requires which checks and thresholds. Each semi-finished product can have its own point and rules without duplicating template logic.


    Add custom fields (like tolerance/threshold values) on the worksheet or check model, and drive your automation rules from those fields instead of the template record ID.


    If you need version control of templates, you can add a custom field like “Inspection Type” (e.g., pre_op, final, etc.) that stays constant, and use that in your automation filters. That way you can create multiple versions but still group automations logically.


Hope it helps

Awatar
Odrzuć
Powiązane posty Odpowiedzi Widoki Czynność
1
sie 25
305
3
sie 25
1018
3
lip 25
535
2
lip 25
1147
1
cze 25
699