Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 51 Oracle Analytics and AI Sharing Center
- 19 Oracle Analytics and AI Lounge
- 288 Oracle Analytics and AI News
- 57 Oracle Analytics and AI Videos
- 16.3K Oracle Analytics and AI Forums
- 6.5K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 111 Oracle Analytics and AI Trainings
- 21 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Enhance Session Timeout Management with Warning Pop-Up and Auto-Save Options in HCM (OTBI)
Currently, users experience unexpected session timeouts in the Oracle HCM application, which results in the loss of unsaved updates and, at times, inaccurate data. There is no advance warning before a timeout occurs, nor is there an auto-save feature to preserve work in progress. For example, when updating audience criteria, users may complete their changes but are unable to save if the session has timed out, forcing them to redo their work after refreshing the session.
Use Case
Administrators and HR professionals frequently update audience criteria and other critical data within Oracle HCM. Without a warning prior to session timeout, users risk losing significant work, which leads to frustration, inefficiency, and potential data inaccuracies. Introducing a warning pop-up five minutes before a session timeout, along with a “Yes/No” prompt to refresh the session, would allow users to save their progress or extend their session proactively. This enhancement would reduce rework, improve data integrity, and enhance overall user satisfaction and productivity within the HCM environment.
Comments
-
Hi Nick,
Welcome to Oracle Analytics and AI community.
Is this specific to Oracle Application Learning module or any specific to Learning Subject area related OTBI reports?
Thanks.
0 -
Hi @MandeepGupta -
Thanks for welcome and the quick response.
This issue is not limited to any particular Learning subject area or module. It relates to the OTBI tool overall, which currently lacks an auto-save feature and can unexpectedly time out without warning. Ideally, the tool should only time out after a period of user inactivity, and if the user is actively working, the session should remain open. Introducing an inactivity-based timeout and auto-save functionality would enhance usability and prevent loss of work across all OTBI reports and modules.
Regards,
Nick
1 -
This makes sense now. I think you should drop Learning from post subject and body as it is for all subject areas.
Thanks.
0
