But what about cancel or void?
Or +/- qty, or is x2 added depending on if you have numberpad etc
If nothing else you need to add thinks like GStatus= so void and gift prders arnt counted
As above this would be in both sences of not counted voided orders and also how to amend previous orders if one of 3 is voided or cancelled etc
Holy rapid-posts Batman. All good points. It definently needs further work.
But what I have done few times I have used is to not use event like order added but put my promo automation in an automation command rule that way the automation can easily be triggered from a bunch of different events with execute automation command such as, order added, cancelled voided, etc or possibly just of ticket total changed.
However not sure about your deal since your using order name dynamically rather than a fixed value like a promo state etc and automation command wouldnt have a menu item name to call on.
But if you did so with automation command rule and execure from rules like cancelled, voided, etc you could pass menu item name as the command value and use command value in place of menu item name.
Did you only have one portion for wine by glass?
Not tested yet but think that could work nicely.
As I said though, this action causes some unexpected results on print template in relation to order total and tag values when doing multiple qty on order lines - or at least when I brought the issue up a while back.
Calculates fine, onscreen and accounts are fine, think it is/was a bug just in the print rendering, so check outputs to make sure get what you expect. specificly on multiple qty lines.
Beleive its because it uses a special value in tag json TV rather than TP or something like that, guess value rather than price.
However the built in automation within the action is pretty good and allot easier than trying to catch all eventualities with seperate custom automation.
Haha, I did not think its going to be easy as that, at least I am on the right track now, time to get back on the drawing board and consider different scenarios
I used Update Order Gift state action cus I was in testing, I didnt really think of using that one, Ill probably go for a different one unrelated to GStatus but have to see which is easier and doesnt require too many new buttons just to cancel/void etc.
I think Void doesnt work on New
items so as long as they are new it should be easy to cancel.
As far as the Submitted
go, they will be easy to Void. Even if they are Gift as they belong to same GStatus group, one will replace the other, however, that sets ODI to false so simple (ODI=True) should suffice in the constraint.
They are not using numberpads and quick qty are disabled for Wine categories, so they have to click on products as an agreed method of use. +/- they wont have access to either, well, service staff wont. Alternatively, I could Lock 3rd order that was updated as Gift, or go as far as locking the whole trio.
Bottles are 2 for 1 too but they are a separate product, I separated them at the beginning because I knew I didn’t want to check for portion names as well. However, (MN=[:MenuItemName]) sorts my problem of having to have wine in different group codes.
{TICKET ORDER QUANTITY TOTAL EXP:(ODI=True) and (MN=[:MenuItemName]) and (OS.GStatus= )}
I think I will have to use this one instead, mainly because after you close the ticket it will merge all GIFT & billable products into one line. And ORDER COUNT checks for order lines instead of qty.
From memory if you have tag as not included and not sistributed it won’t merge as tags would have different values.
@Jesse do you know whats the syntax for this expressions field in Select Orders Action? Its kind of semi-working, not sure which one of these expressions its picking up on
It was released back in 5.2.14
Whats the event?
Expect its the MN part if your having issues.
Automation Command Executed event while the order is selected. Its almost as if expressions are doing only OR operation instead of AND. Because it does what its supposed to do but only when any one of these expressions is valid.
Predictable sugestions if not already, show message with those values to make sure expected returns.
When you say semi you mean its semi firing or semi selecting?
Whats %, i mean I know what your doing but not done that before and intregued on exactly what its doing?
Basically I am automating Cancel Order. Its just extra quirks I want to polish out because I am too stubborn to let it slide
When you order
-
1 x Glass
-
1 x Glass
-
1 x Glass FREE
So if I cancel say 2nd one, its supposed to automatically select gift one and update gift to null.
So then result would be
1 x Glass
1 x Glass
Well the whole thing works when any of the expression is True.
This is my expression…
(OS.Status=New) AND (OS.HHNumber=0) AND (MN={PRODUCT NAME})
BUT it behaves like its this, which is why I asked Jesse, maybe I am using wrong expressions or something.
(OS.Status=New) OR (OS.HHNumber=0) OR (MN={PRODUCT NAME})
@VehbiEmiroglu could you please tell me whats the right syntax for Select Orders Actions in the Expression Field
What happens if they have 6, 4 and 2 gift, and cancel one of paid ones?
Thats why I put to cancel just the New one, but it doesnt listen to the expression, it removes gift state to a Submitted order.
Say on ticket there is:
1x Glass Submitted
1x Glass Submitted
1x Glass GIFT Submitted
1x Glass New
1x Glass New
And I cancel last one, it will update GIFT order even though its submitted because its not listening to (OS.Status=New) expression.
It has a brain of its own haha
I think I hit a snag that wont go away without help from Devs, so for now I will put this cancelling thing for later and possibly use Adjust Order Price action.
I came to a point where I am putting in too much time into reinventing the wheel
Thanks for all your suggestions and help, if you want the DB and want to try it out yourself just hit me with a PM.
P.S. I might actually send you a message to give me some help with that Adjust Order Action if I hit another bump down the road.