Skip to main content
Jan 20, 2021 5:25 PM UTC
Archived

Design Exploration - Hide Checkpoint Number, or have it customizable or able to rebuild from 1.

Related products:Creo Parametric

Hi,

We are using Design Exploration. We are finding that there are some scenarios when checkpoints are created inadvertently, which causes the number to go higher. We then have to delete checkpoints and end up having checkpoints with numbers like 5, 13, 22. The issue is that we are building a top-down approach for engineers to select a design concept and push that out to Creo and then configure it using a skeleton with parameters. We would like the numbers to be able to be:

  1. Hidden
  2. Customizable
  3. Able to be rebuilt where the first checkpoint starts with 1 again.

 

Thanks!

5 replies

Community Manager
Feb 20, 2025 11:10 AM UTC
Status changed to: Clarification Needed

Thank you @jwagh for publishing your idea. However, we need more information as specified in the questions below. You may simply add a comment to your idea. The more details and context you give to document your idea, the better. Think about ways to educate and convince other Community members to support your idea and present your case to the product management team for consideration.

Please let us know within the next three weeks.

1. What version of the software are you running?.
2. What is the problem?
3. Are you using a workaround? If yes, please describe it.
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.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.

Please see examples of well-documented ideas:

https://community.ptc.com/t5/Creo-Parametric-Ideas/Make-Shrinkwrap-quality-more-scalable-to-data-size-complexity/idi-p/810192 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Option-to-Import-STEP-file-as-Inseparable-Assembly-by-Default/idi-p/812924 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Eztol-Rename-action-not-synchronous-in-Eztol/idi-p/828000 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Always-enable-ability-to-Add-View-Label-in-a-drawing/idi-p/837630 

Feature parameters can be input and changed togeth... - PTC Community 

Feb 25, 2025 2:24 PM UTC

Hello @jwagh ,
I agree that some operations can lead to weird numbering patterns in the DEX structures. While merge, You can loose some checkpoints with their numbers, too.

To hide unwanted numbers, it could be an idea to enhance RENAME funtionality to delete the number in the beginning of the expression.

 

Your 3rd point: Agree: it could be nice solution to select a node in a branch and press a new button RENUMBER / REBUILD). to create numbers beginning from 1. Of course, other branches and substructures need a proper solution for that case as well.

 

Perhaps PTC could provide a new function for each branch, which stamps a "solution1" with an own parameter. "Solution2" and so on. This would remain more constant than the numbering in the structure. But imho this is quite close to family table fonctionality.

 

Best regards!

jwaghAuthor
Mar 5, 2025 5:32 PM UTC

1. What version of the software are you running?

Creo 10
2. What is the problem?

See first post
3. Are you using a workaround? If yes, please describe it.

No
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.

Creating a start-up product design exploration session that can be used by the organization. We would like it to be simple, without it being confusing. Having 'random' number checkpoints can lead to confusion from the end user.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

About 50 users. They currently don't want to use Design Exploration, due to the fact that they feel it isn't 'polished' to the point of it being useful for them. There needs to be some additional work to take it from 80% to 100%

Community Manager
Mar 6, 2025 9:27 AM UTC
Status changed to: Acknowledged

Thank you @jwagh 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.

olivierlp
Community Manager
Apr 1, 2025 4:00 PM UTC
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.

Olivier