Happy hour ticket template

Exactly correct. The Time constraints are useless in this case with Matches.

1 Like

I agree. I believe the definition of the State is what is making this not work. I think removing the State will fix the issue.

@QMcKay @Jesse No the problem is that the {TIME} constraints are not working somehow , when i remove it the hh appears on the bill, so i dont know what to do , in the happy hour triggers method the time triggers works perfectly and i can change the price List to hh but the rule with the trigger executed event doesn’t seem to have an action based on “update order state”, the only event that accept the update order state action is the “Order added to Ticket” event

So I can have to working rules, one using the “trigger executed” event to set the happy hour time and change the price List and the other using the “order added to ticket” event to update the order state so it can appear on the bill

So is there a way to relate these two rules so they can work at the same time? thank u

Start from the beginning
 your using triggers plus this method?

The setup posted by me does not use Triggers, and it does not use Price Definitions either. It uses Order States and Order Tags to apply discounts.

From the sound of it he has ended up with a miss match of the two methods


Well yeah but the {TIME} before and {TIME} after constraint are not working in my setup, thats why i switched to the trigger method and it worked but i just need to show the hh letters on happy hour orders on the bill so i used an action to update the order state to hh but it cant work with the same rule of the triggers, so im just asking if i can let them work together, the rule using trigger executed event and the other rule using the order added to ticket event

There is always a way LOL but triggers are timed changes, not a time range, you would have to do something like setup a happy hour program setting change on the triggered rules and then use that program setting as a constraint on your HH tags/state (order added rules) bit of a round about way when the time constraints would be allot simpler.
If the time constraints didn’t work it would have been an error somewhere in the settings as is a tried and tested method.
Did you change to MATCHES ALL like @QMcKay said?

@Comfnmb can you show your rule where your using {TIME} it does work I use it every day. You must have configured something wrong.

@Jesse, @JTRTech those are my update order state action and rule:

Where it says Execute rule if: Change it from Matches to Matches All see if that fixes it.

Also it should be 12:24 and 12:45 you must insert the : I know that was my fault in the tutorial I gave you I will fix that.

EDIT: Fixed my original screenshot sample.

4 Likes

@Jesse yeah it works now! It was the missing : that was stopping it, so now its working! thanks a lot and i appreciate it!

1 Like