Releasing revised items in Upchain
In this lesson, we’ll look at how to release a revised item, and how to leverage important tools when preparing and reviewing the Change request.
Releasing items again
In this video, we explore the process for releasing an item a second time, and explore 3D comparisons, BOM comparisons, release types, and linking Investigation requests to the Change request.
Before you start:
Please note items must have been revised and are currently in Development, ready to be released again.
Key takeaways
- A new Change request (CR) is required to release your revised items. The process of creating one is the same as creating the first CR.Â
- The 3D comparison tool inside a CR is useful for comparing the current design to its previous released version to visually determine what has changed in the model.
- The BOM comparison tool inside a CR is useful for comparing the current BOM to its previous released version to visually see how the BOM has changed.
- Linking Investigation requests to a CR is useful to fully document the reason for the change and where the original request came from.
- The user who can approve the CR and release the items is governed by a workflow.