I thought I got that. It when it is set to New it only prints new orders and thus the last Ticket on the entity. When it is blank it will print the entire order as many times as you hit the button and it still only prints the order from the last Ticket. Another problem because it re-sends the orders on the Ticket to the kitchen. So for example; a customer orders an appetizer so the server punches it in a sends the order to the kitchen; then 10 minutes later they decide on their entre. When the server sends the entre to the kitchen it also re-sends the appetizer.
So to avoid this, I placed the original Order State Name (Status) and Order State (New) back into the Execute Kitchen Orders Print Job Action. But the problem still remains that the only the last ticket automatically prints.
I am also curious to see what Kendash comes up with. Iām going to implicate the Advanced Split Payments either way. Seem like it could be very useful instead using the Move feature.
Having these will defiantly not work if your ticket closing rule is as default in changing orders to submitted.
I would sugest you add a new state to orders when added which are to be printed of say State Name āKitchenPrintedā Value =āFalseā then set the print job states to look for kitchenprinted = false rather than new then after your print job for print button add an update order state action to update orders with KitchenPrinted=False to =True.
This will mean it will print to kitchen a ticket already closed/orders submitted for orders not already printed to the kitchen.
That should sort states.
This seems like a pretty good idea. I could play around with this.
Yes. My ticket closing rule Update Order Status Action changes the Status to Submitted
Where would I find this?
I am not too familiar with States. To be honest I have steered clear of them because I saw a lot of warnings in the forum here about messing around with them.
Yes, dont change the default Status States but you can make a new state action with a state name of something else.
If you do that it will only effect things which you add which work from those states.
TBH the fact you havenāt looked in to them if part of the reason why your strugling to understand what Im saying about the new/submitted sequence and its effect as it stands of either printing everything or only new orders.
I edited the Ticket Closing Rule. I bypassed the Execute Kitchen Orders Print Job and changed the Status and Current Status to KitchenPrinted and False respetively.
I donāt know what you are trying to do. What you try to archive with creating new state or what you want it to be?
Donāt see how you creating State and you still using Status State to update your KitchenPrinted which is wrong. There is no Status False (you never set any order to Status False) so, it will never update to KitchenPrinted.
And I donāt see how the flow will be different from default even with KitchenPrinted State.
I am trying to get all tickets under one entity to print to the kitchen at the same time. I really dont know what I am doing at all. I am just trying to piece together what people have said on here. I have never worked with states and I do not know what I did wrong.
I add an action to default Add ticket rule to prevent ticket to print you can create new button if you like but I think this is less clicks. But the last ticket you have to click add ticket and close empty ticket (If you click close on any ticket it will print that ticket). when you go back to the same table you will see print all:
Click print all it will print all un-printed tickets. Even some ticket already print it is not a problem.
