From that list if your saying to set price list for order to 2x1.
Jagermeister would change to 55 but smoothiew would remain at 60 as no 2x1 price set.
So long as you dont have other price list related actions running at same time.
My preference would be custom product tag for 2x1, fill applicable products 2x1 field with anything - say ‘Y’ and rather than specify a huge list of groups/names just have
{PRODUCT TAG:2X1} not null
{DATE:HHmm} greater 1500
{DATE:HHmm} less 1800
I use similar tactic for allot on my system, printing, package items, deals and discounts.
What does that mean?
Did you read my post?
If you changed to matches or matches any when you added all those other constraints it wont work. these would mean that either DATE would match as at any time the time will be greater than 1500 OR less than 1800. It needs to be ALL to make it only within that window, but all wint work with your specification of all those groups/names. As I said above.
Yep sorry I read it I have to translate everything ’ and I know nothing about computers and programs so please be patient… last time I try to use that I maded a mess …
Hi guys! I’ve done this setup and, supossedly, it works, but it only works in single terminal where it was done, as well as server, however three other terminals dont ring up HH discount. I have a small restaurant, and just started to do our Happy Hour. I have checked over and over setup, but cant figure out whats wrong. Is there anyone out there who would give me some kind help.
Hi! I did my setup on Friday, shuted down all terminals at night’s shift end, then, next day, started as I would regularly do. Happy Hour was supposed to launch later, but was never able to do so… so I had to manually change price to each item, such a trouble going into every ticket, as we have around 40 tables… got any other idea, what could be the issue?
I finally figured out: turns out my server and terminal where doing automation have both windows in english, and all other terminals have windows in spanish, since I live in Mexico…
So I went to Samba and just clicked on “override windows regional settings” and, that was it, finally got it to work… It seems quite strange, but somehow it worked.
Use a global program setting, update it with a toggle automation command for say ON/OFF and change daye/time rule constraints for program setting equals ON.
Make an automation command button, for happy hour,
put ON and OFF in the values box and select toggle.
This will make the command value toggle each time the button is pressed.
Then make an automation command executed rule for the command name of that button and use the command value for the value of the program getting in an update program setting action with global set to true and setting name of say ‘HappyHour’.
Then in HH rule where time constrints were origionally change the time and date parts to just be {SETTING:HappyHour} equals ON, where HappyHour is the setting name set above, to call the current value from the program setting.
