Skip to main content
Sep 29, 2023 5:16 PM UTC
Acknowledged

Updating objects in your workspace shouldn't flag an object as modified in Design Exploration

Related products:Creo Parametric

Please include detailed documentation such as screenshots, images or video.

1. What product and version are you running?
Creo Parametric 8.0.8.0


2. What is the problem?
Reference: 

Case - 16406179

SPR - 13945104

Article - 373237

 

If we are working in design exploration, and update objects in our workspace that are in the current checkpoint, a new checkpoint is created which flags those items as modified. If you are not in session, updates to the workspace do not cause this problem. However, once the problem occurs, there is no way to undo it. This was noticed too late by our users and now when they try to push a checkpoint out, it includes hundreds of instances from family tables that are also getting pushed out.... because they were in the DEX modified session. Cleaning up these issues are very difficult. Please enhance this capability, as we can't use DEX if it has such large gaps in workflow.

3. Are you using a workaround? If yes, please describe it.
No. We have stopped using DEX. In theory it is a great tool. In practice, it needs much improvement, specifically regarding Windchill.

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.
Idea: Any time an object is updated in the workspace, while DEX is opened, it loads the object and does NOT flag it as modified. Maybe even a prompt asking the user whether they want it modified is sufficient.

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
~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 hardware parts (screws...) getting pushed out from DEX that shouldn't be.

1 reply

Oct 2, 2023 5:48 AM UTC
Status changed to: Acknowledged

Hi @jwagh!

Thank you for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.