DEX - Branching Improvements
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?
Branching features are not intuitive. What I am proposing:
- You should be able to create a branch off of the last checkpoint. You shouldn't need to have a subsequent checkpoint afterwards to branch off of it. Let's say I know that I want to have 3 concepts, each with 3 different sub iterations (1a,1b,1c and 2a,2b,2c and 3a,3b,3c). Today, Creo DEX requires me to make a 4, before I can make 3a,3b,3c. That doesn't make sense - it requires users to create a dummy concept below to get around this... Maybe you could right-click the checkpoint and instead of saying "create new checkpoint" it could be "create new checkpoint or create new branch" and that way it knows if you want to continue at same level or create a lower level option (branch)
- Going off my example above, what if 1a, 2a and 3a all require the same features? Today, I would have to repeat the steps and do all that work 3 times and save 3 checkpoints. It would be cool if I could create a branch off 1 and tell DEX to go apply the same features on subbranches of other checkpoints (i.e. I make 1a and tell it to go make a 2a and 3a using the same steps).
3. Are you using a workaround? If yes, please describe it.
Both ideas I have extremely tedious workarounds which make DEX less attractive for our organization to use. We do a ton of concept design though, so improving DEX in these ways would mkae it much more likely for a wider group in our org to adopt DEX into their workflows.
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.
Early-stage concept development as we are part of a large product development team at a consumer electronics company
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Workarounds are slow and tedious and drive people to not use DEX (or at least be afraid of using it). These are 2 simple changes which would have immense benefits to the user and would make DEX a more compelling tool in the toolkit of a product development engineer.
