Clock in/Clock out auto sequence: Micros Res 3700 version 3.2

[mrwonderfulsaloon]

Hello. I am brand new to the forum and have searched high and low to find an answer to setting up a simple auto sequence so that the server receives their "read" at the end of their shift and is also automatically "clocked out" from the micros system. I would like the server/bartender/kitchen to be able to clock in on their own with their unique password or swipe card. But I want only managers to have the ability to sign them out, the system is already set up for servers and bartender to received their "reads" with a manager swipe card only. I was able to create a button in the touchscreen designer, it clocks them in and clocks them out with their own ID. I just want to auto sequence the clock out feature when they receive their print out when they are done their shift.

Any help would be much appreciated. I apologize in advance if I posted in the wrong section of the wrong forum.

Avery

 

[CathalMF]

Easy enough.

1. Check your manager and employee autosequence privleges. PosConfig -> Employee classes -> Privleges -> Privlege Levels. Higher number = More privlege. eg. Manager should be 3.
2. Create a new Autosequence called "Employee Report and Clockout". Set the privlege level for this autosequence to 3. PosConfig -> Reporting -> Autosequences
3. Add steps to the new autosequence. Posconfig -> Reporting -> Autosequence Steps.
3a. Step 1. Report. Set the Range Source to be Specified. Range Selection to be Today, Shift Range to be Current Shift, Object Range Source to be Inherit. Set the report to be a 40 column employee report that you want.
3b. Step 2. Stored Procedure. Set the stored proecedure to be the chockout employee procedure.

I believe this is it. Note that this is from memory.



Do you want some custom SIM scripts developed. Contact me via my website

http://www.microspostools.com/

 

[mrwonderfulsaloon]

I followed the steps above. It doesn't clock the employee out. They can still punch in more orders and so on. Not sure if it because i have an existing auto sequence for when we print their report at the end of their shift.

In my existing set up we don't use a clock in/clock out system, we simply write down their hours manually on paper. This can be bad for many reasons, people forget to sign out and we have to guess when they left and sometime we lose, sometimes they lose.

Currently when a server is finished work we print their report which will only print if all checks are closed otherwise the system will tell me there are open checks. Then we manually clock them out. This button under touchscreen designer is called "10151 server check out" under the autosequence in the bottom right corner. So i assume if i go to autosequence steps and look under "10151" i will find the sequence that currently prints their report and i just have to add a clock out step last.

the current sequence goes:
step1)
stored procedure:
error actions-branch, branch-10101 uws open check report, step 1
stored procedure- 105 employee open checks, parameter-employee parameter

step 2)
report:
date range source-specified, date range selection-today, shift range source-current, object range source-inherit.
error actions- ignore
report-136 40col-employee detail totals



So my question is how do I take the current auto sequence (10151) that is performing server report at the end of their shift and add one more "step" to that auto sequence that also clocks them out? Currently if i had a 3rd step to my existing report print as a another stored procedure, i find the option to add "112 clock out an employee". Parameter is set to "employee parameter", source, numeric value & string value are left blank. Error action is set to "ignore", and ranges is left blank.

again, any help would be great. I feel like i am just one step away from getting this work.

Avery

 

[BootstrapperRI]

Yes, add the third step as that Autosequence and set the object range source as inherit.

David Jenulis

http://www.ncbpinc.com

 

[mrwonderfulsaloon]

I just tried adding the 3rd autosequence but still no luck. It prints the server read and that ID remains in the system. I can still exit out of that screen and continue to punch in orders. If I go to clock in, it asked if want to clock out.

Any other ideas of what I try?

Also, what if late at nite a server gets their read to cash out at 1am, but after their cashout is complete they stay on to flip chairs and clean. Would the best solution for that scenario to just manually clock them back in and out for that time period where they will have no extra sales from the time their read was printed?

avery

 

[Moregelen]

There is a stored procedure you can use the lock the employee out of the system rather than clocking them out. We usually setup our employee checkout report to also lock the employee out, and then the End of Day unlocks all employees. They can still clock in and out, but can't ring anything in. The only annoying part is that anyone working a double now has to be manually unlocked by a manager for their second shift, but we just look at it as a form of validation.

Add stored procedure Lock Employee, #146, to your Employee Balance or whatever you call it autosequence. Set the source to object number. On the ranges tab set the object source to inherit. Make sure to give the managers a button they can hit to unlock employees. Do this by creating a new autosequence with Unlock Employee and set the range to prompt. Then use the autosequence with prompt button type.

One thing to keep in mind is that if the report fails to print for any reason, like being low on paper, they'll still get locked out. It isn't a supervised print or anything. You might want to consider creating a touchscreen with a confirmation button they hit to indicate it printed, and have that button do the lockout.

Also make sure to add an unlock employee account with range set to all to your end of night or you're going to have a bad time every day.

 

[mrwonderfulsaloon]

Hello again,

So i have given up on the system automatically clocking employees out when we print their end of shift report.

But...now when i try to put the autosequence back the way it used to be it no longer works.

Before, if i attempted to print a server report when they still had open checks it would prompt me on the screen and no allow me to print the report until they were closed. Now it just prints the report regardless if there are open checks or not.

this is what it looks like now.

autosequence Steps.

10151 server check out
1. stored procedure: ranges=nothing, error actions=branch, 10101 uws open check report, step 1, stored procedure=105 employee open checks, employee parameter.

2. report: ranges=specified, 101 today, current shift, inherit object range. error actions=ignore, report=134 40col employee detail totals.

If i delete the stored procedure the report prints fine but can still print with open checks. If i leave the first line or tinker with it, it usually just prints the open check report even though im trying to print a detail report.

How do i tell the system to first look if the server has open checks, if they do prompt me to close them first. And only allow me to print the read once all are closed off?

Any help would be appreciated. Also if anyone know how to fix this and add on the line that would close them out from the system that would be a bonus.

Avery