Sorry for all the questions.
I’m using the basic clocking in system, so staff are assigned to tickets via employee entity to track clock in/out. The downside of this is staff can now press close to close ticket without payment as the Employee entity is assigned to the ticket.
Is there a way of disabling Employee entity from being able to close ticket without payment whilst leaving this option open if customer or table entity is selected?
Thanks!
Jesse
June 19, 2018, 9:55pm
2
You can change mapping of Close Automation Command to work only if Status=Paid. But that could cause other issues depending on your setup.
BTW: The ticket is not really closed it remains in open status. You can access it from Entity screen or tickets module.
A better thing to do is train staff how that works. Since you assign people to tickets it would be really easy to see who has unpaid tickets.
Thanks Kendash, I think i’l change the close button to a log out button and add a park order button for suspending a transaction as a workaround.
Take a look at this;
Uses: Ticket Tags, Report Expressions, Ticket List, Ask Question
This will likely end up as a mini series of 2-3 videos of the process of creating a new layaway/switch user setup.
I have purposefully not rehearsed and only refer to a previous setup for rough reference as this is a new configuration I have made to hopefully be an improvement on my previous switch user setup. I believe that a few videos of this style will be beneficial for newbies in that its not always a straight obvious answer…
You may be particularly interested in the prompt when user logs in next to tell them they have layed away/parked ticket…