Think you can just setup a new rule for order added to ticket
Set custom constraint as { ITEM TAG:Main } greater than 2
Add your print job that you want to print
So when you add two orders where their product tags are both Main it should print your print job
or maybe actually do it in a ticket closed/closing rule with remaining balance equals zero so it will only print was ticket is paid, otherwise as soon as you add the two orders the order added rule will print your job. Which then leaves a possible misuse issue where the orders are then removed so potentially discount vouchers given out with no actual order made
I dont think that would work as order added would only relate to that addition, a report expression will be needed.
You would want to use a report expression to count the orders of specific condition and use this number as a constraint.
Your ‘trigger’ would most likely want to be on ticket closing with constrains similar to the final payment ‘mark ticket closed’ rule so remaining balance < 0 and total > 0.
So on ticket closing rule
remaining balance <0 (ticket has been paid)
ticket total >0 (ticket had a value - ie not a all void ticket)
report expresion to count main orders > 1 (2 or more)
Simply when an Order is added to a ticket they are tagged with MAIN, STARTER, DESSERT etc so that the kitchen print out is put in the right order.
All I want to be able to do is when my Waiters click print bill the System works out how many mains have been sold and if its greater than 2 execute a print job that prints a free meal voucher for the next day.
Ive tried so far {ITEM TAG:MAIN} Greater than 2 as explained this does not trigger the rule.
Ive Tried {ITEM TAG TOTAL:MAIN} Greater than 2 this also doesnt trigger the rule.
I do not understand the report expression method that JTRTech mentioned.
Am I running along the right lines or is what i want a rather complicated process.