Im not saying it need to be hardcoded, just asking is solution to do so to prevent this senario with switch user.
Can you explain that scenerio in detail. I think you kind of did in another post but you have not here yet. I simply latched onto a challenge to create something but now that I see points from @emre I wonder if its really useful if its not then I would rather spend my time figuring out useful cool things.
OK;
- I Log in to terminal A and start a ticket 1
2 Walk away and pour drinks from tap at other end of bar
3 customer calls out more drinks or alternativly say while waiting for guinness to settle grab another customer a bag of crisps
4 I swipe in to termial B as closer but forgot to logout of terminal A to ring in crisps on ticket 2
5 A new ticket (2) is started for me to ring in crisps and program setting update lodgs ticket 2 as last ticket,
6 While at this terminal another tender logs me out on terminal 1
This lease ticket one open but not on a table/customer, I feel the ticket list is not ideal for use on busy bar as a graphical layout is easier to identify like tables etc.
To a regular bartender who ends up in this position I would not know where the ticket 1 went and proably end up ringing it all in again.
This ticket would go forgotten untill you try to run end of day and are prompted that there are open tickets by which point that bar tender has buggered off home or cant remember it and you dont know if its been paid or not or rang back in and needs voiding.
Does that explain the situation?
The situation is created by the use of the swithc user config however being able to switch user on busy bar without allocating to an entity is much more economical
Up till now this is the way the place down the road has been doing it as hadnt got my head arround the switch user config.
Am attempting to force logout of user from any other terminals on login but am stuck.
So far i have setup,
Action of send message [:Message}
Additional action on the open hold ticket on login rule to broadcast the message ‘LOGIN {:CURRENTUSER}’
Now am working on the message received rule to force logout/close
Rule: Message received - rule constraint of command contains 'LOGIN {:CURRENTUSER} fireing the actions of close ticket and logout.
HOWEVER even with the switch user setup in place and working the logout only happens on the other machines if no ticket is open, It only logs out if the other terminal is logged in but no ticket started.
It doesnt close the change popup/ask question which shows on ticket payment if change due.
Any suggestions?
Its odd as the LOGOUT button ive made which actions close ticket and logout works to close any ticket reg of entity due to the switch user tags however the message received rule which actions the exact same close ticket and logout actions will not close the ticket?!?
Tried adding a exacute automation comand action of the LOGOUT button but that didnt work either :-/