Reusable workflow templates
Configure request forms, conditional fields and ordered approval stages with quorum and mandatory sign-offs. Preview JSON or YAML policies before saving; existing requests retain the version selected for their review.
Read the workflow docs →Custom change-validation conditions
Combine typed request answers, changed-record counts and supported proposed or linked record values in bounded expressions. Choose blocking conditions or warnings and show reviewers the guidance needed to repair a failed check.
Read the workflow docs →Requirement impact and saved review reports
Inspect linked requirements and current verification evidence for individual changes or every target in a bulk field request. Optionally include parent assemblies from current live BOM usages. Save a report for the review round and read the retained evidence after approval or rejection.
Read the workflow docs →Retained validation history
Inspect explicit validation executions and constrained submission attempts, and retain reviewed passing, warning or failed results. Download original evidence without replacing it when the workflow or proposal changes.
Read the workflow docs →Versioned lifecycle transitions
Define permitted directed moves between native lifecycle states and inspect the policy behind a proposed change. Submitted reviews retain the original transition decision; changed evidence can require rework.
Read the workflow docs →Change requests
Prepare edits in a working copy and send them to the team for review. Keep the proposed changes, reviewers and decision history together. The live product record changes only after approval.
Read the workflow docs →Immutable revisions
Applied engineering changes preserve labeled, read-only revision snapshots with their decision evidence. Browse and compare revisions to understand how the product changed.
Read the workflow docs →Named approver rosters
Set default approvers per type, with flat rosters or ordered review stages. Require all signers or a stage quorum, and retain signatures from approvers or their authorized delegates. The completed approval applies the change atomically.
Minor and major classes
Route changes to the approvers required for their class. Use different approval groups for minor corrections and major redesigns.
Comments and request changes
An approver can send a request back with a reason instead of rejecting it outright. The discussion lives on the change request, next to the diff it is about.
My work and team reviews
Find assigned reviews in My work tasks and pending or returned changes in Team reviews across projects you can access. Filter by project or agent activity, then open the full review to inspect the diff and record a decision.
Propose a reversion
Open a change request pre-filled from an earlier revision. Going back is a governed change with the same approvals as going forward, not an untracked overwrite.
Change lock
Freeze a record’s engineering definition with an administrator’s recorded reason. Definition changes, including BOM edits on frozen drafts, require an authorized unfreeze with its own reason.
Obsolescence and supersession
Retire a part, point it at its replacement, and work the still-used list from a dedicated page that hands off to the swap tool.
Audit trail
Every record carries its own history: who changed what, when, and under which change request. Sub-resources and configuration changes are audited too, not only the record body.