Approval workflows
Standard work releases itself. Everything else reaches the right person.
Cadxor routes configurations by rule — engineering for non-standard lengths, purchasing for special materials, sales for large quotes, the customer for drawing sign-off — and records every decision against the exact version that was approved.
Routing examples
Rules decide who needs to look.
| Condition | Route | Step |
|---|---|---|
| Standard configuration | Released automatically after generation | — |
| Length over the standard maximum | Engineering | 1 |
| Non-standard material | Engineering + Purchasing (parallel) | 1 |
| Long assembly needing handling review | Manufacturing | 1 |
| Quote over $50,000 | Sales manager | 2 |
| Customer requires drawing approval | Customer, via secure single-use link | After generation |
Thresholds shown are examples from the demo workspace. Each manufacturer sets its own.
Supported patterns
From one signature to a release board.
- No approval required
- Engineering, sales, customer, quality, manufacturing and purchasing approvals
- Multi-step sequences and parallel approvals within a step
- Threshold-based approvals (price, dimensions, quantity)
- Approvals triggered by non-standard components or customer requirements
- Rejection requires a comment and returns the configuration to draft
What is recorded
- Approver
- User, or named customer via signed link
- Decision
- Approved / rejected
- Timestamp
- UTC
- Comment
- Required on rejection
- Version
- Configuration number and revision
- Config hash
- SHA-256 of every engineering-relevant value and component revision
- History
- All previous decisions, including invalidated ones
Change after approval? If anything that affects engineering output changes, the hash changes and open or completed approvals for the old version are invalidated automatically.
See Cadxor with your own product family.
Bring one configurable product line. We will map its components and rules and show you the generated package.