NEW FEATURES:
The following options have been added:
-
Define product weight from KDS 2
Press and hold a product with weight to access the content options and adjust its quantity directly from the kitchen. The new value is synced with XEF and recorded in the activity history. -
Profile selector at login
If more than one profile is configured, KDS 2 will prompt the user to select which one to use upon login. If only one profile exists, it is assigned automatically. -
Unfire dishes from KDS 2
You can now undo the firing of a dish directly from the KDS, without having to go back. -
Improved notification management
New button to clear all notifications at once. In addition, notifications from the previous day are automatically deleted when the app is opened.
The following items have been improved:
-
Collapsible filters
Filters now include a button to collapse or expand them as needed, without losing sight of the rest of the screen. -
Device status bar visible
The status bar of the tablet or Android device is now displayed at the top of the application. -
Orders without dish order
KDS 2 now correctly accepts and syncs contents that do not have a dish order assigned. -
Automatic device information reporting
KDS 2 automatically sends the installed version, device model, and IP address to the back-office each time a user logs in. -
Integration with the
contentsReadywebhook
KDS 2 notifies other services when the contents of an order are ready to be served. -
Dish firing (fired) and unfiring (unfired) notifications
KDS 2 notifies Revo XEF when a dish is fired or unfired.
RESOLVED:
Resolution of the following issues:
- Incorrect time counter when syncing: the order time counter was using the moment the order was opened as a reference instead of when it was sent to the kitchen. It now displays the correct time.
- Closed order disappeared when syncing: if a completed order was reprinted and orders were synced, that order would disappear from KDS 2. The issue has been fixed.
- New order notification sounded on KDS that should not have received it: the alert sound was triggered on devices that had no visibility over that order. The behaviour has been corrected.
