Skip to main content
Skip table of contents

(06.24.02-00) Session Timeout

Content was last updated in 06.01.13-00

Revision History

  Version No.

  Reference No.

  Changes

R2-16779

06.01.13-00

Browser session timeout

Imagine this — You are talking on phone with someone, it is a free-flowing conversation, and without you knowing the line disconnects, but you still keep talking at your end. By the time you realize there could be a lot that you would have said. Now, that is a loss of information at the least; because when line re-connects you will have to repeat everything.

Until now, something similar used to happen in R2, when you had un-saved changes in your login-session and you terminated the session without saving the changes. As obvious, your changes were not acknowledged by the system, and there was no notification about it. Evidently, such problem led to a lot of ambiguity in business processes.

Thus to address the above issue and safeguard you business — We have introduced some functional improvements, notifications messages, and UI elements.

 This feature is applicable only on transactional/ editable interfaces such as Planning Order, Whiteboard, and Graphical Scheduling etc. 

Key benefits:

  1. Prevents any user to hold on to any order perpetually, there by making business operations more flexible.

  2. Maintain data integrity across multiple-user sessions and multiple users as well.

  3. Allowing seamless data portability between R2 and R2 Labor.

 

Functional Improvements

The key safeguard implemented as a solution for this issue, is a 30-minute default 'Browser Session Timeout' window.

These 30 minutes are further split into two sessions. After an intial 25 minutes of inactivity, the system begins a 5 minute countdown, along with displaying a prompt for you choose to stay connected. If you chose to accept, the session timeout is reset for another 30 minutes.

Countdown timer Ends for Session timeout

However, if you do not take any action on the above prompt, once the final 5 minute countdown is lapsed, system disables the session, and the only action possible for you is to close the brower tab.

Upon session timeout, we ask you to close the browser tab and do not sign you out; becuase if we sign out from this inactive session you will be eventually logged out of all your active sessions as well. 

To see the Notification Message, follow the Workflow below

  1. Open any Order in Planning Order, make some changes to it, but don't save your changes.

  2. Leave the browser tab un-attended for 25 minutes for the timeout to get triggered. After 5 minutes close the browser.

  3. Then in new window, re-open the same order.

  4. System will perform the validation, as your last opened session on the order, was in draft state.

  5. The system will present you will a message prompt with 3 options.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.