@emre IS there any updates on this issue as the users are getting more impatient with it because when the bar is busy they are making mistakes due to this.
Sorry about all this, it is just affecting the use of the system as they have to tkae more time to not press the wrong product as it swaps the menu items.
that is correct, after the first item is selected the menu jumps back to a different sub category. This causes a few issues with the people working on the systems as they might need a few things from one category and after the first item is selected it will jump to another category. After it jumps once on that one order it will not jump again.
this issue is still a consistent battle which I am still trying to resolve. Something I did find out is the menu changes back to the first catagory as soon as the status is changed to “New Order”, which the system does after you put the first product in. I am wondering if there is a way to default a new ticket to be in the status of a new order before a product is pressed.
If anyone knows how to to do that it would be great.
You can use Ticket Opened Event Rule add constraint Order Count 0. Then use Add Order then Cancel Order Action.
Or Update Ticket Status from New To New Orders.
Maybe try Update Ticket Status first which is easier.
Do you know how to create Rule? There is Event Name and Constraint that you can select. “Update Ticket Status” Action already have it by default just add it.
So when I open up the POS it says new ticket and if I press any food or drink it will default back to the first page (Which is unhelpful)
After the first product has been put in the tick has a status to it and when it has that status it doesn’t jump from the different sub menus. I am trying to get the status there before anything is pressed so then hopefully it will stop the menu from jumping.
Be very carefull manipulating the default status states for tickets or orders.
If you don’t understand what your doing (which with greatest respect you clearly arnt fluent in the rule system and flow) you will very quickly mess up your system.
This is very true and you all are a great help with people like me. Although this issue has been causing a lot of grief for me and also the bar staff when using the system on busy nights which where they are is very frequent. These tills are in a holiday home that has 6tills plus a server plus a back till.
So they have been reporting this issue to me for a while and they are becoming impatient. So I need to do something drastic and this was the only workaround I can see. If the issue wasn’t as persistent or annoying as it is for them, then I could have had a chance to wait until an update however they have had it.
I have the server backing up daily with the database also being backed up.
I would love to know if there is any other alternative to manipulating the default status.
TBH I dont understand what your trying to do, pretty sure the ticket state has nothing to do with it, Q tested the issue and wasnt first order only, it was to do with the menu itself and what was added first as didnt happen every time.
If emre was on the forum he would probably have sorted and been fixed in an update by now but he seems AWOL at the moment.