Express ECOs - Renumber and Supersede
When using the express ECO there are 2 actions (Renumber and Supersede) that are either; not working correctly or the documentation is unclear. For renumber and supersede there are no updates to the BOM as the documentation implies. My understanding from the PE documentation is: Renumber replaces an existing Part with its copy. The existing Part is copied as a new Part, which is assigned a new Part number, and released. The copied Part becomes the replacement Part in the BOM in which it is defined and supersedes the old Part. I see that on promoting express ECO to Draft Changes that a new part is created and the old part is marked as superseded. However, the Part is not replaced in the BOM. although it says "Superseded" there is no obvious way to view this on the BOM or what part superseded it. Supersede globally replaces one released Part with another released Part. The original Part is superseded. I see that on promoting express ECO to Draft Changes that the old part is marked as superseded. However, the Part is not replaced in the BOM. On the assembly part I see that it says "Superseded" there is no obvious way to view the superseded part except by navigating through ECO. The pictures show Assembly 1 contains Part 1 that I renumbered and Part 2 that is superseded. (For comparison: When I do a revise action on a part in the context of assembly the new revision of the part floats to the assembly. This behaves correctly and the traceability is clear in redline mode). Can you confirm the steps that the user should take to use renumber and supersede correctly, Thanks
Product engineering - moving related model to another product
Hello, i have come across a need to move one of our used models to a different product (Change of business logic) the model i am trying to use is being used by other document/parts/ etc. by trying to delete the relationship it says it is being used by dok nr-xxxx. i have tried to copy the model to a different product using the clipboard Manager and i ended up having same model in two product, but now i get same error in both cases. Is there any way i can move the related model to another product?
