ADM Rel - 200601 - [7-14-20]
Updated
Print

Release Notes rel-190601-Kiosk

The following new features and fixes were deployed starting on 7/14/20. 

 

V5 

What’s new

  • To provide operators with more control over devices when they are offline, we have greatly expanded the functionality around credit card usage in offline mode. Both the V5 and 365Dining kiosks now allow for operators to set how long a kiosk will accept credit cards for when the device is offline. On ADM on the Location Summary and Device Summary pages, there is a field for CC Local Cutoff (Hours) that allows for users to set the amount of time that the kiosk will continue to accept credit transactions. If a value of 0 is entered that indicates that the device will stop accepting CC trans immediately once the device goes offline. This functionality is intended to provide more customization to operators, while limiting the potential liability risk of offline transactions.
  • As we continue to roll out PC swaps to allow for transitions from Legacy to V5 kiosks, we are working to make that process as self-sufficient and as easy as possible for operators. We have gathered a lot of feedback on the current process and have implemented several fixes and updates, such as showing all applicable locations to users on the setup and running the kiosk through a set of additional network checks. All these improvements are aimed at providing an easy to use provisioner to successfully setup a V5 kiosk.

 

Bug Fixes

  • When performing a cashout event on a V5 kiosk with a bill acceptor, a receipt will print with auxiliary information, so the operator knows where and when the cashout was performed and how much cash was collected. We have fixed a bug on this cashout receipt that was causing the Serial Number field to be blank, so operators will now know which specific kiosk the cashout took place on.

  • We have fixed a bug on V5 that was causing the tender payment method to be missing from the sales record when a user added cash during an Insufficient Funds flow. With this fix, when users have insufficient funds on their account and ultimately add funds to complete the transaction, we are now successfully storing and reporting on the payment method used.