Examples
Overview · Rule Patterns · Profile Examples · Name Examples · Common Examples
Common Rule Examples
- Overview
- Run checks on all rows using a wildcard subject
- PhaseOthers should be empty
- UserPhase must match PhaseNumber
- On Hold warning field should normally be empty
- Material determines valid Finish
- AssemblyPrefix must start with PhaseNumber
PhaseOthers should be empty
Problem
The PHASE.OTHERS property indicates that associated objects have conflicting phase values.
This can occur when child objects, father components, or assembly main parts have conflicting phases.
Strategy
Check whether the PHASE.OTHERS cell contains a value.
If the cell is not empty, flag the row and guide the user to correct the phase assignments.
Rule Structure
Subject:
PHASE.OTHERS
Match:
Wildcard *
Target:
PHASE.OTHERS
Conditions: (None)
Minimal Tree
Subject: PHASE.OTHERS
Match: *
Target: PHASE.OTHERS [Direct: CellValueEmpty]
Example Results
| PHASE.OTHERS | Result |
|---|---|
| (empty) | Okay |
| PHASE2^ | Error |
Explanation
If PHASE.OTHERS contains a value, it means associated objects have different phases.
This rule ensures that the model remains consistent by detecting those conflicts.
Notes
The audit message can provide guidance on how to identify the conflicting objects.