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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha POS Takeout and Delivery driver cannot self dispatch 3

Status
Not open for further replies.

davetmt

IS-IT--Management
Nov 17, 2008
5
US
I have 16 stores running 6.7.32 table service and 1.2.72.212 Aloha Takeout.

Two stores are having this problem where drivers that were in the system prior to the upgrade from 6.25 can self dispatch.

Drivers that were added after the upgrade cannot. The button does not appear for them to dispatch. We have verified that the job codes are identical to a driver that works correctly.

I have called our dealer and to say we are disappointment with them would be overly polite. They do not have a clue on how to proceed.

Any help would be greatly appreciated.

Thanks

 
Thanks for the docs Coorsman. I have read these already and are very helpful in most regards except this one.

Each driver has the same job code and access level and one driver can self-dispatch and the other cannot. How can this be?

I have ran DBCONFIG and have rebuilt the indexes. I have backed up the takeout database. Wiped it out and restored the backed up database. Not sure what else to try.

Is there a way to determine what might be happening in the logs.
 
Here is the latest bug review for updates on ATO:

V1.2.73
· RFC #88341 - ATO Driver remains in Drivers Active list in ATO after Clock-out

· RSIM #666960: Resolved issue where ATO could crash during the process of releasing future orders

· RSIM #670018: Resolved issue where ATO could not be navigated to at start of day

· WIT #65642: Resolved issue with drivers not displaying in Dispatch of Drivers screen when clocked in.

· WIT #64037: Added ability to override order mode charge in external order interface.

V1.2.72

· TFS #41292: When a user reopens a check that was in the ATO queue, the check still appears as closed in the queue.

· RSIM #663991: Adjusted the pending future order logic slightly to eliminate a very small window where a future order might fail to release if its release time is the current time or in the past as soon as the order is created.

· RSIM #664002: Fixed an issue that prevented future orders from releasing in fault-tolerant mode.

V1.2.71

· RSIM #663063: Fixed an issue where the "items activated" event from AK could cause ATO to display an incorrect empty order on the ATO terminal that created the order.

V1.2.70

· RSIM #660995: Fixed an issue that caused future order deposits to get closed prematurely during the ATO EOD process.

· RSIM #639029: Fixed an issue that caused the order sequence number to not get reset at EOD if an ATO terminal was offline at the time an ATO EOD was performed.

· RSIM #661981: Changed ATO kitchen integration logic to use table ids instead of check ids when communicating with Aloha Kitchen. This should eliminate any order status inconsistencies between ATO and AK when the table id does not match the check id for a given order in the system. This can happen when split checks are entered into the Aloha POS.

· RSIM #661899: Fixed issue that prevented orders from being synchronized properly on ATO client restarts when offline support is disabled.

· RSIM #662001: Eliminated a race condition in the AK integration logic that was causing empty orders to appear on some ATO clients.

· RSIM #659349: Items on repeated orders are now checked against the order capacity restrictions for specified time segment. Also, improved the capacity checking when the user selects "Back to Aloha" from the order confirmation screen.

· RSIM #662739: Fixed an issue where a future order's ScheduledFulfillmentTime value was being incorrectly set to 1/1/01 12:00AM when the user pressed "Back To Aloha" from the order confirmation screen. This was causing the future order service to expire the future order.



Cheers,
Coorsman

 
Awesome. Our dealer should have caught this one. I will have them push the update over to the store in question and let you know.

Is there a place a non dealer can access info like this.

Thanks very much!!!
 
Coorsman,

I can verify that 1.2.73.217 ATOD has fixed the problem.

Thanks very much for the help!!![thumbsup2]
 
Coorsman, could you please re-upload the two docs that you posted? They are no longer active on your dropbox. Thanks in advance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top