Here is what I am working on. This is going to be only available with V5 due to the navigation screen. But I will share it with you guys.
What this flow does is requires Employee to enter their Password when entering POS. All passwords are 4 digits. It checks the Length and Checks against the Entity Data Password. If match it assigns entity and allows tickets. If not a match it says Invalid Password you press ok and it takes back to Navigation.
This is a start I will customize it further like maybe instead of going back to navigation it will just require Password Entry again or maybe have option to override it with Admin Pin.
Also I will put the check in place to see if they are clocked in.
PS This method fixed the blank Entity issue because its checking that before it executes Change Entity.
@hadjieff even better I will design a configuration task for it. You donât know what that is yet but when version 5 releases I promise you will like it. It is much better than sharing the database.
Got it working. The rule wasnât âmappedâ. I guess I just figured that rules were immediately mapped. Now how would I go about adding a button to âchange waiterâ to the current user and if possible have the current waiter or an admin input their pin?
I was able to create a âchange waiterâ button by creating an automation command and then running the action for updating the entity.
The only thing Iâve noticed is that the entity on the screen doesnât refresh until I go in and out of the ticket. Is there anyway to refresh the ticket screen?
In order to complete the use of the âwaitersâ entity for me, I need to get a custom report working which will do an âend of shiftâ report based upon the âwaiterâ entity for people to count out.
Iâm just starting to dive into the module (got it yesterday). Has anyone completed a report like this yet. BasicallyâŠ
Select Payment Totals from Tickets Where Waiter Entity = Current User and Date* = *Current Work Period
PS Case sensitive⊠if its caps it has to be caps.
However there is one flaw with that syntax⊠what if current user is admin just to view reports?
If your tying users with Entities then it wont matter in the reports⊠you just need to look at sales per entity. Or Sales per User. What would be the purpose of linking the two in the report?
I would write a different report for the admin. This report is only for waiters at the end of their shift. Since tables are often transferred to a different waiter and then cashed out by that waiter I need to show totals at the end of the shift for that waiter based upon the waiter entity.
The idea of using CURRENTUSER is that only that waiter should be able to see their totals. I donât think there is anything to gain from showing all waiter totals.
A follow up question, can you restrict certain reports for certain users? Ideally I want specific user or user groups to only be able to access end of shift reports and admins to be able to access everything.
