First problem I have come across is that I can’t seem to get multiple states to work for Order State. I have tried separating the states with , and ; and it will not match. Also if the state has a space in it like ‘New Order’ it will not match.
While this is not a huge problem it has caused a re-think on my workflow - which at this point is not a bad thing.
Secondly, and probably more important is that when a Ticket State matches the Ticket Lister Widget but the Order State does not, the Ticket is still displayed (without any orders).
In theory you will not just list orders without ticket information, therefore I think that if only a Ticket State is set, then show the Ticket. But if an Order State is also set then both States must match to show the Ticket.
Second one is a great idea. Yes If there is no order that matches order state it might be better not to display ticket at all. I’ve changed it for next release.
I’m not sure why it does not matches if there is a space. That might be an encoding issue because I’m reading raw data for faster querying. I’ll check that.
Supporting multiple states is something we shouldn’t need on workflow based operations. If really needed we can talk about it through an example…
Doesn’t it make it harder to manage? I assume you’ll need a lot of future features to match commands to states. Maybe you should display multiple ticket lister widgets on same screen…
Hello, I’ve implemented comma separated multiple state support for ticket lister widget. It will be available shortly with 4.1.29
Wildcard support is something we shouldn’t implement since SQL Server does not support some needed features so I need to fetch all tickets to test. However if needed we can implement it for order states.
John this is not an easy task because we need a custom expression parser to translate expressions to code. Maybe we can implement specific settings for dates but as I can understand you mean something like rule expressions.
I get that it’s not easy due to the requirement of a parser.
So instead of modifying the current ticket lister, how about a new one specifically to list tickets with a state within a given date range ? And the date range will need to be dynamic, ie Today, Today+1, Today to Today+7, etc
I know this is bordering on reservation style requirements - actually it is reservation style
And we would also need a Date Picker for an Automation Command or Ticket Tag.
OK That was easier than I thought. At least SambaPOS infrastructure permits such modifications. I’ve added support for easily typing date expressions as TicketDate is Today+1 or TicketDate > Now. It supports much more than it seems so you can just ask me how specific filtering expressions (not wildcards :)) can be written…