I showed you my setup, cost me $50 and was easy. I wasnt worried much about security just as I trust the staff, and they need to use it correctly to give customers recipts.
1 Like
@the133448 thanks so much. You’re a big help.
So getting back to the original topic, can anyone help me link in the print bill automation to this AMAZING new auto log out feature we have setup. As I’ve said before the ALO we setup is linked in with “close ticket” action and by default print bill was as well but I removed that and don’t want to readd it. So how do I get this feature to work with print bill as well?
Use the same Actions that are in the Rule called
Rule - Application Screen Changed - AL Screen Change
But in your new Rule…
- set the Event to
Automation Command Executed - add a Custom Constraint of:
Automation Command NameEqualsPrint Bill
1 Like
I didn’t see any rule called “Application Screen changed” I didn’t create it, or the tutorial I followed didn’t require it. However I made a clone of the ALO rule which had the ALO action tagged and as a constraint it was set to automation command ALO as posted in the tutorial. I tried adding bill print in as you suggested but if we’re still on the ticket screen it won’t auto log out. It logs out after 20 seconds of inactivity after transitioning from the ticket screen to the pos screen. But as long as it’s on the ticket screen it won’t log out. Remember I said I removed the “close ticket” action from the bill print rule, this is necessary. So the ALO only activates if we use an automation that returns them to the POS/main menu. So since print bill doesn’t change screens it won’t auto log out. How do we get this ALO to work if it’s still on a the ticket screen? I think all automations return to the POS/main menu except Print Bill so thats what we need to focus on. I could always return the close ticket action to the print bill rule but I don’t want to do this. I removed it to allow easier/faster splitting of tickets becsuse it kept returning them to the POS screen every time they would split and print. And having to do this more than twice can get old fast. So any ideas? I know there’s not a way to make it auto log out no matter what right? Say they logged in and didn’t do anything then walked away, it would be nice if I could set a 20 second timeout no matter what instead of it being triggered by certain automations.
You cannot logout if the Ticket is Open. You need to close the Ticket first.
So maybe if you don’t want to have Close Ticket Action in your Print Bill Rule, then put the Close Ticket Action inside your Logout Rule just before the Logout User Action.
1 Like
How about adding a delay to close ticket and then readding that to print bill? Say after 10 seconds of the ticket still being open after bill print is done if no other selection is made the ticket is closed then that should trigger the ALO after 20 more seconds. The ALO wont happen unless the close ticket action is performed but remember I don’t want it to return to the pos screen immediately after bill print so I removed that action from the bill print rule. So what about readding that but with some kind of delay?
just giving this a bump 
See, that is the beauty of SambaPOS. You can make it do just about anything you want. You have different alternatives, depending on your desired flow.
Without seeing exactly what you have currently implemented, it is difficult to suggest what you should do now.
My suggestion assumed that the Ticket was still in view after Print Bill. If you put a Close Ticket Action in your Logout Rule, you always ensure the Ticket is closed before Logout is performed. It won’t hurt to put it in there anyway, even if there is no Ticket open in the first place.
1 Like
Can I record a video and upload it to youtube then post the link. I figured a video would be good to show you what I’ve got and maybe it will give a better idea on what I want to do and how we can get this working the way I want.
Sure a video is fine.
But you should post screenshots of all the elements (Actions, Rules) of your implementation so we can see exactly what you are working with.
Took me a few days to get it but here it is. Please excuse my silly accent, my rambling, and my big belly at the end of the video lol.
https://vid.me/mEJV
…
So set your department to create ticket mode. Use custom navigation to remake your pos button that actually takes you to table screen instead of pos. You select a table it goes to ticket screen if you close ticket it stays on ticket screen.
I have no idea if that solves anything because honestly your video was very difficult to follow. I still don’t even know what your asking.
I don’t know how to be any more specific. I said it firmly pay attention to the last few minutes of the video. I’m trying to set it up to where the close table action happens when I print bill but not immediately say on a 10 second delay. That way if they print bill they don’t have to click close it will close for them. I don’t want it happenin automatically I want it to happen on a delay the same way we set up auto log out with a delay I want a delay on the close ticket automation if thats possible. I just need some way to force them to leave when they click print bill. I have the close ticket action removed from the bill print rule bc I don’t want it to immediately haplen. I want it to happen on a delay.
Then create an execute automation command action set a delay in it and put that in your print bill rule. Create the automation command executed rule for that command and put close ticket action in it.
Sounds simple enough I’ll try that and see how it does.
1 Like
could you re upload the video please?
Depends on your setup.
There is an autologout option in terminal settings which logs out the the user once ticket is closed…
If your setup is more complex you may need to use the close ticket and logout user action in your automation.
A video will not help much as that type of this is very setup specific if the autologout feature is not correct for your needs.
just need and autologout actions or rule or whatever method it can be used to autologout after X seconds in inactivity.
X seconds of inactivity is a whole other ball game… Due to senarios where it is not possible to close the open ticket, ie added orders but no entity or ticket tag.
Have you tried the autologout tickbox in terminal options?
The next user would need to close the ticket anyway if previous left logged in as they would need to start a new ticket.
im aware of that, i haved think that it could only be applied to the entity screen no matter if there are open tickers and the navigaton screen in any other screnerio the rule can not be applied.