Design Exploration to remove modified objects in checkpoint after object deletion from Creo Session!
1. Describe the Problem
Reference:
Case - 17494178
SPR - 15684520
Article - 426936
There are many situations, while working in Design Exploration, where items in a checkpoint are flagged as 'modified' accidentally and added to the Design Exploration Session. When working with Windchill and/or Family Tables, this could end up causing a lot of future problem managing that checkpoint and pushing out the design to a regular Windchill connected session. Logically, it would make sense, that if an object is deleted from a checkpoint, that it would also be removed from the Design Exploration Session. Then, we could add it back into the checkpoint, unmodified, and continue working in the checkpoint. However, that is not what happens. DEX still tracks the changes to these models, even if they are no longer in the Creo session. There are now no workarounds to clean up a checkpoint that has modification issues besides rebuilding the checkpoint from scratch. If the whole point of Design Exploration is to make it easier on a design to create alternative design concepts, this is one big roadblock preventing it.
2. Are you using a workaround?
No. We have stopped using DEX. In theory it is a great tool. In practice, it needs much improvement, specifically regarding Windchill and undoing Design Exploration Session modifications from a Checkpoint..
3. What is the use case for your organization?
A user would make an accidental change to a released Windchill object. Ideally, they would have a button that reloads the unchanged object from the disk or Windchill. But as a MINIMUM, if the object is deleted from the Creo Session, DEX should stop tracking the changes and have it removed from the DEX session. Then, it can be added back into the assembly.
4. What impact does this problem currently have on your organization?
~50 users. HUNDREDS of hours. Maybe thousands. We were trying to use DEX as a way to jump-start designs, but we can't jump start designs if workspaces can't be managed with thousands of released hardware parts (screws...) in family tables getting pushed out from DEX that shouldn't be happening. This would also cause mismatch in generics, instances, renames, etc. from what is in Windchill. No user wants to touch these DEX files because of the issues they cause with managing the data.
