Skip to main content
Mar 30, 2015 11:48 AM UTC
Question

Re: Simulate Results Definition (.rwd) Files

Gunter,

The functionality was removed intentionally without submitting a Product Idea, therefore, the functionality can be restored intentionally without submitting a Product Idea.

Submitting a Product Idea will not restore this, in my opinion, as I have already submitted 33 Product Ideas since May 16, 2012, and none of them have been considered by the Product Development Team.

    3 replies

    Mar 30, 2015 2:27 PM UTC

    Hi Steven,

    In theory every change can happen - intentionally or unintentionally.

    However, it is very unlikely the functionality will be reverted without multiple customers requesting this change (this is what Product Ideas with voting is about), because the change was intentional (that it was intentional has been confirmed by the R&D investigation triggered by SPR 2127092).

    In return an unintentional software regression does not need a Product Idea, it would be fixed as a correction ("software not working as it is supposed to") for the SPR.

    I can understand that your motivation to submit more Product Ideas is low due to past experience, but keep in mind that product enhancements need their time (the intentional removal surely had been planned a long time ahead as well). Usually a change in functionalitty needs to be designed, before R&D starts programming a new release. With Creo 3.0 being established, programming of Creo 4.0 has already started, so usually when an enhancement is considered now, it will be for Creo 5.0 earliest.

    When I look into your Product Ideas, it seems that only one of the Simulate related ideas got a top voting. Otherwise mostly Creo Parametric related ideas had relevant responses (although this is somewhat relative, since Parametric ideas usually have higher votes).

    The one idea I talk about, is the one to remove the limit for Memory Allocation (37 votes). I will notify Product Management of this idea.

    The "idea behind Product Idea" is that Product Management browses through the ideas with some regularity and picks those that have high votes or are otherwise interesting for consideration. Ideally there should be some comment about whether and when the idea will be implemented or - otherwise - why not. However, naturally there are a lot of things that can happen between design and release, so usually there is some understandabe reluctance in publishing plans before they are successfully completed.

    Regards,

    Gunter


    Mar 30, 2015 2:37 PM UTC

    So what you are basically saying is that any functionality can disappear without warning at any time, and that when this happens all one can do is submit a product idea, hope that a lot of people vote for it, and even when that happens you need to wait a few years to get the old functionality back?

    That does not sound like a very customer-friendly way of working...

    Mar 30, 2015 3:04 PM UTC

    I said in theory it can happen (similar to a jack pot win or getting struck by lightning - and yes, I'd prefer the former if I had a choice).

    And if such a change happens by accident, we fix it as soon as possible.

    But if the change has been intentionally planned, there usually has been some good reason for the change and hence there should be even better reasons to switch back. Product Ideas are the means to provide feedback on the requirements and reasons (comment like "great idea" or "I like it" are nice, but not very helpful).