Update protection until end of version 
Author: John S.
Visited 1775,
Followers 2,
Shared 0
I suggest that the Update Protection (UP)will be defined like this :
UP is valid until the date defined but update will be allowed for the CURRENT paid version until a new version comes.
This will do that users will not end up with some software that is filled with bugs AND it will allow users to download and install the version they have already paid for, in case of computer problems/changes.
Posted on the
I agree 100%!
There were already several suggestions regarding UP, with not even one response from Incomedia... Let's hope they will listen this time and consider the change!
definatly +1 or two, counting Tom in.
+ 1
Didn't I say "NO RESPONSE FROM INCOMEDIA"?
Again - ignored, not even one comment, pretending they haven't seen it... What's new?
Pathetic!
Good day everyone
As per every Idea topic, I can confirm that it has been received correctly, and will be forwarded and discussed by the developers.
Again, as per every Idea topic, it is not possible to know when it will viewed and discussed, but rest assured that they are not forgotten.
At the moment, there is no news regarding this matter, but should there be, it will surely be made public to all the users
Thank you for your feedback and interest in the software, as always
Stefano
Author
Hello Stefano
Thank you for showing us that this kind of reaction is pure copy/paste.
Nothing in my idea should involve a developer.
I had hoped that we customers were treated more seriously by INCOMEDIA.
It would be more honest to just give all idea posts an automatic response : This post has been archived by INCOMEDIA.
Hi John.
I'm sorry if this is the general idea that my message conveyed.
As you may imagine, the functionality of the Update Protection is not merely a matter of adding time to an Update Protection period. it involves logics which need to be discussed, worked on and developed in order to provide a fully functional system.
In this case as well, should this Idea be among those which get implemented, it would require a rework of the general update system, which mean that yes, the developers are involved in the process.
Every Idea is received, discussed and evaluated. Unfortunately, not all of them can be implement, or perhaps not immediately, but none of those is discarded or remains unread.
Should there be any news on this which furthers the matter, I will be sure to notify you here
Thank you
Stefano
Author
Hello Stefano
I would not in a dream, have thought that the developers also was the people that decided how the pricing, and the licence periods was set.
Normal this is something that is for a CEO or a sales department to decide. Then the rest in the organisation has to do what is needed.
Imagine : Someone at Google comes up with an idea - In future, what about let users pay for the API to our map. We could let a click-amount free per month.
Do you think it will be up to the developers to change Googles policy?
Or - do you think they will send it up in the organisation where someone will decide if/that it is a good idea - and then expect that the technical staff will do their job?
John,
Stefano means the software that controls the licences, if you want to change this it also needs to be handeld differently in the portals of all users, in the registration periods and software versions start and end date's, billing, automatic mailing...
Things like that. to sum up; The registration software.
The decision is offcource up to CEO and managing staff.
Author
Hello Andre
Yes - I know that changes involves coding. But normally the process would be that the CEO/managing staff makes the desicion, and then give it to the coders. And as I see it, then it should not be a huge thing. It is still a question of a date - but there will be more parameters involved.
Stefano's post makes only sense to me, if it is decided that changes should be made, and that the coders now are looking at, how much coding is needed.