DEX - Model History
Please include detailed documentation such as screenshots, images or video.
1. What product and version are you running?
Creo 9.0.7.0 - Using DEX (Design Exploration Xtension)
2. What is the problem?
A limitation of DEX is that it applies to the session, not the parts / assembly. I see that as an advantage for most things (DEX is designed as an ad-hoc, trial-and-error environment to explore design options as you guys describe it - and having everthing save within the .tmu session is great at doing that). But a downside is that you may commit to a design option and then work away on your parts and assemblies for weeks after that, only to realize that one of your other concepts from DEX is now of interest. I can open an old .tmu no problem, but it is a snapshot of what the model looked like back then (hasn't accounted for the weeks of work I've done post-DEX. If there was a way to open a newer version of a model and an old DEX session and tell it to try and reapply those features to your new model, that would be very cool. Obviously references may break, but something similar to the re-referencing tools when copying features between different .prt files would be a great solution to this I'd imagine.
3. Are you using a workaround? If yes, please describe it.
Nope - not possible today.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
We do a lot of early-stage cncept development work for consumer electronics products.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Tedious workarounds, making copies of files, suppressing groups, and heavy / slow model trees as a result of that, vs. being able to extract more value out of DEX to avoid these things.
