Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
The new session timeout and dirty form page notifications in Rollbase help create a great user experience. Learn how to configure them and what they look like.
Progress Rollbase is a rapid application development platform which delivers cloud apps quickly and simply. Rollbase now provides an all new enriched UI in the latest release, which is user friendly and helps you develop contemporary responsive web applications with ease. On top of this new Rollbase, we have introduced notifications of two types:
These notifications were introduced in the Rollbase v4.2 release and these are applicable to New UI pages only.
The user can configure notifications at both the tenant and the user level. By default, the user settings are the same as the tenant setting. However, after changing the setting at the user level, this setting will take precedence over the tenant level. This means if an administrator changes the tenant setting, it has no effect on the user setting.
The user will be notified with a session timeout notification in the below two cases:
Note: In the case of a Rollbase Public Cloud, these properties are pre-set and the user cannot update them. The default values are inactiveSessionExpireMins: 60 mins and loginSessionExpireMins: 480 mins. So the user will get an inactive session notification if he is inactive for 55 mins. Along the same lines, the user will get a force logout notification if he is working on Rollbase continuously for 475 mins.
In the case of a Rollbase Private Cloud, the user can configure these properties in the securityLevel.xml file at the instance level.
Inactive Session: To test the inactive session notification (with our example of changing the corresponding value to 15), go to any app view page (New UI only) and keep the session idle for 10 mins.
A session timeout warning will appear in the UI which has a timer that starts at 5 mins
It contains two options: "Extend Session," which the user can click to extend the session, and "Log Out," which will be used to log out from Rollbase immediately.
Login Session Expire: To test the Login session notification (with our example of changing the corresponding value to 30), go to any app view page (New UI only) and maintain an active session for 25 mins
A session forced logout warning will appear in the UI which has a timer that starts at 5 mins.
It contains two options: "Continue," which can be used to continue your work, and "Re-login," which will force the user to log out and shows the log in form to login again.
By default, session timeouts are configured at the instance level. Users can override the instance level session timeout configurations at the application level. This means a user can enable, disable or modify the session timeout notification configurations at the application level using the client side SDK.
If user sets this property to false, then he will not see session timeout notifications whenever he accesses any page in this particular application.
If the user sets this property at the application level, then the user will get notified as per the value. This means if the user sets the value to 10, he will get notified for session timeouts and the timer will start at 10 mins.
<script id="executeBeforeUIStarts"> rb.newui.options.notify.sessionTimeoutNotifierPeriod = 10;</script>
This has been set to true by default. The default behavior logs the user out automatically once the "Session Forced Logout Warning" notification has been completed. If the user sets this to false, then he will simply see a "Session Expired" error growl notification after the completion of the "Session Forced Logout Warning" notification.
The User will see a dirty form page notification when he is leaving a dirty form (New or Edit) page. This will happen when navigating to any other page from New/Edit page while in the middle of filling out a form.
Chandrasekhar Gontla is currently working with Progress as a Senior QA Engineer. He holds Masters in Computer Applications from Osmania University, Hyderabad. He has strong knowledge in SaaS and PaaS products testing. He has written several whitepapers and blog posts on various topics related Rollbase and Cloud, and is an expert in UI testing for large-scale web-based Cloud applications. He has also given technology talks about Rollbase at various events such as Progress Exchange.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.