I am in need of some guidance, it seems I am unable to find my mistake on this odd issue.
I followed this tutorial to setup my kitchen and bar display
But i have some issues (I tried deleting everything and setting everything again from zero but same issue)
My problem is this, Everything shows in the kitchen Display and nothing on the beverage display. however (I have main server, 4 ipads mini, kitchen and beverage display) Two tables connected to server using RDP only print on the Beverage display and the rest print only on the kitchen display.
What i am trying to do is separate food to the kitchen display and beverage to the beverage display and have all of the terminals print on the correct display.
Bellow are the screenshots of my current configuration: (any help would be much appreciated)
Before trying this is will be a good idea to wait for @QMcKay’s input as he implemented a custom display state and I’m not sure if separating mappings is required regarding that.
Great suggestion to make things simpler for others. I happen to already have my Group Codes set to separate Food/Drink, so it was an easy choice for me, rather than using a Custom Product Tag and tagging every item.
@Ruben_Arellano, you have 2 Rules for Ticket Closing event for Food, and 2 Rules for Ticket Closing for Beverages. It should not be this way. The Tutorial does not show this. There should be only 1 Rule for each of Food and Beverage. For example…
However I am not able to select from the Action list: KD Update Order KDStatus twice, it only appears once on the list
Thats why i created the second rule
Ok so i deleted both of the extra rules i created by mistake, closed Samba and reopen it, created a new ticket but same issue still going.
I got both food and beverage showing on the kitchen display
It’s not that I need KDStatus, because yes we could use the Order Status State.
However, there is no way to know for sure that a users system does not have in place other Rules/Events that alter the Status State, which would make troubleshooting very difficult. So I prefer to define States for specific purposes.
This is, after all, the purpose of States, and the reason that we use them. It becomes very clear when tracing user-defined States such as KDStatus what is happening in the flow. Trying to track why/how/when the Order Status State is changing is not something we should need to even question when we have KDStatus State.
@Ruben_Arellano, at this point, you should only have the following active Rules:
Instead of deleting the Rules that you do not need, you can simply remove their Mapping to deactivate them. Be sure you only have the Rules shown above as Active.
Add a Food Order and a Beverage Order to a Ticket, and grab a screenshot. Then close the Ticket and re-open it and grab another screenshot. We are going to look at the Order State assignments and changes to see what is happening so we can narrow this down.
Then it is probably Tagged incorrectly as ItemType=Drink/Beverage.
Need to see what changes when you close the Ticket, then re-open it again. Ticket Closing event is where the States are changed and the Task Print occurs.