I followed a tutorial from probably JTR or Q’s tutorial in creating things such as quick CASH buttons, amount the couple tutorials they also include a feature to turn on the auto update/refresh of any order pending/not paid.
However, this feature interferes with with my multi user environment when one terminal is submitting an order, it will flushing out the screen of another terminal that is still ordering without submitting(that is the order is still at NEW. Can anyone point where to turn of the auto refresh of the order screen?
Thats a ticket list.
Setup I have used that in is my ‘temp tabs without entity tutorial’ and dont remember a refresh of any sort in that tutorial. Mine used a ‘display ticket list’ action where state was specified - beleive it can display list using filters of tag name, state, entity type, entity name and username.
It is also used by detault when selecting an entity with multiple tickets.
The KD has nothing to do with this. It has no automation that uses the Broadcast Message Action, and even if it did, it would not be the cause of your issue. It also does not invoke the Display Ticket List Action.
That said, Messages are being broadcast all the time between Terminals so that they can inform each other what they are doing especially for refreshing Entity Screens and Entity State Updates, among other things.
However, there should be no way that a Terminal with a New Ticket with an Order on it just closes, disappears, and the Ticket List gets displayed.
Generally when a Ticket is Open like that, nothing can make it close except Cancelling all Orders and hitting the Close button at the bottom. Having Automation in place that makes that routine happen is highly unlikely. And a Message Broadcast will not cause that to happen either, not by default.
Are you sure all Terminals are configured with a unique Name in Local Settings on each Terminal?
Messages are being broadcast all the time between Terminals so that they can inform each other what they are doing especially for refreshing Entity Screens and Entity State Updates, among other things.
That is my understanding too.
I have set the each computer with different terminal names but “may not have reboot” the computer. I have however exit the SambaPOS annd reload it several times.