Skip to main content
Mar 30, 2015 3:35 PM UTC
Question

Re: Simulate Results Definition (.rwd) Files

Patrick,

You've made a valid point, and I couldn't have stated it any better. It appears that the "problem" with the Product Development Team is that they do not work on a daily basis with a product as we do, and they don't appear to see the benefits of having this type of capability, and I don't believe you can convince them otherwise. It sort of hits you in the "gut", especially after paying maintenance for many years.

    1 reply

    Mar 30, 2015 4:53 PM UTC

    I guess one of the problems - and this is just my personal experience from about 22 years in Technical Support - is that with users sometimes it is like with doctors:

    Ask 10 for advice and you might receive 12 opinions!

    It's very hard to please everyone, if you design software. What is a requirement for some, is a no-go for others.

    And UI needs some clearing and restructuring now and then to not become too cluttered.

    But usually when I investigate a functional change for a customer, I try to find the reason behind the change and document it.

    In this case there was no customer case, only an internal SPR from Quality Assurance, who noticed the change during their tests.

    For them it was OK to hear the change was intented and there was no discussion about why the change had happened (at least none recorded).

    I created the article just to provide the little information that we had (it's not a bug, but an intented change). I didn't explore it further.

    So what you can do, is open a case with Technical Support with the goal to figure out, why this change has been implemented and which alternate functionality was supposed to replace it! Document your use case and what the loss of functionality means to you, as a base to discuss alternate techniques.

    As stated before, if a change is done by purpose, you can expect that someone has considered all pros and cons. Sometimes alternate functions are in place, but maybe not always obvious.