alexander00pr
IS-IT--Management
I wonder when Table Service 6.4 will be a release version? I had pay over 2 year of aloha upgrade a never done one. My reseller dont want to me to upgrade but alway are billing them?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Aloha 6.4?
- Thread starter alexander00pr
- Start date
- Status
6.4.0 through 6.4.9 and 6.5.1 is available as a pre-release controlled deployment.
If your key is licensed to 6.4 or 6.5 try asking your reseller if they can obtain a pre-release version if you would like to test it. If granted, Radiant will make you sign a form knowing that it is a pre-release version and they want feedback about it.
6.2.19 was release a few weeks ago if you are interested.
---
-Chris
MegabyteCoffee.com
If your key is licensed to 6.4 or 6.5 try asking your reseller if they can obtain a pre-release version if you would like to test it. If granted, Radiant will make you sign a form knowing that it is a pre-release version and they want feedback about it.
6.2.19 was release a few weeks ago if you are interested.
---
-Chris
MegabyteCoffee.com
alohatech2
IS-IT--Management
Yeah, do you guys know why you want 6.4?
Your reseller may be thinking:
1. We have an obligation to keep our clients on the latest version of the Aloha Product if that is the service level they are seeking. There are also penalties for going off of software maintenance and trying to get back on it later. Without software maintenance, clients are not entitled to software upgrades. Software maintenance contracts are greatly under Radiant control and little under reseller control.
2. We don't want to upgrade the software too soon because early releases are ALWAYS "buggy" and the reseller ALWAYS gets blamed for this! Radiant does the best they can to work out all bugs and problems but the honest truth is this is very difficult considering the huge number of variables that occur in the "real world." The reseller client often suffers for this.
3. It is much safer to do our won testing in our lab, or to let other clients or other companies go through the hassles of newer releases so that our clients don't have to. Because of this, it takes time to feel confident enough to release the software even after Radiant has deployed it to the masses.
So as a client, here is what you must ask yourself:
Are the benefits of the latest version of Aloha worth going through the hassle of finding bugs and working with my reseller to get them fixed? This involves time and commitment to providing as much testing and information as possible.
Do I have a really good relationship with my reseller such that this process will be as smooth as possible?
Is my reseller responsive to these issues such that the greatest effort is made to fix or work around them asap??
Will I get charged by my reseller for this service in these situations?
Can I afford to have my system get refreshed or rebooted a lot while testing is taking place?
Can my staff handle the constant changes and feedback necessary to facilitate this research?
Does my company or reseller have enough Aloha Terminals to be heard?
- - As it has been explained to me, the more actual terminals you have, the louder your voice is to Radiant. When complaints come through, they weigh in the number of terminals (not number of customers) that are involved in the problem. So one company with 100 sites of 10 terminals each = 1000 terminals. One company of 500 sites with 1 terminal each = 500 terminals. The one with 1000 terminals may get more attention.
Remember - new software can be all roses. Everything may go just fine for you on the latest version.
However, if something goes wrong, you have to be prepared to face the above questions and be ready to help get it resolved as soon as possible.
Hope this helps.
Your reseller may be thinking:
1. We have an obligation to keep our clients on the latest version of the Aloha Product if that is the service level they are seeking. There are also penalties for going off of software maintenance and trying to get back on it later. Without software maintenance, clients are not entitled to software upgrades. Software maintenance contracts are greatly under Radiant control and little under reseller control.
2. We don't want to upgrade the software too soon because early releases are ALWAYS "buggy" and the reseller ALWAYS gets blamed for this! Radiant does the best they can to work out all bugs and problems but the honest truth is this is very difficult considering the huge number of variables that occur in the "real world." The reseller client often suffers for this.
3. It is much safer to do our won testing in our lab, or to let other clients or other companies go through the hassles of newer releases so that our clients don't have to. Because of this, it takes time to feel confident enough to release the software even after Radiant has deployed it to the masses.
So as a client, here is what you must ask yourself:
Are the benefits of the latest version of Aloha worth going through the hassle of finding bugs and working with my reseller to get them fixed? This involves time and commitment to providing as much testing and information as possible.
Do I have a really good relationship with my reseller such that this process will be as smooth as possible?
Is my reseller responsive to these issues such that the greatest effort is made to fix or work around them asap??
Will I get charged by my reseller for this service in these situations?
Can I afford to have my system get refreshed or rebooted a lot while testing is taking place?
Can my staff handle the constant changes and feedback necessary to facilitate this research?
Does my company or reseller have enough Aloha Terminals to be heard?
- - As it has been explained to me, the more actual terminals you have, the louder your voice is to Radiant. When complaints come through, they weigh in the number of terminals (not number of customers) that are involved in the problem. So one company with 100 sites of 10 terminals each = 1000 terminals. One company of 500 sites with 1 terminal each = 500 terminals. The one with 1000 terminals may get more attention.
Remember - new software can be all roses. Everything may go just fine for you on the latest version.
However, if something goes wrong, you have to be prepared to face the above questions and be ready to help get it resolved as soon as possible.
Hope this helps.
- Thread starter
- #5
alexander00pr
IS-IT--Management
Thanks for the reply. I have a test enviroment in the training facilites for testing out the software. I know that this can never acomplish a real world scenario.
As for my reseller theyre almost out of business.
Im looking in Aloha 6.4 this few things:
1. Tip calculation on check (Like the lonetree tip program that intercept the printing on com port. But since Ts
6.2 require an Aloha Connect add on isnt an opt ion.) As i paid soft upgrade why do I have to paid for the Tip Program $400 and $300 per terminal for Aloha Connect if the new version has that capabilites?
2. Im looking also for the improvement in audit report that was gonna get an update (audit by check number instead of employee #)
3. Disable delete payment by job code.
Does the #2 has been implemented in 6.4?
As for my reseller theyre almost out of business.
Im looking in Aloha 6.4 this few things:
1. Tip calculation on check (Like the lonetree tip program that intercept the printing on com port. But since Ts
6.2 require an Aloha Connect add on isnt an opt ion.) As i paid soft upgrade why do I have to paid for the Tip Program $400 and $300 per terminal for Aloha Connect if the new version has that capabilites?
2. Im looking also for the improvement in audit report that was gonna get an update (audit by check number instead of employee #)
3. Disable delete payment by job code.
Does the #2 has been implemented in 6.4?
- Status
Similar threads
- Question
