I have multiple ticket types,Layaways, Quotes and the default ticket type set to Receipt.
If I no open Receipts selecting a customer brings me to new ticket.
If I have 1 open Receipt selecting a customer brings up their open ticket.
The problem I am having is when there are 2 or more open Receipts the default ticket lister brings up all open tickets belonging to that customer.
Quote and Layaways are ignored when there are less than 1 open receipt, Why does it include them when there are more than 2 open receipts.
In screenshot below
172 is a Quote
173 is a Layaway
179 and 180 are Receipts (I want to merge these but with all the other tickets displaying it can become confusing for staff)
I know I can filter by ticket tag name and ticket state name using automation but I was wondering if its possible to modify the default ticket lister.
Not sure but for starters why not add a tag for layaway and preorder as part of flow so that at least those tickets are marked on the lister as tags are shown on ticket list…
That’s actually an excellent Idea I never thought of that. Thanks.
The only issue I could see with that is some trade customers could have in excess of 100 quotes which would mean the newest orders are at the bottom and Staff would have to scroll down to find the orders. Not a massive issue but a bit of an inconvenience. Is it possible to flip the sorting on the ticket List and show latest ticket at the top? Its looking like it will have to be done via automation.
I dont think there are any options for the automatic ticket list for multiple tickets on an entity just on the show ticket list action.
HOWEVER you could posibly put together a custom flow for showing ticket list and not use default.
Ie, just use entity grid and constrain the actions from entity grid automation command based on a report expression counting number of tickets (ie no tickets = create ticket and set entity, 1 ticket = open ticket, more show ticket list with filters as required?
On Entity Selected Event I have a rule fire to show all the entities tickets with a status of Unpaid.
This rule is constrained with [=TN(’{REPORT TICKET COUNT:(TS.Status=Unpaid) AND (TEN.Customers=[:EntityName])}’)] >1
Which takes me from this
To this which is what I want but now the MERGE button is gone.
Think this will be because behind the scenes you have created a ticket…
Your select entity event relates to a ticket having entity selected…
The sugestion was not to use the default entity grid screen but automate what actually happens when presing the button ie selecting an entity is not what it does, it goes to your rule which works our wether to select entity, open ticket or show filtered list based on report like that and the count.
Check your ticket numbers, or create a show message on ticket created event to see if tickets are being created.
Pretty sure merge isnt there because you have a ticket open in background.
The inherent problem with that, as you can see, is that the button is disabled. I believe this is because no Entity is actually selected in this case. If you feed the Entity Name into the Action, I would guess that the button will become enabled.
If you Select an Entity that has more than 1 Ticket, that list is displayed and the button is enabled…
But the button does not do anything yet, so you then need to manually build the Automation for Merging Tickets when you click your button.
Remove all the Show Message Actions (MSG TEST) from the Rules when you are confident everything is working properly and it will be a seamless operation.
you could posibly put together a custom flow for showing ticket list and not use default.
