Timeclock Implementation Requirements - Discussion

[Jesse]

Ooh check these bad boys out.

{REPORT ENTITY STATE DETAILS:X} Entity State Details
{REPORT ENTITY STATE TOTAL DURATION:X} Entity State Total Duration
{REPORT ENTITY STATE TOTAL HOURS:X} Entity State Total Hours
{REPORT ENTITY STATE TOTAL MINUTES:X} Entity State Total Minutes
{REPORT ENTITY STATE TOTAL SECONDS:X} Entity State Total Seconds
{ENTITY STATE ENTITY LIST:X} Entity State Log Entity Names
{ENTITY STATE START DATE LIST:X} Entity State Log Start Dates
{ENTITY STATE END DATE LIST:X} Entity State Log End Dates

EDIT: I cannot seem to get these to work… @QMcKay any luck? Most of them crash… ive had a few attempts not crash but nothing reports.

[Jesse]

Guess I will wait to see the values for X

[QMcKay]

@Jesse

What if you tell it what State is start and what state is end… so it only looks for those states… instead of [:StateStart] do PunchIn

That’s what I was thinking. But it doesn’t quite work that way… I thought maybe it would pull the EndDate from the 2nd row and make it the StartDate in the first row (note: records are sorted to show most recent first)

Hmmm… I wonder now about maybe I could try setting Async to False ?

EDIT: I’ve also been wondering how it knows to set StartState to PunchOut in the Log when you Clock In for the first time?

EDIT: I give up on that for now (I won’t be using Break/Lunch States anyway, so I removed those choices - I was just trying to get a handle on how the Logging worked)

[emre]

If it is not important you can keep in/out and create a separate state flow for break & lunch statuses.

[QMcKay]

My simple TimeClock Implementation - it is not tied to Users or Logins and does not require PIN:

Time Clock - Basic - Employee Entities (not users)

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 Entities…

[emre]

For @QMcKay, @Jesse and other people who installed test releases…

Please check EntityStateLogs table and if that foreign key and index does not exists create them for better performance and stability.

ALTER TABLE [EntityStateLogs] ADD CONSTRAINT [FK_dbo.EntityStateLogs_dbo.Entities_EntityId] FOREIGN KEY ([EntityId]) REFERENCES [Entities] ([Id]) ON DELETE CASCADE 

and

CREATE NONCLUSTERED INDEX [IX_EntityId] ON [EntityStateLogs]([EntityId] ASC)

[gerlandog]

@emre

test releases…

What I am missing here???

I cannot keep up… please SLOW DOWN!!!

G.

[QMcKay]

@emre, you’re probably in the middle of writing a Tutorial that explains this; if so, feel free to ignore me…

Can you elaborate on what this function actually does? Log Entity State

• what does the Async True/False option do?

• DISREGARD THIS QUESTION… Answer: No. [EntityStateValues] contains last known State and Date/Time. I have a suspicion that it does not just log what you tell it to, instead it reads the last known State [EndState] from the Log based on MAX([EndStateDate]) first, then performs the Logging write as requested. Is this True?

• DISREGARD THIS QUESTION… Answer: [EntityStateValues] contains last known State and Date/Time. If there is no Log Data (table [EntityStateLogs] is empty), and (presumably) the Entity is ‘Stateless’ (i.e. immediately after application launch), how does it know what to write into [StartState]? For me in this case, it seems to magically write PunchOut which is perfect, but how does it decide to do that?

[Jesse]

I just posted a link for the Database Tools import file for my Time Clock implementation. Few things you need to do and will be explained in more detail in the tutorial… Create your Employee entities … create users with same name… enter the same pin for both the entities and the users.

@Jesse

Time Clock linked by Users: Tutorial will be posted soon it is in development. If not sure what to do then wait for tutorial before installing.Time Clock.zip (2.4 KB)

[sukasem]

Can’t wait for official time clock release!
It should have button in the main screen with Work Period, POS…right.

[Jesse]

Personally I don’t like using the main screen for said function.

[sukasem]

Or make Automation Button at the main entity screen

[Jesse]

I have a system that sort of answers that I am about to make it live.

[QMcKay]

@sukasem

Can’t wait for official time clock release!It should have button in the main screen with Work Period, POS…right.

I think this is as “official” as it’s going to get for the next while. The added feature (Log Entity State) has allowed us to build a basic TimeClock, but the feature can also be used for many other things (i.e. tracking table usage)… My guess is that is the primary reason for this feature addition, because it is not specific to TimeClock. I think we’ll be waiting a long while for an “official” TimeClock…

That said, this feature is very powerful, and can be used to build a very decent TimeClock Implementation, immediately. How you do it is up to you.

@Jesse, in his implementation, links Employee Entities to Users and the Login/Logout mechanism, while my posted implementation is very basic to show minimum requirements to implement it…

Time Clock - Basic - Employee Entities (not users)

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 Entities: …

[Jesse]

@QMcKay

the feature can also be used for many other things (i.e. tracking table usage)… My guess is that is the primary reason for this feature addition

Another cool thing this might open up is the Order State tracking. You can track average time for an order to hit the kitchen vs Ready… You can track delivery times… all sorts of really cool things. This will enhance Kitchen screens…

EDIT: Sorry I jumped the gun Order State Logging is not currently available.

[QMcKay]

@Jesse

Order State tracking

@emre

First of all that will be specific to Entity States.

While I did mention the design could have been made for any type of State, that’s not what we have here. It is specific to Entities [EntityStateLogs]… it won’t log Ticket or Order States, however…

@emre

Of course it will be easier to implement same thing for other states but there is no reason to make querying harder as we never need to query other state types together.

So it sounds like @emre could do some copy/paste of code to implement it for Ticket and Order withou too much hassle.

[Jesse]

Yeah sorry I got ahead of myself. You are correct it is not ready for that yet. I tried to say in the future… when I said “might open up” I just used bad wording.