I am pretty confident what is happening is print job action is firing for every order each time the ticket is closed. The action has the ability to filter when it is suppose to fire, when an order is certain state. Since, the closing rule print jobs are all blank, there is no filter. I want to look to make sure the State Name is defined the action.
Hi @Bob_be I’ve been trying different configurations for days. If you notice something that can generate this behavior we try some other configuration. I thank you for all the help. For my part, I am reviewing those configurations, but I am in the first days and I do not understand much.
The reason we using the constraint 1==2 is we are telling Samba to only fire when 1 equals 2. Since 1 will never equal 2 it will never fire. If, in the event you need to turn it on, simply clear out the constraint field.
From the image above, we want to print any new items. New items have the state of New and FNotPrinted. We are only concerned with the state of FNotPrinted (Marked with a 1.) These are the items we want printed/displayed on the Kitchen Display.
After the order has been submitted (ticket closed) the order state changes from FNotPrinted to FPrinted. When an item is in this state, the order will not print again, because the print job is looking for a state of FNotPrinted.
3. There appears to be an error somewhere in your setup. Usually there is not an equals sign in the state. The # might be causing the issue. not sure. We can circle back to that after we get kitchen display working.
Make the above changes and see if that fixes your display issues.
I made the configurations that you suggested, but if I put 1==2 in the first or third, it does not show anything on the kitchen screen when sending an order.
Leaving the FNotPrinted filter in the second one, there is no change to how it was showing the entire order.
Anyway something is confusing me. I think I’m going to start from scratch again, because I don’t want to drive you crazy with this topic. Thank you for the pacience!
Now what happens to me is that the tables do not change color when they are “occupied” (they do when the bill is printed or when they are available). As for the states, I got a little confused because I imported a Cash management configuration that is in English and I have the configuration in Spanish, so some states, rules and automation commands were duplicated. But I’m going to check it out. 100% grateful for the kitchen monitor solution!
You are correct, this is an entity state issue. Put a table in one of the non-color states, then go to Main Menu → Manage → Reports → Add Report. Enter this into the report section and preview it: {ENTITY STATE BY NAME:Tables.<table name>:Status}
it should look similar to this: {ENTITY STATE BY NAME:Tables.Table 1:Status}
Its should display New Orders.
Hi @Bob_be glad to hear you!!!
I was looking at the rules, but I have quite a mixture with the languages. In fact, for example table 2, although it is busy, in the report it tells me “available” in the status.
