About Page View
The page view feature stores unsaved view and filtering data in the database by the artifact ID, such as the report ID or tracker ID, and user ID. This means that the user can reload the same view and filtering data after changing to a different browser.
The page view feature saves the current settings of a view, such as the report and tracker, without saving the view itself.
The logic based on the Permanent Links feature, you are able to save the current settings of a view (report, tracker etc) without actually saving the view.
The page view feature is available on the following pages:
• Document View
• Document Edit View
• Table View
• Traceability Browser
• Coverage Browser
• Planner
• Tracker Cardboard
• Release Cardboard
• Reports page
To create a page view, modify the view state and click to GO. When you click GO Codebeamer collects all the settings specific to the current page and saves them to the database, The page view is reloaded by the artifact ID and user ID. Page view saves also occur when you resize a column or make changes in a view data checkbox, as shown in the following imageCodebeamer will collect all the settings specific to the current page, save them to the database and it will be reloaded by the Artifact id and User id. Page view save also happen when you resize a column or click into a view data checkbox (outline config, resize column, panel view etc.).
You can delete the saved Page view by clicking to the revert button in the Report or in the Tracker view layouts.
Unsaved warning icon appears always, if the saved view and filtering data is not equals with the Page view metadata.
Special scenarios:
Report view page doesn't use Page view (but Report edit uses it!), so when you open a saved Report in the Report view page then we delete the saved Page view,
when you select a preset from the "Load/Manage Traceability Browser presets" it also doesn't use page view and it loads the saved Traceability preset,
after a layout change from Traceability to Table View or Document View then the Traceability Table View or Traceability Document View loads only if it was configured previously. (You must login to see this link. Register now, if you have no user account yet.)
How long do Page view live?
A page view by default is available for 30 day from the last update. This means that if no one modify the view or filtering data then Codebeamer will remove it from its database after 30 day. If you modify the view or filtering information then the counter restarts from zero.
You can override the default 30 days in the application configuration under System Administration using this snippet:
"pageView" : {
"timeToLiveInDays": 10
}
"timeToLiveInDays": 10
}
Page view restore logic use cases:
Pre-action
1. User opens Requirements tracker.
2. Page opens with default layout and view.
3. User loads a previously created view.
4. User adds filters.
5. Page saves state as preset.
Use case 1:
1. User navigates to the page through the menu (default layout / default view).
2. Page loads.
3. Page restores filters from the preset.
4. Page restores the view parameter in the URL.
Use case 2:
1. User navigates to the page with a URL containing view id
2. Page loads.
3. Page restores filters from the preset.
Use case 3:
1. User navigates to the page with a URL containing view id.
2. Page loads.
3. Page restores filters from the preset.
4. User switches to a different view.
5. Page updates filters.
6. Page saves state as new preset.
Use case 4:
1. User navigates to the page with a URL containing a different view id. (The view id is not the same as in the preset.)
2. Page loads.
3. Page does not load the preset.
4. Page saves the view as the new preset.
Use case 5:
1. User navigates to the page with a URL containing a different layout name and the same view id.
2. Page loads.
3. Page restores filters from the preset.