I just had a session with Nizam from Samba Support, we played around with some of the settings in Task Editors, here is where we stand at the moment:
I have 3 terminals, KD=Server, Terminal A and Terminal B as two cashiers, Orders are taken on 10 GOtablets.
There is 2 KD screens, KD - Food and KD - Drink
This morning when we playing with the settings, Nizam was checking the Disable Cache options, which I also aware as I read some of your earlier posts with Emre, but that have never concluded I believe.
The KD - Drink with some twicking, it was working and updating other screens when marking tasks complete on 1 terminal or server.
But the food one is always 1 step behind, - when mark dish-1 ready on Terminal, it doesn’t update on Server KD-food, and when mark dish-2 ready on Terminal, dish-1 got updated on Server KD-food. so on and so forth.
We sort of stuck at that point, and as much as I appreciate Nizam for the help, there won’t be much we could carry on doing anymore, so we called it for a day and I went on to testing around with the automation as I explained earlier, I wish to trigger a close table action when Task is marked complete - I will come back to this later, for now, let’s focus on what happened on the Task Editor itself that may just solved the problem of refreshing.
When I was checking why the 2 screens behave differently, I noticed that KD-drink under the settings, auto refresh was set to unticked, and the interval is 1.
So I went to do the same for the KD-food, which made it sync between the terminal and servers.
Moreover on the earlier topic of to trigger refreshes when tasks marking complete
I have an Automation setup as below:
I believe this triggers the Named Automation Command?
Then A rule set to when it is triggered:
As you can see, I have set multiple actions that I felt might do a refresh on the KD screen,
but when this is in action, the rule fires, but No refresh at all.
The only ways to refresh the KD screen task editor was
Click on the Top tabs on the terminal you would like to refresh the screen on.
to refresh another terminal’s KD screen on a different terminal, this requires to open a ticket and close it, don’t matter if there is order on the table, as long as click on close button, all terminals KD screen refreshes. That is perticularly why I was asking how to trigger a close table action.
However, even though I placed the action Close table in my refresh rule, it still did nothing.
Which makes me believe that there must be some other actions either before ticket closing or when ticket closing that is causing the refresh, moreover, it can also be something hardcoded in the close table/ticket action itself.
I am happy for now with what we achieved so far, but I in general doesn’t like auto refresh as I used it before and find it cause lags on the screens that uses it. So I still hope if there is an alternative solution.