Continuing the discussion from [New 4.1.13] Reprinting Tickets:
Can we add note counting reprint order to kitchen
if reprint 2nd
*Note Count Reprint to kitchen is 2nd
if reprint 3rd
*Note Count Reprint to kitchen is 3rd
Continuing the discussion from [New 4.1.13] Reprinting Tickets:
Can we add note counting reprint order to kitchen
if reprint 2nd
*Note Count Reprint to kitchen is 2nd
if reprint 3rd
*Note Count Reprint to kitchen is 3rd
Yes you use a program setting to store #times pressed and print that in ticket. Use {TICKET NO} as setting name. We can delete the setting on ticket settle. I can show you in a few after I get home.
Program setting would be the way I would go, logging the ticket number and the number of times print has been done.
Kendash beat me to it LOL
Create an Update Program Setting action
Setting Name: [:SName]
Setting Value: [:SValue]
Update Type: Increase
Is Local: False
Add the action to your Print Bill rule:
SName: {TICKET NO}
SValue: 1
Add this line to your ticket template:
<J00>Ticket Copy# {SETTING:{TICKET NO}}
If you want it to show on the ticket for viewing from Ticket Viewer you can add an Update Ticket Tag action to the same rule and put {SETTING:{TICKET NO}}
for the Tag value.
If you want it to be deleted after settle and do not care if you see it in reports we can Delete the setting on settle by modifying the Action as follows.
<img src="/uploads/default/original/2X/9/994ce925053015ac77e711f8752569ee290c7bcd.png" width="417"height=“435”>
Instead of using Increase for Update TYpe set it to [:Update Type]
then type Increase for Update Type inside the rule for Print bill and create a Payment Processed rule with constraint remaining amount equals 0 put the action in there and for Update Type put Delete. Use same settings for SName and SValue as before.
can we hide
Ticket Copy# {SETTING:{TICKET NO}}
at first print order to kitchen.
shown when we clik reprint kitchen
@Johan_yo Yes use this:
<J00>[=TN('{SETTING:{TICKET NO}}') > 1 ? 'Ticket Copy# {SETTING:{TICKET NO}}' : ' ']
A lovely new feature available only in Version 5 is the ternary operator checking if the setting is greater than 1. If it is then it displays it. If its not then it shows nothing.