Restoring a Workspace
Clicking a node takes you back to what it captured. For most views that means more than the address: the filters, sort order and paging you had are put back too, so you land on the result you were looking at rather than the page it lived on.
What comes back
| Restored | Detail |
|---|---|
| The view | The page, module and record the node captured |
| Filters and sort | The query state that produced the result |
| Position | Where you were in a long result set |
| Selection | The row or item in focus, where the view supports it |
Where a node was captured with a thumbnail, the picture in the tree is what you should expect to see when it opens — a quick way to confirm you are clicking the right step.
When a view restores partially
Some views hold more presentation state than is sensible to keep. When that state was too large to store, the node falls back to opening its address with default settings.
You will notice this as landing on the right page with filters reset rather than as an error. The node itself is never lost, and its title, note and position in the tree are unaffected. Re-applying a filter is a small cost; a workspace that silently grew without limit would be a much larger one.
Large result sets
Restoring a large result does not fetch everything at once. eConnect brings back the first portion immediately so the view is usable, and the remainder loads as you scroll. A node that captured a result of tens of thousands of rows therefore opens at normal speed rather than pausing while the whole set is retrieved.
Across sessions and devices
My investigation belongs to the browser or client you built it in. Closing eConnect and coming back finds your tree as you left it; signing in on a different computer starts a fresh one.
If an investigation needs to survive a move between machines — or be handed to somebody else — share it. A shared workspace is stored on the server rather than locally, so it can be opened from anywhere. See Sharing a Workspace.
A shared workspace restores against your permissions, not the sender's. If a node points at data you are not entitled to, it will not open it for you. Nothing about the workspace bypasses the permissions described in Permission Groups.
Starting again
Clear in the tree header is the intended way to finish one investigation and begin the next: the exploratory steps go, the favorites and shared views you kept remain. See The Workspace Tree.