Message 1 of 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
We have a released part at Revision 1, which is still valid and in use in one product. Later, an engineer bumped the revision to 2 to start a change. After working on it, we realized the change is larger than expected and actually requires a new part number instead of just a revision.
How can we best handle this in Vault?
Revision 1 must remain released and usable in other products.
Revision 2 is essentially a false start and should not be considered part of the part’s revision history.
We need to continue with a new part number for the new design.
Is there a recommended way in Vault to “cancel” a revision without marking the original released revision as obsolete?
Solved! Go to Solution.