Overview
The following release notes contains updated versions of the following files:
- Admin Console
- POS
- Kiosk
- KDS
If you have questions regarding the updates described in this document, please contact Heartland Restaurant’s Support Department by email (hrpossupport@heartland.us ) or phone (1-833-844-HPOS).
Updates
The following release notes detail the updates we have included in this release.
HR-7454 Sizes No Longer Disassociated from Menu Items
In previous versions, if you ordered a menu item with different size options, the POS may not have displayed all size options. In such cases, the Admin Console disassociated certain sizes from the menu items they were applied to, for no obvious reason. (These changes were not recorded in the audit trails for menu items or sizes.) This problem only occurred at locations that imported menu items from an Excel spreadsheet. When importing records, if a size’s name included any “blank” characters at the end of the name, the program may have failed to recognize those names in the location’s files, and thus failed to update the records properly. We have corrected this, and the Admin Console now updates menu item and size records properly without disassociating sizes from menu items.
HR-25689 Pricing Rules Enforced Through Entire Time Ranges
In previous versions, the POS may have failed to enforce pricing rules during their entire configured time ranges. For instance, if you set the POS to apply a pricing rule during a specific date, the POS may have applied the rule during the first part of the day, but then stopped applying the rule later in the day. In these cases, the POS miscalculated the location’s end-of-day time, thereby suspending the pricing rule prematurely. (Specifically, the POS may have miscalculated the end-of-day time if a POS device on the network was set to the wrong time zone.) We have corrected this, and the POS now applies pricing rules appropriately during their configured time ranges.
HR-28121 Mock Report Data for All Necessary Dates
In previous versions, if your location uses mock report data, the Admin Console may have failed to generate mock data for all necessary dates. In the Admin Console’s Main Menu, click Location Setup, then click Settings. In the Location Settings screen, on the Location Info tab, if you select the Use Mock Report Data check box, the program will use mock data when generating reports. However, in previous versions, the program may have only generated mock data for dates up to November 7th, but no later. We have corrected this, and now when you enable the Use Mock Report Data feature, the Admin Console will generate mock data properly for all necessary dates.
HR-30125 KDS Displays Tickets Properly After Applying Breakup Quantities
In previous versions, if you used the Breakup Quantities function in the POS Ticket screen to separate a group of items, the POS may not have displayed the separated items properly in the KDS. For instance, in the POS, you may have added an order of mozzarella sticks to a ticket and then changed its quantity to “3”. If you then sent the order to the kitchen, the KDS displayed the ticket and its mozzarella sticks properly.
Later, if you accessed the ticket, selected the mozzarella sticks, then tapped Breakup Quantities, the POS would “break up” the order by listing it as three separate items, rather than a single item with a quantity of “3”. However, the POS may have not have displayed the items as separated in the KDS display. In other words, after using the Breakup Quantities function, the POS may not have updated the ticket immediately in the KDS. We have corrected this, and now when you use the Breakup Quantities feature in the POS, it updates the ticket’s status and displays the separated items properly and immediately in the KDS.
HR-31433 KDS Displays Tickets Properly After Removing Timed Hold
In previous versions, if your location uses future orders, you may have encountered a problem. For instance, if you placed a timed hold on a ticket, the KDS displayed the ticket properly with a timer counting down remaining hold time. However, if you then removed the hold from the ticket, the KDS may have continued to display the ticket with the hold timer. In such cases, the POS did not update the status of the held item properly in the KDS display. We have corrected this, and now when you remove a timed hold from a ticket, the KDS displays the ticket’s new status properly and immediately.
HR-32495 No Repeated “WEB” Ticket Numbers from Online Ordering
In previous versions, if your location uses online ordering, it may have received multiple online orders with the same prefixed ticket number, such as “WEB1”. In some cases, the prefix was not defined in the location’s settings. In certain circumstances, if a customer sent an online order while multitasking (running other apps in the background on their device), the Online Ordering website may have been unable to reset the ticket number properly, resulting in a ticket number being “reused” for later tickets. We have corrected this, and the online booking screen now resets ticket numbers properly, even if customers are multitasking while placing orders.
HR-32579 No More Duplicated Cash Drawer Checkouts
In previous versions, if your location uses cash drawers, the POS may have saved a cash drawer checkout improperly (before it was completed), resulting in seemingly duplicated checkouts. In the Cash Drawer Checkout screen, when you tap Checkout, the POS displays the How much cash in drawer? keypad panel. In this panel, if you enter the cash amount and tap Save, the POS records the checkout as completed. If you tap Count Later, the POS does not record the checkout as completed. Normally, there is no other method to close this panel.
However, in previous versions, if you tapped the inactive (grey) area around the keypad, the POS may have closed the keypad and saved the checkout as completed with no total. If the cashier then tapped Checkout again to resume the checkout, the POS recorded that as a second checkout completed on the same device. We have corrected this, and the POS no longer closes the How much cash in drawer? keypad panel when you tap the inactive area around the panel.
HR-33184 Timed Kiosk Menus Update Properly
In previous versions, if your location uses Kiosk, the app may have failed to update its timed menus properly. For instance, when you ran the Kiosk app at the start of day, the app loaded its first menu (such as a breakfast menu) properly. However, if it was set to change its menu later in the day (such as replacing a breakfast menu with a lunch menu), the app may not have loaded the new menu. In such cases, you could only update the Kiosk menu by closing and restarting the app. We have corrected this, and the Kiosk app now loads timed menus properly throughout the business day.
HR-34304 No Duplicated Tip Pool Transactions in Server Checkouts
In previous versions, if your location uses server banks with tip pools, you may have encountered a problem. In certain circumstances, if a server tried to perform a checkout, the POS may have crashed (quit abruptly). Later, if the server performed the checkout a second time, the POS may have duplicated the server’s contribution to the tip pool.
In such cases, the POS saved the tip pool transaction from the first attempted checkout, even though the checkout itself was not recorded as completed. Consequently, when the server performed a second checkout, the POS recorded a second tip pool transaction. We have corrected this, and the POS no longer crashes when you perform a checkout, thereby eliminating duplicate tip pool transactions.
HR-34948 Imported Ingredient Records Now Update Properly
In previous versions, if your location uses the Import/Export tool to update its ingredients, you may have encountered a problem. In the Admin Console’s Main Menu, click Tools, then click Import/Export. In the Import/Export screen, on the Menu tab, you can export ingredient records from the location’s data files into a spreadsheet. You can then edit the ingredient records in that spreadsheet, then import the records from the spreadsheet back into the location’s files.
However, in previous versions, when you imported updated ingredient records, the records may not have updated properly. In such cases, if you reviewed the updated ingredient records in the Ingredients screen, the records would not have been updated. We have corrected this, and now when you update ingredient records in a spreadsheet and import them into a location’s data files, the program will update those ingredient records properly.