Print Template missing tags

[JohnS]

You got me interested in solving this one, as I too should have tendered and change due on receipts as that's what a customer expects to see.
So I set it up earlier to test it, and we were on the money.

Reset TENDERED & CHANGE DUE on CREATE TICKET .
On CHANGE AMOUNT UPDATED Rule set TENDERED and CHANGE DUE to TenderedAmount & ChangeAmount
Then check TENDERED on PAYMENT RECEIVED and if 0, set TENDERED to AMOUNT
Plus the 2 Actions for updating Tendered & ChangeDue

With the Pole Display I didn't need the first or third settings.

Simple now 


Splitting checks is not popular in Oz (in fact its discouraged), this feature just helps the operator think quicker. The receipts print the same after the first amount is paid, no matter what else gets tendered. My solution would be if the bill is split evenly, then take the first amount, hit Print Receipt x3 and take the remaining money.

I tried some Rules to update Tendered, but wasn't successful.

Maybe Emre can clarify this, as I am sure it will come up elsewhere.

[JohnS]

Emre,

Now that we are so cool having Tendered and Change on the printed receipts

I have come across an issue. If you reprint a receipt, the Tendered & Change amounts are from the last sale - not the actual sale for the receipt you are printing.

[emre]

I think we (including me) shouldn't forget this nice SambaPOS rule.
"If we need to track additional info about tickets we should use Ticket Tags"

We can pretty use "Update Ticket Tag" action for storing tendered and change due amounts on individual tickets and use {TICKET TAG:Tendered Amount, Change Due} tag for printing them on the bill. So we can see these amounts on tickets too. Like The example we can print multiple tags at once by merging them with comma.

The only issue with Ticket Tag printing is we can use {TICKET TAG:x,y,z} tag only once so if you'll need to print additional tags you need to include them in a singe tag by separating them with comma. I changed it like we did for {SETTING:xxx} tag. You'll receive it on next update...

[JohnS]

I think we (ME!) need to get more creative with the solutions

You don't think of using the unique feature of Ticket Tags for things like change due amounts.
What drew me to SambaPOS was the fresh approach to a POS solution and the unique features it offers, and I know I need to exploit these features more.

Ok, so I have given it a go, and got it to work.

Emre, will the formatting be available to Ticket Tags just like {SETTING:xxx} Tag? During my tests I get this result

Tendered: 5.00
Change Due: 1.80

If I use <J>, <R> or <C>, first line does what its told, second line is left justified.




"To be a Programmer, you need to know what a box is.
To be a Creative Programmer, you need to know how to get out of the box!"

[jenem]

Hi John,

(or Good morning from Wales)

I dont quite understand what you mean.

 When you reprint a old receipt. If I select a old ticket and select release lock and select print ticket the receipt prints ok.

The receipt shows the amount tendered, change given etc.

If I generate a new sale the receipt shows the correct value ie tendered value, change etc for the new sale.

Edgar

[JohnS]

Edgar,

That's what I thought until I added the change due to the ticket amount and didn't get the tendered amount on old ticket reprints.

Using Ticket Tags has fixed this for me as the Tendered & Change Due amounts are saved with the ticket.

[emre]

Hello. I've just uploaded 2.81...
You'll be able to use {TICKETTAG:xxx} (not TICKET TAG) for fine formatting.

[JohnS]

Thanks Emre.

[jenem]

Hi Emre,
I have tried to use the TICKETTAG setting but I dont quite understand how it works.
I have Set up a TICKET Tag named TEST and added CHANGEDUE and TENDEREDAMOUNT to ticket tag TEST (Not sure what settings to use in Ticket tag.

I tried adding TICKETTAG setting to print template but was unable to store change and tendered amount with ticket.

Have you any procedures to set up Ticket tags? I have looked at Setting Waiter and Tips using Ticket tags but storing change with ticket is a different application.of Ticket Tags

If I figure it out I'll post later.

Edgar

[JohnS]

Edgar,

- Create 2 Ticket Tags - Tendered & Change Due. Click Free Tagging and type Price
- Add them to the departments
- Create 2 Actions, 1 for each Tag, set the name, but use [Setting Value] for Tag Value
- In your rule for Change Amount Updated, add the 2 Actions above using [TenderedAmount] & [ChangeAmount]
- Set a new Rule on Payment Received (if your haven't already) with Setting TENDERED=0.00, use both Actions above, setting Tendered to [Amount] and Change Due to 0.00

Use the following on your receipts

<J00>Tendered|${TICKETTAG:Tendered}
<J00>Change Due|${TICKETTAG:Change Due}

Does this help?

[jenem]

As ever John, Thanks will try out later.

Just going out to repair a compressor

Edgar

[emre]

Hello John and Edgar...
Since Update Ticket Tag action works like Program Settings there is no need to pre-define ticket tags.
It is useful if you want to have side buttons and want to see these tags on reports.
Thanks...

[jenem]

Hi Emre,

Quote
"Since Update Ticket Tag action works like Program Settings there is no need to pre-define ticket tags.
It is useful if you want to have side buttons and want to see these tags on reports. "

I don't quite understand what you mean.

Do you mean you do not have to create a ticket tag to use TICKETAG on the printed receipt?
Do you have to create different rules/actions to the ones we created for Change Due, Tendered etc?

I just tried to replace SETTING with TICKETTAG but results were 0, and 0 in amount tendered and change.

What are the benefits and application of using TICKETTAG?

Thanks

Edgar

[emre]

Yes, if you use actions / rules for updating ticket tag values you don't need creating Ticket Tags.
You can update CHANGEDUE ticket tag value with Update Ticket Tag action and print its value with {TICKETTAG:CHANGEDUE}. Program settings are global values but Ticket Tag values stored in ticket header data...

For example you can store "Waiter = Emre" value on a ticket and track which waiter received that order .. You'll need buttons for choosing a waiter. For this reason you'll create a ticket tag group and enter waiter names as values. But for storing ChangeDue = 2.45 we don't need a button because action will do it automatically for us when payment screen generates a change due value. Since these values stored with ticket data reprints will work.

[jenem]

Thanks Emre,

"Waiter = Emre"

It should be me waiting on you for all your hard work !!

By the way found Turkish text in red while creating department

Edgar