- DATE:
- AUTHOR:
- The Shift4 Updates team
Release Notes: ActivateX 16.4
Need more information? Email enterprisesupport@spoton.com or call (877) 559-4225. The Support team is available 24/7/365.
Released On: 21 April 2023
Release Version: AX_16.4.0
Release Type: General
Content: Usability improvements to tipping and handheld devices. PPI improvements. Bug fixes.
ActivateX Compatibility:
(as of 21 April 2023)
CheckSync: 1.1.11.1
KDSX (Android): 5.11
KDS (iOS): 4.11
Connect: 12.3
InteractX Kiosk: 2.4
This version only supports sending orders to KDS iOS in Connect Mode (with classic mods) and Local Mode (with classic or new mods). Support to Dual Mode (Connect + Local) will be delivered in a follow-up release (requiring additional KDS and Connect updates).
Feature updates:
Tipping on Customer Facing Display (CFD)
When using Tip on CFD, the buttons will read from left to right, with Custom Tip being the first button and No Tip being the last.
Previously, the display had No Tip as the first button and Custom Tip as the last.
Data gathered by some of our clients and reviewed by the product team shows that humans are likely to press the "No Tip" button more when it is the first button they read. The change should lead to fewer "No Tips" and more tips for the agents.
Orientation Settings
When using a tablet, ActivateX will respect the device's rotation lock settings.
If the device is set to allow screen rotation, then as the agent rotates the device, the screen will rotate to the correct orientation.
If the device is set to disallow screen rotation, then as the agent rotates the device, the screen will remain in the initial orientation.
New Hardware Support
Customer Facing Display (CFD) alterations made to support SpotOn custom hardware.
Previously, there were elements cut off due to the screens being slightly smaller.
Atrium Integration
Added support for non-taxable tenders during meal equivalency transactions.
Previously, the meal equivalency tenders still expected tax to be paid, causing multiple swipes.
CBORD Integration
Improved error handling and the messaging displayed to the agent. This will improve troubleshooting and give agents a clearer picture when the card swipes fail.
LAVA Integration
Changed the workflow used when scanning multiple LAVA cards in one transaction. The first card scanned will apply any discounts and available stored value. The additional cards scanned will only check and apply the stored value. LAVA does not allow more than one card for loyalty and discounts.
Generic PPI
Added New Endpoints
/useDiscounts allows the POS to notify the partner that discounts were used on a transaction, so any limited-use discounts can be decremented, and partner reporting can reflect discounts used.
/voidDiscount allows the POS to notify the partner that they need to void the usage of a certain discount.
/checkIn /voidCheckIn allows the POS to notify the partner that a user has "checked-in" using their loyalty program but does not intend to use it for payment. This is useful for when the customer just wants to accrue loyalty points on their card.
Suites Stored Card Display
When using a stored card to pay for a purchase on a suites account, the button will display both the last 4 digits of the card number and the cardholder name.
Previously, it only displayed the last 4 digits of the card number.
Bug fixes:
Offline Transactions
In 16.2 builds, there were instances where transactions were moving to Sync/Decline and Offline and unable to be synced to Connect. This was fixed in a patch AX 16.2.5 and in this build.
Cached Login
Occasionally, when logging in with a cached login, the menu would be blank. This has been corrected.
Logging In/Out
In previous 16.X builds after employees log out to the terminal login screen, the system would still timeout and lock up, preventing users from logging back into the terminal. The only workaround was to close AX and reopen it. This has been fixed.
Kitchen Management
We recently identified and addressed a case in which the Cancel Mode flag on
Terminal Role > CoreUI was not being respected when using Fire On Next. Changes have been made so that when using Fire On Next, the Cancel Mode will operate the same as in other scenarios.
Receipts
It came to our attention that when Checks are enabled but the venue is not using layouts, the layouts would still print on the receipt with null values. This was messy and unnecessary. It has been fixed, so only venues using layouts will print them on the receipts.
Suites
Previously, when performing a Split Check on Suites, the newly created order number was negative. This has been fixed.
Fixed a bug where suites preorders that were set as tax-exempt had taxes applied when they were opened in AX. Now, the preorder will remain tax-exempt when the order is opened in AX.
Check Sync
When using Check Sync and multiple devices logged into the same user, the check queue on the device not initiating the order would not update automatically. The agent would need to swap between the Menu and Checks screen to see the update. This has been addressed, and now the check queue should display all checks without a refresh.
Discounts
Previously, during a refund, item-level discounts would be split over two entries. If the item level discount were $1.00, then during a refund, the cart would display it as two rows of $0.50 each.
Taxes
When using item-level taxes and applying different taxes to the parent item and the modifier, the modifier inherits the parent item tax rate. This has been corrected so that the modifier will only use the tax rate assigned to it.
Refunds
Fixed an issue with the refund process, which would cause an error message if the process was interrupted. This was a limited use case and would occur if mid-refund of a split payment, the POS was closed. Now, if the POS closed mid-refund, the POS can be reopened and the refund process can be restarted.
LAVA Integration
Addressed a problem where the LAVA cart level % based discount was applying to the subtotal, and the expectation was for it to apply to the Total.
Fortress Integration
Previously, agents would encounter an error message when applying a $0.00 Fortress card to issue a discount. Now, they will be able to do so without error.
Known Issues:
After a background refresh, sometimes items below the fold are not shown. Users can select the Menu button, and full item list will populate.
After Item Breakout is performed, updating modifiers on one item will also cause the second item to get modifiers. User can make the edits necessary at that point. To avoid the issue, do not use breakout and build each item separately.
On initial login, new mods will not populate till after a manual or background refresh. Once a refresh occurs, mods will display properly (until a Clear Storage is performed).
Order Types are not supported when running with Checks in Connect Mode.
If the location is setup to use order types and the accounts/roles use Checks, the orders will not show on KDS.
Combined Suites orders will appear on KDS as partial Submissions (after the combined order is paid).
Suites preorders, when accessed day-of, and items added, send all items to the kitchen, even the items already fulfilled on preorder.