/

In the spreadsheet you define one cell that say the test is success or not.  Set up the quality control point as shown here.  

You can then create a automatic action to send message based on fail in the control check.

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