Summary
- Validation helps users detect missing, inconsistent or unacceptable report data before review and approval.
- The portal should support both general template-level validation and job-specific Work Order validation.
Visual overview
Validation layers
General template rules can be combined with job-specific Work Order rules.
All plans
Template validation
General rules that follow the template every time it is used.
Professional / Enterprise
Work Order validation
Job-specific rules for customer, project or contract requirements.
Practical rule
Use reusable templates for structure. Use Work Order validation when acceptance criteria differ between jobs.
Shop floor · Dimension Control
DCR-WO002-004
Width measurement
Measured value
42.84 mm
Requirement
43.00 ± 0.10 mm
Outside acceptance criteria
Create NCR or correct the registered value before submission.
Work Order
WO-002 · Medium Twinarms
Customer: Twinz · Project: Delivery of Twinarms
Reports
5 / 7
created
Approved
2
ready for export
Review
1
waiting
Material
3"
Heat 1234
Planned work
Raw Material Receipt
Template linked to WO-002
Saw Process
Template linked to WO-002
Extrusion Process
Template linked to WO-002
Heat Treatment
Template linked to WO-002
Dimension Control
Template linked to WO-002
Non-Conformance
Template linked to WO-002
Package Report
Template linked to WO-002
Task help
Common tasks in this area
Open the task that matches what you are trying to do. The full article continues below.
Validation
Choose validation level
Decide whether a rule belongs to the template or the Work Order.
Open
Validation
Choose validation level
Decide whether a rule belongs to the template or the Work Order.
- Use template validation when the rule applies every time the template is used.
- Use Work Order validation when the rule depends on a customer, project, contract or job-specific requirement.
- Avoid duplicating templates only because acceptance criteria differ between jobs.
- Document the reason for stricter job-specific rules where needed.
This keeps templates reusable while still allowing job-specific control.
Open full guide →Advanced validation
Validate validation rules
Use this when several rules may overlap or create conflicting requirements.
Open
Advanced validation
Validate validation rules
Use this when several rules may overlap or create conflicting requirements.
- Start with the template-level rules.
- Then review Work Order-specific rules.
- Check whether a Work Order rule tightens, overrides or conflicts with the template rule.
- Look for impossible combinations, such as one rule requiring a value below 5 and another requiring above 10.
- Check whether warnings and blocking rules are consistent with the intended workflow.
- Resolve conflicts before reports are submitted for review.
Automated conflict analysis can later detect inconsistent or redundant rules. Until then, users should manually check rule hierarchy, overlapping limits and severity.
Two validation levels
Template validation is used for general requirements that apply whenever a template is used.
Work Order-specific validation is used when acceptance criteria depend on the customer, project, work order or contract requirements.
Examples
Template validation: Report Date is required. Result must be selected. A numeric field must be between a general minimum and maximum.
Work Order validation: The same dimensional inspection template is used for several jobs, but the accepted tolerance differs for each Work Order.
Validation severity
A warning tells the user that something should be checked, but it may still be possible to continue.
A blocking validation should prevent submission until the issue is corrected or handled according to the configured workflow.