Ok stumped here - not critical but wish to ensure I have not missed something.
Can we issue “Close Ticket” action before “Select Customer” invokes the Search Grid?
Only 2 Events occur but are inactive.
Goal: Allow Navigation from Search Grid as this will fail if an Entity is selected.
Any thoughts.
As Emre pointed out earlier cannot do this at the Search Grid as it is not Ticket Aware.
Nope…
… you have not missed anything.
You could try automating load ticket and then close ticket but i have my doubts that will work. You would need application screen changed event more than likely
Yep been hammering that but to no avail.
Thanks guys, have the users flying in and out of Account Historys (for multiple accounts) quite well but of course it does not work if Customer Selected (ticket created).
Sad thing is the default “Account Details” works out of the box but I have removed this for consistency of work flow. Arh can’t have it both ways I guess. 
You could try automating load ticket and then close ticket but i have my doubts that will work. You would need application screen changed event more than likely
Well i’ve automated this I think. I made my own buttons and it works 
Inside or Outside of Samba?
Inside Samba, It works and I use ticket states to map the same button in the same place to do different automtion.
If you get the time, can you at least drop a GIF to show we are talking about the same thing here…ta.
Ok I need to bump this thread to see if we can find a way to Close a “No Value/No Item Ticket” before we Navigate to Select Entity Screens?
@emre - is there anyway possible to do this?
Help required…
I thought @emre explained this flow in a different thread. I swear he explained why those buttons wont work when in an open ticket.
Pretty sure its possible to do this with custom automation command flow instead of the default hard coded options your using now. We would need to work out a few things like storing ticket when you navigate away etc.
To be honest it sounds like for your custom need you really should build a custom automation command flow because of the custom nature of your setup. It would give you better control.
What is creating the ticket in the first place? Do you mean if you add something then cancel it or are you automating create ticket in previous part of the flow?
What he means is he started a ticket and it assigned an entity he is then usimg select customer to navigate to that entity screen.
Yes you are spot on kendash I was just ensuring no stone was left unturned with this and asking in case there was some action/event I did not know existed.
I think @QMcKay (as yourself) have got to the point where I need to create ACM buttons for all the Default buttons to: (1) Issue Ticket Close; and (2) Order Buttons so Select Entities are in the same sequence as Default Buttons.
Guys I was so persistent with this as the DEFAULT EDIT ACCOUNT Button can do this, so I thought there may be a hidden gem somewhere that Emre could expose - that’s all…
