5.1.38/39/40
Save Ticket Action
I’ve radically changed how we save Tickets to detect some rare multi terminal issues . With that change I’ve also implemented Save Ticket action. That action will persist ticket to database and read ticket’s latest state from database. You can use it to save new tickets to update ticket ids, save moved tickets automatically or refresh tickets inside rules. I’ve basically implemented it to call it before printing tickets to ensure we’re printing latest version of ticket. Not essential but if you have automation rules that may change tickets from other terminals (for example if kitchen may change ticket’s tags or states while ticket is open on another terminal) you can use it to ensure a final refresh.
###Custom Report Expression Syntax improvement
We already support two summary expression syntax. Third one is new.
[T.Field1.Sum]*[T.Field2.Sum] Multiplies Field1.Sum by Field2.Sum.
([T.Field1]*[T.Field2]).Sum Sum of Field1 * Field2.
[([T.Field1]*[T.Field2]).Sum]/[T.Field2.Sum] Divides sum of Field1 * Field2 by sum of field 2.
This syntax will allow us to use an summary expression inside a summary expression. You’ve noticed that will be useful to calculate weighted averages.
###New Ticket Creation Method
A new Ticket Creating Method implemented for departments called Ticket Selection. Might not have a wide usage but that was a nice V2 feature. It basically uses Ticket List View as primary view. Useful for small venues that have 5~6 tables but does not need table based tracking. It will list open tickets for the department. You can click a ticket to display or use menu buttons to create a new ticket.
Terminal and Product Tag mapping for print jobs.
I’ve noticed mapping products to printers by product group is a lot of job especially if you have many product groups. Now you can Create a product group for printing and map products by custom product tags. Mapping to terminals is also added so you won’t need to create multiple rules for each terminals for terminal based printing.
Payment Descriptions
We’ll be able to store cc info within payment. That will be displayed on settle screen and new printing tags added to print that info on bills.
Decimal Places
We’ll be able to change stored decimal places count on database and also displayed decimal place count on screen.
Order Tag Improvements.
Rate-based Order Tag Calculation
Rate based order tag price calculation and order tag formatting feature explained here. [New 5.1.38] Rate based Order tag Prices
It is amazing to see how much people uses order based discounts. In our country it is generally ticket based. For some places a different price list does the job for most cases. I still don’t know if it is a killer feature o not but I’ve added rate based calculation for order tag prices.
Rate based order tag price calculation is cumulative. I mean sum of order’s price and other order tags before rate tag used for calculation. So placing discount tag to last place on order tag group list will use other order tag prices while calculating price. Adding, removing tags, changing order quantity or price will also update amount.
That will have no connection to accounting but we can still use order tag template tags for reporting or printing needs.
I hope that will help order based discount or servicing amount implementation.
Order Tag Description field
Additionally Description field for order tags added so you can use that field for adding more info about order tags. For example you can store second language names here and use them for kitchen printing.
Related actions and printing tags also improved to support these features.
Order Tag Group Formatting
Inventory Reporting tags
{REPORT COST:X} To read cost for product X. Use <ProductName>.<PortionName> syntax as X.
{REPORT CONSUMPTION DETAILS:X} Reports inventory item consumption details.
{REPORT COST DETAILS:([^}]+)} Reports product cost details.
For people who loves to use SQL we’ll also start storing average product price in [CostItems] table so you can easily calculate profits.
You can check database field names to get a hint. We may provide additional values.
For example Report Order Details supports T.x or O.x to read both Ticket and Order values. For Inventory, try these:
C.StartDate
C.EndDate
C.Name
C.Unit
C.Inventory
C.Warehouse
C.Consumption