Totara Learn Open Discussions

System time out behavior

 
? ?
System time out behavior
par ? ?, Friday 20 July 2018, 08:34
 

Greeting everyone. I've got a scenario that I'm either looking to see if its addressed in newer versions or if anyone has a solution. Here's the gist of it. We have a large account that uses Totara to deliver training to different accounts so they need to keep the users from each org separate. Its a typical multi tenant scenario. They want a leader from one account to be able to run reports on the users from their org. They have setup custom reports using filters and then have hidden the filters using the theme so the customers can't alter them and stumble upon other users. 

It seems that the filters are handled via codes in the url string. So, if you access a particular report, the report filter ID is added to the url string and the report is then limited. As you work with the report by doing things like clicking on column headers, the original ID disappears and probably gets saved in the general login cookie. It then gets replaced by other codes that indicate the column being sorted. 

We had a situation where a customer ran their report and then stepped away from their computer without shutting down the report page. They came back 5 hours later and clicked on a new column header. They were timed out so the system took them to the login page, but it remembered the page they were trying to access. When they logged in they landed on the report again, with the sort they had clicked on applied. However, the saved search id was not present and since it was a new login session, it was not remembered. They essentially re-ran the report and it now showed every user in the system.

This caused quite the problem. Our customer is wanting to know why when a user times out, the system doesn't just shut down the page and take them back to the main login page? Is this something that is maybe new behavior in newer versions? If not, can this kind of thing be added or is there a plugin that will do it? They essentially want the same behavior you would see on a bank site. When it times out, it just reloads your page to the login screen. 

Any feedback would be appreciated.

thanks

Matt

? ?
Re: System time out behavior
par ? ?, Wednesday 25 July 2018, 05:57
 

Hi Matt - not sure what version you're on, but the original issue of restricting reports to a user's own organisation is probably best solved in a different way.

If you set up organisations then you can use the 'content' tab of the report to restrict whoever has permission to run the report (see 'access' tab) to only see data from their own organisation.