A little teething issue with sub menus. Every time a new order/ ticket is made if you click into a different sub category then an item it will then default back to draught. No matter what sub menu it will always default back to draught. I am sure it is a easy fix just hard to find as it is hard to describe.
@JTRTech it seems like a strange issue. I am running 5.1.62 and no I do not have any other menu, it is a standard menu for all terminals.
The only rules added to this system are to void, re open settled ticket, print bill on its own, cancel void warehouse.
There is no rule that messes with the orders as such
I have checked all this and there is no default menu and I have removed the mapping as you said but still this issue occurs.
So you are using the actual submenu option? If I remember correctly that is by design that it returns back to main category. If you want different behavior you might consider using switch menu action and use different menus with Quick Menu at top to change between them. It requires quite a bit of time to setup but it works very well. I use it for mine.
Are we talking sub menu as in menu item sub menu not fast menu?
Unless this has changed since 5.1.60 which is still in live production system at hotel adding a product doesn’t jump back to first one. I dont remember any recent submenu discussions since the major adjustments we made late in v5 beta.
Actually, I reproduced this behavior if I have a Product assigned to the same Category and SubMenu multiple times. First addition of a non-duplicate Product makes it flip back to first SubMenu.
Yes, I am experiencing this weird behavior now as well. Very strange.
The key is to NOT make a selection from the first SubMenu. Select an Item from another SubMenu first, and you will see it flip back to the first SubMenu.
If you notice my first video, I did not do that. I selected an Item from the first SubMenu first, then selected an item from another SubMenu. That initial selection prevents the behavior.
EDIT: I just checked one of my Production Systems (running 5.2.2 Beta) and the same odd behavior occurs.
@emre, I will confirm this as an Issue/Bug since I believe it to be unwanted (unintuitive) behavior.