cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X

Design Exploration to manage accidentally modified objects

Design Exploration to manage accidentally modified objects

Within Design Exploration (DEX), it is very easy to accidentally modify a part that should not be modified. Whether running a mapkey that makes a change, or some reference control, etc. Once it is flagged as modified, the model is then entered into the 'DEX Session'. Once there, we have found a slew of issues, mostly connected to sessions connected to windchill. From rename issues, windchill references, to full libraries of family tables getting modified and added. Then, when our engineers need to use this DEX, there are save issues with a lot of conflicts. Trying to clean up the workspace just to get it to save, almost makes the ease of DEX not worth it. Below are some ideas that will drastically help with our frustrations:

  • The model tree should show which models are modified in the DEX session, either by a column or color coding. We shouldn't have to browse the DEX session or run the 'View Changes', just to see whether it is modified.
  • DEX should give the user the ability to delete and remove the model from the DEX session. In our case, even if we delete the modified part from the design, it is still in session and causing us issues for a family table.
  • DEX should give the user the ability to reload the original model back into the DEX and remove all changes, in case they were accidental.

 

Thanks!