Switch Between Users (Not Entities)

[GreatShakesBar]

Having followed the tutorials on switching users (not entities), the system needed a couple of tutorials to follow to get working.

This isn’t a tutorial but is a database file of a complete set up of the 2 tutorials listed below:

Switch between users

I’m wondering if there is a better way of switching between users. On our old system, user A could be halfway through entering a ticket, user B could then login to the till and put their own ticket on, user A would then logon and resume entering their ticket. Its a busy bar, so sometimes other staff need to jump on the till maybe whilst the other person is pouring the drinks or waiting for the pdq machine. I’ve almost done this through on hold tags. I’ve created an automation command - “log o…

and

Rick's Tutorial 7 - Auto Assigning Cashier as Ticket Entity (needed for switch user function)

If you work in a busy environment such as a bar where multiple people use the same till at the same time, to speed up serving another cashier may need to use the till to process an order whilst another cashier has already started a ticket. For this it is useful to have a switch user function so that if another cashier needs to use the till they can press the switch user button, it saves the ticket the another cashier had open so that the 2nd cashier can process their transaction. when the 1st …

This database file will create an entity called “Staff”, you will need to create a new “Staff” entity for all staff members, making sure that the entity name is EXACTLY the same as the User Name. If they are not the same IT WILL NOT WORK!

Mappings are set to work for everyone, if you want to change this you will need to change the mappings for the rule “SU_Assign Staff To Ticket On Login” and the automation command “SU_Switch User Button”.

Matt

[GreatShakesBar]

Re-Uploaded, fixed Database File:

Make sure you have “Auto Logout” enabled in Settings>Terminals

Switch_User_2.2.zip (1.6 KB)

[1bigwink]

Thanks for posting! What modification is needed for v5 please? I have loaded ok and created the entities for staff but when I click the switch user button nothing happens.

[GreatShakesBar]

It’s made in v5. Check your mapping for each rule

[GreatShakesBar]

Apologies, there is a rule missing. Will re-upload.

Matt

[GreatShakesBar]

Updated to include Table Switch/Merge problems.

Also has tables 1 to 20 added to prevent switch user from returning after table selected. If more tables are needed they need to be added in the “Hold Ticket” and “Open Hold Ticket” rule constraints.

Matt

[JTRTech]

Nice try @GreatShakesBar, hate to be bearer of bad news but think there are some issues with the setup;

Hold Table Ticket

For one this config task is using entities and guessing you dont have entities per staff name so not sure exactly how its even closing the ticket in the first place as you cant set an entity which doesnt exist, Sorry, @GreatShakesBar but this config doesnt seem right to me; [image] Clearing the setting before closing…? No constraints [image] Kitchen print on command… whouldnt this be in ticket closing anyway? [image] Not sure whats going on here? This is what will be recalling the tic…

Some of the points might be out of context as think you were going for a all table are paid type flow but definatly some issues there I think.

[GreatShakesBar]

Hmmmmmmmm shouldn’t do. Maybe I missed something. Don’t think I did.

Did that guy create staff entities?

I’ll check it out with a new setup

[Jesse]

It could just be he needed a different flow than you.