What is a Working Session?
A working session represents the active period during which you’re viewing and editing a risksheet. Think of it as your workspace: when you open a risksheet document, RISKSHEET establishes a session that tracks your edits, manages save operations, and maintains your view state. This session remains active as long as you interact with the risksheet or keep the browser tab open.
How Save Operations Work
When you edit a cell in RISKSHEET, the change is immediately queued for saving. RISKSHEET batches edits and commits them to Polarion’s work item repository within seconds. You’ll see visual feedback—a briefly highlighted cell or a status indicator—confirming that the save completed successfully. This continuous save model differs from traditional spreadsheet applications where unsaved changes remain in memory until you explicitly save the file. With RISKSHEET, every accepted edit is a committed change to the Polarion data model. What Gets Saved:- Cell value changes (text, enums, dates, numbers)
- New risk items or downstream tasks created through inline actions
- Link relationships established through column editors
- Bulk edit operations applied through context menus
- Column width adjustments (unless saved as a Saved View)
- Scroll position or selected cells
- Temporary filters applied through the interface
- Expanded/collapsed row states in hierarchical views
Session Timeout Behavior
Polarion enforces session timeout policies to protect server resources and security. By default, if you remain inactive in a risksheet for approximately 30 minutes, Polarion will prompt you with a timeout warning. You can choose to continue working (which renews the session) or allow the session to expire. Common Scenarios:| Situation | What Happens | Resolution |
|---|---|---|
| Editing actively | Session remains alive indefinitely | No action needed |
| Browser tab open but idle for 30min | Timeout warning appears | Click “Continue” to renew |
| Session expires while editing | Pending edits may not save | Refresh page and re-enter changes |
| Network interruption | Save operations fail silently | Check Save Failures |
Navigating Between Risksheets
When you navigate from one risksheet document to another—either by clicking a link in a Polarion document, opening a nested risksheet through cross-project linking, or switching browser tabs—RISKSHEET closes the current working session and establishes a new one for the target document. Each risksheet document maintains its own independent session. You can open multiple risksheets in separate browser tabs, and each will maintain its own working session with independent save queues and timeout tracking. Navigation Types: Same-Tab Navigation: Risksheet A → (click link) → Risksheet B- Session A closed
- Session B opened
- All pending saves in A flushed before navigation New-Tab Navigation: Risksheet A → (right-click, open in new tab) → Risksheet B
- Session A remains active in original tab
- Session B opened in new tab
- Both sessions independent
You can safely edit different risksheets in multiple browser tabs simultaneously. Each maintains its own working session and save queue. However, editing the same risksheet in two tabs simultaneously can cause conflicts if both sessions attempt to update the same work item field.
Session Interruptions and Recovery
If your session is interrupted unexpectedly—due to network failure, browser crash, or server restart—RISKSHEET’s continuous save model means you’ve already persisted most of your work. When you reload the risksheet, you’ll see the state of the data as of the last successful save operation. Recovery Checklist:- Refresh the risksheet page to establish a new session
- Verify recent edits appear in the grid (check work item revision history if uncertain)
- Re-enter any edits made in the seconds before the interruption
- Check for error messages in the browser console if saves continue to fail
Browser Tab Behavior
Closing a browser tab that contains an active risksheet terminates the working session immediately. RISKSHEET commits all pending save operations before the tab closes, but if the browser terminates abruptly (crash, forced quit), saves in the queue at that moment may not complete. Best Practices:- Allow saves to complete: After making edits, wait a few seconds for the save indicator to confirm persistence before closing the tab
- Avoid force-quit: Use normal browser close operations rather than force-quitting the application
- Check revision history: If uncertain whether an edit saved, view the work item’s revision history in Polarion to confirm the change was committed
Session State and Configuration
Your working session does not remember transient UI state like scroll position or selected cells. However, if you save a Saved View, RISKSHEET persists configuration choices like:- Column visibility and order
- Column width adjustments
- Applied filters or query parameters
- Sort order preferences
Concurrent Editing
RISKSHEET supports multiple users editing the same risksheet document simultaneously, each with their own working session. When two users edit different work items, their sessions operate independently with no conflicts. If two users edit the same work item field concurrently, Polarion’s work item locking and revision control mechanisms determine which edit persists. Typically, the last edit to commit wins, potentially overwriting the earlier change. RISKSHEET does not provide real-time collaborative editing with live cursor tracking; each user’s session saves independently to the Polarion repository.Related Topics
- Session Timeout Errors — Troubleshoot session expiration issues
- Save Operation Failures — Diagnose why edits aren’t persisting
- Saved Views — Persist UI configuration across sessions
- Architecture — Understand the server-side session management model