Get Fast Payment Buttons, help setting values?

Isaac · February 12, 2014, 5:03pm

ha ha, thanks Emre nice one.

JohnS · February 12, 2014, 5:04pm

Isaac,

Create Rule Name - Ticket Total Changed
Event Name - Ticket Total Changed
Action

Update Program Setting, SettingName = TicketTotal, SettingValue = [:TicketTotal]

Update your Fast Payment Rule, and add the following Custom Constraint
{:TicketTotal} Less [:CommandValue]

That will fix it.

JohnS · February 12, 2014, 5:06pm

Emre,

Will we be able to retrieve [:ProcessedTotal], [:TenderedAmount] & [:ChangeDue] for Automation Command Executed events ?

emre · February 12, 2014, 5:07pm

We’ll send tendered amount to “Pay Ticket” action and handle “Payment Processed” event.

emre · February 12, 2014, 5:19pm

@JohnS and @Isaac thank you very much helping me on this nice feature. That was real Fun! While you were talking about it I’ve made changes. I’ve uploaded new version.

By new version Pay Ticket action supports Tendered Amount value. Execute this action from automation commands with Tendered Amount parameter and handle Payment Processed event to update Shell Title.

Isaac · February 12, 2014, 5:46pm

John how we going to do what Emre just said?

emre · February 12, 2014, 6:00pm

This is my test database http://sambapos.com/?wpfb_dl=14

Please check how I’ve implemented Automation Commands, Pay Ticket Action and Payment Processed Rule.

Isaac · February 13, 2014, 10:54am

Hi Emre,

Thanks for attaching your test database, I now have this working as expected and tendered amounts are now displayed. Is it possible to set the change due to 2 decimal points. so instead of displaying 4 it would look better if it displayed 4.00? see pic:

JohnS · February 13, 2014, 10:56am

Use this for Tendered Amount

[=FF(’[:TenderedAmount]’,’#,##0.00’)]

Isaac · February 13, 2014, 2:58pm

Hi John,

Unfortunately this did not work:

Tendered:|[=FF(’[:TenderedAmount]’,’#,##0.00’)]\rChange Due:| [:ChangeAmount]

emre · February 13, 2014, 3:00pm

I think you want to format change due instead of tendered amount.

Isaac · February 13, 2014, 3:06pm

Well Spotted Emre, I used:

<J>Tendered:|[=F('[:TenderedAmount]')]\r<J>Change Due:| [=FF('[:ChangeAmount]','#,##0.00')]

Big Thank you to JohnS as well.

JohnS · February 13, 2014, 9:50pm

You may be right Isaac
Mine needed tendered formatting.

Isaac · February 17, 2014, 3:02pm

@Emre and @JohnS

Guys I think we missed adding some actions to the rules regarding Ticket States. Because any ticket settled as Fast Payment is currently not updating the Ticket Status:

JohnS · February 17, 2014, 3:04pm

You need to refresh the ticket after payment.

Isaac · February 17, 2014, 3:14pm

Yes I did John, once it was settled I closed the tickets and re-opened it from the ticket module. I’m just trying to figure out what actions I need to add to the rules.

Isaac · February 17, 2014, 3:31pm

Settled Tickets are also shown as OPEN tickets instead of Closed?

JohnS · February 17, 2014, 3:32pm

Add Close Ticket to Fast Payment Automation Button Rule.

I just tried refreshing the ticket, and the status will update but you can add more orders to the ticket.

Isaac · February 17, 2014, 4:55pm

@JohnS I now added the close ticket action to my fast payment rules. However for some reason although the tickets are settled and closed, they are appearing as OPEN in my ticket module?

In fact, any ticket created and settled in my Take Away Department, is all showing as OPEN. hmmmmmmm

emre · February 17, 2014, 5:04pm

Ticket Payment Check rule is responsible for closing paid tickets. Check if there is a department specific mapping for this rule.

This is not hardcoded and executed by rule because in some cases restaurants wants to keep tickets open even it gets fully paid since customer still sitting there.