Use the Action called Execute Automation Command. It has a parameter for Delay.
In your Rules for Ticket Closed event, add an action for Execute Automation Command that calls the above Action, then set another Rule for Automation Command Executed Event for that Command, and place the Logout User Action within it.
I use the delay to overcome screenswitch issue on logout, i have it set to 1 second so ticket sorts itself out then logout action kicks in 1 second later
This just delays when logout happens at the normal time ie ticket closed, i dont think there is a way it can be set for inactivity for example set at 60 seconds then touch the screen, wait 30 seconds and touch screen again to reset timer, then wait a further 60 seconds for logout to happen.
For logout to happen ticket would always need an entity assigned for the ticket to close, so a timed logout wouldnt work anyway if there wasnt an entity or ticket tag auto assigned to every ticket created
So… it works fairly well. However… there are a pile of other scenarios that don’t work, so it is not a true timed autologout. We need to take more control over what is happening at various other times. For example…
Create a Ticket, then close it, or pay it, or whatever.
Now navigate somewhere, like the Accounts screen, or the Tickets screen, or the Reports screen, or simply click Select Table (or Customer), but don’t actually select an Entity.
Sit there until the delay has passed, and you will be logged out.
Ok, so we don’t really want to be logged out at that point. We need to reset the delay (reset the timer) somehow…
I’m thinking something like Application Screen Changed Event and an Update Program Setting Action to store the delay… let me think on this a little more…