Jesse:
Here are the two main tutorials for TimeClocks with SambaPOS:
Note Punch Editor will be v5 only so its not shown also these tutorials might change once v5 releases.
Time Clock: Linked to SambaPOS Users with Custom Reports Tutorial
[bangbang] It is wise to backup of your database and test this first before putting into production
Download Link:
Operational Flow:
Clock In:
Employee enters pin or scans badge to log in to SambaPOS4Time clock greets employee by name and gives option to Clock In or Cancel
If employee chooses Clock In it records a punch and logs them into SambaPOS
If employee chooses Cancel it takes them back to the User Log In screen of SambaPOS4
Clock Out:
Employee navigates to the Time Clo…
Time Clock - Basic - Employee Entities (not users) Tutorial
Basic TimeClock implementation using Employee Entities (not Users) and 2 Entity States called PunchIn and PunchOut.
REQUIRED: SambaPOS v4.1.65 + REQUIRED: Custom Report Module from SambaMarket.com
Database Tools Import Files:
Automation (Automation Commands, Actions, Rules): TimeClock_Automation.zip (2.1 KB)
Entity Type, Entity Screen, States TimeClock_EntityType_EntityScreen_States.zip (1.5 KB)
FLOW:
Button to show TimeClock screen:
[image]
TimeClock screen with 4 Employee E…
Hey @Jesse . Based on these two tutorials what is the advantage or disadvantage to using user vs entities to track punch in’s. I currently use entities to assign a waiter to the ticket. Just curious if it matters which way I go.
Thanks,
Joe