Automatic Start of Day

Yes, we have work period closed rule event and a print report action so is easily done.

I saw the trigger and was concerned about this however thats for work period start.
I see that they have just done a user pin specifically for end work period. I would just create some form of confirmation for the work period actually closing and/or a message prompt should there be any open tickets.
Alternativly use the loveley new custom nave screen to create a end work period button…

BTW just so you know triggers will NOT fire if a ticket is open that is how they are designed.

The principle is the same… so if they forget to sign in to that user… wp doesnt get closed… its just added step for them to remember… additionally if they do sign in with that number but a ticket is open… WP doesnt close… it wont warn them it will just not close it they will logout thinking its closed and its not.

A better discipline is to just make them click Close Work period and it will warn if open tickets. I am sorry but this is a very bad practice to try and do this and its my opinion the user method with auto close is even worse your making them manually do something but no assurance its closing WP when they should be clicking Close WP and it properly tells them if there is any issues ensuring it closes.

You do not have to give them Admin to close WP its a simple setting for user settings.

I am new to Samba

Could @JTRTech please show me by picture

Just done a tutorial.
There was probably already something here but was just as easy to do a fresh one, only need one action and one rule.

1 Like

Yea I get the concerns for automating the END WORK PERIOD. I mostly did this to show START OF WORK PERIOD and to include some thing I found interesting as I toyed around. I think setting up user pins to automate actions has a lot of potential.

We also have Application Started event, Screen Change event etc.

I agree there might be potential for something there but what is difference in entering a pin for user login to automate something vs just using automation command requiring a pin? Wouldnt it be better to just create an Automation Command Button and automate it to match an input string via constraint? I mean the effect is you press it then enter required pin and it executes if correct pin is entered. That sounds more realistic vs using a User Login to perform a function.

PS: I am not entirely against automating Work Periods I am trying to stress how important it is to think your process through entirely because 99% of the time automating Work Period starts or Ends will cause major issues eventually that could have been prevented.

Discipline with requiring employee to start or stop WP manually means you have accountability as well. When you automate it then its even harder to know what went wrong and who was responsible when it does.

@emre probably wishes he never allowed that automation :stuck_out_tongue: It was partly mine and Q’s fault hahaha

As you have said before with the custom nav screen or perhaps a ‘manager entity screen’ it offers an alternative to the actual WP screen. It wasn’t added with the intention for full automation.
So long as people understand that it wont work if there are open tickets.
Perhaps he should have hard coded a message into the action if there are open tickets.

1 Like

I like that idea of hard coding a message if tickets are open, i use the action to close work period as part of my end of day (cash up) screen. if there are open tickets nothing happens, it would be good if there was a reminder popup to say tickets are still open

is there something we could create such as an ask question that pops up if when trying to end work period there are open tickets? ive not looked into this yet its on the “To Do” list haha

You could obviously create your own message.
The thought on a hard coded idea was to elevate the beginners using without understanding messing it up.

1 Like

The examples you guys have shared is why Emre allowed it but it was not meant to do full automatic open close automation.

The Actions for Starting and Ending a Workperiod are fantastic. It means we are not locked into a hard-coded Workperiod screen, Instead we have ful control over it. This is the main reason the Action were created. They were not created to be used for Automatic Start/End, though that is possible.


##WP Open or Close [Automation Button] (Widget)##
Entity Screen: Workperiods

###Properties (13):###

Widget Type: Automation Button
Name: WP Open or Close
X: 315
Y: 0
Height: 150
Width: 465
Zindex: 0
Angle: 0
Scale: 0
Corner Radius: 0
Auto Refresh: checked
Auto Refresh Interval: 0
Margin:

###Settings (7):###

Button Color: #00FFFFFF
Caption: [='{SETTING:ISCURRENTWORKPERIODOPEN}'=='TRUE' ? '' : '']WorkPeriod is[=('{SETTING:ISCURRENTWORKPERIODOPEN}'=='TRUE' ? 'OPEN' : 'CLOSED')][=TN('{REPORT TICKET COUNT:(TS.Status=Unpaid)}')>0 ? 'Cannot Close Workperiod with ' + TN('{REPORT TICKET COUNT:(TS.Status=Unpaid)}') + ' Open TicketsClick here to see Open Tickets' : 'Click here to ' + ('{SETTING:ISCURRENTWORKPERIODOPEN}'=='TRUE' ? 'Close' : 'Open') + ' the WorkPeriod']
Command Name: WP Start or End Confirm
Font Size: 16
Image Path:
Validation:
Value: {:ISCURRENTWORKPERIODOPEN}

##WP Start or End Confirm [Automation Command Executed] (Rule)##

Rule Name: WP Start or End Confirm
Event Name: Automation Command Executed
Rule Tags: Workperiod
Custom Constraint List (1):
Execute Rule if: Matches
Automation Command Name Equals WP Start or End Confirm

##Actions (3):##

WP Ask Question

Constraint: ‘[:CommandValue]’==‘TRUE’ && [=TN(’{REPORT TICKET COUNT:(TS.Status=Unpaid)}’)]<1

Question: Are you sure you want to END the WorkPeriod?
Buttons: Yes=y:Green;Gray,No=n:Red;Gray
AMcommand: WP End - Payout Check
BGcolor: Black
WP Ask Question

Constraint: ‘[:CommandValue]’==‘FALSE’

Question: Are you sure you want to START a WorkPeriod?
Buttons: Yes=y:Green;Gray,No=n:Red;Gray
AMcommand: WP Start
BGcolor: Black
WP Display Ticket List

Constraint: ‘[:CommandValue]’==‘TRUE’ && [=TN(’{REPORT TICKET COUNT:(TS.Status=Unpaid)}’)]>0

##Mappings##

Mappings
Terminal User Role Department Ticket Type
* * * *

6 Likes

So i am able to end my work period with tickets open in the system this is currently how my system is running. I could have multiple tickets open and still be able to end the work period. Is this default behavior? If not how do I not allow the work period to end if tickets are open?

Are you marking tickets as closed before payment accepted for some reason?[quote=“antasp3136, post:19, topic:9406”]
Is this default behavior?
[/quote]
No, default behavior does not allow WP to close if tickets are open. It sounds like your tickets are not actually open.

Well if I go to the tickets section of the pos it shows open tickets from the day and after I pay them they close and disappear from there. If there a way to enable or check that the work period is setup right?

Show your Before Ticket Closing rule. Default is called Ticket Payment Check.

Mappings are default

@Jesse found my mistake… Pre orders were allowed in ticket types. We never use this so its working now. Thanks.

1 Like

That was going to be my next question. I’ve been really busy trying to grow a new business sorry for late response.

Its all good… Just glad im finally getting to a point where i can figure some of this stuff out myself… Still needed to ask the question because sometimes im not sure if my problem has a simple solution or if it would have been more complicated.

1 Like