Family table design strategy
Hello everyone,
I am Victor from Spain.
At our company we are thinking to start using family tables to manage our family assemblies. However, we are still reluctant in how Creo manage future instance modifications. As we are using a PLM to manage our documentation, we are worried about the fact that instance can be modified without not even opening the generic.
For example, having a generic assembly (ASM0001)saved with 2 different instances (ASM0001_INST1 and ASM0001_INST1) on the BBDD . It is possible that in the future a colleague could modify and save the ASM0001_INST1 not modifying the generic and making a discrepancy on our BBD.
With that exposed, our question is: Does exist a way to block or prevent instance modifications out of the generic?
Thanks for your support!

