Here is why it will not work. You did not actually define a State or a State flow for it. Give me a few minutes I will show you how to make it work and hopefully demonstrate States and State Grouping more accurately.
We really should use states more properly as I just demonstrated… rules and actions let you modify states dynamically but you can run into issues with State Flows… its better to define your flows from step 1.
BTW So now you can map rules etc to SStatus= and it will look for the status of Seating Order State
You can also do some cool things with printer templates now that you actually have a real state.
BTW you can do this for Ticket States and Entity States as well… Instead of using To Go ticket tags to define To Go orders you can create a custom State Flow using Ticket State so it shows To Go at top of ticket and you can define all sorts of cool behaviors around that state.
Can also use Order States for To go to flag specific orders as Togo and keep them separate from other orders on same ticket… that state can be read to show on a specific screen or printed specific place on ticket… etc
@Jesse I can’t wait to see how your seats configuration is going to work!.. Id really like to be able to add guest to a table but keep them under the same order window but separate each order by guest to keep it organized… might make splitting up bills easier when its time for people to pay as well!
So I had a thought… When i select an item to add to a ticket could i have it ask me what seat number it should be added to?.. ive tried to do it but its not working… not sure what im missing… Or what im doing wrong… When i get to this screen i actually have to force close samba… its stuck in a loop and wont do anything when i choose a seat…